Edit multiple cues together

[Jean Bono]

Hello

I'm running a show with qlab3 and would like to edit the volume of multiple cues together

I'm sending some text in the actors earpieces with a little bell sound to warn them the cue is coming

The volume for the bell is too loud at the moment

is it possible to change all the levels at the same time or should I manually do it?

Thanks for the replies

Jean

[Chris Ashworth]

Hi Jean,

Currently the only ways to edit multiple cues at the same time is by using scripting or sending OSC messages that address multiple cues.

If you have very many cues to edit I could describe those techniques further — if you have relatively few to edit, it’s probably faster to edit them directly.

-C

[Jean Bono]

Thanks Chris

I don't have much time to look into scripting so i'll just do it manually

Thanks for the quick response though

[micpool]

In this specific instance the obvious thing to do is just edit the source bell audio file to be 10db quieter or whatever.

You can adjust one cue and copy its levels. You can then select all the bell cues manually by command clicking them and paste the levels to all simultaneously.

If you think you are going to need to adjust the level of this bell a lot you could use an output you are not currently using and send the bell to that output instead of its normal earpiece output e.g cie output 48. You can do this with the cut and paste method above

You can then use the device matrix to send output 48 or whatever you have used to your earpiece output. You now have a knob which acts as a master for your bell warning sound.

Mic

[Jean Bono]

Hi mic

thanks for your reply

I like the idea of using a different output for the bell, I'll try to remember it for next time

I tried to edit multiple cues by selecting them and changing the level but it didn't work, only the last cue selected got modified

Any tip of what I'm doing wrong?

Cheers

[micpool]

On Friday, October 24, 2014 12:21:48 PM UTC+1, Jean Bono wrote:

I tried to edit multiple cues by selecting them and changing the level but it didn't work, only the last cue selected got modified

Any tip of what I'm doing wrong?

Yes you can't edit multiple cues directly but in Qlab3 you can copy and paste levels to  multiple cues.

1  Adjust levels in one cue

2  Menu Tools/Copy Levels (shift cmd C)

3 Select all cues you want to change to the new levels by cmd clicking

4 Menu Tools/Paste Levels (shift cmd V)

All cues will now be at the new level.

[Jean Bono]

Ah cool

I was just doing cmd c without the shift

Thanks for the tip mic

[Vinny Osborne]

WHAY CANT YOU EDIT MULTIPLE CUES.  IT SEEMS IT A BIT CRAZY AT THIS STAGE.  Surely we should be able to select multiple cues and change volume, outputs, colours etc.  I think Qlab maybe the only program on my PC that I cannot do this!

[Bruce Ellman]

For future reference, what I suggest for a way to handle a cue that is repeated numerous times is to put it into a separate "FX" list (or "MUSIC" list) and use "start" cues in a main cue list. This way you can adjust the level once in the "FX" list for all instances that it's called. I use a prefix in all ancillary lists and try not to use a prefix in the main list. 

For instance cues 5, 20, 25, etc. in the main list could all be "start" cues targeting cue FX5 (bell.aif) in the FX list. To lower the level of all the bell cues you just need do it once in the FX5 cue in the FX list.

Bruce

[Tom Quinn]

...Now there's an idea that's never occurred to me, that's great, thank you!

------------------------------------
Tom Quinn
T...@battle4heaven.com
877-793-5175
www.battle4heaven.com

--
--
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 the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jean Bono]

I was gonna argue that in my situation it is a bit more complicated as I have to send this bell sound to three actors through their in-ear monitor and I want to send it to just one at a  time so I control thet output of the bell cue which I can't do if I just use start cues

But then I can just have 3 bell cues in the FX lists, bell 1, bell 2 and bell 3.

It's a great workaround

Thanks guys

Le jeudi 23 octobre 2014 15:00:14 UTC+1, Jean Bono a écrit :

[Lucas Krech]

With a few less caps but equal confusion I must say I do not understand where the complexity in this problem lies. I know I am not a programmer so I am probably missing something obvious but, QLab already allows for editing multiple cues in the form of moving and deleting. How much harder is it to loop through that set and change a value? 

It should be relatively simple to build an external application which does this in AppleScript or OSC. But at the point that that is possible why not in QLab itself? If I can write a script that allows for "repeat with eachCue in selected of front workspace" how is it prohibitively difficult to bake into the software proper?

I feel I must be missing something obvious here. Please help me out. 

-L

*insert witty mobile device advertising here*

--

[Christopher Ashworth]

If memory serves, the recent (fairly extensive) discussion of this topic on the mailing list covered the challenges and possible solutions fairly well.

Summary: your internal guesstimate of the challenges is inaccurate when applied in a more rigorous way for all properties of cues. It is especially inaccurate when trying to make UI built to edit one cue work with many. These difficulties may be substantially reduced if we introduce an alternative UI for batch editing, some versions of which may well be a good final solution.  There were some creative and helpful suggestions about ways we might do it in the recent discussion. Even so, there are design and usability tradeoffs to consider, and the whole thing is not the simple problem it may seem. 

(mobile)

On Oct 25, 2014, at 12:52 PM, Lucas Krech <des...@lucaskrech.com> wrote:

With a few less caps but equal confusion I must say I do not understand where the complexity in this problem lies. I know I am not a programmer so I am probably missing something obvious but, QLab already allows for editing multiple cues in the form of moving and deleting. How much harder is it to loop through that set and change a value? 

It should be relatively simple to build an external application which does this in AppleScript or OSC. But at the point that that is possible why not in QLab itself? If I can write a script that allows for "repeat with eachCue in selected of front workspace" how is it prohibitively difficult to bake into the software proper?

I feel I must be missing something obvious here. Please help me out. 

-L

[micpool]

It's barely 3 months since we had a similar discussion on this group

Search for the thread: speaker assignment problems

Chris explained the difficulties in implementing this then.

Bearing in mind the major amounts of work that have gone into the release and subsequent refinement over 5 minor releases of 3.1 isnt it really a bit unrealistic to expect a solution to this problem which clearly is not trivial to implement so soon.

We are very fortunate in having Chris's detailed and honest input on this forum. Would that I had the same sort of access to the chief architects of ProTools or Adobe! Let's not abuse this with unrealistic expectations of time frames or shouty posts.

The original poster has at least four very workable solutions to his specific problem as a result of posting here, which may well be of use to others in the future.

Mic

[Lucas Krech]

I recall that discussion but was (obviously mistakenly) under the impression that there was no useful concept of selectedCues in your data model and that was the major structural impediment. Given such functionality exists I don't see where the problem lies. I made suggestions on UI changes in that previous convo but no longer think they are relevant. From a user POV I don't see any need for UI changes in order to implement batch editing. 

I presume there is something more esoteric going on that I just do not see. 

-L

*insert witty mobile device advertising here*

[Dave "luckydave" Memory]

On Saturday, October 25, 2014 at 11:17 AM, Lucas Krech wrote:

I presume there is something more esoteric going on that I just do not see. 

Not for nothin', but this is the story of software development. I think Mic put it well, but I'll restate my own way: if it were easy, it would already be implemented. We're not avoiding it for fun, or for the thrill of frustrating people who use QLab. It's not easy.

-- 

luck...@figure53.com

[Jeremy Lee]

I do this all the time with some scripts generously shared by Rich Walsh on the figure53 website

On Oct 24, 2014, at 8:45 PM, Vinny Osborne <the...@eircom.net> wrote:

--
--

-- 

Jeremy Lee

    Sound Designer - USA 829

        http://www.jjlee.com