Hi!
I finally got a chance to try the "Audio Trigger", it's an important enhancement to the QLC+ feature list!
Unfortunately I'm experiencing a weird behavior: Running the Audio Trigger for an extended period of time (something like 12 hours or more) it simply quits working. Which means no moving bars in the Audio Trigger widget in the Virtual Console and no corresponding DMX output although there is still audio input. Switching the Audio Trigger off an on or switching between Design and Operate Mode does not enable it. Other widgets still work fine.
Only Restarting QLC+ enables the Audio Trigger again.
Environment:
Ubuntu 12.04, kernel 3.2.0, i686
QLC+ 4.6.1, DMX output to ArtNet
Thanks!
Audio Trigger stops working after extended period of time
-
Massimo Callegari
Hello, it's indeed an interesting point but debugging something like that might be very hard.
A lot of software components might be involved, and I wouldn't even exclude the operating system itself.
For example, if crond schedule starts overnight, it can modify the audio driver timings thus bringing QLC+ to a critical situation.
Other things that come into my mind are:
- memory leaks (try cat /proc/meminfo) and see if the memory drops from hour to hour
- mutexes used in QLC+ might overlap until the linux kernel overflows and stop giving them out, thus blocking QLC+
Just ideas, but as I said, this is no easy to identify.
By the way, what is the usage where you need 12 hours of audio triggers ? Just curious.
A lot of software components might be involved, and I wouldn't even exclude the operating system itself.
For example, if crond schedule starts overnight, it can modify the audio driver timings thus bringing QLC+ to a critical situation.
Other things that come into my mind are:
- memory leaks (try cat /proc/meminfo) and see if the memory drops from hour to hour
- mutexes used in QLC+ might overlap until the linux kernel overflows and stop giving them out, thus blocking QLC+
Just ideas, but as I said, this is no easy to identify.
By the way, what is the usage where you need 12 hours of audio triggers ? Just curious.
-
webdb22
Hi Massimo,
I agree, debugging this kind of behaviour might be difficult. Based on your suggestions I'd like to share some observations:
- I was able to reproduce this behaviour several times by just letting the Audio Trigger run for an extended period of time
- I haven't noticed any relevant messages in the operating system log files which could give an indication of the cause
- Restarting just QLC+ brings back the Audio Trigger to work
The use case: I plan to use QLC+ for controlling the light of a dance floor based on Sound-to-Light. The DJ will get a simplified Virtual Console for switching between predefined scenes, chasers, etc., all based on Audio Triggers. As the setup of the equipment will be done during the day, QLC+ will be running from early afternoon until early morning next day, typically 12+ hours.
Thanks!
I agree, debugging this kind of behaviour might be difficult. Based on your suggestions I'd like to share some observations:
- I was able to reproduce this behaviour several times by just letting the Audio Trigger run for an extended period of time
- I haven't noticed any relevant messages in the operating system log files which could give an indication of the cause
- Restarting just QLC+ brings back the Audio Trigger to work
The use case: I plan to use QLC+ for controlling the light of a dance floor based on Sound-to-Light. The DJ will get a simplified Virtual Console for switching between predefined scenes, chasers, etc., all based on Audio Triggers. As the setup of the equipment will be done during the day, QLC+ will be running from early afternoon until early morning next day, typically 12+ hours.
Thanks!