RobertoSpeed

I've identified the issue preventing burned SACDs from playing. The problem appears to be caused by the Waveform Seekbar plugin. After uninstalling the plugin, the SACD was able to play correctly. However, I really enjoy using the Waveform Seekbar and would like to be able to use it without any issues. Could you please resolve the conflict between the plugin and SACD playback? Thanks in advance for your support! Best regards,

I am attaching again the crash reports that I received a little while ago with foobar2000 DarkOne

I just tried with foobar2000 base, i.e. not foobar2000 DarkOne, and it plays burned SACDs without any problems. Why don't they play with foobar2000 DarkOne? What component is preventing it from starting?

Crash with SACD burned on recent version of foo_input_sacd-2.0.10 Hi, Today I tried to play a burned SACD: foobar2000 can open it, but it can't start playback, and the application crashes (in some cases even causing a system freeze). With version foo_input_sacd-2.0.3, the same disc played correctly. I'm attaching the two crash report files, hoping they'll help you pinpoint the cause of the problem. Thanks in advance for your help and for your work on the plugin!

Maxim V. Anisiutkin, I don't understand why you reply to the guy who didn't write this post, but you never reply to me, who wrote this post. Anyway, even with foo_input_sacd-2.0.10, I don't even have runtime error problems.

So: the author of the post: Bug report: foobar2000 crash with foo_input_sacd 2.0.8, it's me: RobertoSpeed, the other one who asked you two questions under my post, I don't know who he is. That is, he asked you these two questions: << I installed v.2.0.8 (with exact vis enabled) and my foobar (2.25.) crashed four times within 15 minutes. Downgraded to 2.0.7 - no crashes so far. >> << v.2.0.9 crashes like 2.0.8. V.2.0.7 works (except stuttering with foo_skip enabled). >> But anyway, now with foo_input_sacd-2.0.9...

I also add the 2 crash reports files

I attach a screenshot of the error