Partager via

Windows Media Player 10 - now available...

  • Article

Windows Media Player 10 is now available for download

Check out the list of devices Media Player 10 works with - here - bet you thought Windows Media player was just for your desktop PC, right

This release of Windows Media Player is designed to offer more music and more choices with support for over 70 different portable music players and a wide range of services via the new digital music mall. Also new is more choice of formats with built-in, reference-quality MP3 ripping in addition to great fidelity and smaller file sizes offered by Windows Media Audio.

Tomorrow (Friday) I'm recording a video for Channel9 covering the Portable Media Center - should be interesting !

- Mike

Comments

  • Anonymous
    September 02, 2004
    The comment has been removed
  • Anonymous
    September 02, 2004
    The comment has been removed
  • Anonymous
    September 02, 2004
    The comment has been removed
  • Anonymous
    September 02, 2004
    Actually Mike, it DOESN'T work with my desktop system.

    http://www.lazycoder.com/weblog/archives/2004/09/02/nifty-wmp-10-is-xp-only/

    But that's OK because it doesn't know what system I'm running anyway.

    http://www.lazycoder.com/weblog/archives/2004/09/02/huh/

  • Anonymous
    September 02, 2004
    How about using Virtual PC, installing Windows XP Pro, then installing Windows Media Player 10 ? :O)

    - Mike
  • Anonymous
    September 02, 2004
    The comment has been removed
  • Anonymous
    September 02, 2004
    This honestly isn't intended as a troll.

    Any plans on native Ogg Vorbis support (to the same level as MP3) in WMP?

    If not, why not, and what would have to change for the answer to be yes?
  • Anonymous
    September 02, 2004
    Can someone please explain to me why WMP 10 eats 5-8% CPU time on an AMD XP 2600+ for playing an mp3 (no visualization at all) and winamp 0-1% ?

    what's 5-8% cpu time? well, not much, but it shouldn't be that much. I just wonder why MS didn't optimize the player lib to get more performace...
  • Anonymous
    September 02, 2004
    The questions about resource time and support for Windows Server 2003 should be posted to the Windows Media newsgroup - http://www.microsoft.com/windows/windowsmedia/community/newsgroups/WindowsMedia/default.mspx?dg=microsoft.public.windowsmedia&lang=en&cr=US

    I'm certainly interested in some of the embedded uses for Windows Media technologies - perhaps a home media server or similar...

    - Mike
  • Anonymous
    September 03, 2004
    There's quite a discussion going on about WMP10 not installing on W2K3 Server - check out the Windows Media newsgroup to get more information...

    - Mike
  • Anonymous
    September 03, 2004
    doesnt work on 2003 server
  • Anonymous
    September 03, 2004
    this issue is being discussed at length in the Windows Media Newsgroup

    - Mike
  • Anonymous
    September 14, 2004
    thank you
  • Anonymous
    September 14, 2004
    The comment has been removed
  • Anonymous
    September 19, 2004
    Mike,

    I recently got a new laptop, installed XP2 and WMP10. I'm noticing periodic CPU/disk hogging so have been watching Task Manager quite closely. wmplayer.exe uses 50%+ CPU every ten seconds, that's with visualisations disabled, and with nothing playing -- it's sitting idle (paused on an MP3) but still eats CPU every 10 seconds. Any idea what is going on?

    Regards,

    Steven
  • Anonymous
    September 19, 2004
    The behaviour is a little different to what I thought I first observed, and is kind of interesting. The CPU spikes are actually about 18 seconds apart, but there are sometimes gaps. An example of what I observe is 5 spikes 18 seconds apart of 50%+ CPU usage, followed by almost a minute of nothing, then 3 spikes each 18 seconds apart. Furthermore, these spikes only seem to occur when WMP10 is minimized to that Toolbar mode.
  • Anonymous
    September 19, 2004
    Some more to report...

    Another run, and the time between spikes is longer though still quite regular.

    SysInternals' ProcExp shows that >90% of the time spent in these spikes is kernel and it appears to be SHLWAPI.DLL!Ordinal505+0x2fa that is the culprit.
  • Anonymous
    June 19, 2009
    PingBack from http://mydebtconsolidator.info/story.php?id=21195