lchoi

It appears that suddenly, my counter objects do not function at all: icon has a dotted edge, no inlets or outlets. Please help.

If I select it, floating inspector says: 

I select help for existing counter objects, 

I select help for new objects in which I typed "counter",

its counter object exhibits the same errors.

1. Using MaxMSP 4.5.7 on Windows XP, I have restored the MaxMSP 4.5/ and Cycling74 directories from a backup made at a time when counter was functioning fine. The problem still exists.

2. I downloaded and newly installed Max/MSP 4.6.3. The problem also exists with the new version.

3. Although I haven't checked every single object in MaxMSP, the problem appears to be unique to counter.

I'm now checking the search paths for files, folders, and subfolders named counter.

If I select it, floating inspector says: 
   No Objects Selected

In existing patchers, 
I select help for existing counter objects, 
counter.help IS NOT DISPLAYED,
max windows says:
   *error: poobah: no such object

In a newly created patcher, 
I try to add a counter, 
max windows says: 
   *error: counter: no such object

In newly created patchers, 
I select help for new objects in which I typed "counter",
counter.help IS DISPLAYED,
max windows says: 
   *error: counter: no such object
   *error: #X: No Such Object

NOTE: When counter.help is displayed:
   its counter object exhibits the same errors.

error-counter-no-such-object

It appears that when I simplified the MaxMSP search path, counter now works. However, I've yet to determine what really caused the problem. Perhaps one of the following?

* a hidden file or folder also named counter

* recursive paths (caused by aliases within the path)

* search path too long
* a hidden file or folder also named counter
* recursive paths (caused by aliases within the path)


> * a hidden file or folder also named counter

maybe a counter.js - never use the same name for js - java and objects...

This could be hidden in a Max standalone or in a jar (java)...

If you increase your search path bit by bit again you'll find it...

lchoi schrieb:
> * a hidden file or folder also named counter

maybe a counter.js - never use the same name for js - java and objects...
This could be hidden in a Max standalone or in a jar (java)...

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


TTBOMK this is not an issue. I've had quite long Search Paths without problem, and I've heard of search paths encompassing entire hard disks. You don't want to do this because it slows the launch of Max down considerably. But I don't believe it causes bad behavior

> * recursive paths (caused by aliases within the path)

That will be it. It could be a counter.js (as Stefan suggests) but also a counter.txt or counter.mxb or counter.mxt or counter without suffix. Don't forget that standalones in the search path are also searched (Mac OS standalones are simply folder hierarchies with a few special attributes).

If you're on Mac OS, Spotlight is your friend in this kind of situation.

That will be it. It could be a counter.js (as Stefan suggests) but also a counter.txt or counter.mxb or counter.mxt or counter without suffix. Don't forget that standalones in the search path are also searched (Mac OS standalones are simply folder hierarchies with a few special attributes). 

If you're on Mac OS, Spotlight is your friend in this kind of situation.


I had the similar problem and faced it a lot of times. I often solve this type of problems using "Long Path Tool". It helped me in solving this error and all related errors.

...a hidden file or folder also named counter

I had the same problem but with different reports in the console. I'm a newbie in Max that's why.

The error practically said that naming a patcher file with the same name as an object it contains is not permitted. Therefore if I name my patcher file "Counter.maxpat" and a counter object is present in the patcher, it will create an error.

As the error message was obvious, I renamed "Counter.maxpat" in something like "Exercice with counter.maxpat", and there's no more error, I can proceed.