1708 and Wasapi -- doesn't work [#12099]

[delavagus]

Hey all! Longtime MM user here. I have been extremely happy with the MediaMonkey wasapi output: I was finally able to get truly gapless bit-perfect output. But I just upgraded to 1708, and wasapi has stopped working. When I double-click on a track, MM hangs up indefinitely. I've had to switch back to kernel streaming.

I've noticed that the wasapi output in my plug-ins folder (out_WASAPI_dll) appears to be new: my computer claims that the file was last modified on 6/19/2014, which is (I assume) newer than my previous MM upgrade. Has something changed? Are there any steps I can take to troubleshoot? Otherwise, is there an easy way I can get my hands on the OLD wasapi output dll, which was working perfectly for me up until about a half-hour ago?

Thanks!

[Lowlander]

Capture it in a debug log (step 4b) and send the log to support: http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=69

[bigkid]

Lowlander, since upgrading to 1708 I've noticed the same thing with Wasapi Event Mode on three computers with three different sound devices: a Roland Quad-Capture; a Chord Qute EX DAC; and, a Jongo A2. Disable Event mode in the Advanced settings for Wasapi and plackback is normal.

I'll try and do a debug report and attach.

Regards,

Allan

[bigkid]

Here is the debug file. I'ts a bit large I'm afraid as I have no idea how to trim it but yet keep the useful bits It is too big for the post so I have attached a link.

https://onedrive.live.com/redir?resid=3 ... 39%2112632

I attempted to play a couple of Alison Limerick songs if that will assist to narrow down the bug location in the log.

Regards,

Allan

[cruisin66stang]

I just installed 1708 and have the same problem. When I try to play a song it hangs up and won't play. It has been a while since I set up the program, but I believe I'm using wasabi also. Hopefully someone can post a fix. Thanks,

[bigkid]

All,

I have heard from Pavle and he notes that he did not develop the wasapi plugin and that he is aware of some driver initialisation issue in wasapi Event mode. His advice is to disable Event mode. You can do this in: Tools > Options > Output Plugins > Media Monkey Wasapi Configure > Advanced > deselect Event driven Exclusive mode.

Works fine on my three setups.

Regards,

Allan

[Peke]

Hi,
As this is starting to be symptomatic I've created http://www.ventismedia.com/mantis/view.php?id=12099 so that we investigate eve it works after Event mode is disabled.

[bigkid]

Thanks Pavle.

Regards,

Allan

ps. love your work

[norkle]

Had the same problem is 1708, but took me a while to realise it was to do with that update, thanks for this thread and helping me identify the problem.

After disabling event-driven mode, per Pavle's instructions/bigkids post, WASAPI was working fine for me again.

I noticed from the mantis issue the fix was to do this automatically on detection of lock/loop, so figure this will work for me in future too.

Hope this helps confirm the fix works.

Thanks.