Comment by dist-epoch
4 days ago
Proper audio resampling should not be identifiable. Of course, the OS mixer probably doesn't do proper (CPU expensive) resampling.
But a quality audio player should account for this and do it's own.
4 days ago
Proper audio resampling should not be identifiable. Of course, the OS mixer probably doesn't do proper (CPU expensive) resampling.
But a quality audio player should account for this and do it's own.
If you're not on a US-based IP, you should check out https://src.infinitewave.ca/
It is an incredible resource to see the quality of the resampling algorithms used by the actual production software likely used in any digital audio workflow.
You will see that while the best are indeed almost 100% transparent, many are not.
> If you're not on a US-based IP, you should check out https://src.infinitewave.ca/
There is also https://src.hydrogenaudio.org/ (with no IP based restrictions, AFAIK).
Currently giving me: "Internal Server error reading database"
I remember using Adobe Audition for resampling audio, this site shows I had good intuition
your software is among the best, but not pitch black best :)
Yeah, we use Secret Rabbit Code for ours, though we have access to the sox code now and that is "perfect". We might change to that as the default sometime this year.
"proper" resampling was expensive in 1997 when Intel was introducing fixed sampling AC'97, but was below noise floor of CPU load meter in 2007 when Microsoft released Vista killing hardware mixing.
I'm also one of those audiophile crazies that obsesses over which metals to use in cabling, power filtering, swapping opamps, and builds their own DACs, amps, and speakers