michrid

For some reason, I can only load abstractions into a Bpatcher when they reside in certain places on my system such as the desktop. Moving the file one-step deeper and reloading the abstraction throws a 'file not found' error once it gets to the main folder in which my patches are all stored.

I noticed someone mentioned having other abstractions with same name could be a problem but I have also tried unique names and still the same problem.

Has anyone else encountered this or know what the problem might be?

For some reason, I can only load abstractions into a Bpatcher when they reside in certain places on my system such as the desktop. Moving the file one-step deeper and reloading the abstraction throws a 'file not found' error once it gets to the main folder in which my patches are all stored. 

bpatcher-strange-behaviour

Quote: michrid wrote on Sat, 20 January 2007 04:39

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

>>> For some reason, I can only load abstractions into 

>>> a Bpatcher when they reside in certain places on my 

abstractions (and all other files a max patch is pointing to)

have to be in your max search path - it probably only works

on your desktop because you saved your root patch to the desktop

too before, so that at the moment a valid relative path is

Quote: michrid wrote on Sat, 20 January 2007 04:39
----------------------------------------------------
>>> For some reason, I can only load abstractions into 
>>> a Bpatcher when they reside in certain places on my 
>>> system such as the desktop.

abstractions (and all other files a max patch is pointing to)
have to be in your max search path - it probably only works
on your desktop because you saved your root patch to the desktop
too before, so that at the moment a valid relative path is
present.

> For some reason, I can only load abstractions into a Bpatcher when

> they reside in certain places on my system such as the desktop.

> Moving the file one-step deeper and reloading the abstraction throws

> a 'file not found' error once it gets to the main folder in which my

> Has anyone else encountered this or know what the problem might be?

I think it is a VERY bad idea to include the desktop or a complete 

partition into the search path. Especially the desktop might cause 

problems. Try to put it into the patches folder of your Max folder, that 

is part of the searchpath by default. (And get rid of the desktop in the 

What other "certain" place don't work for you?

Mike wrote:
> For some reason, I can only load abstractions into a Bpatcher when
> they reside in certain places on my system such as the desktop.
> Moving the file one-step deeper and reloading the abstraction throws
> a 'file not found' error once it gets to the main folder in which my
> patches are all stored.

I think it is a VERY bad idea to include the desktop or a complete 
partition into the search path. Especially the desktop might cause 
problems. Try to put it into the patches folder of your Max folder, that 
is part of the searchpath by default. (And get rid of the desktop in the 
search path).

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


Bpatcher - Strange behaviour