GNOME Bugzilla – Bug 792263
dashdemux: do not parse mpd file and setup streams if updated mpd file is not changed at all
Last modified: 2018-11-03 14:17:17 UTC
if updated mpd file is the same with last one, not changed at all, then no bother to parse mpd file and setup streams.
Created attachment 366407 [details] [review] do not parse mpd file and setup streams if updated mpd file is not changed at all
please review :)
Hi Jun, I am trying to understand the changes that you made. Is there any particular stream that you used? If so can you please provide the link or should use any one stream from https://github.com/Dash-Industry-Forum/dash-live-source-simulator/wiki/Test-URLs?
hi sraut, basically, it is handling with $Number$-template type, like http://vm2.dashif.org/livesim/testpic_2s/Manifest.mpd. But unlike the above one, some content provider set 'minimumUpdatePeriod' a short period, but actually the mpd file is not changed at all. Currently, each updated mpd file will be parsed and stream are set up again, event nothing changed at all. The patch is trying to deal with such scenario.
Hi Jun, Thanks for the explanation. I am able to change the 'minimumUpdatePeriod' to 2 seconds by changing the above mpd URL to: http://vm2.dashif.org/livesim/mup_2/testpic_2s/Manifest.mpd (adding mup_x before /testpic_2s). However, couldn't find the following line: "Updated mpd is not changed at all, do nothing" in the logs. Can you please let me know what value should 'minimumUpdatePeriod' have in order to see the changes? Thanks
hi sraut, the mpd's 'publishTime' is changed, so while doing memcmp, it is judged as changed. Content provider has different behaviors. This patch can cover $Number$-template type with not thing changed at all. I do not remember which stream generator vendor has such behavior, but we do have met a lot:)
Hi Jun, Got it. Thanks.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/647.