From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat: set start_time_realtime when demuxing
Date: Tue, 14 Jun 2022 22:26:00 +0200 (CEST)
Message-ID: <b4c931c6-9bde-f990-c996-eef6a0a2a280@passwd.hu> (raw)
In-Reply-To: <2085463a-c755-6b87-1cd2-ddc78c1e576b@gyani.pro>
On Tue, 14 Jun 2022, Gyan Doshi wrote:
>
>
> On 2022-06-14 01:51 pm, Marton Balint wrote:
>>
>>
>> On Tue, 14 Jun 2022, Gyan Doshi wrote:
>>
>>> Add new flag AVFMT_START_REALTIME for the couple of demuxers that set it
>>> internally.
>>
>> I don't think this is the same semantics.
>>
>> start_time_realtime is the time when the stream was originally captured,
>> and not when the stream was received. So you can't simply use av_gettime()
>> in the demuxers for that field.
>
> I saw that in the rtsp read_packet. I thought of adding a new field but think
> the semantics are close enough to serve the purpose of a rough sync so I
> added the flag for the demuxers that receive origin timestamp.
>
> I can update the doxy to record this difference. Or should I add a new field?
I prefer a new field.
Thanks,
Marton
_______________________________________________
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".
next prev parent reply other threads:[~2022-06-14 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 8:09 Gyan Doshi
2022-06-14 8:21 ` Marton Balint
2022-06-14 9:11 ` Gyan Doshi
2022-06-14 20:26 ` Marton Balint [this message]
2022-06-14 21:48 ` Andreas Rheinhardt
2022-06-15 4:08 ` Gyan Doshi
2022-06-15 4:17 ` Andreas Rheinhardt
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=b4c931c6-9bde-f990-c996-eef6a0a2a280@passwd.hu \
--to=cus@passwd.hu \
--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