Cue Outputs Issue

[Rob]

Hi there, 

I appear to be having an issue with the Cue Outputs in Qlab. For instance, as seen in the screenshot below, when I assign output #10 to 2 Channels, the channel select menu in cue output #9 & #11 disappears.

Additionally, when I attempt to load a third party plug-in (stereo reverb) into Cue Output #10 the following pop-up window appears:

The plug-in itself works in mono and stereo (and currently works without issue in my DAW) so I wonder if the issue originates in that channel assignment error. 

The error occurred in Qlab V4.6.9 and hasn't resolved since updating to V4.6.11.

I'm running macOS Catalina on a MacBook Pro (retina, 15-inch, Mid 2015).

Any help would be much appreciated. 

Rob

[micpool]

The first part of your question is easily answered, the option to make the FX  in ch 9 is removed because ch 10 is in use in a 2ch pair already.

As regards the error. Does Apple AU matrix reverb work in ch 10&11

And does your reverb plug work in say ch 1&2 as a 2ch effect without crashing?

Mic

[micpool]

I've just tried that FX configuration  in QLab 4.6.11 in OS10.10.5 and OS12.2 and it works fine. I would suspect it's the specific plugin, or a bug in the OS you are using.

Either way if the problem persists with other plugins in 10/11 or  your problem plugin. runs  in ch 1&2  but not  10&11, then you probably need to send a support request to Figure 53 via the help menu.

Mic

On Thursday, January 27, 2022 at 11:23:13 AM UTC Rob wrote:

[micpool]

And now I need to go and lie down, as the sight of a stereo pair with an even numbered Left channel,  means I can't function for the rest of the day :-)

[Rob]

Hey Mic, 

Thanks for your message. 

The first (non)issue was so obvious the minute you said it - that was a brain melt moment for me. So thanks for that :)

Apple AU matrix reverb works on ch 10&11 along with other third party plugins. I suspect you're right and the issue lies with the plugin itself - although it's formatted as AU along with VST 2/3 & AAX. I guess it's just Qlab's sensitivity, which wasn't a problem with the plugin in the past. 

Don't worry, the channel numbers were decided at random to use as an example. Forgive me!

[micpool]

Is this an iLok protected Plug-in and are you running it in Monterey?

Which Plugin and which OS

Mic

[Rob]

I'm running Catalina 10.15.7.  Yeah it's iLok protected. 

The plugin is Verbsuite Classics by Slate Digital: https://slatedigital.com/verbsuite-classics/

Rob

[micpool]

Hi Rob

Could you get your workspace to crash again and then send your logs through to Figure 53  support via the help menu?.

If you have any waves plugins on your iLok could you try inserting one of these followed by the Slate Digital Plugin.and see if the Slate Plug in then works without crashing?

I have a few iLok related bug reports with them at the moment, and this seems similar and relevant.

Thanks,

Mic

[micpool]

On Thursday, January 27, 2022 at 12:36:00 PM UTC micpool wrote:

I've just tried that FX configuration  in QLab 4.6.11 in OS10.10.5 and OS12.2 and it works fine. 

Update: It works but if certain plugins are put in FX slots then if QLab is quit and the workspace reopened there is an immediate crash. This has nothing to do with the channel configuration of the FX inserts though. It's an iLok related issue that occurs wherever a plugin from certain manufacturers is inserted.

Mic 

[Rob Moloney]

Hi Mic, 

The Slate plugin worked fine after inserting a Waves plugin. Qlab then crashed after reopening. 

The server is repeatedly timing out when sending the crash log at the moment but I will try again later. 

Thanks, 

Rob

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/mi4maNqn7Co/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/51609df1-5510-4923-874d-52ab12243177n%40googlegroups.com.

[micpool]

On Thursday, January 27, 2022 at 5:29:46 PM UTC Rob wrote:

The Slate plugin worked fine after inserting a Waves plugin. Qlab then crashed after reopening. 

The server is repeatedly timing out when sending the crash log at the moment but I will try again later. 

That's what I was expecting to happen. Please send the logs to figure 53 when the server is back up. (I've just sent some so it may be working again.

Mic

 

[Rob]

Crash logs just went through now.

Rob

[Jim Swonger]

Was there any resolution to this problem? We are having a similar problem with an iLok plug-in a designer spec’ed.  we registered it and updated it and Qlab 4 to the latest versions. When we open Qlab and try to add the plug-in to an audio cue, the whole program quits.  I sent the crash report to Qlab, but it sounds like your problem last year was similar.  

Thanks!

[micpool]

The very specific problem discussed in the above thread was  with iLok plugins in cue outputs, which is no longer a general  issue and as far as I remember didn't apply to plug-ins in audio cues.

You have sent your crash logs to Figure 53, so hopefully they will be able to tell you what's going wrong with specific set up and cues.

In the meantime, if you want to identify which plug-in is causing problems, I'm happy to see if I can replicate the issue on my system (if I have the plug-in or it is available as a trial)

Mic