0

HifiBerryOS 20191121 and REW TosLink

Tato Brutto

December 04, 2019 14:01

None

Follow

Hello,

I have a Beocreate board since a couple of week and I have some questions/comments to post here.

Using the last HifiBerryOS (version 20191121) I could not apply REW filters because of errors in the Python code of dsptoolkit. I’m using REW version 5.19. If you apply  the suggested profile “fullrange-extended.xml” (I could not find it anymore so I used another one following the forum) Toslink  input is disabled. I need the Toslink input otherwise I cannot connect the external computer running REW. Am I missing something?

I would be nice if the most common program/profile for the DSP can be applied using the web interface. With the new HifiBerryOS I saw there are two program for DSP in the web interface. Very nice J. However, for one of them Toslink is disabled and I am not sure if these programs are compatible or dangerous to use with REW filters. Doc are missing or not easily reachable.

I would kindly suggest a better organization of the documents/guides in order to maintain everything updated with the software releases (a kind of wiki). Some old article/information I found are now wrong and they just confuse users. I think Beocreate is very versatile and powerful (but not cheap), it deserves a better documentation.

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  HiFiBerry team December 04, 2019 14:17

  Hi,

  thanks for the feedback. While we try to keep documentation updated, it's always possible that some stuff is outdated. You can edit these on Github and just send a Pull request if you see something that should be corrected.
  
  If you install a profile with TOSLink support (you can simply use the default profile supplied with HiFiBerryOS), you can enable the Toslink input under "Sources".

  We also are not able to provide documentation for any possible feature. In contrast to other DSP products on the market, our system is completely programmable. We do not limit what can be implemented with it. Unfortunately, this comes with some complexity. Pre-configured DSP profiles are our way to provide basic functionality without the need to understand the internals. For advanced projects, you might still need to create your own DSP profile using SigmaStudio. Feel free to ask if you're missing a specific part of the documentation. 

  We are working on a room equalisation tool by ourself that will be integrated at some point, but this still needs some work, especially to make it user-friendly in the UI.

  The dsptoolkit bug will be fixed in the next HiFiBerryOS release expected in 2-3 weeks.
  
  Best regards,
  Daniel
  
  

• 0
  
  Tato Brutto December 04, 2019 16:03

  Thanks for the fast and informative reply. It nice to know you are working on a Room equalization tools. At least for the most common scenarios doc and easy-to-use tool (as you did with crossover) will spread the audience and raise the value of the board.

  If I understood correctly, when the dsptoolkit bug will be fixed, I can use the default HiFiBerryOS’s profile and apply the REW filters to it. Is it correct?

  Kindly regards

• 0
  
  HiFiBerry team December 04, 2019 16:20

  Yes, that's correct. The applay-rew-filters command check the metadata of the profile for an IIR filter bank. As long as this exists, dsp-toolkit will apply the filters. This also means you can create your own DSP profile and still use this feature.

  Best regards,
  Daniel