Integrated Fade Shapes

[Paul Arditti]

I know we've been over this before, but why was the QLab3 integrated fade shape behaviour changed?

In what way is it preferable to that of QLab2?

I have just upgraded an old show from QLab2 to QLab3 and I am frustrated that my fade-in curves no longer move with start points, and my loops drop out every time they hit the fade-in curve. Result? I can't use the integrated fade feature for fade-ins or when looping the whole clip. I have been using QLab3 constantly since it was released, and I still can't work out in what circumstances the current logic might be helpful.

Also, why does it need to be so time-consuming to create a simple fade-in or fade-out? Surely there are enough examples from the DAWs we all use of how to do this in a single drag?

[Lists]

The repetition of the fade curve with looping is useful if you are using it as a form of compression or volume management rather than editing the media, this is made far easier by the behavior of the integrated fade shape in v3 as any edits don't shift with the start time, but stay constat to the media.

> --
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/F0909ECD-CFF1-4E52-9263-D2F8B79DDD75%40btinternet.com.
> For more options, visit https://groups.google.com/d/optout.

[Daniel Perelstein]

If you want the fade in to occur at the same point relative to the start of the audio, regardless of where in the file the audio begins, you can do this simply by auto-continuing from your audio to a fade cue. This way, you can adjust your audio start time all that you'd like, and you still have the fade in at the time you intended relative to the start of the audio cue.

In Q3, the integrated fade envelope is used to adjust the level of moments in audio that need adjustment because of something that needs to be adjusted in the audio.

As an example, if you have a looping environmental bed, and there's one sound that's too loud, you can duck down the volume of that moment using an integrated fade envelope. Now, every time that moment occurs (due to the loop), it will be at its appropriate volume. Or, similarly, if the chorus of a song is a smidge too loud every time, you can duck down the level of the chorus. If the director asks you to change the moment in the song where the audio begins, you can drag to a new start time without losing any of the internal level-adjustments you performed on the audio.

In the old behavior, it'd be adjusted on the first pass of the loop, but back to its louder volume for successive passes.

As to why this is preferable to the old behavior: of course, there are some instances where the old behavior is what you want and some instances where the new behavior is what you want. But when you want the old behavior, you can easily make it happen using fade cues. If we had the old behavior, there'd be no easy way to mock up the current behavior .

Dan

[Sebastian Frost]

I totally agree; I pointed this out a couple of years ago but got a negative response.

Qlab 2 used a 'follow first time, then stick at final level' procedure for this, and that's very handy for an awful lot of audio cues as there's no need to use a separate fade cue. A major time-saver. Alas in Qlab 3, the line follows a 'follow every time' rule that is useful in a few cases, but means i have to enter a fade cue for nearly everything. (I use a lot of looping files) A major time-waster!

What I'd dearly love is to have this selectable on a radio button somewhere....

Seb

[micpool]

Peace Brothers and Sisters

In the last major airing of  this topic last December 

https://groups.google.com/forum/#!msg/qlab/GF_h7gKo9xc/DMJvhSCECwAJ

Chris responded by saying

"To clarify: I have been convinced this is a worthwhile place to add an option for both behaviours "

While I think it is worth a periodic reminder, that in the main, the Brits don't like the V3 behaviour, and really need a button to select the V2 behaviour. This does seem to be on Chris's roadmap and I think he understands both arguments and intends to make it work for both camps.

I've got the champagne on ice in preparation for the day!

Mic

[Sam Kusnetz]

Thank you, Mic

Indeed, we are VIVIDLY AWARE of the variety of opinions on this matter.

The short answer to why it's different in v3 than in v2 is that if you
are using v2, and you want the v3 behavior, it's nearly impossible to
achieve. If you are using v3, and you want the v3 behavior, it is
possible, though irritating.

There are thousands of people using QLab, and we got more complaints
about the integrated fade envelope in v2 than we have gotten for v3.

Nevertheless, we are planning to examine the integrated fade envelope
closely in the near future, and try to address the concerns that have
been raised.

Thanks so much for your continued input and examination of QLab. We
couldn't do it without you!

Sam

--
Sam Kusnetz | Figure 53
s...@figure53.com

[Andy Lang]

On Tue, Mar 22, 2016 at 11:17 AM Paul Arditti paula...@btinternet.com wrote:

Also, why does it need to be so time-consuming to create a simple fade-in or fade-out? Surely there are enough examples from the DAWs we all use of how to do this in a single drag?

On Tue, Mar 22, 2016 at 11:29 AM Sebastian Frost sebasti...@me.com wrote:

 Alas in Qlab 3, the line follows a 'follow every time' rule that is useful in a few cases, but means i have to enter a fade cue for nearly everything. (I use a lot of looping files) A major time-waster!

Well, there is a current solution for solving the “time wasting” of having to manually create fade ins and fade outs, in the form of a couple of the many script cue macros that fellow users like Rich Walsh and Sam have shared over the years.

I’d strongly encourage taking a look at the full package of scripts that Rich has provided in his template workspace recently, which you can find here:

https://groups.google.com/forum/#!topic/qlab/8alVV7-MJ8w

You can also find lots of other user-contributed scripts (including fade in and fade out creation) in our wiki:

https://figure53.hostedwiki.co/pages/QLab%20Scripts%20and%20Macros

(The caveat here is that, being a wiki, it's user-edited, and some scripts may need slight edits to be compatible with v3, if they were written for v2. If you find one, it would be appreciated if you'd edit appropriately; you can always email us at sup...@figure53.com if you need help updating a script to work properly with v3.)

Having some or all of these scripts available on a “scripts” or “macros” cue list in your workspace, with hotkey triggers assigned, will forever change your workflow in QLab. I haven’t manually created a fade in or fade out in years!

-Andy

—
Andy Lang
@SoundGuyAndy
sup...@figure53.com

​