The sound device is configured to use its maximum buffer size. 128M is good for about 3 minutes of 32/96. It uses two 128M buffers for smooth playback. Perhaps knowing this makes it sound better to me. In a future version I'll probably get rid of this option and be more clever about choosing bit depth, unless you guys report improved SQ. At least with MPD, I know for a fact that it is bit-perfect. Perhaps (probably) I am wrong, but I have no way to confirm it. Subjectively, I think it sounds different than Daphile. With MPD, it is very simple to define a hw sink in the config file and then use basic command-line tools to verify that MPD is in fact dumping the bit-perfect PCM stream directly to (in my case) the USB/SPDIF converter. The problem, for me, is that there is no way to verify whether Daphile is truly bit-perfect (as far as I know). Agreed: given that the codec has already thrown away lots of bits of data from the original recording, trying to get Spotify bit-perfect does seem to have an element of 'rearranging the deck-chairs on the Titanic' (and other rather more vulgar metaphors) about it. This is why it is so puzzling to me that Daphile's sound changed somewhere through the upgrades to newer revisions (in my subjective opinion). If you have more questions feel free to ask via pm, post a reply, or simply head over to the forums for your specific distro. This post by Rizlaw is a great summary, albeit rather outdated. Bit-perfect is bit-perfect, regardless of what software is running on the player. There are many options out there for playing back bitperfect audio in linux as far as music players go. The player pc has two jobs (in a bit-perfect setup) decode the audio file format(s) into PCM (or DSD as the case may be) and then dump that straight to the next downstream device. This app offers bit-perfect, gapless playback of lossless audio formats, and it supports lossy formats as well. In the end there are regular audio player's which use system implemented driver's (for output) and sound great with in app implemented processing (decoding, processing libs, effects and everything) like for example Selenium.Indeed. Bit-Perfect Streaming Hello, I am new to the scene and have some questions about streaming. 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. Skilled in people and asset management, with a focus on developing customer-first solutions to better your business. 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. |