![]() ![]() And should the device not support high-res-audio at all then Neutron will resample to 48 kHz no matter what else has been set. So "Oversampling" means something like follow-source-frequency-multiplied-by-n. It seems that in recent versions Neutron doesn't use non-supported sampling rates at all. But it might force Neutron to resample to an non-even multiple, which isn't as perfect as resampling to an even multiple. Audio Hardware > Frequency will set the sampling rate to a value supported by the device. But if the resulting sampling rate isn't supported by the device the firmware will resample again after the DSP to the best suitable rate.ĥ. This is a good thing on its own, better than a non-even multiple. Audio Hardware > Oversampling sets the sampling rate to an even multiple of the input. They certainly will result very differently. Right now there is very little information concerning for example, if crossfeed is performed before EQ or after. If you activate Audio Hardware > Oversampling then Audio Hardware > Frequency will be ignored.Ĥ. Topics may include general information such as oversampling, internal bit depth, dithering algorithm, DSP pipeline order(the order to apply each DSP algorithm), etc. If the DSP delivers a supported sampling rate the firmware won't resample.ģ. If the firmware resamples, it will do so only after the DSP and only if it doesn't support the sampling rate delivered by the DSP. If Neutron resamples, it resamples the output of the decoder and feeds the DSP with the new sampling rate, so the DSP will work with the new sampling rate, and deliver data with this rate to the output.Ģ. Some things about the sampling rate that I found out in the meantime :ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |