Flash Function (only for scenes)
Brought to you by:
mcallegari79
Menu
▾
▴
Hi again folks. I interpreted the Flash function as meaning while the button is pressed the function is active and when you let go it is no longer active (DMX level set to original value). I am trying to use a button to turn on strobe but only while the button is being pressed. Currently if I press the button the strobe DMX value goes to 255 but when I let go the value stays at 255 and the strobe does not turn off. Can someone please tell me what I'm doing wrong?
Thanks ............ Rob
This is the old LTP problem again. LTP simply does not return to previous value in QLC+.
Jano, a quick easy fix, at least for shutter/strobe channels, would be to remove the Shutter group from Fixture editor, and add Shutter/Strobe option under Intensity->Colour with the shutter icon. Just makes sure it behaves exactly like the Generic option. Then, if need be, the user can set the channel modifier to LTP, and it will still work the way it should.
BTW, this leads me to believe it's not an LTP issue, but something in the way groups are handled. Otherwise, forcing Intensity channels to LTP would make the problem come back. Right?
You have to go to fixture editor and change your strobe channel to Intensity, Generic. You'll be stuck with the intensity icon for the channel, but it will work the way it's supposed to now. This was dicussed in this thread... https://sourceforge.net/p/qlcplus/discussion/general/thread/25e41321/#1c4f/2bbe
Here is a working example. You'll have to go to fixture editor and open the Chauvet LEDSplash Jr fixture and change channel 2 (Shutter/Strobe/Dimmer) to Intensity->Generic. Then in QLC+ set the channel modifier to LTP, because it needs to be pulled down to the strobe parameter when you activate the strobe buttons.
Hi Guys,
i have the same problems here as described by Rob. When its the old LTP problem again, isn't it better to wait if its fixed with the next release?
I don't like to modify my fixtures to get to work as described by dmxWolf - and then with the next release i have to revert all fixture changes.
Thanks and regards
Heiko
I'm afraid it's a bit more distant topic...
I just pushed a solution on GIT.
https://github.com/mcallegari/qlcplus/commit/829bb9384399b685a890e10ec6c5b052eda71452
It comes at the cost of more CPU usage, especially when hundreds of channels are used.
I have no idea at the moment if this change breaks anything else.
I used the attached project for testing.
Anyone building from sources, please report if you encounter unexpected behaviours.
I'll try to build a test version and upload it in the development section.
Windows TEST version available here:
https://sourceforge.net/p/qlcplus/discussion/development/thread/73d5dfcf/
Thank you Massimo,
LTP now works under Windows 7, for more Tests i need an OS X Version, because all other Environment is connected to may Mac.
Maybe its time for me to learn how to build QLC+ from sources :)
Heiko
Thank you very much for your awesome work. :) I will definitely check out the test version later.
I also wanted to publish a workaround that works with the new loopback plugin so the people on Mac don't have to change their fixture definitons:
-create a loopback universe with loopback 1 as input and output and a single dimmer on channel one. I called the dimmer "strobe LED" since it is the routing for the strobe function.
-create a fader somewhere in an active frame, that is set to level mode and controls the strobe channels of the fixtures that are supposed to strobe when pushing a button. (Or flash in everybody elses case) Set your loopback universe:channel 1 as input
-create a scene with the dimmer of the loopback universe and set it to the value you want for the channels that are supposed to flash
-create a button in VC that is set to flash and starts the scene with the dimmer
This is an easy way to work around flash on channels that are not used by other functions - like strobe for example.
If you have other functions permanently setting the channels you have to use a mixture of this workaround and davids in this thread: https://sourceforge.net/p/qlcplus/discussion/general/thread/1cd1c598/
This will disable the other funtions via a inverted submaster while flashing and then return to them.
Works pretty well! Why am I not able to change the fade times for flashes tho? Don't always want a hard snap for flashes. 0.07ms fades often make things look much nicer.
Actually... I alway thought you could do that: The clock symbol is there if you select a scene and I always thought the times you set here would be used when flashing the scenes.
But you are right, I just tried and it didn't work.
Massimo, is this a bug or is there some kind of reason for this behaviour?
I've try and build it on ubuntu but get some errors in scene_test.cpp
EDIT: log cut
Last edit: Massimo Callegari 2015-03-01
Please do not paste logs into messages. Use attachments.
This is the wrong place anyway to post a build error. Use the development forum.
An by the way, why do you guys always build the DEB package ?
Use make/make install just for testing
OSX TEST version available.
I bundled Qt 5.4.1, so please test also the audio/video playback.
Thanks
Hey,
I just tried to use the test version in Windows and for me it did not work, the LTP strobe channels still did not return to 0 after strobing.
I am on Windows 7 64-bit, QLC+_4.8.5-TEST-20150228, trying to flash the fith channel of a selfmade fixture definition. Channel in QLC set to LTP, already tried swichting to HTP, save, close QLC, start QLC, change back to LTP, save, close, start and try again, still doesn't work for me.
Also tried: Creating a new project with clay Paky Sharpy, setting strobe to flash. Result: Also does not return to 0 as it should. :/
Well, that's still not possible for the simple fact that LTP channels are not reset to 0 when they're "released".
That's the behaviour of intensity channels.
With my latest changes you can do it anyway. You just need a running function keeping the strobe channel at 0 and then you can flash to the value you want. When you release the flash it will go back to 0.
For convenience I think you can do it with a collection (haven't tried though)
That wasn't possible with 4.8.4
Ahhh so I mixed it up, sorry, my bad...
I'll try that when I have time to install the test build again.
Since this running function keeping the value at 0 is needed anyway a workaround via the loopback plugin is almost as convenient. Still very good that you implemented it. Thanks for your awesome work! :)