This question is completing previous question about IAudioSessionControl /
ISimpleAudioVolume that you replied here one month ago
As the Microsoft Audio Developer, you have on your blog/github the source
code to check the problem to get icon/app name from IAudioSession
(be sure Ive tried all method you gave in your blog to get icon/app name
from a process ID).
Candy Crush Soda Saga is used by millions of users since years on WIN10
I
cannot be the one who fill the bug in Feedback Hub, it is statistically not
possible!
When I put a question regarding audio driver here, I get no reply
, I remind
you that Im still waiting replies regarding the HLK certification process
that no-one at Microsoft tested with the SYSVAD
Do you prefer I come back
to these subjects?
VB
De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : jeudi 15 novembre 2018 13:01
À : wdmaudiodev@xxxxxxxxxxxxx; Pete Brown (WDG/PAX)
Objet : [wdmaudiodev] Re: Question about IAudioSessionControl & Candy Crush
Soda Saga
Huh? What does any of this have to do with audio drivers? This is a
discussion list about how to write audio drivers.
Your first question sounds like a bug in either Candy Crush itself or in
whatever audio APIs Candy Crush is using. Can you file this bug in Feedback
Hub? We can either fix it ourselves or relay it to whoever owns Candy Crush,
depending.
If youre curious, heres a blog post where I talk about how to discover
what APIs apps use to play and record audio:
<https://blogs.msdn.microsoft.com/matthew_van_eerde/2018/11/12/what-api-is-b
eing-used-to-play-or-record-audio/>
https://blogs.msdn.microsoft.com/matthew_van_eerde/2018/11/12/what-api-is-be
ing-used-to-play-or-record-audio/
The answer to your second question is use the process ID. There are two
different code paths you have to take, depending on whether the process is a
Store app or not.
_____
From: <mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
wdmaudiodev-bounce@xxxxxxxxxxxxx < <mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
wdmaudiodev-bounce@xxxxxxxxxxxxx> on behalf of Vincent Burel (VB-Audio) <
<mailto:vincent.burel@xxxxxxxxxxxx> vincent.burel@xxxxxxxxxxxx>
Sent: Wednesday, November 14, 2018 11:39:49 PM
To: <mailto:wdmaudiodev@xxxxxxxxxxxxx> wdmaudiodev@xxxxxxxxxxxxx; Pete
Brown (WDG/PAX)
Subject: [wdmaudiodev] Question about IAudioSessionControl & Candy Crush
Soda Saga
Hello,
Regarding IAudioSessionControl we have basically 2 problems with Candy Crush
Soda Saga delivery with WIN10:
1- It creates 2 Audio sessions (with different GroupingParam) , one is
not active. this can be seen on the Windows Mixer itself (see picture
attached).
groupID {55C986DA-757B-4C10-A3FB-4DC9C75C0726} _GUID
SessionIdentifier:
"{0.0.0.00000000}.{db0fec5a-d3c5-405a-ba20-dc6f4df2d8f2}|#%b{3171F6E2-B5AD-4
09B-B696-22115DEEF86B}"
wszApplicationName: 0x005aebcc "C:\Program
Files\WindowsApps\king.com.CandyCrushSodaSaga_1.114.500.0_x86__kgqvnymyfvs32
\stritz.exe"
ProcessUID: 580
groupID {E587D2E2-46AC-4F38-84D3-8301C1A2EAED} _GUID
SessionIdentifier:
"{0.0.0.00000000}.{db0fec5a-d3c5-405a-ba20-dc6f4df2d8f2}|\Device\HarddiskVol
ume4\Program
Files\WindowsApps\king.com.CandyCrushSodaSaga_1.114.500.0_x86__kgqvnymyfvs32
\stritz.exe%b{00000000-0000-0000-0000-000000000000}"
wszApplicationName: 0x0085e7a4 "C:\Program
Files\WindowsApps\king.com.CandyCrushSodaSaga_1.114.500.0_x86__kgqvnymyfvs32
\stritz.exe"
ProcessUID: 580
QUESTION: Is there a way to deal with these 2 sessions or is
there a bug needing to be corrected somewhere ?
2- We did not find any way to get icon / application name of this both
session.
Windows Enumeration gives 2 handles that have no icon and no name
And the
application directory seems to be protected in a way we cannot extract any
information from the stritz.exe resource section.
QUESTION: How to get icon and application name of Candy
Crush Soda Saga from IAudioSessionControl ? How does the Windows Volume
Mixer application ?
Regards
Vincent Burel
