Audio Triggers Missing Beats / Inconsistent Behavior
Posted: Sun Feb 21, 2021 8:17 pm
Hello!
I am relatively new to QLC+ and DMX in general but have been spending lots of time recently getting to know as much as I can.
I have tested several different software suites and tools (both free and $$$) and have found QLC+ to be the best for me.
Especially, since it runs on linux and RPi, it is the best solution that meets my needs and have 4.12 running on my RPi 4 8GB and it is pretty amazing.
I have gotten most everything I need figured out and even created a VST plug in to control QLC+ using OSC from my DAWs. (will share if you would like it)
One thing that I would love to get working and have been unable to do so is triggering functions/values using the Audio Trigger.
I tried similar things in other tools too and nothing seems to be quite right but QLC+ is sooo close to working for me.
My goal is to be able to be able to toggle on an Audio Trigger and let it take over control of some functions during a live set.
Some of the functions/sequences will be triggered/automated remotely via OSC but I would also like to send the audio from the board to QLC, running on Linux or RPi, and have certain lights react to different frequency bands.
This looks like it should work and I have configured it to, for instance, trigger a chaser to flash 50ms (strobe-like) to the beat when a kick hits over 50% on 0-300hz.
The external audio source is routing correctly from my audio interface and the Audio Trigger is reacting to the signal.
It kind of works but its inconsistent. It seems to works some times but it doesn't always trigger and sometimes misses lots of triggers in a row.
Almost like the sampling of the audio are out of phase and will hit correctly on 8-10 beats then miss 7-8 beats and then hit correctly again.
The meters on the Audio Trigger do appear to be reacting in time correctly for the most part but do seems to very in amplitude even though the source is (or appears to be) consistent.
But even when the meters are visibly bouncing above and below the threshold to the beat, the trigger doesn't seem to work.
I have tried this on Windows/Linux/RPi with very similar results.
I watched some training vids on how to configure the Audio Trigger and think I have it set up correctly.
Is there something I am missing about how the Audio Trigger is supposed to work?
This seems like a fairly common place thing to do and I have to assume I am just misunderstanding something.
Has anyone done this successfully before? Any ideas of what I am doing wrong?
I am relatively new to QLC+ and DMX in general but have been spending lots of time recently getting to know as much as I can.
I have tested several different software suites and tools (both free and $$$) and have found QLC+ to be the best for me.
Especially, since it runs on linux and RPi, it is the best solution that meets my needs and have 4.12 running on my RPi 4 8GB and it is pretty amazing.
I have gotten most everything I need figured out and even created a VST plug in to control QLC+ using OSC from my DAWs. (will share if you would like it)
One thing that I would love to get working and have been unable to do so is triggering functions/values using the Audio Trigger.
I tried similar things in other tools too and nothing seems to be quite right but QLC+ is sooo close to working for me.
My goal is to be able to be able to toggle on an Audio Trigger and let it take over control of some functions during a live set.
Some of the functions/sequences will be triggered/automated remotely via OSC but I would also like to send the audio from the board to QLC, running on Linux or RPi, and have certain lights react to different frequency bands.
This looks like it should work and I have configured it to, for instance, trigger a chaser to flash 50ms (strobe-like) to the beat when a kick hits over 50% on 0-300hz.
The external audio source is routing correctly from my audio interface and the Audio Trigger is reacting to the signal.
It kind of works but its inconsistent. It seems to works some times but it doesn't always trigger and sometimes misses lots of triggers in a row.
Almost like the sampling of the audio are out of phase and will hit correctly on 8-10 beats then miss 7-8 beats and then hit correctly again.
The meters on the Audio Trigger do appear to be reacting in time correctly for the most part but do seems to very in amplitude even though the source is (or appears to be) consistent.
But even when the meters are visibly bouncing above and below the threshold to the beat, the trigger doesn't seem to work.
I have tried this on Windows/Linux/RPi with very similar results.
I watched some training vids on how to configure the Audio Trigger and think I have it set up correctly.
Is there something I am missing about how the Audio Trigger is supposed to work?
This seems like a fairly common place thing to do and I have to assume I am just misunderstanding something.
Has anyone done this successfully before? Any ideas of what I am doing wrong?