ZynewaveIt is also worth mentioning that you can use the Track menu to configure at which point in the master effect chain that you want the bounce to be extracted. So if you have moved the master fader or effects above the bounce point, then the bounced audio file will not include these effects.
ZynewaveZynewaveZynewaveHi John,
How do you check the memory leaks? When do they occur?
What do you use to check the high resource usage; The Windows Task Manager or the Podium CPU indicator? The Podium CPU indicator is not a measurement of how much your total available CPU power is utilized, rather it is a measurement of how close you are to experiencing audio drop outs. Podium Free is limited to only one CPU core for plugins, so if you e.g. have a quad-core machine, when the Podium indicator hits 100% the Windows task manager will show ~25%. The full Podium version uses all available cores.
Which plugins are crashing for you in Podium Free? I’m currently working on a revision of the plugin loading, so newer Podium versions should be more stable when loading plugins, but I cannot guarantee that plugins that previously crashed will not crash with the newer versions.
ZynewaveI don’t recall ever receiving the project file to test with, so no progress. If you can reproduce the problem, please email me a project file.
ZynewaveI have no experience with Linux, so I can’t help you there. The crash could be caused by the loading of the audio driver you previously have enabled. If you delete the Podium.ini file to reset your driver selections (and all other customizations you may have made), then Podium should at least be able to start up.
ZynewaveI will fix this for the next release. It’s of course unnecessary that the ‘Convert to unique cropped copy’ command copies the entire sound before it crops the copy.
Zynewavebtw are there plans for a Nucleum x64?
Unlikely. I used the SynthMaker tool to create Nucleum, and the developers of that tool currently have no plans of supporting x64 plugins.
ZynewaveAfter the release of 3.2.6 I have resumed my work on strengthening the plugin loading system. Still needs more work, so I can’t say when it will be ready for testing, but I sure hope 3.2.7 will fix the NI Kontakt loading crashes.
ZynewaveI have now ‘paused’ the caching on CloudFlare. Please let me know if this resolves the problem.
ZynewaveThanks for notifying me. Like the last time, I’m not seeing the problem here in Denmark. I updated WordPress a couple of days ago, which probably is the reason why this problem has resurfaced. I thought I had cleared the CloudFlare caches, but I’ve now done it again just to be sure. Give it a few hours, and let me know if the problem persists.
ZynewaveThanks. I fixed the garbage time position in the popup menus. It only appears in the Podium x86 version. There were a couple of other menus that had this problem as well. Podium 3.2.6 is now released.
ZynewaveBeta2 is up. The bug was related to the fade-in/out curves on the sound events. While working on fixing the bug I ended up doing another round of optimizations in the engine. Please let me know if the new beta fixes your crash problem. If there are no further issues I’ll probably release 3.2.6 this week.
ZynewaveThanks Nicholas. Bug confirmed. It is a side effect from the code optimizations I made for 3.2.5. I’ll post a new beta once I have fixed it.
ZynewaveSorry for not responding to this topic sooner!, but I’d just like to say that the upcoming Podium 3.2.6 has a new system for managing waveform images. No more .mini files. Instead there is a single central cache database in the Projects folder.