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

[mlb2095]

Hi @moss .This relates to OSC.

Now that Bitwig 5 distinguishes between clip launch and clip release, would it be possible to have your script send an OSC message like /track/{1-8}/clip/{1-8}/isReleaseQueued

The trigger would be receiving a /track/{1-8}/clip/{1-8}/launch message with a value of 0

Thanks

[moss]

Hi @moss .This relates to OSC.

Now that Bitwig 5 distinguishes between clip launch and clip release, would it be possible to have your script send an OSC message like /track/{1-8}/clip/{1-8}/isReleaseQueued

The trigger would be receiving a /track/{1-8}/clip/{1-8}/launch message with a value of 0

Thanks

I added already the following new messages (see the manual for details):

/track/stopAlt
/scene/{1-8}/launchAlt
/track/{1-8}/clip/{1-8}/launchAlt
/clip/launchAlt
/clip/stopallAlt

The state notifications were not updated in API 18.

[moss]

Hi, thank you for awesome scripts!

I'm using Bitwing 5.0.4 and having a problem that rectangle around focused scripts isn't showing up. I have used DrivenByMoss before and there was always a red rectangle around selected tracks or clips. In my controller options i've turned on "Paints a rectangle around focused clips..."

Which device are you using?

Arturia Beatstep. All other features seem to be working

The rectangle is only displayed when session mode is active (Shift + 6).

EDIT: I will change this to be always active in the next update!

[mlb2095]

Hi @moss .This relates to OSC.

Now that Bitwig 5 distinguishes between clip launch and clip release, would it be possible to have your script send an OSC message like /track/{1-8}/clip/{1-8}/isReleaseQueued

The trigger would be receiving a /track/{1-8}/clip/{1-8}/launch message with a value of 0

Thanks

I added already the following new messages (see the manual for details):

/track/stopAlt
/scene/{1-8}/launchAlt
/track/{1-8}/clip/{1-8}/launchAlt
/clip/launchAlt
/clip/stopallAlt

The state notifications were not updated in API 18.

Hi yes I saw those additions many thanks for them! Do you know if Bitwig have any plans to update notifications in the API to cover the new launch / stop states?

[moss]

Hi @moss .This relates to OSC.

Now that Bitwig 5 distinguishes between clip launch and clip release, would it be possible to have your script send an OSC message like /track/{1-8}/clip/{1-8}/isReleaseQueued

The trigger would be receiving a /track/{1-8}/clip/{1-8}/launch message with a value of 0

Thanks

I added already the following new messages (see the manual for details):

/track/stopAlt
/scene/{1-8}/launchAlt
/track/{1-8}/clip/{1-8}/launchAlt
/clip/launchAlt
/clip/stopallAlt

The state notifications were not updated in API 18.

Hi yes I saw those additions many thanks for them! Do you know if Bitwig have any plans to update notifications in the API to cover the new launch / stop states?

No idea, you need to ask support.

[SVRVDX]

Hi Moss! Recorded video this is an attempt to make the parameters the same as in Bitwig it all works on LUA just parses the parameter names through osc. There are complications that I foresee further, namely, when renaming a parameter or user preset to a remote control with other names, it will not work and will display a normal handle. So I wanted to ask if there is access to these types of parameters in the API and is it possible to expect this in your OSC?

[moss]

Hi Moss! Recorded video this is an attempt to make the parameters the same as in Bitwig it all works on LUA just parses the parameter names through osc. There are complications that I foresee further, namely, when renaming a parameter or user preset to a remote control with other names, it will not work and will display a normal handle. So I wanted to ask if there is access to these types of parameters in the API and is it possible to expect this in your OSC?

No, that info is not available.

[resonaural]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hey Moss. Thanks for all the hard work you've put into this extension - can't imagine how long it has taken to get right.

I've upgraded to Bitwig 5.0.4 and I'm using an Allen & Heath Xone K2 (Generic Flexi) along with a Novation Launchpad X and Maschine MK3.
Maschine is controlling the VST in the project and the launchpad is being used as a clip launcher.

I have mapped different functions of the DAW to the K2 - using the Bitwig 'right-click menu > Map to controller or Key' and then pressing the button / moving the cc on the K2. Everything works fine, but I just can't seem to manage to get the buttons to light up.

I have RTFM, but I honestly don't know what I'm doing wrong. I haven't assigned any functions in the generic flexi settings as I want those to be mapped to specific devices / controls in my project.

If you could direct me in the right direction, that would be awesome.

Thanks in advance.

Cheers!

 

This does only work if your controller expects the exact same value for the LED as the one sent, which I guess not the case with yours.

 

I've gone through the Xone K2 manual (https://www.allen-heath.com/media/Xone+K2_UG_AP8509_2.pdf) for the MIDI implementation, and the value sent back to the buttons is the same (they are note values). Really not sure why the LEDs still do not light up.

[moss]

Hey Moss. Thanks for all the hard work you've put into this extension - can't imagine how long it has taken to get right.

I've upgraded to Bitwig 5.0.4 and I'm using an Allen & Heath Xone K2 (Generic Flexi) along with a Novation Launchpad X and Maschine MK3.
Maschine is controlling the VST in the project and the launchpad is being used as a clip launcher.

I have mapped different functions of the DAW to the K2 - using the Bitwig 'right-click menu > Map to controller or Key' and then pressing the button / moving the cc on the K2. Everything works fine, but I just can't seem to manage to get the buttons to light up.

I have RTFM, but I honestly don't know what I'm doing wrong. I haven't assigned any functions in the generic flexi settings as I want those to be mapped to specific devices / controls in my project.

If you could direct me in the right direction, that would be awesome.

Thanks in advance.

Cheers!

 

This does only work if your controller expects the exact same value for the LED as the one sent, which I guess not the case with yours.

 

I've gone through the Xone K2 manual for the MIDI implementation, and the value sent back to the buttons is the same (they are note values). Really not sure why the LEDs still do not light up.

I suggest to confirm this with a MIDI tool of your choice (e.g. MIDI-OX on Windows) by sending these messages to the device and see if the buttons light up. I had a quick look at the manual and it says the pads are multi color and I understood that the buttons send 127 on press and 0 on release which indicates that the values are not the same.

[resonaural]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hey Moss. Thanks for all the hard work you've put into this extension - can't imagine how long it has taken to get right.

I've upgraded to Bitwig 5.0.4 and I'm using an Allen & Heath Xone K2 (Generic Flexi) along with a Novation Launchpad X and Maschine MK3.
Maschine is controlling the VST in the project and the launchpad is being used as a clip launcher.

I have mapped different functions of the DAW to the K2 - using the Bitwig 'right-click menu > Map to controller or Key' and then pressing the button / moving the cc on the K2. Everything works fine, but I just can't seem to manage to get the buttons to light up.

I have RTFM, but I honestly don't know what I'm doing wrong. I haven't assigned any functions in the generic flexi settings as I want those to be mapped to specific devices / controls in my project.

If you could direct me in the right direction, that would be awesome.

Thanks in advance.

Cheers!

 

This does only work if your controller expects the exact same value for the LED as the one sent, which I guess not the case with yours.

 

I've gone through the Xone K2 manual (https://www.allen-heath.com/media/Xone+K2_UG_AP8509_2.pdf) for the MIDI implementation, and the value sent back to the buttons is the same (they are note values). Really not sure why the LEDs still do not light up.

I suggest to confirm this with a MIDI tool of your choice (e.g. MIDI-OX on Windows) by sending these messages to the device and see if the buttons light up. I had a quick look at the manual and it says the pads are multi color and I understood that the buttons send 127 on press and 0 on release which indicates that the values are not the same.

Will do thanks!!

[moss]

DrivenByMoss 21.0.0 is online!

Big feature is Ableton Push 3 support! But there are also many other goodies!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Fixed an exception with controllers not having user parameters.
  • Fixed: Improved feedback of automation modes.
• Generic Flexi
  • Fixed: Switching project/track remote pages was triggered twice.
• HUI
  • New: RecRdyAll toggles rec arm state on all tracks.
  • New: Option+Jog Wheel - Change tempo (press Shift for fine adjustment).
  • New: Control+Jog Wheel - Change loop start (press Shift for fine adjustment).
  • New: Alt+Jog Wheel - Change loop length (press Shift for fine adjustment).
  • Fixed: Clip related function did not work when assigned to F1-F8 buttons.
