Forums > MaxMSP

Collectives of 4.6 do not work on 4.5?

September 27, 2006 | 8:50 pm

I just tried to load a collective which was made with 4.6.2 into a
MaxPlay of version 4.5.7. It did not load correctly, basically none of
the ui elements where there. Shouldn’t the collective format be
independent of the version?

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


September 29, 2006 | 3:33 pm

On 27 Sep 2006, at 21:50, Stefan Tiedje wrote:

> Shouldn’t the collective format be independent of the version?

Doesn’t the collective include all the Max externals used by the
patcher(s)? If so, you’re trying to load the Mach-O externals from
4.6.x into a Max runtime which expects CFM.

(In other words, a collective might be self-contained, but it’s not
necessarily portable.)

– N.

nick rothwell — composition, systems, performance — http://
http://www.cassiel.com


September 29, 2006 | 7:03 pm

Well yes, in fact it should work but as you say, it doesn’t.

I tested by building a collective on Intel MaxMSP 4.6.2.

It loads on Windows but not on PPC 4.5.7.

Unfortunately this situation escaped our attention during the design of the UB version of MaxMSP.

Basically, if you want to make a collective in 4.6 that is readable in 4.5.7 it can’t contain any externs. To do this, add the "excludeexternals" keyword to your collective script.

Thanks for the report and sorry for the inconvenience.

-Andrew


September 30, 2006 | 4:37 pm

Nick Rothwell wrote:
> Doesn’t the collective include all the Max externals used by the
> patcher(s)? If so, you’re trying to load the Mach-O externals from
> 4.6.x into a Max runtime which expects CFM.

I thought it would only include the externals which do not belong to Max
itself, and those all where CFM externals. I assumed that is the trick
to make them also crossplattform…

But I might be wrong.


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


October 1, 2006 | 1:33 pm

Andrew Pask wrote:
> Unfortunately this situation escaped our attention during the design
> of the UB version of MaxMSP.
>
> Basically, if you want to make a collective in 4.6 that is readable
> in 4.5.7 it can’t contain any externs. To do this, add the
> "excludeexternals" keyword to your collective script.

Yes, but this would not help with third party externals as Peter was
pointing out on the dev list…
I don’t know of any idea beside creating multiple collectives to solve it.
Though if I could include both CFM and Matcho versions and Max would be
smart enough to ignore those which would not work…
(Well the CFM ones need to be placed in a way that Max 4.5.7 would find
it first…)

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


October 2, 2006 | 12:17 am


October 3, 2006 | 9:59 pm

Joost Rekveld wrote:
> what is your reason not to make a stand-alone ?
> size ?

Size and overhead of performance… Its just wasting resources.

I have Max running always, whenever I get a standalone I extract the
collective from it… Prevents also the opening of a Maxplay version if
you doubleclick on a Maxpatch which still happens from time to time. On
my Mac any MaxPlay moves into the trash…


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


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