Crash when streaming to remote MediaMonkey

Help improve MediaMonkey 5 by testing the latest pre-release builds, and reporting bugs and feature requests.

Moderator: Gurus

sunspot
Posts: 114
Joined: Fri Jun 16, 2006 11:45 pm

Crash when streaming to remote MediaMonkey

Post by sunspot »

I've been trying to use MM 5 to stream from my desktop PC (running MM5) to my media PC (running MM5). I'm getting a pair of error messages after a track or two. One pops up in MM5 on the media PC, the other is a general windows app error.

The MM error message is "Current audio configuration cannot play 0 Hz. Verify that your sound drivers are properly installed or try to change/re-configure the output plugin."

The application error is: "Application throw an exception Access violation at address 0D8789E1 in module 'out_MMDS.dll". Read of address 00000004 Would you like to restart MediaMonkey in Safe mode?"

On both systems I've set the output plugin to MediaMonkey DirectSound outpt and I'm using the Primary Sound Driver. I've disabled all options except Enable hardware acceleration. I'll try disabling that next.

MM doesn't seem to have this problem playing local files on the Media PC. It's something to do with DLNA/UPnP.
sunspot
Posts: 114
Joined: Fri Jun 16, 2006 11:45 pm

Re: Crash when streaming to remote MediaMonkey

Post by sunspot »

I'm running Win 10 Home, latest version of MM (5.0.0.2338).
Lowlander
Posts: 59294
Joined: Sat Sep 06, 2003 5:53 pm

Re: Crash when streaming to remote MediaMonkey

Post by Lowlander »

Can you please try on build 2419 for both installs: https://www.mediamonkey.com/forum/viewt ... 86639&sd=d

What File Type(s) does this happen for?
sunspot
Posts: 114
Joined: Fri Jun 16, 2006 11:45 pm

Re: Crash when streaming to remote MediaMonkey

Post by sunspot »

It's definitely happening with FLAC files. Might have hit with an MP3 as well.

Turning off hardware acceleration didn't help.
Ludek
Posts: 5118
Joined: Fri Mar 09, 2007 9:00 am

Re: Crash when streaming to remote MediaMonkey

Post by Ludek »

Could you please capture it in a debug log (step 4b) and attach it to a Support Ticket: viewtopic.php?f=30&t=86643
Post Reply