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

[gExpectations]

Oh good to know, I kind of misunderstood that you can control devices from one of the videos.

[xtreme sounds]

HI sir

I have a feature request for the Akai fire. When we move it to chromatic mode, it would be nice if under settings we could specify a default Layout (I like 8th up) . Also can we get a drum layout mode for use even without the drum machine loaded? Maybe like the 8th up layout but in a 4 by 4 grid. that would be really useful as well when working with other drum vsts.

You can configure this in the document settings. Simply store it in your project template.

Thanks I normally use the scale modes but somethimes need the chromatic mode. I dont see wa way to switch to a default layout for chromatic mode. It stays on whatever layout Im using for the scale mode. does the 4 by 4 drum pads mode work for other instruments? I need a chromatic scale on the 4 by 4 drums

[wvshpr]

I've experimented a bit with the footswitch input of the Push 2 to start the recording of a new clip in the launcher. Unfortunately when recording a new audio clip it creates a new clip, but does not record anything and mutes the input. With MIDI tracks it seems to work. Is this expected behavior?

Which function are you using? If you use "New clip", this works only with MIDI.

Do you know why this limitation to MIDI clips exist? It's such a head scratcher that it doesn't work with audio clips

[moss]

HI sir

I have a feature request for the Akai fire. When we move it to chromatic mode, it would be nice if under settings we could specify a default Layout (I like 8th up) . Also can we get a drum layout mode for use even without the drum machine loaded? Maybe like the 8th up layout but in a 4 by 4 grid. that would be really useful as well when working with other drum vsts.

You can configure this in the document settings. Simply store it in your project template.

Thanks I normally use the scale modes but somethimes need the chromatic mode. I dont see wa way to switch to a default layout for chromatic mode. It stays on whatever layout Im using for the scale mode. does the 4 by 4 drum pads mode work for other instruments? I need a chromatic scale on the 4 by 4 drums

The drum sequencer can only work with the Drum Device. Instead use the note sequencer (press STEP). This sequencer also respects the scale settings but you need to change them from the play mode (press NOTE), since I ran out of button combinations in the note sequencer.

[moss]

I've experimented a bit with the footswitch input of the Push 2 to start the recording of a new clip in the launcher. Unfortunately when recording a new audio clip it creates a new clip, but does not record anything and mutes the input. With MIDI tracks it seems to work. Is this expected behavior?

Which function are you using? If you use "New clip", this works only with MIDI.

Do you know why this limitation to MIDI clips exist? It's such a head scratcher that it doesn't work with audio clips

Since there is now audio comping with take recording, it should not be that hard to implement.
Feel free to send a wish to Bitwig support.

[moss]

DrivenByMoss 16 is out!

Get it from http://mossgrabers.de

• New: Support for Gamepads!
• Launchpad:
  • New: Improved the 4 step change of virtual faders on already lit pads. It changes now the direction when the maximum or minimum value of the pad is reached instead of wrapping around.

Enjoy!

[mtelesha]

Cubase 12 New Controller Script is so good. I hope that Bitwig will start pushing the envelope interms of Controller Scripting.

[ayzel]

hi Jürgen I would like to see support for native instruments komplete controls 25 in Bitwig not in the demo version. Is there any further work planned on this controller?
Thank you in advance

[moss]

Cubase 12 New Controller Script is so good. I hope that Bitwig will start pushing the envelope interms of Controller Scripting.

So far, I am not impressed at all. At first sight it looks nice with this auto-creation of widgets but the features are still pretty similar to what was there with the Generic Control since ages. The supported devices are pretty limited and not one with a display. Didn't have time yet to check out the API in detail but AFAIK there seem to be no sequencers.

[moss]

hi Jürgen I would like to see support for native instruments komplete controls 25 in Bitwig not in the demo version. Is there any further work planned on this controller?
Thank you in advance

Not sure what you are asking for. All Komplete Kontrol models are supported by DrivenByMoss.

[mtelesha]

Cubase 12 New Controller Script is so good. I hope that Bitwig will start pushing the envelope interms of Controller Scripting.

So far, I am not impressed at all. At first sight it looks nice with this auto-creation of widgets but the features are still pretty similar to what was there with the Generic Control since ages. The supported devices are pretty limited and not one with a display. Didn't have time yet to check out the API in detail but AFAIK there seem to be no sequencers.

I should have qualified what I was impressed with. The gui and the widgets. So just the looks. This is still behind in terms of API in Bitwig 1.

[Alban18]

Hey Moss,

I have an M-audio Oxygen Pro that I'd like to configure with your script. So far, I followed your instructions and I'm currently trying to configure it with Flexi script. So far, the only configuration that kinda works for me in "MIDIIN3 (Oxygen Pro 49)" for the input and "Oxygen Pro 49" for the output.

Now the problem is most of my buttons don't auto detect. Okay fine, but now when I try to find the midi cc number for let's say metronome, I can't find where the cc number is even with the labels.

Then the second problem which may even be a bigger problem, the play button was auto detected by the flexi script and I'm able to assign that to the Transport: play button. But the problem is that the play button was auto assigned to "93 CC Effect 3 Depth - Celestial [Detuned] Depth". Which tells me that even if I wanted to manually assign my midi, the midi cc isn't even labeled correctly.

If you can help me out that'll be great. Is the m-audio even possible to configure with your scripts?

[Tj Shredder]

If you want to auto detect a cc, but the button plays a note, it might not work…
The labels are those, a long time ago the Midi association defined. In the real world its just a number…
You should always have a Midi monitor in your toolbox. Then you know what your controller spits out. It could also be some more complex Midi command like sysex or it uses the HUI protocol. Did you try the HUI script? (I bet it will work, as I just googled Oxygen HUI… And never underestimate the reading of a manual…)

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

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