Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Politics
Date: Wed, 22 Dec 2021 20:54:11 +0100
Message-ID: <20211222195411.GD2829255@pb2> (raw)
In-Reply-To: <DM8P223MB0365ADDAC6BF8E3EBD7C7094BA7D9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 2829 bytes --]

On Wed, Dec 22, 2021 at 01:29:04PM +0000, Soft Works wrote:
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> > Niedermayer
> > Sent: Monday, December 20, 2021 4:24 PM
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] Politics
> > 
> > I am not sure the direction from which you approuch this is going to
> > increase the chances this patch has.
> > 
> > All stream types in libavformat/codec are timebase based, that was
> > done because its exact (for some definition of exact at least)
> > 
> > I think you should argue why this is the best way forward not why its
> > not too bad
> > 
> > also in a few places where a fixed timebase is used ffmpeg uses
> > AV_TIME_BASE_Q which is micro not milli seconds. That suddenly
> > allows exactly addressing individual frames and audio samples.
> > And it should be easy to change to from ms, its just a *1000
> > it would weaken the precission argument
> 
> For the final chapter of this story, let us return to the original 
> subject which I would summarize like:
> 

[...]

> I think I know better and therefore insist 
> on having a higher precision and/or flexible timebase for subtitle 
> timings, otherwise I won't accept the patchset"

I didnt say any of this

what is the case is that FFmpeg tries to use flexible timebases 
for everything. And also we try to be exact
I have said nothing about accepting or rejecting this patchset,
nor have i really made my mind up on how i would vote if it comes
to a vote.
What i have made my mind up on is that if someone replaces these
timestamps with higher precission or exact ones i would support it.

Also i do want someone to work on and improve subtitles
in FFmpeg. iam not your oponent here. I do want you to stay and
continue to contribute. But the area you picked certainly is
one where people have strong oppinions and its a big change as
well. I would suggest to keep a cool head and not give up yet.
Find out exatly what the people who objected want and if you can
find some compromise that makes everyone ok with it


> 
> Let's look at the concern first: The concern is about that with 
> a subtitle precision of milliseconds (let's say milli, even
> though we actually have microseconds), it would not be possible

Not sure i understand you but the code you add to AVFrame says "ms" and 
thats milli not micro, 
the prefix for micro is the SI system is μ or u if you want ASCII

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2021-12-22 19:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 14:06 Daniel Cantarín
2021-12-20 15:23 ` Michael Niedermayer
2021-12-22 13:29   ` Soft Works
2021-12-22 19:54     ` Michael Niedermayer [this message]
2021-12-22 20:17       ` Soft Works
  -- strict thread matches above, loose matches on Subject: below --
2021-12-20 16:27 Daniel Cantarín
2021-12-20 13:48 Daniel Cantarín
     [not found] <8dbfd345-c661-459e-b242-94830107eae3@www.fastmail.com>
     [not found] ` <DM8P223MB0365510C72E8CFEF027FF97FBA749@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
     [not found]   ` <MqpKkF_--7-2@lynne.ee>
     [not found]     ` <DM8P223MB0365FEDCCEFB370D20979CF5BA749@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
     [not found]       ` <c2f7048d-a1b6-253e-8a50-7fdf9a34ada3@canta.com.ar>
     [not found]         ` <DM8P223MB036596CACBB6509CB1AE78CBBA759@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
     [not found]           ` <CAPYw7P64=axtAC0-8Ux+1d+f8WEseuWk9OkhmbAnNWp-eRpq8A@mail.gmail.com>
2021-12-15 13:34             ` Soft Works
2021-12-18 10:26               ` Paul B Mahol
2021-12-18 11:34                 ` Soft Works
2021-12-18 13:32                   ` Lynne
2021-12-18 14:28                     ` Soft Works
2021-12-18 15:16                       ` Lynne
2021-12-18 15:43                         ` Soft Works
2021-12-18 17:53                           ` Lynne
2021-12-18 18:16                             ` Daniel Cantarín
2021-12-18 18:30                               ` Hendrik Leppkes
2021-12-18 18:49                                 ` Soft Works
2021-12-18 20:05                                 ` Daniel Cantarín
2021-12-18 20:41                                   ` Soft Works
2021-12-19 15:16                                     ` Michael Niedermayer
2021-12-19 18:23                                       ` Soft Works
2021-12-19 18:31                                         ` Soft Works
2021-12-20 14:49                                           ` Michael Niedermayer
2021-12-20 22:35                                             ` Soft Works
2021-12-20 23:20                                               ` Soft Works
2021-12-21 18:38                                                 ` Michael Niedermayer
2021-12-22 10:23                                                   ` Soft Works
2021-12-18 17:59                           ` Daniel Cantarín
2021-12-18 15:41                     ` Daniel Cantarín

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=20211222195411.GD2829255@pb2 \
    --to=michael@niedermayer.cc \
    --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