segeke

Afterwards, the FFT object and "/~" object of MaxMSP4.5.7 cannot be used.

The error message and the object are the following.

? error: can't fragload fftin~ (missing <>), err -2804

? error: can't fragload fftout~ (missing <>), err -2804

? error: can't fragload fft~ (missing <>), err -2804

? error: can't fragload gizmo~ (missing <>), err -2804

? error: can't fragload ifft~ (missing <>), err -2804

? error: can't fragload /~ (missing <>), err -2804

? error: can't fragload burrow~ (missing <>), err -2804

? error: can't fragload dentist~ (missing <>), err -2804

? error: can't fragload disarray~ (missing <>), err -2804

? error: can't fragload drown~ (missing <>), err -2804

? error: can't fragload ether~ (missing <>), err -2804

? error: can't fragload morphine~ (missing <>), err -2804

? error: can't fragload pvcompand~ (missing <>), err -2804

? error: can't fragload pvoc~ (missing <>), err -2804

? error: can't fragload scrape~ (missing <>), err -2804

? error: can't fragload shapee~ (missing <>), err -2804

? error: can't fragload swinger~ (missing <>), err -2804

? error: can't fragload taint~ (missing <>), err -2804

? error: can't fragload thresher~ (missing <>), err -2804

? error: can't fragload vacancy~ (missing <>), err -2804

? error: can't fragload xsyn~ (missing <>), err -2804

I updated it to MacOS10.4.6 today. 
Afterwards, the FFT object and "/~" object of MaxMSP4.5.7 cannot be used.
The error message and the object are the following.

"fftout~"
? error: can't fragload fftout~ (missing <>), err -2804

? error: can't fragload xsyn~ (missing <>), err -2804


problem-of-fft-object-of-macos10-4-6-and-maxmsp4-5-7

I can reproduce this on my system. The veclib errors, at least. I don't 

have FFTease, but InterfaceLib errors are typically the result of trying 

to use an OS9 object in OSX. I don't know if that's the case here, 

though. Looks like Apple removed some stuff from the CFM Carbon library 

in the most recent update. How nice of them.

I can reproduce this on my system. The veclib errors, at least. I don't 
have FFTease, but InterfaceLib errors are typically the result of trying 
to use an OS9 object in OSX. I don't know if that's the case here, 
though. Looks like Apple removed some stuff from the CFM Carbon library 
in the most recent update. How nice of them.

Quote: Jeremy Bernstein wrote on Tue, 04 April 2006 05:37

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

> I can reproduce this on my system. The veclib errors, at least. I don't 

> have FFTease, but InterfaceLib errors are typically the result of trying 

> to use an OS9 object in OSX. I don't know if that's the case here, 

> though. Looks like Apple removed some stuff from the CFM Carbon library 

> in the most recent update. How nice of them.

> Am 04.04.2006 um 13:30 Uhr schrieb shigeki tamura:

> > Afterwards, the FFT object and "/~" object of MaxMSP4.5.7 cannot be 

> > The error message and the object are the following.

Quote: Jeremy Bernstein wrote on Tue, 04 April 2006 05:37
----------------------------------------------------
> I can reproduce this on my system. The veclib errors, at least. I don't 
> have FFTease, but InterfaceLib errors are typically the result of trying 
> to use an OS9 object in OSX. I don't know if that's the case here, 
> though. Looks like Apple removed some stuff from the CFM Carbon library 
> in the most recent update. How nice of them.
>
> jb
>
> Am 04.04.2006 um 13:30 Uhr schrieb shigeki tamura:
> > I updated it to MacOS10.4.6 today. 
> > Afterwards, the FFT object and "/~" object of MaxMSP4.5.7 cannot be 
> > used.
> > The error message and the object are the following.
> >
> >
>
----------------------------------------------------


Yes, I think for now, users should NOT upgrade to this version of the 

OS. If it's too late, you'll need to downgrade if you need to use these 

Yes, I think for now, users should NOT upgrade to this version of the 
OS. If it's too late, you'll need to downgrade if you need to use these 
objects immediately.

after a quick test here, everything seems to be fine.

did the upgrade to 4.6 this morning too, with the combo-updater.

after a quick test here, everything seems to be fine.
did the upgrade to 4.6 this morning too, with the combo-updater.
?
hth
hans

hans w. koch
im krahnenhof 11
d-50668 koeln
+49-221-554902
www.hans-w-koch.net


>Yes, I think for now, users should NOT upgrade to this version of 

>the OS. If it's too late, you'll need to downgrade if you need to 

>Yes, I think for now, users should NOT upgrade to this version of 
>the OS. If it's too late, you'll need to downgrade if you need to 
>use these objects immediately.

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

Ah, wonderful! OK, confirmed. Running the Combo Updater solves the 

problem for me, too (even on top of the via-the-Software-Update updated 

Ah, wonderful! OK, confirmed. Running the Combo Updater solves the 
problem for me, too (even on top of the via-the-Software-Update updated 
10.4.6).

You did make a complete bootable backup of your system before doing the 

Luckily it looks like you get a second chance this time.

You did make a complete bootable backup of your system before doing the 
upgrade, didn't you?

>You did make a complete bootable backup of your system before doing 

>You did make a complete bootable backup of your system before doing 
>the upgrade, didn't you?
>

Anyone know what did apple changed in those libs ?

Looks like there's just a problem with the "delta" updater. Use the 

Looks like there's just a problem with the "delta" updater. Use the 
"combo" and you won't have a problem.

Problem of FFT object of MacOS10.4.6 and MaxMSP4.5.7.