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 001/293 v8] avutil/channel_layout: Add a new channel layout API
Date: Thu, 17 Mar 2022 16:51:03 -0300
Message-ID: <ff2a0ead-678d-adad-44cc-4d82eb714d1b@gmail.com> (raw)
In-Reply-To: <4048bc0f-9a75-1b3c-6f47-ac4f78fe2e0e@gmail.com>



On 3/17/2022 4:46 PM, James Almer wrote:
> 
> 
> On 3/17/2022 4:39 PM, Michael Niedermayer wrote:
>> On Tue, Mar 15, 2022 at 11:00:02PM -0300, James Almer wrote:
>>> On 3/15/2022 9:41 PM, Michael Niedermayer wrote:
>>>> On Mon, Jan 24, 2022 at 05:46:56PM -0300, James Almer wrote:
>>>>> From: Anton Khirnov <anton@khirnov.net>
>>>>>
>>>>> The new API is more extensible and allows for custom layouts.
>>>>> More accurate information is exported, eg for decoders that do not
>>>>> set a channel layout, lavc will not make one up for them.
>>>>>
>>>>> Deprecate the old API working with just uint64_t bitmasks.
>>>>>
>>>>> Expanded and completed by Vittorio Giovara 
>>>>> <vittorio.giovara@gmail.com>
>>>>> and James Almer <jamrial@gmail.com>.
>>>>> Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
>>>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>>>> ---
>>>>> Changes since last version:
>>>>>
>>>>> *Both av_channel_layout_describe() and 
>>>>> av_channel_layout_from_string() now
>>>>>    support a "2 channels (FL+LFE)" syntax, to signal native (usually
>>>>>    non-standard) or custom order layouts.
>>>>> *a single decimal value is now interpreted as a mask by
>>>>>    av_channel_layout_from_string(), same as a single hexadecimal 
>>>>> value.
>>>>> *De-duplicated code by simplifying 
>>>>> av_channel_layout_channel_from_string().
>>>>>
>>>>> The entire set can still be found in
>>>>> https://github.com/jamrial/FFmpeg/commits/channel_layout4
>>>>>
>>>>>    libavutil/channel_layout.c | 661 
>>>>> +++++++++++++++++++++++++++++++++----
>>>>>    libavutil/channel_layout.h | 551 +++++++++++++++++++++++++++++--
>>>>>    libavutil/version.h        |   1 +
>>>>>    3 files changed, 1110 insertions(+), 103 deletions(-)
>>>>
>>>> didnt bisect but
>>>>
>>>> this
>>>> ./ffmpeg -i ~/tickets/3542/out.mov -channel_layout stereo -acodec 
>>>> pcm_s16be file.mov
>>>> fails after the patchset but not before
>>>>
>>>> [graph_0_in_0_0 @ 0x5642d659ec40] filter context - fmt: s16 r: 44100 
>>>> layout: 3 ch: 2, incoming frame - fmt: s16 r: 44100 layout: 60000000 
>>>> ch: 2 pts_time: 0
>>>> [graph_0_in_0_0 @ 0x5642d659ec40] Changing audio frame properties on 
>>>> the fly is not supported.
>>>> Error while filtering: Invalid argument
>>>> Failed to inject frame into filter network: Invalid argument
>>>> Error while processing the decoded data for stream #0:0
>>>> Conversion failed!
>>>
>>> Should be fixed.
>>
>> Heres another which broke around the channel change
>> ./ffmpeg -i tickets//2064/mus_sympathy_for_the_devil_l.wav file.wav
>>
>> "tickets//2064/mus_sympathy_for_the_devil_l.wav: Function not 
>> implemented"
>>
>> file seems here:
>> https://www.djxmmx.net/ffmpeg/2064/
> 
> What was this file read as before the set? Ticket 2064 mentions a file 
> with a wav extension that's an "unknown container", and then the ticket 
> was closed as fixed without referencing a commit.

Nevermind, it's "Black ops audio" container. I see what's wrong.
Will fix in a bit.
_______________________________________________
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:[~2022-03-17 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 20:46 James Almer
2022-01-24 21:08 ` Marton Balint
2022-01-24 21:21   ` James Almer
2022-01-27 15:08 ` Nicolas George
2022-01-31 13:27   ` Anton Khirnov
2022-03-16  0:41 ` Michael Niedermayer
2022-03-16  2:00   ` James Almer
2022-03-17 19:39     ` Michael Niedermayer
2022-03-17 19:46       ` James Almer
2022-03-17 19:51         ` 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=ff2a0ead-678d-adad-44cc-4d82eb714d1b@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