DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)

[Dopplgngr]

Hi Moss, fantastic new release 16.4 with all the note operators supported which brings the Elektron sequencer workflow to Bitwig/Maschine

One feature suggestion: could you implement a "pragmatic recurrence" play on every Nth instance (first / last) in step editing? It's a key feature for fills, crashes etc in the Elektron workflow and more controlled than random only.

UI idea: Remove the two >LENGT parameters (redundant on 3 pages) from chances page to make room for:
RECUR: OFF / 2 / 3 / 4 / 5 /6 / 7 / 8 (Recurrence Length)
RESTPS: FIRST / LAST / MID / NOT FIRST / NOT LAST / EVEN / ODD (Recurrence Steps)

[toovy]

Hi Jürgen,

great work, I'm so happy that I can use the launchpad pro (mkIII) with bitwig! Thanks a lot!

I'm currently building a live setup using some hardware and bitwig as live looper with effects, primarily using the custom view to crossfade between the live track and the recorded loop, map various FX on/off buttons and control the FX mix value. Primarily I want to create awesome transitions between song sections that I cannot easily program on my Syntakt (which acts as main sequencer, drives some other synths).

Imagine it like this:

• I record a 4 bar loop in the session view from the live signal (Syntakt)
• In the custom view I use a fader to fade between the live and loop track (brilliant that I can map two bitwig controls to the same fader with inversed values)
• I trigger a 4 bar drum roll + white noise riser in the session view
• I go back to the custom view and switch on some effects (yes, switch them on using faders)
• then I slowly fade the effects in using the main FX mix (mapped to a FX chain mix)
• in between I mute/unmute some tracks on the Syntakt (or other hardware)
• when the transition is over (at the end of the 4 bars) I set the fader which fades between loop and live signal to 0 => back to live signal, no FX any more

Well, while this works I asked myself, If the custom view could be "better". I imagined that instead of having 8 big faders it could consist of a mix of controls that would better suite a live situation. I thought of e.g. (see attachment)

• having a small 4x4 session view (record the loop, start 4 bar drum rolls, risers)
• a 4x2 button/switch grid (push buttons in bitwig, e.g. FX on/off, Midi CC buttons I guess)
• a 4x2 drum view (improvise drum fills, trigger one-shots, Midi Notes I guess)
• 8 faders, half size (each 1x4, Midi CCs I guess)

So the big question is: With all your experience, is it possible to create something like this? I'm a developer, Java lies back a couple of days, but maybe, if you point me into the right direction, I could help with this).

BR, toovy

Sure, you can do such things. Did you watch the new Bitwig videos with Richie Hawting? He did (or let do ) exactly such tuned scripts for his workflow.
If you want to get started with coding, check out the Bitwig API series (playlist) on my Youtube channel. That should set you on the right track!

Hi again, Jürgen,

of course I saw it, I think Bitwig positioned it very prominently . Thanks for linking the playlist, I've already watched a couple of tutorials, good work! Still one question left for the time being, would you see the feature I described as part of DrivenByMoss (e.g. with a setting that changes the way the "custom view" works)? Or would you rather say that it should be a completely new script? I mean, I love all the other functions of DrivenByMoss... so starting with a completely new script would be daunting I guess, as probably I would rebuild 95% of DrivenByMoss

[moss]

Hi Moss, fantastic new release 16.4 with all the note operators supported which brings the Elektron sequencer workflow to Bitwig/Maschine

One feature suggestion: could you implement a "pragmatic recurrence" play on every Nth instance (first / last) in step editing? It's a key feature for fills, crashes etc in the Elektron workflow and more controlled than random only.

UI idea: Remove the two >LENGT parameters (redundant on 3 pages) from chances page to make room for:
RECUR: OFF / 2 / 3 / 4 / 5 /6 / 7 / 8 (Recurrence Length)
RESTPS: FIRST / LAST / MID / NOT FIRST / NOT LAST / EVEN / ODD (Recurrence Steps)

