Opened 4 weeks ago

Closed 2 weeks ago

Last modified 23 hours ago

#11283 closed defect (fixed)

"aloop" filter somehow gave misalignment in 48 KHz Stereo WAV

Reported by: Danny Weijermans Owned by:
Priority: normal Component: avfilter
Version: git-master Keywords: aloop
Cc: Marton Balint, MasterQuestionable Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

when using the aloop audio filter in ffmpeg

to produce a looped audio section,
it works sample accurate in 44.1kHz mono or stereo,
and in 48kHz mono.

But for some strange reason,

it's off (probably by 1?) when using a 48kHz stereo file.

I didn't test other sample-rates yet..
I'm including a 48kHz stereo wav file containing a pure 480Hz sine,

so you can test yourself.

I'm using for testing:
ffmpeg -y -i /Users/disjt/Desktop/s.wav -filter_complex "aloop=loop=4:start=48000:size=48000" s.wav


Attachments (1)

s.wav (750.2 KB ) - added by Danny Weijermans 4 weeks ago.
pure 480Hz Sinewave 16bits 48kHz stereo wav file

Download all attachments as: .zip

Change History (17)

by Danny Weijermans, 4 weeks ago

Attachment: s.wav added

pure 480Hz Sinewave 16bits 48kHz stereo wav file

comment:1 by MasterQuestionable, 4 weeks ago

Keywords: seek seeking added
Resolution: duplicate
Status: newclosed
Summary: ffmpeg aloop audio filter not working correctly in 48khz stereo wav"aloop" filter somehow gave misalignment in 48 KHz Stereo WAV
Version 0, edited 4 weeks ago by MasterQuestionable (next)

comment:2 by Marton Balint, 4 weeks ago

Cc: Marton Balint added
Component: undeterminedavfilter
Keywords: aloop added; seek seeking removed
Resolution: duplicate
Status: closedreopened
Version: unspecifiedgit-master

No, this is a totally different issue, it has nothing to do with seeking. I will send a patch to fix this soon.

comment:3 by MasterQuestionable, 4 weeks ago

͏    Looks somehow similar, nevertheless.

comment:4 by Danny Weijermans, 3 weeks ago

thanks Marton!
are there anymore combinations of sample-rates and channel-counts to be tested?
I wouldn't expect this to behave different with a certain combination of S/R and channel-count..

comment:5 by MasterQuestionable, 3 weeks ago

Cc: MasterQuestionable added

͏    I guess Mono alone would suffice. (doesn't seem Channel# related)
͏    I think it might be essentially seeking issue:
͏    So probably just try changing the loop start point..?

comment:6 by Danny Weijermans, 3 weeks ago

I will investigate further, because I need it for some of my own code..
@Marton : you found the bug? ('I will send a patch to fix this soon.')

comment:8 by Danny Weijermans, 3 weeks ago

W O W !!!

comment:9 by Danny Weijermans, 3 weeks ago

How will I know when it has been 'patched' ?

comment:10 by Danny Weijermans, 3 weeks ago

thanks so much, Marton!
Would it be possible to also shine your light

on my other ticket:

https://trac.ffmpeg.org/ticket/11281
would be great if you can find that 'bug' too..

comment:11 by Marton Balint, 2 weeks ago

Resolution: fixed
Status: reopenedclosed

comment:12 by Danny Weijermans, 2 weeks ago

thanks a lot, Marton!!

comment:13 by Danny Weijermans, 11 days ago

is the fixed version distributed already?

comment:14 by Danny Weijermans, 35 hours ago

would this also be automatically updated in ffplay? or is this the same code?

comment:15 by MasterQuestionable, 33 hours ago

͏    Likely the same bundle?
͏    (unsure MacOS's distribution handling)

͏    FF-series tools share significant portion of common codes.

comment:16 by Danny Weijermans, 23 hours ago

updated ffmpeg,

and bug is gone: THANKS a lot!!
but I think ffplay is not updated yet on OSX..
and it could be used with a filter to realtime-play seemless loops ;)

let me know when this will be updated in ffplay as well..
thanks again for all your work!
regards, Danny

Note: See TracTickets for help on using tickets.