Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Daniel Cantarín" <canta@canta.com.ar>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Politics
Date: Mon, 20 Dec 2021 11:06:44 -0300
Message-ID: <678798058a84fb8a30dcfaa177431607@canta.com.ar> (raw)


> 
> consider a subtitle track
> consider 2 video tracks for US 30000/1001 fps and EU 25 fps
> 
> the 6th frame in the US track is at  0.2002 sec, the 5th in the EU 
> track at 0.2sec
> 
> 
> if these differ and you want a subtitle to either stop displaying after 
> the
> earlier or begin displaying after the earlier reliably. Then you need a
> timebase that can represent points within each such close encounter of 
> frame
> times.
> 

So, this isn't a subtitle problem if subtitle timings are correct. You
let 0.2002 in the subtitle, players will decide the frame. You want to
match the frame with the content, then you transcode the video properly.
Am I losing something?

Then again, we're of course not discussing players. One may say "that's
not ffmpeg responsability", yet players are 90% of the time the main
reason we have to do any extra work with ffmpeg. If we discuss real
life scenarios, we should be discussing players.

I also fail to see why would somebody want a "frame-perfect" sync
between two videos with different FPS. That's absurd: there's no such
thing as "frame-perfect" in such scenarios. What you would want is video
timings to be honored. That is: FPS conversion to be faithful to video
timings and content. I can imagine such precision dealing with frames
being blurred and having to do lots of fine tuning in order to be able
to perceive a single frame off in subtitles. That would be the real
problematic situation, not any .0002 rounding.

So, I see your example as a case of "what would the player do with that
0.2002 rounding" (in which case, we all know there would be two
different subtitle files/streams with different precision for each
video if it's THAT important) instead of "we need to change the timebase
to something 4 decimals precise multiplier to both videos".

And even if this fails and a frame is interpreted incorrectly in the
player, good luck finding anyone saying anything about it: nobody cares
about a single frame when it's about subtitles. People watching
subtitles are simply not looking at that. This isn't speedrunning: it's
translating and transcribing. People wants to understand what's going on
in the screen, not debugging video frames.

So, I see no "serious subtitle problem" nor anything close to
"unnaceptable" here.

Let's remark, as softworkz say, this are all fantasy scenarios, and the
patchset doesn't show any real precision problem so far. If anyone is
willing to share input files to test such possible precision problems,
I'm willing to do the tests. No such files so far.


_______________________________________________
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-20 14:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 14:06 Daniel Cantarín [this message]
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
  -- 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=678798058a84fb8a30dcfaa177431607@canta.com.ar \
    --to=canta@canta.com.ar \
    --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