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

[_TIP_]

Hi Moss, I bought a second hand Maschine MKII on ebay after watching your videos and I couldn't be happier with all the functionality, one thing I would really love to have though is chord mode, is there a possibility to add any possible combination to get in chord mode (it doesn't have to be a convenient combination, anything would be so welcome). Thank you for your hard work, I really appreciate it!!!

I had no real idea. Just make a suggestion.

Some suggestions:
1) double click the pad mode button
2)shift + Double click Pad mode (not sure if it's even possible)
3)shift + Scene
4)shift + pattern
5)shift + duplicate

Not sure if any of the combinations above could possibly work, just making a suggestion. Personally don't really care what the combination is as long as we get chord mode

[moss]

HI definately running into an issue with the shift button on the akai fire. it seems to lock into a shift mode somehow and turning the select knob will only change the octave. changing notes and scales stopped working during a session. I tried unplugging the fire and pluggin it back in and still no change. Pressing Alt also stopped responding. it just changed track selection. Fire also displays select a drum pad on the display constantly. And other text overlayed over it as I turned the knobs. I was working with the drum sequencer on one track then switched to another track to play notes in using the normal sequencer and everything went wonky out of nowhere. I think I entered note edit mode on the drum sequencer and then exited or switched tracks while still in that mode or something. Very undesirable result here. The only other thing i changed during the session was the velocity pad settings. I toggled a set velocity OFF then ON again and changed the constant value. Trying to figure out what broke the fire script in session.

Note edit mode is de-/activated with Alt+STEP or Alt+DRUM.

[moss]

I don't understand something: I can't control different devices using a midi keyboard separately from each other. If I have 2 tracks and I bind the first encoder to the parameter of the first synthesizer and the first encoder to the parameter of the second synthesizer - then no matter which track I select, when I turn the encoder, both bound parameters change synchronously.

How can I avoid this?

I bind it via the right mouse button "map to controller or key". (novation launchkey 25, if it matters)

If you use direct mapping it will fix the knob to the parameter. Don't do this. Read how to use remote control parameters instead, which are also available for trracks and the whole project.

[xtreme sounds]

HI definately running into an issue with the shift button on the akai fire. it seems to lock into a shift mode somehow and turning the select knob will only change the octave. changing notes and scales stopped working during a session. I tried unplugging the fire and pluggin it back in and still no change. Pressing Alt also stopped responding. it just changed track selection. Fire also displays select a drum pad on the display constantly. And other text overlayed over it as I turned the knobs. I was working with the drum sequencer on one track then switched to another track to play notes in using the normal sequencer and everything went wonky out of nowhere. I think I entered note edit mode on the drum sequencer and then exited or switched tracks while still in that mode or something. Very undesirable result here. The only other thing i changed during the session was the velocity pad settings. I toggled a set velocity OFF then ON again and changed the constant value. Trying to figure out what broke the fire script in session.

Note edit mode is de-/activated with Alt+STEP or Alt+DRUM.

HI I did deactivate note edit. There was still the glitch i mentioned.

[moss]

HI definately running into an issue with the shift button on the akai fire. it seems to lock into a shift mode somehow and turning the select knob will only change the octave. changing notes and scales stopped working during a session. I tried unplugging the fire and pluggin it back in and still no change. Pressing Alt also stopped responding. it just changed track selection. Fire also displays select a drum pad on the display constantly. And other text overlayed over it as I turned the knobs. I was working with the drum sequencer on one track then switched to another track to play notes in using the normal sequencer and everything went wonky out of nowhere. I think I entered note edit mode on the drum sequencer and then exited or switched tracks while still in that mode or something. Very undesirable result here. The only other thing i changed during the session was the velocity pad settings. I toggled a set velocity OFF then ON again and changed the constant value. Trying to figure out what broke the fire script in session.

Note edit mode is de-/activated with Alt+STEP or Alt+DRUM.

HI I did deactivate note edit. There was still the glitch i mentioned.

Please give some exact steps to reproduce the issue. I did some tests but could not reproduce it.

[xtreme sounds]

HI definately running into an issue with the shift button on the akai fire. it seems to lock into a shift mode somehow and turning the select knob will only change the octave. changing notes and scales stopped working during a session. I tried unplugging the fire and pluggin it back in and still no change. Pressing Alt also stopped responding. it just changed track selection. Fire also displays select a drum pad on the display constantly. And other text overlayed over it as I turned the knobs. I was working with the drum sequencer on one track then switched to another track to play notes in using the normal sequencer and everything went wonky out of nowhere. I think I entered note edit mode on the drum sequencer and then exited or switched tracks while still in that mode or something. Very undesirable result here. The only other thing i changed during the session was the velocity pad settings. I toggled a set velocity OFF then ON again and changed the constant value. Trying to figure out what broke the fire script in session.

Note edit mode is de-/activated with Alt+STEP or Alt+DRUM.

OK here are something to try that made it start acting strange where the select knob stopped responding to change the octave range.

