Recent changes to 81: Proper bitdepth reporting with DSD

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Sat, 07 Dec 2024 12:24:25 -0000

I really tried everything to make "channel mask" work with 5.1 sacd (including reloading info) but it still stays empty. Could you please check it?

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Thu, 28 Nov 2024 15:53:22 -0000

Reloading does not help - the field is still blank for 5.1 SACDs (I checked different albums).
Does it mean that "decoded_bitspersample" takes data after being DoPed and before deDoPed? I use ASIO+DSD for Native Output.

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Thu, 28 Nov 2024 08:39:02 -0000

Even after Properties->Tools->Reload info?
The "natural" format for both PCM and DoP is 24-bit.

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Wed, 27 Nov 2024 16:29:48 -0000

Thank you, foo_input_sacd v 1.5.12 works well.
Two minor "issues":
1. "channel mask" does not produce anything for 5.1 SACD's but it works well with stereo.
2. "decoded_bitspersample" always shows 24 no matter if I change the output mode to DSD, DSD+PCM or PCM. What does it show then? If DSD is chosen the signal shouldn't be decoded and the "meters" do not work so there is no "fake" PCM stream for visualisation. What do those 24 bits mean then?

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Wed, 27 Nov 2024 11:11:06 -0000

Thank you. I added parameters to foo_input_sacd v 1.5.12. Interesting, what difference in performance it has compared to foo_input_udsd.

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Tue, 26 Nov 2024 19:36:42 -0000

reinstalled the portable version of 2.24, this time I made it 64bit and managed to crash FB with foo_input_udsd.
I also discovered that while "normal" dsd eats more resources than with foo_input_sacd but is responsive. But when it is DST and 5.1 it reaches 96% while with input_sacd it was no more than 40-45-50.
Crash log attached.

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Tue, 26 Nov 2024 17:16:33 -0000

Unfortunately there is no crash dump - I checked the crash report folder and it is not there. It happened on 32 portable 2.24 (my test FB). FB just closed suddenly and when restarted it asked if I want to open it in safe mode or normally but no crash dump. I played sacd again but it didn't crash this time. The processor load is so high that even my mouse cursor jumps/stutters across the display (again 96%).

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Tue, 26 Nov 2024 16:43:18 -0000

Could you share that crash dump file please?

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Tue, 26 Nov 2024 16:04:36 -0000

It still stutters (even crashed foobar once) and consumes about 96% of processor (foo input sacd consumes 8-20%). It still cuts the ending of each song, the track changes and the ending of the previous song is heard as the beginning of next. Because there is nothing after the last song in the playlist, the ending of last song is just cut off (I think it's about 1 second). The cutting only happens with DSD ( I tried one mp3 and one flac and it seemed ok). The "channel mask" worked for stereo SACD but not for 5.1 (produced empty space).

#81 Proper bitdepth reporting with DSD

Maxim V.Anisiutkin — Tue, 26 Nov 2024 11:56:47 -0000

"channel_mask" is added in v0.0.12. "stream_count" is not relevant because for all playable DSD streams is equal to one. This version should have approximately the same performance as the latest foo_input_sacd.