Hi,
can somebody explain me what's exactly happening when i'm doing a seek
command on a pipeline with an rtspsrc? In what way goes the seekevent
trough the network? (And it's properties like rate, start, stop?)
I'm working on a simple rtsp server, and have some troubles with
seeking. My application is working like this:
- call the seek command on client's pipeline
- the rtspsrc sends a PAUSE rtsp request
- the rtspsrc send a PLAY rtsp request with ntp header from when i
wan't to play (it should be absolute or relative, depeding on what?)
- the server processes the PLAY request and does the seek somehow (if
the server side works with gstreamer, too, what is the correct way to
do this? parse the ntp header and call the seek command?)
- the server sends an OK response with ntp header, but what is the
correct value for this header?
Thanks in advance,
Tibor
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Locked
