Bitwig

antic604 · Post by **antic604** » Thu Mar 01, 2018 11:53 am

Shor wrote:Freeze tracks. And no, bounce in place is not a good replacement for this.

How is freezing tracks FUNCTIONALLY superior to the options we have in Bitwig? Sure, it takes few more clicks, but bouncing a track, disabling & hiding it doesn't take THAT much more work.

SLiC · Post by **SLiC** » Thu Mar 01, 2018 12:07 pm

antic604 wrote:
Shor wrote:Freeze tracks. And no, bounce in place is not a good replacement for this.
How is freezing tracks FUNCTIONALLY superior to the options we have in Bitwig? Sure, it takes few more clicks, but bouncing a track, disabling & hiding it doesn't take THAT much more work.

It does you bare right, its almost a macro; but given that it should be super-easy to implement and therefore a quick win for the Bitwig team and a time saver for those that freeze a lot.

pdxindy · Post by **pdxindy** » Thu Mar 01, 2018 12:25 pm

SLiC wrote:
antic604 wrote:
Shor wrote:Freeze tracks. And no, bounce in place is not a good replacement for this.
How is freezing tracks FUNCTIONALLY superior to the options we have in Bitwig? Sure, it takes few more clicks, but bouncing a track, disabling & hiding it doesn't take THAT much more work.
It does you bare right, its almost a macro; but given that it should be super-easy to implement and therefore a quick win for the Bitwig team and a time saver for those that freeze a lot.

I don't think it's even a time saver at all.

Yes, the initial act of freezing is a bit faster. But when you decide to unfreeze, make a small edit and refreeze, then bounce is faster... For example, with bounce, you can mute the bounced audio and try something on the original midi. There is no time spent having to refreeze if you prefer the original.

So I think if you count the whole process, freeze does not save time. Bounce might even be faster if you edit frequently.

zengel · Post by **zengel** » Thu Mar 01, 2018 12:26 pm

Total touchscreen integration with gesture with more than 2 fingers.

stamp · Post by **stamp** » Thu Mar 01, 2018 12:54 pm

Freeze! Absolutely!

And not that shitty Ableton freeze but something like Reaper where you can freeze at the point you want inside the chain and have multiple freeze points per track.

Hanz Meyzer · Post by **Hanz Meyzer** » Thu Mar 01, 2018 3:05 pm

For me it would be a gpu accelerated gui first. So optimally only doing this first with the whole team.

antic604 · Post by **antic604** » Thu Mar 01, 2018 3:07 pm

stamp wrote:(...)something like Reaper where you can freeze at the point you want inside the chain(...)

You can already do that using bounce-in-place, which bounces the device generating sound and leaves everything that's after it in the chain intact. Obviously - because this is Bitwig - you can put some of the effects into the FX slot of the instrument / VST and they will be bounced as well. To preserve the MIDI information just Ctrl+drag the clip to the Clip Launcher before bouncing.

You can also choose the bounce point when using regular *bounce* (just choose Custom in the pop-up window), but then you need to copy & paste the effects past the bounce point manually. Hope they'll automate that part.

odix · Post by **odix** » Fri Mar 02, 2018 12:17 am

Id also like a marry midi or keep midi for the bounce feature. If checked, as soon as you bounce the midi will be invisible but attached to the clip it rendered. To see it, you would just goto inspector or the midi and hit copy midi, or maybe shift cntrl c on the audio file, then youd have to paste the clip somehwere on the track.

And no the midi would not move with if you resized the audio clip, it will stay static. Even a full time second clip board would be cool that holds things like this.

Wait. A second clip board all the time would be genius.

JHernandez · Post by **JHernandez** » Fri Mar 02, 2018 3:18 am

What antic said, just copy midi clip to the Clip Launcher before bouncing.

Code: Select all

https://youtu.be/M1Y1V-T-iXs?t=42s

odix · Post by **odix** » Fri Mar 02, 2018 11:16 am

oh yea...thanks - Im terrible with that thing, never used it once. One day I will figure it out. I'm old school stuck in arranger

J-909 · Post by **J-909** » Sat Mar 03, 2018 12:13 am

I love the Bounce in place scheme in general, but would also find a freeze function useful. Specially if it is so customizable like has been said about Reaper.

Bounce (not necessarily in place) is a step forward when designing sound: you create a complex thing you like (CPU heavy creation), just bounce it and delete the making tracks. Sometimes it is just 2 seconds and won't need it anymore. Missing this in Live (choosing to apply sends, etc)

But when it comes to pad stuff or long musical stuff I miss the freeze function. I just want to click somewhere for it o be less CPU-hungry and I'm sure I will change something later on. Bounce in this case makes you occupie space and too many steps for me (renaming, rearraging, moving midi if it's "in place", etc).

meta-redundant · Post by **meta-redundant** » Sat Mar 03, 2018 12:52 am

I chose "Other" - and my "other" is for a timeline that can display TIME and not only bars/beats. IIRC the way Ableton does it is by putting a separate timeline at the bottom. Other DAWs let you toggle the main view back and forth. I understand this is not so important for the EDM people, but for the composer / sound design / mix / work-for-hire people, we're always discussing the timing of certain events.

ejgallego · Post by **ejgallego** » Sat Mar 03, 2018 1:20 am

meta-redundant wrote:I chose "Other" - and my "other" is for a timeline that can display TIME and not only bars/beats. IIRC the way Ableton does it is by putting a separate timeline at the bottom. Other DAWs let you toggle the main view back and forth. I understand this is not so important for the EDM people, but for the composer / sound design / mix / work-for-hire people, we're always discussing the timing of certain events.

This, I've recently started to do work with video and Bitwig is very hard to use for this reason. I am using cue markers, but they are far from optimal.

ejgallego · Post by **ejgallego** » Sat Mar 03, 2018 1:20 am

meta-redundant wrote:I chose "Other" - and my "other" is for a timeline that can display TIME and not only bars/beats. IIRC the way Ableton does it is by putting a separate timeline at the bottom. Other DAWs let you toggle the main view back and forth. I understand this is not so important for the EDM people, but for the composer / sound design / mix / work-for-hire people, we're always discussing the timing of certain events.

This, I've recently started to do work with video and Bitwig is very hard to use for this reason. I am using cue markers, but they are far from optimal.

odix · Post by **odix** » Sat Mar 03, 2018 4:03 am

i wish we could save track types on the fly, with the device chains. Say I want to add a kontakt but route the midi to bitwig ... add>presets>tracks>kontakt and itll just put in the tracks and all the necesarry routing information i already have stored. That would definitely make life easier. 2.3 is the money version for bitwig its now too hard to ignore. Zplane is the icing.

Bitwig

KVR Audio

[POLL] What next?

What do you miss the most?