Connect a [print] object to the output of one of the [==] objects to see what it is doing, or read the help file.

If your number is equal to 1, then it outputs 1, otherwise it outputs 0. You also need to familiarise yourself with execution order - look at the [trigger] helpfile.

However, you might be better off using [select] as follows:

[0 \
|
[sel 1 2 ]
| |
[12 ( [0 (
| |
| /
| /
| /
[0 \

You can also set autoscale to output the range in the direction you want, eg:

[autoscale 1500 0]

You could try using [folder_list] from hcs to compile a list of the files that exist, then read them from that list.

Here's another solution using [tabdump] from zexy

http://www.pdpatchrepo.info/hurleur/reading_array.pd

You could try using the /dev/urandom output via the [shell] object. I had trouble getting it to reliably report a number each time so I forced it with some [spigot] logic. See attached patch.

http://www.pdpatchrepo.info/hurleur/alternative_random_number.pd

A table or array is filled with a number of values, each of which can be addressed by it's 'index'. Look at the help file for [tabwrite]

Put them in all in one directory, then select them randomly with [playlist], or use [folder_list] to load them to [textfile] or [msgfile]. In either case, you can then output the filename to [readsf~].

Use [random] for shuffle play.

[echo 'hola mundo';( is a message, not an object.

[shell] can be found in the ggee library.

Maybe try adding a delay to the loadbang?

[loadbang]
|
[del 1000]
|
[open 1(
|
[comport]

Send a message to pd like:

[; pd midi-dialog 1 0 0 0 0 0 0 0 1 1(

to select the relevant midi device.

You can check the exact message required by receiving pd messages like so:

[r pd]
|
[print]

and then change the midi-settings in the menu.

I would write a shell script and call it from the [shell] object. You will need to parse the output of this command:

osascript -e 'get volume settings'

What about this?

[X] - toggle
|
[select 1]
| /
[random 10]
| /
| /
| /
| /
|/
[outlet]

Your multiplication object

• after the two [expr] objects doesn't output the new samples playback value until you change the start or end points of the loop, so the [phasor~] is still receiving the previous sample's playback frequency. If the samples are of different length then the new one will be at the wrong speed! Try banging the start/end point value out again once the new sample is loaded to make [expr 1 /$f1] calculate the new [phasor~] frequency. Or reset the sample playback points to zero, which will also send the value out again. Make sure you use a [trigger] to determine execution order.

http://www.pd-tutorial.com/english/patches/3-4-2-10-karplus-strong1.pd is the only vanilla compatible patch. The other ones use [z~] from zexy.

I also found [mapping/iir] quite useful for this purpose.

It works for me in 0.43.4-extended-20130117 on OS 10.6.8.

Try importing the cyclone or markex library. Or use [cup] from ekext. Or just build your own with a [f]x[+ 1] as in creb's [count].