Hey there, long time DJ but brand new to DMX/lighting stuff. Coming from ENTECC Emu, I'm having trouble in QLC+ getting the audio trigger widget to smoothly control my dimmer. It's much more harsh than the EMU solution which uses a fade in/fade out upon detecting audio.
QLC overall seems far better than EMU, which has odd quirks I can't overcome. Plus it's free so you can't beat that! Hoping there's a means of accomplishing this. I've been perusing the forums and Google and just can't find anyone asking this specific question. Most results tend to be about synchronizing music via midi etc which isn't what I'm looking to do just yet.
I've attached the fixture file I am using for these (I'm just using the 4x ADJ pars) in case it's relevant. Here are videos demonstrating the difference. It's not easy to tell through a video so I got the dimmers on screen in frame as well, in order to showcase the difference.
EMU Solution
https://youtu.be/DTZUcsRBZCo
QLC+ Solution
https://youtu.be/eDvOxgGFVNA
Thanks!
Smooth/Faded Audio Trigger Configuration
-
- Posts: 3
- Joined: Mon Jul 03, 2023 12:17 am
- Real Name: Joe C
- Attachments
-
American-DJ-Mega-Hex-Par.qxf
- (6.14 KiB) Downloaded 68 times
- GGGss
- Posts: 3319
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
The audio trigger does what it is supposed to do: divide an audio stream into frequency bands and, with the help of thresholds, trigger stuff. It doesn't make sense to integrate or differentiate this signal with an additional time because it just flattens the output, and we need the spikes to be present.
Now, without being able to check your project file, I assume that you drive your fixtures directly by the audio widget. There is a workaround using these triggers to go into loopback channels and use those signals as external input for buttons on your VC. Those buttons are bound to scenes, which have some fade times present. This is how I tackle when a slower pace is wanted.
Now, without being able to check your project file, I assume that you drive your fixtures directly by the audio widget. There is a workaround using these triggers to go into loopback channels and use those signals as external input for buttons on your VC. Those buttons are bound to scenes, which have some fade times present. This is how I tackle when a slower pace is wanted.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 3
- Joined: Mon Jul 03, 2023 12:17 am
- Real Name: Joe C
Gotcha. Yeah I can attach the project when I'm back home if needed, apologies for not including it initially. I was up way past bedtime trying to figure this all out.GGGss wrote: ↑Wed Oct 09, 2024 9:00 am The audio trigger does what it is supposed to do: divide an audio stream into frequency bands and, with the help of thresholds, trigger stuff. It doesn't make sense to integrate or differentiate this signal with an additional time because it just flattens the output, and we need the spikes to be present.
Now, without being able to check your project file, I assume that you drive your fixtures directly by the audio widget. There is a workaround using these triggers to go into loopback channels and use those signals as external input for buttons on your VC. Those buttons are bound to scenes, which have some fade times present. This is how I tackle when a slower pace is wanted.
I'll definitely look into that loopback remedy tonight and report back. Thank you.