Hi, I'm trying to install some externals (SPAT and other stuff from IRCAM as well as the AUVI) on a new macbookpro using Max 4.6. It works well under max 4.5 on the same machine but I know it will probably be faster under 4.6...

But how could I get it working without the "loading old CFM externals disabled" message for each external I'm trying to load? Is there a way to enable this? Or will it simply be in the next version of Max?

Hi, I'm trying to install some externals (SPAT and other stuff from IRCAM as well as the AUVI) on a new macbookpro using Max 4.6. It works well under max 4.5 on the same machine but I know it will probably be faster under 4.6...
But how could I get it working without the "loading old CFM externals disabled" message for each external I'm trying to load? Is there a way to enable this? Or will it simply be in the next version of Max?
Thanks a lot!


loading-old-cfm-externals-disabled

AUVI wont run, as loading CFM externals for Jitter is disabled (yes, 

that makes baby jesus cry), and you cant run PPC plugins on an Intel 

If you havent installed CFM support, you should. Check the archives 

for instructions, or.. read the updated documentation that came with 

On Aug 28, 2006, at 11:08 AM, Pm B wrote:

> Hi, I'm trying to install some externals (SPAT and other stuff from 

> IRCAM as well as the AUVI) on a new macbookpro using Max 4.6. It 

> works well under max 4.5 on the same machine but I know it will 

> But how could I get it working without the "loading old CFM 

> externals disabled" message for each external I'm trying to load? 

> Is there a way to enable this? Or will it simply be in the next 

AUVI wont run, as loading CFM externals for Jitter is disabled (yes,  
that makes baby jesus cry), and you cant run PPC plugins on an Intel  
machine. (ahh, fun yes)

If you havent installed CFM support, you should. Check the archives  
for instructions, or.. read the updated documentation that came with  
the max ;)

>
> Hi, I'm trying to install some externals (SPAT and other stuff from  
> IRCAM as well as the AUVI) on a new macbookpro using Max 4.6. It  
> works well under max 4.5 on the same machine but I know it will  
> probably be faster under 4.6...
> But how could I get it working without the "loading old CFM  
> externals disabled" message for each external I'm trying to load?  
> Is there a way to enable this? Or will it simply be in the next  
> version of Max?
> Thanks a lot!
> --
> Pm B

I think (but I could be wrong) that on an Intel Mac CFM externals will

> AUVI wont run, as loading CFM externals for Jitter is disabled (yes, that

> makes baby jesus cry), and you cant run PPC plugins on an Intel machine.

> If you havent installed CFM support, you should. Check the archives for

> instructions, or.. read the updated documentation that came with the max ;)

> On Aug 28, 2006, at 11:08 AM, Pm B wrote:

> Hi, I'm trying to install some externals (SPAT and other stuff from IRCAM as

> well as the AUVI) on a new macbookpro using Max 4.6. It works well under max

> 4.5 on the same machine but I know it will probably be faster under 4.6...

> But how could I get it working without the "loading old CFM externals

> disabled" message for each external I'm trying to load? Is there a way to

> enable this? Or will it simply be in the next version of Max?

I think (but I could be wrong) that on an Intel Mac CFM externals will
never work.

2006/8/28, vade :
>
> AUVI wont run, as loading CFM externals for Jitter is disabled (yes, that
> makes baby jesus cry), and you cant run PPC plugins on an Intel machine.
> (ahh, fun yes)
>
> If you havent installed CFM support, you should. Check the archives for
> instructions, or.. read the updated documentation that came with the max ;)
>
>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>
>
> On Aug 28, 2006, at 11:08 AM, Pm B wrote:
>
>
> Hi, I'm trying to install some externals (SPAT and other stuff from IRCAM as
> well as the AUVI) on a new macbookpro using Max 4.6. It works well under max
> 4.5 on the same machine but I know it will probably be faster under 4.6...
> But how could I get it working without the "loading old CFM externals
> disabled" message for each external I'm trying to load? Is there a way to
> enable this? Or will it simply be in the next version of Max?
> Thanks a lot!
> --
> Pm B
>
>
>
>


On Mon, 28 Aug 2006, Alessandro Fogar wrote:

> I think (but I could be wrong) that on an Intel Mac CFM externals will

that sums it up. cfm externals will only load on mactel hardware when 

running a pre-UB version of max/msp under rosetta. as soon as you run a 

UB version of max, all the objects have to work for that architecture as 

well, which means mach-o only on intel macintosh hardware.

this entire situation is described in some detail in the ReadMe.rtf that 

> I think (but I could be wrong) that on an Intel Mac CFM externals will
> never work.

that sums it up.  cfm externals will only load on mactel hardware when 
running a pre-UB version of max/msp under rosetta.  as soon as you run a 
UB version of max, all the objects have to work for that architecture as 
well, which means mach-o only on intel macintosh hardware.

this entire situation is described in some detail in the ReadMe.rtf that 
comes with the 4.6 installers.

> AUVI wont run, as loading CFM externals for Jitter is disabled 

> (yes, that makes baby jesus cry), and you cant run PPC plugins on 

In case you missed it Anton, if you install Jitter 1.5.3, Jitter 

1.6.1 UB supports CFM on PPC. We don't guarantee that there won't be 

problems, but most objects seem to work with the broad exception of 

CFM OpenGL objects. I haven't heard from any AUVI users yet, but 

cv.jit objects allegedly work. It just requires that the CFM 

compatibilty libraries have been installed (as queried on initial Max 

Launch), and that Jitlib 1.5.3 resides in /Library/CFM Support/. Any 

other CFM library (like an AUVI lib), must also reside there to be 

As has been clarified by other messages in this thread, previous 

threads, and the MaxMSP readme file, there is no way to use PPC code 

inside an Intel native process. Therefore there is no way to use PPC 

code inside the Universal Binary version on Intel. You can only use 

PPC code within an application that runs in Rosetta, such as MaxMSP 

Note that CFM is inherently PPC (or Motorola 68k).

> AUVI wont run, as loading CFM externals for Jitter is disabled  
> (yes, that makes baby jesus cry), and you cant run PPC plugins on  
> an Intel machine. (ahh, fun yes)

In case you missed it Anton, if you install Jitter 1.5.3, Jitter  
1.6.1 UB supports CFM on PPC. We don't guarantee that there won't be  
problems, but most objects seem to work with the broad exception of  
CFM OpenGL objects. I haven't heard from any AUVI users yet, but  
cv.jit objects allegedly work. It just requires that the CFM  
compatibilty libraries have been installed (as queried on initial Max  
Launch), and that  Jitlib 1.5.3 resides in /Library/CFM Support/. Any  
other CFM library (like an AUVI lib), must also reside there to be  
found.

As has been clarified by other messages in this thread, previous  
threads, and the MaxMSP readme file, there is no way to use PPC code  
inside an Intel native process. Therefore there is no way to use PPC  
code inside the Universal Binary version on Intel. You can only use  
PPC code within an application that runs in Rosetta, such as MaxMSP  
4.5.X (i.e. PPC native code).

Ah, this was not clear to me at all, that the 1.5.3 jitter library 

could be loaded along side 1.6.x. I dont think the documentation 

makes that all that clear. Ill test that ASAP on my PPC machine.

I am aware that intel machines cannot load PPC CFMs at all. That was 

made clear by the Readme included with the 1.6/4.6

Thanks for pointing this out overly verbosely to me, otherwise I dont 

-PS, Joshua, thanks again for the tips @ siggraph. I just re- 

implemented my module loading using some of your advice, and I think 

On Aug 28, 2006, at 3:29 PM, Joshua Kit Clayton wrote:

> On Aug 28, 2006, at 8:20 AM, vade wrote:

>> AUVI wont run, as loading CFM externals for Jitter is disabled 

>> (yes, that makes baby jesus cry), and you cant run PPC plugins on 

> In case you missed it Anton, if you install Jitter 1.5.3, Jitter 

> 1.6.1 UB supports CFM on PPC. We don't guarantee that there won't 

> be problems, but most objects seem to work with the broad exception 

> of CFM OpenGL objects. I haven't heard from any AUVI users yet, but 

> cv.jit objects allegedly work. It just requires that the CFM 

> compatibilty libraries have been installed (as queried on initial 

> Max Launch), and that Jitlib 1.5.3 resides in /Library/CFM 

> Support/. Any other CFM library (like an AUVI lib), must also 

> As has been clarified by other messages in this thread, previous 

> threads, and the MaxMSP readme file, there is no way to use PPC 

> code inside an Intel native process. Therefore there is no way to 

> use PPC code inside the Universal Binary version on Intel. You can 

> only use PPC code within an application that runs in Rosetta, such 

> as MaxMSP 4.5.X (i.e. PPC native code).

> Note that CFM is inherently PPC (or Motorola 68k).

Ah, this was not clear to me at all, that the 1.5.3 jitter library  
could be loaded along side 1.6.x. I dont think the documentation  
makes that all that clear. Ill test that ASAP on my PPC machine.

I am aware that intel machines cannot load PPC CFMs at all. That was  
made clear by the Readme included with the 1.6/4.6

Thanks for pointing this out overly verbosely to me, otherwise I dont  
think id have realized!

-PS, Joshua, thanks again for the tips @ siggraph. I just re- 
implemented my module loading using some of your advice, and I think  
it will solve quite a few of my issues.

>
> On Aug 28, 2006, at 8:20 AM, vade wrote:
>
>> AUVI wont run, as loading CFM externals for Jitter is disabled  
>> (yes, that makes baby jesus cry), and you cant run PPC plugins on  
>> an Intel machine. (ahh, fun yes)
>
> In case you missed it Anton, if you install Jitter 1.5.3, Jitter  
> 1.6.1 UB supports CFM on PPC. We don't guarantee that there won't  
> be problems, but most objects seem to work with the broad exception  
> of CFM OpenGL objects. I haven't heard from any AUVI users yet, but  
> cv.jit objects allegedly work. It just requires that the CFM  
> compatibilty libraries have been installed (as queried on initial  
> Max Launch), and that  Jitlib 1.5.3 resides in /Library/CFM  
> Support/. Any other CFM library (like an AUVI lib), must also  
> reside there to be found.
>
> As has been clarified by other messages in this thread, previous  
> threads, and the MaxMSP readme file, there is no way to use PPC  
> code inside an Intel native process. Therefore there is no way to  
> use PPC code inside the Universal Binary version on Intel. You can  
> only use PPC code within an application that runs in Rosetta, such  
> as MaxMSP 4.5.X (i.e. PPC native code).
>
> Note that CFM is inherently PPC (or Motorola 68k).
>
> -Joshua

> Ah, this was not clear to me at all, that the 1.5.3 jitter library 

> could be loaded along side 1.6.x. I dont think the documentation 

> makes that all that clear. Ill test that ASAP on my PPC machine.

Oops. The following paragraph never made it into the public beta 

"This will also install a new jitlib in /Library/CFM Support/ which 

should permit CFM objects like cv.jit or auvi objects run within UB 

on PPC. OpenGL CFM objects are not supported, and there's no 

guarantee that CFM objects will generally work in the UB version. 

Most of the ones we tested however did. Any other CFM shared 

libraries should also be copied to /Library/CFM Support/"

> Ah, this was not clear to me at all, that the 1.5.3 jitter library  
> could be loaded along side 1.6.x. I dont think the documentation  
> makes that all that clear. Ill test that ASAP on my PPC machine.

Oops. The following paragraph never made it into the public beta  
announcement:

"This will also install a new jitlib in /Library/CFM Support/ which  
should permit CFM objects like cv.jit or auvi objects run within UB  
on PPC. OpenGL CFM objects are not supported, and there's no  
guarantee that CFM objects will generally work in the UB version.  
Most of the ones we tested however did. Any other CFM shared  
libraries should also be copied to /Library/CFM Support/"

(• error: TAKETE-sys:/Applications/MaxMSP 4.6/-External-Tools/Lobjects_OSX/ Lobj_X_10_04/Label: loading old CFM externals disabled)

> (• error: TAKETE-sys:/Applications/MaxMSP 4.6/-External-Tools/ 

> Lobjects_OSX/ Lobj_X_10_04/Label: loading old CFM externals disabled)

