On Mon, Jun 08, 2020 at 11:38:15PM +0000, Daniel Loman wrote: > Let me know if there is anything I can do to help get this included in 4.3 :)
Before included in 4.3, I think first it's had to be reviewed and accepted into master. I give my review comment for the patch. > ________________________________________ > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> on behalf of Brad Hards > <br...@frogmouth.net> > Sent: Monday, June 8, 2020 4:14 PM > To: 'FFmpeg development discussions and patches' > Subject: Re: [FFmpeg-devel] release/4.3 > > (CAUTION)This email originated outside Toyon. Do not click links or open > attachments unless you recognize the sender and know the content is safe. > > > My apologies for the broken link. > http://ffmpeg.org/pipermail/ffmpeg-devel/2020-June/263793.html > > I have no association with the original author, but it’s a fairly small > change (just exposes existing code) that helps compliance with MISB ST0604. > That standard (available at > https://gwg.nga.mil/misb/docs/standards/ST0602.4.pdf) requires insertion of a > timestamp in the SEI side data. > > I'm a contributor to an open source project (jMISB) which provides > implementations of some of those MISB standards, based on ffmpeg via the > bytedeco javacpp-presets project > (https://github.com/bytedeco/javacpp-presets). > > We're currently tracking a non-compliance to the standard > (https://github.com/WestRidgeSystems/jmisb/issues/102) that I would like to > fix. To use that SEI function, I need it exposed in the C++ API to get it > into the java bindings. > > So getting it into 4.3 would help me, and therefore I ask for it to be > included. > > Brad > > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Carl Eugen > Hoyos > Sent: Tuesday, 9 June 2020 8:42 AM > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] release/4.3 > > Am Di., 9. Juni 2020 um 00:39 Uhr schrieb Brad Hards <br...@frogmouth.net>: > > > > Is there any chance that > > https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200601212323.16757 > > -1-dlo m...@toyon.com/ can be included in that? > > The link that you did (not) provide gives a strong reason not to include the > patch. > > Carl Eugen > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org > with subject "unsubscribe". > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". -- Thanks, Limin Wang _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
