0

DSP Profile changes do not seem to 'stick' with new profile

Edward Archibald

December 19, 2022 17:43

None

Follow

I'm working on a new DSP profile with the starting point being dacdsp-v12-1.dspproj from the github master branch.  The changes I am incorporating are:

- Route data from the DSP output to the PI so that it can be read from the alsa capture device.  I used the documentation here to get me going:

https://www.hifiberry.com/docs/software/using-the-dac-dsp-to-record-audio-from-s-pdif/

The only change I made was to have the source for ASRC6 be the DSP rather than the SPDIF receiver.  In fact, I applied all changes from the previously referenced article from within SigmaStudio because my aim is to have a profile that has this functionality when I boot the PI. This works well and as expected.

- Fix the issue with the reversed output channels. This is a real problem for me because my application uses both the digital output and the analog output and while I can swap the cables on the RCA, I can't do anything about the digital outputs.  So I switched them in SigmaStudio.

After doing this I tested to make sure that everything was working as expected i.e. DSP output available on the PI capture device, digital and analog outputs reversed from 'factor' by pushing the new program to the DAC+ DSP.  Everything works as expected. I then created a new profile with metadata,including a checksum, using the documentation here:

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

The profile that I created installs cleanly with dsptoolkit install-profile and after reboot I can see that it remains installs and that it is in the list of available profiles and I can re-install it. 

All seems well but.... when using this profile the channels are in the correct order i.e. they appear to still be reversed according to dacdsp-v12.xml.  The other thing that happens is that sometimes after reboot there is no sound on the outputs but when I execute a script to read from the capture device the sound suddenly appears.  

I may have missed a step but I'm not exactly sure where to look for the issue.  My guess is that I can look at what's in the profile .xml file and identify the 'ParamName' for the outputs to see if they are set as expected but I'm not exactly sure what to look for here.  Any guidance would be much appreciated.

It's all pretty impressive how the DSP profile is wired into the UI and this is my next area of investigation.

 

 

 

 

 

 

 

• Facebook
• Twitter
• LinkedIn

5 comments

• 0
  
  Edward Archibald December 19, 2022 17:49

  P.S. I just tried another reboot and everything seems to be working as expected!  Let's see if it persists...

• 0
  
  HiFiBerry team December 20, 2022 07:58

  Just FYI: You don't need to create a new DSP profile to switch channels. This can be done in the UI. You can map each output channel to left/right/mono

• 0
  
  Edward Archibald December 22, 2022 14:46

  Thanks for the tip!  Of course!  

  I'm still having problems with using my own customized profile. I have two issues:

  - as mentioned in the original post, immediately after a 'cold' start i.e. from power off to on, I get no output from the analog or digital outputs.  I found that if I 'kick' it by executing the 'dsptoolkit check-eeprom' command that I get a few loud clicks and then audio commences.  Not sure where to look in my profile, or elsewhere, for the issue. The output of this command also confirms that my custom profile is the one that's loaded.

  - If I install the profile from within the UI, the channels are still not swapped as expected even though the install appears to have worked. If I install the same profile from 'dsptoolkit install-profile' I hear that the channels are swapped as expected.

  I still have some learning to do vis-a-vis what the default profile (dacdsp-12.xml) does/can do etc. so will stick with this profile until/if I hit a major roadblock.

  Thanks a lot for your support!  Much appreciated.   

   

   

   

• 0
  
  HiFiBerry team December 22, 2022 16:41

  I can only guess what might be the problem in your DSP profile. One thing you need to check is that the SPI programming speed is set to 1MHz (instead of the 10MHz default setting).

  If you install a DSP profile via the UI all settings form the UI will also be applied. Therefore, make sure, you set the channel mapping correctly in the UI.

• 0
  
  Edward Archibald December 22, 2022 23:40

  Thanks for the response. On the SPI programming speed, I think you must be referring to the 'Write Speed' on the EEPROM Settings dialog box in SigmaStudio? Otherwise, I would think that the SPI programming speed is set somewhere in the SigmaServer environment on the Pi.  If it is the 'Write Speed', the default value is, indeed 10000 kHz and this is also what is shown as the correct setting in the Hifiberry documentation.  If it's supposed to be 1000 kHz (1 mHz) you will want to update those images. I'll try this out tomorrow with the 1000 kHz setting and see how it goes. Fingers crossed!