Hello,
i'm quite new to this software so i might be overlooking something.
BUT my Enttec DMX usb Pro (not mk2!) does not work or even get recognised on any version of QLC+ newer than 4.6.1 which works fine btw.
I'm on a macbook pro late 2008, mac os x 10.6.8 clean install.
Read this problem somewhere here, that's why i reverted back to 4.6.1. But can't find the thread anymore.
Anyone? Thanks in advance!
Enttec DMX usb pro not recognised on newer than 4.6.1
-
Chris de Rock
I have the same problem and my solution is to compile every version to use the ftd2xx library (per default only enabled in windows-versions). this requires some little changes in the source but it works.
-
Nick
I'm having a similar issue, but with the Enttec Open DMX. I was using the latest QLC+ version, on Max OSX 10.6.8, and it wouldn't show in the input/output section. The same issue happened with another RS-485 USB adapter I had. Both are based on the FTDI D2xx libraries.
Downgrading to QLC + 4.6.1 fixes the issue.
Edit: Downgrade allows the USB DMX dongle to now show, but I'm still not getting any actual DMX output to it. Yes, I do have it checked as an output device.
Downgrading to QLC + 4.6.1 fixes the issue.
Edit: Downgrade allows the USB DMX dongle to now show, but I'm still not getting any actual DMX output to it. Yes, I do have it checked as an output device.
-
Jano Svitok
I went through the changes between 4.6.1 and 4.7.0 and I don't see anything suspicious. Most probably git bisect is needed here, or at least someone with a debugger. I can't do it, because 1) I don't have osx environment 2) I don't have enttec pro (though I have enttec open).
-
Chris de Rock
You can try my latest version compiled from GIT: http://chris.derock.de/qlc/
it comes bundeled with the ftd2xx.dylib
it comes bundeled with the ftd2xx.dylib
-
Massimo Callegari
I would really like to solve this FTDI issue on OSX once and for all.
I don't care if libftdi or D2xx has to be used, even though the FTDI website is not clear about which one should be used on OSX. I think it's all a matter of licenses.
So, anyone that can test Christian's version (thanks for it), report here if it works and which OSX version you are using.
If feedbacks are positive, I will switch to D2xx and hopefully end this miserable OSX story.
Again, Apple doesn't help at all to have consistent softwares across OSX versions. They like to change their OS every year, thinking they are a religious order, with accolite developers that like to fill their code with workarounds for each OSX version released.
Not even talking about those poor devs trying to deliver apps on iOS...
I don't care if libftdi or D2xx has to be used, even though the FTDI website is not clear about which one should be used on OSX. I think it's all a matter of licenses.
So, anyone that can test Christian's version (thanks for it), report here if it works and which OSX version you are using.
If feedbacks are positive, I will switch to D2xx and hopefully end this miserable OSX story.
Again, Apple doesn't help at all to have consistent softwares across OSX versions. They like to change their OS every year, thinking they are a religious order, with accolite developers that like to fill their code with workarounds for each OSX version released.
Not even talking about those poor devs trying to deliver apps on iOS...
-
Chris de Rock
The problem with ftd2xx is the license. in my version, the lib is bundeled and this may taint the license of qlc+.
-
Massimo Callegari
Well, the Windows version of QLC+ already links to D2xx statically, so I guess if there was any license issue, it should have been faced a long time ago...
To summarize:
- VCP drivers and D2xx come from Future Technology, manufacturer of the FTDI chips. They are close source, so one can only call their APIs, hoping they won't change in time. The license is proprietary, expressed in these terms:
http://www.ftdichip.com/Drivers/FTDrive ... ummary.htm
Basically it's just a bunch of "if your FTDI chip explodes, it's not our fault"
- libftdi, instead, comes from intra2net and it is an open source project licensed with GPLv2, which is compatible with QLC+ Apache 2.0.
Needless to say the latter is widely used on every Linux system.
To summarize:
- VCP drivers and D2xx come from Future Technology, manufacturer of the FTDI chips. They are close source, so one can only call their APIs, hoping they won't change in time. The license is proprietary, expressed in these terms:
http://www.ftdichip.com/Drivers/FTDrive ... ummary.htm
Basically it's just a bunch of "if your FTDI chip explodes, it's not our fault"
- libftdi, instead, comes from intra2net and it is an open source project licensed with GPLv2, which is compatible with QLC+ Apache 2.0.
Needless to say the latter is widely used on every Linux system.
-
Massimo Callegari
Wait, didn't see the full license terms link:
http://www.ftdichip.com/Drivers/FTDrive ... eTerms.htm
Basically QLC+ is violating 3.1.1 and 3.1.2 unless we explicitely add a note about it.
http://www.ftdichip.com/Drivers/FTDrive ... eTerms.htm
Basically QLC+ is violating 3.1.1 and 3.1.2 unless we explicitely add a note about it.
-
quota
I can confirm Christian's version is working.
Macbook Pro 3,1 OSX 10.6.8 Enttec DMX usb Pro (Mk1) Firmware 1.44
Macbook Pro 3,1 OSX 10.6.8 Enttec DMX usb Pro (Mk1) Firmware 1.44
-
Nick
Don't take my silence as Christian's version not working. I won't be able to provide feedback until this coming Sunday. Fingers crossed!
-
Nick
That build doesn't work for me. When I look under output, I can check the outbox for DMX Usb, but there is no S/N showing either. Its pretty much the same results as the other 4.6.1, but the difference is that 4.6.1 at least showed the adapter serial number. Just no output from either.
Time to toss this old iMac.
Time to toss this old iMac.
-
Chris de Rock
Have you tried both of your adapters? im using the enttec open dmx on osx 10.6 and it works.