[Csnd] Trying to use string pfield as diskin2 name

[Csnd] Trying to use string pfield as diskin2 name

Date	2010-05-12 00:41
From	Tobiah
Subject	[Csnd] Trying to use string pfield as diskin2 name
	I read about strget, but when I try to use a string parameter: i "source" 12.5735575797 20.0 13931.8888193 443.435999165 0.941055156517 "yeah2.wav" 1.0 i "source" 17.8829973409 20.0 11811.3360861 266.403077568 0.5306028094 "yeah8.wav" 1.0 i "source" 8.14582259095 20.0 15854.7611801 768.225977851 0.952209447406 "yeah2.wav" 1.0 (the yeahX.wav corresponds to existing file names) and try to use it in the orchestra: S_source_file_name strget p7 asig diskin2 S_source_file_name, i_source_pitch I get errors like: B 0.000 .. 0.333 T 0.333 TT 0.333 M: 0 0 B 0.333 - note deleted. instr yeah5.wav undefined B 0.333 .. 1.154 T 1.154 TT 1.154 M: 0 0 B 1.154 - note deleted. instr yeah5.wav undefined Not what I expected. Csound version 5.12 (double samples) Feb 28 2010 The original orchestra and score are here: http://tobiah.org/d.orc http://tobiah.org/d.sco Thanks, Tobiah Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-12 07:01
From	Oeyvind Brandtsegg
Subject	[Csnd] Re: Trying to use string pfield as diskin2 name
	I think only one string is allowed in a score statement, and since you use a named instrument the string is used for that. And the second string overwrites the first, so Csound thinks you are calling instrument "yeahN". However strange this behaviour is, afaik it is a known issue. It should be possible to fix it when the new parser is in place. Oeyvind 2010/5/12 Tobiah : > I read about strget, but when I try to use a string parameter: > > i "source" 12.5735575797 20.0 13931.8888193 443.435999165 > 0.941055156517 "yeah2.wav" 1.0 > i "source" 17.8829973409 20.0 11811.3360861 266.403077568 0.5306028094 > "yeah8.wav" 1.0 > i "source" 8.14582259095 20.0 15854.7611801 768.225977851 > 0.952209447406 "yeah2.wav" 1.0 > > (the yeahX.wav corresponds to existing file names) and try to use it > in the orchestra: > > S_source_file_name strget p7 > asig diskin2 S_source_file_name, > i_source_pitch > > I get errors like: > > B 0.000 .. 0.333 T 0.333 TT 0.333 M: 0 0 > B 0.333 - note deleted. instr yeah5.wav undefined > B 0.333 .. 1.154 T 1.154 TT 1.154 M: 0 0 > B 1.154 - note deleted. instr yeah5.wav undefined > > Not what I expected. > > Csound version 5.12 (double samples) Feb 28 2010 > > The original orchestra and score are here: > > http://tobiah.org/d.orc > http://tobiah.org/d.sco > > Thanks, > > Tobiah > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-12 08:40
From	jpff@cs.bath.ac.uk
Subject	[Csnd] Re: Trying to use string pfield as diskin2 name
	One can only have 1 string in a score statement. I suppose one could consider working on this ==John ff > I read about strget, but when I try to use a string parameter: > > i "source" 12.5735575797 20.0 13931.8888193 443.435999165 > 0.941055156517 "yeah2.wav" 1.0 > i "source" 17.8829973409 20.0 11811.3360861 266.403077568 0.5306028094 > "yeah8.wav" 1.0 > i "source" 8.14582259095 20.0 15854.7611801 768.225977851 > 0.952209447406 "yeah2.wav" 1.0 > > (the yeahX.wav corresponds to existing file names) and try to use it > in the orchestra: > > S_source_file_name strget p7 > asig diskin2 S_source_file_name, > i_source_pitch > > I get errors like: > > B 0.000 .. 0.333 T 0.333 TT 0.333 M: 0 0 > B 0.333 - note deleted. instr yeah5.wav undefined > B 0.333 .. 1.154 T 1.154 TT 1.154 M: 0 0 > B 1.154 - note deleted. instr yeah5.wav undefined > > Not what I expected. > > Csound version 5.12 (double samples) Feb 28 2010 > > The original orchestra and score are here: > > http://tobiah.org/d.orc > http://tobiah.org/d.sco > > Thanks, > > Tobiah > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-12 08:46
