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

[nowiamone]

EDIT: updated on 20.1.24

Dear Jürgen, thank you so much for answering! Here are my thoughts:

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

This is only possible when Track or Volume pages are selected in the SL MK3 Display.
When the Parameter-Page of a Track is shown, the Track < > Buttons are "dead", because they're re-assigned to switching the pages, which isn't even necessary since the pages can be directly accessed via the Buttons above the Cliplauncher.
Based on muscle memory of that basic function on the keyboard (track switch left/right), it's quite unfortunate to lose it, especially since i mostly never want to leave the Parameter-Page of Tracks!
Well, maybe, if i m lucky, you will reconsider the horizontal cliplauncher, and then the track next/previous buttons would have a new location anyway (up arrow/down arrow next to Cliplauncher) and hopefully work under all circumstances

- 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.

Yes, it would be great to have "primary device" on top of the "Parameters" page. I would stay in that page for 99% of the time! Because in my workflow i mostly need to control my favorite VST plugin parameters
I forgot to mention a wish which is quite essential for this:
Could you please color the Parameters-Page/Primary-Device-Page of Tracks after the Track-Color, not permanently pink/purple for all Bitwig Tracks I like pink/purple, but my main usage of the keyboard is “staying” in the Parameter-Pages of Tracks all the time -> so it makes no sense to have them all colored the same, as it destroys visual Feedback about which Track is selected!

11.jpg

- 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.

Implementing this would be incredibly valuable and awesome though!
A 2x8 Cliplauncher is quite limited in general, but the usefullness of the orientation highly depends on the structure of the Bitwig live-set!
One could say that the current cliplauncher isn't useful at all to quickly launch Clip-Variations (=Scenes), because only 2 Scenes are available to choose from!
So increasing the available Scenes from 2 to 8 makes a huge impact.

Aside from that advantage of better "Remix" abilities of a horizontal Grid, i have to say that i'm simply in love with Bitwigs horizontal Arrange-view-Cliplauncher.

I live and think within that horizontal logic.
Actually that view was one of the main reasons why i switched over to Bitwig (amongst other things, including your OSC script, haha!! )
And i never look at the MIX view, but always have the ARRANGE view Cliplauncher in front of me.
So, switching the orientation of the SL MK3 Cliplauncher would, literally 'change the world' for me.

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.

It would be so valuable if there was an option to also exclude the Fader-Section-Buttons totally from the drivenbymoss "Incontrol" script as optional setting -> by Adding "Disable Faderbuttons" to the Controller Settings.
This would have a big advantage, because i could assign their MIDI CCs in my Touch OSC Bitwig Looper, which sends out /OSC messages based on incoming Midi CC. Otherwise i have double-assignments and unwantingly press mute/solo all the time.

In case you don't want to do a horizontal Cliplauncher, it would be really awesome to be able to "disable Cliplauncher", too! I could then use the Arrows and Pads in a more meaningful way, like being assigned to my Looper, or to a drummachine!

- 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?

Yes, However, i now found out, that via the "Global" button, it's okay enough to reach that function

Thank you so much for your time and work!!

[Brainlag]

Hey everyone,

First of all: thanks for all the amazing work to enable us to do all these things with Bitwig, it is much appreciated!

Now to my question:
I'm an absolute coding noob, but I've been trying to get into OSC/OpenStageControl to better understand your script and be able to edit things to my needs. I've been able to do simple buttons/commands, but the ones most crucial for me, I just can't seem to get the hang of:

/launcher/postRecordingAction

and

/launcher/postRecordingTimeOffset

Specifically, I would like to create buttons that allow me to quickly switch from 1 Bar post Recording Time Offset to 4/8 Bars. Somehow I can't seem to get it to work, is there something particular to keep in mind?

I currently put "/launcher/postRecordingTimeOffset/16" in as address

I have tried looking for the question, but it is very difficult to browse this massive Forum. If it has been asked/answered already, feel free to refer me/delete this Post.

Much love,
Brainlag

[nowiamone]

Hey everyone,

First of all: thanks for all the amazing work to enable us to do all these things with Bitwig, it is much appreciated!

Now to my question:
I'm an absolute coding noob, but I've been trying to get into OSC/OpenStageControl to better understand your script and be able to edit things to my needs. I've been able to do simple buttons/commands, but the ones most crucial for me, I just can't seem to get the hang of:

/launcher/postRecordingAction

and

/launcher/postRecordingTimeOffset

Specifically, I would like to create buttons that allow me to quickly switch from 1 Bar post Recording Time Offset to 4/8 Bars. Somehow I can't seem to get it to work, is there something particular to keep in mind?

I currently put "/launcher/postRecordingTimeOffset/16" in as address

I have tried looking for the question, but it is very difficult to browse this massive Forum. If it has been asked/answered already, feel free to refer me/delete this Post.

Much love,
Brainlag

Hello,
"/launcher/postRecordingTimeOffset 4" is one bar.
You have to make it without the / slash sign, as the 4 is an argument.

I'm working with Touch OSC and don't know the specifics of Open stage control.
However, Mr drivenbymoss did very good tutorials, including on youtube:


Also, it's really helpful if you open the open stage control template provided by drivenbymoss archive package, in the resources folder/osc folder! Just open that template "OpenStageControl4Bitwig.json" and learn the basics of how to properly send the commands
When i look into it, i see the pre-roll for example, which has a similar structure to the post record actions. It's done by a switch, like this:

switch.jpg

switch2.jpg

For further OSC related questions, you might find help in the Bitwig discord #controllerism, for example.

[gibson_g]

Hello everyone,

i am using some of your scripts for quite a time and im really thankfull for all the work!

some days ago i got a launchpad pro mk3 and im struggling to get into the user mode.

double clicking the device button just switches between device and project parameters.

im am using the drivenbymoss 22.2.0 with Bitwig 5.1 on a Ubuntu Studio LTS installation.

thanks already

[Oriolus]

Dear Jürgen,
I have been using DM Generic Flexi with Faderfox EC4 in Bitwig which is very convenient because of self mapping structure.
In 22.2 I've got a strange behave of "Track: scroll track" command. Now active track can not scroll through the group normally. It just scroll up to the head group track and fall's back to the next one - the first track in the group. And if I fold all the groups it will not scroll at all.
Before, in 22.1 it was also a kind of issue with this option - active track could't scroll through the head track of the group easily, needed additional scrolling. Now, in 22.2 it just stops.

in FF EC4 - Type:CCR1
in Flexi - Knob mode: Relative Two Complement
as before

[astralcurrents]

Hi Moss, I have a request for the little lightbulb button in the upper left on the Push 3. Instead of launching a web browser, can you configure it to show the description window for the selected Bitwig device? (normally F1) That can be a finicky key combination on a Mac since you have to press Fn+F1 to bring it up.

[moss]

Hello everyone,

i am using some of your scripts for quite a time and im really thankfull for all the work!

some days ago i got a launchpad pro mk3 and im struggling to get into the user mode.

double clicking the device button just switches between device and project parameters.

im am using the drivenbymoss 22.2.0 with Bitwig 5.1 on a Ubuntu Studio LTS installation.

thanks already

That's correct, project/track parameters replaced user parameters and will be removed in the future from Bitwig.

[moss]

Dear Jürgen,
I have been using DM Generic Flexi with Faderfox EC4 in Bitwig which is very convenient because of self mapping structure.
In 22.2 I've got a strange behave of "Track: scroll track" command. Now active track can not scroll through the group normally. It just scroll up to the head group track and fall's back to the next one - the first track in the group. And if I fold all the groups it will not scroll at all.
Before, in 22.1 it was also a kind of issue with this option - active track could't scroll through the head track of the group easily, needed additional scrolling. Now, in 22.2 it just stops.

in FF EC4 - Type:CCR1
in Flexi - Knob mode: Relative Two Complement
as before

I had a look and this seems to be a Bitwig issue. I did report it.

[moss]

Hi Moss, I have a request for the little lightbulb button in the upper left on the Push 3. Instead of launching a web browser, can you configure it to show the description window for the selected Bitwig device? (normally F1) That can be a finicky key combination on a Mac since you have to press Fn+F1 to bring it up.

Yes, tried this already but it seems that the action has no effect. Did report it to Bitwig as well.

[moss]

DrivenByMoss 22.2.1 is online!

Get it from https://mossgrabers.de

• Fire
  • New: Selecting an already selected group track in mix mode does toggle the group open/closed.
• LaunchControl XL
  • New: In transport mode (keeping 'Record Arm' pressed) button 5 triggers Undo and button 6 Redo.
• OSC
  • Fixed: /track/param/{-,+} and /project/param/{-,+} did switch 8 pages instead of 1.
• Push
  • Fixed: Improved button colors in simulator.

Enjoy!

[astralcurrents]

Hi Moss, I have a request for the little lightbulb button in the upper left on the Push 3. Instead of launching a web browser, can you configure it to show the description window for the selected Bitwig device? (normally F1) That can be a finicky key combination on a Mac since you have to press Fn+F1 to bring it up.

Yes, tried this already but it seems that the action has no effect. Did report it to Bitwig as well.

Thanks! Hopefully it can be sorted out. It would be a handy shortcut.

[nowiamone]

DrivenByMoss 22.2.1 is online!

Get it from https://mossgrabers.de

• Fire
  • New: Selecting an already selected group track in mix mode does toggle the group open/closed.
• LaunchControl XL
  • New: In transport mode (keeping 'Record Arm' pressed) button 5 triggers Undo and button 6 Redo.
• OSC
  • Fixed: /track/param/{-,+} and /project/param/{-,+} did switch 8 pages instead of 1.
• Push
  • Fixed: Improved button colors in simulator.

Enjoy!

thanks for the /param/+- fix !

[gibson_g]

That's correct, project/track parameters replaced user parameters and will be removed in the future from Bitwig.

thanks for the reply!

Just to understand it completely - there is no possibility to display the project param pages on the scenes buttons? similar to the user mode ...

because now you could just switch pages with next and prev?

[moss]

That's correct, project/track parameters replaced user parameters and will be removed in the future from Bitwig.

thanks for the reply!

Just to understand it completely - there is no possibility to display the project param pages on the scenes buttons? similar to the user mode ...

because now you could just switch pages with next and prev?

Both works. But I just noticed that the color indication on the scene buttons seems to be missing.

Edit: to be more specific: the scenes buttons change the pages by 8

[gibson_g]

Both works. But I just noticed that the color indication on the scene buttons seems to be missing.

Edit: to be more specific: the scenes buttons change the pages by 8

so i guess you have not planned to reintroduce using the scenes buttons for direct access to the first 8 pages?

and another one: are there mappable slots left for midi interaction which isnt possible with the project params? For shortcuts for example?

thanks for the support!