![]() Or you try to tweak embedded in phone what you have with an app like Neutron (for QC SoC's) but some things will disregardingly need a costume ROM with some configuration changes. So you use in app embedded drivers for USB audio 2.0 and a processing (UAPP, HiBy, HF, FiiO, Shanling.) but the chain is limited to the what app provides. Let's just say how Android default system audio implementation is bad to broken (when it resamples 44100 to 48000 Hz I consider it broken) from every view point (OS-vendor-OEM). You would be nuts not to use widely available duble precision floting point (which by the way will translate back to the precision point rounding in integer) or 64 bit FP and linear upsampling for processing (effects, EQ.) even leaving analog output going over standard output rates (44100 ~ 48000 Hz) to the extent that you want to drive noise (or most of it) out to the frequency hearing range (DSD128 for example) to where it can't be heard. That's analog domain and human hearing anyway. ![]() If you look at capability of DAC output there is absolutely no need for more than 21 bit integer precision (as you can feel remaining 3 bit's noise flor whit what ever you like it will stay beyond auditable threshold) depth or sample rate of 44100 or 44800 Hz. Bit perfect as usually prefered to means that digital source is passed on to analog output as it is (sample rate bit depth).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |