3.2 (Beta 1) is OUT!!!

[SmajjL]

I think this forum ends up in my trashcan before Bitwig, i have complaints!
Ps, not all of you.. specially not you *top secret*

[Tj Shredder]

BWS still doesn't have MSEG modulator ... just need a lovely device around it with record-play buttons

The steps in the grid can now be abused for that, as it interpolates between steps. Set it to a high number and you can draw an envelope... Though I would still prefer a MSEG. To get at least a APDSR I usually combine several envelopes with aftertouch.

[SLiC]

...add a tick box to hide legacy devices in browser.

It is there already, in the right click menu for the browser: "Include Legacy Devices".

That's different:
1) It reveals them, not hides
2) It's only for the pre-2.0 modulation devices: LFO-Mod, Note-Mod, etc.

Perhaps the older EQ's will be hidden this way (and revealed this way) when its out of Beta?

Personally I have my EQ's in a collection (another for Reverbs, another for Dynamics etc) so I only see what I want to see anyway when I select EQ's.

[abique]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

Cheers,
Alex

[SmajjL]

Already getting good results with the Arp
But i wanted to go further using 3 different Polysynths, one for the barking, one for glide etc-stuff but the Instrument Selector is eeeeasy to break atm
Beta2 popped up btw.

[keel]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

Cheers,
Alex

Improvements

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

THANK YOU SO MUCH!

[Tj Shredder]

I just made a hack with the Array and Steps module to create a drawable waveform oscillator.
I bet this could be simplified. But as a first test...
It seems the content of the array is not stored in the preset, and there is a separate array per voice. At least there should be an option to have the same array for all voices, and it would make life a lot easier, if writing would not always require a trigger (also as option...) and of course an option to store the array with the preset - actually it doesn't need an option, it should, has to, must store it!

[abique]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

Cheers,
Alex

Improvements

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

THANK YOU SO MUCH!

Thank you, that was a really good suggestion.

[SLiC]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

Cheers,
Alex

Improvements

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

THANK YOU SO MUCH!

Thank you, that was a really good suggestion.

Seeing that exchange has made my day.

[keel]

Check your account; we made a very quick beta 2 update to address the vst2 issue with serum and some other vsts. I hope that it helps you testing, and sorry for that critical issue.

Cheers,
Alex

Improvements

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

THANK YOU SO MUCH!

Thank you, that was a really good suggestion.

Well, the joy didn't last long. Good news is, it is really working. The VST gui is popping up, but if I hit the same key again, it won't close the gui. So can you super please make it to close the gui in same button, if the gui is open? This is how it is working on S1, Cubase and even on Live. Please?

[abique]

Maybe bitwig did not have the focus and did not receive the key event?

[SmajjL]

Already getting good results with the Arp
But i wanted to go further using 3 different Polysynths, one for the barking, one for glide etc-stuff but the Instrument Selector is eeeeasy to break atm
Beta2 popped up btw.

Expressions/Select4/XY (Control) and A/B buttons and what have we - SchhmajjL.. problem?
Ps, you "thought" stuff again didn't you? *caught*
No problem SchhmajjL, thx..

Ps, harder to break Instrument Selector on beta2 (not happened, yet')

[keel]

Maybe bitwig did not have the focus and did not receive the key event?

It definately has the focus. If i hit the key, the gui open up every time, but simply doesn't close it, if I hit the key again. I need to close it on X every time. And when I close it on X, I hit the key again, the gui open. This is how it is working for me at least. Can you guys fix it?

[xbitz]

I just made a hack with the Array and Steps module to create a drawable waveform oscillator.
I bet this could be simplified. But as a first test...
It seems the content of the array is not stored in the preset, and there is a separate array per voice. At least there should be an option to have the same array for all voices, and it would make life a lot easier, if writing would not always require a trigger (also as option...) and of course an option to store the array with the preset - actually it doesn't need an option, it should, has to, must store it!

yepp, quite fun that it can record things, like automations

but without storing in the preset ???

[fwsuperhero]

I would love to see retrigger on evey step (like 1x,2x,4x,8x..) in the updated arpegiator too. It would make it complete imho. Like some drum machines have.

Great update, thanks.

You can use Note Echo for that and automate its on/off for certain notes.

Thanks for the tip. This is much more flexible for various rolls.