Jump to content

lpost

  • Content Count

    553
  • Joined

  • Last visited

  • Country

    United States

About lpost

  • Rank
    Junior Member

Recent Profile Visitors

2075 profile views
  1. Roon themselves recommend against backing up db to Dropbox. If by chance it succeeds it will almost always fail to restore. I’ve never cared to try, just sharing what I’ve read Danny at Roon post.
  2. Received my Serene L2 yesterday. What a nicely fleshed out sound. After less than 24 hours it's sounding pretty well settled. Have others noticed many changes after more hours like the May?
  3. I've always kept the two on separate machines but had a thought, have you tried configuring Roon HQP setup to use the IP address instead of localhost 127.0.0.1?
  4. Up Gateway is available at Mouser. https://www.mouser.com/ProductDetail/AAEON-UP/UP-GWS01-A20-1432-A11?qs=XeJtXLiO41RgX%2B9BTRGE%2Bw%3D%3D Works perfectly with NAA image, PCM 1.5M and DSD512. 8w consumption. I've used it for a few months, I've had the May for 4 months and used 1.5M PCM until I updated my HQPe machine to be able to handle DSD256 ASDM7EC. No comparison for me, it bests 32fs PCM easily, but preferences do differ.
  5. With any sort of DSP (convolution in my case) performed in HQPlayer some headroom is required to prevent intersample overs and Jussi recommends a minimum -3dB regardless. It seems there is no way to get around some the dynamic range reduction. Since CD 16-bit is only capable of ~96dB range is there any significance to 104dB vs. 120dB in practice? Have you measured the Serene or has some one with comparable data to the table above?
  6. Serene on the way to compliment May and compare to BHK preamp with a very nice set of Telefunken ECC802S. Thanks for the heads up on the pricing increase. Just snuck in under the line.
  7. lpost

    HQ Player

    Setting value to 0 means the word length claimed by audio device should be used.
  8. I've had the May KTE/L3 since March, 2800 hours. Today I flipped the fuse and after 15 mins. flipped it back. They got it right from shop. It was clearly different, less coherent. Flipped back and normalcy resumed. FWIW, the gold end down is my preferred and the way it came.
  9. I haven't thought about Baa Baa Black Sheep in decades. I enjoyed that show and the Corsair(s).
  10. I run Pi-Hole on a Pi4 running DietPi for the same functions. I have no idea what they are doing differently with the Linux builds vs. Windows but it's definitely different. Last evening I rebooted Windows and observed Roon network activities at startup. It was very active, ~20Mb/s for nearly 20 minutes but then settled to near zero. My library is 10k albums (3/4 local, 1/4 Qobuz, 100,000 tracks. I've used Tidal in the past and Qobuz currently. The db is never purged of data so all the Tidal entries are still there (the db admin in me dislikes this fact). It's 14GB. It's accessible
  11. Roon runs independently on another computer from HQPe and NAA. It's just a machine on the network and thus has no impact on the data/sound when playing music with HQPe.
  12. I've played a few tracks in HQPe without Roon involved and I frankly don't hear any difference with Roon feeding HQPe. In both cases there is a separate NAA endpoint device connected to the DAC via USB. Unfortunately, for me using HQPe alone or with HQPDControl is untenable. I ran Foobar2000 for a long time and it reminds me of those days way too much ;) but Foobar does sound fantastic. EuphonyOS sounded great to me too but it's based on Audio-Linux which is NOT supported by Jussi. Jussi does Debian (I believe) and AL is Arch. I also ran Audio-Linux from Pierro for a few years befo
  13. I've run Roon core on Windows 10, Ubuntu and ROCK (MOCK) over the years. Windows is by far the most efficient. Ubuntu and ROCK are seemingly always busy doing something. ROCK in particular makes ~10x more DNS requests than Windows (same db and music files). Roon uses a framework that is compatible with all but native to none. I've forgotten the name but I think they made a grave error back in the day hitching their horse to this model of non-native apps. They seem to continually chase their tail trying to fix issues because of this and it takes away from 'advancing' the product. All of this is
×
×
  • Create New...