I will upload the Windows installers after I have selected which 
configuration (float or double) I will support. This will take some 
performance timing and ABX listening tests.

I am writing one orchestra to do both tests, I should be able to do this 
today or tomorrow.

I will continue to maintain our ability to build both configurations on 
Windows, but I will not package and release both configurations.

Regards,
Mike
----- Original Message ----- 
From: "Victor Lazzarini" 
To: "Developer discussions" 
Sent: Thursday, September 24, 2009 7:58 AM
Subject: [Cs-dev] release


>
> The new SF release interface is confusing. Where do release notes go?
> I have
> uploaded the OSX 10.5 package, will work now on OSX 10.4.
> Is this release live already?
>
> Victor
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register 
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Just to register my vote for the double version.  Even with realtime, 
I've never had a need to use the other, and it's worth it for the 
quality (IMHO).

- Dave

michael.gogins@gmail.com wrote:
> I will upload the Windows installers after I have selected which 
> configuration (float or double) I will support. This will take some 
> performance timing and ABX listening tests.
> 
> I am writing one orchestra to do both tests, I should be able to do this 
> today or tomorrow.
> 
> I will continue to maintain our ability to build both configurations on 
> Windows, but I will not package and release both configurations.
> 
> Regards,
> Mike



------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'd vote doubles too.

please advise when the new windows installer is available for download.

thanks to everybody. im looking forward to re-acquainting myself with csound
with this release. largely due to the ctrl C problem being fixed, trivially
enough....



Dave Seidel wrote:
> 
> Just to register my vote for the double version.  Even with realtime, 
> I've never had a need to use the other, and it's worth it for the 
> quality (IMHO).
> 
> - Dave
> 
> 
> 


-----
http://www.timmortimer.net


-- 
View this message in context: http://www.nabble.com/Another-serious-problem-in-5.11-tp25591670p25620972.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Just a note re: OSX releases. These now incorporate both
floats and doubles. The command linked to doubles is called.
csound64.

Victor

----- Original Message ----- 
From: "Dave Seidel" 
To: "Developer discussions" 
Sent: Saturday, September 26, 2009 1:01 AM
Subject: Re: [Cs-dev] release


> Just to register my vote for the double version.  Even with realtime,
> I've never had a need to use the other, and it's worth it for the
> quality (IMHO).
>
> - Dave
>
> michael.gogins@gmail.com wrote:
>> I will upload the Windows installers after I have selected which
>> configuration (float or double) I will support. This will take some
>> performance timing and ABX listening tests.
>>
>> I am writing one orchestra to do both tests, I should be able to do this
>> today or tomorrow.
>>
>> I will continue to maintain our ability to build both configurations on
>> Windows, but I will not package and release both configurations.
>>
>> Regards,
>> Mike
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register 
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

When will the source release be ready (as in, not changing anymore)?
So I can update the debian package.
The qutecsound version that will be in the windows instaler for this
release is 0.4.2?

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> When will the source release be ready (as in, not changing anymore)?
> So I can update the debian package.

Last Friday -- we have not announced as we are waiting for Windows.  The
files are tagged in CVS as well

==John ff


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I should probably update qutecsound as I believe you announced a fix
for something a week or so ago.

Regards,
Mike

On 9/27/09, jpff@cs.bath.ac.uk  wrote:
>> When will the source release be ready (as in, not changing anymore)?
>> So I can update the debian package.
>
> Last Friday -- we have not announced as we are waiting for Windows.  The
> files are tagged in CVS as well
>
> ==John ff
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> 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

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I did say there was a serious problem in Engine/fgens.c but that was
fixed before the .zip and tgx source files were placed on SF.  I am
not aware of any change since the files were upload.  Also the CVS is
tagged with csound5.11 for the version released. 
==John ffitch

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Does anyone volunteer for updating csound.sourceforge.net before the
official release announcement? I am not sure I have the correct skills.

Victor


On 28 Sep 2009, at 14:21, jpff wrote:

