Hello everyone,
I decided to create this sticky topic to gather all the TEST versions in one place, instead of creating one thread every time.
Please note that TEST versions are development versions, so they are not meant to be used in a production environment !
From time to time they fix specific issues raised in the QLC+ forums, so they can help users when a problem is found.
Let's consider them as an anticipation to the next stable release, but until then do not consider these builds as final, as developers might decide to change things at the very last minute.
The changes that have been done from the last stable version are listed in the GitHub changelog
TEST VERSIONS AVAILABLE HERE
Linux: Qt5 GIT packages. Thanks to the help of Veljko Stankov, now we have automated builds of QLC+, targeting Arch, Fedora, OpenSUSE and Ubuntu.
If you are going to comment on these versions, the first thing you must say is exactly which version you tested. Thanks.
Enjoy !
QLC+ TEST versions
-
- Posts: 7
- Joined: Sat Oct 31, 2015 11:37 pm
- Real Name: Rob McDonald
Just wanted to say to Massimo and all those who give up their time to make QLC plus happen, THANKS! Such a lot of work to produce a fantastic programme, I use it for theatre and love it! Thank you all so much, really appreciate your hard work and professionalism
-
- Posts: 9
- Joined: Fri Oct 21, 2016 12:39 am
- Real Name: Ramiro Garza
Hello everyone,
Just for the record, I have Sierra 10.12.1 and an ultraDMX Micro USB. I tried all the test versions on this post and although the ultraDMX was recognized no communication was taking place. I had to run the following command to get it to work
sudo kextunload -b com.apple.driver.AppleUSBFTDI
It seems this command needs to be executed every time the MAC restarts. Is anyone aware of a more permanent solution?
Regards,
Ramiro G.
Just for the record, I have Sierra 10.12.1 and an ultraDMX Micro USB. I tried all the test versions on this post and although the ultraDMX was recognized no communication was taking place. I had to run the following command to get it to work
sudo kextunload -b com.apple.driver.AppleUSBFTDI
It seems this command needs to be executed every time the MAC restarts. Is anyone aware of a more permanent solution?
Regards,
Ramiro G.
- Mysteryland
- Posts: 8
- Joined: Sun Apr 12, 2015 4:50 pm
- Location: Hagen, Germany
- Real Name: Heiko Fanieng
- Contact:
Maybe the Enttec FTDI Driver Cleaner works for you: http://www.enttec.com/dmx_usb/FTClean.ziprgarza wrote: It seems this command needs to be executed every time the MAC restarts. Is anyone aware of a more permanent solution?
-
- Posts: 17
- Joined: Thu Apr 30, 2015 7:36 pm
- Real Name: Drew E
- Contact:
Hi,
I saw the note on the homepage recommending we occasionally test the test version of qlc+. Is there a link or place where I can regularly find out what the changes and updates are so I can perhaps test certain features or aspects of the software? Knowing this is a test version is great, but it'd be also great to know what changed/to look for in the test version.
Thanks,
Drew
I saw the note on the homepage recommending we occasionally test the test version of qlc+. Is there a link or place where I can regularly find out what the changes and updates are so I can perhaps test certain features or aspects of the software? Knowing this is a test version is great, but it'd be also great to know what changed/to look for in the test version.
Thanks,
Drew
-
- Posts: 1326
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
Drew,
one source is changelog: https://github.com/mcallegari/qlcplus/b ... /changelog
It is manually updated, so it may not contain all the changes.
Second source is commit list: https://github.com/mcallegari/qlcplus/commits/master
It contains all changes to source code, although the description may not be descriptive enough
You also need to find out what was the last change that went to a particular test build.
Either you will see commit id (sha sum) as a part of the name (or in appveyor history)
or you'd need to check the date of build.
one source is changelog: https://github.com/mcallegari/qlcplus/b ... /changelog
It is manually updated, so it may not contain all the changes.
Second source is commit list: https://github.com/mcallegari/qlcplus/commits/master
It contains all changes to source code, although the description may not be descriptive enough
You also need to find out what was the last change that went to a particular test build.
Either you will see commit id (sha sum) as a part of the name (or in appveyor history)
or you'd need to check the date of build.
-
- Posts: 7
- Joined: Tue Sep 20, 2016 8:30 pm
- Real Name: Marcin Sikorski
Did this work for you?Mysteryland wrote:Maybe the Enttec FTDI Driver Cleaner works for you: http://www.enttec.com/dmx_usb/FTClean.ziprgarza wrote: It seems this command needs to be executed every time the MAC restarts. Is anyone aware of a more permanent solution?
Marcin
-
- Posts: 1326
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
The crash is during initialization of OLA plugin. I suppose ola plugin version does not match the actual ola version. Either remove ola plugin or upgrade ola. Or something.gmint wrote:Crashes for me on launch under OS X 10.12.2 FWIW, I believe that 4.10.5(all versions) exhibited the same behavior. 4.10.4 works.
-
- Posts: 118
- Joined: Wed Apr 15, 2015 8:04 pm
- Real Name: George Qualley IV
Well what do you know, that was it I don't even recall installing OLA, but I must have. Luckily even if I'm not smart enough to figure out what's causing the crash, at least I can figure out where OLA was installed from the crash log... Thanks @Janosvitokjanosvitok wrote:The crash is during initialization of OLA plugin. I suppose ola plugin version does not match the actual ola version. Either remove ola plugin or upgrade ola. Or something.gmint wrote:Crashes for me on launch under OS X 10.12.2 FWIW, I believe that 4.10.5(all versions) exhibited the same behavior. 4.10.4 works.
-
- Posts: 1326
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
Great!
-
- Posts: 77
- Joined: Sun Sep 27, 2015 10:58 am
- Location: Italy-Arezzo
- Real Name: Mihai Andrei
- Contact:
If you can integrate the function
"Virtual Console / Slider: improved level monitoring with The Possibility to act like a Simple Desk slider (see documentation)"
Also in the XY pad for moving heads and perfect!
if you use it without the virtual console screen holds up ... do not crash .. obvious to use it you have to have an external controller .. as I tried it ..
"Virtual Console / Slider: improved level monitoring with The Possibility to act like a Simple Desk slider (see documentation)"
Also in the XY pad for moving heads and perfect!
if you use it without the virtual console screen holds up ... do not crash .. obvious to use it you have to have an external controller .. as I tried it ..
-
- Posts: 5
- Joined: Thu Feb 18, 2016 8:56 am
- Real Name: Casper
Thanks a lot Massimo!
Only thing i noticed is that the slider monitor isn't showing the actual fade out time, only the fade in from the next que! I got really confused before realizing!
Again, thanks for all the work you put into this!
Only thing i noticed is that the slider monitor isn't showing the actual fade out time, only the fade in from the next que! I got really confused before realizing!
Again, thanks for all the work you put into this!
-
- Posts: 31
- Joined: Sat Oct 10, 2015 10:43 pm
- Location: France
- Real Name: Patrick Yoyotte
- Contact:
Hi Massimo,
I don't know if this has already escalated.
I just compiled latest git version and I found a little bug when modifying color in a scene.
When max value (255) is set for blue channel (0xFF) for instance, when you want to modify color by clicking on relevant icon, values are not correct: 254 instead of 255, 0xFE instead of 0xFF. See screenshot attached.
Works fine when initial value is not equal to 255...
Hope this helps.
I don't know if this has already escalated.
I just compiled latest git version and I found a little bug when modifying color in a scene.
When max value (255) is set for blue channel (0xFF) for instance, when you want to modify color by clicking on relevant icon, values are not correct: 254 instead of 255, 0xFE instead of 0xFF. See screenshot attached.
Works fine when initial value is not equal to 255...
Hope this helps.
Didou
OS: Ubuntu 18.04 Mate Edition
QLC+ Version: 4.12.0
OS: Ubuntu 18.04 Mate Edition
QLC+ Version: 4.12.0
-
- Posts: 1326
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
ColorPicker problem seems like a QT Bug e.g. https://forum.qt.io/topic/49790/qcolord ... d-qt-red/6
-
- Posts: 77
- Joined: Sun Sep 27, 2015 10:58 am
- Location: Italy-Arezzo
- Real Name: Mihai Andrei
- Contact:
used for several hours at my own risk .. I had no crash! Institute to perfection for 10 consecutive hours ... with normal modifcation the program during the event.
My configuration:
Os: OSX 10.11.6 ElCapitan
SW: QLC + _4.10.6-TEST-20170326.dmg
And signaling over E1:31 to OLA on Raspberry Pi 3 with USB interface Enttec Pro
My configuration:
Os: OSX 10.11.6 ElCapitan
SW: QLC + _4.10.6-TEST-20170326.dmg
And signaling over E1:31 to OLA on Raspberry Pi 3 with USB interface Enttec Pro