[QLab] Resetting All targets?

1,703 views
Skip to first unread message

Christopher Neumeyer

unread,
Apr 18, 2011, 6:45:31 PM4/18/11
to ql...@lists.figure53.com
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? Thought I recall one in v1. But that's the last time I had to do it.

Cheers
Chris N
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com
Follow Figure 53 on Twitter here: http://twitter.com/Figure53

*

unread,
Apr 18, 2011, 7:31:49 PM4/18/11
to Discussion and support for QLab users.
Other than using space, there isn't anything easier than bundling that I'm
aware of.

When I'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?

________________________________________________________

luckydave

unread,
Apr 18, 2011, 8:10:31 PM4/18/11
to Discussion and support for QLab users.
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.

luckydave
luck...@figure53.com

Jeremy Lee

unread,
Apr 18, 2011, 8:49:12 PM4/18/11
to Discussion and support for QLab users.
The only problems happen if you are not diligent about your file/ folder structure. If you drag files from all over the place into QLab, then bundling is your only solution. But if you have a structure like:

SHOW NAME Folder
-->Show File.qlab
-->Audio Files Folder
---->Something that makes sense to you
---->Something that makes sense to your assistant
-->Video Files Folder
...etc...

And copy the whole SHOW NAME Folder to another computer, you're golden and everything just works.

On Apr 18, 2011, at 8:10 PM, luckydave wrote:

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

--
Jeremy Lee
Sound Designer, NYC - USA 829
http://www.jjlee.com

Rich Walsh

unread,
Apr 20, 2011, 8:41:41 AM4/20/11
to Discussion and support for QLab users.
On 20 Apr 2011, at 13:31, Maik Waschfeld wrote:

> 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: http://wiki.figure53.com/QLab+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

Michael Keniger

unread,
Apr 20, 2011, 9:51:00 AM4/20/11
to QLab users.
> > 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: http://wiki.figure53.com/QLab+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
>

Maybe if you were switching to a variation of the same file from a group of files with names like "dog bar 01", "dogbark 02", "dogbark 03", "dogbark 04", might be slightly faster in the sense that it would locate to the right 'area' of a group of files?  Also serves as a reminder of the file name you don't want to pick again, if the existing file name was not displayed fully in the cue list.  But otherwise...

Maik Waschfeld

unread,
Apr 20, 2011, 8:31:05 AM4/20/11
to Discussion and support for QLab users.
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".

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.


Regards...
...Maik
(PGP-key on request)

Phone: +49-711-336 18 83 * Mobile: +49-172-714 50 36
Fax'n'Phone: +49-1805-060 334 021 12

<http://www.maik-waschfeld.de/>

...the manual said: Win XP/Vista/7 or better, so I used Mac OS X

Reply all
Reply to author
Forward
0 new messages