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

[moss]

DrivenByMoss 21.2.0 is online!

Get it from https://mossgrabers.de

• All devices
  • Fixed: Button combinations on session grid did always execute clip play.
• Launchkey Mk3
  • Fixed: Parameter Pages 9-16 could not be accessed.
• Push 3
  • New: Added configuration page for audio interface

Enjoy!

[AuralBee]

Moss! Excellent! I bow before you, O Controller Of Controllers!

[mgawwww]

Howdy! Thou pretty much perfect, Launchkey Mk3 (37 keys) script might have few bugs

- I can't get the user custom Pot or Pad Modes pass any Midi CCs to Bitwig (Midi modulator). With the standard controller script that comes with Bitwig, Midi CCs work ok thou.
- "Long press a pad to only select the clip without starting it." doesn't seem to work.

Also a few feature requests to consider:
- In Drum Mode Sequencer View: Use the green up and down arrows to change "Edit Page 1,2,3 ect" instead of current Offset
- In Session Mode "Stop Solo Mute" menu maybe add New Clip Lenght selection on the 1st row

AND what if we could use the user pot and pad modes with your Flexi Script functionality simultaneously? This could actual work nicely with any controller that has user modes, for eg Launchpad.

Anywho, thank you for that funky music!

[nowiamone]

Moss! Excellent! I bow before you, O Controller Of Controllers!

Hi Jürgen, another OSC question:
I'm trying to build a interface which shows several devices at once, with their name and parameters. I'm reading about "sibling" , and "primary" device in the Documentation. So at least it should be able to show 3 devices at once, before having to press "/device/+" to show more, am i right? Or could there even be a hidden "secondary" "third" "forth" etc. device adress [doesnt seem to exist though] ?

EDIT: it seems /device/sibling/param doesnt exist either, oh.
So i guess, what can be shown on one page are only two devices at once,
the /primary, and the /device. Right?

Thanks alot for the infos

[moss]

Howdy! Thou pretty much perfect, Launchkey Mk3 (37 keys) script might have few bugs

- I can't get the user custom Pot or Pad Modes pass any Midi CCs to Bitwig (Midi modulator). With the standard controller script that comes with Bitwig, Midi CCs work ok thou.

That's how it works. Click on any Bitwig parameter to map one of the knobs. If you really need MIDI CC for a plugin you need to insert a MIDI CC device in front of it and map these.

- "Long press a pad to only select the clip without starting it." doesn't seem to work.

I sadly had to remove this to make the on-release feature work in Bitwig 5.

Also a few feature requests to consider:
- In Drum Mode Sequencer View: Use the green up and down arrows to change "Edit Page 1,2,3 ect" instead of current Offset
- In Session Mode "Stop Solo Mute" menu maybe add New Clip Lenght selection on the 1st row

Noted.

AND what if we could use the user pot and pad modes with your Flexi Script functionality simultaneously? This could actual work nicely with any controller that has user modes, for eg Launchpad.

I am afraid this will not happen.

[moss]

Moss! Excellent! I bow before you, O Controller Of Controllers!

Hi Jürgen, another OSC question:
I'm trying to build a interface which shows several devices at once, with their name and parameters. I'm reading about "sibling" , and "primary" device in the Documentation. So at least it should be able to show 3 devices at once, before having to press "/device/+" to show more, am i right? Or could there even be a hidden "secondary" "third" "forth" etc. device adress [doesnt seem to exist though] ?

EDIT: it seems /device/sibling/param doesnt exist either, oh.
So i guess, what can be shown on one page are only two devices at once,
the /primary, and the /device. Right?

Thanks alot for the infos

... and /eq

[nowiamone]

Thank you for the info! Oh yea, the eq, i kind of 'repressed' the eq in my mind, because i'll wait for the osc-Eq-5

Thanks so much also for the Midi Monitor, i just realized how important it is for bugfixing, when trying to make my own midi script, which shall be bi-directional (for LED feedback on TouchOSC . I have a question though: is there any chance you will upgrade the midi monitor some day, to be 'bi-directional'? So i can check if Bitwig is sending the midi feedback back to my script? Or is that a dumb idea? I'm still a beginner, sorry.

[nowiamone]

Also sorry for another beginner question: i'm reading "getLoopLength()" in the API documentation of Bitwig. Could this somehow be used to grab clip lengths via an osc adress? Because there was the following idea "With a tiny tiny script (lua script within touchosc) it would be possible to get the Clip Playback Progress, based on the length of the clip and the data passed by /beat/str to calculate %complete since clip started playing" by Martin Beech who made the first touchosc controller for Bitwig. So i thought: is "getLoopLength" maybe a possible solution, for our problem of not having clip-playback-progress available in osc interfaces?

[moss]

Thank you for the info! Oh yea, the eq, i kind of 'repressed' the eq in my mind, because i'll wait for the osc-Eq-5

Thanks so much also for the Midi Monitor, i just realized how important it is for bugfixing, when trying to make my own midi script, which shall be bi-directional (for LED feedback on TouchOSC . I have a question though: is there any chance you will upgrade the midi monitor some day, to be 'bi-directional'? So i can check if Bitwig is sending the midi feedback back to my script? Or is that a dumb idea? I'm still a beginner, sorry.

Interesting idea, will take note.

[moss]

Also sorry for another beginner question: i'm reading "getLoopLength()" in the API documentation of Bitwig. Could this somehow be used to grab clip lengths via an osc adress? Because there was the following idea "With a tiny tiny script (lua script within touchosc) it would be possible to get the Clip Playback Progress, based on the length of the clip and the data passed by /beat/str to calculate %complete since clip started playing" by Martin Beech who made the first touchosc controller for Bitwig. So i thought: is "getLoopLength" maybe a possible solution, for our problem of not having clip-playback-progress available in osc interfaces?

No, because you do not know the play position of the clip. However, there is a hack if you use the step position of a MIDI clip but this does not work for audio clips.

[nowiamone]

Also sorry for another beginner question: i'm reading "getLoopLength()" in the API documentation of Bitwig. Could this somehow be used to grab clip lengths via an osc adress? Because there was the following idea "With a tiny tiny script (lua script within touchosc) it would be possible to get the Clip Playback Progress, based on the length of the clip and the data passed by /beat/str to calculate %complete since clip started playing" by Martin Beech who made the first touchosc controller for Bitwig. So i thought: is "getLoopLength" maybe a possible solution, for our problem of not having clip-playback-progress available in osc interfaces?

No, because you do not know the play position of the clip. However, there is a hack if you use the step position of a MIDI clip but this does not work for audio clips.

Oh yes i forgot, the /beat/str is of course only the normal transport playback, not telling anything about clips position

[nowiamone]

Hi Jürgen,
Am i wrongly expecting /eq/param addresses to be alive?
/eq/param/1-8/name
/eq/param/1-8/valueStr
/eq/param/1-8/value
etc, and /eq/page/selected/name seem to be dead?
I’m asking because i thought i could make a quick EQ control which is built exactly like the control for the /device, but it seems that’s impossible. It’s not that big of a deal, because for a nice EQ interface, it’s better anyway to have no switching around pages. So my main question is about the /eq specific additional adresses: /q,/gain:
In case of the reset-function, it doesn’t seem to work as expected.
/eq/gain/1 (0/127) is working properly, but /eq/gain/1/reset does just the same, not resetting. Also not working are /eq/gain/reset/1, and /eq/gain/1 reset[reset sent as string], and /eq/gain/1/value/reset
How do i reset parameters of the /eq, specifically the /gain? I was trying to make a reset button via /eq/gain/1 and sending a 63 or 64 value. But sadly, that translates to either -0.2 or +0.2db, which isn't a true reset to 0.0db. Maybe there's a hack to send 63.5 , haha, but it doesnt seem to work.
Thank you for your help!

[mgawwww]

Also a few feature requests to consider:
- In Drum Mode Sequencer View: Use the green up and down arrows to change "Edit Page 1,2,3 ect" instead of current Offset
- In Session Mode "Stop Solo Mute" menu maybe add New Clip Lenght selection on the 1st row

Noted.

Ok, thanks for you replies! One request more would be to have the possibility to focus Track and Project Remotes, for eg with the Device Select button menu as now with the normal devices. Cheers!

[nowiamone]

Hi Jürgen,
not sure if you encounter the same "bug" like me:

When moving the navigation-button of the Komplete Kontrol S49MK2 to navigate through Tracks, the Group Track is like a "border", not letting the navigation through, unless the navigation-button gets double-tapped quickly. Not sure if that's "normal/expected" behavior.
How i encounter this behavior:
- Bitwig 5 Beta 13, and Bitwig5.0, drivenbymoss 20.3.0
- ARRANGE View, Cliplauncher View
- Project has several Tracks, including at least one Group Track
1. i click on a Clip in the Clip Launcher, to focus it (to navigate within the Cliplauncher)
2. then i use the Komplete S49MK2 4-Direction-Button to navigate from a non-grouped Track to the Grouptrack
-> Result: The Grouptrack doesn't get selected. Instead, it's only in focus for a millisecond, then the focus switches back to the non-grouped Track. (="invisible border")
The same invisible border exists when trying to switch from a Track inside a Group to the Grouptrack.

Since i wasn't sure if that was also the case in the past, I checked it with Bitwig 4.4.10 with DrivenByMoss-19.2.2 : there, the navigation-button switches through group-tracks without effort.

Thanks alot for all your work

I can reproduce that. Seems to be a regression in Bitwig 5. It seems that slots/clips on a group track cannot be selected and therefore it jumps back to the previous track. I reported it.

Hi Jürgen,
sadly, since i changed from DrivenByMoss-20.3.2 to the latest DrivenByMoss-21.2.0,
the Bug i was describing in the quoted post (=”invisible border Bug”) is sadly also affecting horizontal movement in the Cliplauncher now.

When i move in the ARRANGE view Cliplauncher (i have Flip track/clip navigation = on),
the 4-direction-Knob of the Keyboard now even has problems when moving horizontally, from scene to scene. The Clip-Selection “hangs” and jumps back to the original Clip instead of moving to the next.

To reproduce the bug this time, there aren’t even groups necessary.
1 Open new project, Click into the Cliplauncher, focusing/selecting a Clipslot
2 Using the 4-directional-knob, Move from Clip to Clip within the same Track: This works properly
3 Now move to a Clip in the next Track, and THEN again from Clip to Clip within that Track
-> Bug happens!
Checking back with DrivenByMoss-20.3.2 -> Bug does not happen within the same use-case.

Thanks alot for looking at it I'm using Bitwig 5.0.6, on Windows11.

[moss]

Hi Jürgen,
Am i wrongly expecting /eq/param addresses to be alive?
/eq/param/1-8/name
/eq/param/1-8/valueStr
/eq/param/1-8/value
etc, and /eq/page/selected/name seem to be dead?
I’m asking because i thought i could make a quick EQ control which is built exactly like the control for the /device, but it seems that’s impossible. It’s not that big of a deal, because for a nice EQ interface, it’s better anyway to have no switching around pages. So my main question is about the /eq specific additional adresses: /q,/gain:
In case of the reset-function, it doesn’t seem to work as expected.
/eq/gain/1 (0/127) is working properly, but /eq/gain/1/reset does just the same, not resetting. Also not working are /eq/gain/reset/1, and /eq/gain/1 reset[reset sent as string], and /eq/gain/1/value/reset
How do i reset parameters of the /eq, specifically the /gain? I was trying to make a reset button via /eq/gain/1 and sending a 63 or 64 value. But sadly, that translates to either -0.2 or +0.2db, which isn't a true reset to 0.0db. Maybe there's a hack to send 63.5 , haha, but it doesnt seem to work.
Thank you for your help!

Ah, seems I was answering too quick. The EQ has specific parameters, see the EQ section after /device in the manual.