Hi all,
I have a problem I just cannot understand, I hope you guys have an explanation, or even a solution! This is my problem:
I have a Novation Impulse connected to my PC via USB using Reaper 5.80 X64.
On my Impulse there is a Nord Lead 2 connected via the MIDI INPUT. This is possible, because the Impulse has a built-in MIDI interface.
I don't use Automap and assigned all faders and knobs via 'Actions'.
Fader 1-8 are assigned to control Volume Faders of Track 1-8 and they work just fine. They are all very responsive.
Fader 9 (CC#49) is assigned to 'Automation Lane: set active fader (MIDI CC/OSC only). This is a great idea, so I can use Fader 9 to write automation over MIDI. It works in Trim/Read mode, however... as soon as Automation Mode is set to Write or Touch it introduces an annoying delay between moving the fader and the actual response. It is getting slow and jerky and this is also perfectly visible when I click on 'Sends' on the Track. The fader jumps around.
Now, when I assign a knob from my Nord Lead 2 to 'Automation Lane: set active fader (MIDI CC/OSC only) there is no problem at all! The fader remains very responsive, also in Write- and Touch mode!
The faders on the Impulse are set to CC and send values from 0-127.
I compared the difference between the two MIDI outputs in MIDI-OX, but could not see any strangs things happen.
So why does Reaper has this terrible delayed, jerky behaviour when I assign a fader to 'Automation Lane: set active fader (MIDI CC/OSC only) when I want to control 'Send Volume' or 'Send Pan'?
And why doesn't the problem doesn't occur when the Nord Lead 2 is been used instead of the MIDI output of the Impulse.
I tried to solve the problem by connecting my Impulse to the MIDI input of my HDSPe AIO, so no USB connection was used, but nu luck.
There is a technical difference between the MIDI CC's of the Impulse and the Nord Lead 2, but I really can't find out what the heck is going on.
Please enlighten me!
Automation Issue with Send Volume/Pan in Reaper
-
- KVRist
- 151 posts since 24 Nov, 2011
i7-9700K @ 4.6 GHz - Asus Prime Z390-A - Corsair DDR4 32 GB 3600 MHz - Samsung 970 EVO Plus 500 GB - RME HDSPe AIO + XLR balanced breakout - 2x Iiyama PL2492H - Arturia Keylab Mk3 Black - Evolution UC-16 - Clavia Nord Lead 2 - Yamaha S80
-
- KVRAF
- 7115 posts since 22 Jan, 2005 from Sweden
Could it be CC#49 is used for something else, as well that make Reaper choke.
Looking in manual for my NL2X - CC#49 is not used anywhere, so you probably use something else, right?
I would try any other controller and see.
Looking in manual for my NL2X - CC#49 is not used anywhere, so you probably use something else, right?
I would try any other controller and see.
-
- KVRist
- Topic Starter
- 151 posts since 24 Nov, 2011
Thanks for your reply!
No, CC#49 is the one on my Impulse.
If I assign the Impulse to the CC which Nord Lead 2 uses (and works flawlessly) the problem is still there.
It is something weird inside Reaper. I posted this question on their forum, but unfortunately no reply there...
No, CC#49 is the one on my Impulse.
If I assign the Impulse to the CC which Nord Lead 2 uses (and works flawlessly) the problem is still there.
It is something weird inside Reaper. I posted this question on their forum, but unfortunately no reply there...
i7-9700K @ 4.6 GHz - Asus Prime Z390-A - Corsair DDR4 32 GB 3600 MHz - Samsung 970 EVO Plus 500 GB - RME HDSPe AIO + XLR balanced breakout - 2x Iiyama PL2492H - Arturia Keylab Mk3 Black - Evolution UC-16 - Clavia Nord Lead 2 - Yamaha S80
-
- KVRist
- Topic Starter
- 151 posts since 24 Nov, 2011
Deleted
i7-9700K @ 4.6 GHz - Asus Prime Z390-A - Corsair DDR4 32 GB 3600 MHz - Samsung 970 EVO Plus 500 GB - RME HDSPe AIO + XLR balanced breakout - 2x Iiyama PL2492H - Arturia Keylab Mk3 Black - Evolution UC-16 - Clavia Nord Lead 2 - Yamaha S80