Reread the topic, and noticed you said the crash also occurs during realtime-bouncing, in which case it’s not a memory issue.
Could you please try something, in order to home in the problematic track/plugins:
Backup your project, and create a duplicate project. In the duplicate project, delete each track/track group until you have only one track left. Do an offline bounce, and if this doesn’t crash, undo until you have undone the second last deleted track, and repeat the bounce. Continue like this until you reach the track that causes a crash. Then reload and delete all tracks except the track that caused a crash, and see if it still crashes. It’s much easier to debug, if we can isolate the problem to a specific track.
If you search for “nanokontrol” on this forum, you will find a few posts that indicate it should be possible to make it work. This is the preview topic back when the feature was implemented:
http://www.zynewave.com/forum/viewtopic.php?t=2783&start=0
I have limited knowledge of the nanokontrol, but I would guess you need to somehow switch it to support MCU mode. Check the Korg manual for that.
I can’t reproduce the crash here, but after some testing, I suspect the crash occurs because Podium runs out of available free memory. How much RAM do you guys have in your PCs?
I’ll investigate the memory consumption during bouncing, and see if I can optimize it.
@thcilnnahoj wrote:
Hmm, so you can’t reverse note “clusters” either (as in, simply swap two chords’ places on the timeline) unless they have the same number of notes (of which the note values can be swapped)…
Is there a workaround or trick to this, or is it just not what the function is intended for?
I considered implementing a reverse method like you describe, but there are scenarios where this would be tricky. It would make sense in the no. 2 example in your screenshot, but what if the last note was shorter and there was a pause at the end, how would you expect it to be reversed then? Reversing any non-quantized sequence of notes would mess up the timing.
I received your file, and I’ll have a look at it this weekend.
@thcilnnahoj wrote:
Is “gain strength” only relevant when using the absolute gain dial (the topmost one)?
Would you mind explaining its purpose to me, Frits? 😳
Because the only way I can think of using it is to set it to either 100 or 0 in order to choose between applying an absolute or relative gain setting,
which seems like a strange way to handle it, in my opinion.
Gain strength only applies to the gain value.
Say you have a bunch of sound events with varying gain offsets, that you feel are too random. You can then e.g. set the gain to -6 dB, and then use the strength dial to gradually pull the gain offsets towards -6 dB.
@thcilnnahoj wrote:
I’m having trouble with the reverse notes function though, as it seems to go crazy on drum grooves. Here’s a distilled example:
1. shows my original notes
2. is what I expected to get (judging from the function’s help text that it would simply flip notes horizontally)
3. is what it actually didWhat am I misunderstanding? 😕
The “reverse notes” will only reverse the note values of the selected events, and not the actual events. The same with the seperate velocities commands. So note timing is not affected.
I thought it useful to e.g. create up/down runs of a note sequence without affecting dynamics and timing.
Secondly, I expected the notes to retain their velocity levels – instead, the lowest note (most quiet in the original) is now the loudest after using the reverse function.
Only the note values are reversed. Do an additional reverse velocities, and they should follow along.
My email is listed on the ‘About’ page. It’s: info(at)zynewave.com
What ASIO buffer size do you use?
If you get constant overload during realtime bounce, try to increase the ASIO buffer size.
Does it crash if you bounce the individual tracks rather than the master track?
You could email me your project file, and I’ll check if there is anything on the timeline that causes Podium to mess up.
Often these kind of crashes are caused by plugins. If you have effect plugins on your kick drum track, try bypassing them, and see if it still crashes. Also try bouncing some of the other tracks. If some of these bounces do not crash, then try step by step to enable plugins, until you find the plugin that causes the crash.
@ishkabbible wrote:
Although I do find it a bit odd that the Podium CPU load indicator is bouncing between 60 – 90, yet the windows performance monitor is showing one core at around 40%, and the other 3 below 10% (yes, I am monitoring kernel time as well).
The Podium load indicator shows the amount of ‘time’ spent within the time available for each ASIO buffer. If you e.g. use only one plugin and that plugin uses all the time available, the Podium indicator will show 100%, even though only one core can be utilized.
I have been (incorrectly, it seems) assuming that the DAW simply spawns each instance of a given plugin off in its own thread, and lets Windoze manage them from there.
Your assumption was correct. A single plugin cannot be spawned on multiple cores though, unless the plugin itself has been coded to utilize multiple cores (like e.g. NI Kontakt).
Which VST SDK version does Podium use?
The latest before VST3, which is 2.4.
Any forums you can recommend for plugin developers?
The developer forum at kvr is a good place:
http://www.kvraudio.com/forum/viewforum.php?f=33
It’s possible that the ZynAddSubFx vst isn’t coded to support multiprocessing. Try to turn off the “enable multiprocessing” option in preferences, and check if this gets rid of the unwanted noises.