From	jpff@cs.bath.ac.uk
Subject	[Csnd] Re: Re: Trying to use string pfield as diskin2 name
	> I think only one string is allowed in a score statement, and since you > use a named instrument the string is used for that. And the second > string overwrites the first, so Csound thinks you are calling > instrument "yeahN". > However strange this behaviour is, afaik it is a known issue. It > should be possible to fix it when the new parser is in place. > > Oeyvind > The new parser is an orchestra parser, and at prsent there are no plans for a new score parser -- except in my longerm plan. I was considering another hack like the one in opcodes that allowed up to 4 strings. ==John ff Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-12 09:03
From	Oeyvind Brandtsegg
Subject	[Csnd] Re: Re: Re: Trying to use string pfield as diskin2 name
	That would be very nice, 4 strings should be quite sufficient to solve most (currently known) limitations regarding strings in score statements. all best Oeyvind 2010/5/12 : >> I think only one string is allowed in a score statement, and since you >> use a named instrument the string is used for that. And the second >> string overwrites the first, so Csound thinks you are calling >> instrument "yeahN". >> However strange this behaviour is, afaik it is a known issue. It >> should be possible to fix it when the new parser is in place. >> >> Oeyvind >> > > The new parser is an orchestra parser, and at prsent there are no plans > for a new score parser -- except in my longerm plan. I was considering > another hack like the one in opcodes that allowed up to 4 strings. > > ==John ff > > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-13 15:46
From	ben hackbarth
Subject	[Csnd] Re: Re: Re: Re: Trying to use string pfield as diskin2 name
	hello. i would very much like to see csound support multiple strings per scoreline. i tend to write instruments with a lot of different processing options which can be toggled by the user according to certain pfields. i am currently using strset to deal with number-to-string conversions. at 60+ pfields per note, my scores become difficult to understand and quickly become "fossilized" (i.e., difficult to parse and edit). i believe additional strings could help make complex scores easier to metabolize. cheers and thanks, — ben -- http://crca.ucsd.edu/~ben/ On Wed, May 12, 2010 at 10:03 AM, Oeyvind Brandtsegg wrote: > That would be very nice, 4 strings should be quite sufficient to solve > most (currently known) limitations regarding strings in score > statements. > all best > Oeyvind > > 2010/5/12 : >>> I think only one string is allowed in a score statement, and since you >>> use a named instrument the string is used for that. And the second >>> string overwrites the first, so Csound thinks you are calling >>> instrument "yeahN". >>> However strange this behaviour is, afaik it is a known issue. It >>> should be possible to fix it when the new parser is in place. >>> >>> Oeyvind >>> >> >> The new parser is an orchestra parser, and at prsent there are no plans >> for a new score parser -- except in my longerm plan. I was considering >> another hack like the one in opcodes that allowed up to 4 strings. >> >> ==John ff >> >> >> >> Send bugs reports to the Sourceforge bug tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> 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 tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-17 02:45
From	Louis Cohen
Subject	[Csnd] Re: Trying to use string pfield as diskin2 name
	While I have successfully passed a p-field string to an instrument, I have NOT been able to do the same with an equivalent "event" opcode. Is this a known situation, and is the ability to pass strings in "event" opcodes likely to come to pass? -Lou On May 13, 2010, at 10:46 AM, ben hackbarth wrote: > hello. > > i would very much like to see csound support multiple strings per > scoreline. > > i tend to write instruments with a lot of different processing options > which can be toggled by the user according to certain pfields. i am > currently using strset to deal with number-to-string conversions. at > 60+ pfields per note, my scores become difficult to understand and > quickly become "fossilized" (i.e., difficult to parse and edit). i > believe additional strings could help make complex scores easier to > metabolize. > > cheers and thanks, > — ben > > -- > http://crca.ucsd.edu/~ben/ > > > > > On Wed, May 12, 2010 at 10:03 AM, Oeyvind Brandtsegg > wrote: >> That would be very nice, 4 strings should be quite sufficient to >> solve >> most (currently known) limitations regarding strings in score >> statements. >> all best >> Oeyvind >> >> 2010/5/12 : >>>> I think only one string is allowed in a score statement, and >>>> since you >>>> use a named instrument the string is used for that. And the second >>>> string overwrites the first, so Csound thinks you are calling >>>> instrument "yeahN". >>>> However strange this behaviour is, afaik it is a known issue. It >>>> should be possible to fix it when the new parser is in place. >>>> >>>> Oeyvind >>>> >>> >>> The new parser is an orchestra parser, and at prsent there are no >>> plans >>> for a new score parser -- except in my longerm plan. I was >>> considering >>> another hack like the one in opcodes that allowed up to 4 strings. >>> >>> ==John ff >>> >>> >>> >>> Send bugs reports to the Sourceforge bug tracker >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>> 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 tracker >> https://sourceforge.net/tracker/? >> group_id=81968&atid=564599 >> 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 tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-17 07:09
From	Victor Lazzarini
Subject	[Csnd] Re: Re: Trying to use string pfield as diskin2 name
	you can use scoreline opcode for that. Victor On 17 May 2010, at 02:45, Louis Cohen wrote: > While I have successfully passed a p-field string to an instrument, > I have NOT been able to do the same with an equivalent "event" opcode. > > Is this a known situation, and is the ability to pass strings in > "event" opcodes likely to come to pass? > > -Lou > > > On May 13, 2010, at 10:46 AM, ben hackbarth wrote: > >> hello. >> >> i would very much like to see csound support multiple strings per >> scoreline. >> >> i tend to write instruments with a lot of different processing >> options >> which can be toggled by the user according to certain pfields. i am >> currently using strset to deal with number-to-string conversions. at >> 60+ pfields per note, my scores become difficult to understand and >> quickly become "fossilized" (i.e., difficult to parse and edit). i >> believe additional strings could help make complex scores easier to >> metabolize. >> >> cheers and thanks, >> — ben >> >> -- >> http://crca.ucsd.edu/~ben/ >> >> >> >> >> On Wed, May 12, 2010 at 10:03 AM, Oeyvind Brandtsegg > > wrote: >>> That would be very nice, 4 strings should be quite sufficient to >>> solve >>> most (currently known) limitations regarding strings in score >>> statements. >>> all best >>> Oeyvind >>> >>> 2010/5/12 : >>>>> I think only one string is allowed in a score statement, and >>>>> since you >>>>> use a named instrument the string is used for that. And the second >>>>> string overwrites the first, so Csound thinks you are calling >>>>> instrument "yeahN". >>>>> However strange this behaviour is, afaik it is a known issue. It >>>>> should be possible to fix it when the new parser is in place. >>>>> >>>>> Oeyvind >>>>> >>>> >>>> The new parser is an orchestra parser, and at prsent there are no >>>> plans >>>> for a new score parser -- except in my longerm plan. I was >>>> considering >>>> another hack like the one in opcodes that allowed up to 4 strings. >>>> >>>> ==John ff >>>> >>>> >>>> >>>> Send bugs reports to the Sourceforge bug tracker >>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>>> 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 tracker >>> https://sourceforge.net/tracker/? >>> group_id=81968&atid=564599 >>> 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 tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> 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 tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-17 19:54
From	Louis Cohen
Subject	[Csnd] Re: Re: Re: Trying to use string pfield as diskin2 name
	Victor, Thanks for pointing out the "scoreline" opcode. I was not aware of it. "scoreline" seems equivalent in most ways to "event", although with an obviously different syntax (the required curly brackets.) Is there a reason why both opcodes exist? some distinction that I'm missing? (aside from one handling strings, the other not.) best, Lou Cohen On May 17, 2010, at 2:09 AM, Victor Lazzarini wrote: > you can use scoreline opcode for that. > > Victor > On 17 May 2010, at 02:45, Louis Cohen wrote: > >> While I have successfully passed a p-field string to an instrument, >> I have NOT been able to do the same with an equivalent "event" >> opcode. >> >> Is this a known situation, and is the ability to pass strings in >> "event" opcodes likely to come to pass? >> >> -Lou >> >> >> On May 13, 2010, at 10:46 AM, ben hackbarth wrote: >> >>> hello. >>> >>> i would very much like to see csound support multiple strings per >>> scoreline. >>> >>> i tend to write instruments with a lot of different processing >>> options >>> which can be toggled by the user according to certain pfields. i am >>> currently using strset to deal with number-to-string conversions. >>> at >>> 60+ pfields per note, my scores become difficult to understand and >>> quickly become "fossilized" (i.e., difficult to parse and edit). i >>> believe additional strings could help make complex scores easier to >>> metabolize. >>> >>> cheers and thanks, >>> — ben >>> >>> -- >>> http://crca.ucsd.edu/~ben/ >>> >>> >>> >>> >>> On Wed, May 12, 2010 at 10:03 AM, Oeyvind Brandtsegg >> > wrote: >>>> That would be very nice, 4 strings should be quite sufficient to >>>> solve >>>> most (currently known) limitations regarding strings in score >>>> statements. >>>> all best >>>> Oeyvind >>>> >>>> 2010/5/12 : >>>>>> I think only one string is allowed in a score statement, and >>>>>> since you >>>>>> use a named instrument the string is used for that. And the >>>>>> second >>>>>> string overwrites the first, so Csound thinks you are calling >>>>>> instrument "yeahN". >>>>>> However strange this behaviour is, afaik it is a known issue. It >>>>>> should be possible to fix it when the new parser is in place. >>>>>> >>>>>> Oeyvind >>>>>> >>>>> >>>>> The new parser is an orchestra parser, and at prsent there are >>>>> no plans >>>>> for a new score parser -- except in my longerm plan. I was >>>>> considering >>>>> another hack like the one in opcodes that allowed up to 4 strings. >>>>> >>>>> ==John ff >>>>> >>>>> >>>>> >>>>> Send bugs reports to the Sourceforge bug tracker >>>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>>>> 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 tracker >>>> https://sourceforge.net/tracker/? >>>> group_id=81968&atid=564599 >>>> 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 tracker >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>> 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 tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> 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 tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2010-05-17 20:05
