SACD breaks built-in spectrogram
Status: Inactive
Brought to you by:
manisiutkin
Menu
▾
▴
1 Attachments
#223 SACD breaks built-in spectrogram
When I have foo_input_sacd installed, built-in Spectrogram no longer has mono view: If I right click on the display>Channels>Mono, it still shows the default channels, which is unchanged. I get that feature back if I uninstall foo_input_sacd. Is there a solution to the problem? Thank you!
Discussion
Anonymous
I've pinpointed the problem to have started since "v2.0.3 - Spectrum visualization is fixed". v2.0.2 doesn't have this problem but the mono display for DSD does have problem. It shows a "zoomed in" spectrogram when mono is selected.
Does v2.0.14 fix this?
Yes, v2.0.14 fixed the problem! You are so quick in responding and fixing it, Maxim. Thank you so much!
@manisiutkin as far as I know you are absent from Hydrogenaudio forum. There has been some disscussion abut some hacks that are used in sacd_input that are not necessary.
Below is a message from one the the users/developers:
None of the hacks that alter foobar2000 behavior are necessary to play DSD. The component could for example implement its own output and send PCM data to foobar2000 core and feed the DSD bits directly to the special output. Everything would work perfectly and nothing would get broken.
I don't think that there is any conspiracy or opposition to your component or sacd in general.
Maybe you should just communicate with those guys to make things work better?
As far as I understand most problem arise from DSD-visualisation. Maybe the DSD-vis should be excluded from the SACD-input componet and rewritten as stand-alone visualisation component.
I am not a developer so please excuse me if I my thinking is ipmproper.
But once again - those guys at Hydrogen say that sacd-input component does some "nasty" tricks to foobar and that those tricks are really not necessary for it to work properly. To my understanding they say there should be a "proper" solution to be able to play and visualise DSD signals within foobar - meaning some part of your component should behave differently (which probably means: some part should be rewritten in a different way).
Once again thank you for this component.
I don't think either. Foobar developer just doesn't care about Native/DoP DSD playback for more than 14 years. If this attitude changes, it'll be reflected in the SDK. Until then foobar's private parts abuse will be going on.
Not abuse, it's creativity. You've made DSD work and kept it working all this time. You are skilled enough to do so in spite of their indifference or lack of assistance. Furthermore, your implementation is referenced in several audio application notes; so better people think it is the way to playback DSD. Massive kudos.
Thank you for understanding. The rational way would be to add DSD support to the foobar's SDK. The other ways are just a kind of reactive.