#111 plugin won't play certain videos

3.21
closed-duplicate
Plugin (92)
5
2006-08-15
2006-08-11
Anonymous
No

I've been having trouble getting the mplayer plugin to
play videos from the comedy central website lately.
First, here's my setup:

FC5 with:
firefox 1.5.0.6
mplayer-1.0-0.45.pre8
mplayerplug-in-3.25-1
essential-20060611 codecs

Now, here's the URL of a video I am having trouble with:

http://www.comedycentral.com/sitewide/media_player/play.jhtml?itemId=72759

The plugin window keeps looping the following messages:

Connecting to server <servername>
Buffering http://<url>
Playing mms://<url>

The video will not play. However, I can right-click
and do a "get URL" from the plugin to obtain:

mms://a1768.v9950c.c9950.g.vm.akamaistream.net/7/1768/9950/v001/comedystor.download.akamai.com/9951/_!/com/colbert/2101_seat.wmv?auth=caEdCbtdFcHa4b6cYcmcAcjc6cyaDaVcbcf-be29zQ-dHa-DDNzoE&aifp=mtvn_02

I can run mplayer directly from the command line using
this URL (single quoted) and it works just fine.

Any ideas why this doesn't work with the mplayer
plugin? Is there a way I can get additional debug
information?

email contact: noky (at) noky (dot) net

Discussion

  • Kevin DeKorte

    Kevin DeKorte - 2006-08-11
    • status: open --> closed
     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-11

    Logged In: YES
    user_id=685413

    Upgrade to 3.30 and this will be fixed.

    Depending on how your mplayer is compiled you may have to add

    nortc=1
    nolirc=1

    to ~/.mplayer/config

    This is a known bug in 3.30 and will be fixed in the next
    release.

     
  • Nobody/Anonymous

    Logged In: NO

    I'm the original poster... I followed your suggestion and
    upgraded from 3.25 to 3.30. I also added those two lines to
    the config file.

    However, the video still will not play. The plugin screen
    still keeps cycling text which indicates: Connecting,
    Buffering, Playing...

     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-11

    Logged In: YES
    user_id=685413

    ok, then...

    Well set "debug=1" in the mplayerplug-in.conf file and then
    run your browser from a terminal. You should get a ton of
    information as to what is going on. Post that and it should
    be pretty easy to fix.

     
  • Nobody/Anonymous

    Logged In: NO

    The debug feature does not seem to work! I added debug=1 to
    ~/.mplayer/mplayerplug-in.conf, then started firefox from
    the command line. Nothing appeared on stdout when
    mplayerplug-in started. I also modified
    /etc/mplayerplug-in.conf (~/.mozilla/mplayerplug-in.conf
    does not exist for me). I even logged out of my gnome
    session and logged back in. Still, no debug output

    Is there a logfile or something that it is writing to?

     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-11

    Logged In: YES
    user_id=685413

    You might need to apply this patch to the firefox startup
    script...

    diff -u /usr/bin/firefox bin/firefox-out
    --- /usr/bin/firefox 2006-08-08 14:29:24.000000000 -0600
    +++ bin/firefox-out 2006-08-11 13:34:49.000000000 -0600
    @@ -145,7 +145,7 @@
    # if there's no command line argument and there's not a running
    # instance then just fire up a new copy of the browser
    if [ -z "$1" ]; then
    - exec $MOZ_PROGRAM $MOZARGS 2>/dev/null >/dev/null
    + exec $MOZ_PROGRAM $MOZARGS
    fi

     
  • noky

    noky - 2006-08-15

    Logged In: YES
    user_id=1576235

    OK, I've got a dump of the mplayplug-in output, but I can't
    seem to attache a file. I even created a sourceforge
    account... Does the bug status need to be "open" in order
    to create attachments for a bug?

     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-15

    Logged In: YES
    user_id=685413

    Maybe... I opened it back up...

     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-15
    • status: closed --> open
     
  • noky

    noky - 2006-08-15

    Logged In: YES
    user_id=1576235

    I could not attach a file to this bug report! Maybe because
    I originally posted anonymously. I don't know. The only
    was I was able to attach a file with debug info was to open
    a new bug report. See 1540697

     
  • Kevin DeKorte

    Kevin DeKorte - 2006-08-15
    • status: open --> closed-duplicate
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks