Bitwig Studio 4 announced (+beta available)!

[antic604]

Using a clip as a midi device would be very cool to me

Can you elaborate on this idea?

[pdxindy]

Although in my case, I'll only be installing native plugins when I get an Apple Silicon Mac.

Serious question, why would you limit yourself in such a way if other plug ins still ran fine, just not 'native'?

Cause I would still have a feast of options... in practice, it would be no limitation at all.

[syntonica]

Also, Apple will most definitely drop Rosetta 2 in the next OS version or two. The same fate as Rosetta 1. (RIP)

[apoclypse]

However I get what you mean. Logic for example still doesn’t have gain handles on audio clips after years (decades at this point) of begging from users. The workflow is as clunky as Bitwig in that regard as you can only change gain via the inspector.

If you're referring to what I think you are, Bitwig actually now edges out Logic in this regard and your information may be outdated. You can just drag from the top anywhere on an audio clip to adjust gain.

I wasn't saying Bitwig didn't have clip gain. I was referring to the my original post that Bitwig requires you to use the Inspector to edit multiple tracks volume, pan, mute, and solo buttons. I know what features Bitwig has and how they work.

[apoclypse]

So like I mentioned, with the way selections are now in Bitwig what you selected can be globally changed and by carefully grabbing the volume or solo, mute, etc. you can still adjust things in the selection whilst retaining the global selection. It's almost like VCA faders. In a DAW like Live I don't see any way to do this? I'm messing with it right now and selected items all conform to the global selection no matter what modifier key I press. so in more complex selctions of tracks you're having to deselect then reselect to do the same thing you can do in one step in Bitwig. IMO it's slight complexity that doesn't sacrifice features, to use the Info panel for global selections.

Right but that doesn't address things like being able to drag and drop effects across multiple channels which you can't really do in Bitwig now, or affect sends across multiple channels which you can't do in Bitwig now. With the way things work now it would be very difficult and complex to do these things from the inspector.

[id4kvr]

WTF??? They list support for Apple Silicon as a major new feature for V4? That's beyond absurd!

that's native support, there is no other DAW natively support Apple Silicon except Logic Pro right now.

[dplduffy]

lot of threads, i am barging in this one.

how strictly is bitwig for upgrades, my upgrade plan expires at june 26. V4 is expected end Q2/begin Q3, it can land on june 26, or a week later, or even later.

has anyone experience with this?

i am fine with the 3.3.x version, although i thought, i would do the upgrade plan when 4 arrives...
but it is coming too soon...

so, i won't weep, but still, if you can get it... so? experiences? is june 26 very fixed (it must be in a way, but 2 days later? o well i will not hold it against bitwig, as i said, still working with 3.3.x and gives me what i want, next to all other DAW's i have..)

I'm in the same boat as you (June 17 expiration). I e-mailed them to ask, I'll report back.

thanks! i wanted to do the same thing. i wait for your report...

Support said that it’s based on when full release comes out, not the beta, but they will review on a case by case basis if the dates are close. Not sure how “close” it has to be but sounds like at least they are willing to accommodate some people.

[_leras]

Using a clip as a midi device would be very cool to me

Can you elaborate on this idea?

sure - at the risk of you telling me how I can already do it!

instead of having e.g. an arpegiator it would be great to be able to drop in a midi clip. then e.g. holding middle C would play the clip, different note would transpose playing the clip, and a new note would start the clip from the beginning again (maybe an overlapping note would just change the pitch and not restart).

So I guess a 'phrase' sequencer based on a clip. Why a clip - well because we already make loads of them in our projects anyway - so it's an easy building block imo.

[WasteLand]

lot of threads, i am barging in this one.

how strictly is bitwig for upgrades, my upgrade plan expires at june 26. V4 is expected end Q2/begin Q3, it can land on june 26, or a week later, or even later.

has anyone experience with this?

i am fine with the 3.3.x version, although i thought, i would do the upgrade plan when 4 arrives...
but it is coming too soon...

so, i won't weep, but still, if you can get it... so? experiences? is june 26 very fixed (it must be in a way, but 2 days later? o well i will not hold it against bitwig, as i said, still working with 3.3.x and gives me what i want, next to all other DAW's i have..)

