From: Devlist Archive <devlist@rlb.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Wed, 28 May 2025 08:20:24 -0700
Message-ID: <CANJxsBmNKNTQzg4QAQdOFWiPM_3=rzNQDJfb+T4A6dK9KKqr_g@mail.gmail.com> (raw)
In-Reply-To: <CANJxsBmxJC8Tm_hFrsT0bjvnHVrAcmySQVOOMgMCGTNSobSV4w@mail.gmail.com>
I have had some work done on captions over on CasparCG, and the dev there
has informed me that Softworkz's Subtitle Filtering or something like it is
a framework that would make solving the embed/extract problem easier for
sidecar and mxf files. The whole set of terminology practice used in this
project of referring to captions as a type of subtitle has been a bit
confusing to me, as I see them as separate data types. I am sorry that has
made it hard to evaluate the various proposed solutions. What progress
needs to be made for Subtitle Filtering, or something like it to be ready
to merge? What are the specific areas that need updated or cleaned up to
allow that to happen? Let's please give specific references to parts of
code instead of talking in generality about the patchset unless there are
structural changes required. I know there is a history here that I am not
fully briefed on, but some structural change like subtitle filtering is
needed to solve the broken state of captions support in ffmpeg.
Zach
On Sun, Feb 9, 2025 at 6:55 PM Devlist Archive <devlist@rlb.org> wrote:
> I believe I have sorted out the embed/extract issues I encountered into a
> formatting issue with the .scc file and lack of eia-608 codec for embedding
> captions. It is possible this might be a result of an oversight regarding
> drop frame or non drop frame time codes with some part of the chain that
> handles extracted captions data. Please discuss the best way to solve
> these issues in the appropriate locations. Once a solution is identified
> let me know if I need to go find sponsorship funds to expedite generating
> the appropriate patches.
>
> https://trac.ffmpeg.org/ticket/11461
>
> https://trac.ffmpeg.org/ticket/11462
>
> On Sun, Feb 9, 2025 at 12:34 PM Soft Works <
> softworkz-at-hotmail.com@ffmpeg.org> wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> > Marth64
>> > Sent: Sunday, February 9, 2025 9:23 PM
>> > To: FFmpeg development discussions and patches <ffmpeg-
>> > devel@ffmpeg.org>
>> > Subject: Re: [FFmpeg-devel] Captions SCC
>> >
>> > On Sun, Feb 9, 2025 at 2:14 PM Soft Works
>> > <softworkz-at-hotmail.com@ffmpeg.org> wrote:
>> > > Numpad alignment 7, LeftMargin=x VertMargin=y
>> >
>> > Yeah, that could work. I forgot about margins. I'll play around with
>> > it.
>>
>> That's the elementary way to position ASS text.
>> Years ago I had a chat with one the libass developers because I didn't
>> want to believe it and thought there must be something else.. 😊
>>
>> 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".
prev parent reply other threads:[~2025-05-28 15:20 UTC|newest]
Thread overview: 54+ 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
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
2025-02-07 23:46 ` Soft Works
2025-02-07 23:58 ` Marth64
2025-02-08 0:10 ` Soft Works
2025-02-08 14:43 ` Devin Heitmueller
2025-02-09 3:39 ` Tom Vaughan
2025-02-09 14:03 ` Devin Heitmueller
2025-02-09 17:41 ` Devlist Archive
2025-02-09 18:41 ` Tom Vaughan
2025-02-09 18:45 ` Soft Works
2025-02-09 19:37 ` Marth64
2025-02-09 20:14 ` Soft Works
2025-02-09 20:23 ` Marth64
2025-02-09 20:33 ` Soft Works
2025-02-10 2:55 ` Devlist Archive
2025-05-28 15:20 ` Devlist Archive [this message]
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='CANJxsBmNKNTQzg4QAQdOFWiPM_3=rzNQDJfb+T4A6dK9KKqr_g@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