From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: fix implementation of updated input start time
Date: Fri, 14 Oct 2022 19:07:49 +0530
Message-ID: <ccddfc0e-8d14-c2f0-10d6-6978de08d76b@gyani.pro> (raw)
In-Reply-To: <CAEu79SYHJBFw1OEABao86fWZsmhroC_2b+Ouu2XXcfE2=AKZ0w@mail.gmail.com>
On 2022-10-14 06:49 pm, Jan Ekström wrote:
> On Tue, Sep 27, 2022 at 7:41 AM Gyan Doshi <ffmpeg@gyani.pro> wrote:
>> The current adjustment of input start times just adjusts the tsoffset.
>> And it does so, by resetting the tsoffset to nullify the new start time.
>> This leads to breakage of -copyts, ignoring of user_ts_offset, breaking
>> of -isync as well as breaking wrap correction.
>>
>> Fixed by taking cognizance of these parameters, and by correcting start
>> times just before sync offsets are applied.
> Out of interest and sorry for not testing this myself: does this
> improve the current state of affairs with itsoffset with discontinuous
> inputs like MPEG-TS?
I just recompute the tsoffset the same way but with the effective new
start time.
> Until now the offset was put together with a whole bunch of other
> things, which led to logic which was supposed to only start the input
> at PTS=0 to also take out the configured itsoffset at the same time
> (since both the user defined offset as well as the format start time
> offset were both chunked into the same thing).
That's not my experience.
If the itsoffset is 5 and the first packet timestamp is 40, then only
the 40 is negated and the packet is relayed with a ts of 5.
Isn't that what's expected?
Regards,
Gyan
>
> Cheers,
> Jan
> _______________________________________________
> 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".
prev parent reply other threads:[~2022-10-14 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 4:40 Gyan Doshi
2022-10-02 19:46 ` Gyan Doshi
2022-10-04 9:11 ` Anton Khirnov
2022-10-12 6:35 ` Gyan Doshi
2022-10-12 16:20 ` Anton Khirnov
2022-10-14 4:22 ` Gyan Doshi
2022-10-14 13:19 ` Jan Ekström
2022-10-14 13:37 ` Gyan Doshi [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=ccddfc0e-8d14-c2f0-10d6-6978de08d76b@gyani.pro \
--to=ffmpeg@gyani.pro \
--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