Can you point me to the section of a Elektron manual where this is described? Did not fully get how this should work.

[moss]

...
Well, while this works I asked myself, If the custom view could be "better". I imagined that instead of having 8 big faders it could consist of a mix of controls that would better suite a live situation. I thought of e.g. (see attachment)

• having a small 4x4 session view (record the loop, start 4 bar drum rolls, risers)
• a 4x2 button/switch grid (push buttons in bitwig, e.g. FX on/off, Midi CC buttons I guess)
• a 4x2 drum view (improvise drum fills, trigger one-shots, Midi Notes I guess)
• 8 faders, half size (each 1x4, Midi CCs I guess)

So the big question is: With all your experience, is it possible to create something like this? I'm a developer, Java lies back a couple of days, but maybe, if you point me into the right direction, I could help with this).

BR, toovy

Sure, you can do such things. Did you watch the new Bitwig videos with Richie Hawting? He did (or let do ) exactly such tuned scripts for his workflow.
If you want to get started with coding, check out the Bitwig API series (playlist) on my Youtube channel. That should set you on the right track!

Hi again, Jürgen,

of course I saw it, I think Bitwig positioned it very prominently . Thanks for linking the playlist, I've already watched a couple of tutorials, good work! Still one question left for the time being, would you see the feature I described as part of DrivenByMoss (e.g. with a setting that changes the way the "custom view" works)? Or would you rather say that it should be a completely new script? I mean, I love all the other functions of DrivenByMoss... so starting with a completely new script would be daunting I guess, as probably I would rebuild 95% of DrivenByMoss

I think that is too specific.

[killmaster]

I updated to the new Launchpad X firmware 2.0 today and was just trying to follow the sequencer instructions in the manual and it doesn't appear to be working as expected. Note and Raindrop are blank and poly only shows the bottom half.

[moss]

I updated to the new Launchpad X firmware 2.0 today and was just trying to follow the sequencer instructions in the manual and it doesn't appear to be working as expected. Note and Raindrop are blank and poly only shows the bottom half.

Make sure that there is an existing MIDI clip selected in Bitwigs' clip launcher.

[Dopplgngr]

Hi Moss, fantastic new release 16.4 with all the note operators supported which brings the Elektron sequencer workflow to Bitwig/Maschine

One feature suggestion: could you implement a "pragmatic recurrence" play on every Nth instance (first / last) in step editing? It's a key feature for fills, crashes etc in the Elektron workflow and more controlled than random only.

UI idea: Remove the two >LENGT parameters (redundant on 3 pages) from chances page to make room for:
RECUR: OFF / 2 / 3 / 4 / 5 /6 / 7 / 8 (Recurrence Length)
RESTPS: FIRST / LAST / MID / NOT FIRST / NOT LAST / EVEN / ODD (Recurrence Steps)

Can you point me to the section of a Elektron manual where this is described? Did not fully get how this should work.

It's on page 47 - but that A:B mathematical UI approach is a bit different than Bitwig's visual UI approach. Not sure if my approach above is closer to Bitwig UI (Recurrence Length + Recurrence Steps)

A:B A sets how many times the pattern (or track, if the track length is shorter than the pattern length) plays before the trig condition is true. B sets how many times the pattern (or track, if the track length is shorter than the pattern length) plays before the count is reset and starts over again. This cycle then repeats until you stop the sequencer.
For example:
With the setting 1:2, the trig condition is true the first time the pattern plays and then the third, the fifth, and so on.
With the setting 2:2, the trig condition is true the second time the pattern plays and then the fourth, the sixth, and so on.
With the setting 2:4, the trig condition is true the second time the pattern plays and then the sixth, the tenth, and so on.
With the setting 4:7 the trig condition is true the fourth time the pattern plays and then the eleventh, the eighteenth, and so on.

Source: https://cdn.www.elektron.se/media/downl ... 220202.pdf

[Dopplgngr]

RECUR: OFF / 2 / 3 / 4 / 5 /6 / 7 / 8 (Recurrence Length)
RESTPS: FIRST / LAST / MID / NOT FIRST / NOT LAST / EVEN / ODD (Recurrence Steps)

