* [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error?
@ 2022-07-20 12:18 facefunk
2022-07-20 12:41 ` "zhilizhao(赵志立)"
0 siblings, 1 reply; 3+ messages in thread
From: facefunk @ 2022-07-20 12:18 UTC (permalink / raw)
To: FFmpeg development discussions and patches
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?
_______________________________________________
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".
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error?
2022-07-20 12:18 [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error? facefunk
@ 2022-07-20 12:41 ` "zhilizhao(赵志立)"
2022-07-21 12:31 ` facefunk
0 siblings, 1 reply; 3+ messages in thread
From: "zhilizhao(赵志立)" @ 2022-07-20 12:41 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> 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".
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error?
2022-07-20 12:41 ` "zhilizhao(赵志立)"
@ 2022-07-21 12:31 ` facefunk
0 siblings, 0 replies; 3+ messages in thread
From: facefunk @ 2022-07-21 12:31 UTC (permalink / raw)
To: FFmpeg development discussions and patches
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".
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-07-21 12:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-20 12:18 [FFmpeg-devel] libavformat/movenc: Is packets being more than INT_MAX apart always an error? facefunk
2022-07-20 12:41 ` "zhilizhao(赵志立)"
2022-07-21 12:31 ` facefunk
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