False Triggers

[Oddjob]

Hi all,

I have been using Showcue with great success and am very impressed. However, when triggering a cue by pressing the space bar yesterday (an audio cue), it immediately paused by itself after 1 second or less but the timer showed 1 sec, and also before that on a different occasion (midi note on/off), on triggering it jumped to the following cue seemingly by itself.

The second jumping cue may have been caused by holding down the space bar a fraction too long, so I have increased the delay from .4 sec (default) up to 1 second.

However I can't seem to fathom out the pause. I have run the show though again a number of times on trial with a diagnostic dump file running but it acts OK. Obviously the command for pause is CTRL + U, so that can be discounted and the mouse is kept on a shelf away from the operator to avoid accidents.

I am running a wireless keyboard and mouse. I have had a thought that perhaps the broadband wireless router which is within 1 metre of the PC tower may be upsetting the wireless receiver in the USB port, they are in the same frequency band, so I am relocating the router tomorrow. Doesn't quite add up though. I am going to also replace the keyboard and mouse in case those are the offenders.

I will continue to run a diagnostic dump file for a while in case it happens again. I have the Pro edition with the latest software 11.4.2.3.

I would appreciate any suggestions.

thanks
Geoff.

[Mike Daniell]

The second jumping cue may have been caused by holding down the space bar a fraction too long, so I have increased the delay from .4 sec (default) up to 1 second.

Coincidentally, we stumbled on that same problem a few days ago. That is a bug which I have now fixed for the next release. Unfortunately increasing the delay will probably not help. The solution we adopted on encountering the problem was to switch from using the space bar to using right-click on the laptop's touch-pad buttons. We also placed a sticker on the right button to make sure the operator pressed the right button and not the left button.

Is it possible the other problems are related to holding down a key too long?

[Oddjob]

Hi Mike,

No I don't think the pausing would have been caused by holding the key down too long. The cue advanced to the next manual key as normal. The audio cue that paused virtually straight away was set to fade out in about another 10 cues so there was nothing to tell it to pause. The following cues after the one that paused had no relationship to it.

I assume the delay is meant to counteract contact bounce or quick double hitting of the space bar not being slow releasing it, or indeed a sticky switch.

So setting a longer delay won't help if the key is held down a bit too long. Have I got that right?

I could use the right hand button of the mouse to trigger the cues, but that doesn't explain the pausing.

I shall continue with relocating the modem, which has to be done anyway, replacing the keyboard and running the diagnostic dump file.

When do you think the next release will be to fix that bug?

Geoff.

[Mike Daniell]

Geoff,

Could you email me a diagnostic file? You can create this file by selecting 'Create Diagnostic File' from the drop-down menu displayed when you click the Help button in the main window. The file will be saved in a folder named "SCS Diagnostics" under "Documents" or "My Documents". Please tell me which cues are causing issues.

[Oddjob]

Diagnostic dump file emailed.

Geoff.

[Mike Daniell]

Geoff,

Thanks for the diagnostic file, but I can't see any reason for the cue to pause. I've emailed you details of a tracing version to run so if the pause does occur again then the associated log file should help identify why the cue paused. This tracing version also includes the fix for holding down the space bar too long.