[vlc-devel] [PATCH 1/1] Supporting ONVIF PRofile-G recording playback

Ross Finlayson finlayson at live555.com
Tue Aug 5 19:39:52 CEST 2014


At this point perhaps it's worth stepping back and asking: Where do these 'absolute' times come from?  I.e., What are you doing (or planning on doing) in VLC to get these 'absolute' times?

If you're planning on getting these times simply by 'seeking' using VLC's GUI (i.e., using its slider), then those are *not* absolute times - they are relative times.  That's explicitly what 'npt' ("Normal Play Time") means (see RFC 2326, section 3.6, paragraph 3).  Therefore, if you're getting these times only by 'seeking' using VLC's GUI, then "range: npt" strings are *exactly* what you want - and therefore you should not be considering making *any* changes to VLC.

Note that (quoting from RFC 2326, section 10.5, final paragraph) "A media server only supporting playback MUST support the npt format and MAY support the clock and smpte formats".  Therefore, if your server does not support "range: npt" strings, then it is *not* standards compliant, and VLC (nor any other media player client) is under no obligation to support it.  Note that the Internet standard here is RFC 2326 (IETF), not 'ONVIF'.  ('ONVIF' is an 'industry consortium', not a standards organization.)

If, on the other hand, you're planning on getting these 'absolute' times in some way other than by using VLC's GUI slider, then presumably you can arrange to generate the appropriate (ISO 8601 format) string then, assign it to some "char*" variable, and modify VLC's "live555" access module to check whether that variable is non-NULL - and then call the appropriate version of "sendPlayCommand()".

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20140805/7580382f/attachment.html>


More information about the vlc-devel mailing list