We just released a new version of the dsptoolkit to work with our DSP boards, e.g. to change settings, create crossovers, apply room equalisation filters and much more.
The software can be found here:
https://github.com/hifiberry/hifiberry-dsp
Post your feedback, questions, suggestions here.
Note that if you still have the "old" SigmaTCPDaemon installed, you need to remove it first as the DSPToolkit replaces the old server.
Hi,
If we do a fresh install of Beocreate will the new DSPtoolkit server be pulled during install?
Thanks
Duncan
Hi,
not yet. The Beocreate installation script needs to be changed for this. As it is vacation time, it will still take some time.
Best regards,
Daniel
Hi Daniel,
I ran the script on Github and it all seemed to work with no errors but the new port seems not active and the old server is still active?
Should I remove the old one first? If so, how?
Thanks
Duncan
Yes, it is using the same port as the old one. Do you use the Beocreate image?
Best regards,
Daniel
Ah, ok. The readme indicates it uses 8089 and the old one is using 8086, so that answers that question.
Yes, I started off with the beocreate image then used the CX50 profile and tweaked the equalization to suit my DML speakers & added a crossover filter.
How do I know the new server is running and not the old one? I ask this because I still get an "AA" error when checking the EEPROM has written correctly as well as still having the kernel panic error.
Duncan
Hi,
forgot the "verification" feature of SigmaStudio. That doesn't work reliably. SigmaStudio sometimes does mess up when reading larger amount of data. I also recommend NOT to read back register values as this can easily break a working project.
If you haven't disabled the old daemon, it will still be running. You have to comment it out in /etc/init.d/beocreate-4ch
To check if the progam in the EEPROM is the one that is currently running, then run
dsptoolkit check-eeprom
Best regards,
Daniel
Hi Daniel,
Great work on this new release. Finally managed to get some time last night to play and its much easier to tweak settings this way than use Sigma software. Even managed to get a quick EQ in to test.
1 - I assume the EEPROM jumper doesn't need to be removed when running the "store-filters" command? It seems to work without fiddling with the jumpers?
2 - Is there a way to run a band pass in the cross over instead of only a hp or lp?
3 - If I wanted to run Volumio, could I do a fresh install of Volumio, SSH in, install DSPToolKit and all would work ok including programming DSP still? Or is it easier to have two SD cards, one for programming and one for Volumio?
Thanks!
Hi,
1. You don't need to fiddle around with the jumper
2. A band pass is just a combination of a HP and a LP. Just use a HP AND a LP to implement a bandpass
3. In general DSPToolkit should also work on other distributions, but it hasn't been tested.
Best regards,
Daniel
Hi Daniel,
So everything was going well. I even managed to program some REW filters which is great!
I saved a "filters2.txt" and a "filters.txt" so i could flip between the two and hear the difference which worked yesterday. I tried today and the moment I write the "filters2.txt" the DSP loses its 'ish and makes super high frequency police siren type noises!!! Only way to silence it is to issue a dsptoolkit reset or manage to get close enough to unplug. Not cool!
Something seems very unstable in the DSP still and have no idea where to start debugging.
I have noticed in the past (when I was fiddling with Sigma) that if a Pk filter gain is set out of range the same thing happens. What I don't understand is why it didn't happen yesterday. I edited the filters file and changed all gains to 0 and all Q's to 1 and it didn't scream at me so I assume the config file is pushing the DSP out of its bounds.
What is the limit ITO gain & Q that can be applied?
D
Hi,
it might still be a bug in the software. There aren't many users of this yet. We haven't had a lot of feedback, so it's likely that there are still bugs. Can you post the problematic filter configuration?
Best regards,
Daniel
Hi Daniel,
This is what originally worked then stopped working below. I have a suspicion it might have something to with volumes IE if the DSP tries to level too far, like filter 3 for example. But this would need to tie up to the input volume to cause a problem as it sometimes works and somethings doesn't. Perhaps the Q is also being pushed out of allowable limits.
Filter Settings file
Room EQ V5.18
Dated: 23 Aug 2018 8:23:20 PM
Notes:
Equaliser: Generic
Aug 23 20:21:39
Filter 1: ON PK Fc 5990 Hz Gain 9.0 dB Q 1.23
Filter 2: ON PK Fc 3610 Hz Gain -15.3 dB Q 3.46
Filter 3: ON PK Fc 12530 Hz Gain -17.5 dB Q 3.24
Filter 4: ON PK Fc 700 Hz Gain -5.4 dB Q 2.74
Filter 5: ON PK Fc 10764 Hz Gain 9.0 dB Q 5.00
Filter 6: ON PK Fc 146 Hz Gain 9.0 dB Q 5.15
Filter 7: ON PK Fc 70.1 Hz Gain -7.0 dB Q 4.31
Filter 8: ON PK Fc 5718 Hz Gain -7.7 dB Q 5.00
Filter 9: ON PK Fc 13188 Hz Gain 8.4 dB Q 4.86
Filter 10: ON PK Fc 47.3 Hz Gain -9.9 dB Q 7.07
Filter 11: ON PK Fc 5437 Hz Gain -6.3 dB Q 5.00
Filter 12: ON PK Fc 194 Hz Gain -8.2 dB Q 6.42
Filter 13: ON PK Fc 2474 Hz Gain -5.9 dB Q 5.00
Filter 14: ON PK Fc 1746 Hz Gain -3.7 dB Q 5.00
Filter 15: ON PK Fc 140 Hz Gain -8.0 dB Q 12.51
Filter 16: ON PK Fc 7425 Hz Gain -1.5 dB Q 5.00
Filter 17: OFF None
Filter 18: OFF None
Filter 19: OFF None
Filter 20: OFF None
I will check this file.
In general it looks like you're trying to flatten your frequency response extremely. Corrections of 9-15dB should not be necessary with any speaker - except in the low frequencies. Filters also come with a cost. While a filter can flatten the frequency response, it will have an impact on phase. A speaker with linear frequency response, but lots of phase changes might sound worse than before.
Therefore I would recommend to correct to +/-3dB. Also flatten measured response before calculating filters.
Room acoustics problems are usually in the low frequencies. So correcting the frequency range of 20-200Hz is most important.
Best regards,
Daniel
Hi Hifiberry team,
I had to do: sudo chmod +x /opt/hifiberry/bin/spotifyd-notification
as spotifyd was crashing with permission denied errors when trying to trigger playback from the Spotify app. Now works correctly - I wonder if there is an issue here? https://github.com/hifiberry/beocreate-tools/blob/3c15f1cda4281a056388a03378374b69a11cf5e8/install-spotify#L88
Thanks,
Richard
Hi all
After getting over some initial difficulties, I finally got my 4ch amp output some sound, following this thead: https://support.hifiberry.com/hc/en-us/community/posts/115003763105-Guided-setup-does-not-start, using these commands:
":/home/pi/create/SigmaClientTool# ./SigmaClientTool 127.0.0.1 write_eeprom /home/pi/dsp/basic-fullrange.xml
Initializing connection to 127.0.0.1
Writing /home/pi/dsp/basic-fullrange.xml to EEPROM
SUCCESS
:/home/pi/create/SigmaClientTool# aplay /home/pi/Music/startup.wav
Wiedergabe: WAVE '/home/pi/Music/startup.wav' : Signed 16 bit Little Endian, Rate: 44100 Hz, stereo"
In order to setup the beocreates for my 3-way speakers, I thought dsptoolkit would be handy, especially starting off "/home/pi/hifiberry-dsp-master/doc/crossovers.md". So I tried:
"dsptoolkit install-profile /home/pi/hifiberry-dsp-master/sample_files/xml/4way-iir.xml"
But this takes forever and the "SUCCESS" message as when writing "basic-fullrange.xml" using "SigmaClientTool" never shows.
Any hint what I did wrong?
Greez
chris
Hi Christoph,
I guess, you still have the old SigmaTcpServer running that is not compatible with most functions of the new dsptoolkit.
You need to upgrade the TCPServer to the one that comes with DSPToolkit. What distribution are you using?
Best regards,
Daniel
Hi Daniel
I am using raspian. How do I replace the TCPServer with the one that comes with DSPToolkit?
Greez
Chris
Daniel
By the way, I installed based on this guide: "https://www.hifiberry.com/beocreate/beocreate-doc/beocreate-installing-the-sigmatcpserver/" using the section titled "Simple installation on Raspbian".
Greez
Chris
Hi,
if you use our setup script, it will install the server automatically. However, if the old server is still running, it won't start as both will try to listen to the same TCP port.
What's the output of
systemctl status sigmatcp
Best regards,
Daniel
Daniel
":/home/pi/hifiberry-dsp-master/sample_files/xml# systemctl status sigmatcp
● sigmatcp.service - SigmaTCP Server for HiFiBerry DSP
Loaded: loaded (/lib/systemd/system/sigmatcp.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-09-03 13:24:51 UTC; 2s ago
Process: 23461 ExecStart=/usr/local/bin/sigmatcpserver --alsa (code=exited, status=1/FAILURE)
Main PID: 23461 (code=exited, status=1/FAILURE)
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/server/sigmatcp.py", lin
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: TCPServer.__init__(self, server_address, RequestHandlerClass)
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: File "/usr/lib/python3.5/socketserver.py", line 440, in __init__
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: self.server_bind()
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: File "/usr/lib/python3.5/socketserver.py", line 454, in server_bind
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: self.socket.bind(self.server_address)
Sep 03 13:24:51 beocreate-4ch-blank sigmatcpserver[23461]: OSError: [Errno 98] Address already in use
Sep 03 13:24:51 beocreate-4ch-blank systemd[1]: sigmatcp.service: Main process exited, code=exited, status=1/FAILURE
Sep 03 13:24:51 beocreate-4ch-blank systemd[1]: sigmatcp.service: Unit entered failed state.
Sep 03 13:24:51 beocreate-4ch-blank systemd[1]: sigmatcp.service: Failed with result 'exit-code'."
I am puzzled with "OSError: [Errno 98] Address already in use". If I do "systemctl start sigmatcp" and then again "systemctl status sigmatcp", I get the same result.
Greez
chris
Daniel
I have the demon running now. All I had to do is comment out the line
" /home/pi/create/SigmaTcpDaemon/sigmaTcpDaemon > /dev/null &"
in "/etc/init.d/beocreate-4ch", which you already indicated above ( I overread that, sorry)
" # Start SigmaDSP daemon:
echo "Starting SigmaDSP daemon..."
# /home/pi/create/SigmaTcpDaemon/sigmaTcpDaemon > /dev/null &
"
greez and thanks so far for patience and support
chris
Hi Daniel, could you please confirm the expected format for 'value':
dsptoolkit write-reg address value
https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/dsptoolkit.md
I can read the address successfully using:
dsptoolkit read-hex address
but write-reg doesn't seem to change anything.
Other functions (eg. volume control) seem to work fine.
Thanks!
Richard
For registers, value is just an integer value. Note that not all registers of the DSP are writeable, some are read-only and you won't be able to change these.
Best regards,
Daniel
Thanks! Is there any way to determine whether a register will be read-only?
It's in the data sheet. In general you should not write to registers at all. This needs a good know-how of the internals of the DSP. You should not need it.
My guess is, that you want to write to the data memory instead. What exactly do you want to do?
Best regards,
Daniel
Perhaps writing to data memory is what I need to do. I adapted this guide: https://www.hifiberry.com/modify-dsp-registers-on-the-fly/ to the new dsptoolkit based on the instructions on github - but now I realize that write_val in the old guide must be equivalent to write-mem in the new system?
I'm trying to use the RPi to switch between equalizer pathways using a muxing block in the DSP.
Thanks for your assistance!
yes, it's write-mem
Best regards,
Daniel
Hi all
Playing with SigmaStudio got me going rather quick in order to setup a threeway crossover with delay for the woofer. I would now like to move on with some room equalisation stuff. That's wher I think dsptoolkit comes handy. Is it possible to add rew filters to a SigmaStudio created profile?
Greez
chris
There are two ways:
- you add these directly in SigmaStudio by hand
- you create a DSP profile, deploy it with dsptoolkit and manage the filters with dsptoolkit
The second approach takes a bit more work, but it is easier to manage in the long run.
Check out how to create a DSP profile here:
https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/dspprofiles.md
You can also use an existing DSP profile and apply your filters on this:
https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/crossovers.md
Best regards,
Daniel
Hi all
Looks like my wish is already covered and confirmed/described in /doc/dspprofiles.md: GREAT!
In that file it is said:
"There are some specific functions that can be controlled later by
dsptoolkit:
- Volume - controls the output volume
- VolumeLimit - controls the maximum volume
- Balance - a DC source with a value of 0-2
- Mute - a switch to mute the output
- IIR_L, IIR_R - 2 IIR filter banks to apply equalisations to left and
right channels
- IIR_L1,IIR_L2,IIR_L3,IIR_L4, IIR_R1,IIR_R2,IIR_R3,IIR_R4 -
a mixer/equalisation matrix to implement crossovers
"
What I miss here, are delays. Does that mean, delays can't be set througg dsptoolkit?
greez
chris