Learnings from working with Open Lighting Architecture for Mac OSX 10.9.5:
Getting the OLA c++ source, compiling it, and running the OLA daemon with Max/MSP to send pixel control data over E131.
- I had a lot of initial trouble getting OLA to compile and run on my system. My goal was to eventually control LEDs with DMX/E131 protocol using Max or another client application (built in Openframeworks, Cinder, or Processing).
- I found that my library compile problems were coming from Macports. The Official OLA documentation recommends installing with Macports but in practice Homebrew was a better option for me. Here is some info on Homebrew. http://brew.sh/ Once you have homebrew installed, you should be able to run the command
brew install ola --universal
in your terminal, which will install OLA to /usr/local/Cellar and symlink to /usr/local/lib directory. Sometimes homebrew installs the package but does not link it. You may have to runbrew info ola
to check whether this is the case. If in fact brew has not linked ola yet, just enterbrew link ola
. NOTE: If homebrew is coughing up blood and telling you to get rid of macports, I recommend uninstalling macports per these instructions
Update on 11/16/14: I compiled a new max external and am working on an example patcher. Stay tuned...
So I'm assuming you've successfully brew installed/compiled ola and now you want to get cookin'! Here's how you get the client application to talk to the server:
- in a terminal, type
olad
- Open up a web browser and go to http://localhost:9090
- You'll need to configure your olad web UI per these instructions: Configure OLA
-
- Go back to your terminal and execute the application by
./[application_name]
where [application_name] gets replaced with the name of your application :)
- Go back to your terminal and execute the application by
- Communications should be happening between the client and server.
To test whether packets are sending over the ethernet from olad enter sudo tcpdump port 5568
Here are the build settings I used when building the commandline app in XCode:
- Library Search paths should be
/usr/local/lib
- Header Search paths should be
/usr/local/include
- Press run and you should see a successfully built application in the Products folder in Xcode! Note: I found that I also needed to add the libolacommon.0.dylib & libola.1.dylib in XCode's Build Phases -> Link Binary With Libraries