GNOME Bugzilla – Bug 771088
decodebin3: Don't send duplicated stream-start event
Last modified: 2017-08-17 10:41:50 UTC
decodebin3: Don't send duplicated stream-start event group-id in stream-start event might be updated in parse_chain_output_probe (). This cause duplicated stream-start twice with identical stream-id and seq-num, but only group-id is different. Although there is no change, stream-start event will be followed by the first buffer.
Created attachment 335149 [details] [review] patch#1
Created attachment 335150 [details] dup_stream_start.log Log for duplicated stream-start event. It's tested by using following mpd http://dash.akamaized.net/dash264/TestCases/5c/nomor/4_1a.mpd And, current DASH demux has mult-period playback problem with playbin3, patch at #Bug 768900 was applied.
After much digging in my git history and branches ... I can't remember why I added. Let's remove the event propagation in master and see how it fares.
Comment on attachment 335149 [details] [review] patch#1 commit 06cf7440ce28d42768b0a980d67fc6f53c6cb7b9 (HEAD -> master, origin/master, origin/HEAD) Author: Seungha Yang <sh.yang@lge.com> Date: Fri Sep 9 10:29:01 2016 +0900 decodebin3: Don't send duplicated stream-start event group-id in stream-start event might be updated in parse_chain_output_probe (). This cause duplicated stream-start twice with identical stream-id and seq-num, but only group-id is different. Although there is no change, stream-start event will be followed by the first buffer. https://bugzilla.gnome.org/show_bug.cgi?id=771088