On Mon, Jan 06, 2020 at 09:51:34PM +0000, Mark Thompson wrote: > On 28/12/2019 01:38, Limin Wang wrote: > > On Fri, Dec 27, 2019 at 11:32:40PM +0000, Mark Thompson wrote: > >> On 26/12/2019 01:01, [email protected] wrote: > >>> From: Limin Wang <[email protected]> > >>> > >>> Signed-off-by: Limin Wang <[email protected]> > >>> --- > >>> update to add keyframe NAL checking as H.264 patch for global header > >> > >> This case is much easier in H.265, though - the extradata can include SEI > >> which applies globally, so just put it there rather than splicing it into > >> the stream. > > > > Mark, are you say put the user data into the extradata? For my case, the > > string > > in the user data will be updated for every key frame runtime. > > Yes - if you put it in the extradata then it isn't necessary to update any > frames in the stream at all. That ends up being far simpler for > global-header streams (MP4 / MKV), and in flat streams (Annex B, TS) the > extradata will be spliced in at every seek point by the writer.
Sorry, my description isn't clear before, for my case, The user data may have time related string, so it'll updated for every insertion. Also, it'll be used for real time streaming, RTMP protocol etc. You had to use API to get the function, FFmpeg cli can't test it. > > - Mark > _______________________________________________ > ffmpeg-devel mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". -- Thanks, Limin Wang _______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
