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

[nuancesdengrais]

Hello,

Zunächst einmal danke ich Ihnen für Ihre Arbeit und Ihre Zeit, es ist wirklich ein großartiges Werkzeug, und diese Arbeit bringt viel.

I'm writing here because I haven't found a solution to what I'm doing.

Or I haven't figured out how to do it. =)

The first question is perhaps less specific to your extension.

I'm preparing a live set, with Bitwig, using a faderfox, UC4 and Touch OSC, with Drivenbymoss, and Flexi.
So far, so good.

But there are some things I can't do. I'd like to have an instrument selector, which would work with midi. First of all, I wanted it to be connected to the selector track. But it could only be a fader or a button on the touchscreen. I tried several solutions.

But I couldn't find a clean and pleasant way of doing it.

I tried direct mapping, a fader “radio” type controller, controlled from the CCs and sent back to the track. Ideally, I'd change with a fader the precet instrument or fx on the selected track.

My question, about more the extensions :

I'm using a faderfox, UC4 in Flexi mode. And I've assigned the buttons 1-8, in CC for changed track, track 1 to 8. This works well, but now I'd like to have feedback on the LEDs, to know which track is selected. That would be great.

Chatgpt wrote me a script for that, but I don't know where to find it or how to use it, or even what I wrote would work.

And, I also tried to use grid, for that but I couldn't find a way to get what I wanted to have.


vielen Dank un schönen Feierabend ,

Mfg,

[moss]

Hello,

Zunächst einmal danke ich Ihnen für Ihre Arbeit und Ihre Zeit, es ist wirklich ein großartiges Werkzeug, und diese Arbeit bringt viel.

I'm writing here because I haven't found a solution to what I'm doing.

Or I haven't figured out how to do it. =)

The first question is perhaps less specific to your extension.

I'm preparing a live set, with Bitwig, using a faderfox, UC4 and Touch OSC, with Drivenbymoss, and Flexi.
So far, so good.

But there are some things I can't do. I'd like to have an instrument selector, which would work with midi. First of all, I wanted it to be connected to the selector track. But it could only be a fader or a button on the touchscreen. I tried several solutions.

But I couldn't find a clean and pleasant way of doing it.

I tried direct mapping, a fader “radio” type controller, controlled from the CCs and sent back to the track. Ideally, I'd change with a fader the precet instrument or fx on the selected track.

My question, about more the extensions :

I'm using a faderfox, UC4 in Flexi mode. And I've assigned the buttons 1-8, in CC for changed track, track 1 to 8. This works well, but now I'd like to have feedback on the LEDs, to know which track is selected. That would be great.

Chatgpt wrote me a script for that, but I don't know where to find it or how to use it, or even what I wrote would work.

And, I also tried to use grid, for that but I couldn't find a way to get what I wanted to have.


vielen Dank un schönen Feierabend ,

Mfg,

Not sure if I fully understood what you are trying to achieve. If you want to switch sounds in an instrument selector, the easiest way is to enable program changes for it and program your controller to send program changes.

[nuancesdengrais]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Super thanks, I'll try that for the selector instrument.

I'm Sorry if my message wasn't clear. I'm currently spending the night on bitwig.

2)
The other thing I'm trying to do:
It's to have a Led feedback, on the green buttons of the UC4, on the selected track.
Each button is assigned to a track 1-8. But I'd like to have Led feedback on which track is selected.

The idea, would be. When a track is selected that would send back the corresponding CC message to the controller.

3)
The 3rd thing I'm looking at, this time it's with the EC4. The poteniometter are assigned to the track controllers and I'd like to have the text, if possible, of what's being controlled. And that it changes when I select another track.

Is this possible?


Thank you a lot

Translated with www.DeepL.com/Translator (http://www.DeepL.com/Translator) (free version)

[moss]

Super thanks, I'll try that for the selector instrument.

I'm Sorry if my message wasn't clear. I'm currently spending the night on bitwig.

2)
The other thing I'm trying to do:
It's to have a Led feedback, on the green buttons of the UC4, on the selected track.
Each button is assigned to a track 1-8. But I'd like to have Led feedback on which track is selected.

The idea, would be. When a track is selected that would send back the corresponding CC message to the controller.

With Generic Flexi this does only work if the LED is lit with exactly the same command as the related button is using, e.g. if the button sends CC 20 with data 127 on press and 0 on release, the LED needs to be lit with CC 20 as well and turned on with data 127 and turned off with data 0.

3)
The 3rd thing I'm looking at, this time it's with the EC4. The poteniometter are assigned to the track controllers and I'd like to have the text, if possible, of what's being controlled. And that it changes when I select another track.

Is this possible?

Not with Generic Flexi but if you use my EC4 implementation:

[Hongaki]

Hello Moss, thank you for your tremendous work , been using your Bitwig extensions for years , they are a blast !

