DSD encoding mostly works now!

Answered

Martin Amdur

• March 01, 2023 21:45
• Edited

After the fix DSD encoding is working, but, as usual, documentation around this sucks. DSD encoding does not work from a network attached Vault (2 in my case). Please add this info to the sparse documentation offered so folks can spend way fewer hours trying to get this all working.   

 

edit: It turns out DSD encoding did happen despite the error saying it failed. When I set the drive to my vault I get 2 messages: one says DSD encoding will happen in the background. The other gives a failure message complaining about the drive selected. Despite this error message, DSD encoding did happen!

0

• 

  Bjørn Ulvik

  Hi-Res

  • March 01, 2023 21:50

  Please add this info to the sparse documentation offered so folks can spend way fewer hours trying to get this all working.

  Should be well documented when you enable the DSD playback feature.
  
  

  0
• 

  Martin Amdur

  • March 01, 2023 22:14

  Except it isn't. DSD encoding works (albeit with an error message saying it didn't as well as a simultaneous message saying it did), despite your screen shot. I'll add that despite  what the message in the screen shot says, I was told multiple time that DSD encoding should work on Vaults (& 2 & 2i). Like I said: "The documentation sucks." There is what I read, and what I am told, and they do not necessarily match up. 

  0
• 

  Bjørn Ulvik

  Hi-Res

  • March 01, 2023 22:32

  You get the error message when you use a mapped drive as source/destination (even though the conversation happens).
  No error message if you use local or USB disc.

  0

Please sign in to leave a comment.