DSD512 ...upsampled free demo from www.wechdomi.org [Resolved with build 218]


(Mr Fix It ) #1

A file that was called

Wechseldominante - Babel DSD512\Wechseldominante - Babel (DSD512).dff

caused an issue in the V1.3 Build 216 scanning and resulted in a crash loop so if you have this on your system suggest you remove it and perhaps others from the same source

http://www.wechdomi.org/english/index.html

Use at your own risk until support gets a wiff of the issues with it


New install - Cannot connect to RoonServer
Build 216: Update stuck in a connect and reconnect loop [resolved with bad DSD analysis identified]
(Jani Vallius) #2

I can confirm this. I have two DSD512 tracks, one of which is the same track that caused issues for wizardofoz, and the result is the same crash loop with Build 216. I needed to delete both files from followed folders. Previous builds were not affected but then they didn’t identify the files at all.


(Mr Fix It ) #3

@vova Weil thanks go to Vova for helping pull that one out of the logs…hope its helped a few others too.


(Mr Fix It ) #4

Not sure if the 218 build has fixed this…but will try to restore the file back from a backup and see…or download it again.


(Jani Vallius) #5

It fixed it for me, no more crash loop.

Roon now identifies one of the two DSD512 tracks, the other is skipped due to “tag extraction failed”. The one that Roon sees only plays for a few seconds, but that is not so unexpected because my old Mac Mini lacks performance. I also have a DSD256 version of the same track and it plays just fine.


(Mr Fix It ) #6

Yep 0.6X is not going to cut it…I noticed that the downsampling is every bit as demanding as the upsampling - which I guess when you think about it is what to expect.


#7

Thanks @wizardofoz, managed to download the ‘Wechseldominante - Babel DSD512\Wechseldominante - Babel (DSD512).dff’ and playback on my Holo Spring DAC. Direct DSD512 playback is far less computer intensive if it doesn’t do any form of conversion. I managed to playback DSD512 without any issue.


(Mr Fix It ) #8

@jvall @MusicEar thanks for the positive feed back that this is sorted in build 218, need to go recover that one for testing again.