Auto stop cues - could we get this...?

[Johannes Halvorsen]

I love the flexibility of Qlab, and I understand that having to explicitly stop/fade cues is a design decision.

HOWEVER: Not having the option of specifying "fade and/or stop me after x seconds/loopings/when next cue of same or given type fires/when something else tries to output to the surface or sound device I am using/etc." ads a lot of extra clutter and work when working with a linear show.

I wish for this kind of OPTIONS to be added in the future. I don't think it's good workflow design that one MUST use three cues to do what could be done with just one. By all means, keep it the way it is today as default behavior, but please ad some options to tidy up the cue list when that level of fine grained control isn't strictly necessary. :)

Thanks for a great progra!

[Jevans]

QLab is not PowerPoint or KeyNote, and as I understand it the design has very explicitly been the opposite of what you describe - QLab provides the tools in what you might describe as a "Turing complete manner" ie. with the basic cue types and tools QLab gives you you can construct anything, but you might have to do some work to do it. This keeps the actual design of QLab itself and the cue types very simple - each cue type can be completely explained within a couple of minutes to someone, as there's not pages and pages of options for each cue. If Chris and co. added every single option to cues that people asked for the interface would very rapidly be a mess, so thought has to go into what's provided.

The options you describe "fade and/or stop me after x seconds/loopings/when next cue of same or given type fires/when something else tries to output to the surface or sound device I am using/etc." are not simple and would surely add at least a tab of cue options. Also: more code => more bugs to fix!

If inserting a particular sequence of cues that you use all the time is annoying then you can build a script that inserts them for you on a hotkey or something. Use QLab's tools to your advantage and you will find that programming becomes much easier.

Thanks,

John

[Johannes Halvorsen]

I do understand the nature of Qlab. :)

Good tip about making an auto-insert-sequence-script. Thanks!

I do, however, stil stand by my wish for some built in mechanism for easy (read lazy ass) deployment of linear cue sequences. A simple "stop que after 1 playback"-tick box for audio/video cues would go a long way. I simply disagree with the idea that this would incurr lots of bugs or added complexity.

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/EWRgY1lkhys/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sam Kusnetz]

Johannes Halvorsen wrote:
> I do, however, stil stand by my wish for some built in mechanism for
> easy (read lazy ass) deployment of linear cue sequences. A simple
> "stop que after 1 playback"-tick box for audio/video cues would go a
> long way. I simply disagree with the idea that this would incurr lots
> of bugs or added complexity.

If you have an Audio cue that plays a track that's, say, 30 seconds
long, it will stop itself after 30 seconds; one playback. If, in the
Time & Loops tab, you set it to play through twice, then it will stop
itself after one minute; two playbacks. This is the same for Video cues
*unless* you check the "Hold at end" box, which will automatically pause
the video on the last frame.

Perhaps QLab already does what you need?

Cheerio
Sam
--
Sam Kusnetz | Figure 53 Field Operative
s...@figure53.com

[Johannes Halvorsen]

Oooo... I didn't know that. Just assumed I had to stop the cues no matter what. That goes a long way; thanks!

(Feeling a bit stupid now...)

[luckydave]

On March 15, 2015 at 1:41:51 PM, Johannes Halvorsen (johan...@gmail.com) wrote:

> Oooo... I didn't know that. Just assumed I had to stop the cues no matter what. That goes a long way; thanks! 

The exception is for still images, which since they don't have a duration, can't stop themselves. The same holds true for a loop, but of course that can't stop itself.

-- 
luckydave

[friendlygiraffe]

When reacting to an audience, sometimes It would be nice to skip halfway through an audio/video cue.

But stopping/killing off the previous cue would be with images is needed