Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: facefunk <facefunk@fcfnk.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error?
Date: Thu, 21 Jul 2022 13:31:37 +0100
Message-ID: <CAOxBKoSiZ1Rko7b9Ao3T=Z8OQHCgKvzEY9Toz-1u1tuXc-OG_w@mail.gmail.com> (raw)
In-Reply-To: <tencent_E4E0AB734EF470F32D899A18403E9A009F08@qq.com>

Wow! Thanks!

That really works. I had no idea we could just play with timescale like
that.

On Wed, 20 Jul 2022 at 13:41, "zhilizhao(赵志立)" <quinkblack@foxmail.com>
wrote:

>
>
> > On Jul 20, 2022, at 8:18 PM, facefunk <facefunk@fcfnk.com> wrote:
> >
> > It's commonly the case with forced subtitle tracks that samples are more
> > than INT_MAX microseconds (35m47.48s) apart. This being the case, packet
> > duration will be deemed out of range by check_pkt and the packet dts set
> to
> > an incorrect value, even if pkt->duration is actually valid.
> >
> > I had begun working out how to inject extra packets to satisfy this check
> > but I thought I would ask. Is this check necessary for mov_text packets?
>
> I think so, it’s still limited by the 32bits sample_delta in stts.
>
> On the other hand, I have an idea that a timescale like 100 can be used in
> that case, which is 2^31/100/3600 = 5965 hours.
>
> > _______________________________________________
> > 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".
>
_______________________________________________
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:[~2022-07-21 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 12:18 facefunk
2022-07-20 12:41 ` "zhilizhao(赵志立)"
2022-07-21 12:31   ` facefunk [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='CAOxBKoSiZ1Rko7b9Ao3T=Z8OQHCgKvzEY9Toz-1u1tuXc-OG_w@mail.gmail.com' \
    --to=facefunk@fcfnk.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