jabbr Posted July 16, 2018 Share Posted July 16, 2018 @Miska : any plans to support ARM in hqplayerd? The NVidia Jetson architecture looks interesting ... Custom room treatments for headphone users. Link to comment
jabbr Posted July 19, 2018 Share Posted July 19, 2018 On 7/16/2018 at 6:31 AM, Miska said: Yes, but still haven't got time to try it out. I have a Jetson TX2 board... The Xavier is calling me ... need a reason to get Custom room treatments for headphone users. Link to comment
jabbr Posted March 10, 2019 Share Posted March 10, 2019 6 hours ago, Miska said: I have two servers running 18.04 Server, with only ssh-server selected from the installer. Network configured through /etc/network/interfaces same way as on Debian. I only replaced the kernel with my own one. But other than that I didn't need to modify the installation and didn't notice much unnecessary extra, just added the things needed by HQPlayer Embedded. I assume that the only reason to use your kernel would be direct attach DAC/ALSA ... I'm using HQPe on an application server with stock kernel (Ubuntu 18.10). I could swap it in if there were a benefit but I'm trying to minimize variables at this point as I install all the upgrades to the server (starting with a Dell T420 E5-2440, 48Gb ECC) ... Custom room treatments for headphone users. Link to comment
jabbr Posted March 10, 2019 Share Posted March 10, 2019 6 minutes ago, Miska said: Depends on what you want... But overall I would stay away from short-term Ubuntu releases. If you want bleeding edge, I'd rather go with Fedora. No doubt there are advantages and disadvantages ... I'm most familiar with debian/ubuntu ... the third parties/hardware folks seem to support ubuntu better e,g, NVidia and Mellanox, for example the Mellanox drivers are currently at 18.10 Ubuntu but Fedora 28 .... my point/question is that I am assuming things like RT and the ALSA mods that are available in your image would have no bearing on a server that only intends to serve NAAs, correct? Custom room treatments for headphone users. Link to comment
jabbr Posted March 10, 2019 Share Posted March 10, 2019 3 hours ago, Miska said: Yes, not as much... But for Ubuntu I'd rather stick with LTS ones unless you really want to go through the trouble of switching over to another version every six months and risking hardware support. At least Nvidia won't be very quick to follow, so be prepared to be in a strange gap for months if you go with non-LTS. P.S. Isn't Mellanox supported by the mainline kernel without need for 3rd party drivers? Ok, this is great advice for most people ... I'm prepared to reinstall on 18.04 if problems encountered... Mellanox ... I like to use the latest drivers for some of this stuff, for example the included IXGBE driver somehow doesn't work for me and I recompile on my machine ... but in general folks should stick with LTS. Custom room treatments for headphone users. Link to comment
jabbr Posted March 16, 2019 Share Posted March 16, 2019 You can download a linux distribution (debian stretch or ubuntu bionic) from https://www.armbian.com/clearfog-base/ so stock 4.14.y though I'm running 4.18.8 (mvebu has been mainlined as far as I know) Custom room treatments for headphone users. Link to comment
jabbr Posted March 19, 2019 Share Posted March 19, 2019 What is the correct way to get "multicore DSP" in hqplayer-embedded? In my hqplayerd.xml file if I set either <engine multicore="auto" ..> or <engine multicore="1" ...> I seem to get 4 main threads (htop) and two have utilization 98-100% and the other two 50% ... this is with 2x E5-2470 V2 -- with DSD64 source This causes intermittent stuttering at DSD512 regardless of DSD or PCM input and regardless of filters etc. Is this the correct setting? Any way to use more threads/cores? Custom room treatments for headphone users. Link to comment
jabbr Posted March 19, 2019 Share Posted March 19, 2019 2019/03/19 19:48:54 Signalyst HQPlayer 4 Embedded 4.9.0 + 2019/03/19 19:48:54 Engine starting... 2019/03/19 19:48:54 libDSP version 20.7.1 2019/03/19 19:48:54 HQPlayer Engine version 4.11.1 2019/03/19 19:48:54 CUDA offload requested 2019/03/19 19:48:54 Number of processor cores: 20 2019/03/19 19:48:54 DSP thread pools enabled (10) 2019/03/19 19:48:54 Pipelined DSP enabled 2019/03/19 19:48:54 Audio engine: network 2019/03/19 19:48:54 Network Audio IPv6 support disabled 2019/03/19 19:48:54 Discovery from 0.0.0.0 & 2019/03/19 19:48:54 Discovered network audio: name='clearfogbase' version='Signalyst Network Audio Daemon 3.5.5' @192.168.1.39:43210 & 2019/03/19 19:48:54 Discovered network audio: name='clearfogbase' version='Signalyst Network Audio Daemon 3.5.5' @192.168.1.39:43210 & 2019/03/19 19:48:54 Discovered network audio: name='espressobin' version='Signalyst Network Audio Daemon 3.5.5' @192.168.1.30:43210 2019/03/19 19:48:55 Network endpoint: iFi (by AMR) HD USB Audio: USB Audio (hw:CARD=Audio,DEV=0) 2019/03/19 19:48:56 Network endpoint: Pre Box S2 Digital: USB Audio (hw:CARD=Digital,DEV=0) 2019/03/19 19:48:56 Network endpoint: Loopback: Loopback PCM (hw:CARD=Loopback,DEV=0) 2019/03/19 19:48:56 Network endpoint: Loopback: Loopback PCM (hw:CARD=Loopback,DEV=1) 2019/03/19 19:48:56 Discovered 2 Network Audio Adapters 2019/03/19 19:48:56 Output set channels: 2 (2) + 2019/03/19 19:48:56 Connect to 192.168.1.39:43210 2019/03/19 19:48:56 Network format: 44100/32/2 [pcm] 2019/03/19 19:48:56 Network format: 48000/32/2 [pcm] 2019/03/19 19:48:56 Network format: 88200/32/2 [pcm] 2019/03/19 19:48:56 Network format: 96000/32/2 [pcm] 2019/03/19 19:48:56 Network format: 176400/32/2 [pcm] 2019/03/19 19:48:56 Network format: 192000/32/2 [pcm] 2019/03/19 19:48:56 Network format: 352800/32/2 [pcm] 2019/03/19 19:48:56 Network format: 384000/32/2 [pcm] 2019/03/19 19:48:56 Network format: 705600/32/2 [pcm] 2019/03/19 19:48:56 Network format: 768000/32/2 [pcm] 2019/03/19 19:48:56 Network format: 2822400/1/2 [dsd] 2019/03/19 19:48:56 Network format: 3072000/1/2 [dsd] 2019/03/19 19:48:56 Network format: 5644800/1/2 [dsd] 2019/03/19 19:48:56 Network format: 6144000/1/2 [dsd] 2019/03/19 19:48:56 Network format: 11289600/1/2 [dsd] 2019/03/19 19:48:56 Network format: 12288000/1/2 [dsd] 2019/03/19 19:48:56 Network format: 22579200/1/2 [dsd] 2019/03/19 19:48:56 Network format: 24576000/1/2 [dsd] 2019/03/19 19:48:56 Input set channels: 2 (2) 2019/03/19 19:48:56 Hardware volume control disabled 2019/03/19 19:48:56 Volume max: 0 2019/03/19 19:48:56 Volume min: -60 2019/03/19 19:48:56 Volume scaler: 0.75 2019/03/19 19:48:56 Set volume: -3 2019/03/19 19:48:56 Automatic rate family enabled 2019/03/19 19:48:56 DirectSDM disabled 2019/03/19 19:48:56 SDM conversion parameters (5, 0) 2019/03/19 19:48:56 DSD 6 dB gain enabled 2019/03/19 19:48:56 Initial parallel threads: 40 2019/03/19 19:48:56 Number of logical cores: 40 Custom room treatments for headphone users. Link to comment
jabbr Posted March 19, 2019 Share Posted March 19, 2019 1 [ 0.0%] 11 [ 0.0%] 21 [ 0.0%] 31 [ 0.0%] 2 [| 2.0%] 12 [||||||||||| 24.8%] 22 [|| 2.6%] 32 [||||||||||| 23.5%] 3 [ 0.0%] 13 [ 0.0%] 23 [|||||||||||||||||||||||||||||||||||95.4%] 33 [ 0.0%] 4 [||||||||||||||||||| 47.4%] 14 [| 1.3%] 24 [ 0.0%] 34 [|| 1.3%] 5 [ 0.0%] 15 [ 0.0%] 25 [ 0.0%] 35 [ 0.0%] 6 [||||||| 14.9%] 16 [| 1.3%] 26 [| 0.7%] 36 [ 0.0%] 7 [| 0.6%] 17 [ 0.0%] 27 [ 0.0%] 37 [ 0.0%] 8 [|| 2.0%] 18 [ 0.0%] 28 [|||||||||||||| 33.1%] 38 [| 0.7%] 9 [| 0.6%] 19 [ 0.0%] 29 [ 0.0%] 39 [| 0.7%] 10 [| 1.3%] 20 [ 0.0%] 30 [| 1.3%] 40 [|||||||||||||||||||||||||||||||||||98.7%] Mem[||||||||| 5.24G/157G] Tasks: 36, 314 thr; 6 running Swp[ 0K/8.00G] Load average: 6.45 5.43 3.48 Uptime: 00:21:27 PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 22450 hqplayer 10 -10 11.6G 628M 174M S 293. 0.4 13:46.90 /usr/bin/hqplayerd 27122 hqplayer 10 -10 11.6G 628M 174M R 98.2 0.4 4:32.36 /usr/bin/hqplayerd 27124 hqplayer 10 -10 11.6G 628M 174M R 94.9 0.4 4:22.57 /usr/bin/hqplayerd 27123 hqplayer 10 -10 11.6G 628M 174M R 50.4 0.4 2:21.75 /usr/bin/hqplayerd 27121 hqplayer 10 -10 11.6G 628M 174M R 49.1 0.4 2:19.41 /usr/bin/hqplayerd 20668 root 20 0 7835M 2381M 226M S 45.8 1.5 6:31.20 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 28452 root 20 0 7835M 2381M 226M S 32.1 1.5 0:11.35 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 23382 root 20 0 7835M 2381M 226M D 5.2 1.5 0:25.02 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 27755 root 20 0 7835M 2381M 226M S 3.9 1.5 0:12.05 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 20909 root 20 0 7835M 2381M 226M D 2.0 1.5 0:14.13 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 27754 jon 20 0 33152 5732 3912 R 2.0 0.0 0:04.13 htop 26843 hqplayer 10 -10 11.6G 628M 174M R 1.3 0.4 0:07.97 /usr/bin/hqplayerd 27731 root 20 0 7835M 2381M 226M S 0.7 1.5 0:05.09 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 20678 root 20 0 7835M 2381M 226M S 0.7 1.5 0:01.20 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 20688 root 20 0 7835M 2381M 226M S 0.0 1.5 1:40.08 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 27756 root 20 0 7835M 2381M 226M S 0.0 1.5 0:18.81 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 21308 root 20 0 7835M 2381M 226M S 0.0 1.5 0:01.63 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 20910 root 20 0 7835M 2381M 226M S 0.0 1.5 0:00.64 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 27126 hqplayer 10 -10 11.6G 628M 174M S 0.0 0.4 0:00.11 /usr/bin/hqplayerd 20681 root 20 0 7835M 2381M 226M S 0.0 1.5 0:01.84 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 20682 root 20 0 7835M 2381M 226M S 0.0 1.5 0:00.96 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 3986 root 20 0 548M 46076 17444 S 0.0 0.0 0:00.05 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe 27915 root 20 0 7835M 2381M 226M S 0.0 1.5 0:13.79 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 26903 root 20 0 7835M 2381M 226M S 0.0 1.5 0:14.46 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 21040 root 20 0 7835M 2381M 226M S 0.0 1.5 0:00.22 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=44883 27757 root 20 0 7835M 2381M 226M S 0.0 1.5 0:28.82 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonApplianc htop indicates only 4 active threads ... Custom room treatments for headphone users. Link to comment
jabbr Posted March 19, 2019 Share Posted March 19, 2019 Ok maybe this, log says: 2019/03/19 19:52:33 Nested parallelism: 0 2019/03/19 19:52:33 Parallel pipelines: 4 any way to increase the number of pipelines? Custom room treatments for headphone users. Link to comment
jabbr Posted March 19, 2019 Share Posted March 19, 2019 When I set SDM conversion = "narrow", then stuttering stops on DSD playback For PCM conversion, the CPU utliization seems not to change with various settings/filters (assuming DSD512) and there is slight stuttering -- so is it that the E5-2470 v2 inadequate CPU? I was hoping to be able to use this as both an application server/tensorlink platform, as well as HQPe when I'm at home Custom room treatments for headphone users. Link to comment
jabbr Posted March 20, 2019 Share Posted March 20, 2019 1 hour ago, Miska said: I think your challenge is more on running the non-parallelizable tasks than those that can be. While keeping same filter, you could try some different modulator like DSD5 and see how much it makes difference. Ok DSD5 drops the core usage down to 80/80/60/60 and the sound is smooth with xtr-mp-2s, but still stuttering at xtr-mp 🙇♀️ Custom room treatments for headphone users. Link to comment
jabbr Posted March 24, 2019 Share Posted March 24, 2019 On 3/20/2019 at 3:55 AM, Miska said: Do you still get uneven core load with xtr-mp? Or are you using CUDA? If CUDA is in use, then that explains why the load is not spread more. Right, without CUDA: 1 [||||||||||||||||||||||||||||| 71.5%] 11 [||||||||||| 25.5%] 21 [||||||||||||||||||||||||||| 66.7%] 31 [|||||||||||||||||||| 49.0%] 2 [ 0.0%] 12 [|||||||||||||||||||| 48.1%] 22 [|| 1.3%] 32 [ 0.0%] 3 [|||||||||||||||||||||||||||||| 74.5%] 13 [ 0.0%] 23 [ 0.0%] 33 [|||||||||||||||||||| 48.7%] 4 [|||||| 14.5%] 14 [| 0.6%] 24 [|||||||||||||| 34.2%] 34 [||||||||||||||||||||||||||||| 71.2%] 5 [|||||||||||||||||||| 49.7%] 15 [|||||||||||||||||||||||||||| 69.7%] 25 [ 0.0%] 35 [|||||||||||||||||||||||||||| 69.9%] 6 [ 0.0%] 16 [| 1.3%] 26 [|||||||||||||||||||| 48.4%] 36 [ 0.0%] 7 [||||||||||||||||||| 47.1%] 17 [||||||||||||||| 35.9%] 27 [||||||||||||||||||||||||| 60.1%] 37 [||||| 12.4%] 8 [ 0.0%] 18 [ 0.0%] 28 [ 0.0%] 38 [|||||||||||||||||||| 48.7%] 9 [|||||||||||||||||||||||| 56.2%] 19 [|||||||||||||||||||||||||||| 69.3%] 29 [||||||||||||||||||||||||||| 66.0%] 39 [|||||||||||||||||||||||||||| 69.7%] 10 [|||||||||| 24.8%] 20 [|||||||||||||||||||| 47.7%] 30 [|| 2.0%] 40 [ 0.0%] Mem[||||||||||||| 5.32G/157G] Tasks: 37, 341 thr; 5 running Swp[ 0K/8.00G] Load average: 11.60 6.01 3.77 Uptime: 15:03:49 PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 26483 hqplayer 10 -10 6816M 238M 26072 S 1251 0.1 25:54.19 /usr/bin/hqplayerd 27014 hqplayer 10 -10 6816M 238M 26072 S 71.2 0.1 1:18.35 /usr/bin/hqplayerd 27005 hqplayer 10 -10 6816M 238M 26072 S 71.2 0.1 1:19.77 /usr/bin/hqplayerd 27011 hqplayer 10 -10 6816M 238M 26072 S 71.2 0.1 1:04.80 /usr/bin/hqplayerd 27018 hqplayer 10 -10 6816M 238M 26072 R 70.5 0.1 1:28.53 /usr/bin/hqplayerd 27007 hqplayer 10 -10 6816M 238M 26072 R 70.5 0.1 1:29.32 /usr/bin/hqplayerd 27015 hqplayer 10 -10 6816M 238M 26072 S 70.5 0.1 1:08.59 /usr/bin/hqplayerd 27001 hqplayer 10 -10 6816M 238M 26072 S 70.5 0.1 1:13.55 /usr/bin/hqplayerd 27002 hqplayer 10 -10 6816M 238M 26072 S 69.2 0.1 1:16.54 /usr/bin/hqplayerd 27016 hqplayer 10 -10 6816M 238M 26072 S 69.2 0.1 1:10.18 /usr/bin/hqplayerd 27009 hqplayer 10 -10 6816M 238M 26072 S 64.7 0.1 1:14.62 /usr/bin/hqplayerd 26999 hqplayer 10 -10 6816M 238M 26072 S 59.4 0.1 1:14.72 /usr/bin/hqplayerd 27008 hqplayer 10 -10 6816M 238M 26072 S 52.9 0.1 1:05.15 /usr/bin/hqplayerd 27000 hqplayer 10 -10 6816M 238M 26072 S 49.6 0.1 1:13.56 /usr/bin/hqplayerd 26998 hqplayer 10 -10 6816M 238M 26072 S 49.0 0.1 1:12.88 /usr/bin/hqplayerd 27004 hqplayer 10 -10 6816M 238M 26072 S 48.3 0.1 1:06.62 /usr/bin/hqplayerd 26997 hqplayer 10 -10 6816M 238M 26072 S 48.3 0.1 1:12.53 /usr/bin/hqplayerd 27003 hqplayer 10 -10 6816M 238M 26072 S 48.3 0.1 1:14.01 /usr/bin/hqplayerd 27012 hqplayer 10 -10 6816M 238M 26072 S 47.7 0.1 1:15.51 /usr/bin/hqplayerd 27010 hqplayer 10 -10 6816M 238M 26072 S 47.7 0.1 1:04.09 /usr/bin/hqplayerd 27013 hqplayer 10 -10 6816M 238M 26072 S 47.0 0.1 1:06.31 /usr/bin/hqplayerd 24223 root 20 0 9442M 2265M 287M S 26.8 1.4 12:44.86 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=37031 27006 hqplayer 10 -10 6816M 238M 26072 R 26.1 0.1 0:29.80 /usr/bin/hqplayerd 17211 root 20 0 9442M 2265M 287M S 25.5 1.4 0:44.59 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=37031 27017 hqplayer 10 -10 6816M 238M 26072 R 25.5 0.1 0:29.93 /usr/bin/hqplayerd 28716 jon 20 0 33156 5780 3984 R 2.0 0.0 0:01.28 htop 24250 root 20 0 9442M 2265M 287M S 0.7 1.4 0:03.71 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=37031 24249 root 20 0 9442M 2265M 287M S 0.7 1.4 0:01.18 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=37031 26792 root 20 0 9442M 2265M 287M S 0.7 1.4 0:00.26 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=37031 24760 root 20 0 9442M 2265M 287M S 0.7 1.4 0:00.86 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogpo Bad stuttering, not usable Custom room treatments for headphone users. Link to comment
jabbr Posted March 24, 2019 Share Posted March 24, 2019 With xtr-mp @ DSD512 and using CUDA on the RTX 2080 Ti/Founders Edition, there is intermittent stuttering, perhaps every 10sec or so, but this makes it very much not ideal. Hard to tell if switching to the i9-9900k would fix that, or even the i7-9900x which has a more reasonable number of PCIe lanes. Custom room treatments for headphone users. Link to comment
jabbr Posted March 24, 2019 Share Posted March 24, 2019 1 minute ago, Miska said: I guess the 1251% one is the main process with aggregate load, consuming 12.5 cores worth. But overall seems to spread load over 22 cores. Yes, 22 threads (20 cores total). But xtr is not listenable due to continuous stuttering. Custom room treatments for headphone users. Link to comment
jabbr Posted March 24, 2019 Share Posted March 24, 2019 4 hours ago, Miska said: I can run that on normal i7-7700K + RTX 2080. When parallelizable work is moved to GPU, the non-parallelizable or high precision (non-vectorizable) work is left to CPU. For tasks that cannot be broken down to parallel ones, bare "single thread" CPU performance rules. You still have more than one parallel task, but not so many (you can use number of channels x2 as ball park). Ok so i7-7700k vs i9-9900k? 4 cores vs 8 with base 4.2 -> 4.5 vs 3.6Ghz -> 5 ? Custom room treatments for headphone users. Link to comment
jabbr Posted March 25, 2019 Share Posted March 25, 2019 Let me expand on the question. Assuming we have a pattern with 4 cores where 2 cores take the brunt of the processing and two others do ~2/3 of that. Are the cores in the i9-9900k which has 8 cores going to be working at 3.6 GHz or 5 GHz, effectively? Custom room treatments for headphone users. Link to comment
jabbr Posted April 6, 2020 Share Posted April 6, 2020 24 minutes ago, bodiebill said: before main modem router => CAT7 => 1st MikroTik SFP switch => fiber => Server SFP NIC 1; 1st MikroTik SFP switch => fiber => 2nd MikroTik SFP switch => CAT6 => NAA endpoint after main modem router => CAT7 => 1st MikroTik SFP switch => fiber => Server SFP NIC 1 <BRIDGED WITH> SFP NIC2 => fiber => 2nd MikroTik SFP switch => CAT6 => NAA endpoint It seems like you are using your second Microtik as an SFP ... that's fine. The "before" config is correct. 24 minutes ago, bodiebill said: And soon I will receive a Cisco WS-C2960G-24TC-L switch (SFP + RJ45) and the JCAT net card FEMTO to play with. Where would you put the latter? If you are substituting different cards and switches, there is no "correct" config beyond what you started with, so you can place different devices in different places and the ones that produce music will be "correct" Custom room treatments for headphone users. Link to comment
jabbr Posted April 6, 2020 Share Posted April 6, 2020 48 minutes ago, bodiebill said: So that puts me before a difficult choice: doing what is 'correct', or what sounds 'better' to my ears... I will keep experimenting... There are many advocates on AS for a bridged setup (the 'after' setup), but apparently you have a different view? Is this based on theory or perceived SQ, or both? I have briefly tested various brands of fiberoptic NICs on various servers, all 10Gbe or greater (e.g. 25,40,100 Gbe) and cannot tell a bit of SQ difference. Nor can I tell an SQ difference among professional quality switches. When I was testing endpoints 5 years ago I thought I heard an SQ improvement going from copper RJ45 ethernet to fiberoptic but that might have been bias. In any case I'm only using fiber and wi-fi at this point. For HQPlayer, wired is far more reliable at DSD512, and wifi works well at DSD256 and if the wind is blowing the right way in my house DSD512 -- I can usually pull 280 Mbs over WiFi to my NUC/NAA Custom room treatments for headphone users. Link to comment
jabbr Posted April 7, 2020 Share Posted April 7, 2020 18 minutes ago, bodiebill said: I understand. However I have the impression that FMC's and fiber NIC's are noisy and that could be worse than the isolation advantage. My post was in reaction to @jabbr's post, but I appreciate your answers! Learning all the time... Hi, don't want to delve too far off topic here but I don't use FMCs. I use Mellanox which outsources to HPE and Dell. I have also used Intel and Solarflare NICs. They all work great. Newer Fiber NICs are very low noise and must meet extremely tight noise standards. Custom room treatments for headphone users. Link to comment
jabbr Posted April 7, 2020 Share Posted April 7, 2020 @bodiebill ... and others ... Let me give my overall impressions: 1) The best thing you can do with HQPlayer is NAA which gives Ethernet isolation and a low powered quiet machine attached to the DAC. 2) I use fiberoptic Ethernet for isolation 3) I haven't yet fully evaluated the myriad of filters and algorithms including kernels for room correction and digital crossover -- I expect that these will have a much greater difference in SQ than various switches and because my brain has a limited ability to compare things that mostly sound very similar I am selective in what I compare. I got my Mellanox (100gbe) switch because I got a fantastic deal on it, and I got my prior Brocade (10Gbe) switch for the same reason. 4) I find that Wifi works reliably for me up to DSD256 where wired is reliable to DSD512, so I'm currently looking at whether ASDM7EC/DSD256 compares with AMSDM7/DSD512 that said, I think the dropouts/latency with Wifi is likely much more of a factor regarding SQ than perhaps EMI (my house has a *very* active Wifi situation going on right now with multiple kids doing home schooling/videoconferencing on laptops, also TVs which wifi netflix/amazon etc) Thoughts on ASDM7EC/DSD256 compared with AMSDM7 etc./DSD512? Custom room treatments for headphone users. Link to comment
jabbr Posted April 16, 2020 Share Posted April 16, 2020 20 hours ago, The Computer Audiophile said: Is there any way to access HQP Desktop’s settings via web interface? I know HQP embedded enables this, but I’m using Windows desktop. use case - Listening to my headphones in bed via mRendu. Want to switch NAA outputs from my main system to the mRendu but only have access to my phone. I don’t want to run an rdp session on my phone either. Theres a lot to be said for HQP Embedded though even this use case isn’t perfectly covered. I use the Roon iPhone app to select music to play into HQPlayer but there’s a single zone for an instance of HQP ... maybe an iPhone/Android app that sends a message to HQPe to switch NAAs? Doesn’t yet exist AFAIK The Computer Audiophile 1 Custom room treatments for headphone users. Link to comment
jabbr Posted April 16, 2020 Share Posted April 16, 2020 8 hours ago, The Computer Audiophile said: This is a big question I’m trying to answer. I’ve tested the embedded version and so far think it’s a little buggy. The Windows version works pretty well. I’d love to try it on Ubuntu Studio but I also have to make sure the new hardware I select works with Ubuntu. I hate to say it, but Windows is the safest bet and most people are comfortable with it. I hear ya. People are comforted by a GUI. I started with the MacOS version and have used the Windows version of HQPlayer but just realized that my licenses for desktop are Version 3! I haven't tried to use HQPlayer desktop since I got HQPlayer embedded working. Why? 1) I take the view of music as a service. HQPe is a linux service, thus restarts when the power comes back on and the computer reboots. 2) I like the idea of HTTP config. That's how our music network *should* work 3) I love the idea of being able to control my music with an iPad or iPhone. I really don't need to know where it is coming from. 4) This fits best with the model of a high powered, perhaps "noisy" compute server and a very quiet renderer/NAA connected to the DAC 5) The DLNA model is great -- I don't care for the implementation -- but HQPe can be paired with Rygel as a DLNA endpoint. 6) I would prefer that the HQP/NAA protocol be "opened" by I understand @Miska's business requirements. It the best "remote ALSA" protocol out there bar none. So ... in an ideal world, there would be an HQP GUI that ran on the desktop as well as on an iPhone/Pad/Android that would control the HQP engine ... like Roon does ... but understand that precious resources are devoted elsewhere. The Computer Audiophile 1 Custom room treatments for headphone users. Link to comment
jabbr Posted April 16, 2020 Share Posted April 16, 2020 11 minutes ago, Miska said: Isn't that what for example HQPlayer Client + HQPDcontrol already allow? You will pry my iPhone from my cold dead body Now HQPlayer Client ... I see that's bundled with HQP4 Desktop which I haven't looked at (see above 😆) ... so that is a GUI that works with HQPe? Custom room treatments for headphone users. Link to comment
jabbr Posted April 16, 2020 Share Posted April 16, 2020 10 hours ago, Miska said: You listed Android too... Ha ha, just to be fair! In all seriousness, the web interface for configuration works great on the iPhone browser. So you can go to config page and then switch back and forth from NAAs/DACs easily from the phone **unlike from the Desktop version** Custom room treatments for headphone users. 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