[Cs-dev] Next release dates

[Cs-dev] Next release dates

Date	2010-01-04 18:12
From	john ffitch
Subject	[Cs-dev] Next release dates
	It is now January, so time to make a timetable. I have gained an extra constraint for the week of 11 jan, so may I suggest: Cease code changes 16 Jan Release built systems 20 Jan Start work on 5.13 21 Jan Is that OK for all packagers and builders? And code changers, documenters and all ==John ffitch ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-04 19:09
From	victor
Subject	Re: [Cs-dev] Next release dates
	Sounds good to me. ----- Original Message ----- From: "john ffitch" To: Sent: Monday, January 04, 2010 6:12 PM Subject: [Cs-dev] Next release dates > It is now January, so time to make a timetable. I have gained an > extra constraint for the week of 11 jan, so may I suggest: > > Cease code changes 16 Jan > Release built systems 20 Jan > Start work on 5.13 21 Jan > > Is that OK for all packagers and builders? And code changers, > documenters and all > > ==John ffitch > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-04 20:25
From	Michael Gogins
Subject	Re: [Cs-dev] Next release dates
	Fine with me. Regards, Mike On 1/4/10, victor wrote: > Sounds good to me. > ----- Original Message ----- > From: "john ffitch" > To: > Sent: Monday, January 04, 2010 6:12 PM > Subject: [Cs-dev] Next release dates > > >> It is now January, so time to make a timetable. I have gained an >> extra constraint for the week of 11 jan, so may I suggest: >> >> Cease code changes 16 Jan >> Release built systems 20 Jan >> Start work on 5.13 21 Jan >> >> Is that OK for all packagers and builders? And code changers, >> documenters and all >> >> ==John ffitch >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Michael Gogins Irreducible Productions http://www.michael-gogins.com Michael dot Gogins at gmail dot com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-05 08:20
From	Oeyvind Brandtsegg
Subject	Re: [Cs-dev] Next release dates
	I'm trying to finish the documentation and example for the modmatrix opcode (the opcode itself has been submitted), hopefully I'll be able to get it done before the 16th as suggested. If not, a few days to or fro won't make much of a difference, I got a heavy start this year. ... so stick to the suggested timetable, yes. Oeyvind 2010/1/4 Michael Gogins : > Fine with me. > > Regards, > Mike > > On 1/4/10, victor wrote: >> Sounds good to me. >> ----- Original Message ----- >> From: "john ffitch" >> To: >> Sent: Monday, January 04, 2010 6:12 PM >> Subject: [Cs-dev] Next release dates >> >> >>> It is now January, so time to make a timetable. I have gained an >>> extra constraint for the week of 11 jan, so may I suggest: >>> >>> Cease code changes 16 Jan >>> Release built systems 20 Jan >>> Start work on 5.13 21 Jan >>> >>> Is that OK for all packagers and builders? And code changers, >>> documenters and all >>> >>> ==John ffitch >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > > -- > Michael Gogins > Irreducible Productions > http://www.michael-gogins.com > Michael dot Gogins at gmail dot com > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-06 17:56
