Alessandro,
Well, you are most likely right. In theory manufacturers are supposed to implement a miniport driver (is that the right name?) and they then get directX and all of the other drivers (including ASIO) for 'free'. The problem is that miniport drivers are below the kmixer level and therefore go through all of the Microsoft crap. I assume that what RME (and probably quite a few other manufacturs) have done is make their ASIO drivers talk directly to their custom kernel drivers. Arghh . . . all of this wouldn't be necessary if Microsoft had done things right the first time. Of course I have a service pack that fixes all of these Windows problems - it is called linux!
Karl
On Tue, 5 Dec 2000, Alessandro Fogar wrote:
I think that the way to go for professional audio in Windows is Steinberg ASIO.
DirectX is for multimedia and games, not professional audio.
The RME for example has very good ASIO drivers but no DirectX direct drivers (you can see it under DirectX with 'emulated drivers').
But I don't know how we can then distribute the sources of the application which uses the ASIO Api sdk.
Bye
Alessandro Fogar
----- Original Message ----- From: "Karl MacMillan" karlmac@peabody.jhu.edu To: pd-list@iem.mhsg.ac.at Sent: Monday, December 04, 2000 9:22 PM Subject: Re: PD symbols with funny characters
On Mon, 4 Dec 2000, Miller Puckette wrote:
Yep, spaces are hard to get into symbols... I'm thinking someday about allowing symbols within quotes like "this symbol has 4 spaces" but I
think
there are more urgent problems for me to face (like latency in Windows).
Do you have an idea about how to handle the latency problem in Windows? I know that they claim that the drivers/schedular can handle 5ms latency (for DirectX) but this requires circumventing the 'kmixer', which essentially means using a driver specific work around. Do you know of a more standard way to do this?