In live mode on the start of a show, the keyboardtriggering of a scene works ok.
But after a while running a scene without any userinterference, the program does not react anymore on a keyboardtrigger.
Both to activate another scene, aswell as ending the running scene.
Using a mouseclick on the livescreen will bring-back the keyboardtriggering.
But only for a few minutes, and the againg not responsive....
I'm using WIN10 on a laptop. Dongle present or not does not make a difference.
In my experience, this issue was not present in the may version?
But it is already present in the nov. beta and now still in the december release.
Keyboard scenetriggering inactive after appr. 10 minutes
Re: Keyboard scenetriggering inactive after appr. 10 minutes
Hey,
Could it be that the software loses focus for some reason ? Does any other application on your computer happen to take over at any point, or any window pop-up ?
Regards,
Could it be that the software loses focus for some reason ? Does any other application on your computer happen to take over at any point, or any window pop-up ?
Regards,
TomHat
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
--
Daslight Support
Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
Re: Keyboard scenetriggering inactive after appr. 10 minutes
As far as I know, there are no other apps running. Also, I do not switch the screen.
But, maybe a background process could cause this behaviour?
I'll check and come-back later.
Thanks for your response.
But, maybe a background process could cause this behaviour?
I'll check and come-back later.
Thanks for your response.
Re: Keyboard scenetriggering inactive after appr. 10 minutes
Searching WIN10 forums has learned me that loosing focus happens sometimes in various cicumstances.
One solution I have found is adapting a entree in the register.
Run regedit a admin
Search for HKEY_CURRENT_USERControl Paneldesktop
Alter ForegroundLockTimeout (default: 0x00030d40 = decimal 200000)
Set up a higher value: 0x001e8480 = decimal 2000000
Is ten times higher value, and it works fawlesly. Running a scene for more than one hour and then triggering another scene with a keyboard shortcut : Perfect!!
Maybe a solution for other users with this kind of problems!!
One solution I have found is adapting a entree in the register.
Run regedit a admin
Search for HKEY_CURRENT_USERControl Paneldesktop
Alter ForegroundLockTimeout (default: 0x00030d40 = decimal 200000)
Set up a higher value: 0x001e8480 = decimal 2000000
Is ten times higher value, and it works fawlesly. Running a scene for more than one hour and then triggering another scene with a keyboard shortcut : Perfect!!
Maybe a solution for other users with this kind of problems!!