[Bug 758928] play https mp4 gst blocking

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=758928

--- Comment #5 from Athanasios Oikonomou <athoik at gmail.com> ---
Playing the file locally there is no problem. I think that suggests that
problem is somewhere else, right? (eg souphttpsrc?)

# GST_DEBUG_NO_COLOR=1 GST_DEBUG=dvbvideosink:4 gst-launch-1.0 playbin
uri=file:///media/usb/video-sd.mp4
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
WARNING: from element /GstPlayBin:playbin0/GstPlaySink:playsink: No volume
control found
Additional debug info:
/opt/openpli/openpligst/build/tmp/work/mips32el-oe-linux/gstreamer1.0-plugins-base/1.7+gitAUTOINC+71505dfa24-r22/git/gst/playback/gstplaysink.c(2852):
gen_audio_chain (): /GstPlayBin:playbin0/GstPlaySink:playsink:
Volume/mute is not available
0:00:00.672978481   783 0x74f5a060 INFO            dvbvideosink
gstdvbvideosink.c:1370:gst_dvbvideosink_set_caps:<dvbvideosink0> caps =
video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)3,
profile=(string)main,
codec_data=(buffer)014d401effe10018674d401eeca06c1ef37808800000030080000019078b16cb01000468ef85f2,
width=(int)854, height=(int)480, framerate=(fraction)25/1,
pixel-aspect-ratio=(fraction)1/1
0:00:00.674824814   783 0x74f5a060 INFO            dvbvideosink
gstdvbvideosink.c:1472:gst_dvbvideosink_set_caps:<dvbvideosink0> H264 have
codec data..!
0:00:00.675400851   783 0x74f5a060 INFO            dvbvideosink
gstdvbvideosink.c:1498:gst_dvbvideosink_set_caps:<dvbvideosink0> H264 main
profile at 3.0
0:00:00.675992999   783 0x74f5a060 INFO            dvbvideosink
gstdvbvideosink.c:1554:gst_dvbvideosink_set_caps:<dvbvideosink0> MIMETYPE
video/x-h264 -> STREAMTYPE_MPEG4_H264
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "playbin0".
Execution ended after 0:04:46.336278243
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.