I'm a newbie and have difficulties reading some tutorials when the patch in question is described as text, not as a picture or an actual patch. For example, [cosinesum <arraysize> .5 -.5( .
I can guess some things, but not all. Could someone please tell me how to read such textual descriptions? Or maybe there is an online source with some directions?
Thanks a lot!
reading patch descriptions as text
Hi, in general we try to use some schematics in this forum (it's faster and easier to type than to create a patch, make a picture of it and upload it here). So objects are represented by [object name], such as [osc~], [spigot], etc. Then messages are represented by [message content(, such as [open(, [; pd dsp 1(, etc. Then we use |, /, __ and - to symbolise patch chords. Also, sometimes people use + to redirect a patch chord, such as in:
| +---+ |
Finally, in order to be able to use more than one space between two characters, you have to enter your text as "code". To do so, indent the whole text by 4 spaces in the beginning of each line:
[osc~ 440] | | [1( | | [spigot~] | / [dac~]
I hope that helps! Take care,
One last thing: when someone writes information inside <example> (or sometimes also as <example>), you should exchange it for another text that is relevant in your case. So let's say someone is trying to help you playback a file, but the person does not know what is the name of the file you want to play. They may advise you to send the message [open <filename>( to [readsf~]. So then, when you want to play a file named my-file.wav, you should simply have:
[open my-file.wav( | [readsf~]
without any < >. So in your example above [cosinesum <arraysize> .5 -.5(, if your arraysize is 100 then you should simply use [cosinesum 100 .5 -.5(
Great thanks! Yuhuu!