Has anyone else ever had the problem of Qlab functioning just fine most of the time, but then occasionally failing to trigger a cue immediately when one hits "Go"?
I've experienced this in several different theatres by now, as a sound board op and as a designer. I've more or less never used Qlab to trigger anything but audio, because the jobs I tend to do are so low-budget that there is not a need for especially complicated tech. But it is often the case that audio cues-- such as door slams-- must happen (ideally) at the precise instant there is an onstage action-- such as an actor slams a door. And in my experience with Qlab, there are always a few shows when there is a very small delay after pressing "go" before the cue is fired, or worse, one presses "go" and the cue doesn't fire at all; you have to hit go again. And it ruins the effect onstage.
Usually I use hotkeys to trigger cues, e.g. the keyboard spacebar is "go". But I have also tried clicking the Go button in the Qlab window, and I have tried assigning different hotkeys on the keyboard. It's the sort of thing that my board ops will complain of, but when I go to try and fix it, everything works fine. But I believe them, because I've had it happen to me too.
Is this an issue of the hard drive going to sleep during long breaks between cues? Is it a Qlab bug? Is it that all the computers I've ever used just so happen to be a bit old and this is therefore to be expected? Or am I the only one this has happened to?
I've experienced this in several different theatres by now, as a sound board op and as a designer. I've more or less never used Qlab to trigger anything but audio, because the jobs I tend to do are so low-budget that there is not a need for especially complicated tech. But it is often the case that audio cues-- such as door slams-- must happen (ideally) at the precise instant there is an onstage action-- such as an actor slams a door. And in my experience with Qlab, there are always a few shows when there is a very small delay after pressing "go" before the cue is fired, or worse, one presses "go" and the cue doesn't fire at all; you have to hit go again. And it ruins the effect onstage.
Usually I use hotkeys to trigger cues, e.g. the keyboard spacebar is "go". But I have also tried clicking the Go button in the Qlab window, and I have tried assigning different hotkeys on the keyboard. It's the sort of thing that my board ops will complain of, but when I go to try and fix it, everything works fine. But I believe them, because I've had it happen to me too.
Is this an issue of the hard drive going to sleep during long breaks between cues? Is it a Qlab bug? Is it that all the computers I've ever used just so happen to be a bit old and this is therefore to be expected? Or am I the only one this has happened to?