The Grid: Tips and Tricks

[xbitz]

I would modulate a DC Offset inside the Grid, Audio Rates modulator can see it and they can drive other Macros from any container device which can be assigned to anywhere inside the container

I don't really get it how is it any simpler for note generation and midi parameters sending.
EDIT: or perhaps you mean for blocking audio output from all the DC-offset clickers?

here's 2 channel more complex preset example

^^^ yepp... and we're done

[Emma Fletcher]

beta 2. once again, have fun

[Dirkitator]

easier perhaps.PNG

This is the easier way to step thru the merge module. It is important to select the merge modul an then click in the inspector the button nearest

And take care with the phase signal it goes from zero to 0.99 only. Other signals go from zero to one.

[sagetone]

I guess I've forgot to mention it in this topic. It is possible to do using Replacer device. For single note you could just send triggers directly to audio out (it will generate sharp square gate waves), for more you can employ DC offset device and modulate it from Grid, also putting Main note chain and any additional note chains into Instrument Layer under Grid FX chain. You would want to cut off sound after Replacer, so easiest way I found is to just drop HW FX device with no inputs or outputs selected (by default) in the Generator chain of the Replacer, or if you want multi-note sequencing, then place that device in the Note Layer FX chain.
For generated notes you just attach modulator and apply it to Note value of the Replacer, same method for Velocity.
Also you need to set up custom Transport module in the Grid and make sure to uncheck option for free-running when transport is stopped. See arrows in the screenshot for other things, like cutting off triggers on transport stop (otherwise if you stop on held note, it will go on forever).

Example preset in attachment

Thank you @x.iso! I'll work with your preset today to understand what you did. I am still not very familiar with Replacer, so need better understanding there. And, let's hope that the devs will provide us with MIDI out modules in The Grid soon, to make this really easy!

[odz]

Feedback

You can achieve rudimentary feedback by routing any signal to the "Modulator Out" device, then adding a "Value" device (in the Level group), then modulating the Value device by the Modulator Out, then routing the output of the Value back into whichever input port you couldn't originally send a feedback loop to. Here's an example with a sine oscillator modulating its own phase:



I assume there is some latency inherent in the feedback loop (one buffer probably) but haven't tested yet.

I just found out that you can do feedback loops so long as you include a device in the chain that requires that a delay is added. This works with e.g. the Long Delay, since it's minimum delay time is 0.02 ms. This does not work with mod delay, or delay, as they can be turned down to 0.00 ms. I'm not sure which other devices this works with, but it's easier and clearer than routing through a modulator.



1 sample in 44,100 Hz is 0.022 ms, and at 48,000 Hz it's 0.0208 ms. I assume that it will be rounded to a single sample, so this delay is something you can probably live with :p

Unfortunately it won't be 0.02ms, it will be at least 10ms in both cases (Modulator Out + Value or Long Delay).

Try to recreate https://en.wikipedia.org/wiki/Karplus–S ... _synthesis
You'll notice result pitch change as you make less delay time, but no change below 10ms. And min possible pitch will be the same in both cases (Modulator Out + Value or Long Delay with any delay <= 10ms)

Just checked this to verify, in Beta 2.

It seems like most delay settings are slightly off from what the dial on the module says, at least when bouncing. I can't say what it looks like in the signal path though. For anything < 40ms, it gets delayed by about 40 ms when bouncing. Other values get offset by a little bit here and there.

[ilmai]

I demoed the Dreadbox Erebus Mk3 today and was really impressed by it, and especially the unique bass sounds you can get using its Triple Ring feature. Well, it took me about two minutes to replicate it in The Grid and it sounds really nice!

Basically, it's taking a pulse oscillator to select between a sine and a triangle. Playing with the relative pitches (or disabling key tracking!) of the oscillators and pulse width results in some really interesting sounds. Try it!

[x.iso]

Thank you @x.iso! I'll work with your preset today to understand what you did. I am still not very familiar with Replacer, so need better understanding there. And, let's hope that the devs will provide us with MIDI out modules in The Grid soon, to make this really easy!

I found later that HW FX device that I put there for easy blocking of the audio output from the Grid and DC-shifting, is actually putting some significant delay to the track apparently, so better go with other options.

[x.iso]

Just checked this to verify, in Beta 2.

It seems like most delay settings are slightly off from what the dial on the module says, at least when bouncing. I can't say what it looks like in the signal path though. For anything < 40ms, it gets delayed by about 40 ms when bouncing. Other values get offset by a little bit here and there.

now this seems like a bug

[maschinelf]

Can anyone comment on how well (or badly) bitwig grid works with multi-touch?

[xbitz]

AD envelopes can be chained that's working nicely

etc.

[odz]

Just checked this to verify, in Beta 2.

It seems like most delay settings are slightly off from what the dial on the module says, at least when bouncing. I can't say what it looks like in the signal path though. For anything < 40ms, it gets delayed by about 40 ms when bouncing. Other values get offset by a little bit here and there.

now this seems like a bug

Thanks for pointing that out, I sent a detailed report to them

edit: They replied pretty fast, on a Sunday even!

thanks for your report – this is a known issue – actually a correct behaviour – but it needs to be clarified in the application.
Long Delay is the only delay to allow (freely configurable) Feedback loops, and thus the minimum delay time of Long Delay is your current audio buffer size.
The value display on the delay time dial does not show the actual delay times in that area currently.
We are looking to make it all clearer and less confusing.

All the best,
Bitwig Support Team

TL;DR It's not a bug, it's a feature.

[odz]

Also, I recommend this video:



He points out some things that aren't very intuitive about routing and how signals work. Well worth a watch.

[nbyte]

Here an additive approach to create some kind of MSEG.

[x.iso]

I've set up a drum sequencer with variable timed sub-sequences on different drums, quite usable already. Drum Machine is nested in the Grid, just change preset to whatever you like, adjust the notes of 'perc' and 'clap' so they land where needed in preset. Also the hi-hat is modulated in device chain to switch from closed to open hi-hat, you might need to adjust that depending on Drum Machine preset.

in this demo there's also Grid synth playing custom note sequencer made in Grid as well and combined with screen capture it was choking my CPU quite a bit


still, sequencer like this seem to tax CPU more than it should for the task, that is probably due to needless audiorate modulations, and that's why we need MIDI Grid without oversampling and modulations at rates that MIDI can't really handle. Should make much less impact on CPU.

[AuralBee]

@x.iso: That is a thing of bea(u)ty, thanks for sharing that!