I have made a small sampler patch.

I wanted to know how to read the file from my hard rive as soon as i open the patch
so i don't have to reload samples every time it opens

I will appreciate any sort of help

Hi,

You can do something as simple as this:

Is that what you are looking for?

Take care,
Gilberto

PS: sorry for the spelling mistakes in the image above, it's still too early for me here

I think it's the space in your file's path. Instead of /Users/you/Desktop.PD Samples/Clp (8Voices).wav, try changing it to /Users/you/Desktop/PD_samples?Clp_8Voices.wav and see if that works...

@jjegede01: Besides the spaces, I think the main problem is order of bangs:

1. open the file
2. send 1 to sfread~

Use [trigger] to ensure the right order...

@xbarbie Although it is always good practise to use triggers, I don't think there was any mistake with the order of bangs in my patch above. The file was always being opened for the next time it was going to be played, not just before it. Look: the [loadbang] would open it for the 1st playback. The 1st playback can finish in two ways: either by itself if the file has been fully played, in which the [readsf~] rightmost outlet would reopen the file for the next time, or when the user set the toggle to 0, in which case the file would also be reopened for the next time.

But of course your patch above is of course much more elegant.

Cheers!
Gilberto

I tried the bang order thing and it seems to have worked in one case because the error message changed to say there is no such file in directory.

So i i tried to replace the spaces with underscores and it was recognising the path correctly.

so you were both right.

However at the end it still said no such file.. exists

But this file is on my hard drive in this exact place
is this a bug

Pd 0.45.4

@jjegede01 @xbarbie you guys are right, sorry for insisting on my mistake. What happened is that my patch was banging the open message while [readsf~] was still playing, and it caused problems. A simple trigger solves it. Once again, a lesson to be learned: using triggers is always the right way, even when you disagree with it

As for your problem, it's very strange. Are you sure you have the exact correct path? Is OS X case sensitive like Linux? If so, I would double check everything.

Also, you can use the following trick to write a file's complete path to a message:

Take care,
Gilberto

@gsagostinho said:

Also, you can use the following trick to write a file's complete path to a message:

It works

I Will just follow your method lol
Thanks to both of you

Maybe [readsf~] understands Unix syntax. In this case you should give it the following path /Users/you/Desktop/PD_Samples/Clp\(8Voices\).wav (parenthesis in Unix take a backward slash before the actual symbol, like this: \( for opening parenthesis and \) for closing) but this will result in a "keycode 92: dropped" message cause of the backward slashes. Try renaming your file without using parenthesis or any symbol non alphanumeric.

This technique is useful when you want to automate things without using [openpanel].

@alexandros I am using Linux, and Pd does not accept \, if you try to use it in a message or in an object, pd-extended will output keycode 92: dropped.

@gsagostinho I know, I wrote that above, only I didn't highlight it... that's why I suggested to remove the parenthesis altogether.

PD does not accept \ in windows either, and as jjegede01 is using osx it looks as though pd (all versions) use \ for a reserved purpose.

Pd uses "space" to delimit atoms in a list, and so (in windows at least) we are forever typing "_" to glue stuff together. Is that true in Linux and OSX as well? .... probably/definitely? That is why pd cannot tolerate spaces.

Windows does not like spaces for similar reasons. It's a "Dos" thing. If you want to give windows a path (to a file) and the path contains any space then windows (much like pd) will think that you have arrived at the end of the message when it sees the "space". This is solved in windows by putting the whole path in quotes......."c:/user/lala/desktop/PD where I keep my patches/"... and in this way windows 'glues" the path together in a batch file.

//\\"space"......it isn't easy! Note that this forum has particular ways of dealing with Keycode 92 and with spaces as well.
Special characters are often reserved, for use by the operating system or the application, and so best avoided for "everyday" use...... except in your passwords!

@alexandros You are obviously right, Alexandros, I believe I wrote my answer before finishing reading your full post. I'm sorry, I didn't get much sleep last night and I can barely write down my own name today

@gsagostinho no worries