1

DSP settings not available in HifiBerryOS

mklod

February 25, 2021 19:59

None

Follow

Hi,

I'm using the Latest HiFiBerry OS - hifiberryos-20210203 - on a pi 3B.

The About page on HiFiBerryOS shows my DAC + DSP as a DAC+ Zero/Light/MiniAmp. The Sound>DSP page just tells me what I can do if only I had a DSP card connected!

"These features require a DSP-equipped sound cards as the HIFIBerry DAC+ DSP..."

Yeah, that's my precise card. How can I set it to the correct DAC? I found a post where dac-dsp reset was the command to use but this creates a 'command not found' error. I also read through related threads and had no luck.

tried this (several times)

/opt/hifiberry/bin/reconfigure-players

 

output

no change. terminated

 

tried this

mount -o remount,rw /boot
nano /boot/config.txt 

modified last line

dtoverlay=hifiberry-dacplusdsp

reboot

result:
now correctly shows dac+dsp on the about page, but the Sound>DSP page still tells me a DSP card is required to play with DSP settings

tried this:

dsptoolkit --timeout=60 get-volume

outputs:

Profile doesn't support volume control

 

• Facebook
• Twitter
• LinkedIn

23 comments

• 0
  
  mklod February 27, 2021 00:05

  tested it on a pi 4 and I get the same problem.

• 0
  
  Domenico Guerra February 27, 2021 09:39

  try to reinstall dsp profile

• 0
  
  mklod February 27, 2021 22:45

  I tried 

  dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/dacdsp-default.xml

  no luck. I also tried

  dsptoolkit reset

  Now I am able to successfully set and retrieve volume settings.

  # dsptoolkit set-volume -- -3db
  Volume set to -3.0dB
  # dsptoolkit get-volume
  Volume: 0.7079 / 95% / -3db

  aplay shows correct soundcard recognized:

  # aplay -l
  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberrydacplusdsp_sou], device 0: Hifiberry DAC+DSP SoundCard HiFi dacplusdsp-codec-0 [Hifiberry DAC+DSP SoundCard HiFi dacplusdsp-codec-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  However I still can't apply DSP profiles in the Hifiberry OS UI...

  Am I missing something obvious? I thought the point of Hifiberry OS was to be plug and play ready with DAC+DSP

  Edited by mklod February 27, 2021 23:27
• 1
  
  Fotis Diamantopoulos February 28, 2021 06:17

  Hey,

  The DSP programs are in /opt/beocrate/beo-dsp-programs/

  Try to install a profile from that folder.

  Regards,

  Fotis

• 0
  
  mklod February 28, 2021 23:49

  The dacdsp default profile on git should work with my DAC+DSP according to the (very terrible) documentation.

  I also tried installing several profiles in /opt/beocreat/beo-dsp-programs and resetting dsptoolkit to load them, and they always return "Profile doesn't support volume control".

  None of the profiles fix the major issue that Hifiberry OS does not allow me to configure the DSP or load profiles through the UI. Installing a profile on the command line shouldn't even be necessary in my case.

  

   

  # /opt/hifiberry/bin/check-system
  HiFiBerryOS version: 20210203
  Pi model: 3B
  Sound card: DAC+ DSP
  Sound card ID: 0
  Mixer: DSPVolume
  Features: pi pi3orlater arm7 dsp toslink localui
  Linux version: Linux hifiberry 5.4.83-v7 #1 SMP Wed Feb 3 11:52:16 UTC 2021 armv7l GNU/Linux
  Date and time: Sun Feb 28 15:48:40 PST 2021
  /data mounted: OK
  /dev/dri/card0: OK
  BT devices:
  WiFi devices: wlan0
  audiocontrol2: running
  beocreate2: running
  bluetooth: not running
  bluealsa: running
  bluealsa-aplay: running
  dlnampris: not running
  mpd: running
  pigpio: running
  raat: running
  shairport-sync: running
  sigmatcp: running
  snapcastmpris: not running
  spotify: running
  squeezelite: not running
  sshd: running
  ympd: running
  weston: running
  cog: running

• 0
  
  mklod March 04, 2021 22:33

  This is ridiculous. I've wasted so much time on debugging something that's supposed to work out of the box and a week later there's still zero support from Hifiberry team. My Hifiberry hardware still doesn't work with the official Hifiberry OS.

  I wanted to use Hifiberry OS first just to test the hardware before working on a more advanced system installation. Hifiberry OS sounds like a great, easy thing -- if only it worked. I'm certainly not going to bother with a more advanced system config if I can't run a basic test of the hardware with a stock/preconfigured DSP profile.

  From my messages it should be clear that I'm not new to linux or raspi. I'm not new to DSP either. Anyone who finds this thread should be warned: save yourself hours of headache and go over to miniDSP and get one of their units instead. My Hifiberry ADC+DSP is going back from whence it came.

   

• 0
  
  HiFiBerry team March 05, 2021 05:23

  I'm sorry to hear that you're having problems. This looks like a software bug as the DSP is detected.
  
  You might try
  
  rm /etc/hifiberry.state
  /opt/hifiberry/bin/reconfigure-players
  
  BTW: I sent you this already 3 days ago!

  Edited by HiFiBerry team March 05, 2021 06:32
• 0
  
  mklod March 05, 2021 07:24

  They should take notes here. The way Hifiberry OS is designed, it really should have an option to select your board during software setup. Ok sure, it's not a big deal to setup SSH and define the hardware board in config.txt, if that would do it. But that wasn't sufficient to fix the issue in my case.

  As an engineer, it's a red flag when the 'datasheet' is a link to a brief web page and not a literal .PDF datasheet. Not to mention the ambiguity (or outright errata). The 'datasheet' (https://www.hifiberry.com/docs/data-sheets/datasheet-dac-dsp/) for the DAC+DSP says the overlay should be 'dac' (!), while some posts on the forums say it should be 'dacplusdsp':

  CONFIGURATION

  Overlay for config.txt:
  dtoverlay=hifiberry-dac

  I'd consider giving Hifiberry another shot if they had a preinstalled adaptive loudness DSP profile. Using this link (https://clemme.weebly.com/dsp-program.html) as an example project is a complete joke. Good luck doing anything other than setting EQ and filters without spending a year learning Sigma Studio.

• 0
  
  westy March 06, 2021 03:06

  Bump.  Having the same problems, tried everything listed above.  Others are posting the same issue elsewhere.

  https://support.hifiberry.com/hc/en-us/community/posts/360014715057-DAC-DSP-Is-Not-Correctly-Recognized?page=1#community_comment_360003990118

   

• 0
  
  HiFiBerry team March 06, 2021 05:39

  What is the output of

  /opt/hifiberry/bin/check-system

• 0
  
  westy March 06, 2021 06:30

  HiFiBerryOS version: 20210203
  Pi model: 4
  Sound card: DAC+ DSP
  Sound card ID: 0
  Mixer: Softvol
  Features: pi bluetooth pi3orlater arm7 toslink localui
  Linux version: Linux hifiberry 5.4.83-v7l #1 SMP Wed Feb 3 11:58:50 UTC 2021 armv7l GNU/Linux
  Date and time: Fri Mar 5 22:28:33 PST 2021
  /data mounted: OK
  /dev/dri/card0: OK
  BT devices: hci0 - Cypress Semiconductor (305)
  WiFi devices: wlan0
  audiocontrol2: running
  beocreate2: running
  bluetooth: running
  bluealsa: running
  bluealsa-aplay: running
  dlnampris: not running
  mpd: running
  pigpio: running
  raat: running
  shairport-sync: running
  sigmatcp: running
  snapcastmpris: not running
  spotify: running
  squeezelite: not running
  sshd: running
  ympd: running
  weston: running
  cog: running

• 0
  
  HiFiBerry team March 06, 2021 06:41

  Looks like the DSP isn't detected. This could be a hardware problem or a bug. What's the output of
  
  dsptoolkit get-meta detected_dsp

• 0
  
  westy March 06, 2021 06:55

  usage: dsptoolkit [-h] [--delay DELAY] [--host HOST] [--timeout TIMEOUT]
  {apply-fir-filter-left,apply-fir-filter-right,apply-fir-filters,apply-iir-filters,apply-iir-filters-left,apply-iir-filters-right,apply-rew-filters,apply-rew-filters-left,apply-rew-filters-right,apply-settings,check-eeprom,clear-iir-filters,get-checksum,get-limit,get-loudness,get-memory,get-meta,get-prog,get-samplerate,get-volume,get-xml,install-profile,load,loop-read-dec,loop-read-hex,loop-read-int,loop-read-reg,mute,read-dec,read-hex,read-int,read-reg,reset,save,set-limit,set-loudness,set-volume,store,store-filters,store-settings,tone-control,unmute,version,write-mem,write-reg}
  [parameters ...]
  dsptoolkit: error: argument command: invalid choice: 'get_meta' (choose from 'apply-fir-filter-left', 'apply-fir-filter-right', 'apply-fir-filters', 'apply-iir-filters', 'apply-iir-filters-left', 'apply-iir-filters-right', 'apply-rew-filters', 'apply-rew-filters-left', 'apply-rew-filters-right', 'apply-settings', 'check-eeprom', 'clear-iir-filters', 'get-checksum', 'get-limit', 'get-loudness', 'get-memory', 'get-meta', 'get-prog', 'get-samplerate', 'get-volume', 'get-xml', 'install-profile', 'load', 'loop-read-dec', 'loop-read-hex', 'loop-read-int', 'loop-read-reg', 'mute', 'read-dec', 'read-hex', 'read-int', 'read-reg', 'reset', 'save', 'set-limit', 'set-loudness', 'set-volume', 'store', 'store-filters', 'store-settings', 'tone-control', 'unmute', 'version', 'write-mem', 'write-reg')

   

• 0
  
  HiFiBerry team March 06, 2021 06:57

  get-meta 

• 0
  
  mklod March 06, 2021 06:59

  oh look, a bunch of simple commands that would have been really helpful to have listed in a datasheet or other documenation as basic troubleshooting steps

   

  You might try
  
  rm /etc/hifiberry.state
  /opt/hifiberry/bin/reconfigure-players

   

  
  What's the output of
  
  dsptoolkit get-meta detected_dsp

   

   

  What is the output of

  /opt/hifiberry/bin/check-system

• 0
  
  westy March 06, 2021 17:30

  20 years ago I was technical support for an industrial controls company.  I got sick of answering the same old questions over and over.  I wrote white papers on the 20 most common problems and with in a year the number of tickets dropped by 70% which allowed me to spend my time doing more interesting things.  Didn't go over well with some of my coworkers who liked getting paid to answer easy questions.

• 0
  
  westy March 08, 2021 04:31

  Resolved:  https://support.hifiberry.com/hc/en-us/community/posts/360014624237-DSP-settings-not-available-in-HifiBerryOS

  Super secret worky/no-worky jumper that didn't come installed on my board.  

  Seems like this would be good information to put into the data sheet.  I'm sure that is probably too difficult.

   

   

  Edited by westy March 08, 2021 04:34
• 1
  
  Mfuttrup April 09, 2021 20:45

  Hi

  I have the same problem. Were does the jumper go on the DSP board?

  Thanks!

• 1
  
  ktully April 10, 2021 02:35

  Edit: The documentation/datasheet I reference below has been updated since my original post and now indicates the location and necessary state of the jumper on the DAC+DSP.

  Thanks, HiFiBerry team!

   

  This is indeed an issue that could be easily avoided if the documentation included a reference to the required jumper. Perhaps another issue seems to be that the DAC+ DSP product page's reference image shows an older revision board (1.01), while the last two of this model that I've purchased have been 1.3.
  
  I spent a few hours in forum posts and looking at the online datasheet (https://www.hifiberry.com/docs/data-sheets/datasheet-dac-dsp/), but even in the 'Connectors and Jumpers' section, this jumper isn't specified.
  
  Here's a photo of what you'll want to be looking for:
  

  Notice the jumper (a cap that connects the pins) is installed in these photos. This is what a working board should look like.
  If you DO NOT have a jumper, that may be why your board isn't working.

  (link to Imgur album if the images are missing - https://imgur.com/a/jf2X2r9)

  This is on board revision 1.3. There are two pins directly behind the SPDIF input next to the R7 resistor. They must have a jumper on them for the DSP to be recognized.  From what I understand from their other documentation, you'll void your warranty if you solder anything to the board, so consider a jumper first if that's important to you.
  
  

  Mfuttrup: Knowing this, here's what I'd recommend for your next steps:

  - Power off your Raspberry Pi
  - Apply a jumper to the two pins nearest to the SPDIF Input (see red highlight in the pictures above)
  - Power on your Raspberry Pi
  - SSH to the Pi as root
  - Run the following command: /opt/hifiberry/bin/reconfigure-player
  - If using HifiberryOS, navigate to the web UI in a browser and go to the 'Sound' tab. 
  - Ensure 'Show Advanced Settings' is checked. You should now (hopefully) see a 'DSP Programs' option.
  - Click 'DSP Programs' and select "DAC+ DSP Universal" (I had two versions, 11 and 12. I just selected the high version)
  - Click "Install this program.'

  That's it! You should (hopefully) have a working DAC+DSP at this point.
  
  It's frustrating to know this was a simple hardware issue, but hopefully, the Hifiberry team can include some additional info about the jumper for future customers.
  
  My guess is that 3rd-party resellers are not including the jumper with their boards, which would explain why many amazon reviews for US-based resellers suggest they are selling DOA boards. I've bought all of my HW from Hifiberry directly in the past but bought this one from amazon as I was in a rush and couldn't wait for shipping from Switzerland. 
  
  Hifiberry already does a great job of pointing this out for the Beocreate2, so I'll keep my fingers crossed that documentation is updated to include a reference to the jumper!

   

  Edited by ktully May 07, 2021 22:36
• 1
  
  HiFiBerry team April 10, 2021 06:27

  We'll update this soon.

• 0
  
  RyanB21 December 18, 2023 18:03

  I just purchased an Amp4 to replace my Amp2 as it has DSP. But was surprised to see in Hifiberry‘s excellent OS that the DSP option wasn’t available as in the posts above. I guess that I too need to insert a jumper cable to one of the two sets of pins at the edge of the board. Any guidance on (a) if this correct and (b) which set of pins need to be connected ? I couldn’t info find this. Something on this in a visible place on Amp4 would be v.useful.

  Edited by RyanB21 December 18, 2023 18:04
• 0
  
  RyanB21 December 18, 2023 18:12

  Oh, I just noticed that I have to buy the DSP add on board. The Amp4 is just compatible with it. Should have read this more carefully…. Maybe I should have gone for the Beocreate board instead? Or is it easier to configure the DSP settings with the add on board?

• 0
  
  HiFiBerry team December 19, 2023 09:26

  The UI basically works the same way with the Amp4 + DSP addon and the Beocreate.