Having two audiotriggers in Virtual Console crashes Qlc+

[Juha hartikainen]

Steps to reproduce:
- Create empty project
- Add two audio triggers to virtual console
- Open second audio trigger properties (double click) and change Number of spectrum bars to 10
- Open first audio trigger properties (double click) and you will notice that number of spectrum bars changed mysteriously also to 10, just click OK
- Open second audio trigger properties (double click) and Qlc+ crashes

Sidenote: Sometimes Number of spectrum bars "proposes" strange numbers to other widget, like 12 or 13 or 14 (something in between of widget settings)

I am using latest code from git, also latest beta (posted here in forums) crashes.

[EDIT] on Windows 7 64-bit with Nuforce udac2 audio card

[Massimo Callegari]

Short version: you can't use several audio triggers with different number of bars.

Long version: the audio spectrum is generated through FFT processing and the number of frequencies must be pre-determined before entering the FFT. Since there is just one audio source, a single FFT is applied and a number of frequency bars is retrieved.
To have different bars for different triggers the FFT should be performed multiple times, leading to a high CPU usage.
This has been chosen by design. Could be changed but at the moment I see no need for it.

Just use the same number of bars on every trigger

By the way "latest code from git" means you're building QLC+ from sources on Windows ? As for beta...there is no beta...just TEST versions