From	Michael Gogins
Subject	Re: [Cs-dev] Next release dates
	For the next release I have added to the Csound API samplewise access to the Csound audio input (spin) and output (spout) buffers, and to the numbered software busses. This should simplify matters for API writers and get round the problems with pointers to pointers, which SWIG doesn't wrap, for the audio busses. The code is committed but only very lightly tested. For example, I did not verify that adding to input actually works; the timing of calls in kperf may need to be changed. Also, the bus calls that return MYFLT values also return error codes on failure. This of course means that testing return calls for errors is not reliable as a valid sample value could be (although it is unlikely) the same as an error code. But I thought it was better than doing nothing for errors, and we need the value semantics. Regards, Mike /** * Adds the indicated sample into the audio input woriing buffer (spin); * this only ever makes sense before calling csoundPerformKsmps(). * The frame and channel must be in bounds relative to ksmps and nchnls. / PUBLIC void csoundAddSpinSample(CSOUND csound, int frame, int channel, MYFLT sample); /** * Returns the indicated sample from the Csound audio output working buffer (spout); * only ever makes sense after calling csoundPerformKsmps(). * The frame and channel must be in bounds relative to ksmps and nchnls. / PUBLIC MYFLT csoundGetSpoutSample(CSOUND csound, int frame, int channel); /** * Sets the chani opcode MYFLT k-rate value for the indicated channel. * The bus is automatically extended if the channel is greater than * previously used, clearing new locations to zero. * Returns zero on success, CSOUND_ERROR if the index is invalid, * and CSOUND_MEMORY if there is not enough memory to estend the bus. / PUBLIC int csoundChanIKSetValue(CSOUND , int channel, MYFLT value); /** * Returns the chani opcode MYFLT k-rate value for the indicated channel. * The bus is automatically extended if the channel is greater than * previously used, clearing new locations to zero. * Returns the sample value on success, CSOUND_ERROR if the index is invalid, * and CSOUND_MEMORY if there is not enough memory to estend the bus / PUBLIC MYFLT csoundChanOKGetValue(CSOUND , int channel); /** * Sets the chani opcode MYFLT a-rate value for the indicated frame * of the indicated channel. * The bus is automatically extended if the channel is greater than * previously used, clearing new locations to zero. * Returns zero on success, CSOUND_ERROR if the index is invalid, * and CSOUND_MEMORY if there is not enough memory to estend the bus. / PUBLIC int csoundChanIASetSample(CSOUND , int channel, int frame, MYFLT sample); /** * Sets the chani opcode MYFLT a-rate value for the indicated frame * for the indicated channel. * The bus is automatically extended if the channel is greater than * previously used, clearing new locations to zero. * Returns the sample value on success, CSOUND_ERROR if the index is invalid, * and CSOUND_MEMORY if there is not enough memory to estend the bus. / PUBLIC MYFLT csoundChanOAGetSample(CSOUND , int channel, int frame); On 1/5/10, Oeyvind Brandtsegg wrote: > I'm trying to finish the documentation and example for the modmatrix > opcode (the opcode itself has been submitted), > hopefully I'll be able to get it done before the 16th as suggested. > If not, a few days to or fro won't make much of a difference, I got a > heavy start this year. > ... so stick to the suggested timetable, yes. > Oeyvind > > 2010/1/4 Michael Gogins : >> Fine with me. >> >> Regards, >> Mike >> >> On 1/4/10, victor wrote: >>> Sounds good to me. >>> ----- Original Message ----- >>> From: "john ffitch" >>> To: >>> Sent: Monday, January 04, 2010 6:12 PM >>> Subject: [Cs-dev] Next release dates >>> >>> >>>> It is now January, so time to make a timetable. I have gained an >>>> extra constraint for the week of 11 jan, so may I suggest: >>>> >>>> Cease code changes 16 Jan >>>> Release built systems 20 Jan >>>> Start work on 5.13 21 Jan >>>> >>>> Is that OK for all packagers and builders? And code changers, >>>> documenters and all >>>> >>>> ==John ffitch >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and >>>> easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> >> -- >> Michael Gogins >> Irreducible Productions >> http://www.michael-gogins.com >> Michael dot Gogins at gmail dot com >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Michael Gogins Irreducible Productions http://www.michael-gogins.com Michael dot Gogins at gmail dot com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-06 20:55
