From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Marth64 <marth64@proxyid.net> Subject: Re: [FFmpeg-devel] [PATCH v2] libavformat: add RCWT closed caption muxer Date: Sun, 7 Jan 2024 13:02:19 +0100 Message-ID: <ZZqSy0F+7SIvvmYJ@mariano> (raw) In-Reply-To: <20240106214105.1557632-1-marth64@proxyid.net> On date Saturday 2024-01-06 15:41:05 -0600, Marth64 wrote: > Signed-off-by: Marth64 <marth64@proxyid.net> > > Thank you for the good feedback and review. Most feedback is addressed. > > > nit: no need to shift > I left this alone only since I see it being done this way in lavf/ccfifo > and other documentation. I assumed it could be doing the shift for a reason, > but I can study further why if you think it shouldn't shift. > > > I don't remember if new elements addition entails a minor library bump (probably it should) > I reviewed APIchangelog and didn't see similar type of bumps for adding to allformats. > The publically exposed codec ID has been in ffmpeg for a long time. > But I am happy to patch in a version bump with your confirmation. > > Much appreciated, > Marth64 > > --- > Changelog | 1 + > doc/muxers.texi | 40 ++++++++++ > libavformat/Makefile | 1 + > libavformat/allformats.c | 1 + > libavformat/rcwtenc.c | 166 +++++++++++++++++++++++++++++++++++++++ > tests/fate/subtitles.mak | 3 + > tests/ref/fate/sub-rcwt | 1 + > 7 files changed, 213 insertions(+) > create mode 100644 libavformat/rcwtenc.c > create mode 100644 tests/ref/fate/sub-rcwt > > diff --git a/Changelog b/Changelog > index 5b2899d05b..3d60f688ca 100644 > --- a/Changelog > +++ b/Changelog > @@ -18,6 +18,7 @@ version <next>: > - lavu/eval: introduce randomi() function in expressions > - VVC decoder > - fsync filter > +- Raw Captions with Time (RCWT) closed caption demuxer demuxer -> muxer? > > version 6.1: > - libaribcaption decoder > diff --git a/doc/muxers.texi b/doc/muxers.texi > index 7b705b6a9e..0bdeaeeaf3 100644 > --- a/doc/muxers.texi > +++ b/doc/muxers.texi > @@ -2232,6 +2232,46 @@ Extensions: thd > > SMPTE 421M / VC-1 video. > > +@anchor{rcwt} > +@section rcwt > + > +Raw Captions With Time (RCWT) is a format native to ccextractor, a commonly > +used open source tool for processing 608/708 closed caption (CC) sources. > +It can be used to archive the original, raw CC bitstream and to produce > +a source file for later CC processing or conversion. As a result, > +it also allows for interopability with ccextractor for processing CC data > +extracted via ffmpeg. The format is simple to parse and can be used > +to retain all lines and variants of CC. > +This muxer implements the specification as of 2024-01-05, which has > +been stable and unchanged for 10 years as of this writing. > + > +This muxer will have some nuances from the way that ccextractor muxes RCWT. > +No compatibility issues when processing the output with ccextractor > +have been observed as a result of this so far, but mileage may vary > +and outputs will not be a bit-exact match. > + > +Specifically, the differences are: > +@enumerate > +@item > +This muxer will identify as "FF" as the writing program identifier, so > +as to be honest about the output's origin. > +@item > +ffmpeg's MPEG-1/2, H264, HEVC, etc. decoders extract closed captioning > +data differently than ccextractor from embedded SEI/user data. > +For example, DVD captioning bytes will be translated to ATSC A53 format. > +This allows ffmpeg to handle 608/708 in a consistant way downstream. > +This is a lossless conversion and the meaningful data is retained. > +@item > +This muxer will not alter the extracted data except to remove invalid > +packets in between valid CC blocks. On the other hand, ccextractor > +will by default remove mid-stream padding, and add padding at the end > +of the stream (in order to convey the end time of the source video). > +@end enumerate This part is probably a bit too technical for user documentation, especially for the details related to the implmentation (which might change), so probably can/should be left out. You might keep the link to the file format below though. [...] LGTM otherwise. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-01-07 12:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-06 2:14 [FFmpeg-devel] [PATCH] " Marth64 2024-01-06 12:33 ` Stefano Sabatini 2024-01-06 21:41 ` [FFmpeg-devel] [PATCH v2] " Marth64 2024-01-07 12:02 ` Stefano Sabatini [this message] 2024-01-07 15:07 ` [FFmpeg-devel] [PATCH v3] " Marth64 2024-01-07 15:24 ` Stefano Sabatini 2024-01-14 14:16 ` Stefano Sabatini 2024-01-14 16:57 ` Marth64 2024-01-15 4:25 ` Xiang, Haihao 2024-01-15 4:33 ` Marth64 2024-01-15 4:38 ` [FFmpeg-devel] [PATCH] rcwtenc: add sub-rcwt fate test ref Marth64 2024-01-15 5:06 ` Xiang, Haihao 2024-01-15 5:20 ` Marth64 2024-01-15 23:55 ` Marth64
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZZqSy0F+7SIvvmYJ@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=marth64@proxyid.net \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git