[Cs-dev] Windows build of Csound
Date | 2011-01-21 02:47 |
From | Michael Gogins |
Subject | [Cs-dev] Windows build of Csound |
I am getting to work on the 5.13 installer for Windows Csound. This will include all bells and whistles and be built with up to date tools and libraries. Please bring to my attention any issues relevant to this new Windows release. Bugs that I am aware of and plan to fix: -- Fencepost error in CsoundVST buffer indexing. -- Numerical imprecision in line, linen, linseg and corresponding "r" opcodes (adding increment rather than multiplying by increment, leading to drift over long time spans). Other changes: -- Need better "readme" for Windows. -- Xanadu to be default piece in QuteCsound. I am planning to use FLTK 1.3 and Python 2.7.1 for this release. A major upgrade like this can take several weeks to complete. Regards, Mike -- Michael Gogins Irreducible Productions http://www.michael-gogins.com Michael dot Gogins at gmail dot com ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2011-01-21 09:06 |
From | Victor.Lazzarini@nuim.ie |
Subject | Re: [Cs-dev] Windows build of Csound |
Attachments | None |
Date | 2011-01-21 09:45 |
From | Andres Cabrera |
Subject | Re: [Cs-dev] Windows build of Csound |
Hi Michael, > -- Xanadu to be default piece in QuteCsound. Are you planning on modifying the QuteCsound sources for this? I would prefer to have the releases synchronized and to know when someone says they are using 0.6.1 that they are using the same source code, so it would be great if we include that for the next release, but if possible, please use the 0.6.1 released source package to prepare your build. Alternatively, we could ask Andy to build the QuteCsound Windows package so that you can use those binaries. Also a thought on this idea. Some releases ago, I shipped a default file which was not blank, but which produced sound and showed some widgets in action. Although this was good for many beginners, it's actually a nuisance to regular users, so the system for the default file has actually changed and now instead of selecting a file, there is a text box where you enter the csd template you want to use (this idea was taken from WinXsound). I think the examples menu serves the beginners well enough in this respect. Cheers, Andres On Fri, Jan 21, 2011 at 2:47 AM, Michael Gogins |
Date | 2011-01-21 14:01 |
From | Michael Gogins |
Subject | Re: [Cs-dev] Windows build of Csound |
This is a bug reported to me personally by Judy Klein, who was trying to use very long segments in a piece (but it didn't work) and convincingly demonstrated it to me. I am going to fix it in CVS of course. In pseudocode, the bug is, for each segment of the envelope, for each sample frame: newgain = newgain + increment And the fix is: newgain = startgain + sample_frames_elapsed_in_segment * increment With the bug, during a long segment, rounding errors can cause the error in newgain to drift way out of bound, but with the fix, even in the longest segments the error in newgain remains strictly within a small bound. I used to re-tag such post-release changes, but what I do now is have my own set of tags for the Windows releases, which are mostly but not completely in sync with the Linux/OS X tags. What I suggest is that after all my and all anyone else's post-release fixes are in, we do a synchronized point release and remove the earlier versions from the files page. Regards, Mike On Fri, Jan 21, 2011 at 4:06 AM, |
Date | 2011-01-21 14:26 |
From | Victor Lazzarini |
Subject | Re: [Cs-dev] Windows build of Csound |
That is fine, but I would have preferred if we had synchronised all bug fixes just once before the 5.13, to save me having to re-do packages. Maybe we could have a go/no go system for release where all the package maintainers and main developers could agree on a single release date. Victor > What I suggest is that after all my and all anyone else's post-release > fixes are in, we do a synchronized point release and remove the > earlier versions from the files page. > > Regards, > Mike > > On Fri, Jan 21, 2011 at 4:06 AM, |
Date | 2011-01-21 16:07 |
From | Michael Gogins |
Subject | Re: [Cs-dev] Windows build of Csound |
A go/no go date is fine with me. But I think a better idea is a beta/final release system. I think the beta period should be long enough to actually work -- probably a couple of months. Regards, Mike On Fri, Jan 21, 2011 at 9:26 AM, Victor Lazzarini |
Date | 2011-01-23 11:16 |
From | john ffitch |
Subject | Re: [Cs-dev] Windows build of Csound |
> Maybe we could have a go/no go system for release where all the > package maintainers and main developers could agree on a single > release date. which is why I gave such a long lead time, with reminders...... ==John ffitch ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |