Jump to content

acatala

Members
  • Content Count

    147
  • Joined

  • Last visited

About acatala

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The version 4.14 also had an update 4.14.1 only for OS image but not for the Debian package (or another Linux distribution). These .1 versions are meaningless for their respective packages? I mean, these .1 have only improvements for the OS images?
  2. From the log output from Luchoh, it seems that DSD512 is supported too. At least with the x64 image that is the one it should run in my UpBoard device. That's good news. I mean, UpBoard with NAA x64 image (3.x or 4.x) + Topping D90 (with AK4499). Right?
  3. Hi @Miska, Does NAA run in DSD native mode (at least DSD256) with AK4499 based DACs (Topping D90) and/or ES9038Pro (Topping DX7 Pro)? I have been reading some articles and review about both DACs and it seems nice piece of hardware.
  4. Hello @ALLOsupport / @Audio_Allo I few months ago (I think it was in February), I built a network DAC with these components: Allo Sparky Allo Kali Allo Piano 2.1 DAC Wi-Fi Adapter DietPi 6.x This device was in my second house, so I use it less than the main device in my house (Allo DigiOne with RoPieee). Both devices run as RoonBridge. The Piano device worked without issues until past friday. Before playing music, I updated DietPi to the current version 6.26.3. After that I played Roon and I noticed that the music played only to the left channel. After changing the cables attachment, I can confirm that only left channel worked. I checked all mixer parameters with aplay and amixer and all of them were correct. Actually, nobody modified them, so there was no reason for being misconfigured. I took the Piano DAC and installed it in my house, next to the Allo DigiOne. I can access DietPi, everything seems right but the DAC still plays only to the left channel. I don't know if there is a problem with Piano 2.1 DAC or, on the other hand, the problem is with Kali. Besides, I am not sure of this, but the left channel sound like slightly distorted. Maybe it is just a bad perception on my part. Have you any idea or any guide that helps me to figure out what is happening?
  5. I have upgraded Debian Stretch to Debian Buster in the NUC. After that, I have updated HQPlayer Embedded to 4.12.1. After the upgrade Roon didn't play with HQPlayer but it did to a DigiOne with RoPIee (my backup transport). I have restarted hqplayerd and it worked. I don't know what happened to it because it seemed it was working well, systemctl status hqplayerd didn't show anything wrong. The main issue is that, the fingerprint has changed. I guess due to the Debian upgrade, the hardware is the same NUC. I guess I will need a new key. I will send the new fingerprint to your e-mail.
  6. I will upgrade my Intel NUC. It should be easy to upgrade because I kept it with very few packages.
  7. Hi, I have noticed that the new version of HQPlayer Embedded 4.12.x for Debian is published in the buster directory and not in the stretch. Can I use it on a Debian 9 stretch machine?
  8. Thanks for your extended answer, @Miska. The scenario is this: Roon and HQPlayer Embedded run 24x7 on a Intel NUC Debian 9 box, NAA runs on a UP Gateway with your NAA image and is attached to the USB port of the embedded DAC in the preamp. The power on cycle is: Roon and HQPlayer ar 24x7, so no need of power them on most of the time. Power on DAC (actually preamp + amp) Power on NAA The power of cycle is: Stop playing Roon (+ HQPlayer Embedded) Shutdown NAA (Reset button pressing) + Power off it Power off DAC (Preamp + amp) The NAA is powered off before the DAC and yet the next time I play from Roon + HQPlayer Embedded I have to do the double play. Even, some times, the NAA remains running 24x7 a couple of days and I power off the DAC (preamp + amp) in the mean time and the behaviour is the same: I need the double play. In this case, the NAA doesn't fail even the DAC is powered on after him, I only have the double play issue. Weird, isn't it? On the other hand, the rest of the system seems solid rock and I have no further issues. Nice sound quality, easy to update, a bunch of configuration options... in short: happy with the duet Roon + HQPlayer Embedded.
  9. Yesterday, I installed the NAA 3.6.0 image on my Up Gateway's eMMC drive. The install process is simple ( https://audiophilestyle.com/forums/topic/13649-hqplayers-network-audio-adapter/?do=findComment&comment=964209 ). So far, I have not found any issues. I can still play native DSD and it seems it fixed the annoying problem with the shutdown process of the networkaudiod that went into a blocked state for a couple of minutes before closing. Now the shutdown process (after pushing the reset button) is a matter of seconds. The "double play click" is still present. Perhaps this is a specific issue between networkaudiod and the chipset of my DAC, I don't know. But after clicking the play control for thr fist time after powering on the system the music doesn't start, but it does after a second click. After that, it works fine. In either case, NAA is better now.
  10. I run Roon Core and HQPlayer Embedded on an Intel NUC7i7. HQPlayerd upsamples to DSD128 and performs no further processing. The Intel NUC can handle this load so, I have no need to use use further hardware. It works for me this way.
  11. The power off procedure works fine, as expected. The power on also works fine and Roon + HQPlayer play at the first attempt. I guess this is due to click the Apply button after changing the backend. HQPlayer becomes refreshed. The procedure works, although I think that too many steps are required. I can do them, but it can be too much to a plain user. The pressing power off button method is easier although in the next beginning a double play must be executed. Anyway, thanks to @Em2016.
  12. There is even a quicker way: Just push the button of the PSU 😀. NAA image is resilient enough. The only downside is that I have to click twice the play button. It's not perfect but it isn't a big deal either. In either case, when I come back to home I will try your suggested procedure.
  13. Thanks, @Em2016. I can see the point. Sometimes, one can be in a hurry and he/she just pushes the power button at the PSU. I can try this out of curiosity, it seems the way of powering the system off in a controlled way. The procedure would be: 1- Go HQPlayer Embedded webpage and change backend from network to ALSA (or another NAA) 2- Push reset button at Up Board. 3- After 2 second, Up Board is powered off and then power off the DAC. The next power on cycle would be: 1- Power on the DAC 2- Power on the NAA 3- Enter the HQPlayer webpage and change the backend from ALSA (or another NAA) to the actual NAA.
  14. I understand. Perhaps, because of this, HQPlayer is not notified that NAA is going down either. That's precisely the reason for using NAA in my case. To me, both options work fine, but this is a good reason to be the chosen one.
  15. Hi @Miska, here further information about the behaviour of NAA 3.5.6.1 with embedded DAC in Rotel RC-1590 (AKM 4495 based). The Up Gateway, where NAA runs, boots an image of NAA 3.5.6.1 from eMMC. I dettached the Up Gateway from the DAC and brought it to my desk just for testing. I attached a keyboard, a display and USB drive with HQPlayer OS 4.11. I wanted to boot from the USB drive without erasing the NAA image in eMMC drive. Once it booted, I checked out that the HQPlayer OS has not a SSH server enabled. OK, so it is not an option to do a remote power off. After that, I removed the USB drive and booted it again from the NAA image and I tested the reset button while watching the display. It took a couple of seconds or so while it went powered off. Wonderful! But when the UP Gateway is attached to the DAC, the power off procedure from the reset button takes around a minute, maybe a bit more. I presume that all this time is required by NAA while "fights" with the DAC before closing. Perhaps, NAA ends giving up and closes abruptly and it does not inform hqplayerd. So in the next run of Roon + HQPlayer I have to play twice. So, there is no benefit from executing a controled power off and I can power the Up Board off by pressing the power button at the PSU. I think you said that NAA image loads in memory, so I guess there is few chances of damaging the image. In case it fails, I can load it again in eMMC. I have not found any issues with HQPlayer Embedded 4.11 although I have not tested the new features, but it works fine in my system.
×
×
  • Create New...