Struggling on AudioTrigger Autostart

[DjKlex]

Hi Community,

I'm not sure if that's the right place but I can't start a topic in other points.
I'll hope my english is okay.

I'm very new on working with QLC+ on an Raspberry Pi as replacment of an big old DMX controller behind the TV.
I need the space behind
I'm using it only for background lights in the living room with only two pars when watchin concerts, hearing music, playing Singstar or Rockband.
I've got 'everthing' running with a USB DMX Controller (Eurolite USB-DMX512 PRO Interface MK2) and an external USB mic but that's not the point.

I've searched around the forum and have watched a lot of tutorials on YouTube.
But I think I'm not getting the right way to get the AudioTrigger Widget acivated by loopback (as i read on the forum).
I want to get QLC starting on bootup (that happens yet) and starting the AudioTrigger by a startup function or by script.
Now I need to activate the AudioTrigger manually to get it work.

I'm struggling now 'for a few weeks ' on getting it running automatically.

It would be nice someone can help me in this topic. I think I can't give much feedback back to the community.
But that can change when I have new Ideas and work a bit more with it

DjKlex

[GGGss]

Right,

Can easily be solved.
Ingredients for the recipe:
One channel in a loopback universe.
This channel is bound to the 'input' function of the audio trigger widget
A scene where you set the loopback channel
A collection of functions you need when QLC+ starts
Inside this collection, the scene activating the loopback channel
and now the trick: press the green flag on the functions tab.
(tick the collections option)
With this green flag, you can select the function which has to be ran at startup.
(with the use of a collection you can have multiple things running at startup)

Because you are lucky I've attached a sample project for you to study.
EnJoY

[DjKlex]

Thanks GGGss for the fast reply and the startup workspace.
I'll look at it the next days and hope I'll understand the recipe better
I think I was on the right way but struggeld on the last meters.

Greetings DjKlex

[DjKlex]

Yes
Now that point works fine.
It was only one little mistake on the loopbacks on my side
Thanks for the quick feedback.
Next problems I try to do by myself
If I need help (actual sound input of the used (Singstar or something like that) USB mic is extremly low by using alsa input and don't get it higher by alsamixer).
I think I'll post a new question for a better solution with a soundcard and external (clip) mic (what I'd like to prefer).

But actual it's running and I'm nearly happy at the moment

Thanxx
DjKlex

[zik]

hi guys; i am trying this solution but i could not get it work. I have an USB DMX controler. I don't know in which universe i have to add it as an output.thanks for the help

[MichelSliepenbeek]

The USB DMX Controler has to be set as Output in the Universe where your Fixtures are.
So if your Fixtures are in Universe 1, your USB DMX Controler should be set as Output for Universe 1.

[zik]

Sorry, i am a bit lost, i don't get the trick of loopback universe.
If we take GGGss example » Fri May 21, 2021 10:42 am, what do i need to change to have my DMX fixture work? In which universe do i have to add it? I guess i need to add a scene and mybe add it to the startup collection. Moreover, i use a USB DMX adapter. Thanks for the help

[GGGss]

If you defined your fixtures in universe 1 (which is kinda default), your DMX controller uses universe 1 as output. Tick the output square after universe 1 is selected.
Before going to the loopback magic part, check if your fixtures do respond. Go to simple mode and change values there.
If succesfull, go to the next step and select Universe 2 in the input/output tab and tick the Loopback input and output squares. Now universe 2 talks to itself inside QLC+ (Loopback).
Follow above instructions for the auto enable or study the attached project file.

[zik]

thanks for the answer, i will try