audio triggered events not working

[fooschnickens]

When setting up the audio trigger widget to press a button or move the cue list in the VC, I noticed that while the widgets are reacting to the audio trigger, nothing is being sent to the fixtures themselves. Manually pressing a button or moving the cue list makes the fixtures work as intended.

Connecting the audio trigger directly to the function being used worked fine, however. But that negates the usefulness of being able to use the cue list.

Playing the scenes/chasers in design mode exhibits the same behavior as using the manual controls in the VC in live mode.

Tested in Win7 and Win10, QLC 4.10.1

I have attached a sample workspace.

[plugz]

When setting up the audio trigger widget to press a button or move the cue list in the VC, I noticed that while the widgets are reacting to the audio trigger, nothing is being sent to the fixtures themselves. Manually pressing a button or moving the cue list makes the fixtures work as intended.

Connecting the audio trigger directly to the function being used worked fine, however. But that negates the usefulness of being able to use the cue list.

Playing the scenes/chasers in design mode exhibits the same behavior as using the manual controls in the VC in live mode.

Tested in Win7 and Win10, QLC 4.10.1

I have attached a sample workspace.

FYI this is fixed in 4.10.2

[fooschnickens]

When setting up the audio trigger widget to press a button or move the cue list in the VC, I noticed that while the widgets are reacting to the audio trigger, nothing is being sent to the fixtures themselves. Manually pressing a button or moving the cue list makes the fixtures work as intended.

Connecting the audio trigger directly to the function being used worked fine, however. But that negates the usefulness of being able to use the cue list.

Playing the scenes/chasers in design mode exhibits the same behavior as using the manual controls in the VC in live mode.

Tested in Win7 and Win10, QLC 4.10.1

I have attached a sample workspace.

FYI this is fixed in 4.10.2

I'll have to go back and verify, but I believe I tested this in 4.10.2 and it still didn't work. I will double check when I get home after work today.

[fooschnickens]

I was finally able to sit down and test this in 4.10.2, but I can't even get the trigger widget to work properly now.

With no kind of vertical reference on the bars, there's no chance to try and find the correct trigger point without a lot of trial and error. It was pure happenstance that I found the correct values last time and I don't have the time to hunt around for a nebulous trigger range that will work. And on top of that that I can't get a hot enough audio signal into QLC to get any of the bars past maybe 20%.



I've tried about all I can at this point, I'm about to just write the feature off completely since I can't get it to be reliable for neither input nor triggering.

[plugz]

Which OS are you using ? Are you sure you can't crank up the input levels ?

[fooschnickens]

Which OS are you using ? Are you sure you can't crank up the input levels ?

Using Win 7/10. I've tried doing all I can to increase the input levels, but there's nothing built in to the OS that allows me to do it, and my sound cards don't have any way to increase the gain, either.

I've tried getting a virtual audio setup in place (JACK and VB-Audio), but while I can get the virtual program to recognize audio being input into it and modify its levels, I can't get QLC to recognize the virtual output in its in/out tab. I've also tried using an external USB audio device but that didn't give me any increase in gain (at least QLC was able to recognize that). I typically use this device when recording straight off our sound board for live shows and I had planned to use it as a clean audio signal to trigger the lighting cues.

[janosvitok]

My working hypothesis is that RMS of the signal is computed and displayed, while peaks may be more suitable here.
Due to RMS, it is hard to achieve full scale.