no such object

Jul 31, 2006 at 4:53pm

no such object

is there a good technique to find the object causing a “no such object” error message
in a large complex patcher with abstractions, subpatchers & bpatchers which also contain abstractions, subpatchers & bpatchers

i have tried find but it doesnt seem to go into abstractions & bpatchers without closing and reopening in sub patchers

i also tried control/click but it doesn’t seem to list the object causing a “no such object” error message

#26990
Jul 31, 2006 at 5:24pm

On 31 Jul 2006, at 18:53, don malone wrote:

> is there a good technique to find the object causing a “no such
> object” error message
> in a large complex patcher with abstractions, subpatchers &
> bpatchers which also contain abstractions, subpatchers & bpatchers

Best technique I’ve found is to save all patcher files as text, and
use a decent text editor to find the occurrences.

– N.

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

#81254
Aug 13, 2006 at 5:00pm

don malone wrote:
> is there a good technique to find the object causing a “no such
> object” error message in a large complex patcher with abstractions,
> subpatchers & bpatchers which also contain abstractions, subpatchers
> & bpatchers

Save the patch as “test***” then delete half of it, and reopen. If its
vanished its in the half you deleted, if its still there, delete another
quarter… till it vanishes… (recursive Newtonesque method)

Though I would prefer a better debugging aid from Max itself a lot. I
hope for Max 5…

Stefan


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

#81255
Aug 13, 2006 at 6:00pm

#81256
Aug 13, 2006 at 6:05pm

Ouuups… Not to be read, ahemmm. Very sorry for the mistake :-$

f.e
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|

Stefan Tiedje wrote:
> don malone wrote:
>> is there a good technique to find the object causing a “no such
>> object” error message in a large complex patcher with abstractions,
>> subpatchers & bpatchers which also contain abstractions, subpatchers
>> & bpatchers
>
> Save the patch as “test***” then delete half of it, and reopen. If its
> vanished its in the half you deleted, if its still there, delete
> another quarter… till it vanishes… (recursive Newtonesque method)
>
> Though I would prefer a better debugging aid from Max itself a lot. I
> hope for Max 5…
>
> Stefan
>

#81257
Aug 14, 2006 at 3:46pm

On 13 Aug 2006, at 18:00, Stefan Tiedje wrote:

> Save the patch as “test***” then delete half of it, and reopen.

Or: open and save all the patchers as text, then grep through them
for the missing object.

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

#81258
Aug 14, 2006 at 5:36pm

Hi this might be even more complicated, but here it goes..

The max window actually displays the object thats missing:

* error: *(objects name):* No such object

1) Open all patches and subpatches (You can find out how many you’ve got and
their names by selecting “get info” in the main patch)

2) Perform a search of the object in the main patch. (edit:find) it should
check all subpatches for the word you look now.

With luck you might be able to find it this way. If this still doesnt work I
recommend Stefans suggestion: deleting little by little til you find where
it is.
good luck

jONE
—————–
producjohns@gmail.com

On 14/08/06, Nick Rothwell wrote:
>
>
> On 13 Aug 2006, at 18:00, Stefan Tiedje wrote:
>
> > Save the patch as “test***” then delete half of it, and reopen.
>
> Or: open and save all the patchers as text, then grep through them
> for the missing object.
>
>
> nick rothwell — composition, systems, performance — http://
> http://www.cassiel.com
>
>
>
>

#81259
Aug 14, 2006 at 9:24pm

find does not search subpatchers, bpatchers or abstractions

i eventually found all the missing objects
by opening as text and searching

#81260
Aug 15, 2006 at 10:22am

Nick Rothwell wrote:
> Or: open and save all the patchers as text, then grep through them for
> the missing object.

If you didn’t save them as text in the first place it wouldn’t be fast
and grep is only known by Unix geeks.
The problem ususally is that the offending part is burried inside of a
subpatcher of a subpatcher of a subpatcher made by someone who didn’t
save as text. And greping through the whole patch collection would find
a lot which is possibly not connected to the original patch and thus
wouldn’t help either…

Stefan


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

#81261

You must be logged in to reply to this topic.