Serge,
It's good to hear that this is a known issue. Of course, it would
be even better to hear that it worked properly. Can you tell me what
build this will be fixed in?
Thanks, Mike
If you are playing .wav files in an application that uses DirectSound
(e.g., Windows Media Player), this is a known issue. Please try either
.wma files in WMP or .wav files in an application that can be configured
to use waveOut (e.g., graphedt if you have that).
-----Original Message-----
From: Michael R. Preston [mailto:mike@xxxxxxxxxxxxxxxxxxx] Sent: Thursday, September 28, 2006 3:00 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Cc: Jeffrey Hoekman; Serge Smirnov; Shuba Iyer
Subject: Re: [wdmaudiodev] More Vista LFX channel conversion problems
Jeff,
Thanks for your response. I have not been debugging AudioDG directly. I have strictly been debugging the APO. I am seeing this behavior using Windows Media Player 10 on Vista RC1 (build 5600), using the speaker fill sample code which wraps the built-in APO. I would think it's not a problem with Media Player, and it doesn't look like it's an APO problem because the LFX is never asked if it supports 6->8 channel conversion. Are you recommending I debug the AudioDG process to
see what it's doing, or is that something you guys would rather take a look at? As for mono content, I know we can handle it in our APO in the
manner you described if we decide to support it, but I'm not too worried
about it.
Thanks, Mike
Jeffrey Hoekman wrote:
The sample code which you're referring to does not speaker-fill for
mono
content. You will need to modify IsIn{Out}putFormatSupported and
likely
LockForProcess/ValidateAndCacheConnectionInfo and APOProcess to make
it
work for mono. I'm not sure about speaker-fill for >2-channel content -- Serge may be able to comment on that.
If you're debugging AudioDG and not seeing the correct formats in the 'format-supported' calls it's likely the initial format negotiation between the client app and AudioSrv (the service) is not resolving properly. Instead debug the IsInputFormatSupported API from within AudioSrv to determine the original formats queried for render. This
is
generally the first line of negotiation with any player client.
-----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Michael R. Preston Sent: Wednesday, September 27, 2006 11:49 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] More Vista LFX channel conversion problems
Frank/Jeff, Well, my last post may have been a little premature. The new APO sample code was very helpful. Since there was little documentation up until this point, the new sample code definitely helped to better understand how the APIs are to be used. However, even with the new sample code for speaker fill, I'm still seeing some LFX channel conversion problems. I didn't see them at first because I had only tried doing speaker fill on stereo content. Converting 2-channel content to 6 or 8 channels works fine. However, it looks like
anything
other than stereo content is currently not compatible with speaker
fill.
With mono, 4-channel, or 6-channel content, the APO is never given
the
chance to do speaker fill. The number of input and output channels always equals the output mode in these cases. There are a few use
cases
that are less important (say converting mono system sounds to 6 or 8 channels), but the obvious need is to convert 6-channel content to 8 channels. If you're playing a DVD (which is 5.1 content) in a 7.1 speaker system, the LFX should be able to do speaker fill to make
audio
come out the side speakers. With the way Vista is currently behaving,
it is impossible for an APO to do the channel conversion to support this. This seems to be a Windows problem and not an APO problem,
since
the APO is never even asked if it supports 6 channels in, 8 channels out. I have tried this with RC1 (build 5600), and with a more recent version, and the problem remains unchanged. Can you check to see if this is a known problem?
Thanks, Mike -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Mike Preston | Home/Office: (360)756-1655 | | E-mail: mike@xxxxxxxxxxxxxxxxxxx | Cell: (360)303-9331 | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | The man who follows the crowd will usually get no | | further than the crowd. The man who walks alone is | | likely to find himself in places no one has ever been. | | -- Alan Ashley-Pitt | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ******************
WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Mike Preston | Home/Office: (360)756-1655 | | E-mail: mike@xxxxxxxxxxxxxxxxxxx | Cell: (360)303-9331 | |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | The man who follows the crowd will usually get no | | further than the crowd. The man who walks alone is | | likely to find himself in places no one has ever been. | | -- Alan Ashley-Pitt | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ******************
WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/