1. add diva in track one play in some notes
2. add ad rum machine in track 2. Select Irrupt Modular kit 5
3. add an organ on track 3
4. switch back and forth between tracks 1 and 2 (instrument and drums) repeatedly while turning note edit on and off, while note edit is on try switching to the diva track and truning on the arp, try switching back and forth to drums again.
5. while note edit is on try switching between channel mixer user 1 user 2.
6. turn on note repeat on and off.
7. switch between tracks.
8. try plugging in a launch control xl mk2 controller at the same time using a generic flexi script.
9. try turning the select knob to change octave. try changin note scale
10. swithc between step note and drum buttons a few times

Eventually through a series of these moves you will find the akai fire break down. I was able to do it in a new session and the select knob stopped responding. BUt then after a few more presses of step note and drum buttons it came back.

One thing I see right away is text overlap in the display screen.

[isosis]

I don't believe so, i removed the old one from the config - when I do that Bitwig gives me options of the mappings to add and has both options but i just pick the Driven one, and the other is not setup in the config anywhere

I have a slightly newer firmware (which is not released). Could be that there is an incompatibility. Will check back.

Hello there, Bruno from Intuitive Instruments writing.
I have double checked with the current official firmware (2.1.1), the one you can download form our website, and everything works fine in Bitwig with DrivenByMoss version 25.5.0. and Bitwig 5.3.8.

I was up to date, today i re-updated everything now it's sort of working, it sends midi info but it doesn't seem like the controller script is actually working (settings on the device and in the controller settings are no in sync, transport doesn't work, etc) - it's at least working as well as it used to before having any controller script, but not sure what''s up here

have tried with both the built in controller and driven by moss and the behaviour is the same

[icaria36]

Hi Moss,
quick question: Does the Script support the Oxy One Mk2 al well as Mk1? If not: Any Plans for the Mk2?

Sorry, no. I would love to support this as well but OXI seems not to have DAW support in their focus currently. Get in touch with them to show your need.

Happy to post a request on their forum but before there is a detail that would be helpful to understand. Do you mean that the MK1 firmware has some enablers for DAW integration that are missing in the MK2 firmware?

I just got an MK2 and I was hoping that the same extension would work as well, at least partially, but the device won't get into controller mode at all.

[icaria36]

Never mind. Someone started a topic on the Oxi forum requesting to expand it as a MIDI controller and I just added my comment there: please make a user mode. i really want to use OXI One as a MIDI controller.

(Ah, this is my first post there and it is awaiting approval.)

[xtreme sounds]

GM i provided the akai fire steps that cause the instability. did you see it?

[User79]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

[cottontail]

Using the extension on XTouch One:
Is it possible to have zeros in the bars/beats segment display like there is when it is displaying time?

Currently the beats readout on the segment display doesn't seem to line up with the labels printed on the XTouch One (img attached).

It would also be useful if I could choose that the Tempo/Ticks button switches between beats and time. Currently it switches between ticks and tempo, but perhaps that's just a personal preference.

[quincy]

Hi Moss. Thanks for all your hard work on these controller scripts.

I've got a Push 2 and I'm trying to work out if there's a quicker way to switch between tracks when in the device view. When using Ableton Live, one row of the top buttons selects tracks and the other row of buttons selects devices in the track. With Bitwig (as far as I can tell) I have to navigate up the tree to the mix view, then select a new track, then hit device again.

In short, if I'm trying to jam/perform and switch between tracks quickly to control effects or mute/unmute them etc, it's a bit fiddly and slow.

I thought there might be a shortcut I'm missing to switch tracks but stay in the device view, or perhaps always display the track remotes but be able to switch tracks with one button press. Is there anything I might have missed? I also looked at the user view, but I still can't see how to switch tracks to show the track remotes without going back to mix view, then back to the user view again.

[moss]

HI definately running into an issue with the shift button on the akai fire. it seems to lock into a shift mode somehow and turning the select knob will only change the octave. changing notes and scales stopped working during a session. I tried unplugging the fire and pluggin it back in and still no change. Pressing Alt also stopped responding. it just changed track selection. Fire also displays select a drum pad on the display constantly. And other text overlayed over it as I turned the knobs. I was working with the drum sequencer on one track then switched to another track to play notes in using the normal sequencer and everything went wonky out of nowhere. I think I entered note edit mode on the drum sequencer and then exited or switched tracks while still in that mode or something. Very undesirable result here. The only other thing i changed during the session was the velocity pad settings. I toggled a set velocity OFF then ON again and changed the constant value. Trying to figure out what broke the fire script in session.

Note edit mode is de-/activated with Alt+STEP or Alt+DRUM.

OK here are something to try that made it start acting strange where the select knob stopped responding to change the octave range.

1. add diva in track one play in some notes
2. add ad rum machine in track 2. Select Irrupt Modular kit 5
3. add an organ on track 3
...

I tried the tests you suggested.
What I noticed is that you cannot switch tracks when:
- USER1 or USER 2 is active
- When note edit mode is active
but this is intentional.

[moss]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.