Seek functionality in neonhttpsrc

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Seek functionality in neonhttpsrc

deeps8us
For implementing seek functionality, from some links, I could understand that souphttpsrc only supports seeking in bytes, not in time and there should be some other element in pipeline like demux to convert byte format to time format. Does this problem occur if we use neonhttpsrc as well.?
Reply | Threaded
Open this post in threaded view
|

Re: Seek functionality in neonhttpsrc

Mandeep Sandhu


On Dec 18, 2012 5:56 PM, "deepthips" <[hidden email]> wrote:
>
> For implementing seek functionality, from some links, I could understand that
> souphttpsrc only supports seeking in bytes, not in time and there should be

For what 'links' does time seek not work?

We're using souphttpsrc for streaming mp4 (h264/aac) files and time seek works fine.

We're using 0.10.34.

-mandeep

> some other element in pipeline like demux to convert byte format to time
> format. Does this problem occur if we use neonhttpsrc as well.?
>
>
>
> --
> View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Seek-functionality-in-neonhttpsrc-tp4657504.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Seek functionality in neonhttpsrc

Tim-Philipp Müller-2
In reply to this post by deeps8us
On Tue, 2012-12-18 at 04:24 -0800, deepthips wrote:

> For implementing seek functionality, from some links, I could understand that
> souphttpsrc only supports seeking in bytes, not in time and there should be
> some other element in pipeline like demux to convert byte format to time
> format. Does this problem occur if we use neonhttpsrc as well.?

Yes, with most http sources, I'm aware of you can only seek over http in
byte format, i.e. seeking is only supported if the server sends
Content-Length etc. A component in the GStreamer pipeline (a demuxer or
parser, usually), will then transform the seek in TIME format to a seek
to the right BYTE position which can be sent to the server.

However, there are some cases where this doesn't work, and where a seek
in TIME needs to be sent to the http server (e.g. for a DLNA server
that's transcoding on the fly).

I'm not aware of any http sources that support that yet (would also need
demuxer support, though that should hopefully be there already for those
where that's supported, like mpeg*).

Cheers
-Tim

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel