Reaper user here with the XTouch. It seems you've done the impossible which is AMAZING. There are only a few pieces of functionality im missing in DrivenByMoss for Reaper which im hoping I've just missed in the manual or do not understand how to do yet.
Apologies if this question has been asked before I cannot find it,
Is there any way to map the encoder knobs differently than the faders on the Xtouch? This would just be so much better for me for a lot of different reasons. (Mainly EQ having Gain on faders, with Frequency on Knobs) Or even defining a third control by pushing in the rotary encoders? Can you define what the lowest parameters for something is and what the highest is? Ex/ on an EQ, I want bringing the fader all the way down to only cut it by 6db, not bring it straight down to -150db, that way I have more real-estate and control over that area.
Also, is there a way to have DrivenByMoss automatically follow the FocusedFX when in the Plugin mode? Or a way to change the default EQ with the EQ mode.
It would also be preferable if while also following the selected FX, if you were opening an plugin with the Xtouch by pressing the Plugin button, it would display all the plugins on the 8 LCD screens which you could then choose from by hitting the select button on that channel. This way, you don't have to deal with the loading times while scrolling through the plug-ins, with the page buttons still taking you to the next or previous buttons.
It would be cool if the sends page reassigned the 8 faders to be the first 8 sends which you could scroll through in pages, and then pressing the sends button again would show the receives for the track (super useful for like headphone mixes in a studio session.)
DrivenByMoss seems to be the only controller interface that I've tried that simply "Just Works" but still allows for customization. All of the others ones requires something to be open or for you to refresh the controller every 30 seconds.
Genius! Are any of these features already implemented however Im just blind? Most of these seem to already be features but somewhere else in DrivenByMoss, or they seem simple enough to implement. However I don't know enough about the code so hopefully its easy and not impossible without a complete re-structuring of code.
Thank you DrivenByMoss!
Last edited by CodyWright; 08-10-2023 at 06:25 PM.
Reason: Added one feature
Have two music rigs (Windows 7 Pro) using Reaper with Komplete Kontrol MK1 keyboards:
* Desktop with S61
* Laptop with S49
I simply want the Transport buttons on the K.K. to work. Have not explored anything else.
After a little poking and prodding, finally have the Transport buttons working on both Desktop and Laptop....but with things a bit different from the DrivenByMoss manual and video.
Reaper MIDI device Input setup - Contrary to the DrivenByMoss manual, I have to Enable the two checkboxes for "input" and "control" for the K.K. keyboard (which is usually SOP)... But in the associated Reaper MIDI output settings for the keyboard, nothing enabled.
The DrivenByMoss manual mentions the K.K. MK2 version uses the NIHostIntegrationService, but the manual does NOT specifically mention that for the MK1 - However my two MK1s do in fact use it and apparently wont work without it.
Further note - There is something tricky/iffy about my two computers automatically recognizing the keyboards via USB - meaning sometimes they dont...at least I think that is what is going on...so I have to turn the keyboard(s) off with their power button, then back on. MIDIView is useful to verify the keyboard is recognized.
Hope this info is useful. Appreciate the work, thanks so much, Moss.
I've borrowed an X-Touch Compact to play with. I'm trying to set it up and have tested it under three operating systems.
On all three systems I have the newest versions of DrivenByMossforReaper and Reaper.
Windows 10: I updated the X-Touch Compact firmware to 1.14 and did a factory reset. Everything worked as expected.
On Fedora 38 (my main system) and Ubuntu 23.04, I could configure the control surface, but Reaper would lockup. Interestingly, the control surface was working (transport, faders, etc).
If I use Mackie Control instead of DrivenBy, the X-Touch works.
Transport is not working, and only MIDI channel 1 is getting thru. Notice an error in the log....
From log: **************
Loading device INI files from C:\Users\sww2\AppData\Roaming\REAPER ...
reaper-clap-win64.ini not present (this is not an error!).
DrivenByMoss4Reaper-ParameterMaps.ini not present (this is not an error!).
Native Instruments Komplete Kontrol S61 mk I: Starting...
Could not open USB connection: Could not find HID device: Vendor ID: 6092, Product ID: 4960
Native Instruments Komplete Kontrol S61 mk I: Running.
*************** end log
Further notes:
The manual says the MK1 cannot be detected and is added manually. Mine is detected.
Also, the manual mentions that the MK2 uses the NIHostIntegrationService, but the manual does NOT mention that for the MK1 - my MK1 does use it.
UPDATE: I deleted the detected instrument and loaded it manually, and Transport works!!! However, only MIDI channel 1 is coming thru. ( I have my keyboard split into three channels)
The MkI implementation uses USB directly. Therefore, the NI service might interfere with that. This is documented in the DrivenByMoss manual in the MkI chapter.
Hey Moss, Brilliant update. I just recently got a secondhand Push 2 now they're more affordable (Was on Push 1).
Just a quick question, are the buttons around the outside supposed to be duller than with the Ableton integration?
i.e. the Mute, Solo buttons to the left side of the device are barely lit whereas on Ableton they are bright green.
Same with transport, the play button is very dull but does go bright white when project is playing.
Just checking that's how it's supposed to be, thanks again!
Make sure to have power connected. In general the buttons are lit a bit darker in my implementation, which sometimes shows the different quality of the LEDs on the Push.
Hello DrivenByMoss!
Reaper user here with the XTouch. It seems you've done the impossible which is AMAZING. There are only a few pieces of functionality im missing in DrivenByMoss for Reaper which im hoping I've just missed in the manual or do not understand how to do yet.
Apologies if this question has been asked before I cannot find it,
Is there any way to map the encoder knobs differently than the faders on the Xtouch? This would just be so much better for me for a lot of different reasons. (Mainly EQ having Gain on faders, with Frequency on Knobs) Or even defining a third control by pushing in the rotary encoders? Can you define what the lowest parameters for something is and what the highest is? Ex/ on an EQ, I want bringing the fader all the way down to only cut it by 6db, not bring it straight down to -150db, that way I have more real-estate and control over that area.
Sorry, no. If you are looking for more tinkinering CSI might be the better solution.
Quote:
Originally Posted by CodyWright
Also, is there a way to have DrivenByMoss automatically follow the FocusedFX when in the Plugin mode? Or a way to change the default EQ with the EQ mode.
Both on my todo list but not too high ;-)
Quote:
Originally Posted by CodyWright
It would also be preferable if while also following the selected FX, if you were opening an plugin with the Xtouch by pressing the Plugin button, it would display all the plugins on the 8 LCD screens which you could then choose from by hitting the select button on that channel. This way, you don't have to deal with the loading times while scrolling through the plug-ins, with the page buttons still taking you to the next or previous buttons.
Isn't that a Reaper setting to show all windows when a track is selected?
Quote:
Originally Posted by CodyWright
It would be cool if the sends page reassigned the 8 faders to be the first 8 sends which you could scroll through in pages, and then pressing the sends button again would show the receives for the track (super useful for like headphone mixes in a studio session.)
There is an option in the settings to use the last device to exclusivly control FX sends.
I've borrowed an X-Touch Compact to play with. I'm trying to set it up and have tested it under three operating systems.
On all three systems I have the newest versions of DrivenByMossforReaper and Reaper.
Windows 10: I updated the X-Touch Compact firmware to 1.14 and did a factory reset. Everything worked as expected.
On Fedora 38 (my main system) and Ubuntu 23.04, I could configure the control surface, but Reaper would lockup. Interestingly, the control surface was working (transport, faders, etc).
If I use Mackie Control instead of DrivenBy, the X-Touch works.
Thanks Jürgen (and anyone else) for any help you can offer.
The freezing of the configuration dialog happens with some window managers on Linux but it seems you already found the workaround.
If your device misses from the template selection simply make the settings below according to the features of your MCU device (this is just for quick configuration).
Which feedback is not working? What you did in the video seems all fine. E.g. buttons lit up when you pressed them.
The MkI implementation uses USB directly. Therefore, the NI service might interfere with that. This is documented in the DrivenByMoss manual in the MkI chapter.
Am aware of the docs and have tried multiple times to strictly follow the instructions and making sure the NI service is turned off. And what happens is only MIDI channel one comes thru.
Here is my workaround that seems to function with all channels coming thru for multi-channel split-keyboard use - this is from my earlier post here:
Have two music rigs (Windows 7 Pro) using Reaper with Komplete Kontrol MK1 keyboards:
* Desktop with S61
* Laptop with S49
I simply want the Transport buttons on the K.K. to work. Have not explored anything else.
After a little poking and prodding, finally have the Transport buttons working on both Desktop and Laptop....but with things a bit different from the DrivenByMoss manual and video.
Reaper MIDI device Input setup - Contrary to the DrivenByMoss manual, I have to Enable the two checkboxes for "input" and "control" for the K.K. keyboard (which is usually SOP)... But in the associated Reaper MIDI output settings for the keyboard, nothing enabled.
The DrivenByMoss manual mentions the K.K. MK2 version uses the NIHostIntegrationService, but the manual does NOT specifically mention that for the MK1 - However my two MK1s do in fact use it and apparently wont work without it.
Further note - There is something tricky/iffy about my two computers automatically recognizing the keyboards via USB - meaning sometimes they dont...at least I think that is what is going on...so I have to turn the keyboard(s) off with their power button, then back on. MIDIView is useful to verify the keyboard is recognized.
There is still the "Thanks" button below each video (sometimes it is hidden behind the dots "...").
Have to login into Google/YouTube account account to find that "thank you" link.
That's where it was hiding. Just in case people wondered. So I made a contribution.
Works great for LaunchControlXL.
And also like to add...Bitwig studio makes other DAWS obsolete. Node driven grid, something that is needed by all DAWS.
Am aware of the docs and have tried multiple times to strictly follow the instructions and making sure the NI service is turned off. And what happens is only MIDI channel one comes thru.
Here is my workaround that seems to function with all channels coming thru for multi-channel split-keyboard use - this is from my earlier post here:
Have two music rigs (Windows 7 Pro) using Reaper with Komplete Kontrol MK1 keyboards:
* Desktop with S61
* Laptop with S49
I simply want the Transport buttons on the K.K. to work. Have not explored anything else.
After a little poking and prodding, finally have the Transport buttons working on both Desktop and Laptop....but with things a bit different from the DrivenByMoss manual and video.
Reaper MIDI device Input setup - Contrary to the DrivenByMoss manual, I have to Enable the two checkboxes for "input" and "control" for the K.K. keyboard (which is usually SOP)... But in the associated Reaper MIDI output settings for the keyboard, nothing enabled.
The DrivenByMoss manual mentions the K.K. MK2 version uses the NIHostIntegrationService, but the manual does NOT specifically mention that for the MK1 - However my two MK1s do in fact use it and apparently wont work without it.
Further note - There is something tricky/iffy about my two computers automatically recognizing the keyboards via USB - meaning sometimes they dont...at least I think that is what is going on...so I have to turn the keyboard(s) off with their power button, then back on. MIDIView is useful to verify the keyboard is recognized.
Thanks again for your work, Moss.
If you do not care about the display, simply use the MIDI mode of the MkI and any simple MIDI mapping you prefer.
I guess your main issue is that the USB is not recognized.
Have to login into Google/YouTube account account to find that "thank you" link.
That's where it was hiding. Just in case people wondered. So I made a contribution.
Works great for LaunchControlXL.
And also like to add...Bitwig studio makes other DAWS obsolete. Node driven grid, something that is needed by all DAWS.
If you do not care about the display, simply use the MIDI mode of the MkI and any simple MIDI mapping you prefer.
I guess your main issue is that the USB is not recognized.
To be clear, the USB is recognized, just maybe only after I restart the MK1 on after booting.
Any suggestions to diagnose why only channel one comes thru when I setup per your instructions? I assume all channels are supposed to work...
Oddly with version 21, and with the Novation SL MK3, I'm getting a StackHash crash, only when I press any of the buttons-- Mute, Solo, Arm, or Monitor.
All the encoders and other functions are fine.
Last version I was using was 9 or 10 I believe... worked perfectly all this time. Finally updated, now Reaper freezes and crashes immediately upon pressing any of the buttons.
Something about a BXE64 error or something.
To be fair, I was copying a couple large folders (essentially backing up the folders) but the problem still happens when nothing else is going on (no files/folders transferring).
Anyone else?
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Still getting freezing Reaper / forced shutdown/crash with this latest DBM, and the SL MK3. Any idea, Moss? Thank you
Let's say there's just two tracks in the project-- three buttons are lit up (obviously the last is the Master track mute/solo/monitor/arm).
Muting/unmuting the last (Master) does not cause a freeze/crash with version 21. Muting/unmuting any other tracks-- boom, instant freeze/crash.
-----------
EDIT: Went back to version 8.9.4 which I've used since it's been out (for at least two years). Stable, no crashes.
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Last edited by themixtape; 08-17-2023 at 04:31 PM.
When Value Change Speed is toggled to slow and effecting the track volume, the value can only decrease, not increase. Other things like tempo you can both increase and decrease on both speeds.
I just got an Entech EF44 controller which supports 14bit and sysex. However, when I use 14bit mode the values I'm controlling in fabfilter don't move much or they just jump to their highest value and then never go back? Not sure what's happening or how to configure this.
I've tried changing the source mapping to the "encoder" types but I don't get a usable result. I've also messed with the glue source min/max and also unusable results.
Right now I'm just trying to get fabfilter to return to 0 gain, but there isn't enough resolution in the 7bit mode - it lands on .24db or -.24db. I would like it to return to zero.
Any help is greatly appreciated. Thanks!
EDIT: I can't get anything other than 7bit to work and if I dial back the glue source max to 122, I can get to 0db... is that right? Is there something wrong with this controller or just the nature of 7bit?
Last edited by P. WALLACE; 08-19-2023 at 02:36 PM.
When Value Change Speed is toggled to slow and effecting the track volume, the value can only decrease, not increase. Other things like tempo you can both increase and decrease on both speeds.
Ah, the old resolution issue which I forgot about. Turns out this is pretty easy to improve. Will be fixed in the next update!
I just got an Entech EF44 controller which supports 14bit and sysex. However, when I use 14bit mode the values I'm controlling in fabfilter don't move much or they just jump to their highest value and then never go back? Not sure what's happening or how to configure this.
I've tried changing the source mapping to the "encoder" types but I don't get a usable result. I've also messed with the glue source min/max and also unusable results.
Right now I'm just trying to get fabfilter to return to 0 gain, but there isn't enough resolution in the 7bit mode - it lands on .24db or -.24db. I would like it to return to zero.
Any help is greatly appreciated. Thanks!
EDIT: I can't get anything other than 7bit to work and if I dial back the glue source max to 122, I can get to 0db... is that right? Is there something wrong with this controller or just the nature of 7bit?
This could be the same issue as above. Please test again with the next update.
Hey Moss, thanks again for saving the day. Picked up an X-Touch One for dirt cheap a month ago... stupid X-Touch One in any of the modes (MC Reap, MC Standard, MC User)... nothing worked, NOTHING.... in regards to changing the track with the mouse or from a different MIDI controller... the X-Touch One never followed.
With DrivenByMoss? Every single time.
Drives me nuts... don't know why this is such a damn pain in the ass, sometimes... the X-Touch Universal works way, way better than this little guy.
But, it's working like I want. I just wish I could customize F1-F6 to a Reaper Action. No way to do this, is there? Thanks man!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Hey Moss, thanks again for saving the day. Picked up an X-Touch One for dirt cheap a month ago... stupid X-Touch One in any of the modes (MC Reap, MC Standard, MC User)... nothing worked, NOTHING.... in regards to changing the track with the mouse or from a different MIDI controller... the X-Touch One never followed.
With DrivenByMoss? Every single time.
Drives me nuts... don't know why this is such a damn pain in the ass, sometimes... the X-Touch Universal works way, way better than this little guy.
But, it's working like I want. I just wish I could customize F1-F6 to a Reaper Action. No way to do this, is there? Thanks man!
Sure, you can configure it in the settings. Is that not working?
I think the crash I mentioned had to do with running Reaper 6.53 or something. On your site it says 6.71 recommended, at least. I’ve got to pay more attention to these things.
Do you think the freeze/crash when hitting the mute/solo/arm/monitor buttons could be because the Reaper version was prior to 6.71?
EDIT: yes. It seems to be exactly why. I updated to 6.81 and everything's fine. Any reason each new update for DBM needs to be on an updated version of Reaper? I like to stick with a version for a long time because
1. I use portable Reaper, and it's sort of a pain in the ass to update with the export/import config which doesn't always catch everything
2. Your code shouldn't be affected by their code update, right?
------------
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Last edited by themixtape; 08-22-2023 at 02:05 PM.
I think the crash I mentioned had to do with running Reaper 6.53 or something. On your site it says 6.71 recommended, at least. I’ve got to pay more attention to these things.
Do you think the freeze/crash when hitting the mute/solo/arm/monitor buttons could be because the Reaper version was prior to 6.71?
EDIT: yes. It seems to be exactly why. I updated to 6.81 and everything's fine. Any reason each new update for DBM needs to be on an updated version of Reaper? I like to stick with a version for a long time because
1. I use portable Reaper, and it's sort of a pain in the ass to update with the export/import config which doesn't always catch everything
2. Your code shouldn't be affected by their code update, right?
------------
DrivenByMoss always clearly indicates which version of Reaper is necessary in the changes list and on the downloads page. If it requires a new version it normally to new fatures available in Reaper. 6.71 is required for quite some time now.
DrivenByMoss always clearly indicates which version of Reaper is necessary in the changes list and on the downloads page. If it requires a new version it normally to new fatures available in Reaper. 6.71 is required for quite some time now.
Yes, I understand. I guess the Reaper code changes a lot as you update each version.
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Another question I had-- is it possible to use two MC controllers at the same time, with DrivenByMoss? I have an X-Touch and an X-Touch One. It seems only one or the other is detected with DBM "Detect." Usually, just the bigger one.
Wasn't sure if it was a Reaper limitation or a DBM limitation. Thanks!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Another question I had-- is it possible to use two MC controllers at the same time, with DrivenByMoss? I have an X-Touch and an X-Touch One. It seems only one or the other is detected with DBM "Detect." Usually, just the bigger one.
Wasn't sure if it was a Reaper limitation or a DBM limitation. Thanks!
Yes. If it is not detected, simply add it manually.
When you hit the EQ button, it creates a ReaEQ on the track.
When you turn the encoders for adjusting the parameters, there is lag / a delay.
If you hit the Plug-In button (to adjust the same EQ), no delay. I made a video of this to show you what I mean if you want to see it.
I don't know why there's lag when you're in the EQ section, but in the Plug-In section, no lag... adjusting the same exact parameters.
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Also, apologize for my ignorance... with the Function buttons for X-Touch, why are F6-F8 not configurable?
Also, is there any way to use X-Touch in DBM mode, and also midi control mode (regular MIDI Devices section) to re-assign buttons to get more functions? X-Touch has both virtual MIDI drivers-- simply, "X-Touch" and "X-Touch MIDI 2"
Thanks, Moss!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Also, apologize for my ignorance... with the Function buttons for X-Touch, why are F6-F8 not configurable?
They are hardwired (see manual). It is on my todo list to make this configurable as well.
Quote:
Originally Posted by themixtape
Also, is there any way to use X-Touch in DBM mode, and also midi control mode (regular MIDI Devices section) to re-assign buttons to get more functions? X-Touch has both virtual MIDI drivers-- simply, "X-Touch" and "X-Touch MIDI 2"
Linear Mode
