From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavf/matroskadec: stop mapping text/plain attachments to AV_CODEC_ID_TEXT
Date: Wed, 8 Jun 2022 03:19:01 +0000
Message-ID: <DM8P223MB03650454F09DE4D7C396CFB4BAA49@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220607115839.18515-1-anton@khirnov.net>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Anton
> Khirnov
> Sent: Tuesday, June 7, 2022 1:59 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH] lavf/matroskadec: stop mapping text/plain
> attachments to AV_CODEC_ID_TEXT
>
> There is no reason to think that an attachment will contain text
> subtitles. In addition attachments are exported in extradata, so the
> AV_CODEC_ID_TEXT decoder would not do anything useful with it anyway.
> ---
> libavformat/matroskadec.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c
> index de73f97aca..cd30b5f7a4 100644
> --- a/libavformat/matroskadec.c
> +++ b/libavformat/matroskadec.c
> @@ -806,7 +806,6 @@ static const CodecMime mkv_image_mime_tags[] = {
> };
>
> static const CodecMime mkv_mime_tags[] = {
> - {"text/plain" , AV_CODEC_ID_TEXT},
> {"application/x-truetype-font", AV_CODEC_ID_TTF},
> {"application/x-font" , AV_CODEC_ID_TTF},
> {"application/vnd.ms-opentype", AV_CODEC_ID_OTF},
> --
Thank you for trying to find a solution for the ffprobe error.
With this patch, text attachments are no longer shown as "text"
but as "none" and ffprobe outputs a warning:
Stream #0:9: Attachment: none
Metadata:
filename : .....
mimetype : text/plain
Unsupported codec with id 0 for input stream 9
Regards,
sw
_______________________________________________
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-08 3:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:58 Anton Khirnov
2022-06-08 3:19 ` Soft Works [this message]
2022-06-08 3:45 ` Soft Works
2022-06-08 6:17 ` Anton Khirnov
2022-06-08 6:39 ` Soft Works
2022-06-08 7:09 ` Anton Khirnov
2022-06-08 7:43 ` Soft Works
2022-06-08 8:04 ` Anton Khirnov
2022-06-08 8:34 ` Soft Works
2022-06-08 11:29 ` Soft Works
2022-06-08 11:34 ` Soft Works
2022-06-08 12:16 ` Anton Khirnov
2022-06-08 15:38 ` Soft Works
2022-06-08 17:38 ` Anton Khirnov
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=DM8P223MB03650454F09DE4D7C396CFB4BAA49@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.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