Audio Trigger quirks and enhancements

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
webdb22

Hi!

I've tried the various features of the Audio Trigger, it provides fantastic capabilities, but I also experienced some quirks and I'm suggesting some enhancements:

a) The number of spectrum bars changes arbitrarily:
Create a new Workspace, put a new Audio Trigger widget on the Virtual Console, open the configuration dialog by double-click, it will display "16" for the number of spectrum bars. Overwrite the number with "5" (not using the arrows of the spinner), the number of lines in the configuration dialog is reduced accordingly. Click "Ok" to close the configuration dialog, the widget will display more than 5 spectrum bars, e.g. 10. Open the configuration dialog again, it will display e.g. "10" for the number of spectrum bars. Again overwrite the value with "5" and click "Ok". The widget will again display more than 5 spectrum bars, e.g. 7.

b) Segmentation fault on changing the number of spectrum bars:
Create a new workspace, add a new Audio Trigger to the Virtual Console, open the configuration dialog, Overwrite the number of spectrum bars by a two-digit value, e.g "22". On entering the second digit QLC+ will terminate with a segmentation fault.

c) Peak values in spectrum bars do not reach 100%
Although providing a normalized audio and putting the volume controls well over 0 db (up to +11 db) I wasn't able to achieve 100% peak values in the Audio Trigger spectrum bars and therefore not 100% (255) on the DMX value. Maybe a kind of "multiplier" for the Audio Trigger or each spectrum bar would help?

d) Change Threshold in Operate Mode
It would be nice to change the threshold settings for the Audio Trigger spectrum bars in Operate Mode without switching to Design Mode and opening the configuration dialog. Maybe something similar to the Speed Dial used for Chasers, etc.?

e) Beat Detection
For simple use cases, e.g. just having a Chaser in sync with the beat of the music, an additional "bar, which just provides a "tap" instead of values to trigger a Chaser, etc.?


Environment:
Ubuntu 12.04, kernel 3.2.0, i686
QLC+ 4.6.1

Thanks!
Top
Musicutter

Great ideas! I second your thought on C, D and E. Also noticed on Build 4.7 beat divisor is not showing. I will update this in my thread also.
Top
Post Reply

Return to “Archive - no new threads please”