> I did say there was a serious problem in Engine/fgens.c but that was
> fixed before the .zip and tgx source files were placed on SF.  I am
> not aware of any change since the files were upload.  Also the CVS is
> tagged with csound5.11 for the version released.
> ==John ffitch
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Some links to the various frontends would be nice too. It looks very good.

2009/9/29 Andy Fillebrown :
>
>
> I received some good input from Dr.B regarding updating the content at
> http://csound.sourceforge.net so I went ahead and made a bunch of changes
> this morning.  Again, though, if anybody else has input regarding what
> should be on the page, please let me know and I will try to get to it before
> the new release is announced.
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Andy Fillebrown" 
> To: "Developer discussions" 
> Sent: Tuesday, September 29, 2009 3:29:04 AM (GMT-0500) America/New_York
> Subject: Re: [Cs-dev] csound.sf.net page
>
>
> I uploaded the new http://csound.sourceforge.net index.html and faq.html
> I've been working on.
>
> There are only a few issues I wasn't able to resolve:
> - The Windows, OpenSUSE, and Mac OS X download sections need updated links
> to 5.11 installers (I'm not sure which installer goes with each link)
> - The Csound Wiki link is dead (maybe it moved?)
>
> Other than that it should be good to go but proof-reading and link-checking
> would be appreciated.
> Also, if anybody has access to old browsers I'd appreciate it if they could
> be used to test it, too, especially the old Internet Explorer browsers.
>
> The original pages can be found at
> http://csound.sourceforge.net/old_index.html and
> http://csound.sourceforge.net/old_faq.html
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Andy Fillebrown" 
> To: "Developer discussions" 
> Sent: Monday, September 28, 2009 10:13:54 AM (GMT-0500) America/New_York
> Subject: Re: [Cs-dev] csound.sf.net page
>
>
>
> I had volunteered to do this back in July/August but I got pulled away until
> a few weeks ago.  I'm almost done now, though, with only a few hours more of
> work to do on the first draft.  I'm hoping to upload it tonight.  I have not
> yet updated it for the new release and I have some questions about the more
> dated material which I will post when I have a full list put together.
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Victor Lazzarini" 
> To: "Developer discussions" 
> Sent: Monday, September 28, 2009 10:03:22 AM (GMT-0500) America/New_York
> Subject: [Cs-dev] csound.sf.net page
>
> Does anyone volunteer for updating csound.sourceforge.net before the
> official release announcement? I am not sure I have the correct skills.
>
> Victor
>
>
> On 28 Sep 2009, at 14:21, jpff wrote:
>
>> I did say there was a serious problem in Engine/fgens.c but that was
>> fixed before the .zip and tgx source files were placed on SF.  I am
>> not aware of any change since the files were upload.  Also the CVS is
>> tagged with csound5.11 for the version released.
>> ==John ffitch
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I just want to say that this is looking really nice!  Looks and feels
more professional already.

Best,
Jake


On Tue, Sep 29, 2009 at 9:23 AM, Andy Fillebrown
 wrote:
>
>
> I received some good input from Dr.B regarding updating the content at
> http://csound.sourceforge.net so I went ahead and made a bunch of changes
> this morning.  Again, though, if anybody else has input regarding what
> should be on the page, please let me know and I will try to get to it before
> the new release is announced.
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Andy Fillebrown" 
> To: "Developer discussions" 
> Sent: Tuesday, September 29, 2009 3:29:04 AM (GMT-0500) America/New_York
> Subject: Re: [Cs-dev] csound.sf.net page
>
>
> I uploaded the new http://csound.sourceforge.net index.html and faq.html
> I've been working on.
>
> There are only a few issues I wasn't able to resolve:
> - The Windows, OpenSUSE, and Mac OS X download sections need updated links
> to 5.11 installers (I'm not sure which installer goes with each link)
> - The Csound Wiki link is dead (maybe it moved?)
>
> Other than that it should be good to go but proof-reading and link-checking
> would be appreciated.
> Also, if anybody has access to old browsers I'd appreciate it if they could
> be used to test it, too, especially the old Internet Explorer browsers.
>
> The original pages can be found at
> http://csound.sourceforge.net/old_index.html and
> http://csound.sourceforge.net/old_faq.html
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Andy Fillebrown" 
> To: "Developer discussions" 
> Sent: Monday, September 28, 2009 10:13:54 AM (GMT-0500) America/New_York
> Subject: Re: [Cs-dev] csound.sf.net page
>
>
>
> I had volunteered to do this back in July/August but I got pulled away until
> a few weeks ago.  I'm almost done now, though, with only a few hours more of
> work to do on the first draft.  I'm hoping to upload it tonight.  I have not
> yet updated it for the new release and I have some questions about the more
> dated material which I will post when I have a full list put together.
>
> Cheers,
> ~ andy.f
>
>
>
> ----- Original Message -----
> From: "Victor Lazzarini" 
> To: "Developer discussions" 
> Sent: Monday, September 28, 2009 10:03:22 AM (GMT-0500) America/New_York
> Subject: [Cs-dev] csound.sf.net page
>
> Does anyone volunteer for updating csound.sourceforge.net before the
> official release announcement? I am not sure I have the correct skills.
>
> Victor
>
>
> On 28 Sep 2009, at 14:21, jpff wrote:
>
>> I did say there was a serious problem in Engine/fgens.c but that was
>> fixed before the .zip and tgx source files were placed on SF.  I am
>> not aware of any change since the files were upload.  Also the CVS is
>> tagged with csound5.11 for the version released.
>> ==John ffitch
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listi

If you want,  I can host some of the other frontends at csounds.com  
and we can link to them there.  Or.  Developers might send Andy links  
to add.  Definitely want a link on the side to Blue and Stefanne's

-dB

Sent from my iPhone

On Sep 29, 2009, at 12:33 PM, Rory Walsh  wrote:

> Some links to the various frontends would be nice too. It looks very  
> good.
>
> 2009/9/29 Andy Fillebrown :
>>
>>
>> I received some good input from Dr.B regarding updating the content  
>> at
>> http://csound.sourceforge.net so I went ahead and made a bunch of  
>> changes
>> this morning.  Again, though, if anybody else has input regarding  
>> what
>> should be on the page, please let me know and I will try to get to  
>> it before
>> the new release is announced.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>> ----- Original Message -----
>> From: "Andy Fillebrown" 
>> To: "Developer discussions" 
>> Sent: Tuesday, September 29, 2009 3:29:04 AM (GMT-0500) America/ 
>> New_York
>> Subject: Re: [Cs-dev] csound.sf.net page
>>
>>
>> I uploaded the new http://csound.sourceforge.net index.html and  
>> faq.html
>> I've been working on.
>>
>> There are only a few issues I wasn't able to resolve:
>> - The Windows, OpenSUSE, and Mac OS X download sections need  
>> updated links
>> to 5.11 installers (I'm not sure which installer goes with each link)
>> - The Csound Wiki link is dead (maybe it moved?)
>>
>> Other than that it should be good to go but proof-reading and link- 
>> checking
>> would be appreciated.
>> Also, if anybody has access to old browsers I'd appreciate it if  
>> they could
>> be used to test it, too, especially the old Internet Explorer  
>> browsers.
>>
>> The original pages can be found at
>> http://csound.sourceforge.net/old_index.html and
>> http://csound.sourceforge.net/old_faq.html
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>> ----- Original Message -----
>> From: "Andy Fillebrown" 
>> To: "Developer discussions" 
>> Sent: Monday, September 28, 2009 10:13:54 AM (GMT-0500) America/ 
>> New_York
>> Subject: Re: [Cs-dev] csound.sf.net page
>>
>>
>>
>> I had volunteered to do this back in July/August but I got pulled  
>> away until
>> a few weeks ago.  I'm almost done now, though, with only a few  
>> hours more of
>> work to do on the first draft.  I'm hoping to upload it tonight.  I  
>> have not
>> yet updated it for the new release and I have some questions about  
>> the more
>> dated material which I will post when I have a full list put  
>> together.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>> ----- Original Message -----
>> From: "Victor Lazzarini" 
>> To: "Developer discussions" 
>> Sent: Monday, September 28, 2009 10:03:22 AM (GMT-0500) America/ 
>> New_York
>> Subject: [Cs-dev] csound.sf.net page
>>
>> Does anyone volunteer for updating csound.sourceforge.net before the
>> official release announcement? I am not sure I have the correct  
>> skills.
>>
>> Victor
>>
>>
>> On 28 Sep 2009, at 14:21, jpff wrote:
>>
>>> I did say there was a serious problem in Engine/fgens.c but that was
>>> fixed before the .zip and tgx source files were placed on SF.  I am
>>> not aware of any change since the files were upload.  Also the CVS  
>>> is
>>> tagged with csound5.11 for the version released.
>>> ==John ffitch
>>>
>>>
>>> --- 
>>> --- 
>>> --- 
>>> --- 
>>> ------------------------------------------------------------------
>>> Come build with us! The BlackBerry® Developer Conference in  
>>> SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9-12, 2009. Register
>>> now!
>>> http://p.sf.net/sfu/devconf
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> --- 
>> --- 
>> --- 
>> ---------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF,  
>> CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register  
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> --- 
>> --- 
>> --- 
>> ---------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF,  
>> CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register  
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:
> Excellent.
Ditto. Nicely done, Andy, thank you for your work.

Best,

dp




------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I thought it was high time I tried this out, with the latest release 
(5.11 floats, OS X 10.5 intel):

It all looks very nice so far, but when I render to a soundfile, it 
appends lots of spurious stuff to the name (looks  a bit like parts of a 
file diaog filter string), so a file to be called test.wav becomes:

test.wav.wav;*.wavex (unknown)

And of course only OSX is daft enough to allow the star character (etc) 
as part of a filename.

Ostensibly this is a bug; unless there is some non-obvious thing I am 
doing wrong.

??

Richard Dobson


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Not sure, how does this happen? If I add -omyfile.aif to csoptions, I  
get myfile.aif
when I 'render to file'.


Victor


On 30 Sep 2009, at 14:11, Richard Dobson wrote:

> I thought it was high time I tried this out, with the latest release
> (5.11 floats, OS X 10.5 intel):
>
> It all looks very nice so far, but when I render to a soundfile, it
> appends lots of spurious stuff to the name (looks  a bit like parts  
> of a
> file diaog filter string), so a file to be called test.wav becomes:
>
> test.wav.wav;*.wavex (unknown)
>
> And of course only OSX is daft enough to allow the star character  
> (etc)
> as part of a filename.
>
> Ostensibly this is a bug; unless there is some non-obvious thing I am
> doing wrong.
>
> ??
>
> Richard Dobson
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

and when I press record I get a new soundfile with a name based on my  
CSD name.

Victor
On 30 Sep 2009, at 14:19, Victor Lazzarini wrote:

> Not sure, how does this happen? If I add -omyfile.aif to csoptions, I
> get myfile.aif
> when I 'render to file'.
>
>
> Victor
>
>
> On 30 Sep 2009, at 14:11, Richard Dobson wrote:
>
>> I thought it was high time I tried this out, with the latest release
>> (5.11 floats, OS X 10.5 intel):
>>
>> It all looks very nice so far, but when I render to a soundfile, it
>> appends lots of spurious stuff to the name (looks  a bit like parts
>> of a
>> file diaog filter string), so a file to be called test.wav becomes:
>>
>> test.wav.wav;*.wavex (unknown)
>>
>> And of course only OSX is daft enough to allow the star character
>> (etc)
>> as part of a filename.
>>
>> Ostensibly this is a bug; unless there is some non-obvious thing I am
>> doing wrong.
>>
>> ??
>>
>> Richard Dobson
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF,  
>> CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:
> Not sure, how does this happen? If I add -omyfile.aif to csoptions, I 
> get myfile.aif
> when I 'render to file'.
> 

I can't believe it is really recommended to set an output file name by 
changing CsOptions each time! When I click on Render (to file) I get a 
file dialog "Output Filename". The file type filter dropdown only has 
one entry,"WAVE(wavex) Files (*.wav; *.wavex)".

On investigating further, I see in the Configuration dalog (via
"Preferences"), that the anomalous output filename is written into that. 
Fine to preserve the outfile name between runs, but it seems odd to me 
to have a entry box for it in a Config panel. In this dialog  "Use 
QuteCsound options is checked, also "Ask for filename every time". This 
dialog also offers a File type dropdown, where I have "WAVE (wavex)" 
selected.

All of which means that the file name and format settings are 
variable/settable (and somehow interact) from two places. If 
"Configuration" is the primary centre of control, the file name selected 
there should really appear as the default choice in the Render dialog; 
so that when you save a file, your default choices are visible 
automatically, but changeable (without having to modify the csd). And 
really the full set of file format option s needs to be selectable in 
the File Save dialog; as it happens I mostly use Csound for generating 
test files for this and that (rather than composition), and outputting 
to different file (and sample) formats is one of the things I do a lot!

Maybe I am simply not that used to GUIs, but QuteCsound is not yet 
converting me from running csound from the command line.


Richard Dobson



------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

This is clearly a bug, and it has been fixed, thanks. I hadn't spotted
it since I don't use wavex... A lot more eyes on QuteCsound now...

Cheers,
Andres

On Wed, Sep 30, 2009 at 2:11 PM, Richard Dobson
 wrote:
> I thought it was high time I tried this out, with the latest release
> (5.11 floats, OS X 10.5 intel):
>
> It all looks very nice so far, but when I render to a soundfile, it
> appends lots of spurious stuff to the name (looks  a bit like parts of a
> file diaog filter string), so a file to be called test.wav becomes:
>
> test.wav.wav;*.wavex (unknown)
>
> And of course only OSX is daft enough to allow the star character (etc)
> as part of a filename.
>
> Ostensibly this is a bug; unless there is some non-obvious thing I am
> doing wrong.
>
> ??
>
> Richard Dobson
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

QuteCsound gives you the option of either setting the output file in
CsOptions or setting it in the configuration dialog. The configuration
dialog doesn't load any info from particular csds as I feel this is
kind of strange. It would feel odd if opening a file changes your
settings without at least letting you know. So my solution has been to
offer an ask everytime checkbox, which of course... asks every time.
I've just improved this, by making the dialog auto select the previous
file if the outputFile checkbox is checked. If it's not, it will go to
the previously used directory.

Its true that its somewhat awkward to be able to specify options in
two separate places, but I got there because some people prefer using
the configuration menu, while others prefer to have their options on
the csd file itself, so I wanted to provide both possibilities. It can
of course cause trouble if you are using both, but that's what the
"Use QuteCsound Options" and "Ignore CsOptions" checkbox are for. I've
left both options enabled by default, as I think it will prevent
beginners from having troubles.

Thanks for your comments.

Cheers,
Andres

On Wed, Sep 30, 2009 at 3:42 PM, Richard Dobson
 wrote:
> Victor Lazzarini wrote:
>> Not sure, how does this happen? If I add -omyfile.aif to csoptions, I
>> get myfile.aif
>> when I 'render to file'.
>>
>
> I can't believe it is really recommended to set an output file name by
> changing CsOptions each time! When I click on Render (to file) I get a
> file dialog "Output Filename". The file type filter dropdown only has
> one entry,"WAVE(wavex) Files (*.wav; *.wavex)".
>
> On investigating further, I see in the Configuration dalog (via
> "Preferences"), that the anomalous output filename is written into that.
> Fine to preserve the outfile name between runs, but it seems odd to me
> to have a entry box for it in a Config panel. In this dialog  "Use
> QuteCsound options is checked, also "Ask for filename every time". This
> dialog also offers a File type dropdown, where I have "WAVE (wavex)"
> selected.
>
> All of which means that the file name and format settings are
> variable/settable (and somehow interact) from two places. If
> "Configuration" is the primary centre of control, the file name selected
> there should really appear as the default choice in the Render dialog;
> so that when you save a file, your default choices are visible
> automatically, but changeable (without having to modify the csd). And
> really the full set of file format option s needs to be selectable in
> the File Save dialog; as it happens I mostly use Csound for generating
> test files for this and that (rather than composition), and outputting
> to different file (and sample) formats is one of the things I do a lot!
>
> Maybe I am simply not that used to GUIs, but QuteCsound is not yet
> converting me from running csound from the command line.
>
>
> Richard Dobson
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

While you are at i, Andres, could you check why SFDIR does not seem
to be used? If I set in the configuration dialog and then add a '-o 
whatever'
the whatever still ends up in the QuteCsound directory (ie Applications).

Btw, I'm using qutecsound in my Monday class to give the students the
'wow' factor with all the scope and other gadgets (then I will go back to
the command-line... ;). The examples you supply are good. I particularly
like the Phase Mod synth, it's very nice (well I am a fan of all things FM).

Thanks for this nice piece of software.

Victor



----- Original Message ----- 
From: "Andres Cabrera" 
To: ; "Developer discussions" 

Sent: Friday, October 02, 2009 8:39 AM
Subject: Re: [Cs-dev] Qutecsound (or csound) bug with output filename?


Hi,

QuteCsound gives you the option of either setting the output file in
CsOptions or setting it in the configuration dialog. The configuration
dialog doesn't load any info from particular csds as I feel this is
kind of strange. It would feel odd if opening a file changes your
settings without at least letting you know. So my solution has been to
offer an ask everytime checkbox, which of course... asks every time.
I've just improved this, by making the dialog auto select the previous
file if the outputFile checkbox is checked. If it's not, it will go to
the previously used directory.

Its true that its somewhat awkward to be able to specify options in
two separate places, but I got there because some people prefer using
the configuration menu, while others prefer to have their options on
the csd file itself, so I wanted to provide both possibilities. It can
of course cause trouble if you are using both, but that's what the
"Use QuteCsound Options" and "Ignore CsOptions" checkbox are for. I've
left both options enabled by default, as I think it will prevent
beginners from having troubles.

Thanks for your comments.

Cheers,
Andres

On Wed, Sep 30, 2009 at 3:42 PM, Richard Dobson
 wrote:
> Victor Lazzarini wrote:
>> Not sure, how does this happen? If I add -omyfile.aif to csoptions, I
>> get myfile.aif
>> when I 'render to file'.
>>
>
> I can't believe it is really recommended to set an output file name by
> changing CsOptions each time! When I click on Render (to file) I get a
> file dialog "Output Filename". The file type filter dropdown only has
> one entry,"WAVE(wavex) Files (*.wav; *.wavex)".
>
> On investigating further, I see in the Configuration dalog (via
> "Preferences"), that the anomalous output filename is written into that.
> Fine to preserve the outfile name between runs, but it seems odd to me
> to have a entry box for it in a Config panel. In this dialog "Use
> QuteCsound options is checked, also "Ask for filename every time". This
> dialog also offers a File type dropdown, where I have "WAVE (wavex)"
> selected.
>
> All of which means that the file name and format settings are
> variable/settable (and somehow interact) from two places. If
> "Configuration" is the primary centre of control, the file name selected
> there should really appear as the default choice in the Render dialog;
> so that when you save a file, your default choices are visible
> automatically, but changeable (without having to modify the csd). And
> really the full set of file format option s needs to be selectable in
> the File Save dialog; as it happens I mostly use Csound for generating
> test files for this and that (rather than composition), and outputting
> to different file (and sample) formats is one of the things I do a lot!
>
> Maybe I am simply not that used to GUIs, but QuteCsound is not yet
> converting me from running csound from the command line.
>
>
> Richard Dobson
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register 
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

Forgot to mention but that's fixed too. I was adding these to the script
for run in term, so they would have no effect when using the API. Now
I'm passing them usinf the --env flag, and they are working.

Cheers,
Andres

El vie, 02-10-2009 a las 09:15 +0100, victor escribió:
> While you are at i, Andres, could you check why SFDIR does not seem
> to be used? If I set in the configuration dialog and then add a '-o 
> whatever'
> the whatever still ends up in the QuteCsound directory (ie Applications).
> 
> Btw, I'm using qutecsound in my Monday class to give the students the
> 'wow' factor with all the scope and other gadgets (then I will go back to
> the command-line... ;). The examples you supply are good. I particularly
> like the Phase Mod synth, it's very nice (well I am a fan of all things FM).
> 
> Thanks for this nice piece of software.
> 
> Victor
> 
> 
> 
> ----- Original Message ----- 
> From: "Andres Cabrera" 
> To: ; "Developer discussions" 
> 
> Sent: Friday, October 02, 2009 8:39 AM
> Subject: Re: [Cs-dev] Qutecsound (or csound) bug with output filename?
> 
> 
> Hi,
> 
> QuteCsound gives you the option of either setting the output file in
> CsOptions or setting it in the configuration dialog. The configuration
> dialog doesn't load any info from particular csds as I feel this is
> kind of strange. It would feel odd if opening a file changes your
> settings without at least letting you know. So my solution has been to
> offer an ask everytime checkbox, which of course... asks every time.
> I've just improved this, by making the dialog auto select the previous
> file if the outputFile checkbox is checked. If it's not, it will go to
> the previously used directory.
> 
> Its true that its somewhat awkward to be able to specify options in
> two separate places, but I got there because some people prefer using
> the configuration menu, while others prefer to have their options on
> the csd file itself, so I wanted to provide both possibilities. It can
> of course cause trouble if you are using both, but that's what the
> "Use QuteCsound Options" and "Ignore CsOptions" checkbox are for. I've
> left both options enabled by default, as I think it will prevent
> beginners from having troubles.
> 
> Thanks for your comments.
> 
> Cheers,
> Andres
> 
> On Wed, Sep 30, 2009 at 3:42 PM, Richard Dobson
>  wrote:
> > Victor Lazzarini wrote:
> >> Not sure, how does this happen? If I add -omyfile.aif to csoptions, I
> >> get myfile.aif
> >> when I 'render to file'.
> >>
> >
> > I can't believe it is really recommended to set an output file name by
> > changing CsOptions each time! When I click on Render (to file) I get a
> > file dialog "Output Filename". The file type filter dropdown only has
> > one entry,"WAVE(wavex) Files (*.wav; *.wavex)".
> >
> > On investigating further, I see in the Configuration dalog (via
> > "Preferences"), that the anomalous output filename is written into that.
> > Fine to preserve the outfile name between runs, but it seems odd to me
> > to have a entry box for it in a Config panel. In this dialog "Use
> > QuteCsound options is checked, also "Ask for filename every time". This
> > dialog also offers a File type dropdown, where I have "WAVE (wavex)"
> > selected.
> >
> > All of which means that the file name and format settings are
> > variable/settable (and somehow interact) from two places. If
> > "Configuration" is the primary centre of control, the file name selected
> > there should really appear as the default choice in the Render dialog;
> > so that when you save a file, your default choices are visible
> > automatically, but changeable (without having to modify the csd). And
> > really the full set of file format option s needs to be selectable in
> > the File Save dialog; as it happens I mostly use Csound for generating
> > test files for this and that (rather than composition), and outputting
> > to different file (and sample) formats is one of the things I do a lot!
> >
> > Maybe I am simply not that used to GUIs, but QuteCsound is not yet
> > converting me from running csound from the command line.
> >
> >
> > Richard Dobson
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry® Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9-12, 2009. Register 
> > now!
> > http://p.sf.net/sfu/devconf
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> 
> 
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-de