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

[noiseresearch]

Is this the right place to report a bug for support? Or is there an email or something? Thanks

Here is the perfect place (or on GitHub if you want to be more formal).

First, thank you for your work. Not a bug but a feature request for Push (3). I do a lot of dark ambient music and sometimes I want no distraction while mastering music and more darkness could you add a "black" layout to Push. Like using a modifier turns off the display and pads only leaving the transport and master button lid? For me that would be a cherry on top of this great script of yours.

[moss]

Is this the right place to report a bug for support? Or is there an email or something? Thanks

Here is the perfect place (or on GitHub if you want to be more formal).

First, thank you for your work. Not a bug but a feature request for Push (3). I do a lot of dark ambient music and sometimes I want no distraction while mastering music and more darkness could you add a "black" layout to Push. Like using a modifier turns off the display and pads only leaving the transport and master button lid? For me that would be a cherry on top of this great script of yours.

Interesting idea. Noted.

[olimpo]

many thanks as always!

[JasonGibbins]

Is this the right place to report a bug for support? Or is there an email or something? Thanks

Here is the perfect place (or on GitHub if you want to be more formal).

Please could you take a look at the issue I am having? There are more details in my last few posts, but the basics are:
When sliding to the left of a pad, the pitch bends up, rather than down.
I think I have everything set up as you suggested in the YouTube video.
This behaviour was introduced in version 26.

Thank you

[moss]

Is this the right place to report a bug for support? Or is there an email or something? Thanks

Here is the perfect place (or on GitHub if you want to be more formal).

Please could you take a look at the issue I am having? There are more details in my last few posts, but the basics are:
When sliding to the left of a pad, the pitch bends up, rather than down.
I think I have everything set up as you suggested in the YouTube video.
This behaviour was introduced in version 26.

Thank you

I answered this already several times, sorry, but it is what it is for the time being until Ableton documents how this actually works.

[JasonGibbins]

Is this the right place to report a bug for support? Or is there an email or something? Thanks

Here is the perfect place (or on GitHub if you want to be more formal).

Please could you take a look at the issue I am having? There are more details in my last few posts, but the basics are:
When sliding to the left of a pad, the pitch bends up, rather than down.
I think I have everything set up as you suggested in the YouTube video.
This behaviour was introduced in version 26.

Thank you

I answered this already several times, sorry, but it is what it is for the time being until Ableton documents how this actually works.

I didn't realise you answered it, sorry. It seems in your video that it was not happening on your machine, is that right? Does yours pitch bend up when sliding to the left? Maybe there is some setting or something?
I doubt Ableton will want to share this information

[kaveer]

Hi Moss,

First, thank you for your work.
I’m using Push 2 on macOS with the latest Bitwig 5 and the latest script version, with no other MIDI devices connected. We’ve noticed this behavior on several different Push 2 units in Bitwig, and it has appeared in previous Bitwig versions as well.

In Bank/Device mode, pressing the lower page buttons can sometimes cause Device view to jump to Channel view. If you re-enter Bank mode and press the lower buttons again, it can happen repeatedly. On a fresh restart, using Hierarchical track view seems more reliable, but eventually the Device view still jumps up a layer.

Using the navigation buttons on the right doesn’t trigger this issue. When all 8 lower page buttons are assigned, the navigation buttons jump to the first or last page, which seems intentional to step through pages in blocks of 8. I’ve observed this on both simple 2-page devices and more complex devices.

One thought (unconfirmed): the UP button in the same row as Bank might occasionally be triggered or misinterpreted, which could explain the layer jump.

Observation/idea: since Tracks and Scenes navigation in Bitwig can be configured to step by 1 or by page, it might be interesting to explore whether Device page navigation could work similarly — stepping by 1 could potentially reduce the chance of accidental layer jumps.

Just sharing this as feedback that might be useful for stability and usability.

[deailes]

Hey Jurgen

I have a polite feature request if possible to accommodate in some shape or form ?

Using a Kontrol mk3

I love using bitwigs groups and the enter group / exit group functionality. I have this set to two shortcuts on my typing keyboard and this works to dive into the group and the tracks are then reflected on the mixer on the Kontrol screen. (makes it easier to focus on a specific group).

