A big colourful bunch of issues
Brought to you by:
mcallegari79
Menu
▾
▴
Hi,
first of all, thank you guys for the effort. I know it's open source and free, so i'm not making any outrageous demands. I'm a mere user and not graced with too much programming knowledge, so i'll stick to describing my problems:
Running Xubuntu 14.04.01, OLA on a Raspi, KarateLight DMX interface.
1)The ArtNet plugin does not show what Artnet universe/subnet/address QLC+ is using. It autodetects the node on the raspi, but does not properly communicate. (Raspi node is set to 0:0:1.) Since i can neither see nor change what settings QLC+ tries, troubleshooting becomes guesswork. I gave up and tried E1.31, which works like a charm.
2)DMX console - there is no raw dmx console on QLC+, where i can just enter a value for a channel by hand.
3)When following the "Scenes" tutorial step by step, the following occurs:
I created a fixture (Showtec PAR56LED), added it to a new scene and pulled the RED slider to max. When i now click out of the scene, as is shown in the tutorial, it stays stuck on red. This can only be remedied by moving the 00 slider in the simple interface to zero. "Reset universe" does not work, until i move the 001 slider in the simple interface (to any value, just touching it re-enables the stuck "reset universe". Creating a new, empty scene with the same fixture doesn't help. This problem continues throughout: I added a "green" scene with the same fixture. In the "function" tab, clicking either of the scenes results in the desired colour, but unfocusing both hang with the last one used active. Same for the virtual console: if i click the colour button once, the corresponding colour lights up, but the second click on the same button does nothing. A blackout button works temporarily (and as advertised, on/off with two clicks), but as soon as i switch blackout off, the last colour comes on again. Assigning flash doesn't help. The blackout button on top of the window does nothing. Web console has the same problems. What am i doing wrong?
I have attached a screengrab movie:
https://www.dropbox.com/s/gd4ocvzbzcsl6gd/screentest.mp4?dl=0
Greetz
Bernd Liefert
Dear Bernd,
i got the same problems here and the fixture definition was created by me. I changed the RGB Channels from Color-Changer to Intensity. Hope this helps.
I am working with QLC+ 4.8.4 on MAC OS X 10.10.2.
Regards
Heiko
1) ArtNet mapping is fixed. See Artnet plugin description in the online help, or http://qlcplus.sourceforge.net/docs/artnetplugin.html. In your case, 0:0:1 corresponds to QLC+ universe 2.
3) The problem is in the fixture definition. Either place the attached definition in your user fixture folder or copy your system definition and change group for R,G,B channels to Intensity.
I'm confused about the 4th channel. Manual says Full Color, current definition says Helligkeit (Intensity). If it is dimmer channel, please change its group to intensity as well (color: generic). If it is color macro, please post the intervals and respective colors. Thanks!
Heiko, you were faster :)
No Problem Jano :)
Channel 4 is "Full Color" in english, what is the right way to define it in the fixture? There are not more details in the manual: http://www.highlite.nl/de/silver.download/Documents@extern@Manuals/42421_MANUAL_GB_V2.pdf
Maybe 0-9 is R-G, 10-19 is R-B, 20-29 is G-B and so on, but i don't want spent time to find it out with try & error as with my last Fixture, the Varytec LED Laser 4.
It's usually called "Color Macro"
Thanks for the information David.
But which group must be assigned to channel 4: http://qlcplus.sourceforge.net/docs/channeleditor.html
I don't see a color macro group in the documentation?
Color group.
From the help: "Assign a channel to the Color group if the channel controls a fixed color wheel or pre-defined color macros."
The fact that you have to assign Intensity group is not logical - it's heritage from the original QLC. One day I'll add new group "Primary Color".
This is one of the dilemmas - whether dedicate time to improve documentation, or rather fix the problem in the first place...
Jano, you are a developer - so better fix problems first :)
At least for fixing my fixture - should i assign
a) Channel 1-3 to intensity, and then channel 4 to the color group?
b) assigning channel 1-4 to the color group
Whats the right way?
when point b) is the working solution, im back where i startet with my first release of this fixture :)
and point c): What is with your posting of the LTP-Problem with another issue?
Thanks for your support!
Heiko
a) is the right way. I've just committed your new version. The rule is:
Simple colors (R/G/B/C/M/Y/A/W/UV) and dimmer channels are Intensity; Color wheels (with color filters) and RGB color macros (i.e. discrete colors that do not allow fading) are Color group.
LTP: one problem with LTP is that LTP channels don't return to previous value, I don't remember the rest now. Color group is by default LTP, so that's why the color didn't reset.
Thanks for clarifiction Jano & your great work with QLC+
At next point i have to learn something more about DMX-Basics as LTP and so on :)
Thanks for the fast support. Copied the new definition, works like a charm. Nice icon. Does that mean you can sabotage the whole program with one badly coded fixture? Did i happen upon the only one that does that, or is that a problem inherent in the RGB slider?
The mapping on the Showtec junk cans is "on, off, broken". R,G,B, preset colour, strobe, modes (sound operated, which is to be tuned with a knob on the back that does nothing). I hate them, but they were the cheapest stuff we could get our grubby hands on back in the day. Nowadays we don't move them anymore because they tend to lose teeth (LEDs dying in whole rows).
I am trying to replicate the errors now. Brb.
Bernd
Hi Bernd,
i agree that the Showtec are cheap china-scrap, i'll never buy something like that again.
The fixture was from my beginning time with QLC+ 2 years ago. Meanwhile i learned a little bit more about fixtures. But due to some bad manuals its not even easy to create good fixture definitions.
I don't think that badly coded fixture can sabotage QLC+. 2 Years ago it works good for me on 2-3 Shows. I have the feeling, that meanwhile something in QLC+ changed with the RGB-Channels an i forgot to fix it in this fixture - even because i'll never used them again.
2 Weeks ago i take them back from stock for some testing with Mixxx as DJ-Software and QLC+ as VU-Meter.
Regards
Heiko
Last edit: Heiko Fanieng 2015-02-27
Ok. Error persists erratically with the new fixture qxf when using Artnet and E1.31 at the same time on the same receiver:
Set U1 to output E1.31, U2 to output Art.net and changed the fixture from U1 to U2 in QLC+. Does not zero out.
Fiddling with the program while output is on Artnet, light sticks and it crashes after a few clicks.
As soon as i choose U1 which is E1.31, the stuck light goes off and the program behaves properly.
I guess it has something to do with two protocols being used on the same receiver.
Another thing: In all tools i use, holding ctrl or shift while changing size of a box, the aspect ratio stays fixed. Maybe implement that in QLC+ so you can always get square boxes on the console?
Bernd
Oh, and Heiko, if you don't use the Showtec cans anymore, need to get rid of them? :)
Sorry Bernd,
at this time and may be for the next 6 Months i have a job for my 4 Showtec PAR 56 in a few test environments here at my party room that is also an laboratory for different DMX and DJ-Soft- and Hardware :)
If i can find the Time this weekend i'll try to figure out, if some of my problems with QLC+ and my Open DMX Ethernet Interface are the same like you have.
In a another thread i saw a comment, that an old LTP-Bug has a "comeback" in this actual Version: "This is the old LTP problem again. LTP simply does not return to previous value in QLC+."
Heiko
And there i was, wondering if i was being stupid again - when setting three scenes , "R", "G", "B", using the same fixture, i am getting mix colours when i activate two of them at once. On LTP, this shouldn't happen...or am i mistaken there?
You are right. If the colors are LTP (and you assign all three channels to the scenes) then you don't get mixed colors.
For HTP (current state) you can use solo frames if you don't want mixed colors.
Last edit: Jano Svitok 2015-02-27
This thread has been very useful to me. The discussion has explained the reason for a number of odd things that have been happening in my setup. Thanks guys!
So, is there any way to make LTP behave properly? With everything just doing HTP even with the channels set to LTP the program is completely useless because i can't even do scenes with single primary colours.
Hi Bernd,
unfortunately there is no test version for Linux: https://sourceforge.net/p/qlcplus/discussion/development/thread/73d5dfcf/
Yesterday i tested the windows version, at the moment i'm trying out Version 4.8.5 GIT under OS X and for me it works fine.
Regards
Heiko
I don't normally build Linux test versions because I confide Linux users are able to build QLC+ from sources.
It's the easier platform for doing so.
So unless it's extremely necessary, please build from GIT.
Instructions here: https://github.com/mcallegari/qlcplus/wiki/Linux-Build-HOWTO
Hi,
i have no experience in compiling / building from source. Linux is not a specific hacker/programmer operating system anymore. Is there any way to get an installer .deb file or can you tell me if the LTP bug has been resolved in any version?
Hi, i built the latest git version, still no dice.
It now works on the fixture screen, clicking nothing sets everything back to black.
On virtual console, LTP hangs and all channels from one function override those of the next function.
I found a workaround: Setting all other used channels on that fixture to a value of 1 instead of 0. Luckily makes no visible difference on the cheap cans.
So, Function 1: R 255, G 1, B 1 and Function 2: R1, G255, B1 works as advertised. Crosscheck: A function "black" that has all three channels set to 0 doesn't work (in virtual console)
--Conclusion: I guess setting "0" as a channel value results in no new signal being sent, thus nothing happening in LTP. (Console only) Can someone validate / fix?
Hi, i built the latest git version, still no dice.
It now works on the fixture screen, clicking nothing sets everything back to black.
On virtual console, LTP hangs and all channels from one function override those of the next function.
I found a workaround: Setting all other used channels on that fixture to a value of 1 instead of 0. Luckily makes no visible difference on the cheap cans.
So, Function 1: R 255, G 1, B 1 and Function 2: R1, G255, B1 works as advertised. Crosscheck: A function "black" that has all three channels set to 0 doesn't work (in virtual console)
--Conclusion: I guess setting "0" as a channel value results in no new signal being sent, thus nothing happening in LTP. (Console only) Can someone validate / fix?
For some reason i can't edit my post here. The double post should have read:
Another interesting phenomenon is that setting Blackout works for 1 out of 20 clicks. When switching from live to programming mode while blackout button is on, the show hangs on the last used values. Unclicking blackout while on the Functions tab will reset properly.