Comment 39 for bug 108623

Revision history for this message
c (clayton-spicer) wrote :

I get the same thing with every backend. It's ridiculous that i can actually stream videos more reliably over 3G on my phone than using totem on an 8mbit broadband connection (no joke). Seems like fixing this isn't a priority for anyone either considering this problem still persists after more than 3 years. No idea what 'triage' refers to but if it's changing the network settings that does nothing for me. Tried network-buffer-threshold at 1, 2, 3, 4, 5, 10, 20, 50, 100, 999, no effect. Didn't even have a 'buffer-size' setting but tried adding one at various levels, no effect. However there is good news; TBerk's fix - using a competing utility - works perfectly. By abandoning totem altogether and using gecko-mediaplayer plugin with mplayer, streaming works flawlessly, as it should do, and does everywhere else, including buffering on pause, intelligent starting, et c. Why does gnome default to totem and its browser plugin over gnome-mplayer and its plugin? Not sure who to ask about this but it seems like the switch should be made.