Thursday, June 23, 2005
Windows Media Connect Frustrations
Posted by Jason Dunn in "THOUGHT" @ 08:00 AM
Late last year, I bought a Roku M2000, which is a networked audio player that uses the Windows Media Connect foundation. Setup was a breeze, and I was amazed at how easily it worked. There are some things I dislike about the player (like how long it takes to load the browse list with 12,000 songs), but overall the hardware is pretty good. My real frustration is with the Windows Media Connect software that drives the entire process and lives on my MCE 2005 computer.
I have two main problems: insane resource usage, and disconnecting clients. When I log onto the computer that hosts all my media files, I always cross my fingers and hope it's not going to be a "bad Windows Media Connect day". What's a bad WMC day? Today is one - for the past 15 minutes I've had my CPU gunning, with the mswmccds.exe process using up 90-99% usage, and currently consuming 130 MB of RAM. This always happens after login, it's just a question of how long it lasts. On a good day, it will settle down after a few minutes. On a bad day it will last several hours. This is the Windows Media Connect process, presumably scanning for new content and getting snagged on something along the way, then looping endlessly and chewing up CPU and RAM resources along the way. The most frustrating part? There's absolutely no tools in the WMC user interface to tell me what's going on, what files it's snagging on, etc. Talk about frustrating!
The other problem is more directly related to the M2000 - when I turn it on, it comes out of standby and 90% of the time it says "no libraries found". This means that it's unable to find my desktop computer running the Windows Media Connect client. The only sure-fire way to get it connected again is to unplug the M2000 from power and re-connect it. After it does a full reboot it finds the computer with the media. I initially thought this was yet another problem with WMC on the desktop, but after searching the Roku forums it seems I'm not the only one having this problem. I'm hoping to see a fix from Roku soon on this so I can get some real use out of the M2000.
Windows Media Connect is a great idea, but the core technology still reeks of 1.0 issues. I'm looking forward to seeing it evolve into a more mature, stable software solution for linking media devices with home computers.
I have two main problems: insane resource usage, and disconnecting clients. When I log onto the computer that hosts all my media files, I always cross my fingers and hope it's not going to be a "bad Windows Media Connect day". What's a bad WMC day? Today is one - for the past 15 minutes I've had my CPU gunning, with the mswmccds.exe process using up 90-99% usage, and currently consuming 130 MB of RAM. This always happens after login, it's just a question of how long it lasts. On a good day, it will settle down after a few minutes. On a bad day it will last several hours. This is the Windows Media Connect process, presumably scanning for new content and getting snagged on something along the way, then looping endlessly and chewing up CPU and RAM resources along the way. The most frustrating part? There's absolutely no tools in the WMC user interface to tell me what's going on, what files it's snagging on, etc. Talk about frustrating!
The other problem is more directly related to the M2000 - when I turn it on, it comes out of standby and 90% of the time it says "no libraries found". This means that it's unable to find my desktop computer running the Windows Media Connect client. The only sure-fire way to get it connected again is to unplug the M2000 from power and re-connect it. After it does a full reboot it finds the computer with the media. I initially thought this was yet another problem with WMC on the desktop, but after searching the Roku forums it seems I'm not the only one having this problem. I'm hoping to see a fix from Roku soon on this so I can get some real use out of the M2000.
Windows Media Connect is a great idea, but the core technology still reeks of 1.0 issues. I'm looking forward to seeing it evolve into a more mature, stable software solution for linking media devices with home computers.
