Possible problem with fades

[You can call me anything you like. Just don't call me late for lunch.]

I have just updated to 3.0.4 Pro Audio and while getting familiar with it have found what seems to me to be a bug.

I did the following to create a cue to fade in a picture

1   created a new workspace

2   added a fade

3   added a video and dragged a simple JPG onto it

4   dropped the video onto the fade as a target

5   set the video to 0 opacity

6   set the fade to auto-continue

7   set the fade geometry to 100% opacity

When I start the cue it does what I expected and faded the picture in from black. However, if I reset and run it again the picture starts at full visibility instantly. Escape doesn't clear it down, the only way to get the cues to reset is to select the video and run it on its own. I can then run the cue sequence correctly once again.

Any ideas?

Regards,

Chris

[Christopher Ashworth]

This will be the same issue as was happening with audio fades - the state of the cue is set when it's loaded, so if the fade starts running first and the video already ran, the fade is going from the ending value to the ending value, i.e. 100% to 100%.

I can work on a similar adjustment to the way video cues set their state that I implemented this morning for audio levels, but in the meantime put your fade second instead of first and you should be okay.

-C

[Gmail]

I run into this sort of question with students occasionally. The syntax in English is 'I want to fade up a cue,' which leads new users to put in the fade and then the play sound/video cue. However, if you think in terms of manual operation, you don't turn up the volume and then press play, you start the sound/video with the volume/opacity off and then turn the appropriate knob (slider, whatever...). This seems to help my students grasp how a program such as QLab operates.

Mike Post

Sent from my iPad

> --
> --
> 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/groups/opt_out.
>
>

[You can call me anything you like. Just don't call me late for lunch.]

Ok, I understand what you're saying. As it happens I had been running the fade after the image, but I had a series of them and was running them as cross-fades and that all worked great, with image 1 fading out as image two faded in. It was just that I wanted the first image to fade in and not just start with a bang that I ran the fade before the video. I can juggle the fades so that I have the image first, followed by the fade that brings it in and the fade that takes it out and then image two followed by its fades. Just have to work out how to get them to trigger correctly.

Thanks for the info.

Chris

[Joshua Langman]

I don't follow exactly what you're saying, Late for Lunch, but I think there's an easier way to do what you're doing. For cross fades, I just start the second image in a layer under the first and then autofollow into a fade out of the first, so it only takes one fade cue.

[You can call me anything you like. Just don't call me late for lunch.]

Actually I was just messing around trying to get an understanding of what V3 has to offer and trying out different things. I was creating a scenario and seeing how easy it was to accomplish it. In this case I was trying to fade one out and another one in with a varying delay between one and the other. The idea was there there should be a blackout in-between if required.