Comment 4 for bug 494713

I've done some extensive testing with the provided plugins, comparing results with gst-launch with playbin and playbin2 and totem (on linux), here are the results:

• ('Keye FM', 'mms://stream.amaonline.com/keyefm')
    ∘ gst-launch playbin: Could not read packet header
    ∘ gst-launch playbin2: Could not read packet header
    ∘ totem: Could not read packet header
    ∘ moovida karmic: segfault (interrupted system call + Could not read packet header)
    ∘ moovida windows: segfault (Could not read packet header: No error)

• ('NRJ', 'mms://vipnrj.yacast.net/nrj_webtv03')
    ∘ gst-launch playbin: ERROR: Pipeline doesn't want to pause
    ∘ gst-launch playbin2: ERROR: Pipeline doesn't want to pause
    ∘ totem: plays (sound only)
    ∘ moovida karmic: frozen while buffering (interrupted system call)
    ∘ moovida windows: frozen while buffering

• ('Impuls', 'mms://netshow.play.cz/impulswebcam')
    ∘ gst-launch playbin: plays (sound + video)
    ∘ gst-launch playbin2: ERROR: Pipeline doesn't want to pause
    ∘ totem: plays (sound + video)
    ∘ moovida karmic: segfault (Could not read packet header)
    ∘ moovida windows: frozen, no error

• ('EskaTV', 'mms://streamtv.eska.pl:6000/eskatv')
    ∘ gst-launch playbin: ERROR: Pipeline doesn't want to pause (Could not read packet header: Interrupted system call)
    ∘ gst-launch playbin2: ERROR: Pipeline doesn't want to pause (Could not read packet header: Interrupted system call)
    ∘ totem: Could not read packet header: Connection reset by peer
    ∘ moovida karmic: frozen (Could not read packet header: interrupted system call)
    ∘ moovida windows: frozen, no error

• RadioTime plugin with TV support:
    ∘ moovida karmic: segfault (Could not read packet header: Success)
    ∘ moovida windows: segfault (Could not read packet header: No error)