Show Cue System

Hi,

We found two strange behaviors on SCS 11.6 RC4.

1. We tried to change the level of a playing audio cue with the mouse wheel. When we turn the mouse wheel on the fader in the cue panel without focusing the fader before the level sometimes makes an unexpected jump of several dB. Sometimes it even jumps in the opposite direction than expected. But sometimes the level also changes as expected. If you focus the fader first by clicking on it, it also behaves as expected with the mouse wheel.

2. If you press spacebar to start a manual cue and keep it pressed for too long a second cue is fired. A third cue is no fired if you keep it pressed even longer.

Unfortunately we are currently live with the show so I do not want to update to RC8 right now. Therefore I'm not sure if RC8 behaves the same way, but I found nothing corresponding to this in the release notes.

Regards Veit

FBB wrote:1. We tried to change the level of a playing audio cue with the mouse wheel. When we turn the mouse wheel on the fader in the cue panel without focusing the fader before the level sometimes makes an unexpected jump of several dB. Sometimes it even jumps in the opposite direction than expected. But sometimes the level also changes as expected. If you focus the fader first by clicking on it, it also behaves as expected with the mouse wheel.

Fixed in RC9. (This mouse wheel error also exists in 11.5.3 and earlier versions.)

FBB wrote:2. If you press spacebar to start a manual cue and keep it pressed for too long a second cue is fired. A third cue is no fired if you keep it pressed even longer.

Fixed in RC9.

Thanks for finding and reporting these errors! I was just preparing to issue 11.6.0 on general release when your bug report came in.

FBB wrote: ↑

Mon Mar 13, 2017 8:27 am

2. If you press spacebar to start a manual cue and keep it pressed for too long a second cue is fired. A third cue is no fired if you keep it pressed even longer.

We're having this problem. Is it a bug or is there a setting?

11.7.1.3

That's strange, since it was apparently fixed in 11.6. I've emailed you regarding this.