ben100@infonie.fr

I've a new Macbookpro with a Fireface 400 soundcard (all the drivers are up to date and the soundcard works with other softwares.

I recently downloaded Max/msp runtime to makes some tests with a patch someone wrote for me.

The 4.6.1 runtime version does'nt work because of :

"loading old CFM externals disabled". but I can access to dsp status.

So I tried with the 4.5.7 version. The patch appears to load well, but I can't access to dsp status (There 's normally a button to access there in the control window of my patch) so only the internal microphone and speakers work.

I had exactly the same problem with an older computer (not on macintel) a few months ago.

Does anyone know what to do to resolve this problem ?

I would like to try before buying the full version

I've a  new Macbookpro with a Fireface 400 soundcard (all the drivers are up to date and the soundcard works with other softwares.

The 4.6.1 runtime version does'nt work because of :
"loading old CFM externals disabled". but I can access to dsp status. 

I had exactly the same problem with an older computer (not on macintel) a few months ago.
Does anyone know what to do to resolve this problem ?

no-access-to-dsp-status

I don't think this was replied to, so I'll pitch in...

> The 4.6.1 runtime version does'nt work because of :

> "loading old CFM externals disabled". but I can access to dsp status.

CFM support is an installation option for Max/MSP 4.6.x - it sounds 

as if this copy was installed without CFM. All the packaged patchers 

and externals are Mach-O, which is why the DSP Status patcher works.

> So I tried with the 4.5.7 version. The patch appears to load well, 

> but I can't access to dsp status (There 's normally a button to 

> access there in the control window of my patch) so only the 

4.5.7 was a PowerPC release, so an Intel Mac will run it under 

Rosetta emulation, and not give it access to audio hardware over and 

nick rothwell -- composition, systems, performance -- 

> The 4.6.1 runtime version does'nt work because of :
> "loading old CFM externals disabled". but I can access to dsp status.

CFM support is an installation option for Max/MSP 4.6.x - it sounds  
as if this copy was installed without CFM. All the packaged patchers  
and externals are Mach-O, which is why the DSP Status patcher works.

> So I tried with the 4.5.7 version. The patch appears to load well,  
> but I can't access to dsp status (There 's normally a button to  
> access there in the control window of my patch) so only the  
> internal microphone and speakers work.

4.5.7 was a PowerPC release, so an Intel Mac will run it under  
Rosetta emulation, and not give it access to audio hardware over and  
above the built-in stereo.

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


>CFM support is an installation option for Max/MSP 4.6.x - it >sounds 

>as if this copy was installed without CFM. All the packaged >patchers 

>and externals are Mach-O, which is why the DSP Status patcher >works.

I tried to reinstall the max/msp 4.6.2 runtime, 

and simply followed the readme instructions document, 

but there was no option for disabling or enabling CFM support.

>CFM support is an installation option for Max/MSP 4.6.x - it >sounds 
>as if this copy was installed without CFM. All the packaged >patchers 
>and externals are Mach-O, which is why the DSP Status patcher >works.

Many thanks for your answer, 
I tried to reinstall the max/msp 4.6.2 runtime, 
and simply followed the readme instructions document, 
but there was no option for disabling or enabling CFM support.

> I tried to reinstall the max/msp 4.6.2 runtime,

> and simply followed the readme instructions document,

> but there was no option for disabling or enabling CFM support.

Oh, hang on - I had a temporary brain failure. You're on an Intel 

Mac, yes? If so, there's no support for PowerPC externals at all 

(apart from running the entire shebang under Rosetta), so CFM 

binaries are a non-starter. The CFM library is to allow old PowerPC 

binaries to run under the new Mach-O Max/MSP, on PowerPC only.

So I guess the error messager is misleading: when it says

    "loading old CFM externals disabled"

it doesn't mean "I can't adapt CFM PowerPC binaries to Mach-O 

> I tried to reinstall the max/msp 4.6.2 runtime,
> and simply followed the readme instructions document,
> but there was no option for disabling or enabling CFM support.

Oh, hang on - I had a temporary brain failure. You're on an Intel  
Mac, yes? If so, there's no support for PowerPC externals at all  
(apart from running the entire shebang under Rosetta), so CFM  
binaries are a non-starter. The CFM library is to allow old PowerPC  
binaries to run under the new Mach-O Max/MSP, on PowerPC only.

it doesn't mean "I can't adapt CFM PowerPC binaries to Mach-O  
PowerPC", it means "I'm an Intel."

- 4.6.2 won't undestand any external libraries (under power pc)

- 4.5.7 with rosetta doesn't allow me to use my sound card with max/msp ?

Isn't there thousands of people who are in the same case than mine ?????

So there's no solution for me ?
except replace those libraries ?

