Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 6/9] fftools/ffprobe: export Tile Grid Stream Group parameters
Date: Tue, 5 Mar 2024 12:50:09 -0300
Message-ID: <42cfc862-858b-40b7-9332-ca559db4ddf1@gmail.com> (raw)
In-Reply-To: <Zec5RhmEzNPE/25m@mariano>

On 3/5/2024 12:24 PM, Stefano Sabatini wrote:
> On date Tuesday 2024-03-05 12:14:53 -0300, James Almer wrote:
>> On 3/4/2024 9:00 PM, James Almer wrote:
>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>> ---
>>>    fftools/ffprobe.c | 41 ++++++++++++++++++++++++++++++++++++-----
>>>    1 file changed, 36 insertions(+), 5 deletions(-)
> [...]
> 
>> I think I'll withdraw this patch for now. Some stream group types have
>> several layers of data, so components and pieces would not be enough. This
>> is the case for IAMF Audio Elements and Mix Presentation, for example.
>> A generic way to add N amount of layers would be needed.
> 
> I see.
> 
> Does it mean that the nesting level is greater than 3 (side_data,
> components, pieces)?

Yes. Look at AVIAMFMixPresentation, which has an array of AVIAMFSubmix, 
which in turn have an array of AVIAMFSubmixLayout plus an array of 
AVIAMFSubmixElement per submix, the latter which has a 
AVIAMFParamDefinition per element.
If the AVIAMFMixPresentation is the component, the AVIAMFSubmix would be 
the piece, and then we ran out of levels.

> 
> Probably the best we can do is some kind of flattening (ffprobe is not
> designed for generic level of nesting, as we need to define the
> structure of the layout, at least for some formats (e.g. XML)).
> _______________________________________________
> 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".

  reply	other threads:[~2024-03-05 15:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  0:00 [FFmpeg-devel] [PATCH 1/9 v2] fftools/ffprobe: fix printing side data components and pieces James Almer
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 2/9] avformat/avformat: add a function to return the name of stream groups James Almer
2024-03-05 14:50   ` Stefano Sabatini
2024-03-05 14:52     ` Stefano Sabatini
2024-03-05 14:56       ` James Almer
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 3/9 v3] fftools/ffprobe: add support for Stream Groups James Almer
2024-03-05 15:06   ` Stefano Sabatini
2024-03-05 15:09     ` James Almer
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 4/9 v2] fate/iamf: print stream group information James Almer
2024-03-05 15:10   ` Stefano Sabatini
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 5/9 v2] fate/mov: print stream group information for iamf tests James Almer
2024-03-05 15:14   ` Stefano Sabatini
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 6/9] fftools/ffprobe: export Tile Grid Stream Group parameters James Almer
2024-03-05 15:14   ` James Almer
2024-03-05 15:24     ` Stefano Sabatini
2024-03-05 15:50       ` James Almer [this message]
2024-03-06 13:39         ` Stefano Sabatini
2024-03-05 15:21   ` Stefano Sabatini
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 7/9 v3] fate/mov: print stream group information for avif/heic tests James Almer
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 8/9 v2] fate/mov: use framecrc for the remaining " James Almer
2024-03-05  0:00 ` [FFmpeg-devel] [PATCH 9/9] fate/mov: add a heic test with a derived image using a single item twice James Almer
2024-03-05 14:46 ` [FFmpeg-devel] [PATCH 1/9 v2] fftools/ffprobe: fix printing side data components and pieces Stefano Sabatini

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=42cfc862-858b-40b7-9332-ca559db4ddf1@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