Question about changed opcode

Question about changed opcode

Date	2016-01-01 13:40
From	jpff
Subject	Question about changed opcode
	Seeking advice on this. The changed opcode reports if any of a number of kvars have changed from the previous cycle. It remembers that last values for comparison. But that value is initialised to zero, with the consequence that kk = 0 kt changed kk printk 0, kt and kk = 1 kt changed kk printk 0, kt differ as the first cycle does not/does report a change. Is this acceptable? Three offers 1: do nowt 2: initialise to random values so usually first cycle changes 3: treat first k-cycle differently so first cycle does not change. Any thoughts? Or will this break things? Current state is hard to explain though. ==John ffitch Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-01 13:54
From	Rory Walsh
Subject	Re: Question about changed opcode
	That does seem odd. I would prefer to see option 3 in place, but I'm not sure we can change this without breaking people's instruments. The current state doesn't make much sense. Anyone for a changed2 opcode?! On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: Seeking advice on this. The changed opcode reports if any of a number of kvars have changed from the previous cycle. It remembers that last values for comparison. But that value is initialised to zero, with the consequence that kk = 0 kt changed kk printk 0, kt and kk = 1 kt changed kk printk 0, kt differ as the first cycle does not/does report a change. Is this acceptable? Three offers 1: do nowt 2: initialise to random values so usually first cycle changes 3: treat first k-cycle differently so first cycle does not change. Any thoughts? Or will this break things? Current state is hard to explain though. ==John ffitch Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-01 17:34
From	jpff
Subject	Re: Question about changed opcode
	In the array case (new code) I have implemented case 3 and will so document. In the kvar case the documentation is silent on this issue; I really want to change it, but I guess changed2 is needed. Hey Ho! On Fri, 1 Jan 2016, Rory Walsh wrote: > That does seem odd. I would prefer to see option 3 in place, but I'm not sure > we can change this without breaking people's instruments. The current state > doesn't make much sense. Anyone for a changed2 opcode?! > > On 1 January 2016 at 13:40, jpff wrote: > Seeking advice on this. > > The changed opcode reports if any of a number of kvars have > changed > from the previous cycle. It remembers that last values for > comparison. But that value is initialised to zero, with the > consequence that > kk = 0 > kt changed kk > printk 0, kt > and > kk = 1 > kt changed kk > printk 0, kt > differ as the first cycle does not/does report a change. > > Is this acceptable? Three offers > 1: do nowt > 2: initialise to random values so usually first cycle changes > 3: treat first k-cycle differently so first cycle does not change. > > Any thoughts? Or will this break things? Current state is hard > to > explain though. > > ==John ffitch > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-01 17:57
From	joachim heintz
Subject	Re: Question about changed opcode
	i agree with both of you that case 3 is logical, but also, that implementing it in changed might very likely break old code (including my own ... =). (because of the discussion now, i understand the behaviour of changed which i simple accepted and used without knowing why it worked in this way.) so i also vote for changed2. joachim On 01/01/16 18:34, jpff wrote: > In the array case (new code) I have implemented case 3 and will so > document. In the kvar case the documentation is silent on this issue; I > really want to change it, but I guess changed2 is needed. Hey Ho! > > > On Fri, 1 Jan 2016, Rory Walsh wrote: > >> That does seem odd. I would prefer to see option 3 in place, but I'm >> not sure >> we can change this without breaking people's instruments. The current >> state >> doesn't make much sense. Anyone for a changed2 opcode?! >> >> On 1 January 2016 at 13:40, jpff wrote: >> Seeking advice on this. >> >> The changed opcode reports if any of a number of kvars have >> changed >> from the previous cycle. It remembers that last values for >> comparison. But that value is initialised to zero, with the >> consequence that >> kk = 0 >> kt changed kk >> printk 0, kt >> and >> kk = 1 >> kt changed kk >> printk 0, kt >> differ as the first cycle does not/does report a change. >> >> Is this acceptable? Three offers >> 1: do nowt >> 2: initialise to random values so usually first cycle changes >> 3: treat first k-cycle differently so first cycle does not change. >> >> Any thoughts? Or will this break things? Current state is hard >> to >> explain though. >> >> ==John ffitch >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> >> >> Csound mailing list Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> https://github.com/csound/csound/issues Discussions of bugs and >> features can >> be posted here >> > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-01 18:10
From	jpff
Subject	Re: Question about changed opcode
	OKl I have wriyten changed2 which also can take an array. changed is unchanged(!) except marked as deprecated. Documentation to follow ==John ff On Fri, 1 Jan 2016, joachim heintz wrote: > i agree with both of you that case 3 is logical, but also, that implementing > it in changed might very likely break old code (including my own ... =). > (because of the discussion now, i understand the behaviour of changed which i > simple accepted and used without knowing why it worked in this way.) > > so i also vote for changed2. > > joachim > > > On 01/01/16 18:34, jpff wrote: >> In the array case (new code) I have implemented case 3 and will so >> document. In the kvar case the documentation is silent on this issue; I >> really want to change it, but I guess changed2 is needed. Hey Ho! >> >> >> On Fri, 1 Jan 2016, Rory Walsh wrote: >> >>> That does seem odd. I would prefer to see option 3 in place, but I'm >>> not sure >>> we can change this without breaking people's instruments. The current >>> state >>> doesn't make much sense. Anyone for a changed2 opcode?! >>> >>> On 1 January 2016 at 13:40, jpff wrote: >>> Seeking advice on this. >>> >>> The changed opcode reports if any of a number of kvars have >>> changed >>> from the previous cycle. It remembers that last values for >>> comparison. But that value is initialised to zero, with the >>> consequence that >>> kk = 0 >>> kt changed kk >>> printk 0, kt >>> and >>> kk = 1 >>> kt changed kk >>> printk 0, kt >>> differ as the first cycle does not/does report a change. >>> >>> Is this acceptable? Three offers >>> 1: do nowt >>> 2: initialise to random values so usually first cycle changes >>> 3: treat first k-cycle differently so first cycle does not change. >>> >>> Any thoughts? Or will this break things? Current state is hard >>> to >>> explain though. >>> >>> ==John ffitch >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-01 19:19
From	Iain McCurdy
Subject	Re: Question about changed opcode
	I agree that the initial trigger is unlikely to be useful. I sometimes include an if...then... to ignore the trigger on the first k-cycle if it causes something unwanted. I would agree to option 3 but this is changing the behaviour although changed2 feels like an extravagance. Date: Fri, 1 Jan 2016 13:54:31 +0000 From: rorywalsh@EAR.IE Subject: Re: [Csnd] Question about changed opcode To: CSOUND@LISTSERV.HEANET.IE That does seem odd. I would prefer to see option 3 in place, but I'm not sure we can change this without breaking people's instruments. The current state doesn't make much sense. Anyone for a changed2 opcode?! On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: Seeking advice on this. The changed opcode reports if any of a number of kvars have changed from the previous cycle. It remembers that last values for comparison. But that value is initialised to zero, with the consequence that kk = 0 kt changed kk printk 0, kt and kk = 1 kt changed kk printk 0, kt differ as the first cycle does not/does report a change. Is this acceptable? Three offers 1: do nowt 2: initialise to random values so usually first cycle changes 3: treat first k-cycle differently so first cycle does not change. Any thoughts? Or will this break things? Current state is hard to explain though. ==John ffitch Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-03 20:24
