-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing metadata readSPDIFOnRegister in dsp profiles #15
Comments
This attribute is used in our latest DSP profile included in HiFiBerryOS: It shows that the SPDIF input is active. If you want to create a change make sure that attribute is used if it exists and you may ignore it otherwise. |
I'm not sure if I understand what you're saying. I'm not using HifiBerryOS, just default Raspbian (for now). I've installed the I've tried adding |
The profile you're using doesn't support the readSPDIFOnRegister attribute. Just adding some metadata record won't work as the profile itself doesn't support it. I linked the other profile above to chow you a profile that does have support for the readSPDIFOnRegister attribute. |
Aaah, now I understand it. Thanks. Unfortunately SigmaStudio is not available for macos. Although it's probably to complicated for me anyways... I might try the profile you linked to. I probably don't need any special stuff anyways. Thanks again! And thanks for providing a nice product (especially the open-source software!). |
I was trying to get my LG7450PLA with SoundSync to work with my DAC+DSP. It was quite fun to debug the problem (learning a bunch of new stuff!) and I think it's related to a variable/attribute/metadata not being set in the dsp profiles. In the sigmatcp logs I found the following:
Which means
ATTRIBUTE_SPDIF_ACTIVE
orreadSPDIFOnRegister
is undefined. I couldn't findreadSPDIFOnRegister
in any of the DSP profiles xml files, so I guess that must be it. I disabled checking for this register insoundsync.py
and everything worked (well, after re-uploading my DSP profile, somehow the volume didn't change when the ALSA mixer changed...)Unfortunately I have no idea what the value should be, otherwise I would have made a pull request. Sorry.
The text was updated successfully, but these errors were encountered: