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-devel@ffmpeg.org
Subject: [FFmpeg-devel] Swresample strangeness
Date: Sun, 25 Feb 2024 17:38:27 +0100 (CET)
Message-ID: <6374b936-e240-12fb-ec44-72d60656a893@passwd.hu> (raw)

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.

Here is a simple command line which should produce silence, but there is 
an audible regular clicking instead:

ffplay -f lavfi -i \
"sine=440:r=8000:samples_per_frame=2048,aresample=44100:filter_size=1:phase_shift=0,aresample=8000,aformat=cl=mono[a];
  sine=440:r=8000:samples_per_frame=320, aresample=44100:filter_size=1:phase_shift=0,aresample=8000,aformat=cl=mono[b];
  [a][b]amerge,pan=mono|c0=c1-c0"

Thanks,
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-02-25 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 16:38 Marton Balint [this message]
2024-02-25 18:43 ` Michael Niedermayer
2024-02-26  0:40   ` 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=6374b936-e240-12fb-ec44-72d60656a893@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