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

[nowiamone]

Dear Jürgen,
Because i’m working with OSC so much, i realized some missing functions, which i’m sure would be awesome and really helpful for every user to have. Some of them could potentially even increase the joy of working with Bitwig in general, because of better controls!

1. Bitwigs unique and awesome Track Remotes are sadly crippled down into a) just controlling the currently selected Track! b) controlling a maximum of 8 parameters at the same time. Please, please, could you at least get rid of a) and potentially someday also b)? On my Touchinterface, it would be possible to control at least 8 Parameters for 20 Tracks, all on one page, all at the same time! But instead, Bitwig is crippled down to a 8-knob-control, rendering 152 out of 160 Faders/Knobs useless. Poor Knobs! The remotes deserve to be assigned

2. Bitwigs unique and awesome Project Remotes would also deserve to be fully controllable, all on one page. In case it’s technically possible, it would be SO awesome to be able to control more than 8 on one page (increasing bank size). 12 would already be a charm, 16 wonderful. I mean, Bitwig is supposed to be modulation-heaven. I’m sure heaven isn’t restricted into minecraft-style blocks of 8, in general. For me, this is the essence of OSC (and touch interfaces) : getting rid of the standard-limitations of controllers once and for all! Freeeeedom!!!

3. Something which is fundamentally missing from Bitwigs normal Mixerpanel in ARRANGE view are the peak hold values. Only when opening the big meters in the MIX view, Bitwig shows every peak hold value. It would be SO awesome, if you could add an OSC address for those peak hold values (string showing decibel value) for text widgets. And an address for resetting those peak hold values via button-press. This would be SO good, since it is absolutely essential for mixing, and this would feel like an upgrade to Bitwig itself.

4. Option to reset the /crossfade to 0 via /reset address for a button would be great! Right now, the center of the fader is either -0.79 or +0.79db, never 0.0db, due to the innate limitations of a value-range-scale which has no absolute zero-point. Thus a reset button would be essential (just like with the /eq gain and q parameters) for live performances.

5. The SampleBrowser would profit greatly from having an OSC command for toggle “play at original speed / stretch to project tempo”

6. OSC Addresses for setting the Grid (measure of beat time grid, beat grid subdivision, snap to grid, adaptive grid, snap to grid offset, snap to events) would be awesome to have, because those Settings could permanently be shown with their true on/off status in a OSC interface, improving Bitwigs experience alot, because even in Bitwig one doesn’t have an overview of all those toggles, without clicking around! Having those OSC Addresses would fundamentally improve the experience of controlling Bitwig!

7. Having an OSC address for “Restore Automation Control” would be awesome, because its functionality is so much better when having Visual feedback about on/off state !

8. OSC Address missing for: setting record quantizations. Another setting which would fundamentally enhance Bitwig itself! Because it’s not midi assignable in Bitwig! And its status is visually hidden in the PLAY submenu.

9. OSC Adress missing for: record as comping takes.

10. Clip-playback-progress (but i know, we have to pray for Bitwig to implement this

I’m really sorry for that long list! It just came all to me, because i’m looking at my -almost- finished Interface, and thus the ‘last missing pieces’ of the puzzle got more obvious to me.
Anyway, thanks so much for your awesome OSC Script, which makes controlling Bitwig so much fun. All the best

PS: here’s a screenshot in case you’re interested. (Interface for a 24inch screen)

Sternenherz UI Interface for Bitwig.jpg

One of the Subpages:

Arranger Sternenherz UI.jpg

[moss]

so just to be sure: there's no "reset" (return to default) osc function for gain and q, right?
At least it's not part of the manual (but i was hoping it exists somehow, haha).

Makes sense to add them. Maybe I simply could add all the parameters...

In case you've overlooked my other post: there's a new bug since drivenbymoss 21.2.0 with the Komplete Kontrol s49mk2 4-directional-knob, when moving the selection cursor in the cliplauncher with it. Selection gets stuck / jumps back, when trying to move from scene to scene in the cliplauncher, happening only after having switched from track to track in the cliplauncher. Thank you!

Up to my knowledge that is a Bitwig bug.

Thanks!

The bug wasn't happening with My Bitwig 5.0.6 together with DrivenByMoss-20.3.2.
Now, with Bitwig 5.0.6 and DrivenByMoss-21.2.0 it's happening.
I haven't tested the Bitwig internal-script for the KompleteKontrolS49MK2 keyboard for quite some while, but now i did. I almost couldn't believe it: The movement in the cliplauncher is working properly now Even moving through groups!? That's a strange development of things, because many months ago, i permanently switched to using only your script, because it was working better (and it's still so much better designed, with customization in the controllerpanel.. would love it, if it would be restored to former greatness, )!

