ZynewaveHi,
The easiest way is to do a complete DB rebuild, provided that you haven’t customized your plugin DB. You can also load the plugin DB project, reorganize the added/updated folders, and then resave the DB.
ZynewaveZynewave@Me le suono! wrote:
I set the six channels in the Sound Properties dialogue (5.1 surround), but during playback, I only hear the stereo channels. 👿
One of the limitations in Podium Free is that playback is restricted to two channels. If you try the Podium Demo, you should be able to verify that your surround file and routing is ok.
ZynewaveIf you want to apply fades or gain changes to bounced audio, you need to move it to a new audio track. These soundevent features are blocked when placed on bounce tracks, because otherwise redoing a bounce would not result in an identical reproduction of the unbounced audio.
ZynewaveZynewaveZynewaveThose of us here who have taken the time to renew and discuss Feature Requests are often met with no response at all from Zynewave when a simple, ‘yes, I will add that’ or ‘no, I can’t fix that’ would have been plenty and appropriate.
Yes, I intend to improve plugin support in the future. The plugin MIDI out routing was first discussed years ago on this forum, and back then I also said that I plan to support it. If it was a simple thing, I would have implemented it already. The problem is that I have received feature requests to keep me occupied for the next twenty years. Each user has his own idea of what essential features are missing.
ZynewaveZynewaveZynewaveHave you verified that it also crashes when you do a realtime-bounce recording rather than offline rendering?
I’m still suspecting it’s a memory issue, rather than CPU power issue, but if the realtime render crashes, I’m not sure the memory issue is the cause of your crash.
ZynewaveIf you’ve used the segment tool to cut/paste segments, it can result in segmentation of the bounce tracks. This is a point on my todo list that I intend to improve in the future. Hidden bounce tracks really shouldn’t be chopped up like the regular audio tracks.
You can verify this problem by right-clicking the wide “Bounce” button in the master track group in the track inspector rack, and deselect “Hide track lane”. To clean up the bounce track, deselect the bounce mode on the master track, and then redo the bounce.
ZynewaveReread 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.
ZynewaveIf 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.
ZynewaveZynewaveI 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.