From	Victor Lazzarini
Subject	[Csnd] Re: Re: Re: Re: Trying to use string pfield as diskin2 name
	Not much; scoreline takes a string instead of separate p-fields. The string can contain any number of score events. So it's like placing the score literally inside an instrument. Note that the braces define a string that can be multi-line. The example in the manual uses it as a convenient means of transcribing a full score into an instrument. Note that, while event has been there for a long time, scoreline is newer as it uses some Csound5 internals that were not there before. Victor On 17 May 2010, at 19:54, Louis Cohen wrote: > Victor, > > Thanks for pointing out the "scoreline" opcode. I was not aware of it. > > "scoreline" seems equivalent in most ways to "event", although with > an obviously different syntax (the required curly brackets.) > > Is there a reason why both opcodes exist? some distinction that I'm > missing? (aside from one handling strings, the other not.) > > best, > Lou Cohen > > > On May 17, 2010, at 2:09 AM, Victor Lazzarini wrote: > >> you can use scoreline opcode for that. >> >> Victor >> On 17 May 2010, at 02:45, Louis Cohen wrote: >> >>> While I have successfully passed a p-field string to an >>> instrument, I have NOT been able to do the same with an equivalent >>> "event" opcode. >>> >>> Is this a known situation, and is the ability to pass strings in >>> "event" opcodes likely to come to pass? >>> >>> -Lou >>> >>> >>> On May 13, 2010, at 10:46 AM, ben hackbarth wrote: >>> >>>> hello. >>>> >>>> i would very much like to see csound support multiple strings per >>>> scoreline. >>>> >>>> i tend to write instruments with a lot of different processing >>>> options >>>> which can be toggled by the user according to certain pfields. i >>>> am >>>> currently using strset to deal with number-to-string >>>> conversions. at >>>> 60+ pfields per note, my scores become difficult to understand and >>>> quickly become "fossilized" (i.e., difficult to parse and edit). i >>>> believe additional strings could help make complex scores easier to >>>> metabolize. >>>> >>>> cheers and thanks, >>>> — ben >>>> >>>> -- >>>> http://crca.ucsd.edu/~ben/ >>>> >>>> >>>> >>>> >>>> On Wed, May 12, 2010 at 10:03 AM, Oeyvind Brandtsegg >>> > wrote: >>>>> That would be very nice, 4 strings should be quite sufficient to >>>>> solve >>>>> most (currently known) limitations regarding strings in score >>>>> statements. >>>>> all best >>>>> Oeyvind >>>>> >>>>> 2010/5/12 : >>>>>>> I think only one string is allowed in a score statement, and >>>>>>> since you >>>>>>> use a named instrument the string is used for that. And the >>>>>>> second >>>>>>> string overwrites the first, so Csound thinks you are calling >>>>>>> instrument "yeahN". >>>>>>> However strange this behaviour is, afaik it is a known issue. It >>>>>>> should be possible to fix it when the new parser is in place. >>>>>>> >>>>>>> Oeyvind >>>>>>> >>>>>> >>>>>> The new parser is an orchestra parser, and at prsent there are >>>>>> no plans >>>>>> for a new score parser -- except in my longerm plan. I was >>>>>> considering >>>>>> another hack like the one in opcodes that allowed up to 4 >>>>>> strings. >>>>>> >>>>>> ==John ff >>>>>> >>>>>> >>>>>> >>>>>> Send bugs reports to the Sourceforge bug tracker >>>>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>>>>> 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 tracker >>>>> https://sourceforge.net/tracker/? >>>>> group_id=81968&atid=564599 >>>>> 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 tracker >>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>>> 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 tracker >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>> 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 tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> 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 tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > 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 tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"