max v2;
#N vpatcher 10 59 610 459;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 95 32 14 196617 3;
#P message 67 32 14 196617 2;
#P message 41 32 14 196617 1;
#P button 50 93 15 0;
#P newex 50 115 43 196617 delay 1;
#P message 50 142 72 196617 read file 3.aif;
#P message 50 64 95 196617 set read file $1.aif;
#P newex 50 170 67 196617 buffer~ files;
#P connect 7 0 1 0;
#P connect 6 0 1 0;
#P connect 5 0 1 0;
#P connect 1 0 4 0;
#P connect 4 0 3 0;
#P fasten 1 0 2 0 55 85 32 85 32 137 55 137;
#P connect 3 0 2 0;
#P connect 2 0 0 0;
#P pop;

My question—

Is it not possible to use $1 without a space in front of $-sign? When I use the text string [set read file$1.aif] it doesn’t work, but [set read file $1.aif] works just fine. Yeah, I know I can just name all my files as “file 1.aif,” “file 2.aif,” but I’d really prefer to not have a space in the file name. Thanks.

> My question—
>
> Is it not possible to use $1 without a space in front of $-sign?
> When I use the text string [set read file$1.aif] it doesn’t work,
> but [set read file $1.aif] works just fine. Yeah, I know I can
> just name all my files as “file 1.aif,” “file 2.aif,” but I’d
> really prefer to not have a space in the file name. Thanks.

Right, $n needs a space before. For string concatenation, have a look
to the sprintf object: [sprintf symout file %d.aif] should do what
you need.

HTH,
ej

Thanks for the tip on sprintf. I was afraid that would be the case. I may just opt for the space in the file name rather than the extra processing of sprintf since this will be a pretty processor-intensive patch when it’s done.

> ej,
>
> Thanks for the tip on sprintf. I was afraid that would be the
> case. I may just opt for the space in the file name rather than
> the extra processing of sprintf since this will be a pretty
> processor-intensive patch when it’s done.

I’ve never seen any problem of performance with sprintf. I wouldn’t
worry too much about the overhead.

ej