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

[nowiamone]

Happy new year

and some questions

Concerning Komplete Kontrol (S49mk2) in Bitwig 5.1 with the latest drivenbymoss script vs. Bitwigs internal script:

1 When using Bitwigs Komplete Kontrol Controller Script, all 8 Remote Controls of any Device are automatically assigned to the 8 Knobs of the Keyboard, when running in Midi-mode. Any possibility your KompleteKontrol Script does this, too? Maybe i missed something.
2 Since you’re the master of ‘hacking’ devices: Would it be possible to show Bitwigs Remote Control Parameters and their values on the Komplete Kontrol Keyboard Display?
3 Old report, just to be safe: Komplete Kontrol S49MK2 4-directional-knob navigation is broken for switching from clip to clip within a track - because the cursor jumps to the scene, instead of the clip. (You’ve already answered this one, saying that Bitwigs API is broken in some way, to cause this. Hope they'll fix this)

Concerning your OSC script which got even better thanks to the last update, (especially the recording quantization was an important puzzle piece for the "perfect allround controller" of Bitwig)
4 in the touch-controller community, we often times create clip-launchers which don't have a square controller-frame, but for example 10 Scenes, 20 Tracks. It would be nice to be able to have separate bank sizes for Scenes and Tracks - if possible

5 When trying to build a properly functioning browser via the existing /osc adresses, some adresses don't work as expected, or are missing. When using /browser/filter/4/{+,-} to scroll through Tags, for example, those tags will immediately be committed and therefore not let the user scroll through the whole list of tags anymore. The user will be stuck, until resetting the filter, and in addition /browser/filter/x/reset doesn’t work, and there's no /focus filter xy column, and /clear focused filter, available. (Just like no /select quicksource xy).
And /browser/filter/{1-6}/item/{1-16}/isSelected, and /browser/result/{1-16}/isSelected seems unusable for actively selecting the result. Direct selection would be reaaally awesome though.
Thanks to your awesome /action list, i was able to build some workarounds - but now i reached the /action 20 (limit of the /actions) because of those workarounds, haha. But nevermind, those are "first world problems".
I think this whole browser topic is difficult due to Bitwigs browser-re-make, since version 5.0? I can guess the API might be a bit weird in the browser-realm, since then, haha

6 Can i still hope for a /EQ which loads and controls the EQ5 instead of the EQ+, or should i forget about that? Despite EQ+ being changed with 5.1, people like me still very much prefer EQ5 for different reasons and live performance

Thanks for your awesome work

[tommy1979]

DrivenByMoss 22.1.0 is out!

Get it from https://mossgrabers.de

• APC40
  • Fixed: In drum sequencer the first 4 pads of the 2nd step row played sounds.
• Arturia Beatstep
  • Fixed: Knobs were totally broken. Additionally, prevented some weird parameter jumps.
• Electra One
  • New: Added knob sensitivity (speed) settings.
  • New: Made knob touch combinations configurable with plenty of options.
  
  
  Enjoy!

Thank you so much, i can confirm the APC40 bug has been resolved.

[moss]

1 When using Bitwigs Komplete Kontrol Controller Script, all 8 Remote Controls of any Device are automatically assigned to the 8 Knobs of the Keyboard, when running in Midi-mode. Any possibility your KompleteKontrol Script does this, too? Maybe i missed something.
2 Since you’re the master of ‘hacking’ devices: Would it be possible to show Bitwigs Remote Control Parameters and their values on the Komplete Kontrol Keyboard Display?

It works like intended by NI, which means no parameters at all.
But you can access 2 additional modes with the CLEAR button. See the DrivenByMoss manual.

5 When trying to build a properly functioning browser via the existing /osc adresses, some adresses don't work as expected, or are missing. When using /browser/filter/4/{+,-} to scroll through Tags, for example, those tags will immediately be committed and therefore not let the user scroll through the whole list of tags anymore. The user will be stuck, until resetting the filter, and in addition /browser/filter/x/reset doesn’t work, and there's no /focus filter xy column, and /clear focused filter, available. (Just like no /select quicksource xy).
And /browser/filter/{1-6}/item/{1-16}/isSelected, and /browser/result/{1-16}/isSelected seems unusable for actively selecting the result. Direct selection would be reaaally awesome though.
Thanks to your awesome /action list, i was able to build some workarounds - but now i reached the /action 20 (limit of the /actions) because of those workarounds, haha. But nevermind, those are "first world problems".
I think this whole browser topic is difficult due to Bitwigs browser-re-make, since version 5.0? I can guess the API might be a bit weird in the browser-realm, since then, haha

Browser is currently quite broken since the changes of Bitwig 5 are still not reflected in the API.

6 Can i still hope for a /EQ which loads and controls the EQ5 instead of the EQ+, or should i forget about that? Despite EQ+ being changed with 5.1, people like me still very much prefer EQ5 for different reasons and live performance

It is on my TODO list but know idea when and if.

[nowiamone]

1 When using Bitwigs Komplete Kontrol Controller Script, all 8 Remote Controls of any Device are automatically assigned to the 8 Knobs of the Keyboard, when running in Midi-mode. Any possibility your KompleteKontrol Script does this, too? Maybe i missed something.
2 Since you’re the master of ‘hacking’ devices: Would it be possible to show Bitwigs Remote Control Parameters and their values on the Komplete Kontrol Keyboard Display?

It works like intended by NI, which means no parameters at all.
But you can access 2 additional modes with the CLEAR button. See the DrivenByMoss manual.

5 When trying to build a properly functioning browser via the existing /osc adresses, some adresses don't work as expected, or are missing. When using /browser/filter/4/{+,-} to scroll through Tags, for example, those tags will immediately be committed and therefore not let the user scroll through the whole list of tags anymore. The user will be stuck, until resetting the filter, and in addition /browser/filter/x/reset doesn’t work, and there's no /focus filter xy column, and /clear focused filter, available. (Just like no /select quicksource xy).
And /browser/filter/{1-6}/item/{1-16}/isSelected, and /browser/result/{1-16}/isSelected seems unusable for actively selecting the result. Direct selection would be reaaally awesome though.
Thanks to your awesome /action list, i was able to build some workarounds - but now i reached the /action 20 (limit of the /actions) because of those workarounds, haha. But nevermind, those are "first world problems".
I think this whole browser topic is difficult due to Bitwigs browser-re-make, since version 5.0? I can guess the API might be a bit weird in the browser-realm, since then, haha

Browser is currently quite broken since the changes of Bitwig 5 are still not reflected in the API.

6 Can i still hope for a /EQ which loads and controls the EQ5 instead of the EQ+, or should i forget about that? Despite EQ+ being changed with 5.1, people like me still very much prefer EQ5 for different reasons and live performance

It is on my TODO list but know idea when and if.

Thanks alot for the answers! So there’s a little hope for the /Eq , woohey

Did you maybe accidentally over-read one question i had, i was wondering if this is in any way possible/makes sense?:
4 "in the touch-controller community, we often times create clip-launchers which don't have a square controller-frame, but for example 10 Scenes, 20 Tracks. It would be nice to be able to have separate bank sizes for Scenes and Tracks - if possible "

[moss]

1 When using Bitwigs Komplete Kontrol Controller Script, all 8 Remote Controls of any Device are automatically assigned to the 8 Knobs of the Keyboard, when running in Midi-mode. Any possibility your KompleteKontrol Script does this, too? Maybe i missed something.
2 Since you’re the master of ‘hacking’ devices: Would it be possible to show Bitwigs Remote Control Parameters and their values on the Komplete Kontrol Keyboard Display?

It works like intended by NI, which means no parameters at all.
But you can access 2 additional modes with the CLEAR button. See the DrivenByMoss manual.

5 When trying to build a properly functioning browser via the existing /osc adresses, some adresses don't work as expected, or are missing. When using /browser/filter/4/{+,-} to scroll through Tags, for example, those tags will immediately be committed and therefore not let the user scroll through the whole list of tags anymore. The user will be stuck, until resetting the filter, and in addition /browser/filter/x/reset doesn’t work, and there's no /focus filter xy column, and /clear focused filter, available. (Just like no /select quicksource xy).
And /browser/filter/{1-6}/item/{1-16}/isSelected, and /browser/result/{1-16}/isSelected seems unusable for actively selecting the result. Direct selection would be reaaally awesome though.
Thanks to your awesome /action list, i was able to build some workarounds - but now i reached the /action 20 (limit of the /actions) because of those workarounds, haha. But nevermind, those are "first world problems".
I think this whole browser topic is difficult due to Bitwigs browser-re-make, since version 5.0? I can guess the API might be a bit weird in the browser-realm, since then, haha

Browser is currently quite broken since the changes of Bitwig 5 are still not reflected in the API.

6 Can i still hope for a /EQ which loads and controls the EQ5 instead of the EQ+, or should i forget about that? Despite EQ+ being changed with 5.1, people like me still very much prefer EQ5 for different reasons and live performance

It is on my TODO list but know idea when and if.

Thanks alot for the answers! So there’s a little hope for the /Eq , woohey

Did you maybe accidentally over-read one question i had, i was wondering if this is in any way possible/makes sense?:
4 "in the touch-controller community, we often times create clip-launchers which don't have a square controller-frame, but for example 10 Scenes, 20 Tracks. It would be nice to be able to have separate bank sizes for Scenes and Tracks - if possible "

Didn't overlook it and have no plans.

[nowiamone]

Didn't overlook it and have no plans.

Thanks for clarifying!


Dear Jürgen,
I have a new unexpected behavior report (not that important, but i should mention it, in case it's a bug), because i'm trying out the track remotes via the OSC script, and today is the first time i wanted to access a second Track-remote-page.

I don't know how to make buttons for "next Track-Remote-Page", and "Previous Track-Remote-Page"
I expected /track/param/{+,-} might do it, but instead of stepping through each Track-Page, it leaves out the second Track-Page and jumps straight to the Modulator Page (see following picture example). Is that normal?

trackparam6.png

Same behavior seems to apply to project/param/-, so stepping through Project Remote Control Pages seems also not possible step by step.

Another unexpected behavior: when Bitwigs focus is inside of a Track-Device-Chain (on any device), the /track/page/selected actually chooses the project remote pages!

EDIT: Please consider this very low priority report, as the /track/page/selected is working, so i can build a workaround somehow

Best greetings

[codec17]

DrivenByMoss 22.1.0 is out!
[*]Arturia Beatstep

• Fixed: Knobs were totally broken. Additionally, prevented some weird parameter jumps.

Yes! thnx! Still my little friend in my workflow.

[drsyncenstein]

Question;
I wanted to make a xy controller from a 1gen ipad mini with touchosc mk1.
I found the DrivenByMossOSC.touchosc extension (deprecated i know) which is broke in some ways, but fixable for a noob like me.

What i can not get working is parameter feedback.
The ipad is connected with rtpmidi to the Moss osc extension. Tried it also with touchosc bridge.

However, when i use open stage control with the Moss template from another win laptop i receive parameter names and parameter values nicely. So i know rtpmidi and osc extension work correctly.
But open stage control does not support ios 9, that's why i use touchosc.

So i'd like to know if the Moss template should be able to give feedback to touchosc.
Or maybe parameter feedback is not possible with touchosc mk1 and Bitwig?

[moss]

Question;
I wanted to make a xy controller from a 1gen ipad mini with touchosc mk1.
I found the DrivenByMossOSC.touchosc extension (deprecated i know) which is broke in some ways, but fixable for a noob like me.

What i can not get working is parameter feedback.
The ipad is connected with rtpmidi to the Moss osc extension. Tried it also with touchosc bridge.

However, when i use open stage control with the Moss template from another win laptop i receive parameter names and parameter values nicely. So i know rtpmidi and osc extension work correctly.
But open stage control does not support ios 9, that's why i use touchosc.

So i'd like to know if the Moss template should be able to give feedback to touchosc.
Or maybe parameter feedback is not possible with touchosc mk1 and Bitwig?

There were many issues and limitations with TouchOSC in the past. That's why I stopped supporting the template. I think it is better nowadays.

[moss]

DrivenByMoss 22.2 is out!

Get it from https://mossgrabers.de

• All devices
  • Fixed: The range of the gain note parameter seems to have changed. Adapted now.
• Fire
  • Fixed: Alternate clip launch option in Drum XoX could not be used.
• Launchpad
  • New: The selected note for editing is automatically cleared when the note edit mode is closed.
• Push
  • New: Added Drum XoX sequencer.
  • New: By long pressing an edited note in the sequencers it can be deselected. If no more notes are selected the previous mode is restored.
  • New: Opening the track/layers detail mode is now only triggered on button up and if the select button was not used to e.g. select a drum sound.
  • New: The Scenes/Clips and Markers modes stay now active when the session view is left.
  • New: Tracks can now be optionally navigated 'flat' (instead of 'hierarchical').
  • New: Added option to include the master track in the track list. This allows to have access to the clips on the master track.
  • New: Push 3: The button in the upper right switches now between the Session/Clips and Marker mode.
  • New: Push 3: In MIDI clip mode, turning the encoder selects the previous/next note for editing. Moving it left/right selects the previous/next clip page.

Enjoy!

[moss]

I don't know how to make buttons for "next Track-Remote-Page", and "Previous Track-Remote-Page"
I expected /track/param/{+,-} might do it, but instead of stepping through each Track-Page, it leaves out the second Track-Page and jumps straight to the Modulator Page (see following picture example). Is that normal?

Same behavior seems to apply to project/param/-, so stepping through Project Remote Control Pages seems also not possible step by step.

Will be fixed in the next update!

Another unexpected behavior: when Bitwigs focus is inside of a Track-Device-Chain (on any device), the /track/page/selected actually chooses the project remote pages!

This might be for Bitwig support.

[Dipe]

DrivenByMoss 22.2 is out!

Get it from https://mossgrabers.de

• All devices
  • Fixed: The range of the gain note parameter seems to have changed. Adapted now.
• Fire
  • Fixed: Alternate clip launch option in Drum XoX could not be used.
• Launchpad
  • New: The selected note for editing is automatically cleared when the note edit mode is closed.
• Push
  • New: Added Drum XoX sequencer.
  • New: By long pressing an edited note in the sequencers it can be deselected. If no more notes are selected the previous mode is restored.
  • New: Opening the track/layers detail mode is now only triggered on button up and if the select button was not used to e.g. select a drum sound.
  • New: The Scenes/Clips and Markers modes stay now active when the session view is left.
  • New: Tracks can now be optionally navigated 'flat' (instead of 'hierarchical').
  • New: Added option to include the master track in the track list. This allows to have access to the clips on the master track.
  • New: Push 3: The button in the upper right switches now between the Session/Clips and Marker mode.
  • New: Push 3: In MIDI clip mode, turning the encoder selects the previous/next note for editing. Moving it left/right selects the previous/next clip page.

Enjoy!

Hey Jürgen, thank you for this awesome update. When turning on the master track view also all sends are shown in the session view eventhough they are hidden. Is it possible to deactivate this behaviour because with many sends the master tracks move really far back. Thank u mate

[moss]

Hey Jürgen, thank you for this awesome update. When turning on the master track view also all sends are shown in the session view eventhough they are hidden. Is it possible to deactivate this behaviour because with many sends the master tracks move really far back. Thank u mate

What do you mean by "they are hidden"?

[nowiamone]

Hello dear Jürgen,

i had the pleasure of trying out a Novation SL MK3 together with my laptop and your script for 45 minutes, and it's so awesome what kind of integration you achieved! Now i'm thinking about buying one, replacing my KompleteKontrol S!

However, i'd love to know if there's any chance of the following "update/options" for the script in the future:

- When in device "perform" mode (when the primary device parameters are shown in the display), it is no longer possible to switch Tracks via Track Left/Right buttons. Would be so nice though, to be able to switch tracks and keep the focus of knobs and display on the primary device parameters of each track!

- speaking of "keeping the focus on the primary device" when switching tracks -> is that even possible in all cases (i didnt have the time to check what happens when switching from a track where the VST instrument is the first in the chain, to a track where some note FX are in front of it. I would hope for the display/knobs to have a 'primary device' option (like the /primary device of your OSC Script!)

- It would be awesome if users could "Flip track/clip navigation". Coming from your nice Komplete Kontrol S script, i was hoping that option exists -> which would change the "Scene up/down" buttons to "Tracks up/down", and the Track left/right buttons to scrolling the scenes, and the Grid as a whole would show the ARRANGE view Cliplauncher (horizontal Tracks )
The 8 small Track-Selection buttons of the Grid would be Scene launcher buttons then, and the Scene-Launch-Buttons Track-Select Buttons.


- an absolutely awesome addition to the options menu (e.g. instead of project switch) would be "fixed velocity 127" (such an essential button the komplete kontrol S has).

- Any chance to have "the best of both worlds" (without the need to constantly switch via "INCONTROL" button): Your awesome integration of the Knobs and Display with Bitwig, and at the same time custom midi cc assignment for the Fadersection? I'm asking because i have a 20track fader controller already for volume -> so i would love to "hardmap" the remaining custom midi cc things onto faders and faderbuttons.
I imagine this as an option like "Make Fadersection generic flexi", or just "Fadersection follows the Novation Components assignments".

- Sorry for the amount of stuff i'm asking you! But this SL mk3 Bitwig combination is sparking some passion!

[moss]

- When in device "perform" mode (when the primary device parameters are shown in the display), it is no longer possible to switch Tracks via Track Left/Right buttons. Would be so nice though, to be able to switch tracks and keep the focus of knobs and display on the primary device parameters of each track!

You can still change the tracks with the select buttons below the volume sliders.

- speaking of "keeping the focus on the primary device" when switching tracks -> is that even possible in all cases (i didnt have the time to check what happens when switching from a track where the VST instrument is the first in the chain, to a track where some note FX are in front of it. I would hope for the display/knobs to have a 'primary device' option (like the /primary device of your OSC Script!)

Interesting idea. Should be possible (but not 100% sure). Will take note.

- It would be awesome if users could "Flip track/clip navigation". Coming from your nice Komplete Kontrol S script, i was hoping that option exists -> which would change the "Scene up/down" buttons to "Tracks up/down", and the Track left/right buttons to scrolling the scenes, and the Grid as a whole would show the ARRANGE view Cliplauncher (horizontal Tracks )
The 8 small Track-Selection buttons of the Grid would be Scene launcher buttons then, and the Scene-Launch-Buttons Track-Select Buttons.

Not so sure how useful the 2 rows are for launching clips, especiall if you would flip it. So, this will rather not happen.

- an absolutely awesome addition to the options menu (e.g. instead of project switch) would be "fixed velocity 127" (such an essential button the komplete kontrol S has).

You mean for the keys?

- Any chance to have "the best of both worlds" (without the need to constantly switch via "INCONTROL" button): Your awesome integration of the Knobs and Display with Bitwig, and at the same time custom midi cc assignment for the Fadersection? I'm asking because i have a 20track fader controller already for volume -> so i would love to "hardmap" the remaining custom midi cc things onto faders and faderbuttons.
I imagine this as an option like "Make Fadersection generic flexi", or just "Fadersection follows the Novation Components assignments".

Not sure if I fully understand this question but you can always "overwrite" a fader in Bitwig. Which will then be executing exclusivly the assigned Bitwig function.