Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
Date: Thu, 5 Jun 2025 00:44:38 +0000
Message-ID: <DM8P223MB0365BEC0B98EC0A10F5ED797BA6FA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB0365125FF134CCB3AD39337ABA6CA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Mittwoch, 4. Juni 2025 20:35
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
> 
> Objections Summary
> ==================
> 
> 
> Here's a summary of objections made so far:
> 
> 
> Lynne
> -----
> 
> - Not using picture buffers for subtitle data
>   It's not impossible, just doesn't make much sense
>   I said there wasn't anybody against it anymore in 2022.
>   We can dig up previous conversations, or we can just let
>   the TC decide about it


Here's the thread and specifically the message about the reasonings in 
this regard:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-August/300740.html



> Lynne & Hendrik
> ---------------
> 
> - Claimed that AVFrame's timing fields would be sufficient
>   They can take my $1000 challenge to prove it

Here, Hendrik had asked for an explanation for the extra time fields:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-October/303282.html

My reply:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-October/303285.html

And I had asked later whether it's clarified for him:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-October/303371.html

==> No response

------------


In this conversation, I had stated that no unaddressed objections were 
remaining:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-August/300593.html

I had also said (about the timing fields):

> I had explained the reasons and in conversation on IRC, Lynne was
> no longer insisting on this AFAIR.

I still have the log of those conversations. It's just a lot of text
to go through.
But if Lynne wants to insist that it was any different, then I can
post the full IRC log somewhere.


-----------------------------------

Anton said he would review it:

https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2022-August/300729.html

I posted the explanation he was asking for in a reply.

He never responded. 
I sent 4 or 5 reminders over the subsequent weeks and he didn't respond.

-------------

There were more messages where it was talked about whether any objections
would be remaining and there weren't any responses.

That's the evidence for why I said there were no more objections.


Best regards
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".

      reply	other threads:[~2025-06-05  0:44 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 14:20 softworkz .
2025-06-03 16:00 ` Lynne
2025-06-03 16:02   ` James Almer
2025-06-03 16:40     ` Nicolas George
2025-06-03 16:48       ` James Almer
2025-06-03 16:51         ` Devlist Archive
2025-06-03 17:59           ` Nicolas George
2025-06-03 16:12   ` softworkz .
2025-06-03 16:12   ` Devin Heitmueller
2025-06-03 16:43   ` Nicolas George
2025-06-03 17:07     ` softworkz .
2025-06-03 17:15       ` Devlist Archive
2025-06-03 17:16         ` Devlist Archive
2025-06-03 17:19         ` softworkz .
2025-06-04 15:49       ` Rémi Denis-Courmont
2025-06-04 17:13         ` softworkz .
2025-06-04 17:25           ` Nicolas George
2025-06-04 17:31             ` softworkz .
2025-06-04 19:02         ` softworkz .
2025-06-03 17:17   ` softworkz .
2025-06-03 16:28 ` softworkz .
2025-06-03 18:02 ` Hendrik Leppkes
2025-06-03 18:34   ` Zach Swena
2025-06-04  0:01     ` Michael Niedermayer
2025-06-04  7:13     ` Nicolas George
2025-06-04  7:22       ` Diederick C. Niehorster
2025-06-04  7:25         ` Nicolas George
2025-06-04 17:24       ` softworkz .
2025-06-04 17:29         ` Nicolas George
2025-06-04 17:33           ` softworkz .
2025-06-04 17:35             ` Nicolas George
2025-06-04 17:40               ` softworkz .
2025-06-04 17:44                 ` Nicolas George
2025-06-04 17:54                   ` softworkz .
2025-06-04 17:57                     ` Nicolas George
2025-06-04 18:11                       ` softworkz .
2025-06-04 18:12                         ` Nicolas George
2025-06-04 18:17                           ` softworkz .
2025-06-04 20:42       ` Michael Niedermayer
2025-06-05  0:17         ` softworkz .
2025-06-06 14:32         ` Nicolas George
2025-06-06 14:50           ` Devin Heitmueller
2025-06-08 13:10             ` Nicolas George
2025-06-06 16:54           ` softworkz .
2025-06-07 16:19       ` softworkz .
2025-06-07 17:25         ` Kieran Kunhya via ffmpeg-devel
2025-06-07 17:45           ` softworkz .
2025-06-03 19:13   ` softworkz .
2025-06-04  7:34     ` Nicolas George
2025-06-04  1:16   ` softworkz .
2025-06-04  7:36   ` Nicolas George
2025-06-03 19:23 ` softworkz .
2025-06-04  7:33   ` Nicolas George
2025-06-04 18:35 ` softworkz .
2025-06-05  0:44   ` softworkz . [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=DM8P223MB0365BEC0B98EC0A10F5ED797BA6FA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.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