[QLab] Fade cue corruption

[Don Tindall]

We have been experiencing the same problem fairly frequently.
It may have something to do with the order in which we give a fade cue a target vs. when we give it a name, but I haven't had time to verify that. This also only seems to have started since we upgraded to the pro audio license. I don't remember having this problem with the free version.

-Don Tindall
Ithaca College

>Message: 3
>Date: Sat, 20 Oct 2007 08:28:49 -0400
>From: Jeremy Lee <jeremylists at jjlee.com>
>Subject: [QLab] Fade cue corruption
>To: "Discussion and support for QLab users." <qlab at lists.figure53.com>
>Message-ID: <44180F73-A763-4D4F-A5F7-28B1793333ED at jjlee.com>
>Content-Type: text/plain; charset="us-ascii"

>Chris,

>I got into a situation yesterday, and unfortunately I don't know  
>exactly how I did it.  I managed to create a fade cue that no matter  
>what time I told it to fade over, would complete instantly.  I was in  
>the rush of preparing for Tech, so eventually just deleted and re- 
>created the fade cue, and it's fine.

>It might have been that I was trying to fade something up that wasn't  
>assigned in the original sound cue.  I subsequently assigned it in  
>the original, and left the volume full out.

>No idea if this makes any sense.  Long week behind, and another month  
>ahead!!

>Thanks again,

>Jeremy

>-- 
>Jeremy Lee
>     Sound Designer, NYC - USA 829
>         http://www.jjlee.com
>Message: 5
>Date: Sat, 20 Oct 2007 13:55:51 -0400
>From: "Mr. Emery Roth III" <erothsuede at gmail.com>
>Subject: Re: [QLab] Fade cue corruption
>To: "Discussion and support for QLab users." <qlab at lists.figure53.com>
>Message-ID: <826D4D96-0615-4065-AF40-D15002D94C1D at gmail.com>
>Content-Type: text/plain; charset="us-ascii"

>I think I might have run into something like this recently too...Got  
>to a gig to find out that I needed to playback around 50 cues, all on  
>different cd's.  I built a cue list with a lot of copy and pasting/ 
>option dragging. When I finished all the fade cues except the first  
>one weren't firing.  I checked their targets etc. ultimately I  
>replaced them all and it worked fine.  Didn't have enough time to  
>really stop and think about it just needed it to work.

>Emery Roth