Bitwig

Apheo · Post by **Apheo** » Thu Jan 31, 2019 7:16 am

JHernandez wrote: Wed Jan 30, 2019 10:00 pm Oh yeah, no doubt. I love me some noise too, I just happen to have some already. Just curious.

There is something on the volca called Woogle that can produce something like noise if routed properly.

aer72 · Post by **aer72** » Fri Feb 01, 2019 8:14 pm

It seems like the workflow is going to be much more intuitive than Reaktor Blocks. I just hope it has the same sound quality, because despite the somewhat unfriendly workflow of Reaktor (due to it's complexity) it sounds outstanding (to me at least).

u-u-u · Post by **u-u-u** » Fri Feb 01, 2019 10:53 pm

Enkerli wrote: Thu Jan 31, 2019 1:15 am
pdxindy wrote: Tue Jan 29, 2019 5:47 pm
CRAFTMATIX wrote: Tue Jan 29, 2019 5:31 pm Yes I am sure you are right...Again it was just me "wishing" it was a priority now.
A fine wish!

My wish from the videos is that more people asked them questions.

For example, I would like confirmation that the Poly Grid is automatically MPE capable, that it can use per voice modulations and voice stacking like other Bitwig synths.
Good questions.
The Synth Anatomy did involved some pretty useful questions (especially the ones about CPU load). And, since Dave used the onscreen keyboard in a way which sounded like the “pitchbend per note” mode, it’s close to confirmation that MPE works as it should, in The Grid.
Modulation per voice and voice stacking are separate issues but, at this point, it almost feels like the company should warn us if they’re not supported.

Captured from -> here you can clearly see the Pitch, Timbre and Pressure input modules for Poly Grid:

io modules - poly grid.JPG

u-u-u · Post by **u-u-u** » Fri Feb 01, 2019 10:58 pm

From the same NAMM video:

level modules.JPG

I love things like the Bi->Uni/Uni->Bi modules

+ I'd like to know what this 'level scaler' module will do

(looks like it takes 2 dB values but why?)

pdxindy · Post by **pdxindy** » Sat Feb 02, 2019 1:00 am

I would like to know if there is a way to trigger things besides note ons. For example, is there some way to trigger an envelope without a note?

Broken · Post by **Broken** » Sat Feb 02, 2019 5:06 am

pdxindy wrote: Sat Feb 02, 2019 1:00 am I would like to know if there is a way to trigger things besides note ons. For example, is there some way to trigger an envelope without a note?

They've claimed any signal can be patched to any destination, so we can probably assume that any signal could potentially trigger an envelope.

pdxindy · Post by **pdxindy** » Sat Feb 02, 2019 5:35 am

Broken wrote: Sat Feb 02, 2019 5:06 am
pdxindy wrote: Sat Feb 02, 2019 1:00 am I would like to know if there is a way to trigger things besides note ons. For example, is there some way to trigger an envelope without a note?

They've claimed any signal can be patched to any destination, so we can probably assume that any signal could potentially trigger an envelope.

I would say that is promising, but is not confirmation of yes.

SLiC · Post by **SLiC** » Sat Feb 02, 2019 9:07 am

Hopefully we will all know everything in a few weeks....I just hope that this time they have prepared a manual to go with the beta so we can read up and how things are supposed to work rather than just try to work it out by playing!

u-u-u · Post by **u-u-u** » Sat Feb 02, 2019 10:40 am

pdxindy wrote: Sat Feb 02, 2019 1:00 am I would like to know if there is a way to trigger things besides note ons. For example, is there some way to trigger an envelope without a note?

At least from transport there seems to be a trigger output (the yellow one I guess):

lfo modules.JPG

EDIT: and the clock module with a settable frequency + phase reset trigger input (i guess) also looks interesting

EDIT2: also this patch obviously has some envelope triggering. Also look at the AND modules which don't let any trigger pass if the transport is stopped:

env triggering.JPG

u-u-u · Post by **u-u-u** » Sat Feb 02, 2019 10:55 am

Converning the patch above: I ask myself what the purpose of those (gate(blue), value(), note(orange)) sequencer modules is. Is there a possibility to save patterns or automate the steps?
Probably not, because steps modulator steps also cannot be modulated. Also for the note sequencer it would be interesting if we could paste notes from arranger clips there. Or maybe it would be cool if we could edit the note sequencer modules notes in the proper note editor. Or link it to a note clip.

jarnold · Post by **jarnold** » Sat Feb 02, 2019 11:28 am

SLiC wrote: Sat Feb 02, 2019 9:07 am Hopefully we will all know everything in a few weeks....I just hope that this time they have prepared a manual to go with the beta so we can read up and how things are supposed to work rather than just try to work it out by playing!

This x1000.

pdxindy · Post by **pdxindy** » Sat Feb 02, 2019 2:28 pm

u-u-u wrote: Sat Feb 02, 2019 10:40 am
pdxindy wrote: Sat Feb 02, 2019 1:00 am I would like to know if there is a way to trigger things besides note ons. For example, is there some way to trigger an envelope without a note?
At least from transport there seems to be a trigger output (the yellow one I guess):

EDIT: and the clock module with a settable frequency + phase reset trigger input (i guess) also looks interesting
EDIT2: also this patch obviously has some envelope triggering. Also look at the AND modules which don't let any trigger pass if the transport is stopped:

Thanks... that is looking very promising...

sufista · Post by **sufista** » Sun Feb 03, 2019 5:51 am

pdxindy wrote: Sat Jan 26, 2019 1:05 am
sufista wrote: Fri Jan 25, 2019 11:57 pm I want to hear what other changes are to Bitwig 3 other than the grid...
I think the Grid is it... and it is enough by itself

Fair enough, I'm sure there will be more. Beta will tell all haha

pdxindy · Post by **pdxindy** » Sun Feb 03, 2019 6:37 am

sufista wrote: Sun Feb 03, 2019 5:51 am
pdxindy wrote: Sat Jan 26, 2019 1:05 am
sufista wrote: Fri Jan 25, 2019 11:57 pm I want to hear what other changes are to Bitwig 3 other than the grid...
I think the Grid is it... and it is enough by itself
Fair enough, I'm sure there will be more. Beta will tell all haha

Actually, at NAMM, the Bitwig guy said there are a few other things in v3 that they have not announced because they want to focus on the Grid. I wouldn't expect them to be big things... but some things still

kpv · Post by **kpv** » Sun Feb 03, 2019 11:23 am

I'm pretty sure the other Bitwig 3 features will be amazing as well, but The Grid is obviously the prom queen. This is probably the update that will win alot of new users over to Bitwig, both those who have been on the fence for a while, and those who have never heard about it before. I'm surprised how "few" users seem to be active in the Bitwig threads on Muff Wiggler, but I'm sure that's about to change. My ES3 is ready!

2.5 is IMO a rather remarkable workflow / performance update - audio editing in Bitwig is getting pretty good, to say the least - so I wouldn't be surprised if the piano roll will get some love in 3.1 or 3.2, since that's one of Bitwig's obvious "weaknesses" and one of the things most users (at least from the "what is next / top 3 feature requests" threads) want to see updated long time ago. I'm pretty excited to see how the clip blocks will affect the arrangement view, since I use the "create a new scene from all currently playing clips" feature all the time while experimenting, and I work alot in the luncher before I start arranging. So personally, I find the clip blocks to be more exciting than legato clips, but than I'm not particularly interested in playing live at all.

We need more midi experimental tools, particularly step sequencers and intuitive chord devices so we can say goodbye to M4L once and for all.

Bitwig

KVR Audio

Bitwig NAMM 2019 videos