From	Oeyvind Brandtsegg
Subject	Re: Question about changed opcode
	Is it an option to add an optinonal argument to changed? The optional arg would set it to the new behaviour, but it will still work like it used to do if the argument is not present. Still not too pretty, but perhaps better than changed2? 2016-01-01 20:19 GMT+01:00 Iain McCurdy : > I agree that the initial trigger is unlikely to be useful. I sometimes > include an if...then... to ignore the trigger on the first k-cycle if it > causes something unwanted. I would agree to option 3 but this is changing > the behaviour although changed2 feels like an extravagance. > > ________________________________ > Date: Fri, 1 Jan 2016 13:54:31 +0000 > From: rorywalsh@EAR.IE > Subject: Re: [Csnd] Question about changed opcode > To: CSOUND@LISTSERV.HEANET.IE > > > That does seem odd. I would prefer to see option 3 in place, but I'm not > sure we can change this without breaking people's instruments. The current > state doesn't make much sense. Anyone for a changed2 opcode?! > > On 1 January 2016 at 13:40, jpff wrote: > > Seeking advice on this. > > The changed opcode reports if any of a number of kvars have changed > from the previous cycle. It remembers that last values for > comparison. But that value is initialised to zero, with the > consequence that > kk = 0 > kt changed kk > printk 0, kt > and > kk = 1 > kt changed kk > printk 0, kt > differ as the first cycle does not/does report a change. > > Is this acceptable? Three offers > 1: do nowt > 2: initialise to random values so usually first cycle changes > 3: treat first k-cycle differently so first cycle does not change. > > Any thoughts? Or will this break things? Current state is hard to > explain though. > > ==John ffitch > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here

Date	2016-01-03 20:33
From	Rory Walsh
Subject	Re: Question about changed opcode
	The fact that changed takes any number of input arguments might make this option a little messy? On 3 January 2016 at 20:24, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Is it an option to add an optinonal argument to changed? The optional arg would set it to the new behaviour, but it will still work like it used to do if the argument is not present. Still not too pretty, but perhaps better than changed2? 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: > I agree that the initial trigger is unlikely to be useful. I sometimes > include an if...then... to ignore the trigger on the first k-cycle if it > causes something unwanted. I would agree to option 3 but this is changing > the behaviour although changed2 feels like an extravagance. > > ________________________________ > Date: Fri, 1 Jan 2016 13:54:31 +0000 > From: rorywalsh@EAR.IE > Subject: Re: [Csnd] Question about changed opcode > To: CSOUND@LISTSERV.HEANET.IE > > > That does seem odd. I would prefer to see option 3 in place, but I'm not > sure we can change this without breaking people's instruments. The current > state doesn't make much sense. Anyone for a changed2 opcode?! > > On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: > > Seeking advice on this. > > The changed opcode reports if any of a number of kvars have changed > from the previous cycle. It remembers that last values for > comparison. But that value is initialised to zero, with the > consequence that > kk = 0 > kt changed kk > printk 0, kt > and > kk = 1 > kt changed kk > printk 0, kt > differ as the first cycle does not/does report a change. > > Is this acceptable? Three offers > 1: do nowt > 2: initialise to random values so usually first cycle changes > 3: treat first k-cycle differently so first cycle does not change. > > Any thoughts? Or will this break things? Current state is hard to > explain though. > > ==John ffitch > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-03 20:50
From	Oeyvind Brandtsegg
Subject	Re: Question about changed opcode
	o my..., sorry ...(Beer count +1) 2016-01-03 21:33 GMT+01:00 Rory Walsh : > The fact that changed takes any number of input arguments might make this > option a little messy? > > On 3 January 2016 at 20:24, Oeyvind Brandtsegg > wrote: >> >> Is it an option to add an optinonal argument to changed? >> The optional arg would set it to the new behaviour, but it will still >> work like it used to do if the argument is not present. >> Still not too pretty, but perhaps better than changed2? >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >> > I agree that the initial trigger is unlikely to be useful. I sometimes >> > include an if...then... to ignore the trigger on the first k-cycle if it >> > causes something unwanted. I would agree to option 3 but this is >> > changing >> > the behaviour although changed2 feels like an extravagance. >> > >> > ________________________________ >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> > From: rorywalsh@EAR.IE >> > Subject: Re: [Csnd] Question about changed opcode >> > To: CSOUND@LISTSERV.HEANET.IE >> > >> > >> > That does seem odd. I would prefer to see option 3 in place, but I'm not >> > sure we can change this without breaking people's instruments. The >> > current >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> > >> > On 1 January 2016 at 13:40, jpff wrote: >> > >> > Seeking advice on this. >> > >> > The changed opcode reports if any of a number of kvars have changed >> > from the previous cycle. It remembers that last values for >> > comparison. But that value is initialised to zero, with the >> > consequence that >> > kk = 0 >> > kt changed kk >> > printk 0, kt >> > and >> > kk = 1 >> > kt changed kk >> > printk 0, kt >> > differ as the first cycle does not/does report a change. >> > >> > Is this acceptable? Three offers >> > 1: do nowt >> > 2: initialise to random values so usually first cycle changes >> > 3: treat first k-cycle differently so first cycle does not change. >> > >> > Any thoughts? Or will this break things? Current state is hard to >> > explain though. >> > >> > ==John ffitch >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here

Date	2016-01-03 20:54
From	Rory Walsh
Subject	Re: Question about changed opcode
	We're going to have to have a get together soon so we can buy all these beers! On 3 January 2016 at 20:50, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: o my..., sorry ...(Beer count +1) 2016-01-03 21:33 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: > The fact that changed takes any number of input arguments might make this > option a little messy? > > On 3 January 2016 at 20:24, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> > wrote: >> >> Is it an option to add an optinonal argument to changed? >> The optional arg would set it to the new behaviour, but it will still >> work like it used to do if the argument is not present. >> Still not too pretty, but perhaps better than changed2? >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: >> > I agree that the initial trigger is unlikely to be useful. I sometimes >> > include an if...then... to ignore the trigger on the first k-cycle if it >> > causes something unwanted. I would agree to option 3 but this is >> > changing >> > the behaviour although changed2 feels like an extravagance. >> > >> > ________________________________ >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> > From: rorywalsh@EAR.IE >> > Subject: Re: [Csnd] Question about changed opcode >> > To: CSOUND@LISTSERV.HEANET.IE >> > >> > >> > That does seem odd. I would prefer to see option 3 in place, but I'm not >> > sure we can change this without breaking people's instruments. The >> > current >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> > >> > On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: >> > >> > Seeking advice on this. >> > >> > The changed opcode reports if any of a number of kvars have changed >> > from the previous cycle. It remembers that last values for >> > comparison. But that value is initialised to zero, with the >> > consequence that >> > kk = 0 >> > kt changed kk >> > printk 0, kt >> > and >> > kk = 1 >> > kt changed kk >> > printk 0, kt >> > differ as the first cycle does not/does report a change. >> > >> > Is this acceptable? Three offers >> > 1: do nowt >> > 2: initialise to random values so usually first cycle changes >> > 3: treat first k-cycle differently so first cycle does not change. >> > >> > Any thoughts? Or will this break things? Current state is hard to >> > explain though. >> > >> > ==John ffitch >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-03 21:00
From	Oeyvind Brandtsegg
Subject	Re: Question about changed opcode
	Csound at 30, counting 1986-2016, would be an occation? 2016-01-03 21:54 GMT+01:00 Rory Walsh : > We're going to have to have a get together soon so we can buy all these > beers! > > On 3 January 2016 at 20:50, Oeyvind Brandtsegg > wrote: >> >> o my..., sorry >> ...(Beer count +1) >> >> 2016-01-03 21:33 GMT+01:00 Rory Walsh : >> > The fact that changed takes any number of input arguments might make >> > this >> > option a little messy? >> > >> > On 3 January 2016 at 20:24, Oeyvind Brandtsegg >> > >> > wrote: >> >> >> >> Is it an option to add an optinonal argument to changed? >> >> The optional arg would set it to the new behaviour, but it will still >> >> work like it used to do if the argument is not present. >> >> Still not too pretty, but perhaps better than changed2? >> >> >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >> >> > I agree that the initial trigger is unlikely to be useful. I >> >> > sometimes >> >> > include an if...then... to ignore the trigger on the first k-cycle if >> >> > it >> >> > causes something unwanted. I would agree to option 3 but this is >> >> > changing >> >> > the behaviour although changed2 feels like an extravagance. >> >> > >> >> > ________________________________ >> >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> >> > From: rorywalsh@EAR.IE >> >> > Subject: Re: [Csnd] Question about changed opcode >> >> > To: CSOUND@LISTSERV.HEANET.IE >> >> > >> >> > >> >> > That does seem odd. I would prefer to see option 3 in place, but I'm >> >> > not >> >> > sure we can change this without breaking people's instruments. The >> >> > current >> >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> >> > >> >> > On 1 January 2016 at 13:40, jpff wrote: >> >> > >> >> > Seeking advice on this. >> >> > >> >> > The changed opcode reports if any of a number of kvars have changed >> >> > from the previous cycle. It remembers that last values for >> >> > comparison. But that value is initialised to zero, with the >> >> > consequence that >> >> > kk = 0 >> >> > kt changed kk >> >> > printk 0, kt >> >> > and >> >> > kk = 1 >> >> > kt changed kk >> >> > printk 0, kt >> >> > differ as the first cycle does not/does report a change. >> >> > >> >> > Is this acceptable? Three offers >> >> > 1: do nowt >> >> > 2: initialise to random values so usually first cycle changes >> >> > 3: treat first k-cycle differently so first cycle does not change. >> >> > >> >> > Any thoughts? Or will this break things? Current state is hard to >> >> > explain though. >> >> > >> >> > ==John ffitch >> >> > >> >> > Csound mailing list >> >> > Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> > Send bugs reports to >> >> > https://github.com/csound/csound/issues >> >> > Discussions of bugs and features can be posted here >> >> > >> >> > >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> >> >> >> >> >> >> -- >> >> >> >> Oeyvind Brandtsegg >> >> Professor of Music Technology >> >> NTNU >> >> 7491 Trondheim >> >> Norway >> >> Cell: +47 92 203 205 >> >> >> >> http://www.partikkelaudio.com/ >> >> http://soundcloud.com/brandtsegg >> >> http://flyndresang.no/ >> >> http://soundcloud.com/t-emp >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here

Date	2016-01-03 21:07
From	Rory Walsh
Subject	Re: Question about changed opcode
	Every birthday is a reason to celebrate! On 3 January 2016 at 21:00, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Csound at 30, counting 1986-2016, would be an occation? 2016-01-03 21:54 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: > We're going to have to have a get together soon so we can buy all these > beers! > > On 3 January 2016 at 20:50, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> > wrote: >> >> o my..., sorry >> ...(Beer count +1) >> >> 2016-01-03 21:33 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >> > The fact that changed takes any number of input arguments might make >> > this >> > option a little messy? >> > >> > On 3 January 2016 at 20:24, Oeyvind Brandtsegg >> > <oyvind.brandtsegg@ntnu.no> >> > wrote: >> >> >> >> Is it an option to add an optinonal argument to changed? >> >> The optional arg would set it to the new behaviour, but it will still >> >> work like it used to do if the argument is not present. >> >> Still not too pretty, but perhaps better than changed2? >> >> >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: >> >> > I agree that the initial trigger is unlikely to be useful. I >> >> > sometimes >> >> > include an if...then... to ignore the trigger on the first k-cycle if >> >> > it >> >> > causes something unwanted. I would agree to option 3 but this is >> >> > changing >> >> > the behaviour although changed2 feels like an extravagance. >> >> > >> >> > ________________________________ >> >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> >> > From: rorywalsh@EAR.IE >> >> > Subject: Re: [Csnd] Question about changed opcode >> >> > To: CSOUND@LISTSERV.HEANET.IE >> >> > >> >> > >> >> > That does seem odd. I would prefer to see option 3 in place, but I'm >> >> > not >> >> > sure we can change this without breaking people's instruments. The >> >> > current >> >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> >> > >> >> > On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: >> >> > >> >> > Seeking advice on this. >> >> > >> >> > The changed opcode reports if any of a number of kvars have changed >> >> > from the previous cycle. It remembers that last values for >> >> > comparison. But that value is initialised to zero, with the >> >> > consequence that >> >> > kk = 0 >> >> > kt changed kk >> >> > printk 0, kt >> >> > and >> >> > kk = 1 >> >> > kt changed kk >> >> > printk 0, kt >> >> > differ as the first cycle does not/does report a change. >> >> > >> >> > Is this acceptable? Three offers >> >> > 1: do nowt >> >> > 2: initialise to random values so usually first cycle changes >> >> > 3: treat first k-cycle differently so first cycle does not change. >> >> > >> >> > Any thoughts? Or will this break things? Current state is hard to >> >> > explain though. >> >> > >> >> > ==John ffitch >> >> > >> >> > Csound mailing list >> >> > Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> > Send bugs reports to >> >> > https://github.com/csound/csound/issues >> >> > Discussions of bugs and features can be posted here >> >> > >> >> > >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> >> >> >> >> >> >> -- >> >> >> >> Oeyvind Brandtsegg >> >> Professor of Music Technology >> >> NTNU >> >> 7491 Trondheim >> >> Norway >> >> Cell: +47 92 203 205 >> >> >> >> http://www.partikkelaudio.com/ >> >> http://soundcloud.com/brandtsegg >> >> http://flyndresang.no/ >> >> http://soundcloud.com/t-emp >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-03 21:23
