hello list,

believe it or not, only now i realize that you can't read a stereo
sound file with the table/tab opcodes. somehow i had assumed you could
read stereo tables using two outputs, like in loscil. 

i'm trying to make my students consider using csound instead of a
standard audio editor when working on "concrete" pieces. reading
sound files from tables is one of the basic techniques, of course. 

please excuse the ignorance of a non-programmer who doesn't know the
internals of csound, but would it be too difficult to adapt opcodes like
table and tab to read stereo tables?

best,

lj

But is it not just as easy to split a stereo file into
two tables and use two instances of tab etc(or the
whole instrument) to deal with it?

Victor

At 12:57 06/06/2008, you wrote:


>hello list,
>
>believe it or not, only now i realize that you can't read a stereo
>sound file with the table/tab opcodes. somehow i had assumed you could
>read stereo tables using two outputs, like in loscil.
>
>i'm trying to make my students consider using csound instead of a
>standard audio editor when working on "concrete" pieces. reading
>sound files from tables is one of the basic techniques, of course.
>
>please excuse the ignorance of a non-programmer who doesn't know the
>internals of csound, but would it be too difficult to adapt opcodes like
>table and tab to read stereo tables?
>
>best,
>
>lj
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>csound"

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth

sorry if I misunderstood your question, but when you do something like

giChan1		ftgen	0, 0, 0, 1, "stereofile, wav", 0, 0, 1
giChan2		ftgen	0, 0, 0, 1, "stereofile, wav", 0, 0, 2

aL		table	andx, giChan1
aR		table	andx, giChan2

you can use the same index for both channels (and what you like to do  
more). Best -

	joachim



Am 06.06.2008 um 13:57 schrieb luis jure:

>
>
> hello list,
>
> believe it or not, only now i realize that you can't read a stereo
> sound file with the table/tab opcodes. somehow i had assumed you could
> read stereo tables using two outputs, like in loscil.
>
> i'm trying to make my students consider using csound instead of a
> standard audio editor when working on "concrete" pieces. reading
> sound files from tables is one of the basic techniques, of course.
>
> please excuse the ignorance of a non-programmer who doesn't know the
> internals of csound, but would it be too difficult to adapt opcodes  
> like
> table and tab to read stereo tables?
>
> best,
>
> lj
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

could you have them use diskin(2)

also don't know why you are using table instead of loscil, but 
lposcil(or better lposcil3) might have what you need -- you still need 
to use 2 ftables and opcodes but you can at least used deferred table 
length.

i guess if you do need to have the sound in memory (instead of using 
diskin) you could make a UDO that wraps 2 ftgens and 2 lposcils and give 
that to your students..

-m

On Fri, 6 Jun 2008, luis jure wrote:

>
>
> hello list,
>
> believe it or not, only now i realize that you can't read a stereo
> sound file with the table/tab opcodes. somehow i had assumed you could
> read stereo tables using two outputs, like in loscil.
>
> i'm trying to make my students consider using csound instead of a
> standard audio editor when working on "concrete" pieces. reading
> sound files from tables is one of the basic techniques, of course.
>
> please excuse the ignorance of a non-programmer who doesn't know the
> internals of csound, but would it be too difficult to adapt opcodes like
> table and tab to read stereo tables?
>
> best,
>
> lj
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

El Fri, 06 Jun 2008 13:01:11 +0100
Victor Lazzarini  escribió:

> But is it not just as easy to split a stereo file into
> two tables and use two instances of tab etc(or the
> whole instrument) to deal with it?

of course, i'm aware of that possibility and it's the solution i
suggested to my students. the only drawback is that you have to
duplicate many lines of code. also if you use dozens of sound files in
a piece, the number of tables increase considerably.

i was just bit surprised that some opcodes like loscil support reading
stereo tables but the table opcodes don't, and i thought it could be a
good idea to implement something similar there, that's all.

thanks for your attention,

lj