what is ASIO? 
 
do you have documentation pointers? 
 
I think we should not run ASIO drivers, but support ASIO from apps using the 
normal UNIX mechanisms. 
 

ASIO is a driver interface for pro-audio apps developed by Steinberg. It's  
somewhat similar to our beloved Jack sound server, but not as advanced. 
Anyway, I added the URL to the Steinberg ASIO SDK (for drivers and client 
apps), hope this helps. 

jack used to have a --asio switch, but this was removed in 2003.  I don't know 
why this was, or whether that switch, if it were still in place today, would 
enable cubase etc. to work under wine.

I think that switch was for cards that had ASIO hardwired or something. Don't 
know why the JACK devs removed that, guess it wasn't needed anymore, but 
that's unrelated to Wine anyway... 

Created attachment 3517 [details]
wine ASIO driver

Here is a simple wine ASIO driver using Jack as the hardware device.  This is
just a proof of concept at this point put out there for comments.  Please
review it and give me feedback.

This driver works in playback mode and has been tested with
http://www.magma.ca/~gtaylor/ASIOTestSigGen.htm.  Capture mode has not been
tested.  Full duplex mode has been tried but didn't work for me.

Created attachment 3584 [details]
wine ASIO driver version 2

This is version 2 or my wine ASIO driver.  This version fixes a a major
wine/win32 thread bug and also attempts to address some of the Steinberg ASIO
technology licencing issues.

A note on the legality of using the ASIO API: I can't find a decent URL, but it
is frequently claimed that the USL vs. BSDi case gives precedent for header
files and/or API definitions being uncopyrightable (see related mailing list
thread from Sept. 2006).

Created attachment 7998 [details]
Connection map and settings patch

Here's a patch to add the following:
1) You can use ${HOME}/.wineasiocfg or /etc/default/wineasiocfg to store settings.
2) In addition to ASIO_INPUTS and ASIO_OUTPUTS, you can also specify connections, using INPORTn=client:port and OUTPORTn=client:port

Created attachment 8027 [details]
header file missed from patch

Clearly my diff-fu was questionable at the time.  If forgot the "treat new files as previously empty" flag.  Here's "settings.h".

I didn't previously realise that Robert's patches were against the WINE tree and the source I had (from http://people.jacklab.net/edogawa/files/wineasio/) was not closely related.

I've done some substantial additional work since my previous patch and Robert has also made some updates that unfortunately conflicted.

I've passed the updated source package to the JackLab team (well, the packager), to the 64studio team (Daniel and Free), to Robert Reif and to Ralf Beck, who has also logged changes.

Subject to bugs... I expect the updated driver to appear at JackLab, as above, in the coming days.

See also this thread:
http://forum.jacklab.net/viewtopic.php?t=563
for further details.

Is this still an issue in current (1.0-rc4 or newer) wine?

(In reply to comment #11)
> Is this still an issue in current (1.0-rc4 or newer) wine?
> 

The original bug was to support Windows ASIO drivers under WINE.  I don't know whether that's ever been addressed.

However, the alternative is to provide generic ASIO support under Linux and that is what the wineasio project supplies.  By using JACK and wineasio, any jack supported back end becomes a support ASIO device under WINE.

I think this bug can be closed as won't fix. The ASIO's license is not compatible with Wine. And wineasio can not be integrated into Wine because of that.

WONTFIX

Closing.

This is referenced from http://wiki.winehq.org/DirectX-ToDo but is closed as WONTFIX. Which is it?

(In reply to comment #16)
> This is referenced from http://wiki.winehq.org/DirectX-ToDo but is closed as
> WONTFIX. Which is it?

See comment #13