After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628052 - [playbin2] Stuttering when reading TS stream by http
[playbin2] Stuttering when reading TS stream by http
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.30
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-26 18:20 UTC by pacopad
Modified: 2011-01-03 01:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pacopad 2010-08-26 18:20:03 UTC 
I got a problem when i read TS stream by http, the video launch then hangs every 5 seconds. I got no problem when i read the video from a mount point that point to the same server. 

I can read MP4 stream by http without problems too:

gst-launch -v playbin2 uri=http://192.168.1.65/Aliens.ts => stutterings
gst-launch -v playbin2 uri=/mnt/smb/Aliens.ts => OK
gst-launch -v playbin2 uri=http://192.168.1.65/60.mp4 => OK

i got the problems with all my ts streams that contain high bitrate H264 tracks (>4MB/S)

Thank you  
Pacopad
Comment 1 Tim-Philipp Müller 2010-10-08 16:45:54 UTC 
It sounds like the http connection isn't fast enough, and that's why it's rebuffering all the time?

What about:

 gst-launch -v playbin2 uri=pushfile:///mnt/smb/Aliens.ts

(the pushfile:// uri support is in gst-plugins-good's "debug" plugin)

Moving to playbin2 for now, but issue is probably something else (though arguably playbin2's' buffering should be smarter anyway in cases like this, ie. increase the buffer time if it constantly has to rebuffer, so one can see more in one go than just a few seconds?).
Comment 2 Fabio Durán Verdugo 2010-11-23 04:26:46 UTC 
any news?
Comment 3 Fabio Durán Verdugo 2011-01-03 01:59:40 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!