Thank you Maxim ... this is the case in my setup, tested with last 2.0.20, no other DSP selected, glitches are gone :) Regards, .
For continuous conversion of single track sources set "File->Preferences->Advanced->Tools->Converrter->Thread count" to 1 and select tracks with the identical channel counts and samplerates.
Hi Maxim Where do you set number of converter threads ? thank you Regards .
Thanks again for your answer & apologies for the delay of mine (very busy week ...) So I tried your way, it works too. I did not have time to compare wav files obtain with each method but I'll do it this week-end. Thanks again.
Is this fixed in sacd decoder 2.01.9 ? or is this boud to the converter ? By the past I tried to convert DSD isos to .flac or .wav but there were some small inconsistancies at beginning/end of each track, like clicks of small level. It can be seen in low levels not matching whilst trying to mount individual converted tracks in a CD project, for example. I attached such behaviour, done in version 2.0.18 (no additionnal DSP) Best regards, nar
Partially fixed in 2.0.20 when number of converter threads is set to 1. See readme.txt.
Thank you, Maxim. It appears everything is great with ISOs now! The only thing to note with dsf... there used to be no clicks at the start of converted tracks, which I can definitely confirm was the case with version 1.5.11. I am unable to go through the versions to find when the clicks started, but it is present with the latest interim version. I will try to go through the versions to pinpoint when it changed. Thanks again! Parker
Thank you for discovering this. The part of code that prevents clicking was lost from plugin codebase. It works only for SACD-R ISO images. It it still clicks please share the source.
correction with the PS: the files null out when i move the inverted 1.5.6 file back by one sample, excluding the clicks.
correction with the PS: the files null out when i move the inverted 1.5.6 file back by one sample.
Click at the start of converted flac files since Ver. 1.5.6
The other way is to setup any resampler in Preferences->Playback->DSP Manager panel. If you use Multistage DSD2PCM converter try to use DSD2PCM output samplerate as 1/8 of the DSD source sanplerate. For Direct DSD2PCM it's 1/64 or 1/32.
Thanks for your answer, is there any way to go around it and use another resampler ? If not, I'll configure sacd_input on 88.2kHz and create a converter profile with a resampler as dsp and set the sampling rate I want. Thanks again !
The latest versions of foo_input_sacd plugin use default foobar resampler for 44100x -> 48000x conversion. Not sure, but that might be the reason.
SACD input issue when used to convert audio files
Thanks. It was strange that I couldn't find it with search under Manisiutkin... Anyway, compiled without warnings or errors on RPi5. Best regards, Milan
I moved it to https://github.com/manisiutkin/MPD
Hello Maxim, Previously the MPD SACD/DVD-A ISO sources could be obtained both as ZIP archives and via git clone. Currently I can only find ZIP snapshots on SourceForge. Is this intentional (ZIP-only releases), or is the git repository temporarily unavailable? Thanks.
Perfect. Work perfectly... Ty so much :)
From version 2.0 coding a dsd file to flac are always 0dB (less volume than the original because Sigma Delta decimation have a lot of attenuation, of -6d). Band deafult sample rate equal to display in sacd windows (grey if dsd mode is selected). If DOP selected, volume correction is passed but sample rate is always 176400 (i don't understand where is set this rate???). I revert to 1.6.5 where with dsd+pcm option all work perfect for me, because use a lot dsd to flac conversion for a separate portable...
In 2.0.18 this volume adjust is back. Will not work while replaygain info is set.
Sorry, I sent you wrong report. Yesteradys crash was caused by some other component. So far no crashes with 2.0.17 (but only few sacds listened to).
Thank you. This crash dump file is believed to be for the foo_input_sacd (2026-01-28 13:43:20 UTC) Super Audio CD Decoder 2.0.16, but the fix was made in 2.0.17. Does the later one crashes as well?
Another crash, this time with pcm tracks, none of dsd track were even in the playlist.
Try looking in DACs drivers. My drivers show if the DAC receives DoP or Native. The DACs display only shows DSD.
Thank you.
DAC usually doesn't display in which form it receives DSD stream (it can be Native DSD or it can be DoP). It just says 'DSD' or 'PCM'. After you select 'DSD' in plugin settings foo_input_sacd will output DSD stream in DoP format. Then foo_out_asio+dsd will convert DoP to Native DSD if downstream ASIO driver (your DAC driver) supports Native DSD. This might look a bit complicated, but there're no other better ways to output DSD in foobar. No, to get Native DSD use either foo_out_asio+dsd or foo_out_asio...
DAC usually doesn't display in which form it receives DSD stream (it can be Native DSD or it can be DoP). It just says 'DSD' or 'PCM'. After you select 'DSD' in plugin settings foo_input_sacd will output DSD stream in DoP format. Then foo_out_asio+dsd will convert DoP to Native DSD if downstream ASIO driver (your DAC driver) supports Native DSD. This might look a bit complicated, but there're no other better ways to output DSD in foobar.
Thank you for your reply. I'm really confused, now. All this time using foo_out_asio, my DAC indicated that it was receiving native DSD but it wasn't? Anyway, now that I'm using foo_out_asio+dsd - can you please specify what is needed to output native DSD to the DAC? Should this option in the attached image be enough or are there more settings I need to change? Do I need to install DSD Transcoder as well?
I'm really confused, now. All this time using foo_out_asio, my DAC indicated that it was receiving native DSD but it wasn't? Anyway, now that I'm using foo_out_asio+dsd - can you please specify what is needed to output native DSD to the DAC? Should this option in the attached image be enough or are there more settings I need to change? Do I need to install DSD Transcoder as well?
foo_out_asio plugin doesn't output Native DSD, it does only DoP. Native DSD is usually needed to output the highest possible for the device DSD sample rate. As the other possibility DSD Transcoder can be used with the foo_out_asio plugin to get Native DSD out of DoP.
After a little more experimenting, I've noticed a few benefits of foo_out_asio+dsd in comparison to foo_out_asio: 1- Seeking through a track is smoother and with less clipping/distortion . 2- It's possible to play video files in Windows (like, for instance, a youtube video) while foobar is playing a file with a different sample rate. Ofcourse the audio will not play, but with the default foo_out_asio not even the video would. 3- Less prone to playback errors (such as "timeouts") when in exclusive...
After a little more experimenting, I've noticed two other benefits of foo_out_asio+dsd in comparison to foo_out_asio: 1- seeking through a track is smoother and with less clipping/distortion 2- It's possible to video files in Windows (like, for instance, a youtube video) while foobar is playing a file with a different sample rate. Ofcourse the audio will not play, but with the default foo_out_asio not even the video would. Is this component just a slightly more stable version of foo_out_asio? Should...
If foo_out_asio already outputs native dsd, what is the purpose of foo_out_asio+dsd?
Thank you. It might be fixed in v2.0.17. If it doesn't, please provide me with the fresh crashdumps.
SACD_input crashes foobar
I checked it, it works! Thanks for the quick response!
It's partially fixed in v2.0.16. The fix won't work for >= 176400 sources.
foo_input_sacd-2.0.15 failed conversion
Crash when closing foobar when not playing dsd files
ASIO+DSD Output stuck between formats
foo_input_sacd crashes foobar when trying to open some wavpack files
Hello Maxim, many thanks for your prompt follow-up and for the excellent component you made for foobar. Well noted, and so, probably, it would be better to update the release baseline to the new one. Because, without baseline updating we do not get any email notification about any new release. Again, thanks a lot and all the best Andrea
v0.4.4 and 0.4.5 is crashing foobar isn't working..
Hi Everyone. I have similar situation. I've installed all needed components. Real-time conversion PCM to DSD (playback) works with configured DSD Processor (DSP Manager and SACD sub-menu) via WASAPI on my DAC. And the strangest thing is that conversion PCM to DSD (file) works only with PCM format witch frequency is divided by 1000 (48; 96; 192 kHz). With another frequences (don't divide by 1000 - 44.1; 88.2; 176.4 kHz) DSD Converter gives an error - Invalid parameters. I tried different versions...
Hello Maxim, thanks so much for your prompt follow-up. Kind regards, Andrea PS: Sorry for the "anonymous reply", it was me having forget to log-in.
1.5.11. 1.6.x now doesn't work with the newest foobars.
Which is the stable version?
I have updated to the latest 2.0.14 and the issue remains the same as noted above. FYI - The older 1.6.2 plugin is completely non-functional with DSD on the latest non-beta foobar2000, but this older version works fine on the latest beta.
Of course I mean for PCM to DSD in DSDprocessor...
Thank you for the info. That's too complicated for the simples DSD up sampling task. The trivial convolution is very relevant there.
[SUGGESTION] ARDFTSRC resampler
Add option to apply Transition delay also on session start (Stop → Play)
And what is "Bits" value under Preferences->Playback->Output->Devices?
I've currently got Grace m9XX (XMOS USB Audio) [exclusive] selected: Should I pick another option?
This DAC uses XMOS ASIO driver. Have you tried Default: ... [exclusive] 32 bits instead of ASIO: ... ?
I'm using a Grace m9XX DAC/amp.
What output device do you use?
Has anyone else run into an issue where the foo_input_sacd plugin version 1.5.11 works perfectly, but after upgrading to 2.0.14, you hear a constant hiss over the music? It almost sound like an abused, dusty vinyl recording. I'm using Output Type DSD and DoP for Converter, and the old version works great, showing DoP being decoded by my DAC. The latest version, however, seems to be passing along DSD via DoP, but is inserting quite a bit of hiss noise in the sound output. Is this a known issue with...
Thanks, Merry Christmas too! Red colour means CPU overload. It doesn't change audio stream. No, I didn't test in different modes.
Merry Christmas! Maybe the modulator is getting stressed? What actually happens when the ‘Load Metric Indicator’ turns red? Did you test with 4fS / 8fS PCM rates and a longer L?
I've just tested that both 2.0.2 and 2.0.3 produce the same DSD64 stream out of PCM44100 source at 0 dB volume. If, on your system, it is not so it is very strange.
None of my business, but I haven't found any symptoms of disfunction att all. Latest FB2K(64) beta version with all the SACD and ASIO+DSD plug-ins into a Hugo2. And DSD works great. Blind guy, so I don't really care about visualizations. But, keep up the good work, Maxim.
v2.24.6 [x64], as any newer stable or preview version simply don't work (playback continuously shuttering) with SACD Plugin anymore in my playback environment.
v2.24.6 [x64], as any newer stable or preview version simply don't work (playback continuously shuttering) with SACD Plugin anymore in my environment.
v2.24.6 [x64], as any newer stable or beta version simply don't work (playback continuously shuttering) with SACD Plugin anymore in my environment.
v2.24.6 [x64], because any newer stable or beta version simply don't work (playback continuously shuttering) with SACD Plugin anymore in my environment.
What Foobar version do you use?
But the Foobar2k's volume was always set to 0dB... I don't actually use any digital volume in my audio processing pipeline, because my DAC (IFI neo iDSD) has an analogue volume control. What I heard with v2.0.3 is slightly less dynamic range reproduction. v2.0.2 was apparently more energetic and dynamic sounding (BTW I'm still using v2.0.2).
They should match when volume is set to 0dB.
Feature for saving to file and loading from file all settings of DSD Processor
It looks like with "DSP chain presets" Load/Save generic functionality the main goal is already achieved. Except easy portability between fb2k instances. Case closed.
I asked because I'm hearing some sonic differences (in a bad way) when I go from the DSD Processor v2.0.2 to v2.0.3 ... and it's definitely not a placebo at all. I think volume independent DSD Processor was better.
I asked because I'm hearing some sonic differences (in a bad way) when I go from the DSD Processor v2.0.2 to v2.0.3 ... and it's definitely not placebo at all. I think volume independent DSD Processor was better.
I asked because I'm hearing some sonic differences (in a bad way) when I go from the DSD Processor v2.0.2 to v2.0.3 ... and it's definitely not placebo at all. is this normal?
I asked because I'm hearing some sonic differences when I go from the DSD Processor v2.0.2 to v2.0.3 ... and it's definitely not placebo at all. is this normal?
I asked because I'm hearing some sonic differences when I go from the 2.0.2 to 2.0.3... and it's definitely not placebo at all. is this normal?
It's just foobar volume control. For DSD playback it doesn't work. But when DSD Processor is active foobar volume control works again.
It's foobar feature: File->Preferences->Playback->DSP Manager->DSP chain presets.
Are you talking about "DSP chain presets" Load/Save as implementation of the next enhancement request #85? If yes, then this request is not necessary. Thanks!
Just got the 1.6.4 release. Many thanks!
Agreed. WOuld VERY much love to see this and the DVD-A plugin available for Mac version. And thank you so much for all the work on this!
Could you please shed some light on ‘Version 2.0.3 – Volume control is reestablished’? What exactly is the ‘volume control’ feature?