I am working on a new Windows installer for RC2. Should be ready in a few days. This will upgrade Python to 2.4.2, use latest libsndfile (1.0.13) and portaudio, and include all current CVS sources. I am changing the directory structure to mirror the Linux layout, as closely as possible. There will be 1 installer for 32 bit samples and 1 installer for 64 bit samples.

Yes, when fixes are made to CVS sources, such fixes should show up in new binaries built from CVS sources.

Regards,
Mike

-----Original Message-----
>From: Art Hunkins 
>Sent: Jan 3, 2006 11:31 AM
>To: csound@lists.bath.ac.uk
>Subject: Re: [Csnd] Quad Pan
>
>Thanks very much, Istvan.
>
>Two questions:
>
>1) When will this and other recent fixes be available in a Windows binary?
>
>2) As these fixes were, I gather, made to CVS sources, does this mean that
>the fixes will be available in other binaries whenever new binaries are
>built from these sources?
>
>(Pardon my ignorance on such matters.)
>
>Art Hunkins
>
>----- Original Message -----
>From: "Istvan Varga" 
>To: 
>Sent: Tuesday, January 03, 2006 10:05 AM
>Subject: Re: [Csnd] Quad Pan
>
>
>> Fixed.
>>
>> On Tuesday 03 January 2006 00:24, Art Hunkins wrote:
>>
>> > At any rate, I'd much appreciate some developer (johnff, istvan?) taking
>a
>> > look at ioffset in the pan code. It seems to me that in normalized mode,
>> > ioffset = 1 should simply add .5 to both kx and ky, thus centering the
>point
>> > of origin.
>> >
>> > (In raw index mode, ioffset = 1 would seemingly need to add .5 * maxval
>of
>> > kx and ky to these values. Or so I'm assuming.)
>> --
>> Send bugs reports to this list.
>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>
>-- 
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk