Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Upgraded to Foobar v2.24.3 and SACD stopped working (Read 1193 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Upgraded to Foobar v2.24.3 and SACD stopped working

I've been using Foobar v1.6.18 for many years now. I use SACD component v1.2.0. I always use Wasapi for output as it keeps things simple. I had no issues with playing any type of SACD format whether it's ISO, DSF or DFF and it worked with no issues. I can play DSD natively, but I've always used DSD+PCM output mode which is supposed to be DoP.

I decided to upgrade to Foobar v2.24.3 and use the latest SACD component which is currently v1.6.1 and none of my SACD files work now. I can't play natively or using DSD+PCM. I tried using ASIO and that didn't work either. It gives me "Unrecoverable playback error: Unsupported channel layout" error and I have no idea what that means. I'm not sure what the issue is. The older foobar and SACD component worked perfectly, but I can't seem to get the new versions to work. Any ideas? Thanks.

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #1 –
Did you update your component?

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #2 –
Quote from: kyrio on
Did you update your component?


Which component specifically? With the new version of foobar, I just redownloaded all of the most updated components. This includes the Wasapi and SACD components.

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #4 –
Quote from: almo89 on
This includes the Wasapi ...
WASAPI output is built-in and the old component(s) not needed and probably outdated compared to defaults. Try using a default output with "[exclusive]" at the end.

Also might be helpful to list what other components you are using, any DSPs etc?

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #5 –
Quote from: almo89 on
Quote from: kyrio on
Did you update your component?


Which component specifically? With the new version of foobar, I just redownloaded all of the most updated components. This includes the Wasapi and SACD components.
If you are using ver. 1.6.1 of SACD (1.6.2 was just posted), try adding foo_dsd_processor:

03/05/25:
   Version 1.6.1 - Experimental: DoP output handling changed. Needs the new foo_dsd_processor plugin.
https://sourceforge.net/projects/sacddecoder/files/foo_dsd_processor/foo_dsd_processor-1.3.4.zip/download

Also:

02/17/25:
   Version 1.6.0 - Experimental: common codebase with foo_input_udsd plugin.

I've heard foo_input_udsd is a sometimes works/sometimes not replacement for foo_input_sacd, you could try that solo:
https://sourceforge.net/projects/sacddecoder/files/macOS%20%2BWindows/foo_input_udsd/foo_input_udsd-0.1.1.zip/download

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #6 –
Quote from: anamorphic on
Quote from: almo89 on
This includes the Wasapi ...
WASAPI output is built-in and the old component(s) not needed and probably outdated compared to defaults. Try using a default output with "[exclusive]" at the end.

Also might be helpful to list what other components you are using, any DSPs etc?


I tried using the default (exclusive) output. It now can play the music and my DAC will show it's playing DSD natively, but it pauses every few seconds. Really odd. I'm not running any DSPs at the moment. I installed a brand new foobar using portable installation and the only compents I downloaded were the SACD and Wasapi.

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #7 –
Quote from: sveakul on
Quote from: almo89 on
Quote from: kyrio on
Did you update your component?


Which component specifically? With the new version of foobar, I just redownloaded all of the most updated components. This includes the Wasapi and SACD components.
If you are using ver. 1.6.1 of SACD (1.6.2 was just posted), try adding foo_dsd_processor:

03/05/25:
   Version 1.6.1 - Experimental: DoP output handling changed. Needs the new foo_dsd_processor plugin.
https://sourceforge.net/projects/sacddecoder/files/foo_dsd_processor/foo_dsd_processor-1.3.4.zip/download

Also:

02/17/25:
   Version 1.6.0 - Experimental: common codebase with foo_input_udsd plugin.

I've heard foo_input_udsd is a sometimes works/sometimes not replacement for foo_input_sacd, you could try that solo:
https://sourceforge.net/projects/sacddecoder/files/macOS%20%2BWindows/foo_input_udsd/foo_input_udsd-0.1.1.zip/download



I tried adding the new DSD processor and it still doesn't work properly. I tried the foo_input_udsd as well and I have the same problem. I can only get music to play when using default (exclusive) output, but it pauses every few seconds.

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #8 –
View -> Console

Does it show any error?
 

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #10 –
Quote from: almo89 on
the only compents I downloaded were the SACD and Wasapi.
You shouldn't have "downloaded" wasapi, that is now built-in to Foobar, although there are still old plugins for it when it was not natively supported.

1.  Uninstall any currently present DSD-related plugin, and any "Wasapi" plugins.

2.  Install the new 1.6.2 version of SACD like marktherob2005 suggested.

3.  Choose an output device with "[exclusive]" at the end, configure SACD 1.6.2, and see if the pausing is fixed.

Re: Upgraded to Foobar v2.24.3 and SACD stopped working

Reply #11 –
So I tried a different a DAC (SMSL Sanskrit) and now I can play DSD without the skips. My Shanling UA5 still skips using the same exact settings. Something about the new SACD component that isn't compatible with the Shanling. I guess I'll have to live with this for a while. I'll just have to use the old Foobar if I want to use my Shanling. Good thing all my Foobar installations are portable so I can pick and choose which one to use. Thanks for all the help guys.