I recently switched on Arch Linux , I guess it's a bit out of scope , but since my Akai Apc 25 is recognized I tought Gamepads would be too , but they're not for some obscure reasons (my OS is ok with it , it's only inside of Bitwig that I encounter this problem ...)
Do you have any ideas how I could troubleshoot this ?

Many thanks , and long live Jurgen !

[SIL3NC3_SWX]

Hi Moss,
is AKAI MPK 261 support planned?

//SiL

[moss]

Hello Moss, thank you for your tremendous work , been using your Bitwig extensions for years , they are a blast !

I recently switched on Arch Linux , I guess it's a bit out of scope , but since my Akai Apc 25 is recognized I tought Gamepads would be too , but they're not for some obscure reasons (my OS is ok with it , it's only inside of Bitwig that I encounter this problem ...)
Do you have any ideas how I could troubleshoot this ?

Many thanks , and long live Jurgen !

Game pads are tricky and I am afraid I cannot support with that issue.

[moss]

Hi Moss,
is AKAI MPK 261 support planned?

//SiL

No. But Generic Flexi should get you pretty far with this device.

[xtreme sounds]

hi still a workflow issue on the fire. trying to switch scales and every time I press shift it goes to the arp screen so everytime I press shift and left or right grid arrows to change scale I have to press shift again to go back the the piano pads. It just isnt like it used to be

[moss]

hi still a workflow issue on the fire. trying to switch scales and every time I press shift it goes to the arp screen so everytime I press shift and left or right grid arrows to change scale I have to press shift again to go back the the piano pads. It just isnt like it used to be

Yeah, it is not perfect. But that's how it is for reasons.

[moss]

DrivenByMoss 24.6 is online!

Get it from https://mossgrabers.de

• Fixed: Browser could crash.
• Fixed: Scrolling items (e.g. tracks) left could jump in steps of 8. Side effect from the change that the 1st instead of the last item is selected when changing a page backwards.
• Maschine JAM
  • Fixed: When holding down Grid button in step sequencer mode, the group/channel buttons A-H did not reflect the available resolution options. Furthermore, the number of selectable resolutions was coupled to the number of tracks in the project.
• MCU
  • Fixed: Changed VU meter range (when Mackie is selected) to 0-12 instead of 0-13.
• OXI One
  • New: Added DrumXoX sequencer (press Arrange button twice).
  • New: Added the Raindrop sequencer (press Sequencer button 4 times).
  • New: Added automation mode (press Shift+MOD buttons).
  • New: Mixer mode: press Shift+track pads to stop the playing clip of the track.
  • Fixed: Drum 128 was named Drum 64 in the startup view setting.
• Push 1
  • Fixed: Notify played chords feature did halt other display updates.

Enjoy!

[jwex1000]

Hello,
Love all the work you do!

I just installed the latest and am having two issues:
1. All my controllers are following each other now. For example, even when I turn off follow in the settings, my launchxl moves the track window, and then my apc 40mkII also moves. There does not seem to be a way to stop this. Normally, i keep my apc 40 on the first 8 tracks then my launch control on track 9-16.
2. Device locking on the Akai Fire (one of my favorite features), no longer seems to work. While the display locks and it looks like the track locks, it doesn't work. For example, I want to lock the fire to a track, but when I click on another track and hit notes on the fire, it sends the notes to the other track.

Hope this makes sense and am happy to elaborate.

[moss]

Hello,
Love all the work you do!

I just installed the latest and am having two issues:
1. All my controllers are following each other now. For example, even when I turn off follow in the settings, my launchxl moves the track window, and then my apc 40mkII also moves. There does not seem to be a way to stop this. Normally, i keep my apc 40 on the first 8 tracks then my launch control on track 9-16.
2. Device locking on the Akai Fire (one of my favorite features), no longer seems to work. While the display locks and it looks like the track locks, it doesn't work. For example, I want to lock the fire to a track, but when I click on another track and hit notes on the fire, it sends the notes to the other track.

Hope this makes sense and am happy to elaborate.

I didn't change anything with this. Can you please check if track lock state is correct in Bitwig (in the drop down controller window). Is this with the Beta version?

[jwex1000]

Hi, I am running version 24.6 of your script and am on Bitwig version 5.2.7. It does say Beta when i look at the controller page for fire (see screen shot). I am not sure i understand how to check track lock state. Looked everywhere for it in the setting but i cant find it. i have tried playing with the toggle on "scrolls visable content" but nothing seems to help. Tried deleting the main script file and reinstalling but still not working.

Thanks again for your help

[menelik]

Hi,
I just installed version 24.6.0 for my Maschine Mikro MK3.
Bitwig 5.2.5 gives me an Input Error: Maschine Mikro Mk3 could not open midi input, external error

Thank you for your attention

best regards

Alessandro