I'm running Max 4.6.2 on a Mac Pro (Intel 3GHz) running Max OS 10.4.9, and have used the Combo updater to ensure everything is up to date. I use an iLok, so have not installed the PACE software which is causing some users problems. (But previously the PACE software *was* installed, and the problem I'm about to describe happened then too).

There is an issue with umenu - once the object is created, and the Info window is opened (in order to populate the menu with items), the following error messages appear in the Max window:

Both objects DO exist in the externals folder. However, if I attempt to add them to a patcher manually, I get the same error messages. I have re-installed Max several times, and got the same problem with OS10.4.7.

The file search paths are set correctly, and include the externals folder. (Incidentally, trying to change File Preferences by deleting existing entries crashes Max!).

error: substitute: No such object
error: append: No such object
error: substitute: No such object
error: substitute: No such object

mad-messages

Quote: jgucc@mac.com wrote on Sun, 22 April 2007 13:21

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

> I'm running Max 4.6.2 on a Mac Pro (Intel 3GHz) running Max OS 10.4.9, and have used the Combo updater to ensure everything is up to date. I use an iLok, so have not installed the PACE software which is causing some users problems. (But previously the PACE software *was* installed, and the problem I'm about to describe happened then too).

> There is an issue with umenu - once the object is created, and the Info window is opened (in order to populate the menu with items), the following error messages appear in the Max window:

> Both objects DO exist in the externals folder. However, if I attempt to add them to a patcher manually, I get the same error messages. I have re-installed Max several times, and got the same problem with OS10.4.7.

> The file search paths are set correctly, and include the externals folder. (Incidentally, trying to change File Preferences by deleting existing entries crashes Max!).

Do you understand the Max Search Path concept?

Also, you say "add to a patcher manually"... does that mean you've used the Install... command? If you can't instantiate objects that have been installed, then the .mxo/.mxe/.mxd is probably corrupt.

The other common problem is to have a file with the same name as the object (in your case: append, substitute) lurking in your search path. Use Spotlight to check for bogus files.

Quote: jgucc@mac.com wrote on Sun, 22 April 2007 13:21
----------------------------------------------------
> I'm running Max 4.6.2 on a Mac Pro (Intel 3GHz) running Max OS 10.4.9, and have used the Combo updater to ensure everything is up to date. I use an iLok, so have not installed the PACE software which is causing some users problems. (But previously the PACE software *was* installed, and the problem I'm about to describe happened then too).
>
> There is an issue with umenu - once the object is created, and the Info window is opened (in order to populate the menu with items), the following error messages appear in the Max window:
>
> error: substitute: No such object
> error: append: No such object
> error: substitute: No such object
> error: substitute: No such object
>
> Both objects DO exist in the externals folder. However, if I attempt to add them to a patcher manually, I get the same error messages. I have re-installed Max several times, and got the same problem with OS10.4.7.
>
> The file search paths are set correctly, and include the externals folder. (Incidentally, trying to change File Preferences by deleting existing entries crashes Max!).
>
> Any ideas?
----------------------------------------------------

The other common problem is to have a file with the same name as the object (in your case: append, substitute) lurking in your search path. Use Spotlight to check for bogus files.


take a screenshot of your search path and post it here.

I think this must have been it, because I deleted some of the search paths I had created, and the problem went away. It's puzzling however, because if the search path to the externals folder were incorrectly configured, how was Max able to find any externals at all? Why was it unable to find just these, correctly locating others? And the search paths were configured by Max (I used the 'Choose' buttons in the File Preferences dialog) - I didn't configure them myself.

Thanks for your replies. 
>
> Probably a misconfigured search path.
I think this must have been it, because I deleted some of the search paths I had created, and the problem went away. It's puzzling however, because if the search path to the externals folder were incorrectly configured, how was Max able to find any externals at all? Why was it unable to find just these, correctly locating others? And the search paths were configured by Max (I used the 'Choose' buttons in the File Preferences dialog) - I didn't configure them myself. 

> I think this must have been it, because I deleted some of the search

> paths I had created, and the problem went away. It's puzzling

It was maybe caused by substitute and append objects which resided 

inside a java .jar file within one of the search path entries you 

deleted. If Max sees those first, it doesn't look further and complains. 

I consider the existing order of searching a design bug. Max should 

first look in the externals folder, then in the others...

A nice thing would be a Max specific search function, which would tell 

where Max found something. Its needed, because the OS doesn't look 

jg schrieb:
> I think this must have been it, because I deleted some of the search
> paths I had created, and the problem went away. It's puzzling
> however....

It was maybe caused by substitute and append objects which resided 
inside a java .jar file within one of the search path entries you 
deleted. If Max sees those first, it doesn't look further and complains. 
I consider the existing order of searching a design bug. Max should 
first look in the externals folder, then in the others...

A nice thing would be a Max specific search function, which would tell 
where Max found something. Its needed, because the OS doesn't look 
inside the jar files, but Max does...

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


> It was maybe caused by substitute and append objects which resided 

> inside a java .jar file within one of the search path entries you 

> deleted. If Max sees those first, it doesn't look further and complains. 

Ah! I didn't realise Max searched those too. Interesting.

> I consider the existing order of searching a design bug. Max should 

> first look in the externals folder, then in the others...

I agree. I usually change the search order as soon as I install Max, but even so I find its way of finding externals/abstractions etc. a little frustrating. It causes particular problems when I *duplicate* patches with abstractions and bpatchers inside them... Mind you, I think I could be a bit more sensible about the way I archive my patches :-)

> It was maybe caused by substitute and append objects which resided 
> inside a java .jar file within one of the search path entries you 
> deleted. If Max sees those first, it doesn't look further and complains. 
Ah! I didn't realise Max searched those too. Interesting.
> I consider the existing order of searching a design bug. Max should 
> first look in the externals folder, then in the others...
I agree. I usually change the search order as soon as I install Max, but even so I find its way of finding externals/abstractions etc. a little frustrating. It causes particular problems when I *duplicate* patches with abstractions and bpatchers inside them... Mind you, I think I could be a bit more sensible about the way I archive my patches :-)

mad messages