Topic: Preview 2.06: Bounce/Freeze

I really like where you are headed with this.

Question 1:
Let’s say I have set the track for “Bounce Playback” allowing the VSTi to unload and lighten the load on the cpu. And then a little later I decide that I want to keep this bounced audio “as-is”. Would I need to go back and “Bounce Render” or would I be able to copy the bounced audio (currently in a Bounced Playback state) out to another track?

Also, will there be color options to let us know which bounce ability would initiate when clicking the button?

So in other words I’m asking whether the 4 options in the menu are necessary. How about the ability to set the options in a track menu (Render/Playback) and then seeing the feedback in the background color state (for example: a red vs yellow). The click of the “B” button would yield one result or the other. The Boldface “B” would indicate the track was in a bounced state or not. Of course clicking a Boldfaced “B” would remove the render/freeze.

Of course I may be over simplifying things…

Please note, I am not trying to be argumentative in this response, I am trying to give you the most honest feedback I can…

I think that sometimes the flexibilty that is added sometimes creates more confusion. In this context I think what gets lost on a new user is the flexibilty that you are trying to provide. My point is that, in my previous question regarding visual feedback via the “B” button I was also trying to question the implementation of this featre.

If I am new to Podium and have used other DAWs I would wonder why I have to access the record feature through a menu. When I press the “B” button I want it to “Bounce/Freeze”. Once the bouce was created the track and button would stay in that state. Clicking the button again would unload the bounce. I guess I fail to see the need for both the record and playback options. In my mind I see the track going into a “Bounce Playback” state automatically after I record/create the bounce.

As an example:
I push the “B” button and the Bounce track is created: “B” turns red. Once the bounced track is created the button now sits as yellow to indicate that the track is now in a playback state. And if I were to click the button again the bounced track would disappear unloading the bounce. “B” button goes back to original state.

Am I missing something here?

@Zynewave wrote:

@UncleAge wrote:

When I press the “B” button I want it to “Bounce/Freeze”. Once the bouce was created the track and button would stay in that state. Clicking the button again would unload the bounce. I guess I fail to see the need for both the record and playback options. In my mind I see the track going into a “Bounce Playback” state automatically after I record/create the bounce.

That is precisely how I plan to implement it. The B button will then act precisely like the freeze button in other hosts. What you misunderstood is that the purpose of the “Activate Bounce Record” is to enable realtime-bounce recording, as opposed to rendering the bounced audio offline. You can ignore this option if you don’t have the need to bounce realtime for such things as external hardware, DSP hardware plugins and native plugins not capable of working faster than realtime. Perhaps this option will be more obvious if I renamed it to “Activate Realtime Bounce Record”?

I think this new bounce thing looks great 😀
But i also have to admit that the naming of the different bounce options could be very confusing.

I would name it like this:

Activate Slow Bounce

and

Activate Fast bounce

😀

Well, consider make an alternative bounce (ALT+B?) that render each clip in the same bounce track, then you could move and delete the clips without unfreeze (althought the delay type effects couldn’t be accurate).

Regards 🙂