From	Oeyvind Brandtsegg
Subject	Re: Question about changed opcode
	IIRC, There was some talk about gathering in Berlin sometime in June? 2016-01-03 22:07 GMT+01:00 Rory Walsh : > Every birthday is a reason to celebrate! > > On 3 January 2016 at 21:00, Oeyvind Brandtsegg > wrote: >> >> Csound at 30, counting 1986-2016, >> would be an occation? >> >> 2016-01-03 21:54 GMT+01:00 Rory Walsh : >> > We're going to have to have a get together soon so we can buy all these >> > beers! >> > >> > On 3 January 2016 at 20:50, Oeyvind Brandtsegg >> > >> > wrote: >> >> >> >> o my..., sorry >> >> ...(Beer count +1) >> >> >> >> 2016-01-03 21:33 GMT+01:00 Rory Walsh : >> >> > The fact that changed takes any number of input arguments might make >> >> > this >> >> > option a little messy? >> >> > >> >> > On 3 January 2016 at 20:24, Oeyvind Brandtsegg >> >> > >> >> > wrote: >> >> >> >> >> >> Is it an option to add an optinonal argument to changed? >> >> >> The optional arg would set it to the new behaviour, but it will >> >> >> still >> >> >> work like it used to do if the argument is not present. >> >> >> Still not too pretty, but perhaps better than changed2? >> >> >> >> >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >> >> >> > I agree that the initial trigger is unlikely to be useful. I >> >> >> > sometimes >> >> >> > include an if...then... to ignore the trigger on the first k-cycle >> >> >> > if >> >> >> > it >> >> >> > causes something unwanted. I would agree to option 3 but this is >> >> >> > changing >> >> >> > the behaviour although changed2 feels like an extravagance. >> >> >> > >> >> >> > ________________________________ >> >> >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> >> >> > From: rorywalsh@EAR.IE >> >> >> > Subject: Re: [Csnd] Question about changed opcode >> >> >> > To: CSOUND@LISTSERV.HEANET.IE >> >> >> > >> >> >> > >> >> >> > That does seem odd. I would prefer to see option 3 in place, but >> >> >> > I'm >> >> >> > not >> >> >> > sure we can change this without breaking people's instruments. The >> >> >> > current >> >> >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> >> >> > >> >> >> > On 1 January 2016 at 13:40, jpff wrote: >> >> >> > >> >> >> > Seeking advice on this. >> >> >> > >> >> >> > The changed opcode reports if any of a number of kvars have >> >> >> > changed >> >> >> > from the previous cycle. It remembers that last values for >> >> >> > comparison. But that value is initialised to zero, with the >> >> >> > consequence that >> >> >> > kk = 0 >> >> >> > kt changed kk >> >> >> > printk 0, kt >> >> >> > and >> >> >> > kk = 1 >> >> >> > kt changed kk >> >> >> > printk 0, kt >> >> >> > differ as the first cycle does not/does report a change. >> >> >> > >> >> >> > Is this acceptable? Three offers >> >> >> > 1: do nowt >> >> >> > 2: initialise to random values so usually first cycle changes >> >> >> > 3: treat first k-cycle differently so first cycle does not change. >> >> >> > >> >> >> > Any thoughts? Or will this break things? Current state is hard >> >> >> > to >> >> >> > explain though. >> >> >> > >> >> >> > ==John ffitch >> >> >> > >> >> >> > Csound mailing list >> >> >> > Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> > Send bugs reports to >> >> >> > https://github.com/csound/csound/issues >> >> >> > Discussions of bugs and features can be posted here >> >> >> > >> >> >> > >> >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >> >> >> > to >> >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> >> > features >> >> >> > can >> >> >> > be posted here >> >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >> >> >> > to >> >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> >> > features >> >> >> > can >> >> >> > be posted here >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Oeyvind Brandtsegg >> >> >> Professor of Music Technology >> >> >> NTNU >> >> >> 7491 Trondheim >> >> >> Norway >> >> >> Cell: +47 92 203 205 >> >> >> >> >> >> http://www.partikkelaudio.com/ >> >> >> http://soundcloud.com/brandtsegg >> >> >> http://flyndresang.no/ >> >> >> http://soundcloud.com/t-emp >> >> >> >> >> >> Csound mailing list >> >> >> Csound@listserv.heanet.ie >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> Send bugs reports to >> >> >> https://github.com/csound/csound/issues >> >> >> Discussions of bugs and features can be posted here >> >> > >> >> > >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> >> >> >> >> >> >> -- >> >> >> >> Oeyvind Brandtsegg >> >> Professor of Music Technology >> >> NTNU >> >> 7491 Trondheim >> >> Norway >> >> Cell: +47 92 203 205 >> >> >> >> http://www.partikkelaudio.com/ >> >> http://soundcloud.com/brandtsegg >> >> http://flyndresang.no/ >> >> http://soundcloud.com/t-emp >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here

Date	2016-01-03 21:26
From	Rory Walsh
Subject	Re: Question about changed opcode
	That's right. But a few of us we were also planning something in Dublin in the new year. On 3 January 2016 at 21:23, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: IIRC, There was some talk about gathering in Berlin sometime in June? 2016-01-03 22:07 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: > Every birthday is a reason to celebrate! > > On 3 January 2016 at 21:00, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> > wrote: >> >> Csound at 30, counting 1986-2016, >> would be an occation? >> >> 2016-01-03 21:54 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >> > We're going to have to have a get together soon so we can buy all these >> > beers! >> > >> > On 3 January 2016 at 20:50, Oeyvind Brandtsegg >> > <oyvind.brandtsegg@ntnu.no> >> > wrote: >> >> >> >> o my..., sorry >> >> ...(Beer count +1) >> >> >> >> 2016-01-03 21:33 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >> >> > The fact that changed takes any number of input arguments might make >> >> > this >> >> > option a little messy? >> >> > >> >> > On 3 January 2016 at 20:24, Oeyvind Brandtsegg >> >> > <oyvind.brandtsegg@ntnu.no> >> >> > wrote: >> >> >> >> >> >> Is it an option to add an optinonal argument to changed? >> >> >> The optional arg would set it to the new behaviour, but it will >> >> >> still >> >> >> work like it used to do if the argument is not present. >> >> >> Still not too pretty, but perhaps better than changed2? >> >> >> >> >> >> 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: >> >> >> > I agree that the initial trigger is unlikely to be useful. I >> >> >> > sometimes >> >> >> > include an if...then... to ignore the trigger on the first k-cycle >> >> >> > if >> >> >> > it >> >> >> > causes something unwanted. I would agree to option 3 but this is >> >> >> > changing >> >> >> > the behaviour although changed2 feels like an extravagance. >> >> >> > >> >> >> > ________________________________ >> >> >> > Date: Fri, 1 Jan 2016 13:54:31 +0000 >> >> >> > From: rorywalsh@EAR.IE >> >> >> > Subject: Re: [Csnd] Question about changed opcode >> >> >> > To: CSOUND@LISTSERV.HEANET.IE >> >> >> > >> >> >> > >> >> >> > That does seem odd. I would prefer to see option 3 in place, but >> >> >> > I'm >> >> >> > not >> >> >> > sure we can change this without breaking people's instruments. The >> >> >> > current >> >> >> > state doesn't make much sense. Anyone for a changed2 opcode?! >> >> >> > >> >> >> > On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: >> >> >> > >> >> >> > Seeking advice on this. >> >> >> > >> >> >> > The changed opcode reports if any of a number of kvars have >> >> >> > changed >> >> >> > from the previous cycle. It remembers that last values for >> >> >> > comparison. But that value is initialised to zero, with the >> >> >> > consequence that >> >> >> > kk = 0 >> >> >> > kt changed kk >> >> >> > printk 0, kt >> >> >> > and >> >> >> > kk = 1 >> >> >> > kt changed kk >> >> >> > printk 0, kt >> >> >> > differ as the first cycle does not/does report a change. >> >> >> > >> >> >> > Is this acceptable? Three offers >> >> >> > 1: do nowt >> >> >> > 2: initialise to random values so usually first cycle changes >> >> >> > 3: treat first k-cycle differently so first cycle does not change. >> >> >> > >> >> >> > Any thoughts? Or will this break things? Current state is hard >> >> >> > to >> >> >> > explain though. >> >> >> > >> >> >> > ==John ffitch >> >> >> > >> >> >> > Csound mailing list >> >> >> > Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> > Send bugs reports to >> >> >> > https://github.com/csound/csound/issues >> >> >> > Discussions of bugs and features can be posted here >> >> >> > >> >> >> > >> >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >> >> >> > to >> >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> >> > features >> >> >> > can >> >> >> > be posted here >> >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >> >> >> > to >> >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> >> > features >> >> >> > can >> >> >> > be posted here >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Oeyvind Brandtsegg >> >> >> Professor of Music Technology >> >> >> NTNU >> >> >> 7491 Trondheim >> >> >> Norway >> >> >> Cell: +47 92 203 205 >> >> >> >> >> >> http://www.partikkelaudio.com/ >> >> >> http://soundcloud.com/brandtsegg >> >> >> http://flyndresang.no/ >> >> >> http://soundcloud.com/t-emp >> >> >> >> >> >> Csound mailing list >> >> >> Csound@listserv.heanet.ie >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> Send bugs reports to >> >> >> https://github.com/csound/csound/issues >> >> >> Discussions of bugs and features can be posted here >> >> > >> >> > >> >> > Csound mailing list Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >> > https://github.com/csound/csound/issues Discussions of bugs and >> >> > features >> >> > can >> >> > be posted here >> >> >> >> >> >> >> >> -- >> >> >> >> Oeyvind Brandtsegg >> >> Professor of Music Technology >> >> NTNU >> >> 7491 Trondheim >> >> Norway >> >> Cell: +47 92 203 205 >> >> >> >> http://www.partikkelaudio.com/ >> >> http://soundcloud.com/brandtsegg >> >> http://flyndresang.no/ >> >> http://soundcloud.com/t-emp >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > >> > Csound mailing list Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> > https://github.com/csound/csound/issues Discussions of bugs and features >> > can >> > be posted here >> >> >> >> -- >> >> Oeyvind Brandtsegg >> Professor of Music Technology >> NTNU >> 7491 Trondheim >> Norway >> Cell: +47 92 203 205 >> >> http://www.partikkelaudio.com/ >> http://soundcloud.com/brandtsegg >> http://flyndresang.no/ >> http://soundcloud.com/t-emp >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-04 21:39
From	joachim heintz
Subject	Re: Question about changed opcode
	yes, but as my personal secret service tells me, iain will leave to maynooth — good for maynooth, bad for berlin, and bad, too, for a poor german friend living in hannover ... so, maybe dublin ... i have heard there is beer, too ... j On 03/01/16 22:23, Oeyvind Brandtsegg wrote: > IIRC, There was some talk about gathering in Berlin sometime in June? > > 2016-01-03 22:07 GMT+01:00 Rory Walsh : >> Every birthday is a reason to celebrate! >> >> On 3 January 2016 at 21:00, Oeyvind Brandtsegg >> wrote: >>> >>> Csound at 30, counting 1986-2016, >>> would be an occation? >>> >>> 2016-01-03 21:54 GMT+01:00 Rory Walsh : >>>> We're going to have to have a get together soon so we can buy all these >>>> beers! >>>> >>>> On 3 January 2016 at 20:50, Oeyvind Brandtsegg >>>> >>>> wrote: >>>>> >>>>> o my..., sorry >>>>> ...(Beer count +1) >>>>> >>>>> 2016-01-03 21:33 GMT+01:00 Rory Walsh : >>>>>> The fact that changed takes any number of input arguments might make >>>>>> this >>>>>> option a little messy? >>>>>> >>>>>> On 3 January 2016 at 20:24, Oeyvind Brandtsegg >>>>>> >>>>>> wrote: >>>>>>> >>>>>>> Is it an option to add an optinonal argument to changed? >>>>>>> The optional arg would set it to the new behaviour, but it will >>>>>>> still >>>>>>> work like it used to do if the argument is not present. >>>>>>> Still not too pretty, but perhaps better than changed2? >>>>>>> >>>>>>> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >>>>>>>> I agree that the initial trigger is unlikely to be useful. I >>>>>>>> sometimes >>>>>>>> include an if...then... to ignore the trigger on the first k-cycle >>>>>>>> if >>>>>>>> it >>>>>>>> causes something unwanted. I would agree to option 3 but this is >>>>>>>> changing >>>>>>>> the behaviour although changed2 feels like an extravagance. >>>>>>>> >>>>>>>> ________________________________ >>>>>>>> Date: Fri, 1 Jan 2016 13:54:31 +0000 >>>>>>>> From: rorywalsh@EAR.IE >>>>>>>> Subject: Re: [Csnd] Question about changed opcode >>>>>>>> To: CSOUND@LISTSERV.HEANET.IE >>>>>>>> >>>>>>>> >>>>>>>> That does seem odd. I would prefer to see option 3 in place, but >>>>>>>> I'm >>>>>>>> not >>>>>>>> sure we can change this without breaking people's instruments. The >>>>>>>> current >>>>>>>> state doesn't make much sense. Anyone for a changed2 opcode?! >>>>>>>> >>>>>>>> On 1 January 2016 at 13:40, jpff wrote: >>>>>>>> >>>>>>>> Seeking advice on this. >>>>>>>> >>>>>>>> The changed opcode reports if any of a number of kvars have >>>>>>>> changed >>>>>>>> from the previous cycle. It remembers that last values for >>>>>>>> comparison. But that value is initialised to zero, with the >>>>>>>> consequence that >>>>>>>> kk = 0 >>>>>>>> kt changed kk >>>>>>>> printk 0, kt >>>>>>>> and >>>>>>>> kk = 1 >>>>>>>> kt changed kk >>>>>>>> printk 0, kt >>>>>>>> differ as the first cycle does not/does report a change. >>>>>>>> >>>>>>>> Is this acceptable? Three offers >>>>>>>> 1: do nowt >>>>>>>> 2: initialise to random values so usually first cycle changes >>>>>>>> 3: treat first k-cycle differently so first cycle does not change. >>>>>>>> >>>>>>>> Any thoughts? Or will this break things? Current state is hard >>>>>>>> to >>>>>>>> explain though. >>>>>>>> >>>>>>>> ==John ffitch >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>> to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>> features >>>>>>>> can >>>>>>>> be posted here >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>> to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>> features >>>>>>>> can >>>>>>>> be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Oeyvind Brandtsegg >>>>>>> Professor of Music Technology >>>>>>> NTNU >>>>>>> 7491 Trondheim >>>>>>> Norway >>>>>>> Cell: +47 92 203 205 >>>>>>> >>>>>>> http://www.partikkelaudio.com/ >>>>>>> http://soundcloud.com/brandtsegg >>>>>>> http://flyndresang.no/ >>>>>>> http://soundcloud.com/t-emp >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>> features >>>>>> can >>>>>> be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Oeyvind Brandtsegg >>>>> Professor of Music Technology >>>>> NTNU >>>>> 7491 Trondheim >>>>> Norway >>>>> Cell: +47 92 203 205 >>>>> >>>>> http://www.partikkelaudio.com/ >>>>> http://soundcloud.com/brandtsegg >>>>> http://flyndresang.no/ >>>>> http://soundcloud.com/t-emp >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> Csound mailing list Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>> https://github.com/csound/csound/issues Discussions of bugs and features >>>> can >>>> be posted here >>> >>> >>> >>> -- >>> >>> Oeyvind Brandtsegg >>> Professor of Music Technology >>> NTNU >>> 7491 Trondheim >>> Norway >>> Cell: +47 92 203 205 >>> >>> http://www.partikkelaudio.com/ >>> http://soundcloud.com/brandtsegg >>> http://flyndresang.no/ >>> http://soundcloud.com/t-emp >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> >> Csound mailing list Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> https://github.com/csound/csound/issues Discussions of bugs and features can >> be posted here > > > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-04 21:54
From	Rory Walsh
Subject	Re: Question about changed opcode
	There sure is :) On 4 Jan 2016 9:39 pm, "joachim heintz" <jh@joachimheintz.de> wrote: yes, but as my personal secret service tells me, iain will leave to maynooth — good for maynooth, bad for berlin, and bad, too, for a poor german friend living in hannover ... so, maybe dublin ... i have heard there is beer, too ... j On 03/01/16 22:23, Oeyvind Brandtsegg wrote: IIRC, There was some talk about gathering in Berlin sometime in June? 2016-01-03 22:07 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: Every birthday is a reason to celebrate! On 3 January 2016 at 21:00, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Csound at 30, counting 1986-2016, would be an occation? 2016-01-03 21:54 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: We're going to have to have a get together soon so we can buy all these beers! On 3 January 2016 at 20:50, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: o my..., sorry ...(Beer count +1) 2016-01-03 21:33 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: The fact that changed takes any number of input arguments might make this option a little messy? On 3 January 2016 at 20:24, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Is it an option to add an optinonal argument to changed? The optional arg would set it to the new behaviour, but it will still work like it used to do if the argument is not present. Still not too pretty, but perhaps better than changed2? 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: I agree that the initial trigger is unlikely to be useful. I sometimes include an if...then... to ignore the trigger on the first k-cycle if it causes something unwanted. I would agree to option 3 but this is changing the behaviour although changed2 feels like an extravagance. ________________________________ Date: Fri, 1 Jan 2016 13:54:31 +0000 From: rorywalsh@EAR.IE Subject: Re: [Csnd] Question about changed opcode To: CSOUND@LISTSERV.HEANET.IE That does seem odd. I would prefer to see option 3 in place, but I'm not sure we can change this without breaking people's instruments. The current state doesn't make much sense. Anyone for a changed2 opcode?! On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: Seeking advice on this. The changed opcode reports if any of a number of kvars have changed from the previous cycle. It remembers that last values for comparison. But that value is initialised to zero, with the consequence that kk = 0 kt changed kk printk 0, kt and kk = 1 kt changed kk printk 0, kt differ as the first cycle does not/does report a change. Is this acceptable? Three offers 1: do nowt 2: initialise to random values so usually first cycle changes 3: treat first k-cycle differently so first cycle does not change. Any thoughts? Or will this break things? Current state is hard to explain though. ==John ffitch Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-04 22:28
