View Issue Details

IDProjectCategoryView StatusLast Update
0002302MMW v4Playerpublic2006-03-09 16:32
Reporterrusty Assigned To 
PriorityimmediateSeveritycrashReproducibilityalways
Status resolvedResolutionunable to reproduce 
Summary0002302: Some WMA files cause MM to crash on playback and cannot be leveled
DescriptionA WMA file that previously worked perfectly (played without a problem in MM 2.4.2) no longer seems to play in 2.5.1. Moreover, any attempt to play the file causes MM to freeze.

As would be expected, volume leveling for this file also fails.

Posting the file and a debug log to the ftp server (although the debug log seems to be useless).
TagsNo tags attached.
Fixed in build

Relationships

related to 0002799 resolvedjiri Volume leveling in 3.x causes CPU to go to 100% for wma tracks 

Activities

rusty

2005-12-23 16:52

administrator   ~0006754

Further testing shows that:
-all WMA files no longer play in MM on my system
-WMP plays my tracks no problem.
-Even _after_ I play the tracks in WMP, they still can't play in MM!

This makes me think that this is a combination of 2 bugs:

1) When MM doesn't have rights to play back a wma file, it doesn't return a message--it just freezes (until it gets the rights which in scenarios it can't).
2) This is just a hypothesis, but perhaps when user purchases rights for tracks on Napster and those rights have expired, the expiration causes all tracks in the library to no longer function in MM.

Will test further...

rusty

2006-03-09 14:50

administrator   ~0007023

Last edited: 2006-03-09 14:58

As discussed over IM, I was able to reproduce this problem with 2.5.2.950 as follows.

Attempt to play the file in MM --> MM locks up
Attempt to close MM --> no response (MM must be closed 3 times before it responds or closed via the task manager). Once MM is closed, decode.exe continues running.
Attempt to play the file in WMP --> it plays successfully

Posting the file (Beethoven) to the ftp server.

jiri

2006-03-09 16:32

administrator   ~0007043

As Rusty reported, reboot fixed this issue.