Apple AU plug-ins not working, QLab v3

[Katharine Horowitz]

The Apple AU effects in my workspace don't fire on a consistent basis. I'll have a cue running and I'll apply AU Reverb to it, but it doesn't take. I can't hear any reverb (even if I roll all the parameters to the extreme). This is particularly true of short cues (like, five seconds or so), AND cues where the reverb is applied to a subsequent fade (but not the original command cue). Anyone else ever have this issue?

Specs: 

OSX Yosemite

120 GB remaining

QLab 3.1.18

3GHz Intel Core i7

[Sam Kusnetz]

Hello Katharine

Are you by any chance using mono audio files? Apple's AUMatrixReverb only works on stereo (two-track) audio files.

Best

Sam

Sam Kusnetz | Figure 53

s...@figure53.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/44b2d74a-9f3c-40ec-be99-c1c4fdd7a6be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Katharine Horowitz]

Well, that solves the short file problem (thank you!) but not the longer one I'm using, which IS stereo.

On Sunday, March 25, 2018 at 1:12:23 PM UTC-5, sam kusnetz wrote:

Hello Katharine

Are you by any chance using mono audio files? Apple's AUMatrixReverb only works on stereo (two-track) audio files.

Best

Sam

Sam Kusnetz | Figure 53

s...@figure53.com

On Sun, Mar 25, 2018 at 2:10 PM, Katharine Horowitz <k_hor...@comcast.net> wrote:

The Apple AU effects in my workspace don't fire on a consistent basis. I'll have a cue running and I'll apply AU Reverb to it, but it doesn't take. I can't hear any reverb (even if I roll all the parameters to the extreme). This is particularly true of short cues (like, five seconds or so), AND cues where the reverb is applied to a subsequent fade (but not the original command cue). Anyone else ever have this issue?

Specs: 

OSX Yosemite

120 GB remaining

QLab 3.1.18

3GHz Intel Core i7

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
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.

[Katharine Horowitz]

Upon further thought, I should elaborate.

The file I'm using (which is stereo and several minutes long) fades up to an audible level and hangs out for a few seconds. Then, upon a cue call, it fades and STOPS over a three-second period with an AU Matrix Reverb effect attached to the fade-and-stop. (The goal is to have one of those reverberated fade-out, spooky, memory type effects.)

Is it the stop that is causing the reverb to not take? I'd accept this explanation except that it worked just fine two days ago and now it's not. I'm flummoxed.

[micpool]

On Sunday, March 25, 2018 at 7:50:57 PM UTC+1, Katharine Horowitz wrote:

The file I'm using (which is stereo and several minutes long) fades up to an audible level and hangs out for a few seconds. Then, upon a cue call, it fades and STOPS over a three-second period with an AU Matrix Reverb effect attached to the fade-and-stop. (The goal is to have one of those reverberated fade-out, spooky, memory type effects.)

If you fade the original cue it will fade it, and the reverb. What you probably want to do is fade the dry/wet mix. set it to 0 in the original cue and 100 in the  fade.  Leave the fader where it is. Check the stop at end of fade box.

Workspace attached

you may find this useful

https://qlabcookbook.com/1997/01/18/a-plug-in-primer/

Mic