Fader control Loss

Any control of all 10 is lost. Tried restart, shutdown. Only thing that will fix is a reboot. I thought this issue was addressed in V 2.3
  • Both single console and networked.
    Not my console so don't know update method performed.
  • I have had the same thing happen to me on v2.2 with single console (with client tablet). When I had DP8000's networked in I had to reboot the system to get control back. When outputting DMX from onboard DP I could pig-open-backspace and kill playback, then restart playback and got control.
  • My fullboar did get a fullinstall to 2.3.0.
    It happened on a single show, nothing hooked.

    Like i said, before i lost control on fader 1 i had the desk locked and the screensaver was on.
  • Hello everyone,

    Just an update, we finally got this to recreate in the test lab and I have our software guys looking into now.
    As soon as I know the cause and we have this fixed I will let you guys know.
    Thank you all for the information!
  • Hello All,

    We think we found the problem.
    Can you please do me a favor and the next time this occurs to you please send me the log file.
    We want to see if a certain message is present when this occurs.
    In our testing we see this "bad" message and we believe that is the cause.

    Pig+Open+1 and right click to save the file.

    Again thanks for all the help with this issue guys!



  • Michael
    i've just sent one log file to you.

    After reading your post i did a test while keeping the desk 20min locked and with screensaver on.

  • Can you please upgrade to 2.4.0 and let me know if it occurs again?
    We fixed a but where the faders would not respond after locking the desk in a multi-console setup.
    Just want to see if this is in fact the defect y'all are running into.
    We have found another edge case and are working to get the fixed.
  • Thanks, I already have, I'll let you know
  • So I had the faders lock today, tried the pig+open+1 and could copy but not paste. Probly something I'm doing wrong there. But in the past only a restore would fix the issue. This time a soft reset fixed the issue.
1 2 3