bkshepard

I'm trying to use a variable to tell a buffer to read different audio files and so I'm using the following configuration to change a file's name for the buffer.

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.

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.


does-need-a-space-in-front

On 24 oct. 07, at 06:11, Brian Shepard wrote:

> 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 

> 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.

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.

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.


On 24 oct. 07, at 19:50, Brian Shepard wrote:

> 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 

> 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.

You're right, sprintf works great! Thanks for the tip.

You're right, sprintf works great!  Thanks for the tip.


Does $ need a space in front?