KevinW
New Member
--------
Edit: I've attached a log.
(played cues until one got stuck, then quit QS, so it should be near the end)
--------
Hey guys.
Not sure if this is a bug or computer related, but I'm finding that when cues are set to flash and triggered rapidly, one tends to get stuck in the "on" position until triggered a second time.
Qs 2.1 build 358
Windows 7 32bit SP1 fresh install
Intel core duo, 2Gb ram
I can reproduce this issue using the computer keyboard or midi. I've confirmed that it's not the input hardware... Midi is sending the correct data, and the computer keyboard is releasing the key as it should.
If there is any place I can find logs or debug prints, let me know and I'll send them over. Hopefully it's just something I missed and easy to fix.
Thanks.
--
Kevin
Edit: I've attached a log.
(played cues until one got stuck, then quit QS, so it should be near the end)
--------
Hey guys.
Not sure if this is a bug or computer related, but I'm finding that when cues are set to flash and triggered rapidly, one tends to get stuck in the "on" position until triggered a second time.
Qs 2.1 build 358
Windows 7 32bit SP1 fresh install
Intel core duo, 2Gb ram
I can reproduce this issue using the computer keyboard or midi. I've confirmed that it's not the input hardware... Midi is sending the correct data, and the computer keyboard is releasing the key as it should.
If there is any place I can find logs or debug prints, let me know and I'll send them over. Hopefully it's just something I missed and easy to fix.
Thanks.
--
Kevin
Attachments
Last edited: