Wed Jul 21, 2021 12:01 pm
Just a though .
Historically (from DR12.5 till as recently as i can remember) there have been on and off issues where some standard Resolve keyboard mappings have overlapped some of the printerlight mappings. So enabling one would disable the other etc. Typicaly mappings change(d) depending on if PL was off or on so even worse. In some periods it totaly borked one of the printerlight funcions with the out of the box mapping at least on Mac's (i know because i had to build/fix all kinds of bypasses to fix that for my automation, which typicaly avoids keyboard macros like the plague, but for printerlights the nature of the beast "IS' keyboard control).
So maybe you are using a keyboard shortcut that is somehow double mapped to disable/enable printerlights.
I would check the mapping carefully and see if there is anything like that going on.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME