If I wasn't trying to wring the last bit of control and quality from my set up, I would have gladly stoped there. The Pi2AES had more than enough power to render PCM audio at 192K with the Sync-Mx filter. These preferences inform the choices I made. I personally favor timbre, space, and a dark slightly warm sound. I continue to output to a Holo Audio Spring 3 KTE feeding either a Pete MIllet Design Fet-A Solid State or Ampsandsound Kenzie Ovation headphone amp. It is a tiny piece of HQPlayer capability.I migrated from a Pi2AES HQPlayer Embedded built on a Raspberry Pi4 to a Small Green Computer Sonic Transporter i5. If someone is just going to measure HQPlayer to compare with M-Scaler, with a great measuring DAC, it would cause a yawn.
I think some people need some greater understanding that HQPlayer is not just a cheaper software M-Scaler thing. Inside the listening room is just a HQPlayer endpoint running on fanless and headless on RPi4. HQPlayer runs headless on Ubuntu Server on the other side of the house. I can even change room correciton profiles (different bass profiles) while the music is playing, using an iPad from my couch. In my case with HQP I do it all through one DSP engine that I can control from an iPad and at the same time, the digital filtering is highest quality. I could do what HQP does with software on PC/Mac/Linux too but it is way more clunky and needs keyboard/monitor/mouse interaction. I think everyone here only think HQPlayer is only for upsampling?įor me it is my DSP engine for 3-way DSP crossover speakers plus 2 subs with digital room correction (65k tap FIR filter created with Audiolense XO) and headphones EQ/correctionĪnd I can feed ( bit perfectly) Amazon Music UHD and Apple Hi-Res or any source through HQPlayer's DSP engine to do all the above.
0 kommentar(er)
