Hello everyone,

I'm collecting command-line arguments for Csoundo, as one of the
issues that has popped up is that what works for one system doesn't
necessarily work for someone else's. Which is to be expected. For
example, "-g -odac" works for me, but I'm not sure if it works for
everyone. So I'm looking for the most generic set of options that will
work for as many systems as possible. Any suggestions?

I'm also looking for specific arguments that will work for different
OSs. What works best with OS X? Windows? Linux?

I'm also happy to hear what individuals are using for their own custom setups.

Eventually, I want to create a Processing sketch utility that will
help users create a set of command-line arguments, and store those in
a CSOUND_CONFIG.txt file. The idea is that users could configure once,
with the aid of software, then most sketches would work from that
point forward without any further tinkering.

And thanks everyone who has sent me bug reports. Csoundo has been
downloaded a total of 138 times in 8 days, far exceeding my
expectations for this highly unstable alpha release. Thanks!

Best,
Jake

-odac should work everywhere. At least in my experience running Csound  
on Linux, Windows and OSX. However, it might not be in any given OS,  
the best audio device, for instance (ie. someone might have their best  
card on dac2 etc.).

The main question regarding RT audio, for instance, in different  
systems is buffer size and latency. On OSX, buffer sizes can be quite  
small (-b64.-B128) and it seems to work with whatever device. On  
Linux, it might depend on the soundcard and the kernel version (also  
if it is an RT-patched kernel), some soundcards allowing smaller  
buffers, others not. On Windows, current portaudio will give low  
latency only with ASIO, as other Windows APIs are just rubbish (maybe  
the new WASAPI code will be an alternative on Windows 7, but I will  
not be the one to try it). And finally, Linux has the --sched option  
to set up realtime scheduling (but this is restricted to the csound  
command, so it should not matter to you).

In my experience, other command-line options are generally working and  
the same across the board.

Regards
Victor

On 16 Aug 2010, at 21:35, Jacob Joaquin wrote:

> Hello everyone,
>
> I'm collecting command-line arguments for Csoundo, as one of the
> issues that has popped up is that what works for one system doesn't
> necessarily work for someone else's. Which is to be expected. For
> example, "-g -odac" works for me, but I'm not sure if it works for
> everyone. So I'm looking for the most generic set of options that will
> work for as many systems as possible. Any suggestions?
>
> I'm also looking for specific arguments that will work for different
> OSs. What works best with OS X? Windows? Linux?
>
> I'm also happy to hear what individuals are using for their own  
> custom setups.
>
> Eventually, I want to create a Processing sketch utility that will
> help users create a set of command-line arguments, and store those in
> a CSOUND_CONFIG.txt file. The idea is that users could configure once,
> with the aid of software, then most sketches would work from that
> point forward without any further tinkering.
>
> And thanks everyone who has sent me bug reports. Csoundo has been
> downloaded a total of 138 times in 8 days, far exceeding my
> expectations for this highly unstable alpha release. Thanks!
>
> Best,
> Jake
> -- 
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Mon, Aug 16, 2010 at 1:54 PM, Victor Lazzarini
 wrote:
> In my experience, other command-line options are generally working and the
> same across the board.

This is certainly great news, as it should make things easier. For me
and end users. I'll tackle the buffer size issue down the road for
now, but will make a note of it.

Best,
Jake