Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Politics
Date: Wed, 22 Dec 2021 20:17:41 +0000
Message-ID: <DM8P223MB0365A048AB5DD88B75097F6DBA7D9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20211222195411.GD2829255@pb2>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Wednesday, December 22, 2021 8:54 PM
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Politics
> 
> 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


And you weren't meant at all.
(you're actually one of the persons I'm respecting the most) 

Sorry for the misunderstanding. I should have replied to one 
of the earlier messages. I thought the fictional quote would 
make it clear who is meant.


> > 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

subtitle_pts is AV_TIMEBASE_Q.

I had recently suggested to change the other fields (subtitle_start_time
and subtitle_end_time to AV_TIMEBASE_Q as well, to have all subtitle 
timing fields at the same base.

Kind regards,
softworkz
_______________________________________________
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 20:17 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
2021-12-22 20:17       ` Soft Works [this message]
  -- 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=DM8P223MB0365A048AB5DD88B75097F6DBA7D9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --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