Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mxfdec: signal channel layouts using the new channel layout api
Date: Sat, 9 Mar 2024 03:18:27 +0100 (CET)
Message-ID: <d62d7b2b-4300-6e96-e0ea-10574cf68de0@passwd.hu> (raw)
In-Reply-To: <95f16ad5-dd52-43fb-b9b4-d428ef6c7282@gmail.com>



On Fri, 8 Mar 2024, James Almer wrote:

> On 3/8/2024 5:13 PM, Marton Balint wrote:
>>  Signed-off-by: Marton Balint <cus@passwd.hu>
>>  ---
>>    libavformat/mxfdec.c | 129 ++++++++++++++++++-------------------------
>>    1 file changed, 53 insertions(+), 76 deletions(-)
>>
>>  diff --git a/libavformat/mxfdec.c b/libavformat/mxfdec.c
>>  index 289db9833c..e2f4a22983 100644
>>  --- a/libavformat/mxfdec.c
>>  +++ b/libavformat/mxfdec.c

[...]

>>  +    ret = av_channel_layout_retype(ch_layout, AV_CHANNEL_ORDER_NATIVE,
>>  AV_CHANNEL_LAYOUT_RETYPE_FLAG_LOSSLESS);
>>  +    if (ret == AVERROR(ENOSYS))
>>  +        ret = av_channel_layout_retype(ch_layout,
>>  AV_CHANNEL_ORDER_UNSPEC, AV_CHANNEL_LAYOUT_RETYPE_FLAG_LOSSLESS);
>>  +    if (ret < 0 && ret != AVERROR(ENOSYS))
>>  +        return ret;
>>
>>        return 0;
>>    }
>
> I'm not against this patch, but shouldn't we make sure for example that swr 
> supports custom layouts first?

I don't really know what is the best approach here. Sure, some stuff will 
break if it encounters a custom layout. But nobody will fix it, if no 
custom layouts are ever encountered...

Regards,
Marton
_______________________________________________
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-09  2:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 20:13 Marton Balint
2024-03-08 21:15 ` James Almer
2024-03-09  2:18   ` Marton Balint [this message]
2024-03-09  6:27 ` Anton Khirnov
2024-03-14 13:24 ` Tomas Härdin
2024-03-16 18:59   ` 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=d62d7b2b-4300-6e96-e0ea-10574cf68de0@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