On Mon, Aug 12, 2013 at 7:52 AM, Daniel Mack zonque@gmail.com wrote:
On 12.08.2013 13:27, Jesus R wrote:
On Mon, Aug 12, 2013 at 4:52 AM, Daniel Mack <zonque@gmail.com mailto:zonque@gmail.com> wrote:
Right now MPD supports DSD/DoP with one selectable on/off option. On equals DoP output and off equals conversion to PCM. I'm not aware of any case where it does not work. I would seem to me that there is one predominant format?
Let me clarify that again: I read the above as the two options are
a) DSD material is augmented by DOP markers and send as such over a regular PCM interface, or
b) convert DSD to PCM in software and then send PCM samples over a regular PCM interface.
What applications need to use for my new approach is another is:
c) take DSD samples, bit reverse them if necessary, and then send them over the generic DSD data pipe to the Linux kernel. Device-specific details are taken care of by the kernel layer.
Yes, I understood this. I'm not sure what MPD will do going forward though. The end goal should be DoP as needed and native DSD if supported.
I'm not aware of any software that uses that new DSD format type directly except for my example program.
Jussi might be using it:) I'm going to propose it to a project I'm involved in..
Daniel