Zynewave's Forum Page

@siegfried wrote:

Is it hard to implement, Fritz?

It’s not a difficult thing to implement, but it will take some time. I have a few other things on my todo list that have a higher priority.

Sounds like you’ve set it up correctly if you intend to mix multiple stereo tracks into the rear channels reverb. If you only need to add the reverb to the one stereo track, then you could insert the reverb on that stereo track, and then skip the first send/return routing.

@Infinitoar wrote:

But just a question: Have you ever thought that feature should do that? And if so, “would” you implement it?

It would mess up the underlying bounce system if the bounce file should not cover the entire arrangement length. If you did multiple renders within punch range in different timeline positions, the bounce track would include a growing number of fragmented bounce files.

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.