Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:5216] Re: New Csound5 File release for MinGW with ASIO

Date2004-08-15 16:58
From"gogins@pipeline.com"
Subject[CSOUND-DEV:5216] Re: New Csound5 File release for MinGW with ASIO
AttachmentsSchedkwhen.csd  
There are two problems. One is my fault, and one is your fault.

Your problem is that you did not follow the advice in csound.pdf for ASIO.
I have amended your csd to use a command line similar to the example in
csound.pdf. The amended csd works for me (attached).

It may also be a problem that your .csd calls for a very low latency of
half a millisecond (though that does work on my very fast Windows XP
notebook with an M-Audio driver).

And it may also be a problem that your driver has 4 in 10 out, but you have
a mono csd. But my driver has 2 in and 2 out, yet it handles your csd OK,
so your csd should work for you, I guess.

My problem is that the advice in csound.pdf is not quite correct. The
example command line is correct and does work, but the text is not quite
correct. I should have said that BOTH the -B AND the -b options must match
ksmps, not just the -b option. I have fixed up csound.pdf in CVS.

This brings us back to the question of getting rid of the intermediate
audio buffers (controlled by the -b option) in Csound 5, which I would like
to do. I need to hear from John ffitch about this.

Original Message:
-----------------
From: Art Hunkins abhunkin@uncg.edu
Date: Sat, 14 Aug 2004 23:25:28 -0400
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5215] Re: New Csound5 File release for MinGW with ASIO


Hi, Michael,

I ran the attached simple file with the new CS5 file release; its failed
output messages are recorded below.

This is the output without the suggested "-b10" (=ksmps) included in the
command line. With "-b10" added, the output is the same except that
maxlag=10 and anticipated latency, of course, only a small fraction of a
second.

Csound5 is finding only one installed driver, ASIO, which it seems to be
identifying as device 0. This is why I specify
-odac0 as a CS option.

What have I done wrong?

Art Hunkins

C:\Csound5>csound schedkwhen.csd
Using default language
0dBFS level = 32767.0
Csound version 5.00 beta (double samples) Aug 12 2004
libsndfile-1.0.10pre6
UnifiedCSD:  schedkwhen.csd
STARTING FILE
Creating options
Creating orchestra
Creating C:\WINDOWS\TEMP\cs2.orc (7803BC10)
Creating score
orchname:  C:\WINDOWS\TEMP\cs2.orc
scorename: C:\WINDOWS\TEMP\cs3.sco
orch compiler:
36 lines read
        instr   1
        instr   2
sorting score ...
        ... done
Csound version 5.00 beta (double samples) Aug 12 2004
0dBFS level = 32767.0
orch now loaded
audio buffered in 16384 sample-frame blocks
Found 1 PortAudio devices:
Device  0: ASIO Echo Gina/Darla/Layla
           Maximum channels in:       4
           Maximum channels out:     10
           Default sample rate:   44100.000
Suggested PortAudio output latency = 0.743039 seconds.
paBlockingWriteOpen: nchnls 1 sr 22050.000000 maxLag 16384 device 0
paBlockingWriteOpen returned -9999.
PortAudio error -9999: Unanticipated host error.
Unable to open PortAudio output device.
inactive allocs returned to freespace
end of score.              overall amps:      0.0
           overall samples out of range:        0
0 errors in performance
Removing temporary file C:\WINDOWS\TEMP\cs4 ...
Removing temporary file C:\WINDOWS\TEMP\cs3.sco ...
Removing temporary file C:\WINDOWS\TEMP\cs2.orc ...

----- Original Message -----
From: 
To: "Csound Developers Discussion List" 
Sent: Saturday, August 14, 2004 3:33 PM
Subject: [CSOUND-DEV:5213] New Csound5 File release for MinGW with ASIO


I have uploaded a new zip file for Csound 5 and CsoundVST with prebuilt
binaries for Windows compiled with MinGW, and sources for all platforms, to
SourceForge at:

    http://sourceforge.net/projects/csound

Changes in this release:

-- The PortAudio driver now uses ASIO with a blocking wrapper to perform
   low-latency audio input and output on Windows. Output latency as little
   as 3 milliseconds was tested on Windows XP. Input has not been tested!

-- The csound.pdf file has been updated regarding ASIO. Read this BEFORE
   you try using real-time audio!

-- The csound.pdf file's sections have been re-ordered to make it easier
   for beginners to get started with Csound 5.






--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


Date2004-08-15 17:50
FromRichard Dobson
Subject[CSOUND-DEV:5217] Re: New Csound5 File release for MinGW with ASIO
I wonder if this is a good time to reassert that if csd files are meant to be 
portable, highly machine-dependent settings such as buffer sizes and device 
numbesr do not belong in them. Such things should be set by the user of a given 
version of Csound on their particular platform, for use with their particular 
hardware. Some things just have to be supplied from outside. Sensitive (and 
especially, extreme) settings can be guaranteed to render a csd file 
non-portable, or at least non-playable.

Of course, if a csd was never intended to be portable, it doesn't matter!


Richard Dobson



gogins@pipeline.com wrote:
> There are two problems. One is my fault, and one is your fault.
> 
> Your problem is that you did not follow the advice in csound.pdf for ASIO.
> I have amended your csd to use a command line similar to the example in
> csound.pdf. The amended csd works for me (attached).
> 
> It may also be a problem that your .csd calls for a very low latency of
> half a millisecond (though that does work on my very fast Windows XP
> notebook with an M-Audio driver).
> 
> And it may also be a problem that your driver has 4 in 10 out, but you have
> a mono csd. But my driver has 2 in and 2 out, yet it handles your csd OK,
> so your csd should work for you, I guess.
> 
....