See audio waveform while in Show Mode...

[fishmonkey]

occasionally i have audio tracks where i need to manually hit a fade cue between sounds. in this situation it would be really handy to be able to see the waveform and playhead progress.

however, as far as i can see, there is no way to see waveforms while in show mode...

[Tyler]

I second this. Have ran shows in edit mode because of this

[Chris Ashworth]

How about using a slice at the spot you need it to fade? And use the trick described here:

http://figure53.com/qlab/docs/videos/slices-and-vamping/

A slice with a play count of 1 can be used to trigger an action at the slice, rather than looping.

-C

fishmonkey

January 18, 2014 at 11:25 PM

[fishmonkey]

ahh yes, that will do the trick!

it would still be good to have the option of seeing audio waveforms in show mode though, although i suppose that is kinda tricky to implement since you can have many audio cues playing concurrently...

[Andy Lang]

On Mon, Jan 20, 2014 at 6:45 PM, fishmonkey <fishmo...@gmail.com> wrote:

it would still be good to have the option of seeing audio waveforms in show mode though, although i suppose that is kinda tricky to implement since you can have many audio cues playing concurrently...

It's also a gigantic performance hit, especially on Mac Mini's or other machines with Intel graphics, which are otherwise great for audio, but have pretty awful video performance. 

-Andy

Figure 53 Support

[Christopher Ashworth]

(Although in this case the performance hit is mostly, I believe, more about disk access, and to a lesser degree CPU. I don't believe the graphics card is the relevant factor for this one.)

(mobile)

[fishmonkey]

the latest Intel HD graphics stuff is actually pretty decent compared to older integrated graphics stuff, however in this case i would think that reading the audio from disk and analyzing it on the fly would be the bottle neck.

one solution, at the cost of added complexity, would be for QLab to pre-generate analysis files (along the lines of the way Ableton Live does).

[fishmonkey]

i have been experimenting with implementing this trick, and it works, but there is one oddity: when the devamp cue is set to "Start next cue when target reaches the end of the current slice", the next cue starts but the play position isn't automatically moved on to the cue after that. for example, if i use a fade cue to fade out the devamped audio track, the play position stays on the fade cue after the fade, instead of moving on to the following cue.

is this a bug or is that the intended behaviour?

the workaround i am using is to set the fade cue to auto-follow on to a GoTo cue which is set to the very next cue...

[Sam Kusnetz]

On February 9, 2014 at 1:42:13 PM, fishmonkey (fishmo...@gmail.com) wrote:

> there is one oddity: when the devamp cue is set to
> "Start next cue when target reaches the end of the current slice", 
> the next cue starts but the play position isn't automatically
> moved on to the cue after that.
>

> is this a bug or is that the intended behaviour?

This is the intended behavior. The design philosophy behind it is that the only things that move the playback position are a “go” or a “go to”.

> the workaround i am using is to set the fade cue to auto-follow

> on to a GoTo cue which is set to the very next cue…

That certainly works, or you can enclose your Devamp and the cue that it starts inside a Start-first-go-next Group cue. That way you trigger the Group cue, the playback position moves on to the cue after the group, and the Devamp cue triggers the second item within that group.

Cheerio
Sam

—
Sam Kusnetz
QLab Field Operative
s...@figure53.com

[Chris Ashworth]

To fill in Sam's answer a bit more, it falls out from the current logic
of the code, but it's also something that is a bit of a corner case in
how QLab computes where to move the playhead. It comes up enough as
being an unexpected result that we've discussed tweaking this behavior,
and that still may happen.

-C

[fishmonkey]

thanks, that is a neater solution than the GoTo cue...