0001560: Exception when attempting to play non-supported file types

ID	Project	Category	View Status	Date Submitted	Last Update

0001560	MMW v4	Player	public	2004-10-20 02:07	2010-11-22 18:16

Reporter	rusty	Assigned To
Priority	urgent	Severity	minor	Reproducibility	always
Status	closed	Resolution	not fixable

Summary	0001560: Exception when attempting to play non-supported file types
Description	1) I had an old version of Media installed. 2) Installed the latest version 3) Scan my C drive for media file 4) Click on View -> Player 5) under Play list, the folder: Accessible track showed abut 700 media files. I double click on one of them. Then it seems that the Media scanned all tracks in that directory and then generated the error message for every track.
Additional Information	Reported by David Eskenazi. Note: screencap of the error message and debug log are posted to the FTP server
Tags	No tags attached.

Fixed in build

jiri 2004-10-20 14:40 administrator ~0004565	The following text is in the debug log (it isn't produced by MM): ******************************************************************************************** This breakpoint is By Design. You are accessing protected content while running the debugger. This only occurs in Free builds - either use Checked builds or stop playing protected content. Hint: turn off protection of CD copied content in Windows Media Player by going to {Tools}{Options...}, clicking the CD Audio tab, and unchecking Enable Personal Rights Management. ******************************************************************************************** I don't know what does it mean, it seems that the user has something non-standard installed on his machine because this shouldn't be generated by MM or any of the plug-ins.

jiri 2004-10-20 14:40 administrator ~0004566	Reminder sent to jiri Check this out.

rusty 2004-10-20 16:11 administrator ~0004567	Yeah--I noticed this in the debug trace but I also saw that there were a couple of non-wma tracks that still generated errors.

jiri 2004-10-20 21:13 administrator ~0004568	Sorry, I missed those. It seems to be caused by in_mpc.dll. In order to test this we might try to get some of the .mpp files that cause the problem.