The All In One Source Bitwig Information & Speculation Thread

Audio Plugin Hosts and other audio software applications discussion
Locked New Topic
RELATED
PRODUCTS
Bitwig Studio 6-25%$299.00Buy

Post

Suloo wrote:besides that the real modular system hasn`t been shown yet or demonstrated since it will be a v2 feature..
That is the real modular system already there in Bitwig. All current Bitwig devices are built with it. It is just that in V2 the user will have direct access.

Post

pdxindy wrote:The thing with Bitwig that is not clear, is how well the LFO works with a 3rd party plugin... with a Bitwig instrument, the parameter range is visible with the little modulation ring around each parameter. How will you see it and set it in a 3rd party instrument like say Diva?
Works just the same for VSTs and beautifully so.
One of the buttons in the interface shows a parameter list with everything the VST has on offer (with a search field - type "osc" and get a list with all parameters containing this string.
Each parameter has a slider next to it that can be used with the modulation system just as well as all internal parameters. You can set it to any value you want via this slider or the VST GUI and the modulation will work from/around that value.
Since the LFO and all other modulators in BWS are floating point and VST (and native) controls are too, you get smooth and fluid modulation without stepping.

Cheers,

Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

pdxindy wrote:
Suloo wrote:besides that the real modular system hasn`t been shown yet or demonstrated since it will be a v2 feature..
That is the real modular system already there in Bitwig. All current Bitwig devices are built with it. It is just that in V2 the user will have direct access.

sure, but all i mean is that we cannot compare it yet, since we didn`t see the full enabled version.
JamWide - a cross-platform Ninjam client for DAWs

Post

Here's a screenshot:
Image

The dark blue frames indicate modulateable parameters when the modulation arrow is active like in this example for LFO1.
The bright blue frame indicates a modulated parameter with the blue area showing the modulation amount. In this case the parameter itself is set to where the mouse pointer is and the modulation works in negative direction from there (can be positive or negative per parameter).

I entered "fr" in the search field since I wanted to control filter frequency, therefore the list is much shorter than normally where you see all parameters.

Cheers,

Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

Does Bitwig have a vocoder?
If so, can you use per-note automation with it?

Post

That Diva screenshot has got me fired up.. soon I'm going to have as many LFOs and envelopes in Diva as I want! Awesome!

Post

virtualmark wrote:That Diva screenshot has got me fired up.. soon I'm going to have as many LFOs and envelopes in Diva as I want! Awesome!
There is no envelope device in Bitwig... and the LFO would be global, not per voice...

Post

ThomasHelzle wrote:Here's a screenshot:
Image

The dark blue frames indicate modulateable parameters when the modulation arrow is active like in this example for LFO1.
The bright blue frame indicates a modulated parameter with the blue area showing the modulation amount. In this case the parameter itself is set to where the mouse pointer is and the modulation works in negative direction from there (can be positive or negative per parameter).

I entered "fr" in the search field since I wanted to control filter frequency, therefore the list is much shorter than normally where you see all parameters.

Cheers,

Tom
Thanks for the info...

Is there a way to show only modulated parameters? or a user defined group? Some synths have hundreds of modulatable parameters. I wouldn't want to have to do a search each time I wanted to find a particular one. Live lets you start with the list empty and add just the ones you want.

Also, when using the LFO with Bitwig instruments nested, say the Polysynth, can the LFO be per voice?

Post

The Mantra wrote:Does Bitwig have a vocoder?
If so, can you use per-note automation with it?
Not yet AFAIK.
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

pdxindy wrote:
ThomasHelzle wrote:Here's a screenshot:
Image

The dark blue frames indicate modulateable parameters when the modulation arrow is active like in this example for LFO1.
The bright blue frame indicates a modulated parameter with the blue area showing the modulation amount. In this case the parameter itself is set to where the mouse pointer is and the modulation works in negative direction from there (can be positive or negative per parameter).

I entered "fr" in the search field since I wanted to control filter frequency, therefore the list is much shorter than normally where you see all parameters.

Cheers,

Tom
Thanks for the info...

Is there a way to show only modulated parameters? or a user defined group? Some synths have hundreds of modulatable parameters. I wouldn't want to have to do a search each time I wanted to find a particular one. Live lets you start with the list empty and add just the ones you want.

Also, when using the LFO with Bitwig instruments nested, say the Polysynth, can the LFO be per voice?
That was actually one of my first feature requests: there is a knob to only show automated parameters and I would want to have the same for modulated parameters (could be the same knob IMO). It isn't in there yet but I was told it will make it in sooner or later.
(For the moment as a workaround you can add one automation value...)

The other thing is, that if you move a knob in for instance DIVA and have the automation lanes visible and not locked, the first (automatic) lane jumps to that parameter (very very very helpful when parameters aren't named too logical ;-) ) and I would like the same to happen for the VST parameter list.
So yes, this needs some improvements but I find it workable as it is and they liked my ideas so I guess this will grow soon enough ;-)

As for your second question: With nested you mean using Instrument Layers? Yes it can. You can have midi effects and modulators before the synth and fx after per layer. Can be built in or VSTs. Different arpeggios on each layer if you want...
The Pizimidi collection is great with BWS...

Cheers,

Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

ThomasHelzle wrote: As for your second question: With nested you mean using Instrument Layers? Yes it can. You can have midi effects and modulators before the synth and fx after per layer. Can be built in or VSTs. Different arpeggios on each layer if you want...
The Pizimidi collection is great with BWS...

Cheers,

Tom
I mean, if you add an LFO then nest the Polysynth in the LFO FX slot so you can modulate a polysynth parameter... can those modulations of the Polysynth by the LFO be per voice?

Post

ThomasHelzle wrote:
That was actually one of my first feature requests: there is a knob to only show automated parameters and I would want to have the same for modulated parameters (could be the same knob IMO). It isn't in there yet but I was told it will make it in sooner or later.
(For the moment as a workaround you can add one automation value...)

The other thing is, that if you move a knob in for instance DIVA and have the automation lanes visible and not locked, the first (automatic) lane jumps to that parameter (very very very helpful when parameters aren't named too logical ;-) ) and I would like the same to happen for the VST parameter list.
So yes, this needs some improvements but I find it workable as it is and they liked my ideas so I guess this will grow soon enough ;-)
Yeah, sounds like that could use some improvement... Actually, I would suggest that it just follow Live. An option of starting with the list empty and adding what you want is direct and clean.

As you say, parameters do not always have logical names so a search function will also not always find what you want.

This is a case where Live got it right (after a while)

Post

pdxindy wrote:
ThomasHelzle wrote: As for your second question: With nested you mean using Instrument Layers? Yes it can. You can have midi effects and modulators before the synth and fx after per layer. Can be built in or VSTs. Different arpeggios on each layer if you want...
The Pizimidi collection is great with BWS...

Cheers,

Tom
I mean, if you add an LFO then nest the Polysynth in the LFO FX slot so you can modulate a polysynth parameter... can those modulations of the Polysynth by the LFO be per voice?
I don't think so.

Edit: I think these kinds of things will be possible with 2.0 and the modular system.
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

pdxindy wrote:
virtualmark wrote:That Diva screenshot has got me fired up.. soon I'm going to have as many LFOs and envelopes in Diva as I want! Awesome!
There is no envelope device in Bitwig... and the LFO would be global, not per voice...
Ah I didn't realise there wasn't an envelope. Still it should open up a ton of options on Diva. I love that synth but it really could do with more modulation sources, this will definitely help.

Post

i believe an envelope won`t be that much of a problem to code for them..
JamWide - a cross-platform Ninjam client for DAWs

Locked

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”