Re: [Csnd] Csound6 and Spatialization

Re: [Csnd] Csound6 and Spatialization

Date	2013-09-04 10:45
From	jpff@cs.bath.ac.uk
Subject	Re: [Csnd] Csound6 and Spatialization
	I have out from an a-array working, and have written in to an a-array (not totally sure that it is correct yet). Hope to move onto the other operations (diskin2, vbap, fin, fout, pconvolve...) ==John ffitch

Date	2013-09-04 10:59
From	Ben Hackbarth
Subject	Re: [Csnd] Csound6 and Spatialization
	sounds good john. let me know when it is ready to test. -- ben On Wed, Sep 4, 2013 at 10:45 AM, <jpff@cs.bath.ac.uk> wrote: I have out from an a-array working, and have written in to an a-array (not totally sure that it is correct yet). Hope to move onto the other operations (diskin2, vbap, fin, fout, pconvolve...) ==John ffitch Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2013-09-04 18:07
From	Andres Cabrera
Subject	Re: [Csnd] Csound6 and Spatialization
	Hi John, Nice, this is very useful. I'm thinking if rather than having to do it individually for every opcode it could be generalized in the parser, so if you use an array in the inputs, the opcode is automatically instantiated that many times, having the output automatically go into an array. If some of the other inputs are not arrays, the same value will be copied to all instances, and if the array is of smaller size, then the array is "looped". This would simplify so many things! Cheers, Andrés On Wed, Sep 4, 2013 at 2:45 AM, <jpff@cs.bath.ac.uk> wrote: I have out from an a-array working, and have written in to an a-array (not totally sure that it is correct yet). Hope to move onto the other operations (diskin2, vbap, fin, fout, pconvolve...) ==John ffitch Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2013-09-04 18:12
From	Ben Hackbarth
Subject	Re: [Csnd] Csound6 and Spatialization
	yes, i totally agree with andrés! -- ben On Wed, Sep 4, 2013 at 6:07 PM, Andres Cabrera <mantaraya36@gmail.com> wrote: Hi John, Nice, this is very useful. I'm thinking if rather than having to do it individually for every opcode it could be generalized in the parser, so if you use an array in the inputs, the opcode is automatically instantiated that many times, having the output automatically go into an array. If some of the other inputs are not arrays, the same value will be copied to all instances, and if the array is of smaller size, then the array is "looped". This would simplify so many things! Cheers, Andrés On Wed, Sep 4, 2013 at 2:45 AM, <jpff@cs.bath.ac.uk> wrote: I have out from an a-array working, and have written in to an a-array (not totally sure that it is correct yet). Hope to move onto the other operations (diskin2, vbap, fin, fout, pconvolve...) ==John ffitch Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2013-09-06 11:34
From	Steven Yi
Subject	Re: [Csnd] Csound6 and Spatialization
	I'm not sure I really like the idea of this. It seems a lot like SuperCollider's array expansions which I sort of find awkward. In the end, it's very similar to the functional concept of mapping a function across a list of values. So instead of something like: asigs[] = vco2([440, 880, 1320], .5) you'd have something like: asigs[] = map(vco2, [440, 880, 1320], repeat(.5)) The first makes me thing there's some kind of opcode like: asigs[] vco2 kfreq[], kamp which there isn't. What if someone goes to look in the manual? Or how do you go about teaching something like this? I think it obscures the language personally, for the sake of short-hand convenience. The latter, IMO, is a well-understood and used concept in functional programming. Mapping an opcode function across the args would be simpler to implement, and I believe it would ultimately be easier to teach and use. steven On Wed, Sep 4, 2013 at 6:07 PM, Andres Cabrera wrote: > Hi John, > > Nice, this is very useful. I'm thinking if rather than having to do it > individually for every opcode it could be generalized in the parser, so if > you use an array in the inputs, the opcode is automatically instantiated > that many times, having the output automatically go into an array. If some > of the other inputs are not arrays, the same value will be copied to all > instances, and if the array is of smaller size, then the array is "looped". > This would simplify so many things! > > Cheers, > Andrés > > > On Wed, Sep 4, 2013 at 2:45 AM, wrote: >> >> I have out from an a-array working, and have written in to an a-array >> (not totally sure that it is correct yet). Hope to move onto the >> other operations (diskin2, vbap, fin, fout, pconvolve...) >> ==John ffitch >> >> >> >> >> Send bugs reports to the Sourceforge bug trackers >> csound6: >> https://sourceforge.net/p/csound/tickets/ >> csound5: >> https://sourceforge.net/p/csound/bugs/ >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" >> >> >

Date	2013-09-06 14:50
From	Andres Cabrera
Subject	Re: [Csnd] Csound6 and Spatialization
	Hi Steven, I really like the mapping solution. Like you say, much better than the implicit expansion. And it makes it easier and consistent to eventually do something like: asigs[] = parallel(pvsanal, ..... ) Where the processes are parallelized. Cheers, Andres On Fri, Sep 6, 2013 at 3:34 AM, Steven Yi <stevenyi@gmail.com> wrote: I'm not sure I really like the idea of this. It seems a lot like SuperCollider's array expansions which I sort of find awkward. In the end, it's very similar to the functional concept of mapping a function across a list of values. So instead of something like: asigs[] = vco2([440, 880, 1320], .5) you'd have something like: asigs[] = map(vco2, [440, 880, 1320], repeat(.5)) The first makes me thing there's some kind of opcode like: asigs[] vco2 kfreq[], kamp which there isn't. What if someone goes to look in the manual? Or how do you go about teaching something like this? I think it obscures the language personally, for the sake of short-hand convenience. The latter, IMO, is a well-understood and used concept in functional programming. Mapping an opcode function across the args would be simpler to implement, and I believe it would ultimately be easier to teach and use. steven On Wed, Sep 4, 2013 at 6:07 PM, Andres Cabrera <mantaraya36@gmail.com> wrote: > Hi John, > > Nice, this is very useful. I'm thinking if rather than having to do it > individually for every opcode it could be generalized in the parser, so if > you use an array in the inputs, the opcode is automatically instantiated > that many times, having the output automatically go into an array. If some > of the other inputs are not arrays, the same value will be copied to all > instances, and if the array is of smaller size, then the array is "looped". > This would simplify so many things! > > Cheers, > Andrés > > > On Wed, Sep 4, 2013 at 2:45 AM, <jpff@cs.bath.ac.uk> wrote: >> >> I have out from an a-array working, and have written in to an a-array >> (not totally sure that it is correct yet). Hope to move onto the >> other operations (diskin2, vbap, fin, fout, pconvolve...) >> ==John ffitch >> >> >> >> >> Send bugs reports to the Sourceforge bug trackers >> csound6: >> https://sourceforge.net/p/csound/tickets/ >> csound5: >> https://sourceforge.net/p/csound/bugs/ >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" >> >> > Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"