by Roger W » Sat Oct 12, 2013 3:05 am
Trying 4.1 for the first time (build 1662) and looking forward to the DLNA Service feature.
However, it seems that decoder.exe often/always hangs and messes up the media sharing. Everything works fine when running the app normally.
Details: Windows 7, (no UAC), portable install, running as my user which is an admin and has Log on as a Service rights.
The DLNA client is an android device running BubbleUPnP.
There is an auto-conversion rule in place that is trying to transcode WMA Lossless to MP3. This workd when the MMW window is up, but when it's in service-only mode, I see decoder.exe processes start and sit around doing nothing until the client times out, moves to the next track, and then another decoder.exe process spawns and hangs. After that's happened, the service typically doesn't respond to other media requests.
I see this in the log repeatedly, which I'll submit in the morning after I set up an account:
2.1 Date : Sat, 12 Oct 2013 00:31:24 -0700
2.2 Address : 00A25826
2.3 Module Name : MediaMonkey.exe - (MediaMonke)
2.4 Module Version: 4.1.0.1662
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 00A25826 in module 'MediaMonkey.exe'. Write of address 00000020.
2.7 ID : 5506
2.8 Count : 1
2.9 Status : New
2.10 Note :
Trying 4.1 for the first time (build 1662) and looking forward to the DLNA Service feature.
However, it seems that decoder.exe often/always hangs and messes up the media sharing. Everything works fine when running the app normally.
Details: Windows 7, (no UAC), portable install, running as my user which is an admin and has Log on as a Service rights.
The DLNA client is an android device running BubbleUPnP.
There is an auto-conversion rule in place that is trying to transcode WMA Lossless to MP3. This workd when the MMW window is up, but when it's in service-only mode, I see decoder.exe processes start and sit around doing nothing until the client times out, moves to the next track, and then another decoder.exe process spawns and hangs. After that's happened, the service typically doesn't respond to other media requests.
I see this in the log repeatedly, which I'll submit in the morning after I set up an account:
2.1 Date : Sat, 12 Oct 2013 00:31:24 -0700
2.2 Address : 00A25826
2.3 Module Name : MediaMonkey.exe - (MediaMonke)
2.4 Module Version: 4.1.0.1662
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 00A25826 in module 'MediaMonkey.exe'. Write of address 00000020.
2.7 ID : 5506
2.8 Count : 1
2.9 Status : New
2.10 Note :