Targeting 2nd workspace cues

[David Wilson]

We will be teching sound and video on separate computers, then merging the shows onto one for the run. The sound workspace will trigger the video workspace. How do I write the cues in sound workspace to trigger cues in video workspace?

[Mike Post]

Hi David,

It’s a bit simpler (IMHO) to merge them into one workspace with the Video cues in a separate Cue List.  Here’s a link to the manual page for cue lists.

https://qlab.app/docs/v4/general/cue-lists/

Once you have a list created for your Video cues, you can copy and paste them.  You will most likely have to redefine the surface(s) for the workspace.

Alternately if it’s simpler, you could create a list in your Video file for the Sound cues.  You can play back from an alternate list pretty easily.

Once you have that done, you can use the Start Cue in the Sound list to trigger cues in the Video list.  It looks like a “Play” symbol.  If you are in your Sound cue list and create a Start Cue, you can display the cues for your Video in the List display and just drag and drop to target.

Hope that helps!

Mike Post

mdp...@mac.com

http://mdpostdesign.com

On Dec 23, 2021, at 11:31 AM, 'David Wilson' via QLab <ql...@googlegroups.com> wrote:

We will be teching sound and video on separate computers, then merging the shows onto one for the run. The sound workspace will trigger the video workspace. How do I write the cues in sound workspace to trigger cues in video workspace?

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/7050a803-5a7e-4f4d-80cc-753de0b06b8fn%40googlegroups.com.

[micpool]

If you use 2 QLab 4 workspaces 127.0.0.1 and localhost will be treated the same. If you want to address one workspace from the other you have to use the full address for the method e.g.
/workspace/AnotherWorkspace/cue/1/start.

[David Wilson]

OK, I tried this, and good to know it's possible to copy and paste the video cues into a 2nd cuelist. Is there anyway to avoid having to re-target the video files themselves, and the surface? Not a giant deal,

but will take some time with 100-200 cues to re-target. That's why I was hoping for a dual workspace solution as the video would all be nice and tidy in it's own folder and sound workspace would just be

giving start cues. 

[David Wilson]

I'm not able to get this to work. I made a 2nd workspace (AnotherWorkspace), getting errors.  Not up on script cues, what would be the full text and syntax of the script?

Thanks

[micpool]

That’s why Mike suggested it was easier to use the video list as the master and paste the audio cues into that list.

Mic

[micpool]

Its not a script, it’s an OSC message in a network cue.

Mic

[Mike Post]

I usually don’t have trouble with targeting files when I copy and paste, but I suspect it’s a directory structure challenge.  If your video files are in a contained folder on the same level as your video show file, try copying that folder to the one containing the combined show file .

If you have a more complex set of folders for your video file, I’d suggest bundling the video workspace.  This should give you a new “bundled” folder with a QLab show file and a “video” folder.  You can copy and paste the cues from the new show file into your combined one and move the video folder to the same location as the combined show file.  That should (I believe) maintain the file links.

The surface is another question and I think you should be able to go into video settings and redefine the surface(s) to the proper settings/outputs and get the desired result.

Mike

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/bcef1034-08b3-491e-9cd1-31bf1fcc707cn%40googlegroups.com.

[David Wilson]

Ah, Network Cue - got that to work, thanks.

[David Wilson]

OK, I bundled the video workspace and put it in the bundled folder of the audio workspace. Opened both workspaces, copied the Video cuelist, pasted it in audio workspace,

selected all the video cues and globally assigned them to one surface.

 The Video Cues did find their targets. I assume that will work even if the bundle is moving from one computer to another, as long

as it's in the bundled audio workspace should be fine. 

I've also realized that I can just drag the video cues from the 2nd cuelist into my main cuelist, so I don't need to write "start" cues directed to the

2nd cuelist, I can just drag them in.

So I have both methods working, Network cues and copying/pasting the cues. I'm trying to make it as seamless as possible to merge the 2 quickly and simply. 

Either of these will work, we only have 1 video surface, and around 150 video cues, so may take an hour or 2 to splice them into the show.

I would like to find a way to insert dummy video cue "GO"'s in the Audio workspace as we work thru tech, so when the 2nd cuelist is added, everything

will be programed except setting up the video surfaces. 

But one of these solutions will work if I can't get that going.

Thanks-

[David Wilson]

Answering my own question- I think - network cues are the way to go, I will just add the network cues as I go, easy enough to copy and paste and change the cue number.

Once the Video bundled workspace is loaded onto the playback computer and within the audio bundled workspace, and Surfaces are assigned within the Video workspace

bundle, it should just all work, right?

[Mike Post]

If you’re moving to another computer, you’ll most likely have to redefine the surface on that computer, but you can batch that as you saw before so it should be pretty quick.

Mike Post

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/e8eee1e6-a0bf-40fa-942f-c2a6248a8123n%40googlegroups.com.

[micpool]

Network cues are a good solution when you don't have the cues present in the workspace when you make the cues that will start them. A start cue will break if it doesn't have a valid target, whereas the OSC message just fails silently, until the cue it addresses is present when it will start working.

Another trick is to use this address

/workspace/AnotherWorkspace/go "1"

or /go "1" for cues in the same workspace.

This is different to /start because it GOs the cue and the playhead moves to the next cue in the list, autoloading if that is set. This gives you the best of both worlds, it allows you to explicitly start cues as with /cue/1/start but gives you the same behaviour with the playhead and autoload as /go, allowing you to jump around in the primary cue list or workspace without having to worry about the position of the playhead in the secondary list or workspace.

There are 2  important things to note with this. The cues must be in a separate list and , unlike most QLab OSC addresses which automatically set the type of the argument, you have to make the cue number an explicit string by typing the surrounding quotes. (This is for backwards compatability reasons. So QLab would function with apps  like TouchOSC mk1 which could only send /go (or any other address) with a numeric argument attached, QLab was made to ignore the argument. When the /go with cue number argument method  was added, there needed to be a way for the argument not to be ignored, which is why it has to be enclosed in quotes)

Mic