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

[xtreme sounds]

Hey folks I found something that these scripts cannot do and Bitwig cannot do but I found a solution to how to assign a midi channel input to a hardware controller. the solution is simple. download Pizmidi and grab the Midi channelize vst. No more using the mouse to select the input channel in the inspector panel for your hardware. ALL to Same will not work if you want to use a midi controller to play in notes. It will not switch the sound. So this plugin is helpful for users of Elektron gear, Yamaha gear, Roland gear, really anything that has more than one sound on different midi channels. I had to post it here so everyone can benefit.

[PopDV]

These buttons and knobs are not part of the MCU protocol. Question is what they send (or maybe it is configurable), you need to check their manual.

Since this device has no display, I suggest that you use Generic Flexi instead which allows you to configure everything, e.g. you could set these knobs to control parameters.

X Touch Compact in MMC mode
Select button of Master Fader >> 50 CC
A layer B >> 84 CC - 85 CC
rotating knobs 9-14 (push action) >> 40 CC - 45 CC
rotating knobs 15-16 (push action) >> no data

[xtreme sounds]

HI I am using the generic flexi script with the digitakt. Why do the midi tracks not send any note values using the pads? Do I have to program them one by one for all tracks or something? I can send you my script preset if you want to review. I programmed the 8 knobs to work on any device remote control pages. that part is working. but I cannot record notes in using the script.

[MarcusRoelofs]

Hi all,

Is there a way to reset the whole controller list and start over again with a clean setup? I have looked everywhere and was even close to deleting registry entries (Windows 11) but that seemed too risky atm.

I am using Moss's scripts for an NI Maschine Mikro Mk3 and a Arturia Beatstep. When they work all is fine, but somehow I messed up things.
I like to experiment with different setups, specifically for the Beatstep, maybe also using the default config.
But the problem is that Bitwig does weird things when removing controllers ie. it doesn't remove them. Some older controller entries keep showing up and the input mapping is very confused by now. Maybe I did something wrong somewhere along the learning curve.

Thanks in advance for any help.

[moss]

HI I am using the generic flexi script with the digitakt. Why do the midi tracks not send any note values using the pads? Do I have to program them one by one for all tracks or something? I can send you my script preset if you want to review. I programmed the 8 knobs to work on any device remote control pages. that part is working. but I cannot record notes in using the script.

I am not familiar with the Digitakt. Check if the pads and the knobs are on the same MIDI port (Generic Flexi can only handle one MIDI port). Also check their MIDI channel. Make sure that the MIDI channel matches the one you have selected in the Keyboard section (or set it to All) -> restart is required to make it effective.

[moss]

Hi all,

Is there a way to reset the whole controller list and start over again with a clean setup? I have looked everywhere and was even close to deleting registry entries (Windows 11) but that seemed too risky atm.

I am using Moss's scripts for an NI Maschine Mikro Mk3 and a Arturia Beatstep. When they work all is fine, but somehow I messed up things.
I like to experiment with different setups, specifically for the Beatstep, maybe also using the default config.
But the problem is that Bitwig does weird things when removing controllers ie. it doesn't remove them. Some older controller entries keep showing up and the input mapping is very confused by now. Maybe I did something wrong somewhere along the learning curve.

Thanks in advance for any help.

No need for the registry. All Bitwig settings are kept in
C:\Users\<YOUR_USER_NAME>\AppData\Local\Bitwig Studio\prefs
If there are no settings for the current version you are running, Bitwig takes the settings from the most current prefs file it can find. To start clean move all these files out of the folder.

[MarcusRoelofs]

Thank you for your help.
Btw I'm in awe about all the work you do for this community, it's very valuable to many people. Is there some way you are, or can be compensated for all this goodness?

[moss]

Thank you for your help.
Btw I'm in awe about all the work you do for this community, it's very valuable to many people. Is there some way you are, or can be compensated for all this goodness?

There is a THANKS button below each video on my Youtube channel.

[Pirapsy]

Hi Juergen. Im using the Push 2 with your beautiful script and I wanted to mention a weird behavior with the latest of your extensions. Button Add Device opens Presets to replace an existing device instead of Add Device: Add a device after the currently selected one. And Browse button does the same thing none of them adds next to last selected device.
You may include some future adjustments: in the browser the colums are too many and we can read most of the times half of the words caused by narrow space. The colored pads aren't that warm colored in compare when using push with Ableton they are kinda too white to say and this happens with native color pallets and custom they are not matching with each other Color pallets and push 2 buttons . Not sure if this fixable. Thank you in advance and guten rutsch ins Neue Jahr

[moss]

Hi Juergen. Im using the Push 2 with your beautiful script and I wanted to mention a weird behavior with the latest of your extensions. Button Add Device opens Presets to replace an existing device instead of Add Device: Add a device after the currently selected one. And Browse button does the same thing none of them adds next to last selected device.

Select + Browse does that. But I noticed that the 'Add Device' behaviour does work not as described in the manual. Will be fixed in the next update.

You may include some future adjustments: in the browser the colums are too many and we can read most of the times half of the words caused by narrow space. The colored pads aren't that warm colored in compare when using push with Ableton they are kinda too white to say and this happens with native color pallets and custom they are not matching with each other Color pallets and push 2 buttons . Not sure if this fixable. Thank you in advance and guten rutsch ins Neue Jahr

The configured color palette in Bitwig cannot be retrieved, therefore the Push 2/3 also use the color palette as implemented with Push 1.

[Pirapsy]

Thank you for answering that fast. I hope it'll be an easy fix. Some darker colors from the pallet appearing grey or white in the Push that's what I've meant. Thank you thank you thank you

[jwex1000]

Hi, I am having very odd behavior with my Push 3. I work with a lot of nested devices and when I click on different banks pages, it will often bring me back up a level without me wanting it to happen. Here is a video of it happening.

Happy to provide any other details that might be useful

[moss]

Hi, I am having very odd behavior with my Push 3. I work with a lot of nested devices and when I click on different banks pages, it will often bring me back up a level without me wanting it to happen. Here is a video of it happening.

Happy to provide any other details that might be useful

That's a feature. If you press the button longer it brings you up one level. So, don't press it too long

[jwex1000]

Woah. Thanks so much for the response and sorry for the (what now seems like) a silly question.

[moss]

DrivenByMoss 24.7 is online!

Get it from https://mossgrabers.de

• New: Note/Chord notification is now off by default.
• OSC
  • New: Added insertFile commands: /track/{1-8}/clip/{1-8}/insertFile and /clip/insertFile
• OXI One, Push
  • New: Enabling edit mode and selecting notes for editing has now been harmonized across all sequencers:
    • Long press a pad which contains a note to activate the note edit mode and edit the parameters of the note (or all notes at that step in case of Poly Sequencer).
    • When the note edit mode is active, press the pads which contain notes to select them for editing or remove them from editing.
    • Multiple notes can be de-/selected for editing by using the select button in combination with a sequencer note pad as well.
    • When the last note is deactivated for editing, the note edit mode is closed.
    • Pressing a pad which does not contain a note closes the edit mode as well.
    • Pressing a pad which does contain the continuation of a note, does nothing.
• Push
  • New: Added options to configure the behaviour of the cursor keys for scrolling tracks and scenes.
  • Fixed: 'Add Device' and 'Shift+Add Device' did not work as expected.

Enjoy!