Qlab License Uk

[Cookie Grosky]

WhenI'm working on the same machine, I save the workspace file with a new

date/time. When I finish for the night / make big changes / move a

workspace to another machine, I bundle.Once I have everything the way I want it, I bundle again to have a full

backup with a different folder & workspace file.Easy enough to go back & delete old bundles.ra byn (robin)

On Mon, April 18, 2011 5:45 pm, Christopher Neumeyer wrote:

> Hopefully a quick question. Tried to look in the archives, but didn't see

> anything.

>

> Is there a way in qlab v2.3.3 to reset/retarget the targets of ALL cues?

> Easier than bundling it again and again, or going to each cue in the new

> cue list on the new machine?

> Is there a way in qlab v2.3.3 to reset/retarget the targets of ALL cues? Easier than bundling it again and again, or going to each cue in the new cue list on the new machine? Thought I recall one in v1. But that's the last time I had to do it.

It actually works similarly to v1, just without the often confusing Working Directory. As long as you keep the same directory structure - the workspace relative to the files associated with it - when you move it, the files will be located. QLab's very smart about how it finds files: it looks according to the relative path from where the workspace is saved, and if it can't find them there, it'll look according to a unique identifier assigned by the computer. When you move the files to a different computer, they get a new unique identifier. But if they're still relatively in the same place according to where the workspace file is located, they'll still be found.That's why (and how) bundling works - it creates a copy of your workspace, and copies all associated files to a defined structure in a new folder, which you can move to another machine. The files are located according to that directory structure when the whole folder moves. So, the easiest and least consumptive-of-disk-space way to move your workspace is to keep it in a defined structure, and simply copy that whole folder when you move to another machine.luckydave

luck...@figure53.com

> On Apr 18, 2011, at 6:45 PM, Christopher Neumeyer wrote:

>

>> Is there a way in qlab v2.3.3 to reset/retarget the targets of ALL cues? Easier than bundling it again and again, or going to each cue in the new cue list on the new machine? Thought I recall one in v1. But that's the last time I had to do it.

>

>

> It actually works similarly to v1, just without the often confusing Working Directory. As long as you keep the same directory structure - the workspace relative to the files associated with it - when you move it, the files will be located. QLab's very smart about how it finds files: it looks according to the relative path from where the workspace is saved, and if it can't find them there, it'll look according to a unique identifier assigned by the computer. When you move the files to a different computer, they get a new unique identifier. But if they're still relatively in the same place according to where the workspace file is located, they'll still be found.

>

> That's why (and how) bundling works - it creates a copy of your workspace, and copies all associated files to a defined structure in a new folder, which you can move to another machine. The files are located according to that directory structure when the whole folder moves. So, the easiest and least consumptive-of-disk-space way to move your workspace is to keep it in a defined structure, and simply copy that whole folder when you move to another machine.

> Hi List,

>

> I'd like to suggest a new function on the bundling topic.

> Something like "Collect external files" or "Consolidate Workspace", that copies these files to the workspace's folders, that reside somewhere else, outside the workspace's root.

> Or a button in the preferences: "Copy every File to Workspace on import".Synchronicity at work: here are the beginnings of two new scripts I started fiddling with last year and haven't finished yet:(* Change all targets *)--set theExplanation to "This script automates the process of redirecting all the file targets in the current QLab workspace to duplicate files housed somewhere else.It works on the assumption that you are working in a copy of an original workspace and need to move all the file references over to the copied media files."(* Gather files *)--set theExplanation to "This script checks all the non-broken cues of the current QLab workspace for audio, video and MIDI files that are not in a subfolder " &

"of the folder that houses the workspace. If any are found, they are copied to a folder of your choosing, and the cues are updated to reference the copies.Files with the same name will be treated as if they are the same file: the first one will be copied, and all later cues will be updated to reference this new file."> And another thing:

> clicking on a terget's up arrow should open the file selector with the target-file already selected, instead of just open in the root-level of the workspace.

> Just as sugestion.This script does that: +Scripts+and+Macros#x-Audio%20Cues-Change%20target (you could remove the bit that keeps the times). Personally, I'd rather QLab's file dialogues always opened on the last folder you viewed, rather than jumping to the file that is already selected (why would you want to select the same target again?).Rich

I'd like to suggest a new function on the bundling topic.

Something like "Collect external files" or "Consolidate Workspace",

that copies these files to the workspace's folders, that reside

somewhere else, outside the workspace's root.

Or a button in the preferences: "Copy every File to Workspace on

import".

Please could some point me in the right direction. I'm needing/ wanting step by step guide on how to trigger my cues using to timecode from qlab. (I'm wanting to time it with a song, rather than me manually pressing go in time, just wanting the one go at start with song).

first question is whether you want qlab to send out timecode into eos (which I think is a bit complicated over the network), or just to trigger the start of a sequence in eos. I usually do the latter.

4/ in qlab, create a network cue, set the patch to the network patch you created in step 2, and give it a type of "OSC message", in the big box enter "/eos/cue/1/fire" - when you run this cue you should see cue 1 being fired on your console. If you change the number "1" in the message to other numbers, you should see the corresponding cue in eos fire.

So once you have this working you have two options - one is to create a number of network cues as per step 4 above, which you pre-wait (or use a timeline group cue) to fire at the correct point in the show. The other option is to use eos's "show control" screen (displays -> show control) to set up an event list which is fired by your first cue in the sequence. If you want some help with either of these let me know..

Not sure if this is possible so I've been told this is the best place to ask. I work on alot of high profile sports events mainly in the uk. From time to time im asked to provide a log of what's been played out with dates and times etc. Does anyone know if there's a option on qlab for this , or if there's a script avalible somewhere which will allow me to do this ?.

Thanks in advance ,Lee

3a8082e126