craighartley

That’s great (I had asked for it too). Unfortunately it makes the Kaluga LEDs look even brighter by comparison.

Maybe that is why the update is taking so long: they won’t do it until they find a way of not ruining the magic. But NB Miska’s response that it was more likely the modulator that is tripped up by the noise rather than anything to do with filtration. Bear in mind that I only heard the response of the Mola Mola engineer through the UK importer and the message may have become “simplified”.

Except with DXD files. I know you’ve touched on this in a previous post, but I’ve bought 146 DXD downloads, at considerable expense, and the DAC is tripped up by at least 10% of them, so it seems to me that a rider always has to be added when discussing its performance. It impresses immensely on other formats.

Hi Ted, I wonder if you will have time to see if you have any problems with crackles and stutters playing certain (but not all) DXD files with the Mola Mola DAC? I understand there may be noise inherent in some DXD files that is filtered out by DACs with more aggressive filtering. I was told last year (via the UK distributor) that the firmware would eventually be upgraded to address this, but only when it could be done without otherwise affecting sound quality. it’s been my habit to acquire downloads in DXD from NativeDSD and elsewhere when a DXD edit master is available. Craig DXD Downloads with noise problems observed on Mola Mola DAC.docx

Of course that’s only true if you are controlling volume with the Tambaqui.

And mine told me that the combined unit has the edge. You are also comparing a digital vs analogue volume control, so there are a lot of factors in play.

Or DSD256 with EC modulator which many prefer on DAC8 DSD to DSD 512 with non-EC modulators.

Thanks.

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

I asked the question because the new EC modulator is included in HQ Desktop with the advice that it is for 512+ rates.

What processor is needed to use the new pseudo-multibit AMSDM7EC modulator at 512?

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.

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.

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 in the chain.

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.