asdf1000 Posted February 1, 2019 Share Posted February 1, 2019 Hi Jussi @Miska What is this new version for the bootable image: https://www.signalyst.eu/bins/naa/images/naa-3553-x64.7z What's changed/different? Link to comment
Miska Posted February 1, 2019 Share Posted February 1, 2019 13 hours ago, acatala said: Thanks @Miska. I will do some research with that. Perhaps it has to do with something specific to USBridge's DietPi. We'll see. USBridge's DietPi runs Roon Bridge and NAA at the same time. It seems it is not a big deal. Just in case, I disabled Roon Bridge but there was no difference at all. So I have enabled it again and I also enabled it as an output at Roon Core, just as a backup output for DSD. It shouldn't be a problem unless that endpoint is also enabled as output in Roon. Having both enabled in Roon is asking for trouble. It is also stated here: https://kb.roonlabs.com/HQPlayer_Setup acatala 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted February 1, 2019 Share Posted February 1, 2019 8 hours ago, Em2016 said: Hi Jussi @Miska What is this new version for the bootable image: https://www.signalyst.eu/bins/naa/images/naa-3553-x64.7z What's changed/different? It syncs up base OS with HQPlayer Embedded 4.8.0. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
asdf1000 Posted February 1, 2019 Share Posted February 1, 2019 1 hour ago, Miska said: It syncs up base OS with HQPlayer Embedded 4.8.0. Is that version also a ramrooted version NAA? If not, can you add “ramroot” to the filename of the one which is? Just to make it easier to differentiate from the one that isn’t. Although I guess the filesize is a hint? Link to comment
Miska Posted February 2, 2019 Share Posted February 2, 2019 1 hour ago, Em2016 said: Is that version also a ramrooted version NAA? If not, can you add “ramroot” to the filename of the one which is? Just to make it easier to differentiate from the one that isn’t. No "ramroot", but yes it runs out of RAM just like the 3552 too. asdf1000 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
asdf1000 Posted February 2, 2019 Share Posted February 2, 2019 3 minutes ago, Miska said: No "ramroot", but yes it runs out of RAM just like the 3552 too. Ok thanks. Is there going to be a 355 NAA version that syncs up base OS with HQPlayer Embedded 4.8.0, that isn't run out of RAM? Or are all future amd64 NAA versions going to be RAM run now? Not that I'm bothered at all, just for information only. Link to comment
Popular Post Miska Posted February 2, 2019 Popular Post Share Posted February 2, 2019 3 minutes ago, Em2016 said: Is there going to be a 355 NAA version that syncs up base OS with HQPlayer Embedded 4.8.0, that isn't run out of RAM? No, that's the HQPlayer OS image, aka HQPlayer Embedded image. Not much point in making many too similar versions... 4 minutes ago, Em2016 said: Or are all future amd64 NAA versions going to be RAM run now? Yes, for the time being that is the plan. For ARM I still keep it traditional way because those tend not have as much RAM, so it is better used for other purposes. For example the smallest NAA device I have has just 64 MB of RAM while the OS takes more than that... ferenc and asdf1000 1 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
asdf1000 Posted February 2, 2019 Share Posted February 2, 2019 Just now, Miska said: No, that's the HQPlayer OS image, aka HQPlayer Embedded image. Not much point in making many too similar versions... Ah yes, I wonder why the file size was so huge for NAA. All clear now. Is Embedded now fully running in RAM, or just the NAA functionality parts runs in RAM? Link to comment
Miska Posted February 2, 2019 Share Posted February 2, 2019 14 minutes ago, Em2016 said: Is Embedded now fully running in RAM, or just the NAA functionality parts runs in RAM? Everything anyway runs fully in RAM... I personally don't understand the craze about "ramroot" stuff. But Embedded image is normal setup where rootfs is on the storage and both HQPlayer Embedded and NAA functionality run in ordinary way. NAA image is one where the rootfs is in RAM. asdf1000 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
acatala Posted February 2, 2019 Share Posted February 2, 2019 10 hours ago, Miska said: It shouldn't be a problem unless that endpoint is also enabled as output in Roon. Having both enabled in Roon is asking for trouble. It is also stated here: https://kb.roonlabs.com/HQPlayer_Setup It is not enable in Roon in a regular basis. It just was enabled one day while I was testing. Link to comment
ferenc Posted February 2, 2019 Share Posted February 2, 2019 If I want to use an "ultimate" NAA machine with my Hqplayer running on a 18 core iMac Pro, what would be the way to reach my NAA Nirvana? Pimp an SoTM SMS200Ultra or xxxxRendu (or such) with all sorts of external clocks, clocked switch, etc or to build something which can use clocks for mobo, usb card, ethernet, like Pink Faun, PPA or Jcat respective products and solutions? If cost would be no object? Any advice? I do not need Roon endpoint, just NAA handling DSD1024 or 1,536 kHz PCM with my Holo Audio Spring 2. Link to comment
kelvinwsy Posted February 2, 2019 Share Posted February 2, 2019 Sotm sm200 ultra not stable at DSD512 .. sweet spot is DSD256.. Can try a fanless NUC running Jussi"s @Miska Linux /Win 10 NAA .. With a powerful HQplayer PC and aRTX 2080ti u shld get up to DSD 512 even with th tougher filters Only Jussi may know the HW needed to reach DSD1024🤔 Maybe a i9. 9900k with tge RTX 2080 ti? Link to comment
ferenc Posted February 2, 2019 Share Posted February 2, 2019 1 hour ago, kelvinwsy said: Sotm sm200 ultra not stable at DSD512 .. sweet spot is DSD256.. Can try a fanless NUC running Jussi"s @Miska Linux /Win 10 NAA .. With a powerful HQplayer PC and aRTX 2080ti u shld get up to DSD 512 even with th tougher filters Only Jussi may know the HW needed to reach DSD1024🤔 Maybe a i9. 9900k with tge RTX 2080 ti? my sms200 Neo work stable with DSD512, I got no problem with it at all. I expect my iMac Pro to provide at least a good chance for the -2s DSD1024 from 44,1kHz FLAC. It works well with DSD512 in poly-sync / DSD7. Link to comment
kelvinwsy Posted February 2, 2019 Share Posted February 2, 2019 Oh.. of course I was referring to my system on xtr -2s GTX970 cant quite hack it without going down to the polysinc Hb filters But not certain the 8700k can do the xtr?? Most likely with stuttering once a while and with at least the 1080 GPU Link to comment
tboooe Posted February 2, 2019 Share Posted February 2, 2019 Is anyone using a NUC8i3 as the NAA. I am specifically interested in knowing if the fan turns on while streaming music? Do the temps stay low while listening to music? I know I can turn off the fan in bios but of course I don't want to fry the cpu. 12TB NAS >> i7-6700 Server/Control PC >> i3-5015u NAA >> Singxer SU-1 DDC (modded) >> Holo Spring L3 DAC >> Accustic Arts Power 1 int amp >> Sonus Faber Guaneri Evolution speakers + REL T/5i sub (x2) Other components: UpTone Audio LPS1.2/IsoRegen, Fiber Switch and FMC, Windows Server 2016 OS, Audiophile Optimizer 3.0, Fidelizer Pro 6, HQ Player, Roonserver, PS Audio P3 AC regenerator, HDPlex 400W ATX & 200W Linear PSU, Light Harmonic Lightspeed Split USB cable, Synergistic Research Tungsten AC power cords, Tara Labs The One speaker cables, Tara Labs The Two Extended with HFX Station IC, Oyaide R1 outlets, Stillpoints Ultra Mini footers, Hi-Fi Tuning fuses, Vicoustic/RealTraps/GIK room treatments Link to comment
luisma Posted February 2, 2019 Share Posted February 2, 2019 Just prepared my Celeron fanless PC with Miska's NAA image, it boots, networkaudiod is running as a process but HQPE doesn't see it. The network connection is back to back with a cable between both the NAA (Miska's bootable image) and the HQPE (running my minimal Ubuntu install) I see the ethernet IPv6 stack enabled, don't know what could be happening but let me try again this doesn't make sense. the NAA doesn't get an IPv4 IP but that should not matter. Link to comment
luisma Posted February 2, 2019 Share Posted February 2, 2019 Jussi maybe you can suggest something. Ubuntu Minimal Fanless PC HQPE+ROON --- Network cable ---> NAA running your bootable image the new one --- USB ---> Denafrips with Amanero On the HQPE PC looks IPv6 connectivity is there root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router REACHABLE root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router REACHABLE root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router REACHABLE root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router STALE root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router DELAY root@nucplayer:~# ip -6 n sh fe80::22e5:2aff:fe6f:322f dev wlp2s0 lladdr 20:e5:2a:6f:32:2f router REACHABLE HQPE using network audio The weird thing is that is still have the Allo Bridge I was using before as the NAA like it doesn't see the new networkaudio NAA, the networkaudiod process from your image is running when I do a ps Could it be the NAA image is not seeing the DAC? This is the log of HQPE (last version) 2019/02/02 16:53:41 libDSP version 20.6.0 2019/02/02 16:53:41 HQPlayer Engine version 4.10.0 2019/02/02 16:53:41 Number of processor cores: 2 2019/02/02 16:53:41 DSP thread pools disabled 2019/02/02 16:53:41 Pipelined DSP disabled 2019/02/02 16:53:41 Audio engine: network 2019/02/02 16:53:41 Network Audio IPv6 support enabled 2019/02/02 16:53:41 Discovery from :: 2019/02/02 16:53:43 Discovered 0 Network Audio Adapters 2019/02/02 16:53:43 Output set channels: 2 (2) ! 2019/02/02 16:53:43 clPlayerDaemon::CreateEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found - 2019/02/02 16:53:43 Network engine stopping... % 2019/02/02 16:53:43 ...configuration reloaded 2019/02/02 16:53:49 asoundlib version: 1.1.3 2019/02/02 16:53:49 Network Audio IPv6 support enabled 2019/02/02 16:53:49 Discovery from :: Link to comment
luisma Posted February 2, 2019 Share Posted February 2, 2019 I'm just testing something, since I disabled I whole bunch of things on the BIOS that may be the reason, though USB works for the flash drive and the keyboard it may not for the DAC or networkaudiod on initialization. Set the BIOS to defaults and the booting of the NAA image is completely different, takes longer too Testing now ... Link to comment
luisma Posted February 2, 2019 Share Posted February 2, 2019 Seems IPv6 network has an issue of some sorts root@nucplayer:~# ping -6 fe80::22e5:2aff:fe6f:322f%eno1 PING fe80::22e5:2aff:fe6f:322f%eno1(fe80::22e5:2aff:fe6f:322f%eno1) 56 data bytes From fe80::96c6:91ff:fe1b:25f%eno1 icmp_seq=1 Destination unreachable: Address unreachable From fe80::96c6:91ff:fe1b:25f%eno1 icmp_seq=2 Destination unreachable: Address unreachable From fe80::96c6:91ff:fe1b:25f%eno1 icmp_seq=3 Destination unreachable: Address unreachable @Miska on your bootable image I can set a static IP? I guess I can look for the interfaces file there and edit it Link to comment
luisma Posted February 2, 2019 Share Posted February 2, 2019 I'm out of options, there is connectivity but the network device still shows the previous one This is the log of HQPE, how can I get the log on your image on the NAA? * 2019/02/02 18:04:52 Signalyst HQPlayer 4 Embedded 4.8.0 + 2019/02/02 18:04:52 Engine starting... 2019/02/02 18:04:52 libDSP version 20.6.0 2019/02/02 18:04:52 HQPlayer Engine version 4.10.0 2019/02/02 18:04:52 Number of processor cores: 2 2019/02/02 18:04:52 DSP thread pools disabled 2019/02/02 18:04:52 Pipelined DSP disabled 2019/02/02 18:04:52 Audio engine: network 2019/02/02 18:04:52 Network Audio IPv6 support disabled 2019/02/02 18:04:52 Discovery from 0.0.0.0 2019/02/02 18:04:53 Discovered 0 Network Audio Adapters 2019/02/02 18:04:53 Output set channels: 2 (2) ! 2019/02/02 18:04:53 clPlayerDaemon::CreateEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found - 2019/02/02 18:04:53 Network engine stopping... + 2019/02/02 18:04:53 Server starting... 2019/02/02 18:04:56 asoundlib version: 1.1.3 2019/02/02 18:04:56 Network Audio IPv6 support enabled 2019/02/02 18:04:56 Discovery from :: - 2019/02/02 18:04:58 Network engine stopping... 2019/02/02 18:04:58 asoundlib version: 1.1.3 2019/02/02 18:04:58 Network Audio IPv6 support enabled 2019/02/02 18:04:58 Discovery from :: - 2019/02/02 18:05:00 Network engine stopping... 2019/02/02 18:05:33 asoundlib version: 1.1.3 2019/02/02 18:05:33 Network Audio IPv6 support enabled 2019/02/02 18:05:33 Discovery from :: - 2019/02/02 18:05:35 Network engine stopping... 2019/02/02 18:05:35 asoundlib version: 1.1.3 2019/02/02 18:05:35 Network Audio IPv6 support enabled 2019/02/02 18:05:35 Discovery from :: - 2019/02/02 18:05:37 Network engine stopping... 2019/02/02 18:05:43 Web configuration written 2019/02/02 18:05:43 asoundlib version: 1.1.3 2019/02/02 18:05:43 Network Audio IPv6 support enabled 2019/02/02 18:05:43 Discovery from :: - 2019/02/02 18:05:45 Network engine stopping... % 2019/02/02 18:05:45 Reloading configuration... 2019/02/02 18:05:45 libDSP version 20.6.0 2019/02/02 18:05:45 HQPlayer Engine version 4.10.0 2019/02/02 18:05:45 Number of processor cores: 2 2019/02/02 18:05:45 DSP thread pools disabled 2019/02/02 18:05:45 Pipelined DSP disabled 2019/02/02 18:05:45 Audio engine: network 2019/02/02 18:05:45 Network Audio IPv6 support enabled 2019/02/02 18:05:45 Discovery from :: 2019/02/02 18:05:47 Discovered 0 Network Audio Adapters 2019/02/02 18:05:47 Output set channels: 2 (2) ! 2019/02/02 18:05:47 clPlayerDaemon::CreateEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found - 2019/02/02 18:05:47 Network engine stopping... % 2019/02/02 18:05:47 ...configuration reloaded 2019/02/02 18:05:53 asoundlib version: 1.1.3 2019/02/02 18:05:53 Network Audio IPv6 support enabled 2019/02/02 18:05:53 Discovery from :: - 2019/02/02 18:05:55 Network engine stopping... 2019/02/02 18:05:55 asoundlib version: 1.1.3 2019/02/02 18:05:55 Network Audio IPv6 support enabled 2019/02/02 18:05:55 Discovery from :: - 2019/02/02 18:05:57 Network engine stopping... Link to comment
Miska Posted February 2, 2019 Share Posted February 2, 2019 1 hour ago, luisma said: @Miska on your bootable image I can set a static IP? I guess I can look for the interfaces file there and edit it On the HQPlayer OS image you can, since it doesn't have rootfs in RAM. Please see documentation here: https://www.freedesktop.org/software/systemd/man/systemd.network.html Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
Miska Posted February 2, 2019 Share Posted February 2, 2019 46 minutes ago, luisma said: I'm out of options, there is connectivity but the network device still shows the previous one This is the log of HQPE, how can I get the log on your image on the NAA? How does your network layout look like? There are no NAA's found. In most cases the problem has been someone trying to use multi-homed setup in the HQPlayer computer. IOW, one with more than one network interface and network. You can either first stop the service with "systemctl stop networkaudiod" and then run "networkaudiod" from terminal. Or alternatively set NETWORKAUDIOD_LOGFILE environment variable to point to a log file. By default it ends up in system journal, so for example "journalctl -a" should tell something. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
luisma Posted February 3, 2019 Share Posted February 3, 2019 4 hours ago, Miska said: multi-homed The HQPE is multihomed but don't have a problem with my Ubuntu naa or the allo Bridge naa, it's been like that for more than 6 months, of course maybe with the image it have an issue I don't know. Let me start it manually and see what happens and enable the log Thanks Jussi. Link to comment
luisma Posted February 3, 2019 Share Posted February 3, 2019 I'm going to continue looking to solve this. In the meantime I found this. On the NAA Starting networkaudiod. I see the process reporting "clSocket::SetOption() .... no such device, I believe it is looking for the network device (HQPE in this case) connected back to back. The enp1s0 interface is UP BROADCAST RUNNING MULTICAST with an IP6 address and LINK however doesn't seem to connect with HQPE. This is the ifconfig output and the error, by the way the DAC is device number 9 using xhci _hcd On the HQPE side this is my ifconfig, eno1 is the one connected back to back with link to the NAA, it has a statically assigned IP4 and automatic IP6 addresses. root@nucplayer:~# ifconfig eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.96.224 netmask 255.255.255.0 broadcast 192.168.96.255 inet6 fe80::96c6:91ff:fe1b:25f prefixlen 64 scopeid 0x20<link> ether 94:c6:91:1b:02:5f txqueuelen 1000 (Ethernet) RX packets 7 bytes 2310 (2.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1325 bytes 89600 (89.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xdfc00000-dfc20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1351 bytes 311739 (311.7 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1351 bytes 311739 (311.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.95.225 netmask 255.255.255.0 broadcast 192.168.95.255 inet6 2603:3020:2025:8000:6aec:c5ff:fe2a:2501 prefixlen 64 scopeid 0x0<global> inet6 fe80::6aec:c5ff:fe2a:2501 prefixlen 64 scopeid 0x20<link> inet6 2603:3020:2025:8000:9523:1c65:d29f:7267 prefixlen 64 scopeid 0x0<global> ether 68:ec:c5:2a:25:01 txqueuelen 1000 (Ethernet) RX packets 455 bytes 119557 (119.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 310 bytes 52470 (52.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Link to comment
luisma Posted February 3, 2019 Share Posted February 3, 2019 Just for more testing I added a static IP4 to the enp1s0 interface on the NAA and I can ping the HQPE interface with no issues, there is IP4 connectivity and IP6 connectivity however starting networkaudiod gives me the same error setsockopt(): No such device Restarted the HQPE service with the networkaudiod running with IP connectivity same issue and eventually networkaudiod gives up Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now