Fix "clear" implementation by introducing sync points in data stream.vdr-xine-version-802

vdr-xine used a padding packet to push out any remaining data before
input_vdr executed "clear" to drop that data. But depending on the way
how input_vdr is connected to vdr-xine it could happen that the padding
packet reached input_vdr after executing "clear" and therefore "clear"
didn't work as expected.
To fix this issue, sync points are introduced by making the padding
packets "unique" in the stream. input_vdr will now drop all data up to
the sync point packet. So even if the padding packet arrives later than
the "clear" command, only data following the sync point will be fed to
the demuxer.

--HG--
extra : transplant_source : %A1%5E%8C%E1vmW%98D%1EW%A7%AF%B4V%5D%84%26%D0%DA

1 files changed, 2 insertions, 1 deletions

diff --git a/include/xine/vdr.h b/include/xine/vdr.h
index 5102d7f77..a2a3e800f 100644
--- a/include/xine/vdr.h
+++ b/include/xine/vdr.h
@@ -22,7 +22,7 @@
 #define __VDR_H
 
 
-#define XINE_VDR_VERSION 801
+#define XINE_VDR_VERSION 802
 
 
 enum funcs
@@ -270,6 +270,7 @@ typedef struct __attribute__((packed)) data_clear_s
 
   int32_t n;
   int8_t s;
+  uint8_t i;
 }
 data_clear_t;