From: David Flynn <dav...@rd.bbc.co.uk>

>From the first patch commit:
==
Traditionally, clients were required to wrap the decoder with a TLB,
that stored presentation time vs input picture number; when pulling
a picture, the presentation time would be extracted from the TLB.

Clients may be simplified by allowing schroedinger to do the tagging
based on simple rules:
 - a buffer may be supplied with a tag and free function
 - the tag is associated with the first byte of the buffer data
 - when using the autoparse api, the tag becomes associated with
   the next picture data unit to commence at or after the start of
   the buffer.
 - in cases where the above rule would associate multiple tags
   with one picture, the oldest shall take precedence.
 - tags are made avaliable as a member of the SchroFrame structure.
 - the contents of the tag are transparent to the decoder.
==

Comments welcome.  Before they get pushed upstream i'll add some more
docs and merge them together (depends upon what people say).

..david

David Flynn (4):
  decoder: add void* buffer/frame tagging
  decoder: Add candidate api function schro_decoder_get_picture_tag
  decoder: free tag on picture destruction
  decoder: abstract tagging with SchroDecoderTag

 schroedinger/schrobuffer.c     |    2 +
 schroedinger/schrobuffer.h     |    2 +
 schroedinger/schrobufferlist.c |   58 +++++++++++++++++++++++++++++++++-----
 schroedinger/schrodecoder.c    |   60 ++++++++++++++++++++++++++++++++++++++++
 schroedinger/schrodecoder.h    |   17 +++++++++++
 schroedinger/schroutils.h      |    7 ++++
 6 files changed, 138 insertions(+), 8 deletions(-)


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Schrodinger-devel mailing list
Schrodinger-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/schrodinger-devel

Reply via email to