From: Devlist Archive <devlist@rlb.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Captions SCC Date: Fri, 7 Feb 2025 12:20:34 -0800 Message-ID: <CANJxsB=yMDcTn9N1pL3GkGMUApQ7-i9HVWVm-Faf3uk9TPmv4A@mail.gmail.com> (raw) In-Reply-To: <DM8P223MB0365403FA26246C3812777C4BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > > One thing worth noting is that the filenames in that Google drive > don't match up with the example commands you've provided. I would > recommend if you decide to open a ticket to either rename the files or > change the commands so whoever tries to reproduce the issue knows they > are working with the exact same files. The legal requirements are to pass the captions received, not generate captions at least for the small entities like us. As such all the encoding should be done by the content producer as long as the data isn't corrupted. One thing worth noting is that the filenames in that Google drive > don't match up with the example commands you've provided. I would > recommend if you decide to open a ticket to either rename the files or > change the commands so whoever tries to reproduce the issue knows they > are working with the exact same files. Here are some updated commands for the files that are there now and cleaned up from the extra anothergui and windows path junk. The commands are in the text file also. (one file still uploading) Embed: ffmpeg -i AIM-2301_premiereExport.mp4 -i AIM-2301_premiereExport.scc -map 0:v -map 0:a -map 1 -c:v copy -c:a copy -c:s mov_text -metadata:s:s:0 language=eng AIM-2301_ffmpegEmbed.mp4 Extract: ffmpeg.exe -f lavfi -i "movie=AIM-2301.mp4"[out+subcc] -map 0:1 -c:s copy AIM-2301_ffmpeg_extracted.scc On Fri, Feb 7, 2025 at 11:57 AM Soft Works < softworkz-at-hotmail.com@ffmpeg.org> wrote: > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Devlist Archive > > Sent: Friday, February 7, 2025 8:52 PM > > To: FFmpeg development discussions and patches <ffmpeg- > > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] Captions SCC > > > > > > > > Unfortunately, there's no bug which could be "fixed". > > > For a proper solution, a CEA-608 ENcoder is required. > > > And more - like already said. > > > > > > Is a CEA-608 encoder actually required for a frame rate change, or is > > it > > possible to just redistribute the packets of the 608 stream in a > > manner > > that does not involve loss or reordering of data? > > As far as I understand, this is about professional public > television broadcast, which needs to meet the regulations > and work on any TV set out there. > So even when you fiddle something together that works on some > software players - you're still not done (and you would > have nothing achieved at all). > > sw > _______________________________________________ > 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". > _______________________________________________ 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:[~2025-02-07 20:20 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-06 10:19 Devlist Archive 2025-02-06 12:57 ` Jack Lau 2025-02-07 5:12 ` Devlist Archive 2025-02-07 7:48 ` Soft Works 2025-02-07 7:58 ` Jack Lau 2025-02-07 8:16 ` Soft Works 2025-02-07 8:26 ` Jack Lau 2025-02-07 9:11 ` Soft Works 2025-02-07 9:44 ` Jack Lau 2025-02-07 15:38 ` Marth64 2025-02-07 16:05 ` Devlist Archive 2025-02-07 16:18 ` Marth64 2025-02-07 16:37 ` Marth64 2025-02-07 16:42 ` Devlist Archive 2025-02-07 18:05 ` Devin Heitmueller 2025-02-07 18:32 ` Devlist Archive 2025-02-07 19:03 ` Devin Heitmueller 2025-02-07 19:31 ` Devlist Archive 2025-02-07 19:44 ` Soft Works 2025-02-07 19:51 ` Devlist Archive 2025-02-07 19:55 ` Devin Heitmueller 2025-02-07 19:56 ` Devin Heitmueller 2025-02-07 19:56 ` Soft Works 2025-02-07 20:20 ` Devlist Archive [this message] 2025-02-07 19:52 ` Devin Heitmueller 2025-02-07 19:54 ` Devlist Archive 2025-02-07 17:37 ` Rémi Denis-Courmont 2025-02-07 17:31 ` Rémi Denis-Courmont 2025-02-07 17:47 ` Soft Works 2025-02-07 18:36 ` Tom Vaughan 2025-02-07 18:54 ` Soft Works 2025-02-07 20:09 ` Tom Vaughan 2025-02-07 20:49 ` Devlist Archive 2025-02-07 20:58 ` Soft Works 2025-02-07 21:05 ` Devlist Archive 2025-02-07 21:08 ` Devin Heitmueller 2025-02-07 22:02 ` Marth64 2025-02-07 22:18 ` Marth64 2025-02-07 23:12 ` Devin Heitmueller
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='CANJxsB=yMDcTn9N1pL3GkGMUApQ7-i9HVWVm-Faf3uk9TPmv4A@mail.gmail.com' \ --to=devlist@rlb.org \ --cc=ffmpeg-devel@ffmpeg.org \ /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