From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] h264 - Late SEI is not implemented
Date: Tue, 23 Jan 2024 18:46:56 -0500
Message-ID: <f9fcfd30-7deb-4ac5-8cee-ed1b02859501@gmail.com> (raw)
In-Reply-To: <2f229822-b310-41ab-9d34-2c47a3be400a@7183.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1132 bytes --]
On 1/23/24 18:21, Harald Linden via ffmpeg-devel wrote:
>
> Is this interesting to you? Do you want me to upload the sample? It
> might be of dubious nature regarding copyright, depending on local
> legislation.
>
> regards
>
> Harald
You can try to truncate the file to the smallest size that reproduces
the issue, for example via something like:
truncate --size=1024 input.mkv
This will set the file size of input.mkv to 1024 bytes, discarding all
data after it. This is destructive! Make a backup first. It's a good
idea to truncate samples *anyway* regardless of legal ramifications.
I am not a lawyer and this is not legal advice. However, as far as I
understand, Tiny samples for the sake of reproducing technical errors,
that were obtained legally, are likely to be covered by Fair Use in most
jurisdictions. If you aren't sure, you can always double check with the
third party that you obtained the file from. You can also host the
sample elsewhere, such as your own website, or on a site like 0x0.st, if
you are concerned about Videolan's jurisdiction.
- Leo Izen (Traneptora)
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-01-23 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 23:21 Harald Linden via ffmpeg-devel
2024-01-23 23:46 ` Leo Izen [this message]
2024-01-24 1:39 ` Harald Linden via ffmpeg-devel
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=f9fcfd30-7deb-4ac5-8cee-ed1b02859501@gmail.com \
--to=leo.izen@gmail.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