Q Light Controller+

I am trying to configure some audio triggers for triggering lights on by audio trigger, and then let them fade out soon.

Ideal function would be 0 hold time and fade should start immediately. When I try to do such function in QLC+, functions never starts/finishes. Now I have to add some Hold-time (I don't know what is exact limit, having 0.10 as Hold time also fails).

UPDATE: This works with latest git-version.

Hello to you.
3 posts in 30 minutes and you haven't even stated the operating system and which audio card you're using.
No information, no help.

Also, if you guys read the posting guidelines, for specific issues you should share your project.

My apologies.

Information: Windows 7 64-bit, Nuforce udac2.

Steps to reproduce:
- Create new project
- Pick any fixture (like generic RGB)
- Create Scene
- Create chaser with 0 hold time

You know, when claiming a bug you should be 100% sure you understand how the software works.

Attached a working project of what you need to do.
Your mistake is probably that you need to set a chaser in "single shot"

Hi,

I already had it on "single shot". Your project also has the same behaviour. As soon as I add 0.5s of Hold time, it starts to work.

Looking at Fixture Monitor, light goes on and never fades out, also chaser never finishes.

-Juha

This may be related to

https://sourceforge.net/p/qlcplus/discu ... /abdc7e4e/

If you can, please retry with QLC+ built from sources.


EDIT:
Also, can you share your workspace file ?

And I don't understand the need for a zero hold time, can you explain what you are trying to achieve ?

My project works if you hit play on the chaser editor. Check it out with the monitor open.

If it doesn't work attached to audio triggers, then it's another story and it's most likely another of your posts: https://sourceforge.net/p/qlcplus/discu ... /abdc7e4e/

Now since you started 3 threads around the same topic, it's kinda difficult to track which issue is which

Hi,

With latest git version (just compiled), behavior is exactly same. Opening Massimos's project and hitting play on the chaser editor will light the spot and it will stay forever on. Also chaser doesn't finish (one needs to hit Stop ALL functions!-button to make it stop). I didn't make any changes to Massimo's workspace, just hitting the play in Chaser editor. No audio triggers involved.

0-0.4 hold time doesn't work, 0.5 or bigger does.

Massimo: There is 3 threads because there is 3 separate issues. One is related to audio trigger UI bug, which crashes program. This one is related to chaser zero hold setting and 3rd one (which possibly is already fixed, had to test it more carefully) is related to starting chasers rapidly.

David: I want to have light start fading immediately after being triggered. Massimo included workspace here, it triggers the problem for me. OS thing? Are you running Linux/Mac?

UPDATE: I tried this with clean install of latest official release (4.82) and given example workspace doesn't work any better.

UPDATE2: Tried this on 64-bit Ubuntu and latest offical QLC+ (4.82), issue was present there as well.

-Juha

Juha, I don't know what you're doing, but I tried again my sample project on Windows 7 with QLC+ from GIT and it works for me

I was copying only qlcplus.exe over existing (4.82), which clearly wasn't enough. My bad!

This is fixed also with latest git-release.

Thanks for help!

No no, this is my bad luck with nordic people, cause you guys don't read the instructions !
If at some point in the building howto there's written
# make install #
maybe there's a reason for it, don't you think ??

I have read the Windows build-howto quite a many times, but just before that make install thing, I decided to go the QtCreator way ;o)

There's this Play-button in QtCreator and it spits exes and dlls all over the place, not funny.

Seriously: Lessons learned, now I know.

Good news is that latest git-version fixes 2 out of 3 of my findings. A lot more stable now!

I don't usually build with Qt Creator but with just qmake/make/make install from a Powershell.

I think you can use the Creator if you disable the 'shadow build'. Also in any case you need to add 'make install' as a post make step

Yeah. One needs to disable 'shadow build'.

Also, because there's:
CONFIG += debug
in variables.pri, changing to release build from QtCreator doesn't actually change anything. I commented out +- release/debug setting from variables.pri, so it honors QtCreator's profile.

One other thing most of the people might want to do, is to override default make to use jom.exe instead (to allow multicore compiling, from projects/build steps).