/? Object
Hi,
I can still put the /? Objekt into a patch, but I get the following error Message in the Max Window:
? error: can't fragload /~ (missing <>), err -2804
seems you have to reinstall the 10.4.6 update using the combo version
this time...
Best,
ej
After reading this message I tried to make a "/?" object. It crashed
Max. I'm on 10.4.6, with the combo updated, and Max 4.5.7. No other
problems with my install.
--
barry threw :: sound | (if you would see the stars clearly,
http://www.barrythrew.com | look hard at the surrounding darkness)
bthrew(at)gmail(dot)com | -Ooka Makoto
857-544-3967 |
On further inspection, this crash occurs when instantiating an object
with "/" followed by any other symbol (that isn't actually an object).
e.g. [/!] [/@] [/?]
[/~] works fine.
b
--
barry threw :: sound | (if you would see the stars clearly,
http://www.barrythrew.com | look hard at the surrounding darkness)
bthrew(at)gmail(dot)com | -Ooka Makoto
857-544-3967 |
There was discussion a few months back about similar issues with
naming objects slash-digit: [/1], [/2], etc. Some people had crashes,
some people found Max was trying to instantiate Mach-o based externals.
Apparently no one, either inside or outside Cycling '74, was able to
ever work out exactly what was going on, other than there is
something wierd going on when Mach-o externals are installed.
The short answer is, unless you have an external named /?, don't try
to instantiate it. And, to underscore the obvious: you probably don't
*have* an object named /?
For gory details:
Feb06/index.html#39470> and follow the thread "mystery object".
-- P.
-------------- http://www.bek.no/~pcastine/Litter/ -------------
Peter Castine +---> Litter Power & Litter Bundle for Jitter
Heavy-Duty Mathematics for Everyday Use
iCE: Sequencing, Recording &
Interface Building for |home | chez nous|
Max/MSP Extremely cool |bei uns | i nostri|
http://www.dspaudio.com/ http://www.castine.de
Well, yeah. Obviously the answer is "stop doing that".
I am just of the opinion that any error that *crashes your program*
should be reported.
Thanks for the heads up. I'll go back to doing useful things.
b
--
barry threw :: sound | (if you would see the stars clearly,
http://www.barrythrew.com | look hard at the surrounding darkness)
bthrew(at)gmail(dot)com | -Ooka Makoto
857-544-3967 |
On 8-Jun-2006, at 5:46, Barry Threw wrote:
> I am just of the opinion that any error that *crashes your program*
> should be reported.
Fair enough. In fact, any unexpected and/or downright confusing
behavior ought to be reported.
I was basically just trying to point out a previous discussion for
edification and then summarized the only workaround that anyone found
back in February. This is an obscure-but-nasty bug, apparently no one
can track down the cause, and it's very likely to go away as Max on
Mac OS moves from CFM to Mach-O.
-- Peter
[Please cf the .sig from my previous post on this thread if you need it]