Workspace uniqueID

[Drew Dalzell]

Wonderful people of the list,

So part of my current workflow means I have a tendency to run multiple workspaces and then I send commands between those workspaces. In the past I've done this using MSC commands, but lately I've been moving things more and more into the world of OSC.

Currently I've got a show that has 4 Qlab machines on a network running a total of 7 workspaces.  Two of the machines have a single workspace, one has three workspaces, and one has two workspaces. I'm using OSC commands between these computers to activate cues on different machines. The issue is that a standard OSC start command will go to the front most workspace. I can send a command to a specific workspace but I need the uniqueID of that workspace.

This is all a big lead up to my question. What's the quickest way to get that uniqueID?  As far as I can tell it is not revealed anywhere in Qlab in a simple manner. I had to install Xcode, then the command line tools for Xcode, and then finally qcmd so that I could send a command that would return the uniqueID of the running workspaces.

I am hopeful that there is a simpler way to do this, or if there isn't then perhaps this is a feature request that there be a way to see the uniqueID for items inside the standard Qlab GUI.

Thanks!

Drew

[Lucas Krech]

I am probably missing something obvious but why are you running discrete workspaces as opposed to discrete Quelists? It seems the latter would largely solve your problems.

-L

*insert witty mobile device advertising here*

--
--
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.

[Drew Dalzell]

This show has two sound designers and a video designer working on the design.  It's site specific and shows move across multiple locations.  There are 4 stage managers and some scenes use the same tech systems for different cue sections.  As a result the cleanest workflow is for each show/area to have a workspace.  This means if the video designer wants to work offline they can bundle and copy just their workspace, take it offsite and make edits and changes, and then load that back onto the particular show machine.  As long as the cue numbers stay the same then the master workspace is unaffected and continues to fire the cues.  It also allows for one designer to program from a laptop offline, while another programs from the show machine.  Finally Qlab remote sees all the individual workspaces, so if needed different stage managers can log in, and operate two different shows simultaneously while not conflicting with each other.

Drew

[Chris Ashworth]

Hi Drew,

The ID is hidden because in general it is intended to be used programmatically, since it is not a static identifier.  It can change for example if you copied the workspace on disk.  If QLab opens a document that has the same ID as another open document, it will change the ID to enforce them to be unique.

That said, I can look into adding a way for power users to more easily dig in and find it…

-C

[Clay Benning]

+1 for this. 

Clay

[Drew Dalzell]

If this is the case, then is there, perhaps another method in OSC commands that could be used to send commands to a specific workspace that could be a static identifier? As far as I could discern the only way for me to send commands to a specific workspaces was to do the uniqueID. However if this ID is not static then it is not the best option for doing this.

Drew

[Chris Ashworth]

I’ll look in to adding a way to address documents by name in addition to ID

[Chris Ashworth]

Drew,

Here’s the current build, which now includes the ability to address workspaces by display name:

http://figure53.com/temp/QLab-3.1.4-b2.zip

Note: not all valid display names are valid OSC method names, so you can’t (for example) address documents that have a space or diacritical marks in the name. 

Example valid OSC messages include things like:

/workspace/test.cues/go

/workspace/????.cues/go

/workspace/te*.cues/go

Cheers,

Chris