0

Layman's trouble with DspToolkit on DietPi

Aleksandar Lazic

May 07, 2023 01:29

None

Follow

Disclaimer first: I do not know how any of this works, I just like how it sounds :)

I've used RPi3 + DigiPro with RuneAudio for years. Was super happy with it. Now I've setup RPi4 + Digi2Pro with dietPi and myMDP. Again, super happy with it. Reason for upgrade was to run more stuff on it, while I'm having a nice player (that is why DietPi). 

Other reason for upgrade was to check out DSP with REW correction. Spent a day pleasing DietPi to comply, but failed miserably :). After some trouble with missing dev tools, I've managed to install DspToolkit, but got error for installing profile step:

~# dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/client/sigmatcp.py", line 53, in connect
    self.socket.connect((self.ip, self.port))
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/dsptoolkit", line 29, in <module>
    cmdline.main()
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/dsptoolkit.py", line 1055, in main
    self.command_map[cmd]()
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/dsptoolkit.py", line 807, in cmd_install_profile
    res = self.dsptk.install_profile_from_content(data)
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/dsptoolkit.py", line 342, in install_profile_from_content
    return self.sigmatcp.write_eeprom_from_xml(content)
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/client/sigmatcp.py", line 139, in write_eeprom_from_xml
    self.connect()
  File "/usr/local/lib/python3.9/dist-packages/hifiberrydsp/client/sigmatcp.py", line 56, in connect
    raise SigmaTCPException(
hifiberrydsp.server.constants.SigmaTCPException: Could not connect to 127.0.0.1:8086

I've seen mention of 8089 port? Anyway, I've also run those:

~# systemctl list-unit-files sigmatcp.service
UNIT FILE        STATE   VENDOR PRESET
sigmatcp.service enabled enabled

and

~# systemctl list-units sigmatcp.service --all
  UNIT             LOAD   ACTIVE   SUB  DESCRIPTION
  sigmatcp.service loaded inactive dead SigmaTCP Server for HiFiBerry DSP

and 

~# journalctl -f -u sigmatcp
-- Journal begins at Sat 2023-05-06 20:18:54 NZST. --
sigmatcpserver[1813]: ERROR:root:ALSA mixer DSPVolume not found
sigmatcpserver[1813]: ERROR:root:can't create mixer control - aborting
sigmatcpserver[1813]: INFO:root:not enabling LG Sound Sync
sigmatcpserver[1813]: INFO:root:detected ADAU14xx DSP
sigmatcpserver[1813]: INFO:root:None
sigmatcpserver[1813]: INFO:root:saving DSP data memory
sigmatcpserver[1813]: INFO:root:store: getting checksum
sigmatcpserver[1813]: INFO:root:caching program memory checksum
sigmatcpserver[1813]: INFO:root:store: writing memory dump to file
systemd[1]: sigmatcp.service: Succeeded.

Any idea before I start all over again with clean OS. I might mess up ALSA config or something while setting up MPD...

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  HiFiBerry team May 09, 2023 19:17

  Looks like sigmatcpserver died after starting it. You might try to start it from command line.

• 0
  
  Aleksandar Lazic May 21, 2023 08:20

  Bummer. I've installed HiFiBerryOS and confirmed that "dsptoolkit get-volume" and "journalctl -f -u sigmatcp" work. Then I've tried to mimic its "/boot/config.txt", "etc/asound.config" and "etc/mdp.conf on fresh DietPi. There was no change: sound worked as before, but "dsptoolkit get-volume" and "journalctl -f -u sigmatcp" were still showing the same errors.

  Then I've turn HifiBerryOS again and out of pure boredom run

  dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml

  Turned on DietPi again, there was short scratchy sound and after that no sound at all. Back to HiFiBarryOS, no sound. Used its HiFiBerryOS UI to install DSP program 11 & 13, no errors, but no sound. I've also notice that now when I use "dsptoolkit" to change volume, UI doesn't show the change (that worked before I shoot myself in the foot). Also I cannot move volume slider with the mouse. 

  Pulled out DSP board and sound is back. Have I killed my DSP toy?

• 0
  
  HiFiBerry team May 22, 2023 11:49

  Changing configurations in HiFiBerryOS can sometimes create problems. Try a fresh installation. You can't damage the board by just installing a DSP profile. However, the 4way-iir.xml profile won't work at all.

• 0
  
  Aleksandar Lazic May 23, 2023 00:55

  Sounds promising :)

  Stupid question, is DSP program (v11 & v13) in HiFiBerryOS, the same things as DSP profile in `dsptoolkit` manuals? As I've mentioned, I've already installed both of them but that haven't fixed the issue. I would guess they are not the same.

  Not sure what fresh install is. I've already tried to setup fresh HiFiBerryOS installation in a hope that setup process would "reset" DSP board. It didn't.

  Finally, REW guide suggest a way to install a profile:

  dsptoolkit install-profile ./fullrange-extended.xml

  Is this the profile I should install? I do not see it in repository with other profiles. My goal is to use REW to create and use optimization filters. What would be correct profile for that scenario?