0

DSP: Volume-Variable Bass Peak/Shelf

snapcaster1

November 21, 2020 13:04

None

Follow

Hi Folks!

Playing around with DAC-DSP using HifiBerryOS on RPI4.  Successfully played around with the DSP via the WebUI.  My goal is to run mono and use the right channel as a sub and the left channel as a high pass (100hz) full rangish driver ... I was able to achieve this.  However, I am building this into a smallish portable speaker and want to overdrive the bass BUT only at lower volume levels.  My goal is kind of like an automatic and variable "Loudness button" on older amps.  To be more specific: eg:

29Hz +10dB Q0.2  when gain is -35db

29Hz +8dB  Q0.2 when gain is -25dB

29Hz +6dB Q0.2  when gain is -15db

29Hz +1dB  Q0.2 when gain is -5dB

Question:  Is this possible with this DSP? If so, can it be done outside the windows program (CLI or WebUI is preferred).

Thanks!

 

 

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  HiFiBerry team November 21, 2020 16:00

  Check this out:
  https://support.hifiberry.com/hc/en-us/community/posts/360013421238-Loudness

• 0
  
  snapcaster1 November 25, 2020 20:48

  Thanks!  I was able to get my feet wet in the SigmaStudio env ... there are some interesting features in it and I should be able to get what I am after ... 

  When I install the default dacdsp-v11.dspproj found on github, my volume control stops working (testing using Spotify Connect ... nether HiFiBerryOS volume nor Spotify Volume work).  It seems to take it (and stay fixed) from the Master Volume set in SigmaStudio.  Is this normal?  (I am sending that project to the DSP using "Link Compile Download").  Do I need to save to EEProm or reboot?

  One other thing that is not quite evident ... How does the HifBerry WebUI influence things once a custom config is pushed from SS?  For example, the webui has the ability to invert the polarity on a channel ... if this is deleted in SS ... what is the impact? 

  Lastly, should the custom programs from SS be visible to load in the WebUI under "Available Programs"?   

  Thanks in advance! 

• 0
  
  HiFiBerry team November 26, 2020 06:57

  Yes, that's exactly how it's supposed to work. When you push a new DSP program to the Pi, HiFiBerryOS doesn't know anything about it. It doesn't know what features is supports and how it's working internally. For this, you have to create a DSP profile file and add the required metadata. Have a look at the guide on Github:
  https://www.hifiberry.com/blog/how-to-create-your-own-dsp-profiles/

• 0
  
  Lu Greco March 10, 2021 19:41

  hi daniel,

  could one of you guys do a video about the whole procedure of

  https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/adaptexistingprofiles.md  ??

  explained in picture is not always the best way.

  thanks in advance