0

[DAC+ DSP] Profile v13 doesn't recognize TOSLINK input

Nobumasa

February 24, 2023 07:05

None

Follow

Thanks to the new v13 profile, the DAC+ DSP's self-boot finally runs appropriately.

But, there seems to be another issue the TOSLINK input is not detected with the v13 profile mentioned in the blog article.
With the v12-1 included in the hifiberry-dsp repo, I can use TOSLINK input, including the LG Sound Sync feature, but with the v13, it reports "no signal" in the exact same connections. Sound Sync doesn't work, of course.
It's happening in the latest HifiberryOS, but I confirmed that there's the same issue in the RasberryPi OS+hifiberry DSP toolkit.

I suppose it's not a hardware issue but an issue around DSP registers, but I don't know how to fix it. I don't even know whether it's an issue or the design. Maybe there's no issue with the DSP add-on.

Didn't all of you get the same issue with the v13 profile?

• Facebook
• Twitter
• LinkedIn

8 comments

• 0
  
  cube February 26, 2023 15:45

  Hi there,

  first time I used the HiFiBerryOS and must say - wow! I used to have my own implementation but this is so much better!

  As Nobumasa mentioned, the TOSLINK input is also not working for me (Status - not active). When I use V12 it works but then the Listening modes can not be changed.

   

• 0
  
  cureren_carpels02 February 27, 2023 07:40

  Hello there,

  I have the same problem with the new profile: optical input is no longer working with V13. When I loaded V12 I received a warning that the sampling rate was not specified and that it would not be possible to control filters.
  Everything seems to work fine with V12. I have two sets of filters loaded based room compensation profiles created in REW and can easily switch these on and off. And optical input is also functioning as expected and the audio is routed to the dsp and filtered as intended.

  t would be nice to know what has been fixed in V13 and if this is also relevant to current users?
  Are the way filters are implemented different in V12 and V13 and does this mean I will need to do my measurements again?
  Are there plans to fix the optical input again in a next version?

  Kind regards,

  Bram

• 0
  
  HiFiBerry team February 27, 2023 13:57

  We'll look into this. As  the release note say: DSP v13 is an update to ensure compatibility with the latest DAC+DSP hardware. If your DSP works fine with v12, there is no need to update.
  
  BTW: You should report bugs in our bug reporting system on Github:
  https://github.com/hifiberry/hifiberry-os/issues

• 0
  
  cureren_carpels02 March 01, 2023 12:42

  Thanks for the reply. And keep up the good work. The DAC+DSP together with Hifiberry OS are a really great and powerful product that make a massive difference in my living room and help fix some really nasty room modes. I can file a bug report if this is helpful for you.

  Kind regards,

  Bram

• 0
  
  Bob Moss March 15, 2023 10:25

  I've reported this on GitHub today as it looks like no-one else has officially reported it yet.

• 0
  
  Bob Moss March 16, 2023 14:13

  And just to add to this, I've just tried running room measurement using my new DAC+ DSP module and DSPv12 and I get the error "Problem with sound processor, Room compensation filters can't be used because there is a problem with the current DSP program. Known sampling rate and support for parametric equaliser (Sound Design) are required."
  I guess that error is down the the "Sampling rate not specified" error when selecting DspV12.

  So at the moment I can either have TOSLink input OR room compensation. So this needs fixing quickly please!

   

• 1
  
  HiFiBerry team March 17, 2023 08:13

  You can simply edit the v12 DSP profile and change the word "samplerate" to "sampleRate". Then reboot and the system should be able to get the sample rate correctly.

• 0
  
  Bob Moss March 17, 2023 10:53

  Excellent, I'll give that a go. Thanks.