New
#1
WMP Painfully Slow (Not Responding)
Having traversed many of the forums/threads and tried most suggestions offered, I come to the conclusion than the μSoft WMP folks should, by this time realize that their product has serious performance problems/issues when dealing with relatively large media DBs. I would suggest that there exists either a logic flaw(s) in some library/logic- like holding a lock for too long, or a DB indexing/linking problem when dealing with large DBs. It’s time that the designers stop their “Have you tried this, or have you tried that” scenario, and exercise the product clinically with a large DB in the lab- find out where the code is spending (wasting) its time doing its various functions, and provide a solution via a product update (pronounced correction). It should be most obvious to them that THEY (their product) has serious issues.
I used to be able to Rip a CD in 5-10 minutes elapsed with WMP, now it takes an hour plus!!
I’m at a point where I’m willing to spend money to invest in a competitive product that is functionally equivalent to WMP if one exists. Do you have any suggestions? I am at my wits end trying to deal with a product (WMP) that can only be described as one that is seriously flawed, and deficient!
Randy Reist