OSC not triggering while RPU Primary is Locked

Question

Hi, 
 We have an Apex RPU acting as our primary in the dimmer room (KVM'd into the control room) and a Apex5 as the backup / operators console. 
 Last week we decided to lock the RPU when not actively using the keyboard to prevent accidental keypresses. What we discovered is that incoming OSC does nor trigger as EOS if the console is locked. 
 On one hand this is a good feature during a technical rehearsal tea break, on the other hand it seems a little restrictive for remote consoles you may want to protect. 
 Is this a bug? 
 Is it possible to enable OSC triggering while a console is locked. If it is not possible, could we as the user decide this option in the future. 
 Many thanks for your help in advance. 
 Tim Owen 
 EOS 3.2.10.36

Matt Pumplin · Answer

Hello tim owen , this is a known issue in current and previous software. It's written up as 
 [EOS-54272] Some OSC commands are blocked when Primary is locked out but should not be 
 I don't have a complete list of which commands are blocked, but it seems as though Events are not locked out, so you might be able to re-rig your OSC commands to get around this. As a first step, you could experiment with causing your OSC input to be a different User# than the RPU Primary - it seems like more commands get through that way, though still not all of them. 
 I'll update that SCR to say you're continuing to run into this, but there is currently no timeline for it to be addressed.