Hi. I'm using this with an X Touch Extender (just the Extender) and I wanna know if a can use it for example in plugin mode too. Any way to change the modes with the Extender standalone?
Oh,sad to hear that because otherwise it works great. Have you thought about adding that functionality? Any keyboard shortcut could be assigned to change modes, for example.
Hey, now that i'm using this extension with my X Touch Extender I've noticed what I think is a bug. Reaper does not register any volume or pan input as undo state, it only registers when I press the Rec, Solo or Mute buttons. If I use the controller without the extension, the registration in the undo states works for everything. In other words, with this extension if I make a volume or a pan change I can't go back since it is not registered in the Reaper undo state. Is there any solution?
There is an error in the method of temporarily launching a clip in Session mode. It says, "Press and hold Select knob+PAD: Immediately launches a clip. Release the clip pad while holding Select, to return immediately to the last playing clip." - this does not work. I suspect because of the Alternate Launch function. Which leads to the second issue. The documentation says, "Alt+Mute/Solo 1-4 Executes the alternative launch function of the scene". It took me a second to figure out that it's actually "SHIFT+Mute/Solo 1-4" and that this also solves the Select+Pad since SHIFT works in combination with the pads to use alternate launch settings.
At first I thought these functions were not working on my Fire, but I'm thrilled to see it works with even easier functionality than documented. I also want to say this script is AMAZING and the reason I bought Bitwig.
Hello Jürgen,
Friable thanx for your implication in those tools you created !
I've just install your DrivenByMoss 4 Reaper
I'am on a MacBook Pro M2Pro 14" and VENTURA 13.4 OS
My Reaper is in v6.81
Xtouch + Xtouch Extension plugged in USB
I select the controller Mackie MCU Universal + Ext
I have tried to do the "detect" but it seems that there is nothing to see
so I have used the "add" button (and select the MCU+Ext as I said)
So now I'm in the menu CONFIGURATION
I have choose the Xtouch INT for IN/OUT 1
and the Xtouch EXT for IN/OUT 2
My issue is that I can't go further and when I choose the Xtouch my selection is not retain!
First of all, thank you very much for your work! I could successfully use DrivenByMoss4REAPER on Ubuntu with a Novation Launchkey MK3.
I stumbled upon an issue when using OpenSUSE. It doesn't automatically detect the controller and after adding it manually, I see no changes; the controller does not light up differently and I am still unable to control REAPER via the controller, even though it says it's 'running'. I also don't get any error messages which does not help... Although, I am able to get it to work on Bitwig Studio on OpenSUSE. Do you know where I could look further to resolve this issue? Thanks in advance!
Hey, now that i'm using this extension with my X Touch Extender I've noticed what I think is a bug. Reaper does not register any volume or pan input as undo state, it only registers when I press the Rec, Solo or Mute buttons. If I use the controller without the extension, the registration in the undo states works for everything. In other words, with this extension if I make a volume or a pan change I can't go back since it is not registered in the Reaper undo state. Is there any solution?
Thanks for the info. Will be fixed in the next update!
There is an error in the method of temporarily launching a clip in Session mode. It says, "Press and hold Select knob+PAD: Immediately launches a clip. Release the clip pad while holding Select, to return immediately to the last playing clip." - this does not work. I suspect because of the Alternate Launch function. Which leads to the second issue. The documentation says, "Alt+Mute/Solo 1-4 Executes the alternative launch function of the scene". It took me a second to figure out that it's actually "SHIFT+Mute/Solo 1-4" and that this also solves the Select+Pad since SHIFT works in combination with the pads to use alternate launch settings.
At first I thought these functions were not working on my Fire, but I'm thrilled to see it works with even easier functionality than documented. I also want to say this script is AMAZING and the reason I bought Bitwig.
All special/alternate Clip launching does not work in Reaper since it has no such functionality. But it seems I forgot to document the clip behaviour in the "Known Issues" section of the manual. Will add it.
Hello Jürgen,
Friable thanx for your implication in those tools you created !
I've just install your DrivenByMoss 4 Reaper
I'am on a MacBook Pro M2Pro 14" and VENTURA 13.4 OS
My Reaper is in v6.81
Xtouch + Xtouch Extension plugged in USB
I select the controller Mackie MCU Universal + Ext
I have tried to do the "detect" but it seems that there is nothing to see
so I have used the "add" button (and select the MCU+Ext as I said)
So now I'm in the menu CONFIGURATION
I have choose the Xtouch INT for IN/OUT 1
and the Xtouch EXT for IN/OUT 2
My issue is that I can't go further and when I choose the Xtouch my selection is not retain!
have a nice day
fk
Please see the specific MCU installation notes in the manual. All your questions are answered there.
First of all, thank you very much for your work! I could successfully use DrivenByMoss4REAPER on Ubuntu with a Novation Launchkey MK3.
I stumbled upon an issue when using OpenSUSE. It doesn't automatically detect the controller and after adding it manually, I see no changes; the controller does not light up differently and I am still unable to control REAPER via the controller, even though it says it's 'running'. I also don't get any error messages which does not help... Although, I am able to get it to work on Bitwig Studio on OpenSUSE. Do you know where I could look further to resolve this issue? Thanks in advance!
Looks like some kind of incompatibility but I have sadly no idea what could be the cause.
Fixed: Improved Undo state when changing volume and panorama.
Thx! It's fixed! 👍
Couldn't you make the other X-Touch modes accessible on the X-Touch Extender by perhaps pressing two buttons together? It would be great and I would have to make a statue of you in the square of my town 😂
What a fantastic piece of work!. After being very disappointed with Reaper's incomplete HUI support I tried DrivenByMoss with my new Yamaha DM3 mixer in HUI mode and it works extremely well (with a couple of caveats)
The only really significant issue is that channel change, instead of moving the leftmost fader to be on the previous/next channel, moves the selected channel inside the current bank until you get to the beginning/end when it does a bank change. But this precludes grouping faders that cross a bank boundary from being controllable from a single view, which is a shame. (e.g faders 6,7,8,9). You would never be able to get these into a single view on the mixer because you can't move in increments of one channel. The Cubase HUI plugin does do this correctly.
The timecode display works
All transport controls work correctly
Record arm, mute and solo all work
Scribble strips work
Metering works
The rotary encoder will move around the timeline
Scrub and shuttle do NOT work - the plugin log reports these keys aren't supported
Rec/Rdy All reports not supported
The automation buttons don't report any errors in the log but don't appear to work correctly. They can cause automation to be engaged but its unpredictable and things in general don't seem to work correctly here. You can see Reaper's automation fader jumping all over the place as you try and record any automation and the mode doesn't change when you select read/touch/latch/write/trim/off
The bank switches work correctly but the channel switches, instead of moving all faders one position right or left, change the focus within the current bank.
You cannot (AFAIK) configure the plugin so that the master fader is controllable, only the channel faders. [this WAS possible with the Reaper plugin]
What a fantastic piece of work!. After being very disappointed with Reaper's incomplete HUI support I tried DrivenByMoss with my new Yamaha DM3 mixer in HUI mode and it works extremely well (with a couple of caveats)
The only really significant issue is that channel change, instead of moving the leftmost fader to be on the previous/next channel, moves the selected channel inside the current bank until you get to the beginning/end when it does a bank change. But this precludes grouping faders that cross a bank boundary from being controllable from a single view, which is a shame. (e.g faders 6,7,8,9). You would never be able to get these into a single view on the mixer because you can't move in increments of one channel. The Cubase HUI plugin does do this correctly.
I am afraid this will not change. This is due to how it is implemented internally to keep the performance down when multiple devices are used.
Quote:
Originally Posted by ajaym
The timecode display works
All transport controls work correctly
Record arm, mute and solo all work
Scribble strips work
Metering works
The rotary encoder will move around the timeline
Scrub and shuttle do NOT work - the plugin log reports these keys aren't supported
Rec/Rdy All reports not supported
The automation buttons don't report any errors in the log but don't appear to work correctly. They can cause automation to be engaged but its unpredictable and things in general don't seem to work correctly here. You can see Reaper's automation fader jumping all over the place as you try and record any automation and the mode doesn't change when you select read/touch/latch/write/trim/off
The HUI implementation is pretty old and you are the first one who shows interest in this for several years. I am really surprised that such a high-end device supports only such a crappy old protocol.
Back then I had only a few devices with a very limited HUI support and did only implement the features I could test. Meanwhile, I have the Behringer X-Touch which supports HUI as well and covers more of the original features.
I will add it to the wishlist.
Quote:
Originally Posted by ajaym
The bank switches work correctly but the channel switches, instead of moving all faders one position right or left, change the focus within the current bank.
You cannot (AFAIK) configure the plugin so that the master fader is controllable, only the channel faders. [this WAS possible with the Reaper plugin]
I didn't get the last sentence. Are you saying that the master fader does not work? Or does the DM3 not have a dedicated one?
Thanks so much for the response. Yes, it is very surprising that Yamaha support HUI but I expect the issue here is that they are very keen on backward compatibility with their mixers, the various models strive to have a common user interface because obviously when sound techs are working across different environments, they are already (hopefully) familiar with other Yamaha desks.
I personally expect Yamaha to sell quite a lot of these because they are a fairly unique solution in that the desk is very compact but still has 16:8 analogue I/O plus 18:18 USB audio channels and I can say that I am very happy with mine, it's a fantastic piece of kit.
So anyone wanting to use one with Reaper - and that may well be a lot of people - are probably going to turn to your excellent plugin as this looks like by far the best option for DAW integration right now. Of course the integration with Cubase is a little bit better but that's just the way it is, I guess.
Regarding the comment about the master fader. The partial support HUI plugin for Reaper has a surface offset parameter (0 = first fader = master, 1 = first fader = first track) that allows the master fader to be the first fader (i.e channel 1).
I can't see any way with your plugin to do this so that I can control the master fader at all. The master fader on the DM3 is not coupled to the control surface because - understandably - it's controlling the mixer output levels.
Anyway - having written two control surface plugins myself - I want to express my appreciation for your hard work. I see that you put the source for the Bitwig version on github. Is the Reaper version source available?. I would certainly be willing to look at augmenting it to add some of the missing stuff and of course release it back under the LGPL, if this was acceptable to you. This would be a lot less work that reimplementing a solution from scratch. I would just target it specifically at the DM3 I think.
Sorry, I mis-spoke about the master channel. I see if you bank switch right it appears at the very end of all the channels in the project, which I missed, because it ends up in the middle of the bank and I didn't spot it. Apologies, I am a stupid person
Sorry, I mis-spoke about the master channel. I see if you bank switch right it appears at the very end of all the channels in the project, which I missed, because it ends up in the middle of the bank and I didn't spot it. Apologies, I am a stupid person
Don't worry, this is complex stuff :-)
I decided against publishing the adapter between Reaper C++ and Java side since this is quite complicated and I have no time to support this.
Regarding your other wishes, as I wrote, I will look into this sooner or later.
It is possible on some Launchpad models but up to my knowledge not on the Mk2.
Or maybe then change the background on the chords, for example (all 64 pads are burning white, it's unbearable), pick up a dimmer color, and not as now, as if they shine a lamp in the eyes - they torture))) Or can I make such a setting in the menu to change the color?
I Tried to install DBM in mac os Monterey 12.6.4 and I can set up it as a control surface, then i can set up my Komplete kontrol s61 mk2
But after I close Reaper in the next opening its starts to hang at "initializing main window" (right after setting up remote services)
I use the latest DrivenByMoss4Reaper realese (also tried previous installations and they perform the same)
if i remove reaper_drivenbymoss.dylib from the user plugins folder reaper starts
Also I found that if I choose -None- as an audio device Reaper starts, and I can use DBM too without any problem (I just have to set my real audio device and don't forget to set it back to none when i quit Reaper)
I Tried to install DBM in mac os Monterey 12.6.4 and I can set up it as a control surface, then i can set up my Komplete kontrol s61 mk2
But after I close Reaper in the next opening its starts to hang at "initializing main window" (right after setting up remote services)
I use the latest DrivenByMoss4Reaper realese (also tried previous installations and they perform the same)
if i remove reaper_drivenbymoss.dylib from the user plugins folder reaper starts
Also I found that if I choose -None- as an audio device Reaper starts, and I can use DBM too without any problem (I just have to set my real audio device and don't forget to set it back to none when i quit Reaper)
Audio interface- UAD Apollo Twin X
I got this report already from some people but had no idea so far what to do about it. I already added several logging information which pointed in the direction of audio driver.
So, the info that it works with a disabled audio interface is a helpful information.
Since I cannot replicate this on any of my Mac test devices it could also be the case that this happens only with some audio drivers.
On Macos the Java MIDI implementation is broken in several areas (especially MIDI system exclusive messages) therefore I use a library CoreMidi4J. Maybe this causes some kind of a conflict.
I created a patched DrivenByMoss library which can run without CoreMidi4J. This might be helpful to test:
Replace the DrivenByMoss jar file in the drivenbymoss-libs folder with the file from the ZIP and move the file coremidi4j-1.6.jar out of the folder (or delete it).
Check what happens.
Also interesting would be to test with another audio driver, e.g. the on-board audio card.
I just tried to set up Kontrol MK2 and its in green in the java app but the DAW controls don't work. I clicked a button (which I don't remember), which caused the start, record, stop to play notes instead. Any obvious thing I didn't do in Reaper (Mac)?
I just tried to set up Kontrol MK2 and its in green in the java app but the DAW controls don't work. I clicked a button (which I don't remember), which caused the start, record, stop to play notes instead. Any obvious thing I didn't do in Reaper (Mac)?
Did you deactivate the MIDI ports of the Mk2 in Reaper?
Yeah. I do however have an activated Maschine mk2. Could that be a problem?
No real idea besides that. Could be that the different NI services are mixed up which happens some times. You could try to reinstall Komplete (the app) with the drivers.
Have deactivated input/outputs in MIDI devices setup.
Keyboard plays, but transport buttons do not work. In the debug device simulator they do work, via the mouse click of course.
Curious note, this problem is on my laptop. I have a desktop music rig where the transport buttons do work on a KKS61 MK1...BUT I never disabled the KKS61 in the MIDI setting...? Didnt come across that instruction until trying to get this installation to work.
Have deactivated input/outputs in MIDI devices setup.
Keyboard plays, but transport buttons do not work. In the debug device simulator they do work, via the mouse click of course.
Curious note, this problem is on my laptop. I have a desktop music rig where the transport buttons do work on a KKS61 MK1...BUT I never disabled the KKS61 in the MIDI setting...? Didnt come across that instruction until trying to get this installation to work.
I need to manage the MIDI ports myself in DrivenByMoss since the API in Reaper is too limited to use the ports via Reaper. Therefore, all MIDI ports used with DrivenByMoss need to be disabled in Reaper itself.
But the MkI is a different issue since the implementation takes over fully the USB connection to make it possible to write texts to the display. See all the additional installation notes and explanations in the DrivenByMoss manual (in the KK MkI chapter).
I was just poking around the Configuration settings, clicked on Project and poked around there but did not mean to save anything.
I have uninstalled DrivenByMoss and am now getting a warning of some kind regarding DrivenByMoss whenever I open the Reaper Project.
Extensions can store additional data to Reaper projects (e.g. SWS as well). If the extension is not present Reaper tells you about it. I am not sure if Reaper removes it when you simply store the project again. If not you can manually edit the RPP file. At the very end you find a section:
<EXTENSIONS
...
>
Remove it. Make a backup of your project file before doing this to be on the safe side.
I need to manage the MIDI ports myself in DrivenByMoss since the API in Reaper is too limited to use the ports via Reaper. Therefore, all MIDI ports used with DrivenByMoss need to be disabled in Reaper itself.
But the MkI is a different issue since the implementation takes over fully the USB connection to make it possible to write texts to the display. See all the additional installation notes and explanations in the DrivenByMoss manual (in the KK MkI chapter).
So, on my desktop music rig and its KKS61 where transport appears to work, I can expect it to be quirky because I did NOT disable the MIDI in reaper. It wont be until this weekend when I can see the results of disabling MIDI setup. Hope not to lose the transport functionality.
Any suggestions on diagnosing why transport buttons are not working on the laptop and its KKS49, where I have in fact disabled the MIDI setup?
Extensions can store additional data to Reaper projects (e.g. SWS as well). If the extension is not present Reaper tells you about it. I am not sure if Reaper removes it when you simply store the project again. If not you can manually edit the RPP file. At the very end you find a section:
<EXTENSIONS
...
>
Remove it. Make a backup of your project file before doing this to be on the safe side.
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)
Linear Mode
