I'm sending an updated patch that persists the data within the CVS (between IRAP access units with no_rasl_output_flag=1). If this seems like overkill, we can fallback to Hendrik's suggestion of just sending it once. I did consider this alternative but figured the side data could get lost if some frames were dropped in some part of the filter chain.
On Thu, Feb 4, 2016 at 11:04 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Fri, Feb 5, 2016 at 3:05 AM, Neil Birkbeck <neil.birkb...@gmail.com> wrote: >> According to the ITU-T H.265 v3, in Table D - 1, the persistence scope >> of the mastering display metadata is "The Coded Video Sequence (CVS) >> containing the SEI message". So I guess we want to clear when we start >> the next CVS, so I guess when we see the next IDR frame. >> >> Given that the SEI comes before the IDR, I don't see a great way to do >> this aside from initializing the flag to 2 and decrementing (when > 0) >> when we see an IDR. >> > > The usual way I would handle such SEI metadata is just to send the > sidedata once when it appears in the bitstream and not repeat it with > every single frame, and let the user worry about its lifetime. > > - Hendrik > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
0001-lavc-hevc-Parse-SEI_TYPE_MASTERING_DISPLAY_INFO-and-.patch
Description: Binary data
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