Would there be any way to incorporate an Enter / Exit group functionality on the Kontrol keyboard itself?

Potentially:
SHIFT + RIGHT ENCODER to enter group
SHIFT + LEFT ENCODER to exit group

Many thanks

[olimpo]

24.3.0
[/quote]

many thanks

[nowiamone]

Dear Mr. Moßgraber,
is sending /time/signature broken for Bitwig 6 with the OSC script?
i try (/time/signature) STRING(3 / 4)
and (/time/signature) STRING(3 / 4)
and nothing seems to work to set Bitwigs time signature.

Recieving it works though , via the same adress and same formatting...
RECEIVE | ENDPOINT([::ffff:127.0.0.1]:63226) ADDRESS(/time/signature) STRING(3 / 4)
works fine.

But sending to Bitwig doesn't? Any help/info is appreciated

[hesaptest]

Hi, I'm new to the this website and I couldn't find a search button on this thread so I wanted to ask about my touchosc problem myself. So I have touchosc app installed on my tablet. On protokol, i can see both midi and osc connections are working. In bitwig however, only midi connection works. I came to that conclusion because i can't control my DAW from my tablet if i disable midi connection type; disabling or enabling osc however, does nothing. So I set up drivenbymoss extension for bitwig, but still does not work (only thing i did was copy paste a file into "Program Files\Bitwig Studio\resources\Extensions", so idk if it was actually enough but i see the "by drivenbymossgraber" text down below after selecting osc product in bitwig dashboard). I should also note, I use my tablets ip on "host to send to" on bitwig, and also the touchosc app can see my pc as a host. Send and receive ports are also compatible. The reason i need osc connection type to work is because i made a custom template on touchosc and i couldn't make it work since midi control numbers are more than 128, changing channels after 128 didnt work for some reason so i guess i need the osc connection type.

[hesaptest]

Hi, I'm new to the this website and I couldn't find a search button on this thread so I wanted to ask about my touchosc problem myself. So I have touchosc app installed on my tablet. On protokol, i can see both midi and osc connections are working. In bitwig however, only midi connection works. I came to that conclusion because i can't control my DAW from my tablet if i disable midi connection type; disabling or enabling osc however, does nothing. So I set up drivenbymoss extension for bitwig, but still does not work (only thing i did was copy paste a file into "Program Files\Bitwig Studio\resources\Extensions", so idk if it was actually enough but i see the "by drivenbymossgraber" text down below after selecting osc product in bitwig dashboard). I should also note, I use my tablets ip on "host to send to" on bitwig, and also the touchosc app can see my pc as a host. Send and receive ports are also compatible. The reason i need osc connection type to work is because i made a custom template on touchosc and i couldn't make it work since midi control numbers are more than 128, changing channels after 128 didnt work for some reason so i guess i need the osc connection type.

For reaper, someone on reddit told me to do this on touchosc "Scroll down in the button settings, remove MIDI message, In the OSC message remove preexisting address entries, Click + in the osc address and add a constant, In the constant write "/action/1007" (this starts playback)" and it really worked, i didnt even need to map it in bitwig afterwards. But i guess there are no command IDs in bitwig unlike reaper. So i feel totally lost. Is there something i should be writing in the address section, if so, what?

[Simon56]

UPDATE 7/04/26 - solved questions 1 and 3 today by examining more carefully the options offered in the setup screen. What a great piece of software you have built.


Hi there Jurgen,
First many many thanks for your work on the extension for Bitwig.

I'm on Windows 11 using the Icon V1-M + 2 V1-X extenders in Bitwig 6.3. Using the latest drivenbyMoss 26.6 with MCU+2 extenders controller configuration supported by your extender of course.

1) Is there a way to get the stereo out twin meters on the V1-M to output a meter signal correctly with your extension - so far I have not managed to but this is because I normally use Nuendo and am just having a go with Bitwig Studio 6.3. (sorry if you have answered this one many times before - it is ages since I last used KVR forum). I'm aware that under the original Mackie spec the additional 9th fader and meter on the V1-M would be unsupported. With Cubase/Nuendo bjoluc's midi remote script solves this problem - as does the Icon controller configuration with Bitwig.
So far I followed the extender setup advice in your manual pdf and declared the units as main v1-m, extender x2, extender x3. I've tried also setting main to the left - as my setup is v1-m, x2, x3 from left to right.

