DrivenByMoss: Support for many hardware controllers (version 21.2.0)

[themixtape]

Thanks! Great work, as always.

[themixtape]

Originally Posted by moss

Yes. If it is not detected, simply add it manually.

Hi Moss! This isn't possible.

Trying to use X-Touch One and X-Touch together.

The error I get, when trying to add manually...

"Only one instance of a controller type is supported!"

So it seems I can't use two Mackie Control Universal type. Correct me if I'm wrong, as you said it was possible. Thanks!

[themixtape]

Also! Something I discovered which I do believe you changed... did you set the jogwheel for the X-Touch / X-Touch One to jog by bars now, instead of time? I don't know when this was updated, but I noticed it's by bar. I LOVE THAT. That is how I prefer to jog, instead of "a few seconds" which is the MCU default.

Thanks so much man!

[themixtape]

Behringer being annoying again.

Ok.. Moss, any idea why sometimes, the X-Touch One bugs out?

Issues:
1. When I move tracks (< Channel, Channel >), I don't see the track being selected in Reaper. Likewise, when using the down/up pad (the Zoom thing, when Zoom is not engaged, which lets me change tracks "vertically" (I like this a lot), it then DOES show the highlighted track in Reaper, but the screen on the X-Touch One doesn't follow, nor does the fader position reflect the track volume.
2. Selecting a track with the mouse-- nothing happens with the X-Touch One. It just shows the track I last navigated to, using Channel < or >.
3. Sometimes "SOLO" (in the Transport section) acts as "Save Project As" (????)
4. Sometimes F6 turns the metronome on/off, instead of changing the record mode. The "CLICK" button should be Metronome On/Off.
5. Function buttons were automation modes... (F1-F5).

I have X-Touch One set to MC Reap, mode-wise, which has been working fine.

Unplugging unit, disconnecting the USB cable.. then restarting Reaper... nothing helps. Sometimes it just gets "stuck" in this "dumb mode"... I've had it happen before, out of nowhere.

Yes, in the DBM config, it's set to the X-Touch One in port, and out port. Yes, it's using the X-Touch One preset.

I changed nothing, just walked away from the computer for a few hours.

This happened years ago when I owned the One for the first time (2019).

When people say it's not behaving right... yeah. It isn't... and it just happens out of nowhere, truly.

I'm on the latest firmware, 1.10, and the latest DBM, and the latest Reaper version.

Everything was fine, now it isn't.

I guarantee it will fix itself tomorrow.

Has anyone else experienced this? Anyone know the reason why it happens out of nowhere?

Thank you so much.

EDIT / IMPORTANT: I changed the mode to MC Standard. Problems went away. VERY weird. It's gotta be some glitch inside the X-Touch One. I remember changing the mode to get it working like normal.... bizarre. Anyone with a One--- if you notice weird behavior, change the mode. Everything is 100% working as normal now... Click is Metronome On/Off, down/up (Zoom) change the track (it's slightly slower than Channel < > but I like the up/down thing more than left/right), Clicking the track in Reaper reflects the change on the One... etc.

[kicsiobi]

Hi!
I moved to Reaper because of the x-touch support by Moss. Thank you very much for making this wonder!
I tried to install 2 X-Touch extenders with one main X-Touch. The USB connected modules din't work with drivenbymoss, and the interface froze. I have(had) to restart the pc, because some elements were in the RAM yet.
The solution: I connected all of the units via rtpMIDI. It works, so I am very happy now.
An issue: the scribble strips are showing nothing in the units 1 and 3 (extender), only in the main module. I see only colors, nothing more.
Thank you!
(AMD Ryzen, Win10)

[moss]

Originally Posted by themixtape

Hi Moss! This isn't possible.

Trying to use X-Touch One and X-Touch together.

The error I get, when trying to add manually...

"Only one instance of a controller type is supported!"

So it seems I can't use two Mackie Control Universal type. Correct me if I'm wrong, as you said it was possible. Thanks!

You are right. I forgot about this restriction of the Reaper version.

What you can do is either use one of the other MCU imeplementations for Reaper with the One or map it with Generic Flexi.

[moss]

Originally Posted by themixtape

Behringer being annoying again.

Ok.. Moss, any idea why sometimes, the X-Touch One bugs out?

Issues:
1. When I move tracks (< Channel, Channel >), I don't see the track being selected in Reaper. Likewise, when using the down/up pad (the Zoom thing, when Zoom is not engaged, which lets me change tracks "vertically" (I like this a lot), it then DOES show the highlighted track in Reaper, but the screen on the X-Touch One doesn't follow, nor does the fader position reflect the track volume.
2. Selecting a track with the mouse-- nothing happens with the X-Touch One. It just shows the track I last navigated to, using Channel < or >.
3. Sometimes "SOLO" (in the Transport section) acts as "Save Project As" (????)
4. Sometimes F6 turns the metronome on/off, instead of changing the record mode. The "CLICK" button should be Metronome On/Off.
5. Function buttons were automation modes... (F1-F5).

I have X-Touch One set to MC Reap, mode-wise, which has been working fine.

Unplugging unit, disconnecting the USB cable.. then restarting Reaper... nothing helps. Sometimes it just gets "stuck" in this "dumb mode"... I've had it happen before, out of nowhere.

Yes, in the DBM config, it's set to the X-Touch One in port, and out port. Yes, it's using the X-Touch One preset.

I changed nothing, just walked away from the computer for a few hours.

This happened years ago when I owned the One for the first time (2019).

When people say it's not behaving right... yeah. It isn't... and it just happens out of nowhere, truly.

I'm on the latest firmware, 1.10, and the latest DBM, and the latest Reaper version.

Everything was fine, now it isn't.

I guarantee it will fix itself tomorrow.

Has anyone else experienced this? Anyone know the reason why it happens out of nowhere?

Thank you so much.

EDIT / IMPORTANT: I changed the mode to MC Standard. Problems went away. VERY weird. It's gotta be some glitch inside the X-Touch One. I remember changing the mode to get it working like normal.... bizarre. Anyone with a One--- if you notice weird behavior, change the mode. Everything is 100% working as normal now... Click is Metronome On/Off, down/up (Zoom) change the track (it's slightly slower than Channel < > but I like the up/down thing more than left/right), Clicking the track in Reaper reflects the change on the One... etc.

The controllers which provide only one channel but use the MCU protocol use a very bad hack to make this work (since MCU is designed for 8 tracks!). So, what they do (if I remember correctly) is move the page window and show the first track. And there might be situations were this screws up...

[moss]

Originally Posted by kicsiobi

Hi!
I moved to Reaper because of the x-touch support by Moss. Thank you very much for making this wonder!
I tried to install 2 X-Touch extenders with one main X-Touch. The USB connected modules din't work with drivenbymoss, and the interface froze. I have(had) to restart the pc, because some elements were in the RAM yet.
The solution: I connected all of the units via rtpMIDI. It works, so I am very happy now.
An issue: the scribble strips are showing nothing in the units 1 and 3 (extender), only in the main module. I see only colors, nothing more.
Thank you!
(AMD Ryzen, Win10)

Make sure you set the Extender type (in the DrivenByMoss MCU configuration dialog) to "Mackie Extender".
I was not aware that this is possible via RTP, so this could also be an issue.

[politcat]

how do you save parameter mappings to open with every instance of a plugin?

thanks!

[moss]

Originally Posted by politcat

how do you save parameter mappings to open with every instance of a plugin?

thanks!

Should happen automatically. What is your OS? File(s) should be in the same folder as the Reaper configuration files (and all other DrivenByMoss configuration files).

[politcat]

windows 10

what's all this:

Loading device INI files from C:\Users\...
reaper-clap-win64.ini not present (this is not an error!).
reaper-fxfolders.ini not present (this is not an error!).
Ableton Push 2: Starting...
Ableton Push 2: Running.
Resending color palette entry #110 request.
Resending color palette entry #111 request.
Resending color palette entry #112 request.
Resending color palette entry #113 request.
Resending color palette entry #28 request.
Resending color palette entry #55 request.
Failed reading color palette entry #78. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #102. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #126. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #8. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #8. Gave up after 10 retries. Check selected MIDI in-/outputs.

[moss]

Originally Posted by politcat

windows 10

what's all this:

Loading device INI files from C:\Users\...
reaper-clap-win64.ini not present (this is not an error!).
reaper-fxfolders.ini not present (this is not an error!).
Ableton Push 2: Starting...
Ableton Push 2: Running.
Resending color palette entry #110 request.
Resending color palette entry #111 request.
Resending color palette entry #112 request.
Resending color palette entry #113 request.
Resending color palette entry #28 request.
Resending color palette entry #55 request.
Failed reading color palette entry #78. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #102. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #126. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #6. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #8. Gave up after 10 retries. Check selected MIDI in-/outputs.
Failed reading color palette entry #8. Gave up after 10 retries. Check selected MIDI in-/outputs.

It sometimes happens that the color palette does not update completely. Simply ignore it (or if it does look weird, turn it off and on again).

[politcat]

is there a way to keep the FX chain window from opening when pressing WINDOW? so only the plugin window opens

this only happens when opening bridged plugins

[dna598]

Hi any way you could implement adjusting the text size? Some params with long names could benefit from that. Thanks!

[Zabelle_be]

Hi Moss,
I really appreciate your work and use an Icon with Reaper: everything works very well.

On the other hand, I've been struggling for hours (really!) to try to use my launchpad pro MK1 and I can't do it...
In fact, none of the pads light up (but the buttons around the pads light up) and I don't understand how to get close to the screen copies of your manual.

Any idea to help me? I'm on Mac.

Big thank you!

[Zabelle_be]

I really don't know what I did...but it works now with my Launchpad Pro MK1 ;-)

I still have to figure out how to do note repeat and how to properly use drum sequencers

Thanks for all that work !

[metal_priest]

hi evryone, hi Moss.
I just upgrade your driver to the latest version and added an extender to my X-Touch.
Everything works fine but a couple of things:

- I have a default project with a bunch of of tracks into a "main" folder. When i lunch reaper it opens with this default project and the controllers doesn't show any tracks loaded, I have to delete all the tracks and create new ones to make the controller up.
- I have this strange behaviour (see video in the link please): in PAN/SURROUND mode when i move a fader, the controllers switch to TRACK mode temporarly. Not a big issue but it's annoying.
https://streamable.com/91xkd1

With the main controller and the old version i didn't have this two issues, I don't know if it's because of the extender (something wrong in my configuration) or some bug.

Thanks for the help.

[moss]

Originally Posted by politcat

is there a way to keep the FX chain window from opening when pressing WINDOW? so only the plugin window opens

this only happens when opening bridged plugins

There is an "expanded" state remembered from the last opened plugin. On some controllers (e.g. Ableton Push) you can toggle it.

[moss]

Originally Posted by dna598

Hi any way you could implement adjusting the text size? Some params with long names could benefit from that. Thanks!

Which controller? Which text? Where?

[moss]

Originally Posted by metal_priest

- I have a default project with a bunch of of tracks into a "main" folder. When i lunch reaper it opens with this default project and the controllers doesn't show any tracks loaded, I have to delete all the tracks and create new ones to make the controller up.

Is a track selected? If this does not fix it, please send me the template.

Originally Posted by metal_priest

- I have this strange behaviour (see video in the link please): in PAN/SURROUND mode when i move a fader, the controllers switch to TRACK mode temporarly. Not a big issue but it's annoying.

It enables temporarily the Volume mode. You can disable this behaviour in the settings (Workflow -> Activate Volume mode on Fader touch).

[metal_priest]

Originally Posted by moss

It enables temporarily the Volume mode. You can disable this behaviour in the settings (Workflow -> Activate Volume mode on Fader touch).

thanks, it was that.

Originally Posted by moss

Is a track selected? If this does not fix it, please send me the template.

No, even with any tracks selected, it load the master fader but all the other fader are dead, and the scribble is total black.
Here the template. It's just a folder with 24 tracks and 4 other tracks as bus.


EDIT: the folder is hidden in the MCP, maybe this is the issue. If i switch it visible then all the tracks comes alive in the controller. This isn't like that in the previous version.

EDIT 2: another test shows that in "flat mode" for the track navigation and the folder track selected make the thing works, even if the folder it's hidden in the MCP.

[Hael.an]

Hello!

