Feature description
Output Frequency Following File Frequency family. 44.1k, 88.2k, 176.4k / 48k, 96k, 192k.
Problem solved
At the moment I can choose for example 48k or 44.1k output Frequency. But that means playing a file at a different frequency causes resampling.
Brought benefits
Resampling to a while number relationship 88.2k to 44.1k 2:1 or 192k to 48k 4:1 is more battery efficient. The resampler is actually skipping samples rather than resampling.
It also avoids quantisation error entirely (The tiny amount of which can do weird things in the audible high frequencies on cymbals and strings)
Other application solutions
In Neutron Player you can set the maximum output frequency at 48k. The resampling behaviour then follows the pattern of down sampling to either 48k or 44.1k depending on which is a whole number ratio.
Device type
Phone
Additional description and context
I believe current behaviour available is either bit perfect, matching the source file frequency on output and not down sampling at all. Or a set sampling target all files follow regardless of original frequency sometimes up sampling sometimes down sampling.
I could downsample my hi-res library to either 44.1k or 48k depending on the original for better streaming and battery life and use bit perfect settings which would then follow the file at the sample rates I want. But that would require extra space to make a copy.
I searched existing feature requests
on