summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorReinhard Nißl <rnissl@gmx.de>2008-03-02 21:12:01 +0100
committerReinhard Nißl <rnissl@gmx.de>2008-03-02 21:12:01 +0100
commita33991c82965b1cf40c175b7bc9d13488e14cae6 (patch)
treef5fac4e5bf8c2080f47ced0e3f8686ad39b72d63 /NEWS
parente32eab57b9c6d869cdfa41b988e76184f2c5e41b (diff)
downloadxine-lib-a33991c82965b1cf40c175b7bc9d13488e14cae6.tar.gz
xine-lib-a33991c82965b1cf40c175b7bc9d13488e14cae6.tar.bz2
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
Diffstat (limited to 'NEWS')
0 files changed, 0 insertions, 0 deletions