Jump to content


  • Content Count

  • Joined

  • Last visited

About twluke

  • Rank
    Freshman Member

Personal Information

  • Location

Recent Profile Visitors

2458 profile views
  1. The best answers can be obtained from OE333. Also, you might want to check my previous post for reference. If interested, send PM to him.
  2. Hi all, More than a week ago there has been a release of new Amanero firmware (2006be10) supporting native DSD512 with BE format on linux in a thread of Github Amanero issue and the people flashed their Amanero to this new version confirmed that it worked well without any annoying noises. I also confirmed that it was working rock-solid in playing DSD512 via Roon/HQP on Linux (Ubuntu 18.04) on my DAC8 DSD. This firmware can be said to be nearly equivalent to the final release to come. This morning, there was a notification of the release of Windows driver supporting ASIO for this new firmware with related URL from Amanero/Domenico in the thread above but the message has been deleted or cancelled somehow. Anyway I downloaded the driver and installed on a Windows10 system and played DSD512 sources via Roon/HQP on my DAC8 DSD (its firmware already updated to v2.70 with the help of OE333 as I wrote previously). Well, the new driver with ASIO support worked quite well and I'm now enjoying the sound of DSD512, noise-free, from HQP on this DAC for more than hours. Just for your info. Maybe expecting comments from OE333.
  3. twluke

    HQ Player

    Please ignore.
  4. Well, it may be difficult how much the PC occupy the part of the entire room noise because I could not find obvious difference even after turning off all of the equipments related to this measurement. The picture below is the measurement of room noise without any PC and audio gears turned on.
  5. You are misunderstanding. Muted means measuring no sound other than the room and PC by muting the speaker while the latter loaded with playing music. Non-muted means recording the ordinary loudness of speaker when playing music with possible noise from the room and PC, of course.
  6. Okay. I'm not sure this can be of help but the pictures below (poly-sinc-muted, non-muted, xtr-muted) are quick noise measurements using an iPAD app. The speakers (Altec 604-8G and 802-8G/511B horn) are 4.5 m away from the microphone and the PC is 2 m away from it. Regards,
  7. Hi there, I recently built an i7-9700K system using a Z390 Phantom Gaming-ITX/ac MoBo, 16GB DRAM from Corsair, an SFX PSU (SX600-G from SilverStone), a Noctua cooler (NH-U9S) and an M1 case from SFFLAB for the HQP on a linux kernel (Ubuntu 18.04), focusing on playing upsampled DSD512 sources via Roon. The results were quite good and there was no untoward rising of CPU temperature when playing DSD512 with a poly-sinc filter, usually within the ranges of 50 to 65°C as shown in the first picture below. Even with a poly-sinc-xtr filter, the system was well working without any stutters or signal drops in playing DSD512, permitting a rise of CPU temperature up to the ranges of 70 to 80°C around as shown in the second picture. I think this good result is considerably owing to the excellent cooling power of the Noctua cooler. It is almost quiet or nearly silent with a poly-sinc filter. Even with the xtr filter, the fan is very quiet and you can focus on listening to music without being distracted. The M1 case from SFFLAB was very compact but can deal with the size of RTX2080x GPUs. The interior of the case was well designed, allowing smooth air flow from the CPU fan for heat dispersion. Finally what should be stressed here is the current system does not include any GPU, i.e., no cuda offload, yet capable of playing DSD512 with the xtr filter without any problems. Previously I reported a positive result of RTX2080 GPU for dealing with the xtr filter with a 8700K system but the current system gave me another positive result. Well, that said, I'm now back to the poly-sinc filter for listening. Regards,
  8. twluke

    HQ Player

    Hi Miska, I'm very sorry for posting my premature conclusion on the suggestion from you. Later, I again tried it and I'm very happy to let you know that the problem has completely gone. The initial failure to try your suggestion was simply due to my wrong presumption that the change of environmental variable will take effect on the fly. After restarting the HQP, I confirmed the log messages were totally silenced. Thank you very much. # BTW I'll report my positive result of the i7-9700k CPU dealing with poly-sinc-xtr filter for DSD512 without cuda support in another thread later.
  9. twluke

    HQ Player

    lsb_release shows the info below: Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Thank you for this kind suggestion; really appreciated it. I tried both at the user level but they didn't work and the log messages are still flowing. Maybe I need more homework. Regards,
  10. twluke

    HQ Player

    Thanks for this suggestion. Unfortunately I'm using a desktop version of HQP on linux and hqplayerd.service is not available. Maybe living with these messages for now until I can find the other way. Regards,
  11. twluke

    HQ Player

    Thank you for this suggestion. Yes, Roon is running for HQP on each machine. Later I'll figure out how I can silence it. Regards,
  12. twluke

    HQ Player

    Hi Miska, I have a question about the constant log messages from the hqplayer desktop running on my Ubuntu 18.04 machines (one with a 8700K CPU and the other with a 9700K CPU with a 4.15.0-47-generic kernel in each). The HQP (3.25.3) is working well in each machine, sending the quality sound of DSD512 sources to my B3SEpros from TPA (Twisted Pear Audio). What appears weird to me is the continuous flow of log messages from the application in /var/log/syslog as shown below: Machine 1: Apr 15 19:54:41 musik2 hqplayer.desktop[4052]: volumeRange Apr 15 19:54:41 musik2 hqplayer.desktop[4052]: state Apr 15 19:54:43 musik2 hqplayer.desktop[4052]: volumeRange Apr 15 19:54:43 musik2 hqplayer.desktop[4052]: state Apr 15 19:54:45 musik2 hqplayer.desktop[4052]: volumeRange Apr 15 19:54:45 musik2 hqplayer.desktop[4052]: state Machine 2: Apr 15 19:55:20 musik3 hqplayer.desktop[1627]: volumeRange Apr 15 19:55:20 musik3 hqplayer.desktop[1627]: state Apr 15 19:55:22 musik3 hqplayer.desktop[1627]: volumeRange Apr 15 19:55:22 musik3 hqplayer.desktop[1627]: state Apr 15 19:55:24 musik3 hqplayer.desktop[1627]: volumeRange Apr 15 19:55:24 musik3 hqplayer.desktop[1627]: state This set of messages including volumeRange and state is continuously repeated with a 2-sec interval while running the software. Usually it would be okay but occasionally it becomes annoying particularly when I look into the log files for other reasons. Is there any tweaks to avoid this continuous flow of messages? BTW, I didn't find anything abnormal in the HQP log. Thanks in advance.
  13. The graph is quite okay. I think if he can not find the background to explain why the manufacturer recommends I2S HDMI input, then he should have stopped his comment as that point; no need to bring up the USB data graph. As long as concerned with the Cyan DAC, I can say that playing and listening to DSD512 on HQP via the onboard USB DDC was not bad but also not so impressive when compared with the I2S/HDMI connection from the Hermes-BBB/Cronus (data signal isolated and reclocked on board, connected async to the Cyan), though not based on particular measurements. Regards,
  14. Thanks for this comment but I'm afraid to say that the data alone can not convince the USB superiority to I2S without comparison. Regards,
  15. Hi Miska, thank you for this comment. However, I'm a little confused with it. Shown below is part of the description from the Holo Audio-KTE Spring 2 page: ...snip... (This feature i’m most excited for, as many of you know that I highly recommend i2s hdmi input as being ideal connection with our dac) Currently I've been applying this I2S(HDMI) connection to My Cyan DSD DAC (via Hermes-BBB/Cronus from TPA) and have been quite satisified with this setting. Regards,
  • Create New...