• MCU
  • New: Shift+RecArm toggles rec arm state on all tracks.
• OSC
  • Fixed: /track/param did trigger project parameters.
• Push
  • New: Added support for Ableton Push 3.
  • New: Push 2: Removed unecessary Rec Arm, Solo and Mute from Cue channel.
  • New: Metronome volume has been moved into the metronome settings mode (long press metronome button).
  • New: Improved session configuration mode. Easier selection of what to show on the display.
  • New: 'Add Track' mode has now 7 favorites for each track type as well as 7 device favorites.
  • Fixed: Push 1: Master volume graphical representation was not missing line if VU mode was active.
  • Fixed: Do not notify tempo value when tempo knob is used in browser mode to scroll results.

Enjoy!

[questionaire]

Hello Moss,

With using Launchpad Pro mk3 and Launchkey mk3 simultaneously and launching a scene makes the clips belonging to that scene light up green slowly flashing on the launchkey. The clips on the Launchpad Pro mk3 will flash but keep their original clip colour. This is when i use the Drivenbymoss scripts for both devices.

When i use the Launchpad Pro mk3 Bitwig script instead of the drivenbymoss script the clips work as expected on the both devices and they turn out green flashing when launched, can this somehow be corrected in the drivenbymoss script?

It is not a deal breaker i will use the bitwig script meanwhile for the Launchpad Pro mk3. But it would be cool to use the both devices with the drivenbymoss script.

I feel somehow being an ass by pointing bugs to you, it is in no way intended for complaining about this awesome piece of work!

Danke schön,

Questionaire.

[tishta]

Hello and thankyou for making all these amazing scripts available.

I use the Maschine MK3 script in Bitwig.

In device parameter control I can navigate device pages with the large encoder up/down move. However, it seems to me that they work in the opposite order to how I would expect.

Down moves up the list
Up moves down the list

ie: To get to the first page I have to press the encoder to the down position. To get to the last page I press the encoder to the up position.

Is this intentional? Is there a way to flip it?

Thanks!

[guitarfrenzi]

Maybe pile on to Ticket 174664 with your experience.


 

If someone can give some reproducible steps, this would be very helpful!


 

Apparently my first report got lost, just reported again and received this:

Re: Navigating Remote Pages is broken on Push 1 and 2
Hi Chris​,
​
thanks for the info! If this is something Moss can narrow down in his code, he is in direct contact with our dev team and can report what he thinks is the issue with the API there.

Best regards,
Bitwig Technical Support Team

[pc999]

DrivenByMoss 21.0.0 is online!

Big feature is Ableton Push 3 support! But there are also many other goodies!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Fixed an exception with controllers not having user parameters.
  • Fixed: Improved feedback of automation modes.
• Generic Flexi
  • Fixed: Switching project/track remote pages was triggered twice.
• HUI
  • New: RecRdyAll toggles rec arm state on all tracks.
  • New: Option+Jog Wheel - Change tempo (press Shift for fine adjustment).
  • New: Control+Jog Wheel - Change loop start (press Shift for fine adjustment).
  • New: Alt+Jog Wheel - Change loop length (press Shift for fine adjustment).
  • Fixed: Clip related function did not work when assigned to F1-F8 buttons.
• MCU
  • New: Shift+RecArm toggles rec arm state on all tracks.
• OSC
  • Fixed: /track/param did trigger project parameters.
• Push
  • New: Added support for Ableton Push 3.
  • New: Push 2: Removed unecessary Rec Arm, Solo and Mute from Cue channel.
  • New: Metronome volume has been moved into the metronome settings mode (long press metronome button).
  • New: Improved session configuration mode. Easier selection of what to show on the display.
  • New: 'Add Track' mode has now 7 favorites for each track type as well as 7 device favorites.
  • Fixed: Push 1: Master volume graphical representation was not missing line if VU mode was active.
  • Fixed: Do not notify tempo value when tempo knob is used in browser mode to scroll results.

Enjoy!

Nice
I am actually quite tempeted by Push3, but the price...