Brendan

How (or where) do I have to save a patch in order to be able to use it as an object in a new patch?

I wrote the patch and saved it, but when I typed the saved name as an object I got an error message saying that that object does not exist. I assume there is a dedicated folder that I should be saving in?

I wrote the patch and saved it, but when I typed the saved name as an object I got an error message saying that that object does not exist.  I assume there is a dedicated folder that I should be saving in?

patch-as-object

>How (or where) do I have to save a patch in order to be able to use it as

Save it in a folder that's in the search path. Which folders to be

included in the search path is defined in the "Options > File

Preferences..." menu. You might want to create a seperate folder for your

>How (or where) do I have to save a patch in order to be able to use it as
>an object in a new patch?

Save it in a folder that's in the search path. Which folders to be
included in the search path is defined in the "Options > File
Preferences..." menu. You might want to create a seperate folder for your
own abstractions.

It has to be saved in your Max preferences paths, or in the same 

folder as the the patch you want to put it in.

It has to be saved in your Max preferences paths, or in the same  
folder as the the patch you want to put it in.

You have to put it in your externals folder along with the other 

You have to put it in your externals folder along with the other  
objects.

if there is any default location for patches then 

it is the "patches" folder, the "externals" folder

is only needed if you want to include your patch 

but you can keep your patches anywhere in the search 

a relative path to the mother path is enough to find it

back on another computer or operating system, or after

if there is any default location for patches then 
it is the "patches" folder, the "externals" folder
is only needed if you want to include your patch 
in the object list.

but you can keep your patches anywhere in the search 
path - or even outside.
a relative path to the mother path is enough to find it
back on another computer or operating system, or after
moving the folder.
/home/dektop/mainpatch
/home/dektop/subpatch


> You have to put it in your externals folder along with the other objects.

The externals folder works, but I think its a bad idea to use it for 

that purpose. Keep it for the original externals.

And of course the answer to the original question has really to point 

out that there is enough documentation, which gets you faster going than 

asking this kind of stuff on the list. Don't forget "Getting started" 

and "Tutorials and Topics". Definitely start with the tutorials.

I usually use one Folder for all Stuff I create and the 3rd party tools 

I am going to use, and point to it in the file preferences (Options menu).

Corey Fuller wrote:
> Brendan,
>
> You have to put it in your externals folder along with the other  objects.

The externals folder works, but I think its a bad idea to use it for 
that purpose. Keep it for the original externals.

And of course the answer to the original question has really to point 
out that there is enough documentation, which gets you faster going than 
asking this kind of stuff on the list. Don't forget "Getting started" 
and "Tutorials and Topics". Definitely start with the tutorials.

I usually use one Folder for all Stuff I create and the 3rd party tools 
I am going to use, and point to it in the file preferences (Options menu).

  [][]  [][][]  [][]  [][][]
[][][][][][][][][][][][][][][]

         Stefan Tiedje
         Klanggestalter
     Electronic Composition
               &
         Improvisation

            /~~~~~
     \   /|() ()|
     ))))) )|  |  |( \
     ///     _/)/ )))))
             ___/   ///

-------------------------x----
--_____-----------|-----------
--(_|_ ----|-----|-----()----
-- _|_)----|-----()-----------
----------()------------x-----

14, Av. Pr. Franklin Roosevelt,
94320 Thiais, France
Phone at CCMIX +33-1-49 77 51 72


You are right, Stefan.
Thanks for offering a better solution.

Patch as Object