Thanks for the reply - I will check out that new release.
I think I've found my issue:
when I do rtoutput, I use the -odacx cmd-line option, where x is the
device number listed when I do -odac99. For rtinput, I've been
using -idevaudiox, where x is the number for my M-Audio's ASIO
driver. I see now that this is wrong - I grep'd through old
csound list postings, looking for anything related, and saw an
unrelated example using -iadcx, and now see it in the canonical manual,
somewhat buried IMO within notes on using Jack with csound in RT.
This is a bit confusing,on the surface, but I supposed it makes sense
if I think about what the acronym stands for ;) (dac/adc). What's
the difference between the devaudio and dac/adc options?
My 2 cents: It would be helpful for dac, adc and devaudio to be
mentioned in the cmd-line options at runtime (i.e. when I type 'csound'
with no args at the cmdline).
Thanks for the help - Ben
On 1/3/06, Istvan Varga <istvan_v@fibermail.hu> wrote:
On Tuesday 03 January 2006 19:17, Ben McAllister wrote:
> What is the expected behavior of realtime input for the 12/13 build of
> csound5? I'm running a 2.4gHz Win2k pc with 1.5 G Ram, M-Audio 1010LT
> soundcard. Using the in, ins, and inch ugens, I'm getting ~300ms delay with
> the ASIO drivers included with my card at sr=44100 (this even with kr=441).
Make sure that you are using an ASIO input device, and not MME
(which is usually the default) or DirectSound.
By the way, there is a new version (RC2) on SourceForge, although
this is not related to your problem, and it is likely that new
releases will be available soon again.
--
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk