Re: [QLab] auto relink missing files in Qlab2?
mic pool
> But I do wish that QLab did not initialize levels when a sound
> file goes missing (you
> rename it, etc) and then drag a new one onto it. It should retain
> it's level settings, but just indicate that the sound file is missing.
I think this is really important. You should be able to read a
workspace without the audio being present if you just want to edit
Titles and cue numbers for instance.
I don' t want to bundle 4GB of audio when all I want to do is put a
cuelist on a laptop to tidy it up on the train.
I would also expect to be able to transfer the workspace and audio
independently to another computer with an identical folder structure
without bundling. If I transfer the workspace to another computer but
some files are missing, I would just expectt to be able to find the
missing files and for them to be relinked automatically to the cues
they should be in.
--
Best Regards
Mic Pool
m...@micpool.com
Online video portfolio
http://www.micp.tv
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com
John Leonard
use the same settings for a new audio file in a cue, you don't drag and
drop, but use the target selector (the up-arrow to the left of the column)
to open your audio folder and choose a new piece of audio. Double click and
the new audio is in place at the same settings. Dragging and dropping a new
audio file implies that it's effectively a new cue, and levels are reset
accordingly.
John
On 15/09/2009 01:11, "mic pool" <m...@micpool.com> wrote:
> and then drag a new one onto it
Rich Walsh
> Sorry if I'm missing something, but I've always thought that if you
> want to
> use the same settings for a new audio file in a cue, you don't drag
> and
> drop, but use the target selector (the up-arrow to the left of the
> column)
> to open your audio folder and choose a new piece of audio. Double
> click and
> the new audio is in place at the same settings. Dragging and
> dropping a new
> audio file implies that it's effectively a new cue, and levels are
> reset
> accordingly.
If you open a workspace that has missing files the levels are reset in
the empty cues, regardless of how you then add the missing files back
in.
This is potentially disastrous, actually: you need to reconstruct the
correct file structure for your audio files and reopen the workspace
(without saving) or you lose all your programming. You can't even
interrogate the broken cues with a script to find out what they are
looking for...
Rich
mic pool
On Mon Sep 14 18:03:58 PDT 2009 Rich Walsh wrote
If you open a workspace that has missing files the levels are reset in the empty cues, regardless of how you then add the missing files back in This is potentially disastrous,I think this is an area that requires urgent addressing. Qlab changing or losing information is as Rich says potentially disastrous. I have had a few instances of cues resetting because files are missing when editing the same show on multiple machines, and although I haven't been able to pin down exactly how it happens fades sometimes change their target. This may be when moved or the target moves or has its audio changed. I haven't worked out how I just find them when I run the show through after major programming to ensure everything is correct.
I am coming to the end of previews on a heavily underscored show and Qlab has been a joy to work with and the sound quality particularly on low level cues is stunning even with 16 bit files. I really do find the need though to work through the show meticulously before the performance if I have done substantial editing in the day to check that everything has remained exactly as I thought I had programmed it.
Is there any reason for Qlab resetting everything on cues with missing files. It seems perverse that the pre and post wait times should be preserved if a continue is switched off, but a simple thing like an audio file being temporarily unavailable because of accidental deletion or renaming, or not having been transferred to the same location on a backup machine should cause programming information to be lost. It also means that off line editing is not really viable at present.
John Leonard
John
On 15/09/2009 02:03, "Rich Walsh" <rich...@mac.com> wrote:
> If you open a workspace that has missing files the levels are reset in
> the empty cues, regardless of how you then add the missing files back
> in.
Christopher Ashworth
cue, which right now is (incorrectly) calculated by checking if the
file alias exists. Obviously this is, as everyone has pointed out, a
problem when the file has disappeared, either on the original machine
or a new machine.
I will change this so it will not reset default levels if there has
EVER been a file associated with the cue, which should address the
concerns raised in the last few days.
I'll try to make this update available soon.
Best,
Chris
On Sep 14, 2009, at 8:11 PM, mic pool wrote:
> Jeremy Lee wrote:
>> But I do wish that QLab did not initialize levels when a sound
>> file goes missing (you
>> rename it, etc) and then drag a new one onto it. It should retain
>> it's level settings, but just indicate that the sound file is
>> missing.
>
> I think this is really important. You should be able to read a
> workspace without the audio being present if you just want to edit
> Titles and cue numbers for instance.
>
> I don' t want to bundle 4GB of audio when all I want to do is put a
> cuelist on a laptop to tidy it up on the train.
>
>
> I would also expect to be able to transfer the workspace and audio
> independently to another computer with an identical folder structure
> without bundling. If I transfer the workspace to another computer
> but some files are missing, I would just expectt to be able to find
> the missing files and for them to be relinked automatically to the
> cues they should be in.
________________________________________________________
Jeremy Lee
file onto that cue just replaces the target cue, and keeps the levels-
quite brilliant. Same thing happens when you use the Target cue
arrow...
On Sep 14, 2009, at 8:38 PM, John Leonard wrote:
> Sorry if I'm missing something, but I've always thought that if you
> want to
> use the same settings for a new audio file in a cue, you don't drag
> and
> drop, but use the target selector (the up-arrow to the left of the
> column)
> to open your audio folder and choose a new piece of audio. Double
> click and
> the new audio is in place at the same settings. Dragging and
> dropping a new
> audio file implies that it's effectively a new cue, and levels are
> reset
> accordingly.
>
> John
>
>
> On 15/09/2009 01:11, "mic pool" <m...@micpool.com> wrote:
>
>> and then drag a new one onto it
--
Jeremy Lee
Sound Designer, NYC - USA 829
http://www.jjlee.com
Jeremy Lee
On Sep 15, 2009, at 11:00 AM, Christopher Ashworth wrote:
> Currently QLab is setting default levels if it appears to be a
> "fresh" cue, which right now is (incorrectly) calculated by checking
> if the file alias exists. Obviously this is, as everyone has
> pointed out, a problem when the file has disappeared, either on the
> original machine or a new machine.
>
> I will change this so it will not reset default levels if there has
> EVER been a file associated with the cue, which should address the
> concerns raised in the last few days.
>
> I'll try to make this update available soon.
>
> Best,
> Chris
--
Jeremy Lee
Sound Designer, NYC - USA 829
http://www.jjlee.com
Scott Nielsen
> EVER been a file associated with the cue, which should address the
> concerns raised in the last few days.
Thanks Chris!!
Rich Walsh
> Currently QLab is setting default levels if it appears to be a
> "fresh" cue, which right now is (incorrectly) calculated by checking
> if the file alias exists. Obviously this is, as everyone has
> pointed out, a problem when the file has disappeared, either on the
> original machine or a new machine.
>
> I will change this so it will not reset default levels if there has
> EVER been a file associated with the cue, which should address the
> concerns raised in the last few days.
>
> I'll try to make this update available soon.
Mainly for the challenge of trying to do it, I've written a script
that will make a list of all the audio files used in a workspace -
which might help you to spot any rogue file paths when
troubleshooting, moving shows between machines, etc. It's here, for
what it's worth:
http://figure53.com/wiki/index.php?title=QLab_Scripts_and_Macros#Make_a_list_of_audio_files
Of course, it only works _before_ there are missing targets, but you
should be able to analyse a working version to see what might then
cause a non-working version. Possibly.
Rich