Zynewave's Forum Page

Thanks for the video. You’re not doing anything wrong. It’s just that the render within punch range is meant to work a little differently. What you expect is that the underlying track bounce file will be the size of the punch range. In fact, the underlying bounce file is always the full length of the arrangement. If you for example work with a long track with heavy plugins that takes a long time to render, you can use the render within punch range to just render the part on the timeline that you are currently working on, thereby greatly reducing the time required to render.

Instead of saving the bounce, reimporting it and cropping it, you could use the “move bounced audio to new track”, split the event on the new track, and use the “convert to unique cropped copy” on the fragment.

@duncanparsons wrote:

I fear it’s the latter so I’ll have to save fxbs of current settings, remap to the devices first in the VST tree, import the fxb, then delete the unwanted nodes.. would I be right in that assumption?

Yes. Sorry about that. I guess the reason you ended up with multiple Devices folders, is that you used the deprecated import feature found in older Podium versions. The merge project command replaced the import command, and it handles remapping mappings from the merge project to the mappings in the current project. It does not handle remapping redundant mappings within a single project.

I’ve now added support for the Del key in the file browser. It will be included in Podium/Podium Free 3.0.3.

I’ve checked the bounce rendering, and I don’t find a problem with rendering within a punch range. Remember that you must have both punch in and out mode enabled, and that you must use the “render within punch range” command. The normal render command will disregard the punch range.

Thanks for the file. I can load the project and start the arrangements ok with my RME ASIO driver. I of course do not have any of your sound files and plugins, so playback does not produce sound on my system.

The mappings in your project are quite messy. Both your audio inputs and outputs have duplicate (redundant) mappings, and you have three “Devices” folders, each with their own set of bus mappings and plugins.

Unless you already tried the “Merge Project” feature, I would suggest you create a new project with no arrangements, but with a clean set of audio/MIDI/bus/plugin mappings, and then merge your old project into the new one. Perhaps that will clear up some of the redundant mappings.

@michi_mak wrote:

EDIT : kingtubby provided his/her own shoot out with a different plug in on a different machine and came to the same conclusion …

Please reread my post earlier on this page, where I explained why kingtubby observed higher CPU usage.

@michi_mak wrote:

latest cpu shoot out :
1 wav file played in loop with 1 vst effect ( KUASSA Creme )

Zynewave : avg 18%
energyXT : avg 9%
REAPER : avg 2%

EDIT :

Studio One Pro : avg 11%
Live Lite 8 : avg 12%

i rest my case …

If those percentages are from Windows Task Manager, then the percentages include the entire application, including UI updating. That is why kingtubby notices that running Podium minimized results in lower CPU usage, because the UI in that case does not need to be animated. The Podium UI has been programmed to use available CPU power to animate the UI smoothly. The UI thread is lower priority than the audio engine, so if the audio processing takes a lot of CPU, then the UI CPU usage is reduced. You need to measure plugin CPU usage at a higher total percentage, to get comparable numbers. The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads.

@michi_mak wrote:

what do you hope to gain by changing presets?

Depending on the plugin, some preset settings may cause a higher CPU load, possibly leading to denormals. If you see 100% usage, then it is most often caused by denormals.

atm it seems that Podium suffers from cpu spikes when various plug ins have been changed / added / deleted for some time – but why does Podium use so much more cpu power ( charged by Windows Task Manager ) than say REAPER?

To repeat myself, try to pinpoint which plugin is causing you trouble. When we know that, it will be easier to go from there.

@michi_mak wrote:

issue might be related to “left overs” when changing / swapping plug ins …

One way to find out, is to save your project, reboot, load Podium and the project again, and check if the CPU usage is lower?