Jump to content

craighartley

  • Content Count

    922
  • Joined

  • Last visited

About craighartley

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. This may be a dumb question, but what is the difference between the downloads hqplayer-embedded-4.19.1-x64.7z and hqplayer-embedded-4.19.1-x64.7z.asc ? Thanks
  2. I asked the question because the new EC modulator is included in HQ Desktop with the advice that it is for 512+ rates.
  3. What processor is needed to use the new pseudo-multibit AMSDM7EC modulator at 512?
  4. Thanks, I’d forgotten that. Actually one reason for exploring HQPlayer Pro was to try the effect of the two filters I can’t do in real time with HQP OS - sinc-L and closed-form-16M. I can try them with 44.1x files though.
  5. Brilliant! Thanks! - that’s exactly what is happening. The errors were all with 48k based 512 DSD. I’ve just tried two 44.1k based files and they work perfectly with both Roon and Audirvana. I’ll raise it on the Roon forum. Easy to work around, except of course it rules out using non-apodising filters with 48k based source files. The NativeDSD files must be limited to 44.1k-512 (even though they employ an apodising filter). Sensible decision.
  6. Thanks for the response. Yes I don’t know what the difference could be between the NativeDSD 512 files and the ones I’m producing with HQPlayer Pro on my MacBook Pro, unless it is an unintended byproduct of the trial version that I’m using. I was only using Audirvana as a front end via UPNP to my HQPlayer OS server when I wanted to play files on my MacBook that I hadn’t transferred to the NAS that Roon and HQPlayer use as a library. I don’t use Windows. My main reason for trialling HQPlayer Pro was to see if I could produce files to use with Roon without the HQPlayer server
  7. Has anyone worked out why 512DSD files produced with HQPlayer Pro won't import into Roon or why they crash Audirvana (which shows them as 557DSD)? I've tried editing the metadata to make sure that is behaving properly, but it doesn't seem to stem from that. They play with HQPlayer, but that's not why I wanted to make the files. The 512DSD files from NativeDSD, which are made using HQPlayer Pro, do import into Roon. Strange.
  8. 6.07-392 Thanks. I’ll use the separate thread from now on.
  9. Should the album cover be showing on the now playing screen? Mine is not.
  10. Miska, can you advise please?
  11. Understood. So there’s no point in acquiring such files to feed straight to the DAC. But does HQP benefit from receiving 32-bit floating point DXD files to process, rather than 24 bit? (Specifically for DSD output to T+A DAC 8 DSD)
  12. I understand and share your view, but the point of that link was just to show you the claim in relation to DACs handling floating point files: ‘If a DAC with a DSP with an internal (32bit) floating-point architecture (which, again, applies to most DACs) receives a 32bit floating-point signal, it doesn’t have to convert anything at all, right until the moment it’s converted into the analog domain.’
  13. And also https://trptk.com/blog/a-new-chapter-32bit-floating-point-dxd/
  14. so this is wrong/misleading? https://trptk.com/blog/32bit-floating-point-dxd-compatible-dacs/
×
×
  • Create New...