Steven,

Yes.

I am not a Blue user, and I write realtime compositions that I hope others 
will perform using just my .csd (or Lettuce .exe) and Csound (even a 
"stripped down" version, which I supply in a download .zip).

I do not know what kind of system the user will have. Right now if necessary 
the user edits  (under my instructions); or, in Lettuce, the 
performer has direct access to , also editing.

BTW, I use no .csoundrc - overriding anything necessary in .csoptions. In my 
"stripped down" Csound there are no environment variables either; everything 
is run from a single directory.

Do you see now how the proposal could help me?

Would you need to recode anything in Blue if the suggested change were made?

Art Hunkins

----- Original Message ----- 
From: "Steven Yi" 
To: 
Sent: Tuesday, August 18, 2009 1:16 PM
Subject: [Csnd] Re: Re: csoptions idea...


So can someone reply to my thread and tell me why it is a good idea to
add machine-dependent settings to a project?  It seems that it would
make project less portable, not more.

On Tue, Aug 18, 2009 at 12:50 PM, Dr. Richard
Boulanger wrote:
> that would work for me and be clear and intuitive... we still want to
> support all the smart defaulting you have already for sure.
>
> Rick
>
> On Aug 18, 2009, at 12:35 PM, jpff@cs.bath.ac.uk wrote:
>
>>> +1
>>>
>>> Art Hunkins
>>>
>>
>> Would tags like
>> 
>> 
>> -idac1
>> 
>> 
>> 
>> 
>> -+rtaudio=CoreAudio -odac
>> 
>> 
>>
>>
>> be acceptable? Or whatever is correct XML
>>
>>
>> Then one could still have a generic and over write in cases
>>
>> ==John ff
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
csound"= 



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I am one of those (perhaps a minority) who thought CsOptions was a bad 
idea from the get-go. The csd  file (a) has no business telling me what 
hardware to use and how, and (b) there is no way it can work reliably 
all the time on N unknown hosts. My audio hardware is not even fixed 
(apart from the mac internal audio which I only use as Plan B or C); 
they are mostly external Firewire or USB devices, but not quite enough 
to go around all the machines I have to deal with; so I move them around 
a lot.

Any time I have cause to play someone's csd file, I have learned simply 
to delete all the CsOptions; almost invariably whatever -b -B settings 
it has, don't work. It is for the user to set up the options that work 
for them, on ~their~ machine; Csound should not dictate that, and most 
definitely a csd file should not.

Richard Dobson



Art Hunkins wrote:
> Steven,
> 
> Yes.
> 
> I am not a Blue user, and I write realtime compositions that I hope 
> others will perform using just my .csd (or Lettuce .exe) and Csound 
> (even a "stripped down" version, which I supply in a download .zip).
> 
> I do not know what kind of system the user will have. Right now if 
> necessary the user edits  (under my instructions); or, in 
> Lettuce, the performer has direct access to , also editing.
> 
> BTW, I use no .csoundrc - overriding anything necessary in .csoptions. 
> In my "stripped down" Csound there are no environment variables either; 
> everything is run from a single directory.
> 



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"