Thanks for your solution. I finally didn't have to try it because I finally made the other solution I was working on work. Here is what I've done:
My main mistake was about compiling the ola2pd object with flext. in the readme.txt, there was a part I didn't understand first, so I skipped it : "For Ubuntu there is an aditional compilation step. Ubuntu's gcc has a option making buils.sh doesn't link correctly the OLA library. You can copy the last command of the build.sh terminal output and change the option -lola to the end of the command." That was the solution for compiling ola2pd, then after that the pd object worked perfectly. Then I started OLA, and started configuring it here http://localhost:9090 The important part (and I lost a lot of time because of it) was to disable the "Enttec Open DMX Plugin" and "Serial USB Plugin", then enable the "FTDI USB DMX Plugin". I added an output device/port (called FT232R USB UART in my case), then after that I was able to control the lights by using the DMX Console / DMX Monitor (still in http://localhost:9090) In Pd, the object ola2pd is really easy to use (see the help file) and does the same job as the DMX Console. Done! Le lun. 25 juin 2018 à 19:42, Peter Venus <[email protected]> a écrit : > Hello! > > i am using a different solution to control DMX: > i struggeled as well with enttecs openDMXusb and i am now using an > > Enttec ODE (open DMX Ethernet) > > https://www.enttec.com/eu/products/controls/dmx-over-ethernet/ode-mk2-open-dmx-ethernet/ > > This allows me to send Artnet-protocol commands via Ethernet directly > from PD by using the netsend-objects. > > Of course, one has to wrap his/her head around the artnet-protocoll, but > marian weger did already and build some very nice vanilla-only > abstractions, > > [artnetout] > [makeartdmx] > > these can be found in his git within his kollabs-abstractions: > > https://github.com/m---w/kollabs > > maybe this helps? > > The only drawback when using the enttec ODE: to configure it, the > quickest way is to use enttecs own configuration software,which is win > and mac...(i did not try using it via wine) > > enjoy, > > peter > > > On 2018-06-25 08:31, JP - Escarres wrote: > > That's it! > > I didn't really understood the "compiling on ubuntu" part in the > > readme.txt file. > > > > Especially this "You can copy the last command of the build.sh terminal > > output". > > I thought the code line was inside build.sh, but no, it's outputed on > > the terminal. > > So after this, my pd object ola2pd finally works! Thanks a lot for the > hint! > > It doesn't mean I can control the lights yet, but it's already a big > step! > > > > Le ven. 22 juin 2018 à 17:37, IOhannes m zmölnig <[email protected] > > <mailto:[email protected]>> a écrit : > > > > On 06/22/2018 05:37 AM, JP - Escarres wrote: > > > Hi everyone. > > > I'm trying to make my DMX interface (Enttec OpenDMX USB) work > > with Pd. > > > I read a lot of things about it, and probably the best way to > > make it work > > > would be by using Open Lighting Architecture ( > > > https://www.openlighting.org/ola/) > > > I'd like to avoid using something like QLC if possible. > > > I'm on Linux (Ubuntu). > > > > > > I found this external http://puredata.info/Members/santi/ola2pd/ > > which > > > seems to be perfect for me. > > > I tried to follow all the steps (installing Ola, compiling > > Flext), but the > > > object Ola2pd is not recognized by Pd. > > > As they suggested, I tried to compile it myself by using Flext. > > It works, > > > but still, the object Ola2pd is not recognized in pd. > > > I received the message "undefined symbol: > > > _ZTIN3ola6client17BaseClientWrapperE" > > > > > > Any idea of what I could do? > > > > well, the problem you are facing is, that (at least) one of the > symbols > > that are supposedly provided by libola is missing. > > > > so there's two possibilities: > > - either you are not (properly) linking against libola > > - or current version of libola does not provide that symbol any > longer. > > > > assuming the former (as the latter would require porting the > external to > > the new libola), i see that the readme.txt has an explicit note on > > "compiling on ubuntu", that requires you to repeat the linker command > > with "-lflext-pd_t -lola" *after* the output file (ola.pd_linux) > rather > > than before it (because doing it in the wrong order will make modern > > linkers skip the linking; this is actually a bug in the buildsystem). > > > > even if you are not using ubuntu, most modern linkers will require > that > > step. > > > > fgmasrd > > IOhannes > > > > _______________________________________________ > > [email protected] <mailto:[email protected]> mailing list > > UNSUBSCRIBE and account-management -> > > https://lists.puredata.info/listinfo/pd-list > > > > > > > > _______________________________________________ > > [email protected] mailing list > > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > > > > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
