Bug in routing window (concerning receives) (FIXED)

[SonicAxiom]

Reaper v5.21 x64, Win7 x64 SP1

after creating a send from one track to another, then opening the resp. routing window of the receiving track, the receiving level fader does not reflect movements made to the send level fader while the numerical level change is reflected.

[Dstruct]

Confirmed (5.21 x64).

FIXED (5.22pre2)

[Justin]

to be fair that ''keep routing windows open" option in advanced prefs is probably still marked "experimental"... but I'll look at fixing this anyway

[Dstruct]

Thanks!

[SonicAxiom]

Originally Posted by Justin

to be fair that ''keep routing windows open" option in advanced prefs is probably still marked "experimental"... but I'll look at fixing this anyway

Thanks for taking your time, Justin. I didn't even remember having this option set in the advanced prefs. Fixing this minor glitch is very low priority. I only discovered it by accident while demonstrating Reaper's glorious routing capabilities to a collegue and he went "oh, look, fader doesn't even move" :-)

[SonicAxiom]

Originally Posted by Justin

to be fair that ''keep routing windows open" option in advanced prefs is probably still marked "experimental"... but I'll look at fixing this anyway

Thanks for the quick fix, Justin!

May I ask your help regarding another very particular issue I'm having for the last two weeks?

I have a Focusrite RedNet PCIe Dante card in a Win7 x64 desktop pc (intel i5 quad 8 gb of ram). The issue is that (almost) every time I restart Reaper, I get "audio device disabled" and I have to then first choose another audio device (RME Babyface in my case), then shut down Reaper, restart it, choose RedNet PCIe again and even have to reassign the no. of in outs (RedNet PCIE has 128 i/o of which I need 22 ins and 26 outs). Any idea why Reaper forgets about the card - at least 90% of the time: on very rare occasions, the card is still there when I re-launch Reaper.