.@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.
@thcilnnahoj wrote:
It’s definitely an improvement. The only inconvenience is that you’ll have to go through the same menus a few times, whereas you could set everything up in one go in a ‘bounce dialog’ like CQSD suggested in another thread.
A big step forward Frits but…as thcilnnahoj said maybe one dialog box as suggested before, is better still. :-k
Why? The right click menu is more accessible for bounce options than before but I think more options are needed. That will make it even longer :-k
What are these additional options?
a. Render and replace file within Punch in range: That may likely solve Malcoms issue and make bounce files shorter, side stepping the need to crop files after a bounce.
b. Stereo to Mono Bounce Option. (Podium really needs a mono switch on each track as well IMO).
c. Multitrack bouncing:
1. Multitrack bounce (Ignore track FX)
2. Multitrack bounce (Ignore master FX)
d. Replace track events: Or bounce in place. This will overwrite any audio on the track being bounced…not just within the Punch in range as suggested in Point a.
e. Track file convert: When you want to Render a track you should have the file convert options pop up. As of the current beta you only get that when you export the file AFAICT.
As you can see that will lengthen the right click menu but in a dialog box (with drop downs) it will be far easier to navigate than even the existing options in 2.22 beta2.
UI changes…
There is a progress box that shows up during renders but really Frits it looks very strange as it just shows a progress bar and no info at all (time left e.t.c). Not nearly as useful as it could be unless some sort of time left info is added please. I suspect the recent changes with Bouncing will encourage users to do more of it so that screen will show up a lot more. Please do consider adding any kind of time info to it thanks.
I mentioned this problem here initially.
@Malcolm Jacobson wrote:
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.
Is there a reason why you want to use bounce for your export? In your screenshot you have no effects on the track, and there doesn’t seem to be fade-in/out on the individual events, so the bounced audio will be identical to the source audio.
If you just want to export the clips, you could use the “clone phantom sequence” and then “crop unique sequence” on each clip. Then you don’t need to do any edits in the sound editor, but just use the “export to sound file” command in the sound editor file menu.
@Conquistador wrote:
Why? The right click menu is more accessible for bounce options than before but I think more options are needed. That will make it even longer :-k
What are these additional options?
a. Render and replace file within Punch in range: That may likely solve Malcoms issue and make bounce files shorter, side stepping the need to crop files after a bounce.
b. Stereo to Mono Bounce Option. (Podium really needs a mono switch on each track as well IMO).
c. Multitrack bouncing:
1. Multitrack bounce (Ignore track FX)
2. Multitrack bounce (Ignore master FX)d. Replace track events: Or bounce in place. This will overwrite any audio on the track being bounced…not just within the Punch in range as suggested in Point a.
e. Track file convert: When you want to Render a track you should have the file convert options pop up. As of the current beta you only get that when you export the file AFAICT.
As you can see that will lengthen the right click menu but in a dialog box (with drop downs) it will be far easier to navigate than even the existing options in 2.22 beta2.
I’m sorry, but I don’t understand the intended use of most of these suggestions. I’m trying to simplify things, and keep the options to a minimum. I’d like to keep the bounce setup separate from options that deal with file export. That’s what the new “export to sound file” dialog is intended for.
The screenshot you show and some of your suggestions are a mixture of bounce options and file export options. The bounce feature in Podium is a way to reduce the CPU usage in the engine, and so bounced audio is an exact copy of the audio extracted from the engine at the bounce point. If you want to manipulate the bounced audio, then you do that by moving the bounced audio to a new track and do your edits there.
