I could better answer your questions if I understood where you were going with
this. Why do you ask? What is your scenario? These don’t really sound like “how
do I write a driver” questions.
In Windows, the burden falls on the application to either invoke their own
micro-sample-rate-converter, or adjust Windows’ built-in
micro-sample-rate-converter (e.g. via the IAudioClockAdjustment API.)
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Johannes Freyberger <jfreyberger@xxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, August 22, 2018 2:03:14 AM
Subject: [wdmaudiodev] AW: Re: AW: Re: bit transparency from app to WDM audio
driver depending from API?
Thank you very much for this info and the one concerning the exclusive mode for
bit transparency. Is this micro SRC insertion only done in non exclusive mode
or would this also be inserted in exclusive mode, if such a microphone/speaker
situation is detected? Is the SRC factor only computed once or dynamically
adjusted? I’m thinking about a situation where you have a playout system
running multiple hours or even days and if the SRC wouldn’t be adjusted or
extremely precise it probably would result in buffer under- or overruns on any
end after a while.
Does this information concerning exclusive mode, SRC etc. apply to all Windows
OS versions (saying all I think about Windows 7, 8, 8.1, 10 64 bit and Windows
Server 2102 and 2016)?
„Usually a micro SRC is only inserted if the application in question has to
connect two clocks.
If it’s just music playback, then the whole clock is driven by the DAC. If the
effective sample rate is a little slow, then the music just takes a little
longer to play.
But if the microphone and the speaker are both involved, and the ADC and DACs
are at different effective sample rates, then yes, a micro SRC is (hopefully!)