From	Andres Cabrera
Subject	Re: [Cs-dev] Next release dates
	Hi Michael, Would this mean the API needs a version bump? Last time that was done it sent ripples all along the distribution chain, so I think it should not be taken lightly and as much as possible should be added when the version is bumped. Cheers, Andres On 1/6/10, Michael Gogins wrote: > For the next release I have added to the Csound API samplewise access > to the Csound audio input (spin) and output (spout) buffers, and to > the numbered software busses. This should simplify matters for API > writers and get round the problems with pointers to pointers, which > SWIG doesn't wrap, for the audio busses. > > The code is committed but only very lightly tested. For example, I did > not verify that adding to input actually works; the timing of calls in > kperf may need to be changed. > > Also, the bus calls that return MYFLT values also return error codes > on failure. This of course means that testing return calls for errors > is not reliable as a valid sample value could be (although it is > unlikely) the same as an error code. But I thought it was better than > doing nothing for errors, and we need the value semantics. > > Regards, > Mike > > /** > * Adds the indicated sample into the audio input woriing buffer (spin); > * this only ever makes sense before calling csoundPerformKsmps(). > * The frame and channel must be in bounds relative to ksmps and nchnls. > / > PUBLIC void csoundAddSpinSample(CSOUND csound, int frame, int > channel, MYFLT sample); > > /** > * Returns the indicated sample from the Csound audio output working > buffer (spout); > * only ever makes sense after calling csoundPerformKsmps(). > * The frame and channel must be in bounds relative to ksmps and nchnls. > / > PUBLIC MYFLT csoundGetSpoutSample(CSOUND csound, int frame, int channel); > > /** > * Sets the chani opcode MYFLT k-rate value for the indicated channel. > * The bus is automatically extended if the channel is greater than > * previously used, clearing new locations to zero. > * Returns zero on success, CSOUND_ERROR if the index is invalid, > * and CSOUND_MEMORY if there is not enough memory to estend the bus. > / > PUBLIC int csoundChanIKSetValue(CSOUND , int channel, MYFLT value); > > /** > * Returns the chani opcode MYFLT k-rate value for the indicated channel. > * The bus is automatically extended if the channel is greater than > * previously used, clearing new locations to zero. > * Returns the sample value on success, CSOUND_ERROR if the index is > invalid, > * and CSOUND_MEMORY if there is not enough memory to estend the bus > / > PUBLIC MYFLT csoundChanOKGetValue(CSOUND , int channel); > > /** > * Sets the chani opcode MYFLT a-rate value for the indicated frame > * of the indicated channel. > * The bus is automatically extended if the channel is greater than > * previously used, clearing new locations to zero. > * Returns zero on success, CSOUND_ERROR if the index is invalid, > * and CSOUND_MEMORY if there is not enough memory to estend the bus. > / > PUBLIC int csoundChanIASetSample(CSOUND , int channel, int frame, > MYFLT sample); > > /** > * Sets the chani opcode MYFLT a-rate value for the indicated frame > * for the indicated channel. > * The bus is automatically extended if the channel is greater than > * previously used, clearing new locations to zero. > * Returns the sample value on success, CSOUND_ERROR if the index is > invalid, > * and CSOUND_MEMORY if there is not enough memory to estend the bus. > / > PUBLIC MYFLT csoundChanOAGetSample(CSOUND , int channel, int frame); > > > > On 1/5/10, Oeyvind Brandtsegg wrote: >> I'm trying to finish the documentation and example for the modmatrix >> opcode (the opcode itself has been submitted), >> hopefully I'll be able to get it done before the 16th as suggested. >> If not, a few days to or fro won't make much of a difference, I got a >> heavy start this year. >> ... so stick to the suggested timetable, yes. >> Oeyvind >> >> 2010/1/4 Michael Gogins : >>> Fine with me. >>> >>> Regards, >>> Mike >>> >>> On 1/4/10, victor wrote: >>>> Sounds good to me. >>>> ----- Original Message ----- >>>> From: "john ffitch" >>>> To: >>>> Sent: Monday, January 04, 2010 6:12 PM >>>> Subject: [Cs-dev] Next release dates >>>> >>>> >>>>> It is now January, so time to make a timetable. I have gained an >>>>> extra constraint for the week of 11 jan, so may I suggest: >>>>> >>>>> Cease code changes 16 Jan >>>>> Release built systems 20 Jan >>>>> Start work on 5.13 21 Jan >>>>> >>>>> Is that OK for all packagers and builders? And code changers, >>>>> documenters and all >>>>> >>>>> ==John ffitch >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.Net email is sponsored by the Verizon Developer Community >>>>> Take advantage of Verizon's best-in-class app development support >>>>> A streamlined, 14 day to market process makes app distribution fast and >>>>> easy >>>>> Join now and get one step closer to millions of Verizon customers >>>>> http://p.sf.net/sfu/verizon-dev2dev >>>>> _______________________________________________ >>>>> Csound-devel mailing list >>>>> Csound-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and >>>> easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>> >>> >>> >>> -- >>> Michael Gogins >>> Irreducible Productions >>> http://www.michael-gogins.com >>> Michael dot Gogins at gmail dot com >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > > -- > Michael Gogins > Irreducible Productions > http://www.michael-gogins.com > Michael dot Gogins at gmail dot com > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Andrés ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-06 21:08
From	Michael Gogins
Subject	Re: [Cs-dev] Next release dates
	I am not sure. The functions went into empty slots in the existing CSOUND struct, and at the end of the Csound C++ class. So for C and C++, there is no need for a version bump. I am not sure what the impact will be with the Python, Java, Lua, etc. interfaces. There may or may not be a need for a version bump with these interfaces. We don't have separate API versions for each interface language, do we? Regards, Mike On 1/6/10, Andres Cabrera wrote: > Hi Michael, > > Would this mean the API needs a version bump? Last time that was done > it sent ripples all along the distribution chain, so I think it should > not be taken lightly and as much as possible should be added when the > version is bumped. > > Cheers, > Andres > > On 1/6/10, Michael Gogins wrote: >> For the next release I have added to the Csound API samplewise access >> to the Csound audio input (spin) and output (spout) buffers, and to >> the numbered software busses. This should simplify matters for API >> writers and get round the problems with pointers to pointers, which >> SWIG doesn't wrap, for the audio busses. >> >> The code is committed but only very lightly tested. For example, I did >> not verify that adding to input actually works; the timing of calls in >> kperf may need to be changed. >> >> Also, the bus calls that return MYFLT values also return error codes >> on failure. This of course means that testing return calls for errors >> is not reliable as a valid sample value could be (although it is >> unlikely) the same as an error code. But I thought it was better than >> doing nothing for errors, and we need the value semantics. >> >> Regards, >> Mike >> >> /** >> * Adds the indicated sample into the audio input woriing buffer (spin); >> * this only ever makes sense before calling csoundPerformKsmps(). >> * The frame and channel must be in bounds relative to ksmps and nchnls. >> / >> PUBLIC void csoundAddSpinSample(CSOUND csound, int frame, int >> channel, MYFLT sample); >> >> /** >> * Returns the indicated sample from the Csound audio output working >> buffer (spout); >> * only ever makes sense after calling csoundPerformKsmps(). >> * The frame and channel must be in bounds relative to ksmps and nchnls. >> / >> PUBLIC MYFLT csoundGetSpoutSample(CSOUND csound, int frame, int >> channel); >> >> /** >> * Sets the chani opcode MYFLT k-rate value for the indicated channel. >> * The bus is automatically extended if the channel is greater than >> * previously used, clearing new locations to zero. >> * Returns zero on success, CSOUND_ERROR if the index is invalid, >> * and CSOUND_MEMORY if there is not enough memory to estend the bus. >> / >> PUBLIC int csoundChanIKSetValue(CSOUND , int channel, MYFLT value); >> >> /** >> * Returns the chani opcode MYFLT k-rate value for the indicated >> channel. >> * The bus is automatically extended if the channel is greater than >> * previously used, clearing new locations to zero. >> * Returns the sample value on success, CSOUND_ERROR if the index is >> invalid, >> * and CSOUND_MEMORY if there is not enough memory to estend the bus >> / >> PUBLIC MYFLT csoundChanOKGetValue(CSOUND , int channel); >> >> /** >> * Sets the chani opcode MYFLT a-rate value for the indicated frame >> * of the indicated channel. >> * The bus is automatically extended if the channel is greater than >> * previously used, clearing new locations to zero. >> * Returns zero on success, CSOUND_ERROR if the index is invalid, >> * and CSOUND_MEMORY if there is not enough memory to estend the bus. >> / >> PUBLIC int csoundChanIASetSample(CSOUND , int channel, int frame, >> MYFLT sample); >> >> /** >> * Sets the chani opcode MYFLT a-rate value for the indicated frame >> * for the indicated channel. >> * The bus is automatically extended if the channel is greater than >> * previously used, clearing new locations to zero. >> * Returns the sample value on success, CSOUND_ERROR if the index is >> invalid, >> * and CSOUND_MEMORY if there is not enough memory to estend the bus. >> / >> PUBLIC MYFLT csoundChanOAGetSample(CSOUND , int channel, int frame); >> >> >> >> On 1/5/10, Oeyvind Brandtsegg wrote: >>> I'm trying to finish the documentation and example for the modmatrix >>> opcode (the opcode itself has been submitted), >>> hopefully I'll be able to get it done before the 16th as suggested. >>> If not, a few days to or fro won't make much of a difference, I got a >>> heavy start this year. >>> ... so stick to the suggested timetable, yes. >>> Oeyvind >>> >>> 2010/1/4 Michael Gogins : >>>> Fine with me. >>>> >>>> Regards, >>>> Mike >>>> >>>> On 1/4/10, victor wrote: >>>>> Sounds good to me. >>>>> ----- Original Message ----- >>>>> From: "john ffitch" >>>>> To: >>>>> Sent: Monday, January 04, 2010 6:12 PM >>>>> Subject: [Cs-dev] Next release dates >>>>> >>>>> >>>>>> It is now January, so time to make a timetable. I have gained an >>>>>> extra constraint for the week of 11 jan, so may I suggest: >>>>>> >>>>>> Cease code changes 16 Jan >>>>>> Release built systems 20 Jan >>>>>> Start work on 5.13 21 Jan >>>>>> >>>>>> Is that OK for all packagers and builders? And code changers, >>>>>> documenters and all >>>>>> >>>>>> ==John ffitch >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> This SF.Net email is sponsored by the Verizon Developer Community >>>>>> Take advantage of Verizon's best-in-class app development support >>>>>> A streamlined, 14 day to market process makes app distribution fast >>>>>> and >>>>>> easy >>>>>> Join now and get one step closer to millions of Verizon customers >>>>>> http://p.sf.net/sfu/verizon-dev2dev >>>>>> _______________________________________________ >>>>>> Csound-devel mailing list >>>>>> Csound-devel@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.Net email is sponsored by the Verizon Developer Community >>>>> Take advantage of Verizon's best-in-class app development support >>>>> A streamlined, 14 day to market process makes app distribution fast and >>>>> easy >>>>> Join now and get one step closer to millions of Verizon customers >>>>> http://p.sf.net/sfu/verizon-dev2dev >>>>> _______________________________________________ >>>>> Csound-devel mailing list >>>>> Csound-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>>> >>>> >>>> >>>> -- >>>> Michael Gogins >>>> Irreducible Productions >>>> http://www.michael-gogins.com >>>> Michael dot Gogins at gmail dot com >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and >>>> easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> Csound-devel mailing list >>>> Csound-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Csound-devel mailing list >>> Csound-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-devel >>> >> >> >> -- >> Michael Gogins >> Irreducible Productions >> http://www.michael-gogins.com >> Michael dot Gogins at gmail dot com >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Csound-devel mailing list >> Csound-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-devel >> > > > -- > > > Andrés > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > -- Michael Gogins Irreducible Productions http://www.michael-gogins.com Michael dot Gogins at gmail dot com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net

Date	2010-01-07 11:37
From	john ffitch
Subject	Re: [Cs-dev] Next release dates
	I do not think that Michael's changes require a major API bump. All older code will continue to run as the CSOUND structure has been extended in the whole for this purpose. A minor API increment is necessary though. ==John ffitch ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net