get the UB versions @ ftp://arts.ucsc.edu/pub/ems/

>
> I also have problems using Lobjects
>
> (• error: TAKETE-sys:/Applications/MaxMSP 4.6/-External-Tools/ 
> Lobjects_OSX/ Lobj_X_10_04/Label: loading old CFM externals disabled)
>

---
Bernhard Loibner
sound & media artist
http://loibner.cc

On Power PC, I stil have problems to run my patches because

I have read everything I could on this subject on thi forum, in the readme, but haven't found a simple, proper, clear answer.

On Power PC, I stil have problems to run my patches because
loading old CFM externals disabled.

I have read everything I could on this subject on thi forum, in the  readme, but haven't found a simple, proper, clear answer.

> On Power PC, I stil have problems to run my patches because

The first time you start there's a message which allows you to 

> I have read everything I could on this subject on thi forum, in 

> the readme, but haven't found a simple, proper, clear answer.

The installer is contained inside the MaxMSP application package :

MaxMSP.app/Contents/Resources/MaxMSPCFMSupport.pkg

> On Power PC, I stil have problems to run my patches because
> loading old CFM externals disabled.
>
> How am i supposed to enable it.

The first time you start there's a message which allows you to  
install the CFM support for PPC.

> I have read everything I could on this subject on thi forum, in  
> the  readme, but haven't found a simple, proper, clear answer.
>
> HOW CAN I ENABLE OLD CFM EXTERNALS ?

I did ask to install CFM support on certain machines at first installation of max/MSP 4.6.n, not on others.

Now I can't see any way to install CFM support objets again. I have tried to reinstall Max/MSP and Jitter, but the dialog proposing the installation does not appear again.

Shall I destroy all Max/MSP installation and reinstall all ?

I did ask to install CFM support on certain machines at first installation of max/MSP 4.6.n, not on others. 

Control Click on MaxMSP.app in the finder.

Navigate to the Contents/Resources folder

Double Click on MaxMSPCFMSupport.pkg which should launch 

On Oct 20, 2006, at 11:17 AM, cahen wrote:

> I did ask to install CFM support on certain machines at first 

> installation of max/MSP 4.6.n, not on others.

> Now I can't see any way to install CFM support objets again. I have 

> tried to reinstall Max/MSP and Jitter, but the dialog proposing the 

> Shall I destroy all Max/MSP installation and reinstall all ?

Double Click on MaxMSPCFMSupport.pkg which should launch  
installer.app to install CFM support.

>
> Thank you Emmanuel,
>
> I did ask to install CFM support on certain machines at first  
> installation of max/MSP 4.6.n, not on others.
>
> Now I can't see any way to install CFM support objets again. I have  
> tried to reinstall Max/MSP and Jitter, but the dialog proposing the  
> installation does not appear again.
>
> Shall I destroy all Max/MSP installation and reinstall all ?
>
> Roland


So if you use a Mac PPC (not Intel) and you have not installed properly the CFM support for old external objects, or you get the error message : "loading old CFM externals disabled", you can reinstall at any time this option doing the following :

Double Click on MaxMSPCFMSupport.pkg which should launch

Old CFM external objects seems to load fine now.

  Control Click on MaxMSP.app in the finder.
  Choose "Show Contents"
  Navigate to the Contents/Resources folder
  Double Click on MaxMSPCFMSupport.pkg which should launch
  installer.app to install CFM support.
  No need for re-install.
v a d e /

It works.
Old CFM external objects seems to load fine now.
Roland


ctrl-click on the Max application -> show package contents -> open 

contents -> open Resources -> double click MaxMSPCFMSupport.pkg ->

(will only make sense on a PPC Machine. MacIntels have to run Max 4.5.7 

cahen wrote:
> HOW CAN I ENABLE OLD CFM EXTERNALS ?

ctrl-click on the Max application -> show package contents -> open 
contents -> open Resources -> double click MaxMSPCFMSupport.pkg ->
follow the instructions...

(will only make sense on a PPC Machine. MacIntels have to run Max 4.5.7 
under Rosetta)

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