Hi everyone! I´m new to both reaper and the forum, so far impressed by both program and this amazing community!
It's honesty night and day, coming from protools.
I´m having real trouble getting my MCU pro to work with Reaper. I downloaded Klinke´s plugin but it just won't work. However, if I select HUI (limited) mode in reaper instead of Klinke´s MC, it gets the faders, pan knobs and track names working. Not much more than that.
When I turn on my MCU pro, its screen shows "loading HUI emulator"... I think this is because HUI was the protocol it used to work with protools (worked fine actually). Anyone knows if there´s a way to "reset" the unit so it stops loading that HUI configuration when it boots? I think that´s the reason why I´m having no success with Klinke´s plugin.
Thanks very much in advance!
EDIT:
I found the way to change it, very straight forward but I didn´t find it in the MCU pro´s manual, I guess I overlooked it. Found it in youtube: https://www.youtube.com/watch?v=_OqpCsvFEGE
Press the 2 first select buttons in the unit lets you select the operation mode.
Hi guys, i have the Faderport V2 for two years now and it was functioning 50% of the time, today i was on a mission to once for all fix this issue and then stumbled upon this thread. I downloaded MUC Klinke and installed as the instructions say and also updated my V2 and too my horror noting works now. Is there anyone who can help resolve this issue? I read on a different thread i must set my input and output to logic which confused me because i don't see in my setup. Here is the instructions i followed.
"I figured it out. Kinda.
I was originall using a NanoKontrol 2 as a surface controller for Reaper so I had to install MCU Klinke V0.8 to get it to work. PS. it sucks. But while I was reading about .DLL files I found the faderport 2018 uses the the MCU .DLL terribly. Anyway I changed which DAW the Faderport is going to use (by holding the Next button while starting it up) to the Logic setup and HOLY ******* **** it worked. Everything works. Its a little spotty when it comes to the stop button, but other than that its perfectly fine.
TLR - Download the MCU Klinke V0.8 ( havent tried V0.8.3) and change the Faderports input to Logic (hold down Next on startup and press mute ( I think?) and under control surfaces go to Mackie Control Universal Klinke and set the MIDI in/out to Faderport and Boom.
I use Reaper with a Mackie Control Universal Pro with appropriate extenders. Version 3.0.0. By the way, an upgrade to 4.x is unfortunately not possible as I found out.
I could integrate the "Mackie Control Klinke" tool with my Mackie Control and use the extended functions. But the connection does not work with my two extenders. I know the problem is known. It has been a while and I wanted to ask if there is already a further development?
As wonderful as the ""Mackie Control Klinke"" tool is, I use the generic Reaper connection because I need my two extenders.
I would be very happy if there is already something new in this regard or already
other solutions are on the way.
Regarding your recommendation I have installed "DrivenByMoss4Reaper ".
Everything according to instructions and I have to say that it does not work for me. The controllers do not do everything as described and behave very strange. Everything a little bit creepy. I took it out of my configuration immediately. So briefly for me no solution. I wonder how to implement it on Java today. There are better ones.
It's a pity that there is no extender development planned for "Klinke Tool". Which I can understand, because the development is connected with an extreme expenditure of time, which again is not recompensed at expenditures.
Just to say "thanks again" for your amazing plugin!
I've attached some studio photos to show how I'm now using it
It's actually worked out really well that there is the old version (for multiple units) and the new one as I've used the old one to give me 24 basic channels for mixing and then I've got another X touch on the left with the plugin window on a touchscreen above it and I use this with the much fancier new MCU version you did for mostly doing plugin control as the mapping function gives me exactly what I need and for actions etc Oh, and for the excellent folder option.
I'll donate a bit more again to you soon to reiterate on how important and powerful this extension has become to my workflow! Hope things are going well! All the best. MBN
__________________ subproject FRs click here note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
hmm. How do I donate to you now? I don't see a paypal link or anything.
__________________ subproject FRs click here note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
As far as I know the project can't be loaded in Visual Studio 2017 (but I havn't tested it by myself, I still using Visual Studio 2010 as I only use it to build the project and edit the files externally).
Bit late to this but FYI I have it opening and compiling on Microsoft Visual Studio Community 2019 Version 16.7.3.
In case anyone else is interested I've submitted a PR for this.
Last edited by plant-on; 11-04-2021 at 04:43 AM.
Reason: Add link to PR.
It seems that with the latest changes to Reaper that now have the delta solo feature when in Plugin Mode the following has happened;
The master fader no longer controls the DRY/WET mix, it now controls if delta mode is on for the plugin or not.
The flip button now flips between 0% and 100% WET/DRY instead of enabling and disabling the plugin.
While I think having support for delta mode would be great I'd prefer that it's activated by pressing (say for instance) Shift+Flip. I do really love swapping between 0-100% wet tho, but again, that could be Option+Flip (which would also move the master fader from 0% to 100%).
@klinke wanted to check, if I was to make this change would you accept a PR that restores the existing functionality? (and perhaps adds the new functionality if I have time...)
It seems that with the latest changes to Reaper that now have the delta solo feature when in Plugin Mode the following has happened;
The master fader no longer controls the DRY/WET mix, it now controls if delta mode is on for the plugin or not.
The flip button now flips between 0% and 100% WET/DRY instead of enabling and disabling the plugin.
While I think having support for delta mode would be great I'd prefer that it's activated by pressing (say for instance) Shift+Flip. I do really love swapping between 0-100% wet tho, but again, that could be Option+Flip (which would also move the master fader from 0% to 100%).
@klinke wanted to check, if I was to make this change would you accept a PR that restores the existing functionality? (and perhaps adds the new functionality if I have time...)
I just uploaded v0.9.0.3 with the bugfix and delta support from plant-on (@plant-on: thanks a lot for this). Important: This update works only with Reaper v6.37 (or newer).
This update contains also a bugfix from Carlos Nunes that avoid possible crashes when a window created by this extension is closed.
I changed the modifier keys, delta-solo is activated via ALT+FLIP (as you also press the ALT-key when using the mouse for activating delta-solo) and 0-100% Dry/Wet is toggled via SHIFT-FLIP.
I just uploaded v0.9.0.3 with the bugfix and delta support from plant-on (@plant-on: thanks a lot for this). Important: This update works only with Reaper v6.37 (or newer).
This update contains also a bugfix from Carlos Nunes that avoid possible crashes when a window created by this extension is closed.
I changed the modifier keys, delta-solo is activated via ALT+FLIP (as you also press the ALT-key when using the mouse for activating delta-solo) and 0-100% Dry/Wet is toggled via SHIFT-FLIP.
I've been using the X-Touch with Klinke extension for almost a year now, and have been very happy with. However, for some reason, when opening Reaper, an error message pops up...something like "MIDI Error, cannot open X-TOUCH" (sorry, I'm not in my studio, so I'm paraphrasing). As per instructions, I have X-Touch enabled for midi in and out under Klinke in the Control Surface preferences page, as well as in the midi device page. This is how it has been setup from the start.
I click "ok" on the error window, and it disappears, and the X-Touch/Klinke continues to work as before. So, I'm trying to figure out what may be causing the error message.
I recently installed the latest Reaper update, as well as a Windows 10 update...but I can't seem to find any setting that has changed, which would cause the midi error message.
On a related issue, I am planning to add a NI Komplete Kontrol S49 MK2 midi keyboard to my studio. I have read that adding ReaKontrol is required to give this keyboard some needed integration with Reaper...but there is no mention of this working along with an X-Touch with Klinke.
Is there anyone here who has the X-Touch/Klinke plus ReaKonrol NI KK S Series (or similar) running in Reaper? Just wondering if there are any issues.
As per instructions, I have X-Touch enabled for midi in and out under Klinke in the Control Surface preferences page, as well as in the midi device page.
If you use the X-Touch exclusively for Klinke you don't need it having enabled also in the MIDI device page, which probably causes the error (at least I get the same error here on Win 8.1 if I'm trying to enable a MIDI device in 'Control surfaces' and 'MIDI devices' at the same time.)
If you use the X-Touch exclusively for Klinke you don't need it having enabled also in the MIDI device page, which probably causes the error (at least I get the same error here on Win 8.1 if I'm trying to enable a MIDI device in 'Control surfaces' and 'MIDI devices' at the same time.)
Thanks for the reply. I did try disabling the X-Touch midi in and out in MIDI Devices, and the X-Touch did not work properly. I was trying every possible option last night...maybe after making that change, I did not restart Reaper (or something). I will try it again tonight...disable it in MIDI Devices, then restart Reaper and see if that works.
On a related issue, I am planning to add a NI Komplete Kontrol S49 MK2 midi keyboard to my studio. I have read that adding ReaKontrol is required to give this keyboard some needed integration with Reaper...but there is no mention of this working along with an X-Touch with Klinke.
Is there anyone here who has the X-Touch/Klinke plus ReaKonrol NI KK S Series (or similar) running in Reaper? Just wondering if there are any issues.
I can't imagine that this would be a problem. I've not tried this exact setup but I do have a number of midi devices working alongside each other and my MCU and they work fine together, including if they are both modifying fader values or values that the MCU is currently "watching".
Recording FX parameters in cc section of midi editor
Hello everybody,
Thank you again Klinke for this fantastic job! Maybe someone can enlighten me on a dumb question.
I use FX-Mode to control plugin parameters. I can see how to record automations but is it possible to record CC values in the Midi Editor via this mode?
I use an X-Touch (yes, another one....) and an Advence64 keyboard.
Thank you again Klinke for this fantastic job! Maybe someone can enlighten me on a dumb question.
I use FX-Mode to control plugin parameters. I can see how to record automations but is it possible to record CC values in the Midi Editor via this mode?
I use an X-Touch (yes, another one....) and an Advence64 keyboard.
Thanks in advance for your help
Maybe there is a JSFX script that send CCs, and you can control this slider, but it's not possible to do this directly.
It is now possible to control plug-ins on the master track. You
must select the master track via a self-assigned action or the
mouse, since there is no master track select button on the
hardware.
Bugfixes:
The track count for bank switching was incorrect if Anchors were
set in the Track Settings dialog, but the "Use Anchor" option was
set to No.
I use nanoKontrol2 and it works fine, is it possible to view/display which track is being controlled when moving to next or previous track set, as controller does not have display
I use nanoKontrol2 and it works fine, is it possible to view/display which track is being controlled when moving to next or previous track set, as controller does not have display
I'm using a BCR2000 with Klinke's plugin which also doesn't have a display.
I use BCManager (together with a virtual MIDI 'cable', loopMIDI) which includes a Mackie display emulation to show what's currently being controlled.
I'm using a BCR2000 with Klinke's plugin which also doesn't have a display.
I use BCManager (together with a virtual MIDI 'cable', loopMIDI) which includes a Mackie display emulation to show what's currently being controlled.
Thanks for the reply, sorry for delayed response.
Only issue noticed is if any track is set as folder subsequent child tracks are not controlled by nanoKONTROL2, any thoughts..
After reading below two forums was able to create a new UI which is docked on right side
If anybody happens to have the original Mackie Control Universal, I've created a full, and modifiable in Inkscape, overlay for Klinke's plugin. It was created from a scan of one of the original Lexan overlays.
I've yet to physically verify the sub-mm accuracy of all the button/LED/stud cutouts, as awaiting a set of hole punches from Amazon (£15). If anybody is interested, drop me a PM. I'll edit this message and post another response to this thread once any registration errors have been corrected.
Hi. I ‘m quite new to kiinke and mackie mcu pro but quite experienced with reaper.
So my problem is that i’m using a MCP with a track order totally different to the TCP. On the MCU editor show list i’ve chosen the tracks that are shown on the mixer and with the mcu options i’ve chosen Mixer (or even Macke set) but the track order is not the one i have set on my MCP.
Actually it’s more like the TCP order, minus the tracks i’ve chosen not to show in the MCP and MCU with the klinke editor.
Anything i’ve missed or it just can’t be done?
Perhaps that will help? If it does, please be sure to delete all old instances of the plugins from wherever they were installed prior to installing new plugin.
Perhaps that will help? If it does, please be sure to delete all old instances of the plugins from wherever they were installed prior to installing new plugin.
Thanks Cjpn.i’m sure it’s not the old plug ins instances, since i’ve only used the latest klinke release.
I’ll try the other thread.