From	Victor Lazzarini
Subject	Re: Question about changed opcode
	yes, Iain is joining us from February. We’re hoping to do some sort of a Csound day with the three colleges (ours, rory's and brian’s) somewhere sometime. ======================== Dr Victor Lazzarini Dean of Arts, Celtic Studies and Philosophy, Maynooth University, Maynooth, Co Kildare, Ireland Tel: 00 353 7086936 Fax: 00 353 1 7086952 > On 4 Jan 2016, at 21:39, joachim heintz wrote: > > yes, but as my personal secret service tells me, iain will leave to maynooth — good for maynooth, bad for berlin, and bad, too, for a poor german friend living in hannover ... > > so, maybe dublin ... i have heard there is beer, too ... > > j > > > On 03/01/16 22:23, Oeyvind Brandtsegg wrote: >> IIRC, There was some talk about gathering in Berlin sometime in June? >> >> 2016-01-03 22:07 GMT+01:00 Rory Walsh : >>> Every birthday is a reason to celebrate! >>> >>> On 3 January 2016 at 21:00, Oeyvind Brandtsegg >>> wrote: >>>> >>>> Csound at 30, counting 1986-2016, >>>> would be an occation? >>>> >>>> 2016-01-03 21:54 GMT+01:00 Rory Walsh : >>>>> We're going to have to have a get together soon so we can buy all these >>>>> beers! >>>>> >>>>> On 3 January 2016 at 20:50, Oeyvind Brandtsegg >>>>> >>>>> wrote: >>>>>> >>>>>> o my..., sorry >>>>>> ...(Beer count +1) >>>>>> >>>>>> 2016-01-03 21:33 GMT+01:00 Rory Walsh : >>>>>>> The fact that changed takes any number of input arguments might make >>>>>>> this >>>>>>> option a little messy? >>>>>>> >>>>>>> On 3 January 2016 at 20:24, Oeyvind Brandtsegg >>>>>>> >>>>>>> wrote: >>>>>>>> >>>>>>>> Is it an option to add an optinonal argument to changed? >>>>>>>> The optional arg would set it to the new behaviour, but it will >>>>>>>> still >>>>>>>> work like it used to do if the argument is not present. >>>>>>>> Still not too pretty, but perhaps better than changed2? >>>>>>>> >>>>>>>> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >>>>>>>>> I agree that the initial trigger is unlikely to be useful. I >>>>>>>>> sometimes >>>>>>>>> include an if...then... to ignore the trigger on the first k-cycle >>>>>>>>> if >>>>>>>>> it >>>>>>>>> causes something unwanted. I would agree to option 3 but this is >>>>>>>>> changing >>>>>>>>> the behaviour although changed2 feels like an extravagance. >>>>>>>>> >>>>>>>>> ________________________________ >>>>>>>>> Date: Fri, 1 Jan 2016 13:54:31 +0000 >>>>>>>>> From: rorywalsh@EAR.IE >>>>>>>>> Subject: Re: [Csnd] Question about changed opcode >>>>>>>>> To: CSOUND@LISTSERV.HEANET.IE >>>>>>>>> >>>>>>>>> >>>>>>>>> That does seem odd. I would prefer to see option 3 in place, but >>>>>>>>> I'm >>>>>>>>> not >>>>>>>>> sure we can change this without breaking people's instruments. The >>>>>>>>> current >>>>>>>>> state doesn't make much sense. Anyone for a changed2 opcode?! >>>>>>>>> >>>>>>>>> On 1 January 2016 at 13:40, jpff wrote: >>>>>>>>> >>>>>>>>> Seeking advice on this. >>>>>>>>> >>>>>>>>> The changed opcode reports if any of a number of kvars have >>>>>>>>> changed >>>>>>>>> from the previous cycle. It remembers that last values for >>>>>>>>> comparison. But that value is initialised to zero, with the >>>>>>>>> consequence that >>>>>>>>> kk = 0 >>>>>>>>> kt changed kk >>>>>>>>> printk 0, kt >>>>>>>>> and >>>>>>>>> kk = 1 >>>>>>>>> kt changed kk >>>>>>>>> printk 0, kt >>>>>>>>> differ as the first cycle does not/does report a change. >>>>>>>>> >>>>>>>>> Is this acceptable? Three offers >>>>>>>>> 1: do nowt >>>>>>>>> 2: initialise to random values so usually first cycle changes >>>>>>>>> 3: treat first k-cycle differently so first cycle does not change. >>>>>>>>> >>>>>>>>> Any thoughts? Or will this break things? Current state is hard >>>>>>>>> to >>>>>>>>> explain though. >>>>>>>>> >>>>>>>>> ==John ffitch >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>> to >>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>> features >>>>>>>>> can >>>>>>>>> be posted here >>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>> to >>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>> features >>>>>>>>> can >>>>>>>>> be posted here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Oeyvind Brandtsegg >>>>>>>> Professor of Music Technology >>>>>>>> NTNU >>>>>>>> 7491 Trondheim >>>>>>>> Norway >>>>>>>> Cell: +47 92 203 205 >>>>>>>> >>>>>>>> http://www.partikkelaudio.com/ >>>>>>>> http://soundcloud.com/brandtsegg >>>>>>>> http://flyndresang.no/ >>>>>>>> http://soundcloud.com/t-emp >>>>>>>> >>>>>>>> Csound mailing list >>>>>>>> Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>> Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues >>>>>>>> Discussions of bugs and features can be posted here >>>>>>> >>>>>>> >>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>> features >>>>>>> can >>>>>>> be posted here >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Oeyvind Brandtsegg >>>>>> Professor of Music Technology >>>>>> NTNU >>>>>> 7491 Trondheim >>>>>> Norway >>>>>> Cell: +47 92 203 205 >>>>>> >>>>>> http://www.partikkelaudio.com/ >>>>>> http://soundcloud.com/brandtsegg >>>>>> http://flyndresang.no/ >>>>>> http://soundcloud.com/t-emp >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> >>>>> Csound mailing list Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>> https://github.com/csound/csound/issues Discussions of bugs and features >>>>> can >>>>> be posted here >>>> >>>> >>>> >>>> -- >>>> >>>> Oeyvind Brandtsegg >>>> Professor of Music Technology >>>> NTNU >>>> 7491 Trondheim >>>> Norway >>>> Cell: +47 92 203 205 >>>> >>>> http://www.partikkelaudio.com/ >>>> http://soundcloud.com/brandtsegg >>>> http://flyndresang.no/ >>>> http://soundcloud.com/t-emp >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> >>> Csound mailing list Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>> https://github.com/csound/csound/issues Discussions of bugs and features can >>> be posted here >> >> >> > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-01-04 23:33
From	Oeyvind Brandtsegg
Subject	Re: Question about changed opcode
	Congratulations Iain!, and congrats to Maynooth too for gettin Iain. 2016-01-04 23:28 GMT+01:00 Victor Lazzarini : > yes, Iain is joining us from February. We’re hoping to do some sort of a Csound day with > the three colleges (ours, rory's and brian’s) somewhere sometime. > ======================== > Dr Victor Lazzarini > Dean of Arts, Celtic Studies and Philosophy, > Maynooth University, > Maynooth, Co Kildare, Ireland > Tel: 00 353 7086936 > Fax: 00 353 1 7086952 > >> On 4 Jan 2016, at 21:39, joachim heintz wrote: >> >> yes, but as my personal secret service tells me, iain will leave to maynooth — good for maynooth, bad for berlin, and bad, too, for a poor german friend living in hannover ... >> >> so, maybe dublin ... i have heard there is beer, too ... >> >> j >> >> >> On 03/01/16 22:23, Oeyvind Brandtsegg wrote: >>> IIRC, There was some talk about gathering in Berlin sometime in June? >>> >>> 2016-01-03 22:07 GMT+01:00 Rory Walsh : >>>> Every birthday is a reason to celebrate! >>>> >>>> On 3 January 2016 at 21:00, Oeyvind Brandtsegg >>>> wrote: >>>>> >>>>> Csound at 30, counting 1986-2016, >>>>> would be an occation? >>>>> >>>>> 2016-01-03 21:54 GMT+01:00 Rory Walsh : >>>>>> We're going to have to have a get together soon so we can buy all these >>>>>> beers! >>>>>> >>>>>> On 3 January 2016 at 20:50, Oeyvind Brandtsegg >>>>>> >>>>>> wrote: >>>>>>> >>>>>>> o my..., sorry >>>>>>> ...(Beer count +1) >>>>>>> >>>>>>> 2016-01-03 21:33 GMT+01:00 Rory Walsh : >>>>>>>> The fact that changed takes any number of input arguments might make >>>>>>>> this >>>>>>>> option a little messy? >>>>>>>> >>>>>>>> On 3 January 2016 at 20:24, Oeyvind Brandtsegg >>>>>>>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Is it an option to add an optinonal argument to changed? >>>>>>>>> The optional arg would set it to the new behaviour, but it will >>>>>>>>> still >>>>>>>>> work like it used to do if the argument is not present. >>>>>>>>> Still not too pretty, but perhaps better than changed2? >>>>>>>>> >>>>>>>>> 2016-01-01 20:19 GMT+01:00 Iain McCurdy : >>>>>>>>>> I agree that the initial trigger is unlikely to be useful. I >>>>>>>>>> sometimes >>>>>>>>>> include an if...then... to ignore the trigger on the first k-cycle >>>>>>>>>> if >>>>>>>>>> it >>>>>>>>>> causes something unwanted. I would agree to option 3 but this is >>>>>>>>>> changing >>>>>>>>>> the behaviour although changed2 feels like an extravagance. >>>>>>>>>> >>>>>>>>>> ________________________________ >>>>>>>>>> Date: Fri, 1 Jan 2016 13:54:31 +0000 >>>>>>>>>> From: rorywalsh@EAR.IE >>>>>>>>>> Subject: Re: [Csnd] Question about changed opcode >>>>>>>>>> To: CSOUND@LISTSERV.HEANET.IE >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> That does seem odd. I would prefer to see option 3 in place, but >>>>>>>>>> I'm >>>>>>>>>> not >>>>>>>>>> sure we can change this without breaking people's instruments. The >>>>>>>>>> current >>>>>>>>>> state doesn't make much sense. Anyone for a changed2 opcode?! >>>>>>>>>> >>>>>>>>>> On 1 January 2016 at 13:40, jpff wrote: >>>>>>>>>> >>>>>>>>>> Seeking advice on this. >>>>>>>>>> >>>>>>>>>> The changed opcode reports if any of a number of kvars have >>>>>>>>>> changed >>>>>>>>>> from the previous cycle. It remembers that last values for >>>>>>>>>> comparison. But that value is initialised to zero, with the >>>>>>>>>> consequence that >>>>>>>>>> kk = 0 >>>>>>>>>> kt changed kk >>>>>>>>>> printk 0, kt >>>>>>>>>> and >>>>>>>>>> kk = 1 >>>>>>>>>> kt changed kk >>>>>>>>>> printk 0, kt >>>>>>>>>> differ as the first cycle does not/does report a change. >>>>>>>>>> >>>>>>>>>> Is this acceptable? Three offers >>>>>>>>>> 1: do nowt >>>>>>>>>> 2: initialise to random values so usually first cycle changes >>>>>>>>>> 3: treat first k-cycle differently so first cycle does not change. >>>>>>>>>> >>>>>>>>>> Any thoughts? Or will this break things? Current state is hard >>>>>>>>>> to >>>>>>>>>> explain though. >>>>>>>>>> >>>>>>>>>> ==John ffitch >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>>> to >>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>>> features >>>>>>>>>> can >>>>>>>>>> be posted here >>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>>> to >>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>>> features >>>>>>>>>> can >>>>>>>>>> be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Oeyvind Brandtsegg >>>>>>>>> Professor of Music Technology >>>>>>>>> NTNU >>>>>>>>> 7491 Trondheim >>>>>>>>> Norway >>>>>>>>> Cell: +47 92 203 205 >>>>>>>>> >>>>>>>>> http://www.partikkelaudio.com/ >>>>>>>>> http://soundcloud.com/brandtsegg >>>>>>>>> http://flyndresang.no/ >>>>>>>>> http://soundcloud.com/t-emp >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>> features >>>>>>>> can >>>>>>>> be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Oeyvind Brandtsegg >>>>>>> Professor of Music Technology >>>>>>> NTNU >>>>>>> 7491 Trondheim >>>>>>> Norway >>>>>>> Cell: +47 92 203 205 >>>>>>> >>>>>>> http://www.partikkelaudio.com/ >>>>>>> http://soundcloud.com/brandtsegg >>>>>>> http://flyndresang.no/ >>>>>>> http://soundcloud.com/t-emp >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>> https://github.com/csound/csound/issues Discussions of bugs and features >>>>>> can >>>>>> be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Oeyvind Brandtsegg >>>>> Professor of Music Technology >>>>> NTNU >>>>> 7491 Trondheim >>>>> Norway >>>>> Cell: +47 92 203 205 >>>>> >>>>> http://www.partikkelaudio.com/ >>>>> http://soundcloud.com/brandtsegg >>>>> http://flyndresang.no/ >>>>> http://soundcloud.com/t-emp >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> Csound mailing list Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>> be posted here >>> >>> >>> >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-03-01 21:00
From	"Dr. Richard Boulanger"
Subject	Re: Question about changed opcode
	Congrats to Iain. Congrats to Maynooth. And... we all benefit because Iain being in a program (Victor's program) that will totally support his Csound work is an awesome thing for all Csounders! -dB _____________________________________________ Dr. Richard Boulanger Professor of Electronic Production and Design Professional Writing and Music Technology Division Berklee College of Music 1140 Boylston Street, FB-75 Boston, MA 02215-3693 Office @ 161 Mass Ave - 4th Floor 617-747-2384 (office) 774-488-9166 (cell) ______________________________________________ rboulanger@berklee.edu (email) https://www.facebook.com/richard.boulanger.58 (facebook) ______________________________________________ President of Boulanger Labs - http://boulangerlabs.com Director of Csounds.com - http://csounds.com Author & Editor: The Csound Book - http://mitpress.mit.edu/books/csound-book Author & Editor: The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book ______________________________________________ about: http://www.boulangerlabs.com/about/richardboulanger/ about: http://www.csounds.com/community/developers/dr-richard-boulanger/ ______________________________________________ music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/ On Mon, Jan 4, 2016 at 6:33 PM, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Congratulations Iain!, and congrats to Maynooth too for gettin Iain. 2016-01-04 23:28 GMT+01:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>: > yes, Iain is joining us from February. We’re hoping to do some sort of a Csound day with > the three colleges (ours, rory's and brian’s) somewhere sometime. > ======================== > Dr Victor Lazzarini > Dean of Arts, Celtic Studies and Philosophy, > Maynooth University, > Maynooth, Co Kildare, Ireland > Tel: 00 353 7086936 > Fax: 00 353 1 7086952 > >> On 4 Jan 2016, at 21:39, joachim heintz <jh@joachimheintz.de> wrote: >> >> yes, but as my personal secret service tells me, iain will leave to maynooth — good for maynooth, bad for berlin, and bad, too, for a poor german friend living in hannover ... >> >> so, maybe dublin ... i have heard there is beer, too ... >> >> j >> >> >> On 03/01/16 22:23, Oeyvind Brandtsegg wrote: >>> IIRC, There was some talk about gathering in Berlin sometime in June? >>> >>> 2016-01-03 22:07 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >>>> Every birthday is a reason to celebrate! >>>> >>>> On 3 January 2016 at 21:00, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> >>>> wrote: >>>>> >>>>> Csound at 30, counting 1986-2016, >>>>> would be an occation? >>>>> >>>>> 2016-01-03 21:54 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >>>>>> We're going to have to have a get together soon so we can buy all these >>>>>> beers! >>>>>> >>>>>> On 3 January 2016 at 20:50, Oeyvind Brandtsegg >>>>>> <oyvind.brandtsegg@ntnu.no> >>>>>> wrote: >>>>>>> >>>>>>> o my..., sorry >>>>>>> ...(Beer count +1) >>>>>>> >>>>>>> 2016-01-03 21:33 GMT+01:00 Rory Walsh <rorywalsh@ear.ie>: >>>>>>>> The fact that changed takes any number of input arguments might make >>>>>>>> this >>>>>>>> option a little messy? >>>>>>>> >>>>>>>> On 3 January 2016 at 20:24, Oeyvind Brandtsegg >>>>>>>> <oyvind.brandtsegg@ntnu.no> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Is it an option to add an optinonal argument to changed? >>>>>>>>> The optional arg would set it to the new behaviour, but it will >>>>>>>>> still >>>>>>>>> work like it used to do if the argument is not present. >>>>>>>>> Still not too pretty, but perhaps better than changed2? >>>>>>>>> >>>>>>>>> 2016-01-01 20:19 GMT+01:00 Iain McCurdy <i_mccurdy@hotmail.com>: >>>>>>>>>> I agree that the initial trigger is unlikely to be useful. I >>>>>>>>>> sometimes >>>>>>>>>> include an if...then... to ignore the trigger on the first k-cycle >>>>>>>>>> if >>>>>>>>>> it >>>>>>>>>> causes something unwanted. I would agree to option 3 but this is >>>>>>>>>> changing >>>>>>>>>> the behaviour although changed2 feels like an extravagance. >>>>>>>>>> >>>>>>>>>> ________________________________ >>>>>>>>>> Date: Fri, 1 Jan 2016 13:54:31 +0000 >>>>>>>>>> From: rorywalsh@EAR.IE >>>>>>>>>> Subject: Re: [Csnd] Question about changed opcode >>>>>>>>>> To: CSOUND@LISTSERV.HEANET.IE >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> That does seem odd. I would prefer to see option 3 in place, but >>>>>>>>>> I'm >>>>>>>>>> not >>>>>>>>>> sure we can change this without breaking people's instruments. The >>>>>>>>>> current >>>>>>>>>> state doesn't make much sense. Anyone for a changed2 opcode?! >>>>>>>>>> >>>>>>>>>> On 1 January 2016 at 13:40, jpff <jpff@codemist.co.uk> wrote: >>>>>>>>>> >>>>>>>>>> Seeking advice on this. >>>>>>>>>> >>>>>>>>>> The changed opcode reports if any of a number of kvars have >>>>>>>>>> changed >>>>>>>>>> from the previous cycle. It remembers that last values for >>>>>>>>>> comparison. But that value is initialised to zero, with the >>>>>>>>>> consequence that >>>>>>>>>> kk = 0 >>>>>>>>>> kt changed kk >>>>>>>>>> printk 0, kt >>>>>>>>>> and >>>>>>>>>> kk = 1 >>>>>>>>>> kt changed kk >>>>>>>>>> printk 0, kt >>>>>>>>>> differ as the first cycle does not/does report a change. >>>>>>>>>> >>>>>>>>>> Is this acceptable? Three offers >>>>>>>>>> 1: do nowt >>>>>>>>>> 2: initialise to random values so usually first cycle changes >>>>>>>>>> 3: treat first k-cycle differently so first cycle does not change. >>>>>>>>>> >>>>>>>>>> Any thoughts? Or will this break things? Current state is hard >>>>>>>>>> to >>>>>>>>>> explain though. >>>>>>>>>> >>>>>>>>>> ==John ffitch >>>>>>>>>> >>>>>>>>>> Csound mailing list >>>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>>> Send bugs reports to >>>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>>> to >>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>>> features >>>>>>>>>> can >>>>>>>>>> be posted here >>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports >>>>>>>>>> to >>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>>>> features >>>>>>>>>> can >>>>>>>>>> be posted here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Oeyvind Brandtsegg >>>>>>>>> Professor of Music Technology >>>>>>>>> NTNU >>>>>>>>> 7491 Trondheim >>>>>>>>> Norway >>>>>>>>> Cell: +47 92 203 205 >>>>>>>>> >>>>>>>>> http://www.partikkelaudio.com/ >>>>>>>>> http://soundcloud.com/brandtsegg >>>>>>>>> http://flyndresang.no/ >>>>>>>>> http://soundcloud.com/t-emp >>>>>>>>> >>>>>>>>> Csound mailing list >>>>>>>>> Csound@listserv.heanet.ie >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>>>> Send bugs reports to >>>>>>>>> https://github.com/csound/csound/issues >>>>>>>>> Discussions of bugs and features can be posted here >>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and >>>>>>>> features >>>>>>>> can >>>>>>>> be posted here >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Oeyvind Brandtsegg >>>>>>> Professor of Music Technology >>>>>>> NTNU >>>>>>> 7491 Trondheim >>>>>>> Norway >>>>>>> Cell: +47 92 203 205 >>>>>>> >>>>>>> http://www.partikkelaudio.com/ >>>>>>> http://soundcloud.com/brandtsegg >>>>>>> http://flyndresang.no/ >>>>>>> http://soundcloud.com/t-emp >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> >>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>> https://github.com/csound/csound/issues Discussions of bugs and features >>>>>> can >>>>>> be posted here >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Oeyvind Brandtsegg >>>>> Professor of Music Technology >>>>> NTNU >>>>> 7491 Trondheim >>>>> Norway >>>>> Cell: +47 92 203 205 >>>>> >>>>> http://www.partikkelaudio.com/ >>>>> http://soundcloud.com/brandtsegg >>>>> http://flyndresang.no/ >>>>> http://soundcloud.com/t-emp >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> >>>> Csound mailing list Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>> be posted here >>> >>> >>> >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://flyndresang.no/ http://soundcloud.com/t-emp Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here