From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/mov: ensure the IAMF track is the first
Date: Thu, 1 Aug 2024 12:07:35 -0300
Message-ID: <df2f0703-f285-45b6-be2b-42b4e8e3d1af@gmail.com> (raw)
In-Reply-To: <e8177b81-22e8-4037-b2e4-b9a485906852@gmail.com>
On 8/1/2024 9:35 AM, James Almer wrote:
> On 8/1/2024 5:59 AM, Anton Khirnov wrote:
>> Quoting James Almer (2024-08-01 04:14:09)
>>> Fixes crashes when muxing video tracks alongside IAMF ones.
>>>
>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>> ---
>>> libavformat/movenc.c | 11 ++++++++++-
>>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
>>> index ae49582a1a..87ec368d52 100644
>>> --- a/libavformat/movenc.c
>>> +++ b/libavformat/movenc.c
>>> @@ -7536,6 +7536,7 @@ static int mov_init_iamf_track(AVFormatContext *s)
>>> if (!track->iamf)
>>> return AVERROR(ENOMEM);
>>> + track->first_iamf_idx = INT_MAX;
>>> for (int i = 0; i < s->nb_stream_groups; i++) {
>>> const AVStreamGroup *stg = s->stream_groups[i];
>>> switch(stg->type) {
>>> @@ -7558,6 +7559,11 @@ static int mov_init_iamf_track(AVFormatContext
>>> *s)
>>> return ret;
>>> }
>>> + if (track->first_iamf_idx != 0) {
>>> + av_log(s, AV_LOG_ERROR, "The IMAF track must be the first
>>> track\n");
>>
>> Why? And is this documented anywhere?
>
> Just comments in the code. The reason i wrote it this way is because i
> parse the stream groups first, then the remaining streams, and generate
> the tracks in that order, as it was the simplest, least invasive way
> (The muxer handled streams and tracks as separate concepts with
> potentially different count for each of them even before iamf).
>
> I could look into changing it, but it may require some restructuring.
Ok, gave it a try and seemingly found out how to get this working
without too many changes.
Will send an updated patch.
_______________________________________________
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".
prev parent reply other threads:[~2024-08-01 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 2:14 James Almer
2024-08-01 2:14 ` [FFmpeg-devel] [PATCH 2/2] fate/mov: add an IAMF+video muxing test James Almer
2024-08-01 8:59 ` [FFmpeg-devel] [PATCH 1/2] avformat/mov: ensure the IAMF track is the first Anton Khirnov
2024-08-01 12:35 ` James Almer
2024-08-01 15:07 ` James Almer [this message]
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=df2f0703-f285-45b6-be2b-42b4e8e3d1af@gmail.com \
--to=jamrial@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