Ah, I see what you mean. It is a stupid workaround to move the clip selection between track which is not working 100% (before that it had a different issue). Will see what I can do about it...

[moss]

Hey moss last bitwig 5.0.4 not work fix accent in launchpad x

Works fine for me. Tested with 5.0.6.

[moss]

Hi, I've found some bugs with Push 2 on Bitwig 5.0.4.

1. The browse menu does not show Collection, and the configuration options for show/hide Browser elements are shifted. E.g. Collection controls Location, Location controls File Type, etc. Device Type and Device do nothing. I've found no way to make Collection appear.
2. In the browse menu, when scrolling through tags, the list changes as the selection is changed. This is very annoying, makes tag selection kind of useless from push.

Your Bitwig extension for Push is a lifesaver to have. Thanks very much for your work.

The API is sadly not yet adapted to the new Bitwig browser and you get some strange effects.

1) I removed the collection column since it is currently always empty but forgot to update the configuration options. I think I will remove the completely since they do not make much sense anymore.
2) This is the same weird behaviour as in the browser in Bitwig. I will take note but please also report to Bitwig.

[moss]

Elkiwixmandalaz wrote: ↑Thu Jun 29, 2023 7:14 pm
Hi Again, I just went ahead and try toggling through "NOTES" on Bitwig with the LaunchPad Pro and I am notable to toggle through either "NOTE" or "CHORD". I am currently trying to use the LaunchPad as a key board like I did in the past. I simple grabbed the sampler on Bitwig, and selected "Acoustic Piano". I hope that you can help me out. I also grabbed the latest version of DrivenByMoss and put it on my extensions folder.

Thanks in Advance!
What is your question?


Hi Mate,
My question is. How do I activate the piano roll on my launchpad pro? I mean there was a key board if you pressed CHORD in the past. Just wondering if it will still be available or not? I would like some keys, might buy myself a keyboard if you say you took that option away.

Thanks in Advance, Ricardo Fernandez or EL Kiwix Mandalaz

Press Note twice.

[moss]

Moss for Push 3 please please please integrate the pad sensitivity as per Ableton (threshold, drive, compand, and range settings) so that the pads are as beautiful to use as they are in Ableton.

That would be super awesome

Thanks
Jed

Ah, didn't notice that the settings are different. Should hopefully not too difficult to figure them out...

[moss]

Hi, I have a question. I have a Push 2 and have been trying your script which, by the way, is pretty awesome, and I've been looking for a function it has in ableton. In ableton, when you press the record button, it creates a new clip in a empty slot and stop when you press it again. I have been reading you manual and just have found two possibilities:
1. Press new or fixed lenght and create a clip with an specific lenght.
2. Press a "red pad" on an armed track in the session view and, when ended, press the record button and it will stop recording and start looping that clip.
The thing is, I believe it's much more faster to just press one button to start the recording and the same again to stop it. That way you don't have to worry about lenghts and doesn't have to be doing buttons combinations which usually drives me to press it too late and record out of time.
As I said, I didn't find this option in the manual but I suppose It's probably there so, if you can tell me how to do it, I will appreciate it a lot.
Thank you very much in advance!!!

It is currently not there. But on some other controllers. Maybe I will make this configurable as well.

[moss]

I have a Launchpad S and would like to implement support for your extension. Can you give me some hint, how this would be achieved best, i.e. where to make changes to your source code? I did not yet dive into programming of the Launchpad, but my guess is that the protocol is somewhat different. Do you have a protocol layer in your code, so that another protocol can be "plugged in"?

I am afraid I cannot give support for development but as a starting hint look into the sub-folder with the already existing different Launchpad versions.

[moss]

Hi Moss, great work on the Akai Fire!

I think I encountered a bug in Note Editing. After I enable Note Editing, select a note, then turn the Select knob, the values go either up or down by 0.8, 2, 8.4, 34, 96. No matter which way I turn the knob, the values will go in the same direction until I cancel and try again.

I'm new to BitWig but I inspected the piano roll and it seems the notes aren't actually moving but "micro-pitch expression editing" is happening. Screenshot attached.

Not sure what's going on, what do you think?
I'm using 21.2.0.

Yes, this does change the micro-pitch. But there seems to be something broken in Bitwig. The value was in the range of [-24,24]. But now it seems to be in the range of [-96,96]. I suspect that they forgot the update the API accordingly. I reported the issue.

Also, I think you didn't mention it in the documentation but we can transpose clips by an octave by pushing and turning the Select knob.

Yes, will add it! Also I noticed that it still opens the plugin window in that case, which should not happen.

[moss]

Hi Moss, found some weird behavior (maybe a bug?)
I have a flexi device that assigns Track: Select Previous Track and Track: Select Next Track, and these allow me to use my device to move up and down tracks with no issue, unless I have inactive tracks, and I have "show deactivated tracks" turned off. Then, it does not advance the selected track to the next active track as expected.

I cannot see anything wrong with it. When "Exclude deactivated items" is off it selects all tracks, when it is on, only the active ones.

[moss]

On the Launchpad (Mini) the 'red box; sometimes does not follow. Not that much of an important issue I presume but wanted to report it. In the following example all 8 tracks including the group track are on the Launchpad which means the box should start one track lower :


launchpadBox.jpg

It looks as if the 1st track is deactivated, correct? So, I guess that's the reason.

[moss]

Dear Jürgen,
Because i’m working with OSC so much, i realized some missing functions, which i’m sure would be awesome and really helpful for every user to have. Some of them could potentially even increase the joy of working with Bitwig in general, because of better controls!

What an insane setup! But great to see that someone is maxing it out!

1. Bitwigs unique and awesome Track Remotes are sadly crippled down into a) just controlling the currently selected Track! b) controlling a maximum of 8 parameters at the same time. Please, please, could you at least get rid of a) and potentially someday also b)? On my Touchinterface, it would be possible to control at least 8 Parameters for 20 Tracks, all on one page, all at the same time! But instead, Bitwig is crippled down to a 8-knob-control, rendering 152 out of 160 Faders/Knobs useless. Poor Knobs! The remotes deserve to be assigned

a) This would add a lot of messages and I don't want to do that.
b) It is an existing Bitwig drawback.

2. Bitwigs unique and awesome Project Remotes would also deserve to be fully controllable, all on one page. In case it’s technically possible, it would be SO awesome to be able to control more than 8 on one page (increasing bank size). 12 would already be a charm, 16 wonderful. I mean, Bitwig is supposed to be modulation-heaven. I’m sure heaven isn’t restricted into minecraft-style blocks of 8, in general. For me, this is the essence of OSC (and touch interfaces) : getting rid of the standard-limitations of controllers once and for all! Freeeeedom!!!

See above.

3. Something which is fundamentally missing from Bitwigs normal Mixerpanel in ARRANGE view are the peak hold values. Only when opening the big meters in the MIX view, Bitwig shows every peak hold value. It would be SO awesome, if you could add an OSC address for those peak hold values (string showing decibel value) for text widgets. And an address for resetting those peak hold values via button-press. This would be SO good, since it is absolutely essential for mixing, and this would feel like an upgrade to Bitwig itself.

That's something you need to request from Bitwig. Currently, only the VU values are available.

4. Option to reset the /crossfade to 0 via /reset address for a button would be great! Right now, the center of the fader is either -0.79 or +0.79db, never 0.0db, due to the innate limitations of a value-range-scale which has no absolute zero-point. Thus a reset button would be essential (just like with the /eq gain and q parameters) for live performances.

Noted.

5. The SampleBrowser would profit greatly from having an OSC command for toggle “play at original speed / stretch to project tempo”

Not possible (another wish for Bitwig people).

6. OSC Addresses for setting the Grid (measure of beat time grid, beat grid subdivision, snap to grid, adaptive grid, snap to grid offset, snap to events) would be awesome to have, because those Settings could permanently be shown with their true on/off status in a OSC interface, improving Bitwigs experience alot, because even in Bitwig one doesn’t have an overview of all those toggles, without clicking around! Having those OSC Addresses would fundamentally improve the experience of controlling Bitwig!

Same as 5) but partially possible via actions. But actions have the issue to rely on focus.

7. Having an OSC address for “Restore Automation Control” would be awesome, because its functionality is so much better when having Visual feedback about on/off state !

You mean for parameters?

8. OSC Address missing for: setting record quantizations. Another setting which would fundamentally enhance Bitwig itself! Because it’s not midi assignable in Bitwig! And its status is visually hidden in the PLAY submenu.

Noted.

9. OSC Adress missing for: record as comping takes.

Noted. But need to check if possible.

10. Clip-playback-progress (but i know, we have to pray for Bitwig to implement this

Mentioned that as well.

I’m really sorry for that long list!

You should!

[dolomick]

Hello,

I'm trying to get my new X Touch One working with Bitwig 4.4.1 on Win 10.

Which driven by Moss version am I supposed to be using? Couldn't get either the v5 or the "v4.3 and up" to work.

The X-Touch came with firmware 1.1 and I don't see a 1.07 available on the Behringer website, maybe that is my issue?

I put the Moss extension in the folder indicated in the instructions, and I see triangles on my faders in Bitwig, but none of the controls are working. I am sure I am doing something wrong, thanks for helping!

EDIT - I got it working by changing the X Touch into user mode on the top left dial and using the v4.3 and up Moss extension.

Good thing you explained how the scrub button changes modes, the Behringer user guide is nonexistent with any useful info.

[nowiamone]

What an insane setup! But great to see that someone is maxing it out!

i felt obligated, after seeing how well the /osc commands are working

a) This would add a lot of messages and I don't want to do that.

ok, no problem, because at least there's a workaround, via midi mapping

IF it wouldn't be hard for you, adding a Midi Out-Port to your Midi Monitor Utility Script would be insane.
Your Midi Monitor Script is a hidden gem, because of the simplicity of the assignment-methods, compared to the generic flexi. If it would have an Midi Out Port (sending Feedback from Bitwig to my Interface), this would mean the world to me.
[explanation: the generic flexis bi-directional functionality is limited into banks of 8 user parameters, and additionally only works bi-directionally for the 'undefined' midi cc numbers, (like 52-63, 102-119) , while your midi monitor script would work for all midi cc numbers, and not be separated into banks ] I admit it would be a "mis-use" of a script made for monitoring, but if it works, it works

something you need to request from Bitwig

Oh, yet another thing to ask them. I only can hope someday they have mercy about some API 'updates'.

nowiamone wrote: ↑Tue Sep 05, 2023 2:03 am
7. Having an OSC address for “Restore Automation Control” would be awesome, because its functionality is so much better when having Visual feedback about on/off state !
You mean for parameters?

yes, basically, having this button working bi-directionally would be great:

this button.jpg

So, when it lights up in Bitwig, that it also lights up on the OSC interface, because there's an adress for it It's not that important, but would be very convenient, and complete the osc transport section.

Thank you!!

[csharp214]

Hello Professor Moss. First and foremost thank you for your excellent work on this Bitwig script. I do have a question. By watching your videos i was able to get the patch names from my external synths inside of Bitwig version 4. I recently upgraded to version 5 and cannot figure out how to get this working in the new version. To be honest I cant even find out where the patch names are supposed to show up. Can you help me please?