From: "Bernd Dürrer" <Bernd.Duerrer@gmx.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: remove hack breaking creation time parsing
Date: Wed, 12 Apr 2023 10:10:20 +0200
Message-ID: <trinity-58fd0ab7-fe68-45d6-9251-fcf8cafc1cff-1681287020471@3c-app-gmx-bs18> (raw)
In-Reply-To: <b97dcfa1-9746-49f7-13bd-cbc75f84a71e@passwd.hu>
On Tue, 11 Apr 2023, Marton Balint wrote:
>> As defined in ISO/IEC 14496-12, clause 8.2, "creation_time is an integer
>> that declares the creation time of the presentation (in seconds since
>> midnight, Jan. 1, 1904, in UTC time)". This is the date when the content
>> was created (which may have been on photographic film), and not when it
>> was encoded as a digital file.
>
> I don't think that is true, it is not clear from the specs at best. The
> creation time of the presentation can just as easily refer to the file
> itself, not the content. Feel free to reencode something with a commercial
> encoder, I would be suprised if creation time was kept.
I agree that it may be debated for what purpose the creation_time tag has been intended by the authors of the standard, and that this tag may be used inconsistently by different encoders. However, it remains a fact that ffmpeg does not support the date range defined in the standard, and that ffmpeg writes an incorrect date to the file if a date before 1970 is provided. This is a bug that should be amended.
Kind regards,
Bernd
_______________________________________________
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:[~2023-04-12 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:46 Bernd Dürrer
2023-04-11 18:15 ` Marton Balint
2023-04-12 8:10 ` Bernd Dürrer [this message]
2023-04-12 8:38 ` "zhilizhao(赵志立)"
2023-04-13 10:13 ` Bernd Dürrer
-- strict thread matches above, loose matches on Subject: below --
2023-04-08 18:37 Marton Balint
2023-04-08 21:14 ` Michael Niedermayer
2023-04-09 13:49 ` Marton Balint
2023-04-09 14:06 ` Anton Khirnov
2023-04-09 17:20 ` Michael Niedermayer
2023-04-09 17:52 ` Marton Balint
2023-04-09 21:27 ` Michael Niedermayer
2023-04-10 19:11 ` Marton Balint
2023-04-10 22:34 ` Michael Niedermayer
2023-04-10 2:44 ` "zhilizhao(赵志立)"
2023-04-10 14:31 ` Michael Niedermayer
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=trinity-58fd0ab7-fe68-45d6-9251-fcf8cafc1cff-1681287020471@3c-app-gmx-bs18 \
--to=bernd.duerrer@gmx.de \
--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