@Zynewave wrote:
The punch range render was meant as a time-saver. In case you changed just a few bars in a long track, you could redo the bounce within that range, and still keep the bounced audio of the previous full render.
I can see why that could be useful, and I don’t expect you to remove that behaviour, so consider my request as an extra feature/function.
@Zynewave wrote:
Podium automatically resizes the bounce sound event to the full arrangement length, so rendering within the punch range still requires that the bounce event is the full length of the arrangement.
Yes, so I’ll explain why this behaviour makes things a lot more complicated than they should be for my type of editing.
The following screenshot shows a voice over I have edited. Originally one file, I have cut the audio into finished takes, and now I need to turn each of the events into a separate WAV file so I can use them in a separate program.
I create a punch-in/out region for the first event and bounce the audio using “Render within punch range”. This is what I end up with:
So now I have a new audio file that is the duration of the entire arrangement, when what I need is an audio file that matches the duration of the event.
So now I move the bounced audio to a new track
and then I have to open the new track in the editor, crop it to the duration of the event, save it and re-import it to the project (to make sure the new file is the right duration).
For this particular arrangement I need to repeat all these steps 7 times. Imagine doing that for a complex arrangement, and you can quickly see how time consuming it becomes.
Is there already a simple way to generate separate, cut-to-length wavs from each event that I am missing?
Cheers,
Malcolm.
