One other thing to keep in mind when deciding between AvStream and Portcls, is
(in my experience) that Portcls seems to make certain assumptions about data
used based on position information reported. This again reflects the
DMA/interrupt oriented thinking built into it. If accurate audio position
information for a device that is not built in (ie USB, Bluetooth, 1394, etc) is
desired AvStream is probably a better choice. Otherwise there are tradeoffs
necessary to keep the audio data moving and reporting accurate position when
the data is not being consumed directly by the hardware.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Vogan
Sent: Wednesday, May 06, 2015 2:55 PM
To: wdmaudiodev
Subject: [wdmaudiodev] Re: Driver model for multi-client MIDI
Thank you for the insights, Tim. You are right that the MIDI traffic is simple
and primitive. As long as MSDN's caveat about external buses for PortCls just
affects my own buffering on the USB side, I can deal with that.
