problem with an external 32bits version
Dec 13 2013 | 8:41 am
hi everybody,
I'm stuck in this problem: I started building a quite big patch in max 32bits version, using only native objects, but at some point i needed to include the TuioClient object (provided at Tuio.org) that handles tuio messages into a more manageable way for a use inside of max
now i had to migrate to the 64bits version of max, this TuioClient object no longer works, i assume it's because of the 64bits architecture, my question is: is there a way simple enough to fix this problem myself (i asked the dev of this object but yet got no answer, i wouldn't want to bother him too much), considering that i have no experience in building externals?
He included the source code in the download, but i don't have any idea of what i could do with it…
if you have any idea, please don't hesitate to be honest, i already know i'm screwed anyway ;)
thanks!
- Dec 13 2013 | 4:06 pmI agree with Nicolas. Migrating/porting an external from 32 -> 64 bits is a programming task best suited for an experienced C developer. That *could * be you with study. :-)Perhaps another approach is to stay with Max 32-bit. What forced you to use Max 64?
- Dec 13 2013 | 5:45 pmAlso, you can split your patch in two different patches that comunicate via OSC, run the 64-bit with Max 64-bit and the other one wit Max Runtime 32 bit...
- Jan 10 2014 | 9:13 amThank you all for your answers, turns out i found a way to patch something that does the same job as the tuio client's, i should be fine now!I need to work with the 64 bits version of Max because i'm running Max for live, and i need the 64 bits version of Live for it's large RAM addressingLearning C would be really interesting, but probably too much time-consuming in regard to the purpose of my work… I'm wondering though if there's a good place to learn it step by step on the internet…anyway, thanks again guys!
