D2XX Driver on OS X 10.10.5 Finally working!

[mumbles]

Just needed to express my excitement about finally getting D2XX driver to work properly on my mac! Im sure I would of had it working sooner if I would of noticed a stupid space in the file names I was coping. Hopefully if others where having issues installing the FTDI D2XX driver on Mac will find the only issue was a space in the file names and get theirs working.

Ive been using Artnet as my work around for the driver issue. and will probably continue using strictly Artnet but I'm really happy to know I have the ability to use USB as a backup if I need it!

I guess now I can utilize mac mini in soundbooth running QLC+ or OLA as a protocol converter running in the background. and run QLC+ on laptop or iMac as main console.

[mcallegari]

Justin, glad you resolved something, but your post completely misses the whos and whats.

The official QLC+ package for OSX comes with a bundled libFTDI. Bundling the D2XX library is illegal.
So, can you please explain what did you do, what were the issues and how you resolved them ?
Did you build from sources ?
Did you use Chris de Rock unofficial version ?

[mumbles]

Sorry I didn't have time earlier to properly explain everything.

First few attempts a few months ago I kept trying to follow FTDI Drivers Installation guide for MAC OS X. Never had any luck. keep in mind I was try this around 2am after kids finally went to bed. Lack of sleep may of contributed to failure here.

Today I had an hour to kill so I though Id take another stab at getting D2xx driver to work. These are the steps I took to successfully get it to work.

1) Download FTDI driver controller (this disables and enables and provides status of Apples FTDI driver) - http://www.dmxis.com/release/FtdiDriverControl.zip
2) Download FTDI drivers - http://www.ftdichip.com/Drivers/D2XX/Ma ... X1.2.2.dmg
3) Run FTDI driver controller and disable Apples FTDI driver
4) Open FTDI driver file- D2XX1.2.2.dmg
5) Drag D2XX & LibTable to desktop
6) Open a Terminal window
7) sudo mkdir /usr/local/lib
8) sudo mkdir /usr/local/include
9) sudo cp Desktop/D2XX/bin/libftd2xx.1.2.2.dylib/usr/local/lib/libftd2xx.1.2.2.dylib
10) sudo ln -sf /usr/local/lib/libftd2xx.1.2.2.dylib/usr/local/lib/libftd2xx.dylib
11) sudo cp Desktop/D2XX/Samples/ftd2xx.h/usr/local/include/ftd2xx.h
12) sudo cp Desktop/D2XX/Samples/WinTypes.h/usr/local/include/WinTypes.h
13) Plug in usb DMX interface. I my case a ultraDMX Micro.
14) Open QLC+
15) Goto inputs/outputs and next to DMX USB you'll see your device ready to configure

Steps 5-12 are in the read me file. But there are spaces where there shouldn't be so you can't just cut and past in terminal from the read me file.

[mcallegari]

Uhm...it looks like a placebo effect to me

As I said, the QLC+ dmg bundles the open source libFTDI library. It means the DMXUSB plugin is built using it.
The libFTDI library has functions starting with "ftdi_" while the D2xx library has functions starting with "FT_"

For example, the bitrate function looks like this for libftdi:
https://github.com/mcallegari/qlcplus/b ... i.cpp#L393
and like this for D2xx:
https://github.com/mcallegari/qlcplus/b ... x.cpp#L373

Building sources against a dynamic library, means those sources will not work with other libraries unless they have the exact same functions names.
This happens seamlessly on Linux, Windows and OSX.

Now, unless there is a mistery around dylibs that I'm not aware of, QLC+ is not using the D2xx driver, and the only thing that helped to work properly is step #3 of your procedure.
Obviously if you are using the official QLC+ package and not building from sources or using Chris de Rock build

[mumbles]

Im using the official QLC+ downloaded from qlcplus.org

So most of those steps were unnecessary?

Maybe I screwed something up when I was messing around a couple month ago.

Ill try it agin on a mac mini with a clean install of OS X and QLC+. and test after step 3.

[mcallegari]

So most of those steps were unnecessary?

I would say only step #3 is necessary

Maybe I screwed something up when I was messing around a couple month ago.

Every time there is a OSX update you need to disable the Apple FTDI driver again.
I've written it in the documentation here: http://www.qlcplus.org/docs/questionsandanswers.html