Skip to main content
Topic: can't choose "DSDwasapi(event)..." (split) (Read 270 times) previous topic - next topic - Topic derived from foobar2000 v1.3.18
0 Members and 1 Guest are viewing this topic.

can't choose "DSDwasapi(event)..." (split)

I like V1.4.beta17,Only problem is output can't choose "DSDwasapi(event)..."


can't choose "DSDwasapi(event)..." (split)

Reply #1
Hi,Peter,
start after Version of  Win10 1703,The output can't choose "DSDwasapi(event)...",if SACD output mode is DSD.But if SACD output mode is PCM and PCM samplerate is under 88200Hz,When playback PCM and DSD file It is working Normal.Can you fix this bug?Please see the  Picture below:Thanks a lot.



Re: can't choose "DSDwasapi(event)..." (split)

Reply #2
These are settings of foo_input_sacd component, so I think you should ask the author of this component: https://sourceforge.net/p/sacddecoder/bugs/

Re: can't choose "DSDwasapi(event)..." (split)

Reply #3
No,I think this is foo_out_wasapi bugs.Thanks.


Re: foobar2000 v1.3.18

Reply #5
Hi,Peter,
start after Version of  Win10 1703,The output can't choose "DSDwasapi(event)...",if SACD output mode is DSD.But if SACD output mode is PCM and PCM samplerate is under 88200Hz,When playback PCM and DSD file It is working Normal.I think this is foo_out_wasapi bugs,Can you fix this bug?Thanks a lot.

Re: can't choose "DSDwasapi(event)..." (split)

Reply #6
@Peter Calling the author to this topic, then, maybe he can tell you whether his component is responsible for something that by all means appears to be implemented by the SACD decoder component.

Re: Re: foobar2000 v1.3.18

Reply #7
FYI: It is:

"DSD: <another protocol>: <that protocol's device name>"

So,

"DSD: WASAPI (event): <device name>"

Which isn't working. My guess is, some GUID changed, and this idiot is hard coding those instead of using the SDK headers.

Thus, my opinion: foo_input_sacd bug.

Re: can't choose "DSDwasapi(event)..." (split)

Reply #8
FYI: It is:

"DSD: <another protocol>: <that protocol's device name>"

So,

"DSD: WASAPI (event): <device name>"

Which isn't working. My guess is, some GUID changed, and this idiot is hard coding those instead of using the SDK headers.

Thus, my opinion: foo_input_sacd bug.
So,I send this questions to there:https://sourceforge.net/p/sacddecoder/bugs/101/  Thanks a lot.

 
SimplePortal 1.0.0 RC1 © 2008-2018