Hello list,
I'm curious what the specifications of the PD file format look like. Puckette has already posted *something* in 2001 about the connect rules, and stated that the rest of the specs are undocumented. Is there someone who has figured out already what the rest of the fileformat means? Of course it looks quite simple, but I want to make sure there are no mistakes from my side.
On Wed, 30 Jun 2004, Tjeerd Sietsma wrote:
I'm curious what the specifications of the PD file format look like. Puckette has already posted *something* in 2001 about the connect rules, and stated that the rest of the specs are undocumented. Is there someone who has figured out already what the rest of the fileformat means? Of course it looks quite simple, but I want to make sure there are no mistakes from my side.
"#N canvas" starts a new canvas (patcher or subpatcher or graph) "#X restore" ends that canvas (subpatcher or graph) "#X coords" = graph properties
"#X text" = Comment (Ctrl+5) "#X symbolatom" = Symbol (Ctrl+4) "#X floatatom" = Float (Ctrl+3) "#X msg" = Message (Ctrl+2) "#X obj" = All other kinds of objects
"#X connect [from] [outlet] [to] [inlet]" where boxes (objects etc) are numbered starting with 0 within a patcher; inlets/outlets are also numbered starting with 0, so the leftmost inlet is 0.
"#A" is for saved array data
anything else you need to know?
I'm not aware of an up-to-date specification, though I recall seeing a very old one written during the very early versions of Pd maybe.
Mathieu Bouchard http://artengine.ca/matju
Zitiere Mathieu Bouchard matju@sympatico.ca:
On Wed, 30 Jun 2004, Tjeerd Sietsma wrote:
I'm curious what the specifications of the PD file format look like. Puckette has already posted *something* in 2001 about the connect
rules,
and stated that the rest of the specs are undocumented. Is there
someone
who has figured out already what the rest of the fileformat means? Of course it looks quite simple, but I want to make sure there are
no
mistakes from my side.
of course the file-format is quite simplistic. the problem is (i guess), that miller refuses to document some things because of one reason (correct me if i am wrong): as soon as they are documented people can rely on there behaviour and thus things are kind of frozen. undocumented things are "likely to change" in the near future, the far future or never...
mfg.as.dr IOhannes
On Wed, 30 Jun 2004 09:05:01 +0200 (CEST), zmoelnig@iem.at said:
Zitiere Mathieu Bouchard matju@sympatico.ca:
On Wed, 30 Jun 2004, Tjeerd Sietsma wrote:
I'm curious what the specifications of the PD file format look like. Puckette has already posted *something* in 2001 about the connect
rules,
and stated that the rest of the specs are undocumented. Is there
someone
who has figured out already what the rest of the fileformat means? Of course it looks quite simple, but I want to make sure there are
no
mistakes from my side.
of course the file-format is quite simplistic. the problem is (i guess), that miller refuses to document some things because of one reason (correct me if i am wrong): as soon as they are documented people can rely on there behaviour and thus things are kind of frozen. undocumented things are "likely to change" in the near future, the far future or never...
Not maintaining backward-compatibility is no reason for not documenting a file format. I assume Miller Puckette rather spends his time programming/ doing his gig instead of writing documentation for the programs he wrote. Not only the fileformat is undocumented, but a some objects aren't docu- mented also. Fortunately the fileformat isn't too complicated, but it would be nicer if one could download the necessary docs somewhere.
On Thu, 1 Jul 2004, Tjeerd Sietsma wrote:
Not maintaining backward-compatibility is no reason for not documenting a file format. I assume Miller Puckette rather spends his time programming/ doing his gig instead of writing documentation for the programs he wrote. Not only the fileformat is undocumented, but a some objects aren't docu- mented also. Fortunately the fileformat isn't too complicated, but it would be nicer if one could download the necessary docs somewhere. --
Actually I have this document by Miller Puckette, dated 1997.
http://artengine.ca/matju/pd/Miller_Puckette_-_PD_File_Format.ps
Mathieu Bouchard http://artengine.ca/matju
OK, thanks to everyone for saying that basic questions are ok. Here's a basic request to get me started: Can anyone send me a PD file that takes as input a)a local file and b)a live feed from the pc, does some minimal processing and outputs it. Then I will be a long way down the road in my understanding and ability! Thanks, Ivan
Ivan Pope ivan@ivanpope.com http://ivanpope.com
Absent WithOut Leave: My life as an artist http://blog.ivanpope.com
The Man Who Invented The Internet http://blog.themanwhoinventedtheinternet.com
Ivan Pope wrote:
OK, thanks to everyone for saying that basic questions are ok. Here's a basic request to get me started:
what i meant by question was rather not: "can you send me a patch ?"
Can anyone send me a PD file that takes as input a)a local file and b)a live feed from the pc, does some minimal processing and outputs it. Then I will
here we go:
[open mysoundfile.wav, 1( | [readsf~] [adc~] | | [*~ ] | [dac~]
bless you! IOhannes
Ivan Pope wrote:
OK, thanks to everyone for saying that basic questions are ok. Here's a basic request to get me started: Can anyone send me a PD file that takes as input a)a local file and b)a live feed from the pc, does some minimal processing and outputs it. Then I will be a long way down the road in my understanding and ability!
Under the "Media" menu open the "Test Audio and MIDI" option. View these patches, they are a good example of how to get audio in and out of your soundcard. PD's built in documentation is excellent. And the docs are just PD patches so they're interactive, ctrl+e and you're in edit mode.
-lee
-
IOhannes m zmoelnig -
Ivan Pope -
lee -
Mathieu Bouchard -
Tjeerd Sietsma -
zmoelnig＠iem.at