Hi,
I copied all of the examples out of the application package into
another disk. everything is working fine. However when I was fiddling
around I realized that pd would only open abstractions if they are
exactly inside the folder that they were. For instance, the patch /
3.audio.examples/D02.adsr.pd would not work if it is opened from a
different folder.
I do not understand that. I'm not talking about an experimental patch
that has stuff changed, the same patch just "saved as" doesn't work.
I'd appreciate any advice. I tried to add the folder inside the
application package to the startup path, but for some reasons that I
don't understand the configuration is not updated (and I don't know
if that would solve the problem in the first place).
Best Jurgen
On Sat, September 20, 2008 4:02 pm, Lao Yu wrote:
exactly inside the folder that they were. For instance, the patch / 3.audio.examples/D02.adsr.pd would not work if it is opened from a different folder.
How do you open it? Are you opening it from the "help browser"?
Steffen,
On Sep 20, 2008, at 10:22 PM, Steffen Juul wrote:
How do you open it? Are you opening it from the "help browser"?
from the "open" dialog. when I invoke an abstraction I create a new
object and give it the name of the abstraction. in the case of
"output~" that I mention to Claude the abstraction that I create in
my patch wouldn't look like the one in the "figs" folder which I want
to use.
Hmmm....
Best Jurgen
Hi
i ran into similar situations in the past and use the following
procedure now.
Which can easily adapted if you want to copy a complicated (meaning:
consinsting of many different abstractions, that you got from
collections, built yourself or whatever).
So in your example i would open the example patch (the main-patch)
and as you did save to a different location.
Then i would create a folder next to the target location and call it
maybe "abs" or "lib"
Then i would add a "declare" - statement including the new folders (i
noticed that on OSX you need always the Full path whereas on XP and
linux the relative path is sufficient)
And the open all the abstractions contained in the main original path
and save the with the same names in the newly created folders....
That way you can easily copy "projects" from one computer to another... I use several folders where i collect the abstractions i use.
For example i dont want to have pd look into all the abstraction
folders included in pd-extended. It was mentioned before that this
increases loading time.
So i just copy the one or two abstractions i use from maybe "list- abs" or "mapping" and thats it....
Maybe that can help you....
Does someone recommend a different procedure ??
All the Best
Luigi
On Sep 20, 2008, at 7:32 PM, Lao Yu wrote:
Steffen,
On Sep 20, 2008, at 10:22 PM, Steffen Juul wrote:
How do you open it? Are you opening it from the "help browser"?
from the "open" dialog. when I invoke an abstraction I create a new object and give it the name of the abstraction. in the case of "output~" that I mention to Claude the abstraction that I create in my patch wouldn't look like the one in the "figs" folder which I want to use.
Hmmm....
Best Jurgen
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Lao Yu wrote:
Hi,
I copied all of the examples out of the application package into
another disk. everything is working fine. However when I was fiddling around I realized that pd would only open abstractions if they are
exactly inside the folder that they were. For instance, the patch / 3.audio.examples/D02.adsr.pd would not work if it is opened from a
different folder.
Did you copy all the files? Or just that one file?
I do not understand that. I'm not talking about an experimental patch
that has stuff changed, the same patch just "saved as" doesn't work.
A Pd program in general consists of multiple files - the "top level patch", the "abstractions" used by it (and the ones used by them, etc) and sometimes some "externals" too. If you save just one of those files somewhere else, how is Pd supposed to know where the other files are when you load it again?
Quick solution: keep all files belonging to one program in the same folder.
Other solution: add the folders containing the pieces of your program to Pd's -path list.
I'd appreciate any advice. I tried to add the folder inside the
application package to the startup path, but for some reasons that I
don't understand the configuration is not updated (and I don't know
if that would solve the problem in the first place).
Did you restart Pd after changing the settings?
Best Jurgen
Claude
Hi,
On Sep 20, 2008, at 10:35 PM, Claude Heiland-Allen wrote:
Did you copy all the files? Or just that one file?
I copied the entire contents of the package, all the folders that
numbered "1.manual" to "8.sound".
If you save just one of those files somewhere else, how is Pd
supposed to know where the other files are when you load it again?
I understand that, because when I keep the patch in the original
place it works as expected. But from how it looks like the path in
the preferences is absolute (by default), not relative. To me this
means that whenever I load a pd patch that uses abstractions which
are in-built pd must find those. tell me if I'm wrong.
Did you restart Pd after changing the settings?
I realized that pd "vanilla" and pd extended use the same plist - so
I deleted one of them and use only one package. now saving the path
works and the adsr abstraction gets loaded as expected.
However now my patch saved elsewhere doesn't load the "output~"
abstraction, although I linked all folders in the patch, including
the very obscure "figs" folder which contains the "output~" file.
gasp, this is far from reasonable. And the manual is very quiet about
this.
Thanks Claude, very friendly. I will continue my search. How do you
work? Until now I do not know under which name the abstraction is
saved and how pd makes reference to it.
Jurgen
Claude
-
Claude Heiland-Allen -
Lao Yu -
Luigi Rensinghoff -
Steffen Juul