Forums > Dev

access to externals source code

June 14, 2006 | 6:25 pm

hello,

i have been useing max/msp/jitter for a couple of years now but am new to max development.

i was hopeing to use max as a prototyping language for a project and was wondering if it is possible to access the source code for the max externals used in a patch i.e i would like to convert a max patch into c/c+ project.

thanks,

justin


June 14, 2006 | 11:16 pm

Nope. Externals are compiled, the source-code that went into them is
gone.

If you want to see the open source equivalents of some of the Max
externals, check out PD. Not all of the objects are there, doesn’t
have even close to the amount of polish in Max.

You’re better off redesigning your c/c++ project anyhow and just
using the main ideas of your Max patch.

_Mark


June 14, 2006 | 11:45 pm

yeah that’s what i figured – had to check ;)

yep – will prototype with max and then convert to c++.

thanks,

justin


June 15, 2006 | 12:04 am

yeah mine.
Also, i know that yann orlaray (sorry if the spelling is wrong) in lyon
made a wrapper that converts your max patches
into C code…
I’ve never seen it but i’ve heard a lot about it.

Also, loads of third party externals are often donwloadable with their
source code (which is normal to me… but
that’s an other subject…)
I don’t think this is what you’re looking for but at least… it makes you
read c code for max-msp-jitter and it’s always
interesting, isn’t it ?


June 15, 2006 | 8:13 am

Sebastien,

Are you talking about Faust? (http://sourceforge.net/projects/
faudiostream/) It won’t translate max patches into C code, but some
sort of pseudo code to C++ with something intelligent to make Max, PD
external. I’ve never used that either, so…

ej


June 15, 2006 | 9:01 am

On 15-Jun-2006, at 1:16, Mark Pauley wrote:
> Nope. Externals are compiled, the source-code that went into them
> is gone.

Not entirely: the SDK publishes source for about two dozen objects,
and numerous 3rd party objects come with source attached.

Justin: you should take a look at the Max SDK. Then you will better
understand why manual conversion from prototype to C/C++/whatever is
the only realistic path. Understanding the underlying architecture
will also help you tread that path.

Good luck, P.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de

http://www.dspaudio.com/


June 15, 2006 | 5:09 pm

thanks for all the responses. i wish i had discovered this forum earlier – it would have probably saved me some headaches over the past couple of years that i have been using max.

justin


June 23, 2006 | 2:20 pm

The forum only just exists for a few months, before this was a mailinglist..


Viewing 8 posts - 1 through 8 (of 8 total)