[wdmaudiodev] Re: Re : Re: Re : Re: USB Audio/WASAPI channel limits?
- From: "Jerry Evans" <jerry@xxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Fri, 14 Feb 2014 13:14:43 -0000
Hi Florian
You probably are right re multi-client which is significant. Control panel
would be via HID or similar.
USB Audio 2 does support channel naming. Unsure about NI but the WASAPI in
Sonar, Tracktion etc.
It seems to me that the key issue with USB is still latency. 10ms a tad too
high for precise live work. My Delta PCI cards will work very reliably down
at ~2ms with ASIO.
BR.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Florian Schirmer
Sent: 13 February 2014 21:56
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Re : Re: Re : Re: USB Audio/WASAPI channel
limits?
Hello Jerry,
i don't have a full list, but here are a few things which spring to my mind:
- Channel names: Usually you have a sound card with a bunch of channels.
E.g. Mic, Headphone, Line in & out. Each Stereo. How to export a single
sound card with 8 channels but still maintain the info which channel serves
what purpose?
- Multi client support: We got *lots* of user complaints because our ASIO
driver wasn't multi client capable in the early days.
- App support: Lots of Pro audio apps don't support WASAPI.
- Control panel: Lots of cards do have custom settings which are not
directly accessible through WASAPI. Some of them directly affect the audio
e.g. clock selection, (external) sample rate changes, channel routing.
My WDM / KS knowledge is a bit dated so things might have changed, please
feel free to correct me!
Best,
Florian
On 13.02.2014, at 20:12, Jerry Evans <jerry@xxxxxxxxxxx> wrote:
Hello Florian,
I am curious. What can ASIO provide that WASAPI cannot?
BR,
Jerry.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Florian Schirmer
Sent: 13 February 2014 18:33
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Re : Re: Re : Re: USB Audio/WASAPI channel
limits?
Having a USB 2 audio class driver won't solve the problem for professional
use. Vendors still need to ship ASIO drivers and i'm not sure if there is a
reasonable way to plug those into the usb class driver. So unless we also
see an audio API fully supporting the professional use case (comparable to
ASIO or CoreAudio) there is probably limited benefit of having an USB 2
audio class driver.
Best,
Florian
On 13.02.2014, at 19:07, robert.bielik < <mailto:robert.bielik@xxxxxxxx>
robert.bielik@xxxxxxxx> wrote:
Touche, but.. how many USB *audio* class specs are there?
Without USB 2 audio, professional applications using WDM are out of the
question. But ok, fair enough, there's always ASIO...
/Rob
------ Ursprungligt meddelande ------
Från: Tim Roberts
Datum: 2014-02-13 18:51
Till: <mailto:wdmaudiodev@xxxxxxxxxxxxx> wdmaudiodev@xxxxxxxxxxxxx;
Ämne:[wdmaudiodev] Re: Re : Re: USB Audio/WASAPI channel limits?
robert.bielik wrote:
Hmm... USB Audio 2 class is a standardized specification. I would've assumed
that Microsoft generally would be keen on standards compliance?
The nice thing about standards is that there are so many to choose from.
There are a number of USB class specs that do not have generic in-the-box
drivers from Microsoft. There has to be a business case to justify the
considerable development and testing expense. Standards are only
interesting if they are used. If USB Audio 2 is a niche standard that is
only interesting to a tiny fraction of the market (and the current evidence
suggests that is the case), then it doesn't make sense to develop a class
driver. To four decimal places, Audio Class 1.0 satisfies 100% of the
Windows users in the world.
As a point of comparison, remember that Visual C++ STILL does not support
the C99 ISO standard, and there are a lot more C99 developers than there are
USB Audio 2 devices.
--
Tim Roberts, <mailto:timr@xxxxxxxxx> timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
****************** WDMAUDIODEV addresses: Post message:
<mailto:wdmaudiodev@xxxxxxxxxxxxx> mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: <mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe>
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe:
<mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe>
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator:
<mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx>
mailto:wdmaudiodev-moderators@freelists.orgURL to WDMAUDIODEV page:
<http://www.wdmaudiodev.com/> http://www.wdmaudiodev.com/
Other related posts:
