Bitwig

risch · Post by **risch** » Fri Jan 13, 2017 8:40 pm

Hello everybody!

Regardless of the controversy around 2.0 - I think some space for purely discussing the software itself, will be fun! Love to talk about that with fellow producers, find some ideas for techniques i'd never have considered - esp with what the new functionality could bring.

Personally, I've found myself using the native devices almost 90% of the time in 1.x - especially because of the per-note pitch automation, and how the workflow works so fast for me. Polysynth 2.0 is really exciting!

I'm not sure what i'll do with some of the more esoteric modulators, as my music is more based on melodies and harmonies than textures, but I reckon it will easily create some inspiration.

Edit: resolved some grammatical errors xD

ThomasHelzle · Post by **ThomasHelzle** » Fri Jan 13, 2017 8:59 pm

What's really interesting is, that with the factory instruments, the new modulators can even be polyphonic, so you can for instance insert a LFO in polysynth, switch it to poly and have an additional, full, per-voice LFO available.
So in a way, this is already a kind of in-between-step to the modular system that for many people will already do a lot of what they want to do with that. Not everybody is into nodes and code, but this is very accessible to everybody IMO.
If you like the native devices, you should have even more fun in 2.x

Cheers,

Tom

risch · Post by **risch** » Fri Jan 13, 2017 9:40 pm

ThomasHelzle wrote:What's really interesting is, that with the factory instruments, the new modulators can even be polyphonic, so you can for instance insert a LFO in polysynth, switch it to poly and have an additional, full, per-voice LFO available.

Mind = blown

.jon · Post by **.jon** » Fri Jan 13, 2017 9:46 pm

How does the linking of modulators work, is it possible to link parameters into one modulator of one device to all devices on a track, or inside containers? Or even across tracks?

New and updated devices are cool, but that's pretty much there is to new features.

risch · Post by **risch** » Fri Jan 13, 2017 9:47 pm

I've done yet another double post...

Get too excited before posting

I don't want to bisect another thread!

Please see -> viewtopic.php?f=259&t=477232

Eta Carinae · Post by **Eta Carinae** » Fri Jan 13, 2017 10:21 pm

Any changes to VST multi out routing?

jonljacobi · Post by **jonljacobi** » Fri Jan 13, 2017 10:56 pm

Any changes to onset detection and automatically adding stretch markers?
Is the handling and timing of stretching versus raw audio with variable tempo been fixed?
I don't see any mention of multiple time signatures so I'll assume that's not there.

I know Tristan has the actual program. Anyone else? I want my beta.

u-u-u · Post by **u-u-u** » Fri Jan 13, 2017 11:02 pm

.jon wrote:How does the linking of modulators work, is it possible to link parameters into one modulator of one device to all devices on a track, or inside containers? Or even across tracks?

The modulators of a device can be routed to the parameters of that device and to parameters of devices that are nested into that device.
Also the modulators of one device can cross-modulate each other which is pretty awesome I think.
No, it's not across tracks. (at least not at the moment AFAIK - don't know whether it's planned to provide something like that in the future)

digitalfix · Post by **digitalfix** » Fri Jan 13, 2017 11:08 pm

u-u-u wrote:Also the modulators of one device can cross-modulate each other which is pretty awesome I think.

GTFI

The only other DAW I've seen do this is FL Studio. Cya I-L. It's been fun.

.jon · Post by **.jon** » Sat Jan 14, 2017 12:53 am

u-u-u wrote:
.jon wrote:How does the linking of modulators work, is it possible to link parameters into one modulator of one device to all devices on a track, or inside containers? Or even across tracks?
The modulators of a device can be routed to the parameters of that device and to parameters of devices that are nested into that device.
Also the modulators of one device can cross-modulate each other which is pretty awesome I think.
No, it's not across tracks. (at least not at the moment AFAIK - don't know whether it's planned to provide something like that in the future)

Right, so it looks like it's essentially the same modulation as before, just embedded into all devices instead of separate modulator devices, and with more options. It looks pretty cool in the screenshots, but pretty much all plugins already have modulation built in, so I'm not really sure how useful it is in practice.

ras.s · Post by **ras.s** » Sat Jan 14, 2017 1:10 am

.jon wrote:
u-u-u wrote:
.jon wrote:How does the linking of modulators work, is it possible to link parameters into one modulator of one device to all devices on a track, or inside containers? Or even across tracks?
The modulators of a device can be routed to the parameters of that device and to parameters of devices that are nested into that device.
Also the modulators of one device can cross-modulate each other which is pretty awesome I think.
No, it's not across tracks. (at least not at the moment AFAIK - don't know whether it's planned to provide something like that in the future)
Right, so it looks like it's essentially the same modulation as before, just embedded into all devices instead of separate modulator devices, and with more options. It looks pretty cool in the screenshots, but pretty much all plugins already have modulation built in, so I'm not really sure how useful it is in practice.

I think it's a great workflow improvement, or at least it looks like that.

I mean, right now you need to add a modulator, drag devices into it and then assign the modulation. If you want to change the modulator, you need to drag the devices out, add a new modulator, drag the devices in, ... In the new version it will be easier to add a number of modulators to something or switch them around.

Ie. a simple tempo-synced tremolo is much quicker to create by simply adding a Tool and going to its modulation page, add an LFO and that's about it. If you then want to use something else instead of an LFO, it'll be easier.

And apparently the modulators are going to be polyphonic with Bitwig instruments, which is quite something as well ..

contrast · Post by **contrast** » Sat Jan 14, 2017 1:40 am

If wonder if they are also polyphonic with VST3s that support note expression? I don't know exactly how all that stuff works.

Anyone know if there is a list of VST3s with note expression support somewhere? IIRC it's not very many of them but it would be interesting to know which ones.

risch · Post by **risch** » Sat Jan 14, 2017 1:47 am

contrast wrote:If wonder if they are also polyphonic with VST3s that support note expression? I don't know exactly how all that stuff works.

Anyone know if there is a list of VST3s with note expression support somewhere? IIRC it's not very many of them but it would be interesting to know which ones.

+this - I thought note specific pitch bend would translate to synthmaster 2.8 when they added MPE support, but wasn't the case. Is a bore having to remap my FM-4 sub to serum's pitchbend or similar xD

Echoes in the Attic · Post by **Echoes in the Attic** » Sat Jan 14, 2017 2:29 am

risch wrote:
contrast wrote:If wonder if they are also polyphonic with VST3s that support note expression? I don't know exactly how all that stuff works.

Anyone know if there is a list of VST3s with note expression support somewhere? IIRC it's not very many of them but it would be interesting to know which ones.
+this - I thought note specific pitch bend would translate to synthmaster 2.8 when they added MPE support, but wasn't the case. Is a bore having to remap my FM-4 sub to serum's pitchbend or similar xD

note specific pitch bend works for me with synthmaster. Using VST2. Have you set the pitch bend range to 48? If it's set to 2 you wouldn't notice the bend.

I just hope Bitwig will finally let us define the instruments pitch bend range so instruments with less than 48 note range will work correctly. Logic and cubase allow different ranges.

.jon · Post by **.jon** » Sat Jan 14, 2017 9:31 am

ras.s wrote:I think it's a great workflow improvement, or at least it looks like that.

I mean, right now you need to add a modulator, drag devices into it and then assign the modulation. If you want to change the modulator, you need to drag the devices out, add a new modulator, drag the devices in, ... In the new version it will be easier to add a number of modulators to something or switch them around.

Ie. a simple tempo-synced tremolo is much quicker to create by simply adding a Tool and going to its modulation page, add an LFO and that's about it. If you then want to use something else instead of an LFO, it'll be easier.

And apparently the modulators are going to be polyphonic with Bitwig instruments, which is quite something as well ..

Yes, it is an improvement and easily the best implementation of any DAW, my comment was more personal, I don't really see that much value for me in host-provided modulation in general- my plugins (mainly Reaktor) all have modulation, and then there's normal automation. But this iteration of Bitwigs modulation appears clever and well done- not a new feature, just an UX improvement.

What about freeze or grooves, are they coming in 2.0?

Bitwig

KVR Audio

Bitwig 2.0 - Functionality Discussion!