|
|
From the "MMW Not PLaying LOG 1.LOG" I can confirm that there are 7 output devices and that WASAPI fails to play the files: 00021748 78.34133148 [161552] WASAPI: Output thread is starting 00021749 78.34142303 [161552] WASAPI: Looking for device: {0.0.0.00000000}.{c137d1af-7f4f-456e-8e09-ff3e6211e7b8} 00021750 78.34320068 [161552] WASAPI: Default device: {0.0.0.00000000}.{c137d1af-7f4f-456e-8e09-ff3e6211e7b8} 00021751 78.34553528 [161552] WASAPI: Found device: {0.0.0.00000000}.{2dbf64a2-83cb-451a-9bdd-7d41808911c8} 00021752 78.34557343 [161552] WASAPI: Found device: {0.0.0.00000000}.{6740ea00-f982-4316-accb-5ef0647a9b34} 00021753 78.34564209 [161552] WASAPI: Found device: {0.0.0.00000000}.{9fa538f1-ab64-4ec9-9c44-ec1b8bba2626} 00021754 78.34571075 [161552] WASAPI: Found device: {0.0.0.00000000}.{b89ba74c-e3ff-4a5e-b5b4-fbd6eeb32254} 00021755 78.34577179 [161552] WASAPI: Found device: {0.0.0.00000000}.{bfc9cf88-a81d-4d3d-8252-1723b9cce94f} 00021756 78.34584808 [161552] WASAPI: Found device: {0.0.0.00000000}.{c137d1af-7f4f-456e-8e09-ff3e6211e7b8} 00021757 78.34638214 [161552] WASAPI: Using automatic format choice. 00021758 78.34656525 [161552] WASAPI: Best format for playback found: 44100kHz, 2 ch, 16 bps 00021759 78.34662628 [161552] WASAPI: No output format for automatic exclusive mode was found. 00021760 78.34670258 [161552] WASAPI: New track not starting, finishing playback thread. 00021761 78.34674835 [161552] WASAPI: MMOpen finished. While MMDS plays it (MMW PLaying LOG 2.LOG) There used to be fallback to MMDS when WASAPI fails, but this was subsequently reverted ( details in 0006469 ) Note that WASAPI is the default only on Win10+ (details in #16009) We could add the fallback to MMDS back, but you indicated in #16009 that Win10+ distanced itself from DS ? And supposing that only a small set of users is observing this I guess that our KB article is enough, I see it covered e.g. as item 2b here: https://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/88/0/no-sound-is-playing--sound-is-corrupted |
|
|
Resolving, as discussed offline with Peke it was related to user's drivers/devices/system config and sometimes even changing to MMDS did not work and once it worked then also WASAPI started to work. So nothing that we could fix in MM. |
|
|
Re-opened: Upon offline discussion with Peke it would be useful to add an error dialog when playback fails because of an output plugin issue like this. Currently the tracks are only greyed out and skipped and users/support team have no idea what's happening. Assigned to Rusty to suggest wording for such a dialog, something like: "Current audio output configuration has trouble to play file X. Ensure that your sound drivers are properly installed or try to change/configure your output plugin." [Configure] [Help] [Cancel] [Configure] could be a link to Options > Ouptut plugins [Help] could point to https://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/88/0/no-sound-is-playing--sound-is-corrupted |
|
|
How about: "Current audio configuration cannot play xxx.yyy. Verify that your sound drivers are properly installed or try to change/re-configure the output plugin." The [Help] button should link to: https://www.mediamonkey.com/mediamonkey-output-error (redirects are used rather than direct links in case of a change to the back end). |
|
|
Sounds good, targeted to 5.0 |
|
|
Added in 2220. The dialog looks like this: ouput.png (56,478 bytes) |
|
|
Verified 2220 Dialog is properly shown. Test case: It is easier when using BT Audio where you can simply just go out of BT range or turn the Headphones off. |
- Anonymous
