View Single Post
Old 11-24-2013, 09:57 AM   #22
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
Default

-update2-
No bad occurance after the restart. Updated the drivers as well just in case (RME FF UC 1.038 Firmware 118).

Looks like the midi driver might have crashed or screwed up.
The MCU could receive data from Reaper, as faders moved on the control surface when I pushed them around in the GUI, but Reaper did not appear to react to any data from the MCU. The RME unit was showing midi activity, but Reaper wasn't getting anything I suppose.

Will report back if trouble starts up again. The machine had been on for more than a day when this problem occured.
-------------------------
-update1-
An actual godamn restart seems to have fixed the situation, though I've regressed to 4.55 as well. Now testing the newer release again.

Maybe the midi driver is buggy. Checking for drivers updates as well.

-------------
The problem with the MCU control surface is not getting better.

Reaper had trouble even talking to the MCU, so I tried uninstalling Reaper and reinstalling it. Not it appears to work, but ah, it actually doesn't.

It did jump to the right tracks and lit up the SELECT button according to which track I had selected, but when I rolled transport and attempted to record volume automation, nothing at all happened.

Then SELECT'ing another track didn't work. Fader touching wasn't recognized.

After a little while everything began working again, or so it appeared.

Still, no fader movement is even recognized.

Now attempting to go back to a previous version that will hopefully work.
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom

Last edited by airon; 11-24-2013 at 10:25 AM.
airon is offline   Reply With Quote