wavparse: When flushing on EOS, don't process more data than the "data" size
authorSebastian Dröge <sebastian@centricular.com>
Wed, 13 Jan 2016 22:40:20 +0000 (23:40 +0100)
committerSebastian Dröge <sebastian@centricular.com>
Wed, 13 Jan 2016 22:42:31 +0000 (23:42 +0100)
commit53c797d6046c131f751c69fe83e9fe65d8e0da95
tree3280be3676861618ce15af43eecf832a4eae57f7
parentbe5f94734a57a13294ea06ada1466d041a5654a9
wavparse: When flushing on EOS, don't process more data than the "data" size

Even if we have more data queued up when flushing than the size of the data
chunk, don't process and output it. If the data size is known, this likely
contains another chunk (e.g. an INFO chunk) or things like ID3 tags. Just
outputting them as if they were data is going to cause unexpected behaviour
and unpleasant audio noises.
gst/wavparse/gstwavparse.c