Jump to content

Miska

Members
  • Content Count

    13725
  • Joined

  • Last visited

About Miska

Recent Profile Visitors

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

  1. Now the interesting question is, is it better with minimal jitter, or with maximal jitter?
  2. Miska

    Pink Faun 2.16

    You are upsampling in your DAC, but just stuck to the DSP it offers... I try to choose DACs that can work as a plain D/A converter, without any DSP. It doesn't mean that upsampling for example to RedBook to 192k PCM wouldn't make a huge difference. The first step from RedBook upwards matters a lot and there are many different filter options for that operation. Of course if you don't use HQPlayer's DSP capabilities, HQPlayer is pretty much pointless for you. I personally don't use Roon much these days. I play Tidal through UPnP to HQPlayer Embedded. And local content through HQPlayer directly without Roon. For me, Roon doesn't provide any extra value.
  3. Miska

    Pink Faun 2.16

    It does help precisely because of that. The interference is spread to wider spectrum at lower level. When properly done it looks more like random noise rather than discrete tones. Which is good and fully intentional. IOW, it works as intended. No need to disable it, I would rather want to make sure it is enabled. P.S. None of these clocks are used to clock audio, so from audio perspective it has only positive sides. HQPlayer is not supposed to add anything, just improve DAC's analog reconstruction accuracy by DSP means. I'd be curious to see objective comparison results (measurements). Which DAC is this?
  4. This is not related to HQPlayer!? Looks like web browser stuff...
  5. Miska

    HQ Player

    Unmanaged: 16-port version on Zyxel GS1100, if you want optical support, get the 24-port version, NOT the 10-port version. With this, enable 802.3az (EEE) support using the button on front panel. Managed: HPE 1820 series 24+2-port (24G) model. Supports also optical networking. I'm also about to test Cisco SG350-10 switch. Should be good, but been too busy to do it yet. With any managed switches remember to check that 802.3x Flow Control is enabled in settings! Also check that 802.3az support with cable length detection/link power adjustment is enabled, this way it doesn't unnecessarily blast at full power over short cables, but instead uses only the amount of signal power needed (lower noise). All these switches are very reasonably priced but high quality.
  6. Miska

    HQ Player

    Have you tried running OS from Intel Optane M.2? That is as optimal as it can get. All my Debian, Fedora and Ubuntu Server installations are on either SATA SSD or M.2 SSD. Especially with M.2 I like that HQPlayer Embedded is up and running in ~5 seconds after pressing power button. And shuts down in one second after pressing power button.
  7. You can just login and delete those files if necessary, just like any other file. Web interface is only intended to have things that are useful for end-user buying a "streamer device". Manufacturers usually don't want end-users to touch other parts because it makes warranty and technical support so much harder.
  8. Sounds like some network configuration issue. Are you using DHCP or static IP? Are you using graphical desktop on bare text console minimal/server? This makes a big difference because HQPlayer Embedded is started as a system service at boot time, while with graphical desktops network is configured only once you login through graphical desktop (because the configuration is stored per user). This means that HQPlayer Embedded is started way before the network is configured if you have a graphical desktop. HQPlayer Embedded is designed for minimal systems where there is absolutely nothing else than kernel and minimal init system (systemd) running, no graphical desktops or other such stuff. Graphical desktops usually use NetworkManager to deal with network configuration after login. While minimal server installations (headless) usually use something else to deal with network configuration during boot time. If you are on DHCP, please try again after "sudo systemctl restart hqplayerd" once the machine is completely booted up.
  9. I would strongly advice against using analog path because that will ruin sound quality (DAC in CCA is not that great). You would need some suitable audio device with optical input, to deal with mini-Toslink from Chromecast Audio to a computer. Since Spotify is fixed 44.1k, it is quite straightforward. Tidal may be other rates as well, although vast majority is 44.1k (everything else except Masters). Point is that without a certain input device, you need to manually switch input sample rate. For Linux, I have implemented quite a bunch of extra driver support to enable automatic switching of input sample rates with RME ADI-2 (Pro). But it is quite expensive input device if you don't need analog side for vinyl or similar. I haven't got them to support the adaptive ASIO input rate yet through their driver on Windows yet, but otherwise it should work. Among the most inexpensive is miniDSP USBStreamer which works fine on Linux, but requires some amount of extra work to flash it with correct firmware variant (miniDSP provides multiple). I have to admit I have never tried it on Windows or macOS, so if someone else has, please chime in. I do majority of my testing with RME ADI-2 Pro, and some with RME HDSPe AIO too. I also have Motu 8D but it is only feasible if you are OK with manual rate switching or use of only 44.1k input (Spotify for example).
  10. Miska

    HQ Player

    Just remember that latency is function of frequency too, so you need to calculate how many nanoseconds 6 clock cycles is at it's memory frequency. And also weight that with transfer rate, so pick a one that has both as high as possible transfer rate and as low as possible latency. There's a good table for reference here: https://en.wikipedia.org/wiki/CAS_latency So for example DDR4-4600 at CL18 (for example G.Skill Trident Z) gives you pretty good figures at the moment. With i7-8086K I'm at DDR4-2666 CL12 at the moment. So maximum performance within official CPU specs without overclocking.
  11. Miska

    HQ Player

    Point in UTP is that it lets Ethernet's galvanic isolation through transformers work. While STP cable connects grounds and thus negates the galvanic isolation which is one of the main reasons to use Ethernet. Even better, you can use optical Ethernet for complete isolation. Depends where it is and what follows. In NAA, if you have a USB DAC, a lot depends on it's USB implementation. Or if you have a DAC with built-in NAA like the new T+A where you can send up to DSD1024 over Ethernet. On my HQPlayer servers I just get fast RAM with minimal CL to maximize processing capacity. So it is usually something like HyperX Predator. For NAA use I have things like the Logic Supply CL100, UP Gateway, MinnowBoard Turbot (dual core), and the various ARM-based devices. On x86 RAM is typically separate from the processor, except devices like Intel Joule which was stacked architecture like many ARM SoC solutions are. Stacked configuration is systematically always used on mobile phones and tablets. In stacked you have first SoC on the PCB and then RAM sits on top. So it is a sandwich where CPU is in the middle.
  12. I don't think you can currently buy any hardware that would be able to run EC modulators at DSD512 speed. Since it is double the amount of computational effort compared to DSD256, it may take couple of years before that becomes possibility. It specifically requires individual cores to become 2x faster than current ones. Adding more cores won't help. We have here at least one shop selling delidded and tested i9-9900K's that have been verified at 5.2 GHz clocks. Maybe I'll get one of those and see if it could do close to DSD512 with DSD5EC or ASDM5EC. Another approach would be to make a custom DAC that would have sample clocks somewhere between current typical DSD256 and DSD512 clocks. For example 40 MHz.
  13. I have also some other ADCs like Prism Lyra, which is also very good performer, but limited to 192/24 PCM. Should be enough for vinyl though, if one wants PCM. But I would personally go with DSD256 recording for vinyl. At some point I'll hopefully also have the new Merging Anubis, which is potentially good for the purpose too.
  14. Miska

    HQ Player

    Are you making sure that the cable is UTP type? STP/FTP cable types are absolutely no-no for NAA use. So at least check that the RJ45 connector on the cable is full plastic-body, not the metal body type. It absolutely shouldn't make any sound quality difference. If there is difference, it needs some research to find out why to eliminate it. If it makes difference, it is negating point of NAA. Can you measure the difference from DAC output? How does it look like? Everything always runs from the RAM anyway, but loading entire filesystem to RAM just stores redundant information in RAM and reduces amount of free memory to be used as disk cache for content. So I'm not doing it. If you use NAA, I cannot think of mechanism how HQPlayer computer would make a difference. Actual playback is performed by NAA and HQPlayer is just doing processing as a network service. This HQPlayer processing could be even implemented as a cloud service on the internet.
  15. AFAIK, in most cases PHY advertises pause frame capabilities and deals with negotiation, but MAC is the the one that actually generates the pause frames - since it's the one owning the packet buffers. There is always orchestration between PHY and MAC (through MII) to deal with configuring such interactions and this is where the driver steps in (and Linux kernel internally abstracts this). Since driver code runs on the APU (CPU), it cannot properly deal with pause frames because for example in iMX6 case it is behind the slower link between MAC and CPU. So CPU cannot react properly to the upstream traffic it sees "after the fact", once it has traveled across the slow link. Overall, it cannot know when MAC is going to overflow the buffer. While MAC is always has up-to-date information being at the Ethernet side of the slower local bus link and the one that fills the packet FIFO. There are now also newer standards (802.1Qbb) that support flow-control based on packet priority, so lower priority traffic can be put on hold if necessary and keep higher priority traffic flowing. This is important for cases where you have lot of intermixed traffic like between switches, and less important for cases like NAA where you usually anyway have just a one notable stream. These newer things are mostly supported by more fancy newer hardware. For example NAA connection attempts to utilize 802.1p type QoS/CoS that can benefit from such flow control categorization. Even the cheapest integrated NICs for PCIexpress tend to include both QoS/CoS and flow control using the older more established standards, like the commonly used cheap Realtek 8111: https://www.realtek.com/en/products/communications-network-ics/item/rtl8111g You can see both 802.1p and 802.3x listed there. Plus hardware offload of various network checksumming operations. And also 802.3az (EEE) to keep power consumption low. So all the specs I list for NAA.
×
×
  • Create New...