Jump to content

Miska

  • Content Count

    12495
  • Joined

  • Last visited

About Miska

  • Rank
    Masters Level Member

Recent Profile Visitors

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

  1. Miska

    HQ Player

    Not very straightforward, but I think I have better solution for this case coming...
  2. 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.
  3. 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.
  4. Yes, by increasing number of output channels... At least number of cores is correctly detected and thread counts are correct. What filter are you using?
  5. No no, set filter of your choice like poly-sinc-ext2 or something, TPDF dither and PCM rate limit to 768k. You can also set "Auto rate family" if you like, but it is not necessary. Then select PCM in main window. This way all PCM and all DSD gets converted to 768k (or 705.6k).
  6. It would be interesting to know how well MQA supports multichannel configurations. 2.1, 3.0, 3.1, quad, 5.0, 5.1... Such usually need channel mapping at minimum.
  7. In Control Panel -> Device Manager, under sound devices, you can right-click on your DAC and then check the Driver tab to see who's driver is loaded for the DAC. If it says Microsoft, then it is likely the UAC2 driver they introduced in Win10 feature update 1803 or something like that. Support for this new situation may need some actions from the driver developer. ASIO driver has two parts, one is the low level device driver that talks to the hardware, and the other is user space COM component that gets loaded into the application. These two talk to each other in a driver-specific way. If the low level device driver doesn't match the COM component, for example because Microsoft's generic driver gets loaded, the COM component cannot function correctly.
  8. Either one is correct, just different core allocation. How many cores does it say it'll be using in the log file? Maybe there is some problem correctly recognizing the CPU topology.
  9. Seems like it doesn't have enough power for that case... What kind of CPU does it have? I assume you have "Multicore DSP" set to "auto" (grayed)? You could also try it in "enabled" (checked). These two behave slightly different way and on edge cases it may make a small but critical difference. However it is impossible to determine upfront which one will be better in a particular case.
  10. You could try with my custom kernel from here to see if that enables DSD without DoP and thus also the higher rates. Note that it doesn't boot by default, so in grub boot loader menu, select advanced and from the kernel list select the correct kernel after installing it. If it works as expected, you can make it the default option by modifying /etc/default/grub file and then running update-grub I have following line there: GRUB_DEFAULT="2>4" This means option 2 from first menu level and option 4 from the second.
  11. Miska

    HQ Player

    No, I have not seen anybody selling such in EU. There are quite a bunch of Sabre DACs around. Matrix X-Sabre Pro is available, but a bit too expensive for what I'm ready to pay for such.
  12. Miska

    iFi foe fum

    So practically it is modified variant of the default MQA upsampling filter that for example Mytek runs for all PCM when MQA decoding is enabled... Likely on ESS-based DACs the MQA upsampling filter is just uploaded to the ESS chip, but in this case that is not possible with the TI DAC chip, so it needs to be run on XMOS. So this is functionally closer to how Meridian does in the Explorer2 DAC.
  13. Hard to say, one possibility that comes to mind is that Windows is hooking up to the DAC with it's own UAC2 driver instead of the driver you've installed. You could try to fix it with this procedure: - Disconnect the DAC - Uninstall the DAC's driver - Reboot - Install the DAC's driver - Connect the DAC If possible, it is good to first install the driver before connecting the DAC to avoid Windows from attaching it's own driver to the DAC. If the driver is older than UAC2 support on Windows, it may not have ways to deal with the situation otherwise. ASIO driver cannot operate correctly, if the WIndows' UAC2 driver is hooked to the DAC.
  14. OK, then the UP is having some USB connectivity issues for some reason. Both HQPlayer and NAA use the ASIO driver same way, so if OS and the driver are same and it still behaves differently, then there's some issue somewhere. You can also install HQPlayer Desktop on the UP to see if it behaves the same straight to the DAC. But there shouldn't be any difference.
×
×
  • Create New...