bladerunner.
rinxai@Zynewave wrote:
@UncleAge wrote:
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?
You can unhide the track lane for the effect track that is set as the bounce track. That will reveal the bounce event, which you then can drag to another track.
Some thoughts regarding dragging bounced tracks out to new tracks, of which I currently do a lot, I suggest a feature where one can select a single menu option which creates a new track and auto moves the bounced clip there, perhaps such an option could be listed by right clicking onto the bounced clip.
Else, new direction of Bounce implementation looks great.
R
ConquistadorUnhiding tracks is easy enough but I *really* like your idea for a new track that is auto created for bounced clips. Great.
swindus@rinxai wrote:
Some thoughts regarding dragging bounced tracks out to new tracks, of which I currently do a lot, I suggest a feature where one can select a single menu option which creates a new track and auto moves the bounced clip there, perhaps such an option could be listed by right clicking onto the bounced clip.
Thats a good idea!
aMUSEdHi
I hope you will have a realtime bounce/freeze – if it’s always faster than realtime it won’t work with many hardware/dsp synths and effects (even some plugins have problems with faster than realtime).
Conquistador@aMUSEd wrote:
Hi
I hope you will have a realtime bounce/freeze – if it’s always faster than realtime it won’t work with many hardware/dsp synths and effects (even some plugins have problems with faster than realtime).
Hi,
Apologies in advance if I have misunderstood your post…but Podium has had a realtime bounce feature for years. You can already easily bounce a VSTi’s output or even another audio tracks output to another track (or even the same track) in realtime….is that not the realtime functonality for bounce you were referring to in your post? ❓ ❓ ❓
aMUSEdYes but if there’s going to be a proper track freeze (not just recording one track into another) I’m saying that should have a realtime option too.
(I notice now though that Fritz has already anticipated this and discussed it further up)
Antal BodóczkiHallelujah!
Zynewave2.06 beta1 is available in the VIP lounge.
Changelog so far:
• The bounce waveform on hidden bounce tracks will be drawn on top of the events on the track lane.
• Bounce sounds on hidden bounce track lanes will automatically resize to fit the entire length of the arrangement.
• The “B” bounce button is shown on the track headers and mixer strips, if there is any bounce enabled track in the effect chain.
• The old “insert bounce track” menu command has been replaced with a “Bounce” submenu. All effect tracks in the chain are listed in the menu, making it possible to select at which point in the chain the bounce should be executed.
• The Bounce track submenu has a “Bounce Mode” submenu with options for selecting offline rendering or realtime recording mode.
• Tracks set to realtime recording bounce mode now have a dedicated “activate realtime record” option in the Bounce submenu. This replaces the previous realtime record method of activating both the bounce and record button. The bounce button is painted red when recording mode is activated.
• Added “hide bounce track lane” and “unload plugins when activated” options to the “Bounce” submenu.
• Changed the key shortcuts for switching bounce playback and rendering. Pressing the “B” button or the B shortcut key will now perform a render, effectively acting as a freeze button. Holding Ctrl while pressing B will switch playback of previously rendered audio.
• Starting a bounce render will automatically create a new sound event on the bounce track if the previous event has been deleted or moved to another track.
• Extended the “control type” combobox in tracks region properties with a choice for hiding all controls on the headers.
• The controls on the track panel in the inspector will use the control style selected in the inspector view menu.
Note that the new bounce mode options are not yet saved in the project file.
H-manCool,
I’m looking forward to checking this out. Thanks Frits.
Ben
LiquidProj3ct@Zynewave wrote:
• Extended the “control type” combobox in tracks region properties with a choice for hiding all controls on the headers.
• The controls on the track panel in the inspector will use the control style selected in the inspector view menu.
I didn’t understand these :S I didn’t see any change. I liked the new bounce tracks, now are more easy
UncleAgeAfter downloading 2.06 beta1, I only found three issues…
Issue#1
Example:
Master
–Track1
—-Reverb
—-EQ
—-TruePianos
**Offline Bounce**
In the bounce sub-menu it lists the name of the track and the effect tracks as the available choices. Except the track name is grayed-out and is not an available option. Which means in this case I can’t record TruePianos (at least not yet).
If I go into the track properties and enable the bounce feature, I can then go back to the track and bounce the main VST, TruePianos. At this point, in the bounce sub-menu, the track name is grayed out still but this time it has a check mark.
At this point if I choose one of the effect tracks for bouncing and then return to the sub-menu again to try and check mark the track name again:
1. The option is still grayed and won’t allow me to choose it as an option.
2. The option for bouncing audio is un-checked in the track properties as well.
In addition I would like to ask if it is proper to have the options split out into different menus (track properties vs bounce-sub menu). I know this may have been overlooked but I thought this would be a good time to bring it up.
Issue#2
Will “Realtime Bounce” keep the tail end of the audio? I’m not familiar with “Realtime Bounce” and was only using “Offline Bounce” in the above example. Either way the bounce rendered fine except it was the same length of the midi clip which means there wasn’t a trailing reverb at the end. Will “RealTime Bounce” correct this situation?
Issue#3
Let’s say I bounce at the EQ track. Then I change the sub-menu option to the reverb track because I want a rendered bounce at that stage in the tree. As soon as I change the option in the sub-menu the bounced audio in the EQ track is automatically transferred to the reverb track. No harm done really as I can move it or bouncerecord over the top of it. But I’m wondering why it wouldn’t just stay put and let me add another ender at a different stage in the chain.
All that said, I think this is a much needed addition to the app Frits. I like the Ctrl-B shortcut as well 🙂
Zynewave@UncleAge wrote:
After downloading 2.06 beta1, I only found three issues…
Thanks for testing.
**Offline Bounce**
In the bounce sub-menu it lists the name of the track and the effect tracks as the available choices. Except the track name is grayed-out and is not an available option. Which means in this case I can’t record TruePianos (at least not yet).If I go into the track properties and enable the bounce feature, I can then go back to the track and bounce the main VST, TruePianos. At this point, in the bounce sub-menu, the track name is grayed out still but this time it has a check mark.
At this point if I choose one of the effect tracks for bouncing and then return to the sub-menu again to try and check mark the track name again:
1. The option is still grayed and won’t allow me to choose it as an option.
2. The option for bouncing audio is un-checked in the track properties as well.
The track is grayed out because it should not be possible to bounce enable the bottom track in the chain. This is because the bounce sound events otherwise would overlap any other sound or note sequence events that is on the track. I’m going to change the track properties dialog so that the bounce options are disabled for the bottom track. I decided to include the grayed out track name in the menu, to keep the same chain structure as is shown in the Fader and Meter menus.
Note that if all tracks are grayed out in the bounce menu, enabling one of the options in the bounce mode submenu will insert a blank “Bounce” effect track above the bottom track.
In addition I would like to ask if it is proper to have the options split out into different menus (track properties vs bounce-sub menu). I know this may have been overlooked but I thought this would be a good time to bring it up.
I don’t have a problem with this. The same would apply to the Fader and Meter submenus. At least they are all located close to each other.
Will “Realtime Bounce” keep the tail end of the audio? I’m not familiar with “Realtime Bounce” and was only using “Offline Bounce” in the above example. Either way the bounce rendered fine except it was the same length of the midi clip which means there wasn’t a trailing reverb at the end. Will “RealTime Bounce” correct this situation?
Realtime bounce will not behave different to rendering in this respect. What I think will be my official recommendation is to put an “End” marker at the point where you would like the song fadeout to stop. The bounce sound events will resize to the position of the marker.
Let’s say I bounce at the EQ track. Then I change the sub-menu option to the reverb track because I want a rendered bounce at that stage in the tree. As soon as I change the option in the sub-menu the bounced audio in the EQ track is automatically transferred to the reverb track. No harm done really as I can move it or bouncerecord over the top of it. But I’m wondering why it wouldn’t just stay put and let me add another ender at a different stage in the chain.
Managing multiple simultaneous bounce tracks in an effect chain would complicate the bounce submenu I think. In these rare situations you will need to do a bit of manual work with the bounce options in the track properties dialog.
UncleAge@Zynewave wrote:
@UncleAge wrote:
**Offline Bounce**
In the bounce sub-menu it lists the name of the track and the effect tracks as the available choices. Except the track name is grayed-out and is not an available option. Which means in this case I can’t record TruePianos (at least not yet).If I go into the track properties and enable the bounce feature, I can then go back to the track and bounce the main VST, TruePianos. At this point, in the bounce sub-menu, the track name is grayed out still but this time it has a check mark.
At this point if I choose one of the effect tracks for bouncing and then return to the sub-menu again to try and check mark the track name again:
1. The option is still grayed and won’t allow me to choose it as an option.
2. The option for bouncing audio is un-checked in the track properties as well.The track is grayed out because it should not be possible to bounce enable the bottom track in the chain. This is because the bounce sound events otherwise would overlap any other sound or note sequence events that is on the track. I’m going to change the track properties dialog so that the bounce options are disabled for the bottom track. I decided to include the grayed out track name in the menu, to keep the same chain structure as is shown in the Fader and Meter menus.
Note that if all tracks are grayed out in the bounce menu, enabling one of the options in the bounce mode submenu will insert a blank “Bounce” effect track above the bottom track.
Once again I may be reading you wrong here but… Are you saying that, by design, we won’t be able to bounce the bottom track?
Zynewave@UncleAge wrote:
Once again I may be reading you wrong here but… Are you saying that, by design, we won’t be able to bounce the bottom track?
You will be able to bounce the output of the bottom track, but the bounce track need to be above it in the chain. That’s how the old “insert bounce track” command worked. You should not configure the bottom track to be both the bounce track and the instrument track, because the bounce sound events and the note sequence events would then overlap on the same track lane.
H-man@Zynewave wrote:
@UncleAge wrote:
Will “Realtime Bounce” keep the tail end of the audio? I’m not familiar with “Realtime Bounce” and was only using “Offline Bounce” in the above example. Either way the bounce rendered fine except it was the same length of the midi clip which means there wasn’t a trailing reverb at the end. Will “RealTime Bounce” correct this situation?
Realtime bounce will not behave different to rendering in this respect. What I think will be my official recommendation is to put an “End” marker at the point where you would like the song fadeout to stop. The bounce sound events will resize to the position of the marker.
Delays & reverbs bouncing just fine here in both modes? I did notice tho that the bouce track is sizing to something unrelated to the recorded audio.
Could this be the loop/punch-in marker even tho it’s not activated?