From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: asivery <asivery@protonmail.com> Subject: Re: [FFmpeg-devel] [PATCH] avformat/aea: Add aea muxer Date: Sun, 10 Mar 2024 15:00:03 +0100 Message-ID: <Ze284wbYuHjLG6mW@mariano> (raw) In-Reply-To: <Udn4nQXIGrYLw_55GiJyTdoD62pxsS1fCC3P4_9zRbRHqK_-xSQkhL4TuqDPWJkkChyoMWeQJM32_JflR8bS2SJeyz6YXxzxS2avvIw78PA=@protonmail.com> On date Saturday 2024-03-09 17:20:49 +0000, ffmpeg-devel Mailing List wrote: > Thank you both for the suggestions. I've updated the code as requested, and I apologize for the AV_LOG_WARNING instead of AV_LOG_ERROR - it was an oversight on my part. > I have also added the stream codec check, and it did get triggered when I tried to feed it audio that was not ATRAC1, so it seems it is required. > Regarding titles being truncated - that was my intention. However I've now added a warning if it was going to happen. > As for the block count in the header - none of the modern software which uses AEA reads that field, but for the older software, it will now be truncated to UINT32_MAX if needed. > Is there anything else that needs changes? > > From ee1d4c93c66e729d9d0456b2e8e789f3f98389e3 Mon Sep 17 00:00:00 2001 > From: asivery <asivery@protonmail.com> > Date: Fri, 8 Mar 2024 14:45:02 +0100 > Subject: [PATCH] avformat/aea: Add aea muxer > > Signed-off-by: asivery <asivery@protonmail.com> > --- > doc/muxers.texi | 10 +++ > libavformat/Makefile | 3 +- > libavformat/{aea.c => aeadec.c} | 0 > libavformat/aeaenc.c | 115 ++++++++++++++++++++++++++++++++ > libavformat/allformats.c | 1 + > 5 files changed, 128 insertions(+), 1 deletion(-) > rename libavformat/{aea.c => aeadec.c} (100%) > create mode 100644 libavformat/aeaenc.c > > diff --git a/doc/muxers.texi b/doc/muxers.texi > index 2104cc4a95..a4df8f736d 100644 > --- a/doc/muxers.texi > +++ b/doc/muxers.texi > @@ -663,6 +663,16 @@ when enabled, write a CRC checksum for each packet to the output, > default is @code{false} > @end table > > +@anchor{aea} > +@section aea nit: sort order (should go after adts) > +MD STUDIO audio muxer. out of my own curiosity, what is MD STUDIO? [...] You might also add an entry to the Changelog. Looks good to me otherwise, thanks. _______________________________________________ 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-03-10 14:00 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 11:19 asivery via ffmpeg-devel 2024-03-08 11:22 ` Andreas Rheinhardt 2024-03-08 11:48 ` asivery via ffmpeg-devel 2024-03-08 12:06 ` Andreas Rheinhardt 2024-03-08 13:50 ` asivery via ffmpeg-devel 2024-03-09 10:17 ` Stefano Sabatini 2024-03-09 12:06 ` Andreas Rheinhardt 2024-03-09 17:20 ` asivery via ffmpeg-devel 2024-03-09 17:48 ` Andreas Rheinhardt 2024-03-09 17:57 ` asivery via ffmpeg-devel 2024-03-10 14:00 ` Stefano Sabatini [this message] 2024-03-10 14:20 ` asivery via ffmpeg-devel 2024-03-10 15:10 ` Stefano Sabatini 2024-03-12 10:27 ` Stefano Sabatini 2024-03-12 11:10 ` asivery 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=Ze284wbYuHjLG6mW@mariano \ --to=stefasab@gmail.com \ --cc=asivery@protonmail.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