I'm in the same boat as you (June 17 expiration). I e-mailed them to ask, I'll report back.

thanks! i wanted to do the same thing. i wait for your report...

Support said that it’s based on when full release comes out, not the beta, but they will review on a case by case basis if the dates are close. Not sure how “close” it has to be but sounds like at least they are willing to accommodate some people.

thanks for your information. i expected this. of course there must be a deadline, or...
but if it is for instance 2 days... we hope! that it will close enough!

live 11 suite was released faster than i thought/expected, which i also own..

so, it is in the hands of the code!

thanks again!

(and usefull info for others, with the same situation.)

[_leras]

Although in my case, I'll only be installing native plugins when I get an Apple Silicon Mac.

Serious question, why would you limit yourself in such a way if other plug ins still ran fine, just not 'native'?

Cause I would still have a feast of options... in practice, it would be no limitation at all.

Yeah, but if you had a plug in that ran fine just not native - why wouldn't you want to use it?

[pdxindy]

Also, Apple will most definitely drop Rosetta 2 in the next OS version or two. The same fate as Rosetta 1. (RIP)

Yup, that is the other reason. Any plugins that don't port are eventually toast.

[pdxindy]

Serious question, why would you limit yourself in such a way if other plug ins still ran fine, just not 'native'?

Cause I would still have a feast of options... in practice, it would be no limitation at all.

Yeah, but if you had a plug in that ran fine just not native - why wouldn't you want to use it?

I figure if I am not using Rosetta, it is likely to be a bit more stable, a bit more efficient, one less variable for something to go wrong or be a problem.

Also, the writing is on the wall. Rosetta will get dropped in a few years. I prefer to just get to it and move forward. And like I said, I got plenty of plugins.

[EnGee]

There is a big list that is compatible with native M1. I have installed yesterday u-he betas, sugar Bytes, Synapse Audio, Valhalla, TDR and TAL. All are working fine with beta 4 except Synapse Audio (not showing, although they show in Logic). So, things are moving fast.
I have tried to find an easy way to remove Rosetta 2, but there isn't.

[antic604]

Using a clip as a midi device would be very cool to me

Can you elaborate on this idea?

sure - at the risk of you telling me how I can already do it!

instead of having e.g. an arpegiator it would be great to be able to drop in a midi clip. then e.g. holding middle C would play the clip, different note would transpose playing the clip, and a new note would start the clip from the beginning again (maybe an overlapping note would just change the pitch and not restart).

So I guess a 'phrase' sequencer based on a clip. Why a clip - well because we already make loads of them in our projects anyway - so it's an easy building block imo.

Yeah, that would be sweet! There's a lot of devices like that for Reason, holding multiple clips/phrases inside:




Something similar but simpler could be hacked in Bitwig (even using Arpeggiator because it now has those pitch offset lanes), but what you propose would be ideal!

[machinesworking]

So like I mentioned, with the way selections are now in Bitwig what you selected can be globally changed and by carefully grabbing the volume or solo, mute, etc. you can still adjust things in the selection whilst retaining the global selection. It's almost like VCA faders. In a DAW like Live I don't see any way to do this? I'm messing with it right now and selected items all conform to the global selection no matter what modifier key I press. so in more complex selctions of tracks you're having to deselect then reselect to do the same thing you can do in one step in Bitwig. IMO it's slight complexity that doesn't sacrifice features, to use the Info panel for global selections.

Right but that doesn't address things like being able to drag and drop effects across multiple channels which you can't really do in Bitwig now, or affect sends across multiple channels which you can't do in Bitwig now. With the way things work now it would be very difficult and complex to do these things from the inspector.

Looking at DAWs I own personally DP, Logic, Reaper, Live and Bitwig, none of them do what you want. Unless I'm misunderstanding, I'm on Live 10, but you can't drag effects to multiple channels in Live either. None of the other DAWs here automatically place the VST on multiple tracks if multiple tracks are selected. Which DAW do you use that you're looking at this and wishing Bitwig did it this way?