What I don't understand also is: 
Isn't there thousands of people who are in the same case than mine ?????

Quote: ben100@infonie.fr wrote on Mon, 16 October 2006 09:06

----------------------------------------------------

> - 4.6.2 won't undestand any external libraries (under power pc)

Right. Max 4.6.2 on Intel needs Universal Binary or Intel-specific objects. I assume you mean external objects when you say "libraries".

> - 4.5.7 with rosetta doesn't allow me to use my sound card with max/msp ?

This hasn't been the case for me -- I used my MOTU 828 in a concert last week using 4.5.7. It certainly has access to all the CoreAudio Devices I've used.

> Isn't there thousands of people who are in the same case than mine ?????

Probably more like hundreds :) There has been some pretty substantial progress on the development of UB externals. While the percentage of possible externals is low, I think many of the most useful, or my personal favorite, externals have been ported.

And I still keep 4.5.7 around for some things. I did an odd performance last month where 4.6 and 4.5.7 were communicating using OSC, just to give me access to a old patch.

Quote: ben100@infonie.fr wrote on Mon, 16 October 2006 09:06
----------------------------------------------------
> so do I understand what you say :  
>
> for A Macintel,
>
> - 4.6.2 won't undestand any external libraries (under power pc)
>

Right.  Max 4.6.2 on Intel needs Universal Binary or Intel-specific objects.  I assume you mean external objects when you say "libraries".

> - 4.5.7 with rosetta doesn't allow me to use my sound card with max/msp ?
>

This hasn't been the case for me -- I used my MOTU 828 in a concert last week using 4.5.7.  It certainly has access to all the CoreAudio Devices I've used.

> What I don't understand also is: 
> Isn't there thousands of people who are in the same case than mine ?????
>

Probably more like hundreds :)  There has been some pretty substantial progress on the development of UB externals.  While the percentage of possible externals is low, I think many of the most useful, or my personal favorite, externals have been ported.

And I still keep 4.5.7 around for some things.  I did an odd performance last month where 4.6 and 4.5.7 were communicating using OSC, just to give me access to a old patch.  

4.5.7 was a PowerPC release, so an Intel Mac will run it under

Rosetta emulation, and not give it access to audio hardware over and above the built-in stereo.

I don't understand Why the fireface 400 can't work with rosetta.

And also, if I just wanted to use built-in soundcard, I should have 

So may be my problem isn't beetween rosetta and the fireface, but with the fireface and max/msp 4.5 

One more question :
You said :
////
4.5.7 was a PowerPC release, so an Intel Mac will run it under
Rosetta emulation, and not give it access to audio hardware over and above the built-in stereo.
/////
I don't understand Why the fireface 400 can't work with rosetta.
And also, if I just wanted to use built-in soundcard, I should have                 
an acces to the DSP status, no ?

So may  be my problem isn't beetween rosetta and the fireface, but with the fireface and max/msp 4.5 
What could I do to resolve this ?????

If your DSP Status window isn't available, you've probably got something 

screwy in your file preferences. I recommend deleting your Max 

> What could I do to resolve this ?????
>

If your DSP Status window isn't available, you've probably got something 
screwy in your file preferences.  I recommend deleting your Max 
Preferences folders and trying again.

>If your DSP Status window isn't available, you've probably got >something

>screwy in your file preferences. I recommend deleting your Max

>Use MaxMSP 4.6.2
not possible because of the externals !

>screwy in your file preferences. I recommend deleting your Max
>Preferences folders and trying again.

Is there a '/' in your search path, eg. a folder

> not possible because of the externals !

> >If your DSP Status window isn't available, you've

> >screwy in your file preferences. I recommend

Is there a '/' in your search path, eg. a folder
called Max/MSP ?  
cheers
Roger

>
> >Use MaxMSP 4.6.2
> not possible because of the externals !
>
> >If your DSP Status window isn't available, you've
> probably got >something
>
>
> >screwy in your file preferences. I recommend
> deleting your Max
> >Preferences folders and trying again.
>
> I did it but nothing has changed.
>
> Any other solution ?
> Thanks,
>
> ben
>


>> screwy in your file preferences. I recommend deleting your Max

What is the path of your MaxMSP 4.6 folder? Does it contain a slash?

>> screwy in your file preferences. I recommend deleting your Max
>> Preferences folders and trying again.
>
> I did it but nothing has changed.
>
> Any other solution ?

file from the 4.6.2 version, and put it in the 

ej
////////
Is there a '/' in your search path, eg. a folder
called Max/MSP ? 
cheers
Roger
/////////////

Finally, I took the "DSP Status.pat"
file from the 4.6.2 version, and put it in the 
MaxMSP4.5>patches>editors folder.

no access to dsp status