From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/aea EOF Patch
Date: Thu, 9 Mar 2023 00:28:45 +0100 (CET)
Message-ID: <f1c7af46-5d23-e18-971a-8c48af3f87c@passwd.hu> (raw)
In-Reply-To: <s2oG8O7ym2wFkph5_W-8Wn0b5IIsCgUIcliZZ9kpMW7JSpZw1Yfx7POzUAqO4LkiTnElUK92-zKaMUkRjWiZJT6WAEz2tnL6B26tLv01cec=@protonmail.com>
On Sat, 4 Mar 2023, asivery wrote:
> Could someone please take a look? This would improve AEA demuxing, right now every AEA file makes ffmpeg crash with an error.
The way I see it, you could simply replace the whole body of
aea_read_packet() with this single line:
return av_get_packet(s->pb, pkt, s->streams[0]->codecpar->block_align);
Regards,
Marton
> Thank you in advance :)
> ------- Original Message -------
> On Saturday, October 22nd, 2022 at 7:43 PM, asivery <asivery@protonmail.com> wrote:
>
>> Hello,
>> This patch aims to fix a problem I've noticed while working with AEA (Sony ATRAC1 comtainer) files.
>> Right now FFmpeg always exits with an "Input/Output error" when dealing with AEA files.
>> This patch solves that issue by returning AVERROR_EOF once the end of file is encountered, instead of always returning AVERROR(EIO).
>>
>> I am sending this patch again because of an incorrect mime type of the first one.
>>
>> Best regards,Asivery
> _______________________________________________
> 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".
next prev parent reply other threads:[~2023-03-08 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 17:43 asivery
2023-03-04 12:23 ` asivery
2023-03-08 23:28 ` Marton Balint [this message]
2023-03-09 0:50 ` asivery
2023-03-09 20:16 ` Marton Balint
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=f1c7af46-5d23-e18-971a-8c48af3f87c@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