1

HifiBerry OS GUI has stopped working

Bob Moss

March 17, 2023 10:52

None

Follow

I've got the HifiBerry DAC+ DSP board running on a raspberry Pi4 and the latest version of HiFiBerry OS (2023023).

Everything has been working OK for a few weeks now.

Yesterday I decided to try the room correction function and got an error message about sample rates. As I was running Dsp V12, I loaded up Dsp V13 and tried again. This worked OK, but the optical input stopped working. So, I reloaded Dsp V12. Everything was OK, for a minute and then the music stopped playing. I tried clicking on a few settings but no sound was coming out.

So I decided to reboot the unit.

Once the unit rebooted, the web front end has stopped working. If I try going to the web page it just sits there unit eventually the browser times out.

I can ping the device and I can ssh in.

When I ssh in and do "systemctl status beocreate2" it shows and exception is happening (see below).

I've compared the config files to ones I have backed up and they are all the same.

So I wiped the SD card and copied the install over again. Started up the Pi and get exactly the same (i.e. no web interface and the same error)

So I got a brand new SD card, tried the install again, got the same error.

If I unplug the DAC+ DSP board, the web interface comes up OK. If I then plug the DAC+ DSP back in, the web stops working.

So something on the Dac+DSP board is stopping the beocreate service.

Help!

Here is the error output:

     Loaded: loaded (/usr/lib/systemd/system/beocreate2.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/beocreate2.service.d
             └─override.conf
     Active: active (running) since Fri 2023-03-17 10:21:38 GMT; 1min 19s ago
       Docs: https://github.com/bang-olufsen/create/
    Process: 1039 ExecStartPre=/opt/hifiberry/bin/bootmsg Starting Beocreate server (code=exited, status=0/SUCCESS)
    Process: 1124 ExecStartPost=rm /etc/quiet_start (code=exited, status=1/FAILURE)
   Main PID: 1046 (node)
      Tasks: 3 (limit: 3812)
     CGroup: /system.slice/beocreate2.service
             └─1046 /usr/bin/node /opt/beocreate/beo-system/beo-server.js vv

Mar 17 10:21:42 hifiberry node[1046]:     at applyChannelDelayFromSettings (/opt/beocreate/beo-extensions/channels/index.js:703:21)
Mar 17 10:21:42 hifiberry node[1046]:     at EventEmitter.<anonymous> (/opt/beocreate/beo-extensions/channels/index.js:354:5)
Mar 17 10:21:42 hifiberry node[1046]:     at EventEmitter.emit (/usr/lib/node_modules/eventemitter3/index.js:202:33)
Mar 17 10:21:42 hifiberry node[1046]:     at /opt/beocreate/beo-extensions/dsp-programs/index.js:84:18
Mar 17 10:21:42 hifiberry node[1046]:     at /opt/beocreate/beo-extensions/dsp-programs/index.js:323:8
Mar 17 10:21:42 hifiberry node[1046]:     at /opt/beocreate/beo-extensions/dsp-programs/index.js:360:19
Mar 17 10:21:42 hifiberry node[1046]:     at ChildProcess.exithandler (child_process.js:374:7)
Mar 17 10:21:42 hifiberry node[1046]:     at ChildProcess.emit (events.js:400:28)
Mar 17 10:21:42 hifiberry node[1046]:     at maybeClose (internal/child_process.js:1058:16)
Mar 17 10:21:42 hifiberry node[1046]:     at Socket.<anonymous> (internal/child_process.js:443:11)

• Facebook
• Twitter
• LinkedIn

8 comments

• 1
  
  Bob Moss March 17, 2023 11:47

  OK, I've managed to fix this after a lot of debugging.

  The issue is that (as we know) the supplied DSP v12 has an error in it for sample rates.

  I looked at the journal logs and found this error:

  Mar 17 11:18:56 hifiberry node[1938]: }
  Mar 17 11:18:56 hifiberry node[1938]: /opt/beocreate/beo-extensions/channels/index.js:703
  Mar 17 11:18:56 hifiberry node[1938]:                                 beoDSP.writeDSP(delayRegister, 0, true, true);
  Mar 17 11:18:56 hifiberry node[1938]:                                                 ^
  Mar 17 11:18:56 hifiberry node[1938]: ReferenceError: delayRegister is not defined
  Mar 17 11:18:56 hifiberry node[1938]:     at applyChannelDelayFromSettings (/opt/beocreate/beo-extensions/channels/index.js:703:21)

  So I went and had a look at the /opt/beocreate/beo-extensions/channels/index.js file and can see in the code above line 703 there is a comment that says "// Delay is input as milliseconds. Convert to samples based on sampling rate.".

  So, if you have DspV12 loaded, in some cases is causes the delayRegister to be not set, and then the beoDSP.writeDSP(delayRegister, 0, true, true); line fails, crashing the beocreate2 service.

  To fix this, you need to ssh in and manually load up DSPv13 by running:

  /bin/dsptoolkit install-profile /opt/beocreate/beo-dsp-programs/dacdsp-13.xml

  Once you reboot, everything comes back up OK.

  You can then edit the Dsp V12 file and change "samplerate" to "sampleRate". Reload DspV12 and it is all back up and running!

• 0
  
  jzahraoui March 21, 2023 09:58

  thank very much, you saved my life

• 0
  
  Jerome Le Luyer March 21, 2023 16:14

  Thanks for the info. So does v12 with the correct "sampleRate" wording work fine with room correction now ?

• 0
  
  jzahraoui March 21, 2023 17:12

  it's V13 now but had to correct the typo to get it work. hope will be corrected in next version.

• 0
  
  Bob Moss March 21, 2023 17:23

  Jerome Le Luyer Yes, I've just tried it and it works OK with room correction now.

• 0
  
  Bob Moss March 21, 2023 17:25

  jzahraoui There is a V13 but unfortunately it stops the optical input working, which is why I was trying to use V12.

• 0
  
  T Haugen January 08, 2024 17:46

  My devices, plural yes, all have stopped displaying the OS web page but they are responding correctly to SSH and playing music but I cannot restart them from the web page anymore so I have to go into my Closet to restart when there is a problem.  So I would like to fix.  It seems this error could be the same error I am seeing.  How do I check what version DSP I am running?

• 0
  
  HiFiBerry team January 09, 2024 05:43

  If you get a white web page, that's usually a problem with your Adblocker (or similar plugins). Make sure to disable these.