twluke

Du you mean the Amanero firmware? If so, the answer is no because the updating process includes erasing the firmware chip. Anyway, the process itself is quite simple and you can repeat it many times until you accustom to it. BTW, for CPLD, select CPLD for 1081 (not 1080) or you will have to select "CPLD_1081_DSDSWAPPED" if there is a problem of LR channel swap after update. For firmware, always select 2006be10 which enables native DSD512 on linux (and on Win10). If you need an ASIO driver for Win10, search this GitHub Amanero issue thread. You can find the location by the post from Domenico, the author of Amanero firmware. Rgds,

No. Go to: https://amanero.com/combo384_firmware.htm Find the name of firmware_2006be10, then download the file right to it (oem tool 117). Read carefully the manual in it as well as the instruction from T+A. Once more: READ them many times until you fully understand them. Rgds,

Congratulations. But the culprit of your firmware update problem appears all deriving from using a wrong pin assignment between RJ11/12 and RS232 cables. If the pin assignment was correct before the initiation of firmware update, the service tool would have opened smoothly and you could have gone straight to the updating process without such sweating. Please keep your experience to your own and do not extend it to others. Rgds,

Hmm, now the possible causes may be: incorrect RS232 connection or corrupted tool.exe file. If the case is the latter, you might try this one which I previously received from T+A.

Some correction. The service tool application may usually open at the user level privilege, if you already have the firmware text file to be uploaded to the DAC on your PC.

Are you trying to open it as administrator? If not, it won't open (though it is my simple guess).

Leave the "1" unconnected. It is of no use for this serial connection as indicated in the T+A instruction below. Rgds,

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.

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.

Please ignore.

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.

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.

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,

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,

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.