Resampling misbehaving?

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Post Reply
fas42
Posts: 66
Joined: Sat Jun 13, 2015 2:31 am
Operating System: Windows 8 or 8.1

Resampling misbehaving?

Post by fas42 » Sun Mar 24, 2019 1:00 am

In Windows 8.1, using both 2.2.2 and 2.3.1 resampling is not behaving correctly, by my understanding - or am I missing something obvious? Many years ago I tested the ability of Audacity to perform upsampling without adding artifacts, and it performed admirably - now it's adding amplitude distortion at the top end of the frequency band.

Audio at 44.1k which has content above about 20kHz does not have the latter resampled correctly - if one upsamples and downsamples a track, and differences the final from the original, a major spike glitch occurs in the 20KHz area - Audacity can't be used to verify the accuracy of other processing; something I used to regularly do.

steve
Site Admin
Posts: 80679
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Resampling misbehaving?

Post by steve » Sun Mar 24, 2019 12:21 pm

Please give step by step instructions to reproduce the issue. Ensure that you include any non-default settings / Preferences that you are using.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

fas42
Posts: 66
Joined: Sat Jun 13, 2015 2:31 am
Operating System: Windows 8 or 8.1

Re: Resampling misbehaving?

Post by fas42 » Fri Mar 29, 2019 5:16 am

Should have replied earlier, but resolved that the issue was to do with the resampling routines from the SoX library - confirmed that SoX from the command line did the identical thing, and this was because of the bandwidth parameter. I don't know whether it makes sense to pursue it further, but I used a workaround of brickwalling all frequencies above 20kHz, which gave me satisfactory behaviour for what I was trying to do,

Thanks for the reply.

Post Reply