3.2 (Beta 2) is OUT!!!

[mtelesha]

Changes in Bitwig Studio 3.2, Beta 2
Improvements

Toggle Device Window shortcut works even when device chain is not focused or visible
New Shortcut: Toggle Primary Device Window

Fixes

Disable variable buffer size processing for vst2 (caused problems with Serum and other VSTs)

[SmajjL]

Add Instrument Selector and put a Polysynth in there.
On Instrument Selector, right click and choose Load Default Preset, Bitwig will close aka Crash?

[lokanchung]

Add Instrument Selector and put a Polysynth in there.
On Instrument Selector, right click and choose Load Default Preset, Bitwig will close aka Crash?

Same thing happening here, please report to devs

[SmajjL]

As you wish, so it shall be done.
*done*

[w00t_b00ts]

Hello,

I'm still having issues with LFO Tool failing to load (could not load plugin).
To recreate the issue:
1. Open a new Bitwig 3.1 session
2. Drag LFO Tool (vst2 64bit) to track
3. Save & exit
4. Open project in Bitwig 3.2 Beta (1 or 2)

Thanks

[billcarroll]

Hello,

I'm still having issues with LFO Tool failing to load (could not load plugin).
To recreate the issue:
1. Open a new Bitwig 3.1 session
2. Drag LFO Tool (vst2 64bit) to track
3. Save & exit
4. Open project in Bitwig 3.2 Beta (1 or 2)

Thanks

Same here on Mac OS 10.15.4, with Bitwig 3.2 Beta 2, and LFOTool v1.708

Which was kinda awesome because I had to sidechain a pad to a kick with the Audio Receiver and EQ2, and I love this alternate way, and the possibilities are almost endless.

But yeah, LFOTool doesn't seem to load

[antic604]

Hello,

I'm still having issues with LFO Tool failing to load (could not load plugin).
To recreate the issue:
1. Open a new Bitwig 3.1 session
2. Drag LFO Tool (vst2 64bit) to track
3. Save & exit
4. Open project in Bitwig 3.2 Beta (1 or 2)

Thanks

Same here on Mac OS 10.15.4, with Bitwig 3.2 Beta 2, and LFOTool v1.708

Which was kinda awesome because I had to sidechain a pad to a kick with the Audio Receiver and EQ2, and I love this alternate way, and the possibilities are almost endless.

But yeah, LFOTool doesn't seem to load

You mean Audio Sidechain (modulator), right?

[billcarroll]

Hello,

I'm still having issues with LFO Tool failing to load (could not load plugin).
To recreate the issue:
1. Open a new Bitwig 3.1 session
2. Drag LFO Tool (vst2 64bit) to track
3. Save & exit
4. Open project in Bitwig 3.2 Beta (1 or 2)

Thanks

Same here on Mac OS 10.15.4, with Bitwig 3.2 Beta 2, and LFOTool v1.708

Which was kinda awesome because I had to sidechain a pad to a kick with the Audio Receiver and EQ2, and I love this alternate way, and the possibilities are almost endless.

But yeah, LFOTool doesn't seem to load

You mean Audio Sidechain (modulator), right?

Thanks for reading my mind, @antic604 I did mean the Audio Sidechain (modulator)

[psynical]

Please, please, please, can we please get a fix for VST windows opening behind other VST windows. Even though i'm opening the device after the current one in a chain, it should open above, not below the active window...
to repro:
-add a new track
-add a VSTi
-add a vst effect
result: the effect window will open behind the instrument window
this bad behavior has been around for as long as i've used Bitwig (v2) and it's really, really annoying.
thank you!

[mrfrenkie]

Please, please, please, can we please get a fix for VST windows opening behind other VST windows. Even though i'm opening the device after the current one in a chain, it should open above, not below the active window...
to repro:
-add a new track
-add a VSTi
-add a vst effect
result: the effect window will open behind the instrument window
this bad behavior has been around for as long as i've used Bitwig (v2) and it's really, really annoying.
thank you!

Confirm. Very annoying.

[antic604]

Please, please, please, can we please get a fix for VST windows opening behind other VST windows. Even though i'm opening the device after the current one in a chain, it should open above, not below the active window...
to repro:
-add a new track
-add a VSTi
-add a vst effect
result: the effect window will open behind the instrument window
this bad behavior has been around for as long as i've used Bitwig (v2) and it's really, really annoying.
thank you!

Never really noticed it (I think I never add an FX immediately after opening an instrument), but indeed it works - or doesn't work, rather - like like you describe.

[Vladislav_Gronk]

Please, please, please, can we please get a fix for VST windows opening behind other VST windows. Even though i'm opening the device after the current one in a chain, it should open above, not below the active window...
to repro:
-add a new track
-add a VSTi
-add a vst effect
result: the effect window will open behind the instrument window
this bad behavior has been around for as long as i've used Bitwig (v2) and it's really, really annoying.
thank you!

+1 it's so annoying.

[pdxindy]

+1

[lokanchung]

Bounce In Place into a new track by Alt-Draging a clip => crash

[dirtysnow]

Drum returns is a big UX improvement for me since there is a per-drum send, unfortunately right now can't load any Black Rooster Audio plugins there. Weird. Bug is reported, hopefully it gets addressed but who knows.. everything else worked there, and those plugs work elsewhere in the app.