Q Light Controller+

Re-uploaded with missing DLLs.
There was also a typo that prevented RGBScripts to be uninstalled.

Qt4, compiled from 6ea7fafa434e50bc8e41dc576bc3bf795a26b2a4

Unfortunately, I haven't had a ton of time to test this version but in the small amount of testing I have done, I *think* that Art-Net might not be functioning. Unfortunately, when I tested this, I did it early on then left it running during the actual live part of the night (my fault). Things weren't working correctly (may or may not have been related to QLC+ as I had some other things going on) and I restarted running 4.6.1.

I'll try to test more soon to confirm.

Just recalled something. Can you please try to manually raise channel 512 on Simple Desk, start your scenes and tell me if it works ?

Tested on Windows 8.1 64bit.

If I create a folder under scene and create a chaser, push the add sign, and by mistake select the folder under scene and click OK, then the application crashes.

OK, confirmed. Thanks

Dear Massimo, Entecc DMX USB PRO works OK now with 4.7.0 (compared to 4.6.1 where the device LED starts blinking after launching the software, in 4.7.0 the LED only starts to blink after a first activity in the software like changing (raising) a fader, so when a first value change is sent out to the DMX fixture.
But the Open USB DMX device by JMS, the USB2DMX (but recognized as Enttec Open USB DMX, but reading/showing a 'crappy serial-number', and message to "patch the widget to a universe") still does not work, not with 4.6.1, nor 4.7.0.

Reg, Paul

Makes sense. Version 4.7.0 doesn't send data if it is not necessary.
I don't understand though if you needed to raise channel 512 as I suggested or if it works with any number of DMX active channels.

As for Open DMX, there's a whole bunch of threads in the forum that you can read.
There is also a Q&A in the documentation dedicated to OSX 10.9, which seems to be a pain in the ass for many reasons.

I'm afraid this isn't working as expected.
So, again, I'm in the situation to risk to release a new version and get a rain of "extremely unstable"-like comments the day after.

I would kindly ask everyone in this thread to test everything you can, even though you don't normally use some features.

Please help.

Sorry,
I did not have to raise the 512 channel for getting activity.

I already tried every possibility on the Open DMX issue. But no results yet... (I tried another software package, a simple one, but that software package works fine with the Open DMX device - so the device is OK, and somewhere on the Laptop that software package can interact with and/or launch the needed driver or whatever to make it work.. very very strange)

Reg, Paul

OK, so I'm doing some additional testing on the 4.7 Beta by setting up a new show. So in the process of setting up some scenes and EFX, I've experienced a crash when cloning a scene and a crash while editing an FX. Unfortunately, it's not something that I've been able to reproduce, but I wanted to give what feedback I have.

Update: I also experienced a time when the EFX stopped working in both operate mode and test mode until I restarted QLC+

Thanks George. I know Jano made some changes on the EFX part. Maybe what you found is already solved.

Anyway, I'm gonna release version 4.7.0 as BETA in a few days and see what happens.

Hi, I hope that this time I´m in the rite chat.
I tested the git build today. And found out that the XY-pad have some problems with passing the data to the dmx output. When I move the pad position, sometime the output doesn't react immediately e.g. just jump to the final position or it does not do anything at all.
Tested with 8 and 16 bit fixtures, not tested on real fixtures just on fixture monitor with the usb to dmx adapter.
Build on Opensuse 12.x, 13.1, x32/64, QT 4.8.5 Detailed info on builds (logs) are hire: https://build.opensuse.org/package/show ... lcplus-git

Hi, yes, you're almost in the right thread (actually this is related to 4.7.0 prebuilt test and not GIT)

I think Jano can respond on this matter

I will check it tonight.

I can reproduce, but I haven't found the problem yet. Thanks for spotting.

Welcome... glade to be helpful. I hope it is nothing serious.
I know that this thread is for pre-build test versions. The point is that, there are no pre-build versions for opensuse so I made it on my own from git. That's why I posted the problem here.

Cingulingu, you know I'm picky for these kind of things, so please pardon me.
If users don't learn how and where to post in this forum, it will get a mess. Moreover the search box will display messy results when searching something precise.

If you found an issue on a GIT version, it makes sense to me to create a new post named "XY pad DMX output issue on GIT 28/02/2014"

Just my opinion, but is it that difficult ?

No. It is not. I explain it, why I did it that way. It seems to me a good idea, not open a separated thread. It seems that I was wrong (again). Oh well.... no body died . I will do it next time. If you want you can add my repo into test section too. So there will be a larger testers pool to spot problems like that, before the release.

Fixed in git.