From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Swresample strangeness
Date: Mon, 26 Feb 2024 01:40:04 +0100 (CET)
Message-ID: <91c85dcc-4b79-753d-7518-8a1588e08f88@passwd.hu> (raw)
In-Reply-To: <20240225184350.GO6420@pb2>
On Sun, 25 Feb 2024, Michael Niedermayer wrote:
> On Sun, Feb 25, 2024 at 05:38:27PM +0100, Marton Balint wrote:
>> Hi,
>>
>> I am working on a patch to select a better default packet size for the wav
>> demuxer, since it reads at most 4096 bytes which can cause insanely small
>> packets for files with high channel count.
>>
>> Unfortunately some swresample fate tests blew up, and I wonder if the result
>> of the resampling should be dependant on size of the audio chunks which are
>> being fed to it. My assumption is that if it causes audible difference in
>> the output, then it is likely a bug in swresample, but I am not familiar
>> with its code and its many tunable variables, so if someone could confirm,
>> (or even better, fix it :)) that would be great.
>
> From what you describe, the first thing that comes to mind are timestamps.
> If you resample with timestamps that mismatch the exact values expected from
> the sample rate. You will have different resuls when the packet size is changed.
> Its the same data but at a different point in time and thats different then.
>
> I have too many things to do though so i cant really look into this.
Ok, thanks anyway. For the async tests the timestamps were randomly
generated, and that changed. For other tests however I am quite
sure about the swresample bug, so I will send a patch soon to fix that.
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".
prev parent reply other threads:[~2024-02-26 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 16:38 Marton Balint
2024-02-25 18:43 ` Michael Niedermayer
2024-02-26 0:40 ` Marton Balint [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=91c85dcc-4b79-753d-7518-8a1588e08f88@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