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

[unknownError]

Hi Jürgen! And thanks for drivenByMoss!

I have a bug report for Push 2 in note repeat mode. It is changing its note length setting after some time.

I was playing for a longer time in drum machine mode and using "step repeat", 16/3rds because it was so enjoyable . Maybe it was just 15 minutes of drumming but possibly it was also much longer. Then suddenly the note length switched to a slower setting (longer note) but I didn't check which note length exactly. It felt like either jumping from 16th/3ds to 16ths but might have been less too. Will try to find that out exactly next time it happens. I continued jamming around after setting it back to 16th/3rds and it happened again a few times. Also tried a fresh project with only minimum config (drum machine + drum synths) and happened again after some time.

I was using the lower left 16 pads to trigger drums, either individually but also using several pads at once and might have pressed also some of the other pads next to the 16 lit up drum pads accidently, but definitely not touching the repeat button or the note length buttons again. No recording or playing of any clips or tracks.

Arch Linux, Bitwig 4.2.3, Push 2, icon i-key midi keyboard, alsa.

[moss]

Hi Jürgen! And thanks for drivenByMoss!

I have a bug report for Push 2 in note repeat mode. It is changing its note length setting after some time.

I was playing for a longer time in drum machine mode and using "step repeat", 16/3rds because it was so enjoyable . Maybe it was just 15 minutes of drumming but possibly it was also much longer. Then suddenly the note length switched to a slower setting (longer note) but I didn't check which note length exactly. It felt like either jumping from 16th/3ds to 16ths but might have been less too. Will try to find that out exactly next time it happens. I continued jamming around after setting it back to 16th/3rds and it happened again a few times. Also tried a fresh project with only minimum config (drum machine + drum synths) and happened again after some time.

I was using the lower left 16 pads to trigger drums, either individually but also using several pads at once and might have pressed also some of the other pads next to the 16 lit up drum pads accidently, but definitely not touching the repeat button or the note length buttons again. No recording or playing of any clips or tracks.

Arch Linux, Bitwig 4.2.3, Push 2, icon i-key midi keyboard, alsa.

Never heard of such an issue. If you are sure that you did not accidently hit anything (you did also not set the ribbon to the resolution?) try Bitwig support.

[unknownError]

Hi Jürgen! And thanks for drivenByMoss!

I have a bug report for Push 2 in note repeat mode. It is changing its note length setting after some time.

I was playing for a longer time in drum machine mode and using "step repeat", 16/3rds because it was so enjoyable . Maybe it was just 15 minutes of drumming but possibly it was also much longer. Then suddenly the note length switched to a slower setting (longer note) but I didn't check which note length exactly. It felt like either jumping from 16th/3ds to 16ths but might have been less too. Will try to find that out exactly next time it happens. I continued jamming around after setting it back to 16th/3rds and it happened again a few times. Also tried a fresh project with only minimum config (drum machine + drum synths) and happened again after some time.

I was using the lower left 16 pads to trigger drums, either individually but also using several pads at once and might have pressed also some of the other pads next to the 16 lit up drum pads accidently, but definitely not touching the repeat button or the note length buttons again. No recording or playing of any clips or tracks.

Arch Linux, Bitwig 4.2.3, Push 2, icon i-key midi keyboard, alsa.

Never heard of such an issue. If you are sure that you did not accidently hit anything (you did also not set the ribbon to the resolution?) try Bitwig support.

Thanks. It was the ribbon control. Oops. Sorry.

[unknownError]

And it's me again with another question It's about selecting a preset page for one of the drum machine's instruments using the ableton push 2. I try to select a preset page as immediate as possible (without further menu selection) so I don't need to interrupt drumming, e.g. by directly calling up a perform page for a specific drum pad using the associated pad.

So far I found the drivenByMoss setting "Auto select drum setting" which instantly shows the selected drum pad's instrument's mixer controls. Is there a way to show the same instrument's perform page instead? Also thinking further for playing this would become difficult to play if it always automatically switches:

imagine this scenario:
- auto switching to the perform page when hitting a certain drum pad (e.g. kick drum)
- adjusting several parameters of the kick drum
- hitting other drum pads will call up their perform page so the last selected perform page for kick drum is "lost", which might be undesirable...

So a kind of latching-mechanism to keep a perform page would be useful.
e.g. pressing and holding "shift" + triggering a "pad" activates the perform page of the selected pad. (or alternatively the foot pedal input so hands free drumming is possible...)

A pretty old thread touching the topic:

To actually switch a preset from a controller, you would need a bit of script since its in the API and there is nothing to my knowledge with MIDI learn in the DAW for changing a preset.

Pseudo code that would get the job done, minus errors from my over critical brain.

Code: Select all

var CC_NEXT_DEVICE = 42;
var CC_PREV_DEVICE = 43;

var cursorDevice = null;

function init ()
{
    cursorDevice = host.createEditorCursorDevice ();
}

function onMidi (status, data1, data2)
{
    // only iff MIDI cc is 42, 43 and the value sent is 127
    if (isChannelController (status) && data2 == 127)
    {
        switch (data1)
        {
            case CC_NEXT_DEVICE:
                cursorDevice.switchToNextPreset ();
                break;
            case CC_PREV_DEVICE:
                cursorDevice.switchToPreviousPreset ();
                break;
        }
    }
}

Mike

I'd also try to start scripting here, but maybe it makes sense to include something like that into drivenByMoss too

[moss]

And it's me again with another question It's about selecting a preset page for one of the drum machine's instruments using the ableton push 2. I try to select a preset page as immediate as possible (without further menu selection) so I don't need to interrupt drumming, e.g. by directly calling up a perform page for a specific drum pad using the associated pad.

So far I found the drivenByMoss setting "Auto select drum setting" which instantly shows the selected drum pad's instrument's mixer controls. Is there a way to show the same instrument's perform page instead? Also thinking further for playing this would become difficult to play if it always automatically switches:

imagine this scenario:
- auto switching to the perform page when hitting a certain drum pad (e.g. kick drum)
- adjusting several parameters of the kick drum
- hitting other drum pads will call up their perform page so the last selected perform page for kick drum is "lost", which might be undesirable...

So a kind of latching-mechanism to keep a perform page would be useful.
e.g. pressing and holding "shift" + triggering a "pad" activates the perform page of the selected pad. (or alternatively the foot pedal input so hands free drumming is possible...)

A pretty old thread touching the topic:

To actually switch a preset from a controller, you would need a bit of script since its in the API and there is nothing to my knowledge with MIDI learn in the DAW for changing a preset.

Pseudo code that would get the job done, minus errors from my over critical brain.

Code: Select all

var CC_NEXT_DEVICE = 42;
var CC_PREV_DEVICE = 43;

var cursorDevice = null;

function init ()
{
    cursorDevice = host.createEditorCursorDevice ();
}

function onMidi (status, data1, data2)
{
    // only iff MIDI cc is 42, 43 and the value sent is 127
    if (isChannelController (status) && data2 == 127)
    {
        switch (data1)
        {
            case CC_NEXT_DEVICE:
                cursorDevice.switchToNextPreset ();
                break;
            case CC_PREV_DEVICE:
                cursorDevice.switchToPreviousPreset ();
                break;
        }
    }
}

Mike

I'd also try to start scripting here, but maybe it makes sense to include something like that into drivenByMoss too

The quoted code is from a completely different discussion (and outdated as well).

As a work around you could map the performace controls to the user page(s) amd store it in a template.

[exelio]

Hi Jürgen,

Will your MCU improvements be available on the Behringer X-touch One too?
There is no option button on it, and the channel's color is not reflected on the display with your last update.

A big thank for your work!

[moss]

Hi Jürgen,

Will your MCU improvements be available on the Behringer X-touch One too?
There is no option button on it, and the channel's color is not reflected on the display with your last update.

A big thank for your work!

Sadly, no. The color commands are not available on the One.

[exelio]

Hi Jürgen,

Will your MCU improvements be available on the Behringer X-touch One too?
There is no option button on it, and the channel's color is not reflected on the display with your last update.

A big thank for your work!

Sadly, no. The color commands are not available on the One.

Yes, very sad what about the cue markers commands?

[cmd-r]

Hello Jürgen, a huge thank you for the sensational scripts!

Since Bitwig is still new territory for me, I probably have a newbie question.

The Elektron plugin offers separate tracks to all outputs of my Rytm. Bitwig offers a super simple solution and automatically creates all separate output channels in form of chains? The Launch Control faders skip these separate outputs from the Rytm and only grab the following channels as you can see in the screenshot:

Analog Rytm
Audio 2
Audio 3
Audio 4

Is there a way to control the volume and sends on these "chains" as well?
I'm almost sure it's just a Bitwig setting I overlooked and has nothing to do with the script?

[SOLA]

