Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/aacdec: don't force HE-AACv2 profile if no PS info is present
Date: Fri, 22 Jul 2022 16:23:57 +0200
Message-ID: <DB6PR0101MB221440DA65BFA82F3A87C47B8F909@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <8b484a4e-ba96-d54e-a4b5-84e1ee5e53f9@gmail.com>

James Almer:
> On 7/18/2022 10:57 AM, Andreas Rheinhardt wrote:
>> James Almer:
>>> On 7/14/2022 9:10 AM, Andreas Rheinhardt wrote:
>>>> James Almer:
>>>>> Should fix ticket #3361
>>>>>
>>>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>>>> ---
>>>>> This also needs an update to some fate ref samples i'll upload before
>>>>> pushing
>>>>> (fate-aac-al_sbr_ps_04_ur and fate-aac-al_sbr_ps_06_ur which are now
>>>>> decoded
>>>>> properly as he_aac mono, so the .s16 files need to be replaced).
>>>>>
>>>>
>>>> We have both a fixed-point AAC as well as a floating point AAC decoder.
>>>> Is there actually a test that tests that the output they produce is
>>>> reasonably close? If not, could we make the test so that the same file
>>>> is decoded once with the fixed-point and once with the floating-point
>>>> decoder and then compared?
>>>
>>> That wouldn't help much, i think. Almost all changes to *_template.c
>>> files are going to affect both decoders, so a breakage would not be
>>> detected if you compare their output with each other as they would both
>>> exhibit it.
>>>
>>
>> I actually thought that the aac_fixed tests used checksums instead of
>> ref files; then changes and breakages would be visible by changes to
>> these files. Apparently I was wrong about that and the ref files are
>> used for both aac and aac_fixed. But a test like the one outlined above
>> would nevertheless obviate the need for a new ref file.
> 
> Judging by
> https://git.videolan.org/?p=ffmpeg.git;a=blob;f=tests/fate/aac.mak;h=1743428f544fad8946dba11dd4ecec0630eb70a6;hb=HEAD#l117
> it seems at least for these samples the fixed decoder does not generate
> a decoded stream comparable to the float one, so I'll just upload a new
> raw pcm file.

When I decode both of these streams with git master, the left channel is
pretty much identical, yet the right channel of the fixed-point decoder
is silent and the right channel of the floating point decoder is not.
With this patch applied, the result are two mono streams that are pretty
much identical: The test sample created by the floating-point decoder
works with the fixed-point decoder test (if one uncomments and modifies
the latter). So the issue with aac-al_sbr_ps_06_ur is not a reason to
upload new samples.

- Andreas

PS: libfdk-aac produces a file that looks pretty much like the floating
point decoder from git master. Are you sure your patch is correct?
_______________________________________________
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-07-22 14:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 17:59 James Almer
2022-07-14 12:10 ` Andreas Rheinhardt
2022-07-16 12:53   ` James Almer
2022-07-18 13:57     ` Andreas Rheinhardt
2022-07-22 12:46       ` James Almer
2022-07-22 14:23         ` Andreas Rheinhardt [this message]
2022-07-22 14:51           ` James Almer
2022-07-22 14:56             ` Andreas Rheinhardt
2022-07-22 15:03               ` James Almer
2022-07-22 15:14                 ` Andreas Rheinhardt
2022-07-22 15:37                   ` James Almer
2022-07-22 23:00                     ` Alex Converse
2022-07-22 23:10                       ` James Almer
2022-08-02 17:48                         ` James Almer

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=DB6PR0101MB221440DA65BFA82F3A87C47B8F909@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.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