2) Is there a new drivenbymoss extension version for Bitwig 6.0/6.3 in the pipeline?

3) Is there a way to flip the track names on the second display above the faders on the V1-M to the main dispay under the VU meters. Cubase/Nuendo with bjoluc's excellent script seems to do this OK but have not found a way to do it in Bitwig yet.

Have noted and applied the following from the pdf help
'Display track names in 1st display: If enabled to 1st row of the 1st display the track names instead of the mode labels.'
....have not seen so far that this has made any difference in the main display.

Many many thanks Jurgen and very best wishes.
Simon (Milton Keynes, UK)

[olimpo]

Hello Jurgen I hope you can read this.
I told you in the comments of a Youtube video of yours, that I had the intention to redact a parragraph with their corresponding graphs, hopefully to be located in DrivenByMoss User Guide, regarding the use of the Launchpad Pro Mk3 in Bitwig with your scripts.
My current Bitwig version is v5.0.11 so, which script might be best suitable in my case in order to have it correctly working?
DrivenByMoss-24.3.0-Bitwig.zip ?
or
DrivenByMoss-19.2.2-Bitwig.zip ?

My idea is to upgrade to v6.0 but after a while. Thanks.

24.3.0

Hello I've tried both versions, DrivenByMoss-19.2.2 and DrivenByMoss-24.3.0.
Issue:
1.- "Sequencer" and "Chord" Buttons: When selected the layouts appear, pads does not trigger sounds, the notes are recorded in the grid, the "Play" button engages playback but notes does not sound. (They sound when Bitwig script is used)

[Icedragonscale]

Hi Jürgen and community,

​I am struggling to get MPE pitch gliding (X-axis) to work on my Ableton Push 3. I've done everything I could think of to troubleshoot the issue, but I cannot get polyphonic pitch bend to work.

​System:

- ​OS: Linux (Tested on Windows as well, exact same issue)
- ​DAW Version: Bitwig Studio 6.0.3 Beta (Extension API version: 25)
- ​DrivenByMoss Version: 26.6.0
- ​Push 3: Controller only, non-standalone
- ​Push Firmware: 1.5.0 (Updated via Live 12 Lite). In Bitwig, it shows up as Firmware 1.0 Build 87, Board revision 2.

​Issue:

MPE is partially working. MPE Pressure and Timbre/Y-axis work perfectly and show up as multi-polyphonic MPE expressions in the piano roll. But, sliding on the pads on the X-axis only shows a singular Channel 1 Pitch Bend message, rather than per-note MPE pitch expressions. That's why it also only works monophonically and affects all active voices simultaneously and frantically jumps between pitches, when multiple pads glide at the same time.

​Troubleshooting Steps Taken:

- ​Triple checked MPE settings: MPE is activated on the Push 3 itself (Setup > MPE), in the Bitwig controller settings, in the device/plugin inspector and in the plugin settings.
- ​Pitch bend range: Pitch bend range and sensitivity are set to 48 semitones everywhere (hardware, script settings and synth).
- ​Synths tested: Tested with both native Bitwig devices (Polymer) and 3rd-party VST3 synths with MPE support (Vital).
- ​Other MPE controller: I have a second, different MPE controller connected to the same setup, and its MPE pitch glide works exactly as expected.
- ​Different ports: I have tested the Live Port, User Port, and External Port.
- ​Linux permissions: The required udev rules are installed, and my user is in the audio group (everything else from the script works).
- ​Tested with generic script: I disabled the Push 3 script and added a Generic script instead, but same behavior.
- ​Pitch bend inspector settings: If I set the Pitch Bend range in the Track Inspector Panel to -24 / +24, it seemingly "fixes" the glide length, but it only works monophonically. It also forces the physical ribbon strip to 48 st. This confirms it is just emulating global pitch bend on the pads, not true MPE.
- Tested on Windows: Tested the same on Windows, with the same result.

​Pressure and timbre work as polyphonic MPE, but the X-axis glide is only working like a pitch wheel. This is across both Windows and Linux and I have the same issue with the generic scripts.

Is there anything I am missing or is this a known API limitation causing this?

​Any help would be appreciated :)