I have a launchpad mini mk3 that seems to be sensing the script when i load it up but all the keys are unresponsive. The only feedback i get is when i select a track the buttons turn white but no other buttons are working. I made sure the firmware was up to date. I am using Reaper 6.80. I have been using my launchpad pro mk3 flawlessly so I'm not sure what I may be doing wrong. Thank you so much for your hard work!

[Ostent]

Hi, moss!

Update:

I did some more tinkering around and the knobs not working is not limited to just play mode, it is in fact every mode. I cannot get the knobs to respond at all and am just met with the 'should be handled in framework' message. Interestingly, with a midi monitor engaged, all the pads show midi activity however the knobs send none at all - I assume this has something to do with them not being parsed by the extension itself.

I have double-checked that all hardware controls are set to global channel 3 in the Arturia MIDI center. I have tried setting the knobs and pads to 'global' where the global channel is 3 and I have also set each knob and pad manually to channel 3 - to no avail.

--

I have been using the Arturia Beatstep with REAPER and managed to have everything working at one point. However, now when I am in play mode and I use the knobs to change scale, root, etc (anything that would have the on-screen pop-up, I do not get any change at all. For example, if I turn knob 16 to increase the octave I do not get the audible change in octave nor do I see the pop-up on-screen showing the current octave.

Going into the configuration panel of the control surface settings I can see the following message;

`CC 72 should be handled in framework...`

Of course, the CC will change depending on which unresponsive knob that I turn. I am running REAPER 6.82 and the beatstep is running the most current firmware from Arturia.

Any suggestions on what can be done / how to proceed? Thanks!

[vlab]

Hi there !

First of all, thanks so much for the DrivenbyMoss software, it really bring useability to a few of my older controllers here, in no way other Reaper plugins/extensions can !

I was going more in depth using the Akai Fire, and the integration is truly amazing !
I have 2 small questions/requests for it:

- Would it be possible to replace the action of setting the selected track automation to TOUCH automation (instead of WRITE?) (ALT+STOP), so when the pots are not touched, it would not overwrite automation? , or maybe toggle between Trim and Touch with SHIFT+ALT+STOP, As the device display reacts to touch, I was thinking this would be possible?

- Also, it seems unable to assign knobs in USER2 (project), The manual says it's for track parameters, but it does not seem to work? if ever we could have Reaper's track parameters (the ones we can individually assign on each track), that could be helpful to have a few knobs that are track-based, and not plugin-based.

So there you go with my suggestions! Thanks again!

Cheers!
V

[politcat]

Thank you! workflow is light years better

[tommasoferrarese]

Hi Moss! Thanks for the great work supporting Reaper! I have two questions about Push 2 implementation..

1) When I add devices the browser keeps showing a lot of different versions of toy plugins, (ARM or x86_64) but I wish I could filter x86 ones out by default.. is it possible? Can't wrap my head around it..

2) Would it be possible to implement/return to the LED panel interface style of Ableton? I'd really love it (I am willing to pay for this!)

Thanks and keep up the excellent work!

Tommaso

[moss]

Originally Posted by metal_priest

No, even with any tracks selected, it load the master fader but all the other fader are dead, and the scribble is total black.
Here the template. It's just a folder with 24 tracks and 4 other tracks as bus.

EDIT: the folder is hidden in the MCP, maybe this is the issue. If i switch it visible then all the tracks comes alive in the controller. This isn't like that in the previous version.

EDIT 2: another test shows that in "flat mode" for the track navigation and the folder track selected make the thing works, even if the folder it's hidden in the MCP.

Yes, that is expected.

[moss]

Originally Posted by Hael.an

Hello!

I have a launchpad mini mk3 that seems to be sensing the script when i load it up but all the keys are unresponsive. The only feedback i get is when i select a track the buttons turn white but no other buttons are working. I made sure the firmware was up to date. I am using Reaper 6.80. I have been using my launchpad pro mk3 flawlessly so I'm not sure what I may be doing wrong. Thank you so much for your hard work!

Are the MIDI in-/outputs deactivated in Reaper?

[moss]

Originally Posted by Ostent

Hi, moss!

Update:

I did some more tinkering around and the knobs not working is not limited to just play mode, it is in fact every mode. I cannot get the knobs to respond at all and am just met with the 'should be handled in framework' message. Interestingly, with a midi monitor engaged, all the pads show midi activity however the knobs send none at all - I assume this has something to do with them not being parsed by the extension itself.

I have double-checked that all hardware controls are set to global channel 3 in the Arturia MIDI center. I have tried setting the knobs and pads to 'global' where the global channel is 3 and I have also set each knob and pad manually to channel 3 - to no avail.

--

I have been using the Arturia Beatstep with REAPER and managed to have everything working at one point. However, now when I am in play mode and I use the knobs to change scale, root, etc (anything that would have the on-screen pop-up, I do not get any change at all. For example, if I turn knob 16 to increase the octave I do not get the audible change in octave nor do I see the pop-up on-screen showing the current octave.

Going into the configuration panel of the control surface settings I can see the following message;

`CC 72 should be handled in framework...`

Of course, the CC will change depending on which unresponsive knob that I turn. I am running REAPER 6.82 and the beatstep is running the most current firmware from Arturia.

Any suggestions on what can be done / how to proceed? Thanks!

If you get this error it sends the wrong commands. Make sure that you did install the template which comes with DrivenByMoss and you can find it in the resources folder.

[moss]

Originally Posted by vlab

- Would it be possible to replace the action of setting the selected track automation to TOUCH automation (instead of WRITE?) (ALT+STOP), so when the pots are not touched, it would not overwrite automation? , or maybe toggle between Trim and Touch with SHIFT+ALT+STOP, As the device display reacts to touch, I was thinking this would be possible?

Oh, my. :-) This device is already crammed with stuff. But will take note.

Originally Posted by vlab

- Also, it seems unable to assign knobs in USER2 (project), The manual says it's for track parameters, but it does not seem to work? if ever we could have Reaper's track parameters (the ones we can individually assign on each track), that could be helpful to have a few knobs that are track-based, and not plugin-based.

You can toggle between Project and Track parameters with Alt+Select Knob (turning it).
"Project parameters" control the track parameters of the master track (this is the default).
"Track parameters" the track parameters of the selected track.

[moss]

Originally Posted by tommasoferrarese

Hi Moss! Thanks for the great work supporting Reaper! I have two questions about Push 2 implementation..

1) When I add devices the browser keeps showing a lot of different versions of toy plugins, (ARM or x86_64) but I wish I could filter x86 ones out by default.. is it possible? Can't wrap my head around it..

Currently not possible but will take note.

Originally Posted by tommasoferrarese

2) Would it be possible to implement/return to the LED panel interface style of Ableton? I'd really love it (I am willing to pay for this!)

Thanks and keep up the excellent work!

I have no plans or interest in that (also not for money ;-)).

[derschulz]

Hi Moss, hope you're still around in this forum...

1. drivenbymoss is amazing - for me the missing link between Reaper and X-Touch, the thing I was expecting more hoping to see from Behringer
2. on certain plugins it still freezes (e.g. SSL G and E Channel from Waves, but Vocal rider works and a couple more. sometimes the freeze happens on loading the FX, sometimes after a couple seconds to minutes

Setup:
Mac Mini M1 2020, 8Gb
Ventura 13.5.2
Reaper 6.82
X Touch Firmware 1.21

[moss]

Originally Posted by derschulz

Hi Moss, hope you're still around in this forum...

1. drivenbymoss is amazing - for me the missing link between Reaper and X-Touch, the thing I was expecting more hoping to see from Behringer
2. on certain plugins it still freezes (e.g. SSL G and E Channel from Waves, but Vocal rider works and a couple more. sometimes the freeze happens on loading the FX, sometimes after a couple seconds to minutes

Setup:
Mac Mini M1 2020, 8Gb
Ventura 13.5.2
Reaper 6.82
X Touch Firmware 1.21

Hmm, sadly I have none of these plugins. Any other plugins (maybe a free one) which causes this issue? Since it is MacOS, are these ARM plugins?

[derschulz]

hm - another day, no issue!? Two days ago I gave drivenbymoss another shoot after having massive lags on a first try months ago. Yesterday Reaper kept crashing all the time when I tried to load different plugins. 20 hours later I am working on the same project with the same plugins the same gear and my X-touch is driven by moss without a problem.
I will be looking for a crash log later, right now I have to get going with my project.
thanx for your work!