Thanks Funs, It’s really puzzling. I’ve included two short patchers—one my student emailed me, and one I built from his screen grab. Pd opens mine, but not his. Other than the coordinates and order of objects, the only difference I see is on the line with “wave sinesum.” His version has “;” after the coordinates, and my version has “:” after the coordinates. I tried changing that in his version, but still couldn’t get it to open.

My Student’s Version:

#N canvas 473 141 1016 656 10; #X floatatom 425 104 5 0 0 0 - - -; #X obj 332 316 dac~; #X obj 602 111 loadbang; #X obj 599 221 table wave; #X obj 254 34 notein 2; #X obj 265 119 pack f f; #X obj 243 71 mtof; #X obj 297 70 scale 0 127 0 0.9; #X obj 290 162 polypoly 4 1 sync-mod5~ wave; #X obj 327 279 catch~ 20-SIGNAL; #X obj 435 35 notein 1; #X obj 436 63 poly 1 1; #X obj 251 212 sync-mix1~ 0 1 10; #X obj 393 213 sync-mix1~ 2 3 11; #X obj 318 239 sync-mix1~ 10 11 20; #X obj 557 73 ctlin 1; #X msg 557 153 ; wave sinesum 512 1 $1 0.2 0.1; #X connect 0 0 8 1; #X connect 2 0 16 0; #X connect 4 0 6 0; #X connect 4 1 7 0; #X connect 5 0 8 0; #X connect 6 0 5 0; #X connect 7 0 5 1; #X connect 9 0 1 0; #X connect 9 0 1 1; #X connect 10 0 11 0; #X connect 10 1 11 1; #X connect 11 1 0 0; #X connect 15 0 16 0;

My Version:

#N canvas 648 45 840 625 10; #X obj 140 89 notein 2; #X obj 140 133 mtof; #X obj 185 134 scale 0 127 0 0.9; #X obj 140 169 pack f f; #X obj 140 238 polypoly 4 1 sync-mod5~ wave; #X obj 335 89 notein 1; #X obj 335 133 poly 1 1; #X floatatom 357 168 5 0 0 0 - - -; #X obj 523 105 ctlin 1; #X obj 599 148 loadbang; #X msg 523 194 : wave sinesum 512 1 $1 0.2 0.1; #X obj 552 311 table wave; #X obj 240 380 catch~ 20-SIGNAL; #X obj 241 424 dac~; #X obj 97 292 sync-mix1~ 0 1 10; #X obj 316 288 sync-mix1~ 2 3 11; #X obj 209 334 sync-mix1~ 10 11 20; #X connect 0 0 1 0; #X connect 0 1 2 0; #X connect 1 0 3 0; #X connect 2 0 3 1; #X connect 3 0 4 0; #X connect 5 0 6 0; #X connect 5 1 6 1; #X connect 6 1 7 0; #X connect 7 0 4 1; #X connect 8 0 10 0; #X connect 9 0 10 0; #X connect 12 0 13 0; #X connect 12 0 13 1;

-- Brian

On 5/17/11 3:32 PM, "Funs Seelen" funsseelen@gmail.com wrote:

2011/5/15 Brian Shepard brian@studioii.com

...

Greetings,

I have a student using Pd-extended on Ubuntu Linux, and I am using PD-extended in Mac OSX. When he sends me a file created on his computer, I can't open it, and get something like the following in the console:

error: #N: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object error: #X: no such object

When I send him patches, he can open them just fine. If he sends me a screen grab of his patch, I can build it and it works just fine. The problem only happens when I try to open the actual Pd file he sent. I've also tried opening them with a text editor, and everything looks fine. If I then copy/paste the text into a new text file and save it with the .pd suffix, though, it still won't open. Is there some issue regarding transferring between these two systems? Thanks for any help or advice.

I would compare the text file of your re-build to his original. Except for some XY-coordinates and order of objects/connections there shouldn't be a difference. I've never heard of such a problem and never had one, although I'm using Pd (vanilla) on both Ubuntu and OSX (and use patches cross-platform). I don't know if some different text encodings have been used in older versions. Maybe others know more about text encodings et cetera. If you want to be shure try to retype a small file instead of copy/paste. I once even typed a text file on a Windows computer and opened it later at home as a working pd-patch.

Funs

...

-- Brian

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Funs, that¹s it! Forcing Textedit to save with UTF-8 did the trick! Thank you so much!!!

On 5/18/11 1:58 AM, "Funs Seelen" funsseelen@gmail.com wrote:

Hi Brian,

I'm on OSX now and just copied both text files to Textedit where I saved them with UTF-8 encoding. I was able to open both with Pd-0.43-0 and Pd-0.42-5 (except for the objects of libraries I haven't loaded).

2011/5/18 Brian K. Shepard brian@studioii.com

...

Other than the coordinates and order of objects, the only difference I see is on the line with ³wave sinesum.² His version has ³;² after the coordinates, and my version has ³:² after the coordinates. I tried changing that in his version, but still couldn¹t get it to open.

The \;'' is used in the broadcast-message. Yours with:'' will not work there I believe, but that has nothing to do with the problem. The only thing I could think of is text encoding, but I don't know anything about that, except for that UTF-8 uses ASCII and adds a lot to it.

Funs

-- Brian

Brian Shepard Studio II Productions brian@studioii.com http://www.studioii.com/

The information contained in this e-mail may be totally bogus and is intended solely for the whim and entertainment of the named addressee. Access, copying, or re-use of the e-mail or any information contained therein by any other person is ridiculous and an utter waste of time. If you are not the intended recipient please get a life and stop snooping in other people's email.

Good question. Simply double-clicking the files wouldn't open them, so I was trying to open them with TextEdit and save them as a text file. The preferences in TextEdit were set to "Automatic" and once I set them to UTF-8, I was able to save and open the files in Pd. I just tried your suggestion of adding a space before the #N and that worked as well. Thanks for the tip!

On 5/19/11 12:51 PM, "Mathieu Bouchard" matju@artengine.ca wrote:

On Wed, 18 May 2011, Brian Shepard wrote:

...

Funs, that¹s it! Forcing Textedit to save with UTF-8 did the trick! Thank you so much!!!

So, which format had you used before, instead ?

If a file starts the UTF-8 BOM-code (EF BB BF in hex) it will cause "#N" to not be recognised, because it's parsed as 5 bytes instead of 2 (the 3-byte header will be counted as being part of the #N).

In a text file format that uses BOM, you can circument this problem by skipping a line or inserting a space before #N.

If the #N receive-symbol can't be contacted for a 'canvas' message, then the #X receive-symbol won't get registered, causing the other error messages. however, a subpatch declaration will suppress this message until the subpatch ends, because then, '#N canvas' will be correctly read, registering the receive-symbol #X, and '#X restore' unregisters #X.

I think that your default text format was already UTF-8, but with the 3-byte BOM header, instead of the usual headerless format.

---

| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC

-- Brian