Can you point me to the section of a Elektron manual where this is described? Did not fully get how this should work.

Maybe a few examples show how to hardware control Bitwig's visual UI with knobs:

RECUR: 5
RESTPS: MID
=> _ _ X _ _ (as in screenshot below)
RECUR: 2
RESTPS: FIRST
=> X _
RECUR: 4
RESTPS: LAST
=> _ _ _ X
RECUR: 8
RESTPS: NOT FIRST
=> _ X X X X X X X
RECUR: 7
RESTPS: EVEN
=> _ X _ X _ X _

[jaaypeso24]

I know this forum is an endless list of support requests for Moss, but I want to take a second just to say thank you to Moss for all of your hard work over the years to develop and support controller extensions that help so many of us use devices we love in a DAW that we love.

Ironically enough, the Push 2 works better for me in Bitwig than it does in Ableton Live lol. I'm being serious. In Live I get random connectivity issues and can't change the control strip to control faders, midi CCs, etc.

[moss]

I know this forum is an endless list of support requests for Moss, but I want to take a second just to say thank you to Moss for all of your hard work over the years to develop and support controller extensions that help so many of us use devices we love in a DAW that we love.

Ironically enough, the Push 2 works better for me in Bitwig than it does in Ableton Live lol. I'm being serious. In Live I get random connectivity issues and can't change the control strip to control faders, midi CCs, etc.

Thank you!

[davidchesley]

Push 2 script for Bitwig is amazing! Appreciate your work, Moss! I was just wishing there was a note latch feature, and I just went and saw that it was recently added - serendipitous.

I have a small feature request, which I'm hoping it would be quite simple to implement. I would like to have another scale layout which ascends in fifths. I've recently got accustomed to this tuning on guitar, and I'm sure a lot of classical stringed instrument players would enjoy it as well. Cheers

[killmaster]

I updated to the new Launchpad X firmware 2.0 today and was just trying to follow the sequencer instructions in the manual and it doesn't appear to be working as expected. Note and Raindrop are blank and poly only shows the bottom half.

Make sure that there is an existing MIDI clip selected in Bitwigs' clip launcher.

Thanks! That was it, though I could swear that I did have a clip the first time it failed but it worked this time.

[moss]

Maybe a few examples show how to hardware control Bitwig's visual UI with knobs:

RECUR: 5
RESTPS: MID
=> _ _ X _ _ (as in screenshot below)
RECUR: 2
RESTPS: FIRST
=> X _
RECUR: 4
RESTPS: LAST
=> _ _ _ X
RECUR: 8
RESTPS: NOT FIRST
=> _ X X X X X X X
RECUR: 7
RESTPS: EVEN
=> _ X _ X _ X _

Thanks for the explanations. I think it would make sense to add this to the Recurrence Pattern page as some kind of presets.

[moss]

Push 2 script for Bitwig is amazing! Appreciate your work, Moss! I was just wishing there was a note latch feature, and I just went and saw that it was recently added - serendipitous.

I have a small feature request, which I'm hoping it would be quite simple to implement. I would like to have another scale layout which ascends in fifths. I've recently got accustomed to this tuning on guitar, and I'm sure a lot of classical stringed instrument players would enjoy it as well. Cheers

I am pretty sure I will not touch this, scales always drive me nuts
You can check out the lately added "Staggered" layout which makes it pretty easy to play chords (press 3 pads horizontally).

[Bjørnson]

Hi Jürgen, thanks for all your generous controller surface work!
If you are ever contemplating about adding a drum mode like the new Richie Hawtin Fire script: I think it's nearly possible to use your "poly note sequencer mode" like this for drums. But at the moment adding single notes to one step erases the existing ones. I like the context of the active drum events next to selected edited line... Much easier on my brain.

And thanks also for teaching videos on how to get into programming controller surfaces! I will try my baby steps with a custom Fire controller script as a little side project