I am using your extension "DrivenByMoss-16.3.1-Bitwig" and the Native Instruments Komplete Kontrol S61 mk I with an expression pedal on it but it doesn´t send Midi-CC11 as usual to my Bitwig 4.2.3. Bitwig just starts or stops playing when I press the pedal.

[moss]

Hello Jürgen, a huge thank you for the sensational scripts!

Since Bitwig is still new territory for me, I probably have a newbie question.

The Elektron plugin offers separate tracks to all outputs of my Rytm. Bitwig offers a super simple solution and automatically creates all separate output channels in form of chains? The Launch Control faders skip these separate outputs from the Rytm and only grab the following channels as you can see in the screenshot:

Analog Rytm
Audio 2
Audio 3
Audio 4

Is there a way to control the volume and sends on these "chains" as well?
I'm almost sure it's just a Bitwig setting I overlooked and has nothing to do with the script?

Only if you have a Push controller. These channels are are actually layers as part of a device. Since this is quite hard to navigate (it is recursive as well), in my opinion it requires a larger display.

[octobird]

Hey Jürgen,

I'm using your MCU Protocol for my Icon Platform X+ (with the display). As you may know this is simply an extender unit and I use it without the Main unit, first because it's by my knowledge the most compact solution for a set of motorfaders on the market (and space is limited here) and second because I already have an Push2 in my setup which serves well for all the Transport functions (thanks to your fantastic Protocol

So my issue since the last 2(?) versions is related to the display which I need to show me track names. This allways worked fine but since the last versions, whenever I select the master channel it's switching to the project options (activate audio engine etc.) and then when I go back it shows the selected track name, pan and sends and not all 8 track names anymore. These only become visible by touching on of the faders. I tried to find the right mcu midi command to change the display mode and map it to one of the buttons but I just couldn't find it.

Could you put it back into the setting where showing the track names is the default behavior? or provide the midi command to map the display mode manually? That would be total magic!

Also...I found some bugs with the Push2 which I think come from some weird cross interaction between the mackie control and Push2. With both units set up the track select buttons on the push are sending wrong navigation commands.So instead of navigating from Mix mode to channel device mode it would bring me back to the 1st level of track hyrachy (all groups closed). I had both units set to hyrarchical navigation mode. To surpress this behavior I had to set the Platform X+ to extender mode then it works fine. Which is fine as it really is an extender. Just not sure if it's an actual bug you wanna look into.

Thanks again for all your hard work for us Bitwig users.

Cheers,
Eric

[fsciarra62]

Hi Jürgen, hi all...
I apologize because probably this has been already asked but I can't find a direct answer: I'm wondering why in my setup, Program Change is not forwarded to any device in the chain, independly by selected controller... I only have some results selecting midi monitor as controller. What am I doing wrong?
I'm using a Novation 61slmk3 mostly, Bitwig 4.2.4, DrivenByMoss 16.3.1
Thanks in advance.

Fabrizio

[moss]

I am using your extension "DrivenByMoss-16.3.1-Bitwig" and the Native Instruments Komplete Kontrol S61 mk I with an expression pedal on it but it doesn´t send Midi-CC11 as usual to my Bitwig 4.2.3. Bitwig just starts or stops playing when I press the pedal.

Good catch! Will be fixed in the next update!

[moss]

So my issue since the last 2(?) versions is related to the display which I need to show me track names. This allways worked fine but since the last versions, whenever I select the master channel it's switching to the project options (activate audio engine etc.) and then when I go back it shows the selected track name, pan and sends and not all 8 track names anymore. These only become visible by touching on of the faders. I tried to find the right mcu midi command to change the display mode and map it to one of the buttons but I just couldn't find it.

Yes, will be fixed in the next update!

Could you put it back into the setting where showing the track names is the default behavior? or provide the midi command to map the display mode manually? That would be total magic!

It is still there: Hardware Setup -> Display track names in 1st display
Might be worth to remove the device and add it again since Bitwig still mixes up settings when they did changed.

Also...I found some bugs with the Push2 which I think come from some weird cross interaction between the mackie control and Push2. With both units set up the track select buttons on the push are sending wrong navigation commands.So instead of navigating from Mix mode to channel device mode it would bring me back to the 1st level of track hyrachy (all groups closed). I had both units set to hyrarchical navigation mode. To surpress this behavior I had to set the Platform X+ to extender mode then it works fine. Which is fine as it really is an extender. Just not sure if it's an actual bug you wanna look into.

The extender modes changes the MIDI commands which is in no way related to the hierarchy.