My application is actually to generate a playout library for over the air TV, then implement a captions data path into a sub project that relies on ffmpeg for decode/encode. So I need to not just do archival, but build a library in a usable format. This requires an ingest process for both an edit workflow and playout.
As such, I may be able to work out an edit workflow by using RCWT to make a .bin file, using ccextractor to make an mcc file and importing into an edit suite for transcode. The part I will still be missing is something to take the .ssc file output from Premiere and put it back in the .mp4 container. Embedding seems to be present for some forms of subtitles, but not for a proper captions file generated by MacCaption or Captionmaker which is software I am trying to avoid having to buy as I would much rather those funds go towards development. One solution I guess would be to just require sidecar files for playout which I would prefer not to require. I can look into those solutions off list. MCC files or other formats that support 708 are the ideal, but 608 is all that is required. If anyone else has ideas or interest in developing a more integrated process for ffmpeg, I may still be interested in funding that after I investigate the above solutions off list. Zach On Fri, Feb 7, 2025 at 8:37 AM Marth64 <mart...@proxyid.net> wrote: > Added bit: RCWT will preserve more than what the SCC muxer does > You can also convert the RCWT back to SCC with a single EIA608 field > array, again with either tool > _______________________________________________ > 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".