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

[catzilla]

I am about to fix this but this needs some intense testing and being at it, I will also need to support the new "sends can have sends" feature of Bitwig 4.3.

Let me know if I can assist with that somehow. I can pull a git branch with the fix and build the extension myself and test it out.

[moss]

I am about to fix this but this needs some intense testing and being at it, I will also need to support the new "sends can have sends" feature of Bitwig 4.3.

Let me know if I can assist with that somehow. I can pull a git branch with the fix and build the extension myself and test it out.

It is now checked in, if you want to take a look. You can now also access more than 8 sends by pressing the button multiple times. Sends of FX channels cannot be implemented right now, it is missing in the API.

[catzilla]

It is now checked in, if you want to take a look. You can now also access more than 8 sends by pressing the button multiple times.

Wow, you are amazing, Jürgen! Can't even express how grateful I am. Everything's working as expected. My usual sends/returns workflow which I got accustomed to in Ableton Live is now avaialble to me in the Bitwig/Push combo as well and in fact it's even better as Bitwig has no return tracks number limit. Thanks again. You totally saved me.

[israeljameshunter]

hello, I recently downloaded the most up to date version of Divenbymoss 17. and I'm running Bitwig 4.0.8. I can't seem to find the MCU setting under the controller hardware heading. I'm trying to run the AudioSwift software and Keith mcmillen softstep2 ..neither register even with the extension installed. any tips?

[moss]

hello, I recently downloaded the most up to date version of Divenbymoss 17. and I'm running Bitwig 4.0.8. I can't seem to find the MCU setting under the controller hardware heading. I'm trying to run the AudioSwift software and Keith mcmillen softstep2 ..neither register even with the extension installed. any tips?

Version 17 requires Bitwig 4.3

[xtreme sounds]

thanks again for the akai fire script update. I guess the only thing missing is the the operators on the drum machine.

Oh one more thing. Could we have an option that pressing just the record button goes to overdub record mode instead just record? This is for live playing in notes and repeats. I know shift plus record does it, but it would be easier to just press the record button. Actually Im not sure what just pressing the record button does on a current clip. Maybe just revisiting what the shift and alt combos do with transport controls would be useful.

[n0j0e]

Anyone here with an Akai MPK Mini 3 and willing to share the DrivenByMoss script to see whats possible. I have the feeling i miss something of my script, to much possibilities

[x.iso]

I am afraid this is not possible. Even if I would use a "fake" MIDI port, the generated CCs do somehow not qualify for mapping in Bitwig.

I'm pretty certain that using HW instrument to send to midi port that then uses generic controller script is enough to be able to map CC's from that generic controller script. at least I was certainly able to use modulation to global CC mapping this way (although I haven't tried it for shortcuts). well then I'll be using this roundabout method if there's no other option.

Noted.

Would be curious to see what you are doing with this. Any videos?

I only have example of use case for when I made a CV/Gate patchbay out of gamepad controls in Usine. https://cdn.discordapp.com/attachments/ ... 31-072.mp4 (probably need to open it in new tab)
But I was basically making same thing in Grid, just stumbled on this X/Y joystick limitation.


Big idea I had with this patchbay is just using CC's for all controls and then using logic to create various setups with some buttons acting as mode shifts, where it will remap what CC other controls will output, maybe even process the curve, etc. This way it would be possible to even shift between 'pages' of different mappings with shoulder buttons for example, so you could switch between controlling instrument, tracks, FX and whatever you need for live performance. Or for instance for FX processing page you could have A,B,X,Y as 'focus' buttons for left stick and arrows for right stick, so you basically choose which effect to apply with holding buttons and use X/Y to apply amounts of relevant FX parameters. Lots of possibilities for a hand held controller if you include contextual mode switching like that.

[moss]

thanks again for the akai fire script update. I guess the only thing missing is the the operators on the drum machine.

Oh one more thing. Could we have an option that pressing just the record button goes to overdub record mode instead just record? This is for live playing in notes and repeats. I know shift plus record does it, but it would be easier to just press the record button. Actually Im not sure what just pressing the record button does on a current clip. Maybe just revisiting what the shift and alt combos do with transport controls would be useful.

There's already the option "Flip arranger and clip record".

[auricle]

Hi, just a sanity check. In Driven By Moss version 17, it's no longer possible to set note operators from the Akai Fire?

[moss]

Hi, just a sanity check. In Driven By Moss version 17, it's no longer possible to set note operators from the Akai Fire?

This was never supported (maybe you confuse it with Ritchies script).

[moss]

DrivenByMoss 17.1.0 is out!

Get it from https://mossgrabers.de

NOTE: Remove your DrivenByMoss devices after updating and add them again to clean up the settings! (sadly, still a Bitwig bug).

• All
  • New: Only color existing session slots red (for which a scene exists) for recording.
• Fire
  • Fixed: Knobs did not work after leaving note edit mode.
• MCU
  • Fixed: Touch state for touch automation recording was not always set correctly.
• Push
  • New: Push 2: The 4th button above the display now moves to the next sends page. Combine with Shift to move backwards.
  • Fixed: Internal Drum Machine Sends were not handled correctly.
  • Fixed: Do not switch to drum channel when browser is open (when playing pads).
  • Fixed: Push 1: Layer panorama mode - value bars were not setup as panorama.
  • Fixed: Push 1: Layer send modes could not be accessed.
• APC40, APCmini, Launchpad, Launchkey Mini, Maschine, Maschine Mikro, Maschine JAM, Push
  • New: Renamed 'Behaviour on Play' to 'Behaviour on Pause' and renamed the options as well.
• Fire, Force, HUI, Kontrol mkI/II, Launchkey, MCU, MPC, SLmkII/mkIII
  • New: Added additional setting 'Behaviour on Pause' triggered by play button.

Enjoy!

[xtreme sounds]

Hi sir. Im trying to use the flexi mode. How do I assign a pad so that it selects the track but also the device so that it has focus to control the device page knobs after pressing the button. Do I select option track select or something under device? Do I set up midi cc values or something else?

[moss]

Hi sir. Im trying to use the flexi mode. How do I assign a pad so that it selects the track but also the device so that it has focus to control the device page knobs after pressing the button. Do I select option track select or something under device? Do I set up midi cc values or something else?

Bitwig automatically selects the previously selected device of a track when the track is selected again. So, there is no need to additionally select a device.
To navigate devices of the track you can either use the specific Device commands or the Modes (item select).

[xtreme sounds]

Hi sir. Im trying to use the flexi mode. How do I assign a pad so that it selects the track but also the device so that it has focus to control the device page knobs after pressing the button. Do I select option track select or something under device? Do I set up midi cc values or something else?

Bitwig automatically selects the previously selected device of a track when the track is selected again. So, there is no need to additionally select a device.
To navigate devices of the track you can either use the specific Device commands or the Modes (item select).

Thanks. I like this flexi thing. Any way to change the lights and pads color using flexi? Also is there a tutorial how to setup flexi modes?
Also for some reason I am getting a midi note sound trigger assigning toggle mute to a pad on the launch control xl. to stop that from happening I have to change the Type from Note to cc and then back to note. then the sound stops.

Also I want to assign a button to selecting the send tracks only. so that I can quickly change parameters using knobs if needed. I tried selecting FX track and that doesnt seem to work.