Skip to content
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

HifiBerryOS 20200226 Possible Bug In GUI #75

Open
rh1017 opened this issue Mar 24, 2020 · 3 comments
Open

HifiBerryOS 20200226 Possible Bug In GUI #75

rh1017 opened this issue Mar 24, 2020 · 3 comments

Comments

@rh1017
Copy link

rh1017 commented Mar 24, 2020

Hello Tuomas,
There is possibly a bug in the HiFiBerry OS 20200226 GUI.
I have two HiFiBerry DAC+DSP boards, one V1.3, the other V1.0.1. Daniel has advised there is no electrical difference between these versions.
After installing the OS on V1.0.1 the advanced sound options did not show in the GUI.
Manual deployment of the dacdsp-universal-10.xml profile was successful with all options showing in the GUI however they were not retained on reboot.
I have not had any issue with the V1.3 installation which was made with an earlier OS version and updated through the OS before 20200226 was posted on the HFB website.
I cloned that microSD card and booted V1.0.1 with it and the installation is quite stable with all settings pages retained.
Both DAC+DSP boards are on RPi 3A+'s.
Do you think this is possible? Could you investigate and advise if there are any steps I should follow to help?
Best regards,
Richard Harvey
HFB_Cap1
HFB_Cap2
hifiberry-debug.zip

@tuomashamalainen
Copy link
Collaborator

Hi Richard and thanks for your report. I will take a look at your logs shortly. Based on your screenshot it appears to be something that halts the execution of the "DSP Programs" extension (which in turn would mean none of the other DSP adjustments will work), because "damaged code on the sound system" message is hardcoded in the HTML and should be cleared (or replaced) when information is received from the Pi.

Best,
Tuomas from Bang & Olufsen

@tuomashamalainen
Copy link
Collaborator

Looking at the logs, I do not see any uncaught exceptions that would indicate a problem, but I also do not see any other activity that the DSP Programs extension should be doing ("connected to DSP server", "added DSP program XYZ", "DSP checksum is ABC...", etc.) on the last run before you collected the diagnostic file, which is weird.

Just want to make sure: does the issue persist after rebooting? Did you try booting the installation that's giving you trouble with the other sound card?

@rh1017
Copy link
Author

rh1017 commented Mar 25, 2020

Hi Tuomas,

Thank you for your replies.
Your comment mentioning HTML triggered a thought.

When the GUI displayed this on the SOUND page (Clip01b), and, on the SOURCES page (Clip01a). Note: Optical is not shown under "Disabled Sources"
Alternating through other tabs also displayed missing items.

_I tried refreshing the browser and all options were available - the fix was so simple !...

I could repeat this with a number of new installs, on both boards and Chrome and Firefox browsers. I was using a Win7Pro box. I have not tried on a Win10 box.

Is this something that may need attention in the next OS update?

Best regards, stay well and stay safe
Richard

Clip01b
Clip01a

@rh1017 rh1017 closed this as completed Mar 25, 2020
@rh1017 rh1017 reopened this Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants