Jim,

Here's my "chime in":

Thank your lucky stars you're not in Linux-land.

That's where I've been visiting for the last year, and am still not sure 
I'll find my way out. Yes, they do speak a different language.

But yes, those  are key. Do be aware of what options are *not* 
there, as well as what may be present in .csoundrc (if its location is 
correctly specified in your environment variables!). Offhand I don't 
remember whether  or .csoundrc take precedence. (It does say 
somewhere in the manual.)

Art Hunkins

----- Original Message ----- 
From: "Dave Phillips" 
To: 
Sent: Friday, July 31, 2009 2:38 PM
Subject: [Csnd] Re: Re: Re altime Audio Output Gargling


> Jim Aikin wrote:
>>   I wrote as simple a test file as I possibly
>> could -- no sensing the note number or velocity, nothing.
>>
>> The problem, however, is consistent across ALL .csd files, including
>> non-realtime files that are just supposed to be rendering a pre-written
>> score to the dac. So running this file won't tell you anything.
>>
>>
>>
> But it does. :)
>
>
>> 
>> 
>> -d -odac 1
>>
> I replaced your options with these for Linux with JACK :
>
>
>    csound -+rtaudio=jack -d -m0 -g -f -odac:system:playback_ -b128 --expression-opt 
> gargling.csd
>
> I added a specifier for the realtime output system (rtaudio) and I set 
> the -b buffer option to match the JACK period size. I don't know what 
> you'll do in Windows to get the same results, Michael or Art will have to 
> chime in.
>
> Btw, the complex -o definition provides autoconnection in JACK. -odac 
> alone will bring Csound into JACK but won't connect it to anything.
>
>> 
>> 
>>
>> sr = 44100
>> kr = 100
>> ksmps = 441
>>
> I commented out the kr line and changed ksmps to 64, again to match JACK 
> settings. If you're running an ASIO system you might have some similar 
> controls.
>
>> nchnls = 2
>> 0dbfs = 1.0
>>
>> git1    ftgen 1, 0, 8192, 10, 1
>>
>> instr 1
>> kdeclick    linsegr 0, 0.003, 1, 1, 1, 0.2, 0
>> asig        oscili  kdeclick, 220, 1
>>         outs    asig, asig
>> endin
>>
>> 
>>
> All good up to here.
>
>
>> 
>> f0 120
>> 
>> 
>>
>>
>
> I added an instrument instance:
>
> i1 0 10
>
> because there was no MIDI input option in your original CsOptions. If I 
> want MIDI input control I add these options :
>
>    -+rtmidi=alsa -Mhw:2,0
>
> The arcane syntax for the -M option represents the third device on my 
> system. Sorry, it's ALSA-speak. Again, I'm not sure what the similar 
> invocation will be for Windows Csound.
>
> I tested it with a virtual MIDI keyboard, it worked fine. It also works 
> fine with just the i1 statement (i.e. without the f0 line).
>
> I know that the Linux way may not help you directly, but my tests showed 
> that your instrument works fine. I think your CsOptions needs some further 
> attention. hopefully a Windows user can help out from  here.
>
> Best,
>
> dp
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"