WMP 9 takes a long time to start playing avi and mpg

Discussion in 'Windows Media Player' started by davetest, Jun 22, 2004.

  1. davetest

    davetest Guest

    if I play local (on the harddrive) avi or mpg in
    mplayer 6.4, or bsplayer it starts to play the clip
    in about 1 - 2 seconds.

    If I play it in wmp 9, the clip doesn't play until
    5 - 10 seconds have elapsed.

    What is wmp 9 doing that the others aren't?
    Anything I can check for? WAD ?
    something is goofy here.
    (Running wmp 9 in 98SE)

    davetest, Jun 22, 2004
    1. Advertisements

  2. davetest

    Turkbear Guest

    Check to see how each's Buffer amount is set..Other options can affect this as well..
    Turkbear, Jun 22, 2004
    1. Advertisements

  3. davetest

    davetest Guest

    I've played with the buffer in wmp 9. What does it do?
    I thought that was for streaming content only.
    In any case, it didn't affect the problem.

    davetest, Jun 22, 2004
  4. davetest

    zachd [ms] Guest

    That should mean that WMP is trying to resolve/negotiate video playback
    through interference of some kind. Either WMP is having trouble with the
    video card-
    would help with that - or there's some codec interference.
    zachd [ms], Jun 23, 2004
  5. davetest

    davetest Guest

    How to troubleshoot "interference" ? codec issues occured to me,
    but how do nail it down? I've not installed any codec packs, just
    divx and ffdshow.

    Why does it work just fine in the other media players?
    What is wmp 9 doing that the others aren't?

    At the time of the delay there is the word "connecting"
    in the lower left corner.

    davetest, Jun 23, 2004
  6. davetest

    zachd [ms] Guest

    You'd trouble-shoot interference by figuring out settings of relevant items
    in the filter graph you'd want to tweak. A#1 in the list is the video
    driver, which is why I pointed you to
    last time. Did you try that?
    Pretty much every single player out there does it differently.

    Right, "connecting" in that case means "connecting" together the playback
    scheme that is going to be used for that file.


    zachd [ms], Jun 26, 2004
  7. davetest

    davetest Guest

    HI Zach -
    appreciate your continued assistance.
    Your link talks about video flickering (which I don't suffer from)
    and updated video driver and Dx. (which I have)

    Your link also mentions options/performance/HW acceleration.
    Turning this down did not affect the problem.

    As mentioned earlier, the *only* issue I have is the 5 to 10
    second delay. Once it starts it looks and performs just fine.

    This delay only occurs with all avi and mpg. WMV and ASF video files
    start immediateky. In all cases, I'm referring to local (harddrive)
    davetest, Jun 26, 2004
  8. davetest

    zachd [ms] Guest

    It's meant to apply to generic video issues.
    Yep. Exactly what I'm saying. WMP has to know what to ban from the graph.
    I don't know that and can't find that out from here. You don't know that,
    and can only find that out TMK by either tinkering or assmbling the graph
    Right, WMV/ASF don't build filter graphs in WMP, so don't have this problem.

    Checking the filter graphs in GraphEdt.exe...
    WAV->Wave parser->Default DirectSound Device
    AVI-->AVI Splitter-->AVI Decompressor-->Color Space Converter-->Video
    --> ACM Wrapper-->Default DirectSound Device
    MPG->MPEG-I Stream Splitter-->MPEG Audio Decoder-->Default DirectSound
    -->MPEG Video
    Decoder-->Video Renderer
    (and just for kicks)
    ASF-->(audio) Decoder DMO --> Default DirectSound Device
    (video) Decoder DMO --> Video Renderer

    Any attempt to play back any file in WMP6 (mplayer2.exe) will force a graph
    to be rendered. It'll use slightly different graphs than WMP7+ (for
    example, I believe WMP6 uses a filter graph instead of the WMFSDK for ASF
    rendering), but ... your basics are still in place.

    Anyways, if you wade through the above list, you'll note that the
    commonality between the MPEG and AVI rendering is the Video Renderer.
    There's also the resolution of decoder to use, too - it may entirely be
    possible that you have some insane video codec that says it can handle
    everything, gets tried, rejected + banned, taking up those seconds.

    But smart money is on the Video Renderer.
    The only other weird way of solving this I've heard of is unchecking "Start
    player in media guide".

    zachd [ms], Jun 26, 2004
  9. davetest

    davetest Guest

    I can certainly render the file on graphedt and see a similar delay.
    How do I know what was tried and discarded?
    If I could find out this, perhaps I'd have the solution.
    What is TMK?
    I'm not sure what your point is, surely the rendering of this
    graph is things working as designed. Nothing unusual shows up.
    Makes sense. How do I use the tools I have to find out ?
    Video renderer is MS supplied software isn't it?
    What are you implying by this? It's WAD?
    Been there done that, no effect.
    Zach, thanks for taking the time to put this stuff down.

    davetest, Jun 27, 2004
  10. davetest

    davetest Guest

    I have made an improvement in the players response time
    by uninstalling ffdshow (xvid dshow filter) and installing the
    actual xvid codec. Seems to have cut the wait to about 3 seconds.
    Better than before.

    Is there some kind of log or tracing facility that shows you the
    filters that are considered during the rendering of a media file?

    davetest, Jun 27, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.