Foobar 2.25 news API and breaking of sacd playback
Status: Inactive
Brought to you by:
manisiutkin
Menu
▾
▴
#218 Foobar 2.25 news API and breaking of sacd playback
hi, newest foobar preview 2.25.2 from 24.09.2025 makes it impossible to output sacd as dsd with sacdinput1.6.5. no matter what settings, the only way is to play as pcm. dsd gives no signal. it worked up to foobar prewiev from 23.09.2025. it does work with sacdinput2.x but those versions often crash foobar. here is what is written on hydrogenaudio about that problem:
foobar2000 v2.25 has new output API and the changes continue as needed, like seen for example here. There is no conspiracy against SACD component. It breaking is because of its own doing. Instead of asking for API enhancements or writing own output for DSD, the component chooses to hack around foobar's internals.
Discussion
Anonymous
Thank you for the info. Foobar source code needs to be changed to handle DoP properly. It includes separating DSD/PCM DSP chains, bypassing ReplayGain and FadeIn/FadeOut, locking Volume control at 0dB. Also Visualizer interfaces have to convert DoP output to PCM.
It's all in foo_input_sacd v2.x.x code. In this case fiddling around foobar's internals won't be needed.
Thank you. Unfortunatelly sacdinput v2.x sometimes crashes foobar.
Hi,
I think Peter should read the thread ... as a developer he could understand this point of view ?
Regards,
n.
That depends on how many users are interested in the better implementation of DSD playback, I think.
A lot of users buy DSD encoded music directly from the stores.
:)
Hi,
sacdinput2.0.7 or 2.0.10 (did not check 2.0.8 and 2.0.9) - when shift+file and open sacd is used the sacd.iso is added to the playlist but it can't be played and freezes foobar forever (without crash). Must be manually closed (ctrl,alt,del). Foobar restarts with error message (with option to safe-open). Win11, FB2.25.2 preview from 30.09.2025.