Might very well be. How else should I determine what causes this failure on
only one computer?
Børge
On Wednesday, April 24, 2019, Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
OK, then Windows is handing audio to the driver, and the error in the
event log is a red herring.
------------------------------
*From:* wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx>
on behalf of Borge Strand-Bergesen <borge@xxxxxxxxxxxxxx>
*Sent:* Wednesday, April 24, 2019 4:38:23 AM
*To:* wdmaudiodev@xxxxxxxxxxxxx
*Subject:* [wdmaudiodev] Re: USB DAC "was not migrated"
Yes, they do.
Børge
On Monday, April 22, 2019, Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
When you play music to the computer, do the meters move in Settings and
in the legacy Sound control panel?
------------------------------
*From:* wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@freelists.
org> on behalf of Borge Strand-Bergesen <borge@xxxxxxxxxxxxxx>
*Sent:* Saturday, April 20, 2019 8:26:34 AM
*To:* wdmaudiodev@xxxxxxxxxxxxx
*Subject:* [wdmaudiodev] USB DAC "was not migrated"
Hi guys,
I'd appreciate your help with what looks like a Windows driver issue.
I'm working on a USB audio interface on the NXPMIMXRT1050-EVK board. The
code example from NXP works flawlessly on my test computers (Win7/32,
Win10/32, OS X) but fails on my development computer (Win10/64). The error
message I get is:
Device SWD\MMDEVAPI\{0.0.0.00000000}.{afd74c06-0611-47f0-8266-a29ec7e6ef4f}
was not migrated due to partial or ambiguous match.
Last Device Instance Id: SWD\MMDEVAPI\{0.0.0.00000000}.
{0158e0fe-4ae9-4e4e-b789-a85a02d779c8}
Class Guid: {c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
Location Path:
Migration Rank: 0xF00000000000F120
Present: false
Status: 0xC0000719
The error persists after changing the USB PID of the device. Scanning for
updates and rebooting the computer also doesn't help. I found this under
Device Manager and Events for the device in question.
The DAC is unable to play music, but in both player program, Sound
Settings and Device Manager it looks like everything is working perfectly.
Only the Events tab revealed that things aren't up to speed. A different
DAC works perfectly on the same computer.
The NXP code is primarily UAC1. It does have a UAC2 switch, and when I
build with it turned on, Win7 fails to recognize it while OS X can use it.
This is just as expected, even though I haven't gone much deeper into the
code. On the Win10/64 development computer I get the same kind of error
message for both modes.
Best,
Børge
--
Børge Strand-Bergesen
borge@xxxxxxxxxxxxxx | Mobile: +47 90 63 99 18
[image: www.henryaudio.com]
