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

[Alban18]

Hey TJ,

So you are basically saying the labels don't matter, but the cc# does? And to get my midi cc#, I have to use a midi monitor?
Is this midi monitor a software I can download? If I can get this HUI script, how do I apply it to my controller in Bitwig?

Is there a manual for the device? I could not find any on the m-audio webpage.

The upper part in Generic Flexi is a MIDI monitor. If you press a button and nothing is showing up, the controller does not send anything (at least on the port you selected). I think there is also an editor for the controller, if yes, you can check what commands are supposed to be send by specific buttons/knobs.

As TJ suggested above, check if it supports HUI or MCU (MCU would be better) out of the box and then use my HUI/MCU implementation.

Yeah so yes m-audio does have an editor which is the main reason I came here. The play button midi cc# is different from the cc# that your midi monitor generated. So I didn't know if I was basically messing stuff up when I assigned the play button transport using midi cc# 93 when my m-audio editor says the play button uses cc# 4.

I will check what my controller supports when I get home but I believe that I use an MCU script that Bitwig has in it's controller scripts. I would continue using that but I was having problems using my controller whenever I would finger drum while recording which would start desyncing and just throw off the timing horribly. But that only happens when my midi input is on. When I turned it off, I can record my drums fine.

But your script is amazing that I can assign each button on my controller a parameter in my daw and save it without having to midi cc learn everything everytime.

But yeah basically, I get a different cc# from my editor when flexi or just no cc# is populated. But since my m-audio editor cc# is different from the labels, I was hesitant to assign stuff.

[moss]

Hey TJ,

So you are basically saying the labels don't matter, but the cc# does? And to get my midi cc#, I have to use a midi monitor?
Is this midi monitor a software I can download? If I can get this HUI script, how do I apply it to my controller in Bitwig?

Is there a manual for the device? I could not find any on the m-audio webpage.

The upper part in Generic Flexi is a MIDI monitor. If you press a button and nothing is showing up, the controller does not send anything (at least on the port you selected). I think there is also an editor for the controller, if yes, you can check what commands are supposed to be send by specific buttons/knobs.

As TJ suggested above, check if it supports HUI or MCU (MCU would be better) out of the box and then use my HUI/MCU implementation.

Yeah so yes m-audio does have an editor which is the main reason I came here. The play button midi cc# is different from the cc# that your midi monitor generated. So I didn't know if I was basically messing stuff up when I assigned the play button transport using midi cc# 93 when my m-audio editor says the play button uses cc# 4.

I will check what my controller supports when I get home but I believe that I use an MCU script that Bitwig has in it's controller scripts. I would continue using that but I was having problems using my controller whenever I would finger drum while recording which would start desyncing and just throw off the timing horribly. But that only happens when my midi input is on. When I turned it off, I can record my drums fine.

But your script is amazing that I can assign each button on my controller a parameter in my daw and save it without having to midi cc learn everything everytime.

But yeah basically, I get a different cc# from my editor when flexi or just no cc# is populated. But since my m-audio editor cc# is different from the labels, I was hesitant to assign stuff.

Normally such editors support different templates. Could be that you are looking at the wrong one or it is not the one that is active/transmitted to the controller.

Also check out the MCU implementation coming with DrivenByMoss. This gives you much more options and is up to date compared to the stock Bitwig one.

[gExpectations]

heres the manual if its still interesting: https://storage101.ord1.clouddrive.com/ ... 1646957752

[Kevka]

Hi, I bought M-Audio Oxygen Pro Mini just recently for travelling purposes and I have to say I am a bit frustrated with it's editor. For me, it is easier to program knobs, faders and buttons from the keyboard itself. For the keyboard to work You have to set MCUPro with Midi port 3 / in and out and generic keyboard - MIDI keyboard script with MIDI ports Oxygen Pro xx (25/49/Mini...) in and out. Easy. Thats in the manual. But the manufacturer template is rather limited in my opinion. It is nowhere near as good as Ableton. So, I have started fiddling with Generic Flexi kindly provided by mr. Moss. It is a great script and with it You can configure the keyboard to Your liking but there are some things I cannot figure out. For example, I cannot find any way to set up "SHIFT" button the way I would like to. There is no info on that in the manual. Other thing is that I could not find way to set up DAW Mode user preset ( number 9 ) to change between pads with modifier key "SHIFT" so that it sends message that changes between PAN/DEVICE/SENDS status. Sorry for the grammar and my english. It is my first post ever . What i mean is that first three pads 1-3 are labeled PAN/DEVICE/SENDS. In Ableton, MPC and Reason factory templates You can press SHIFT and one of the pads to switch between the setting and then the knobs above control pannnig/device parameters and sends respectively. I tried but I cannot replicate this behaviour in User preset or modify the Bitwig script itself. One thing to notice is that You cannot modify DAW templates from provided editor but You can from the Keyboard itself, correct me if I am wrong. Those are the things I cannot figure out. BUT I have started tinkering with the MIDI monitor yesterday that is provided with Generic Flexi and I figured out the messages that Ableton/MPC/Reason send to do the things I have mentioned above. For example, when using Ableton template, SHIFT + PAD 1 (labeled PAN) combination sends CC 85 on MIDI channel 16, SHIFT + PAD 2 (labeled DEVICE) sends CC 86 on MIDI channel 16 and so on. It is the same on the three aforementioned templates. When selected SHIFT + PAD is pressed it turns red and stays that way using the aforemantioned templates while still holding SHIFT. It does not work in BITWIG template though. When pressing SHIFT in BITWIG or USER template only PAD 1 labeled PAN lights up and I cannot get the Oxygen Pro MINI to replicate the behaviour. Will someone please help or give some hints? Also, when You press PAD without SHIFT modifier button the PAD sends Type: Note, number 30 CC MIDI Channel 1 when in Ableton or Type: Note number 30 MIDI Channel 10 when in MPC template. That is where my tinkering skills fail. I am to incompetent to replicate this behaviour in BITWIG or USER modes. Another "also". I have tested all the Mackie scripts provided with DrivenByMoss v 16.0.0 and none works correctly or maybe I am doing something wrong or the M-Audio implementation is kinda weird. (To bad the Mackie scripts do not provide monitor like in Generic Flexi and You cannot modify assignments). I do not know. If anyone has better understanding of how Oxygen Pro Mini works please contact me. I would be very glad to provide my time and energy to make this controller work well with Bitwig with as complete functionality as it can get. I can do the tedious work like setting the actions or configuring but I am not a pro programmer. I stared learning Python and Javasript a week ago but I will not be able to write a controller script myself in forseeable future. I would also like to implement other functionality from other templates but I lack the skills at the moment. Lastly, I would like to know is it possible to reverse enginner Ableton script? From what I have checked Ableton scripts are written in python and Bitwig in javascript. Is it legal? To rewrite it? I am not a copyright specialist but I think it is copyrighted... and I would like not to break any rules and get in trouble. Anyway, I have written down any messages Ableton template sends through MIDI port 3 if it helps. I was just curious. So far I can share anything I have learned about so far (not that much) and I would like to ask for help for setting it up so it integrates with Bitwig in a more sophisticated manner than what the Bitwig template provides. Cheers. Once again sorry for my broken english. I think it is my first post on the KVR forum ever. I am pretty exited beacuse Oxygen Pro Mini is my first midi controller ever, before I had been doing everything by using mouse and keyboard. Thanks again. PS The manual describes everything apart from the SHIFT button configuration itself. And I hope my post is rather readable.

[dupont]

Is new feature shift + pad trigger in Biitwig 4.2 implemented in drivenbymoss drivers ? I can't make it work with APC40 MKII.

[moss]

For example, I cannot find any way to set up "SHIFT" button the way I would like to.

Are you sure that the Shift button does send a MIDI message? On many keyboards it does not send anything. If you are lucky you can define different MIDI events for all buttons/knobs/faders when Shift is pressed but that is rare.
As a workaround you could define any of your buttons as the Shift button.

What i mean is that first three pads 1-3 are labeled PAN/DEVICE/SENDS. In Ableton, MPC and Reason factory templates You can press SHIFT and one of the pads to switch between the setting and then the knobs above control pannnig/device parameters and sends respectively. I tried but I cannot replicate this behaviour in User preset or modify the Bitwig script itself.

I do not know the device and cannot help you here. I guess these button combinations send specific MIDI messages which need to be handled by the script (sounds a lot like the Novation Launchpad modes). If these messages are simple CC messages you could switch the Generic Flexi modes with them as well.

One thing to notice is that You cannot modify DAW templates from provided editor but You can from the Keyboard itself, correct me if I am wrong. Those are the things I cannot figure out. BUT I have started tinkering with the MIDI monitor yesterday that is provided with Generic Flexi and I figured out the messages that Ableton/MPC/Reason send to do the things I have mentioned above. For example, when using Ableton template, SHIFT + PAD 1 (labeled PAN) combination sends CC 85 on MIDI channel 16, SHIFT + PAD 2 (labeled DEVICE) sends CC 86 on MIDI channel 16 and so on. It is the same on the three aforementioned templates.

So, it should be possible to map these to Generic Flexi mode triggers.

If anyone has better understanding of how Oxygen Pro Mini works please contact me. I would be very glad to provide my time and energy to make this controller work well with Bitwig with as complete functionality as it can get. I can do the tedious work like setting the actions or configuring but I am not a pro programmer. I stared learning Python and Javasript a week ago but I will not be able to write a controller script myself in forseeable future.

If you want to give it a go, see my Bitwig API tutorials on my Youtube channel.

[moss]

Is new feature shift + pad trigger in Biitwig 4.2 implemented in drivenbymoss drivers ? I can't make it work with APC40 MKII.

Not, yet.

[tishta]

Hi Jurgen,
You asked me to post here after posting on your youtube channel about the Open Stage Control script.

Just wanted to let you know I fixed the issue. I did post on your channel as well.

I was getting this error

Code: Select all

OSC Crashed error Index 1 out of bounds for length 1

However, I fixed the issue.

The Bank Page Size was set to 1 instead of 8. Not sure if I did that by mistake or some update reset it to 1. Anyway my template seems to be working again.

Screenshot 2022-03-14 at 9.16.21 am.png

[moss]

Hi Jurgen,
You asked me to post here after posting on your youtube channel about the Open Stage Control script.

Just wanted to let you know I fixed the issue. I did post on your channel as well.

I was getting this error

Code: Select all

OSC Crashed error Index 1 out of bounds for length 1

However, I fixed the issue.

The Bank Page Size was set to 1 instead of 8. Not sure if I did that by mistake or some update reset it to 1. Anyway my template seems to be working again.
Screenshot 2022-03-14 at 9.16.21 am.png

Good to hear!

[Dipe]

Hey Jürgen, thx for all your work! I am just getting my head around open stage control and i cant figure out which osc message has to be sent to trigger the next secene with a buttom. I tried /scene/+/launch and many variations but it doesnt work. As an alternative is it maybe possible that i just create a Button and map this button to the hotkey/controller maping function inside bitwig?? Thanks a lot for your help, Benjamin

[moss]

Hey Jürgen, thx for all your work! I am just getting my head around open stage control and i cant figure out which osc message has to be sent to trigger the next secene with a buttom. I tried /scene/+/launch and many variations but it doesnt work. As an alternative is it maybe possible that i just create a Button and map this button to the hotkey/controller maping function inside bitwig?? Thanks a lot for your help, Benjamin

It is currently not implemented but since there is now a selected state it is possible. Will add it to my todo list.

[Dipe]

Ohh thank you so much that would be awesome! I also wondered if it is possible to send midi cc values via virtual midi loop channels and your flexi script? i am trying to accomplish sth similar like in this video but its not working as i hoped :/

i also tried the generic controller script but it has only 1 midi in and no out

[giftmusic]

Hey Jürgen, thank you for all your hard efforts!
I have found in Bitwig 4.2 with your 16.0.x that my Yaeltex controller all push buttons (toggle/momentary) LEDs do not illuminate when pressed. Tested in Ableton (works fine). Seems like Bitwig wont send state or status to controller? I do have "send value to device" on. I have tried generic templates and even an older version of flexi. IIRC this worked fine with my controller this summer.

Have you seen this or anyone else?

[moss]

Ohh thank you so much that would be awesome! I also wondered if it is possible to send midi cc values via virtual midi loop channels and your flexi script? i am trying to accomplish sth similar like in this video but its not working as i hoped :/

i also tried the generic controller script but it has only 1 midi in and no out

That is simply not necessary since you can use pure OSC in Bitwig. See my tutorial series:
https://www.youtube.com/playlist?list=P ... okJ6SruEpq

[moss]

Hey Jürgen, thank you for all your hard efforts!
I have found in Bitwig 4.2 with your 16.0.x that my Yaeltex controller all push buttons (toggle/momentary) LEDs do not illuminate when pressed. Tested in Ableton (works fine). Seems like Bitwig wont send state or status to controller? I do have "send value to device" on. I have tried generic templates and even an older version of flexi. IIRC this worked fine with my controller this summer.

Have you seen this or anyone else?

Don't have a Yaeltex for testing but tried with a different controller and the feedback was working fine. Are you sure it accepts the same CC message as it uses for sending? Maybe you changed something?