Save Sigma Studio settings correctly

Sven

September 20, 2018 17:39

None

Hey Everybody,

I ordered the beocreate board a few days ago and today I was finally able to try it.

Setting up with the BO software ran smoothly and thank you to the Beocreate team for the hardware and software.

Unfortunately it was not possible for me to save my own setting with the Sigma Studio software.

For this I used and adapted the 2-way eq setting offered from the beocreate team.

I just wanted to use a simple crossover, all over 80 Hz to the outputs CH1 and CH0 and below 80Hz to CH16 / 17.

Everything is saved as it is explained in the videos.
The problem is, that Beocreate now only makes a very quiet outcome on the CH1. On CH0 a "normal" loud and not crossover effected signal comes out.
CH16 is mute
and at CH17 comes out a soundlevel beyond good and evil.

The jumper 4 and 5 are removed on the board.

As a test I removed the selfboot jumper and re-saved everything which did not help.

My question:

How are the settings of Sigma Studio saved correctly?

I also followed this guide:
https://www.hifiberry.com/beocreate/beocreate-doc/beocreate-use-sigmastudio/

However, it is not quite clear to me how I have to deal with the selfboot jumper?

Does this have to be removed while working in Sigma?

thank you for your help

Date Votes

39 comments

0

HiFiBerry team September 20, 2018 17:49

Hi,

you can leave the selfboot jumper plugged. You should not remove it. Unfortunately I can't say what might be the problem with your specific profile.

As SigmaStudio is quite complex to use, we have prepared a profile that can be configured using the new "dsptoolkit" software:

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

First you need to exchange the existing beocreate tcp server by the new dsptoolkit, then you can deploy a profile with it and configure crossovers as shown in the documentation linked above.

Best regards,
Daniel

Comment actions Permalink
0

Sven September 20, 2018 19:45

HI Daniel,

i tried to activated the profile but i got an failure!

dsptoolkit install-profile 4way-iir.xml

^CTraceback (most recent call last):

File "/usr/local/bin/dsptoolkit", line 7, in <module>

cmdline.main()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 837, in main

self.command_map[self.args.command]()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 628, in cmd_install_profile

res = self.dsptk.install_profile_from_content(data)

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 277, in install_profile_from_content

return self.sigmatcp.write_eeprom_from_xml(content)

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/client/sigmatcp.py", line 131, in write_eeprom_from_xml

result = int.from_bytes(self.socket.recv(1),

KeyboardInterrupt

I hope you can help me.

Many thanks

Sven

Comment actions Permalink
0

HiFiBerry team September 21, 2018 04:07

Is the correct daemon running? What is the output of

systemctl status sigmatcp

Best regards,
Daniel

Comment actions Permalink
0

Sven September 21, 2018 18:36

so i tried my best but all i got is this:

root@lol:/home/pi# systemctl status sigmatcp

Unit sigmatcp.service could not be found.

root@lol:/home/pi# sigmatcpserver --alsa

INFO:root:running as root, data will be stored in /var/lib/hifiberry

Traceback (most recent call last):

File "/usr/local/bin/sigmatcpserver", line 16, in <module>

server = hifiberrydsp.server.sigmatcp.SigmaTCPServerMain()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/server/sigmatcp.py", line 680, in __init__

self.server = SigmaTCPServer()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/server/sigmatcp.py", line 666, in __init__

TCPServer.__init__(self, server_address, RequestHandlerClass)

File "/usr/lib/python3.5/socketserver.py", line 440, in __init__

self.server_bind()

File "/usr/lib/python3.5/socketserver.py", line 454, in server_bind

self.socket.bind(self.server_address)

OSError: [Errno 98] Address already in use

root@lol:/home/pi# /home/pi/create/SigmaTcpDaemon/sigmaTcpDaemon

Error starting TCP server: failed to bind socket

Friendly Regards

sven

Comment actions Permalink
0

HiFiBerry team September 21, 2018 18:44

Looks like the new DSP toolkit server isn't installed correctly at all. Did you use the install script?

Please run the following:

ps -ef | grep -i tcp

Best regards,
Daniel

Comment actions Permalink
0

Sven September 21, 2018 18:53

Hi Daniel,

yes i used the install script.

and as result i got:

pi@lol:~ $ ps -ef | grep -i tcp

root 639 1 0 17:06 ? 00:00:00 /home/pi/create/SigmaTcpDaemon/sigmaTcpDaemon

pi 1520 1495 0 18:49 pts/0 00:00:00 grep --color=auto -i tcp

pi@lol:~ $ sudo su

root@lol:/home/pi# sudo pip3 install --upgrade hifiberrydsp

Requirement already up-to-date: hifiberrydsp in /usr/local/lib/python3.5/dist-packages

Requirement already up-to-date: spidev in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: pyalsaaudio in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: xmltodict in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: lxml in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: zeroconf in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: ifaddr in /usr/local/lib/python3.5/dist-packages (from zeroconf->hifiberrydsp)

Requirement already up-to-date: ipaddress in /usr/local/lib/python3.5/dist-packages (from ifaddr->zeroconf->hifiberrydsp)

root@lol:/home/pi#

With regards

sven

Comment actions Permalink
0

HiFiBerry team September 21, 2018 18:58

First of all you need to remove the original SigmaTcpDaemon. Remove the file that starts this from /etc/init.d/beocreate-4ch and reboot. Check that it is not running anymore after this.

Then run the dsptoolkit installer again and post the output here.

Best regards,
Daniel

Comment actions Permalink
0

Sven September 21, 2018 19:30

Hi Daniel,

here my results:

# Start SigmaDSP daemon:

# echo "Starting SigmaDSP daemon..."

# /home/pi/create/SigmaTcpDaemon/sigmaTcpDaemon > /dev/null &

and

pi@lol:~ $ ps -ef | grep -i tcp

pi 823 763 0 19:24 pts/0 00:00:00 grep --color=auto -i tcp

pi@lol:~ $ systemctl status sigmatcp

Unit sigmatcp.service could not be found.

pi@lol:~ $ sudo pip3 install --upgrade hifiberrydsp

Requirement already up-to-date: hifiberrydsp in /usr/local/lib/python3.5/dist-packages

Requirement already up-to-date: zeroconf in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: pyalsaaudio in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: spidev in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: lxml in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: xmltodict in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)

Requirement already up-to-date: ifaddr in /usr/local/lib/python3.5/dist-packages (from zeroconf->hifiberrydsp)

Requirement already up-to-date: ipaddress in /usr/local/lib/python3.5/dist-packages (from ifaddr->zeroconf->hifiberrydsp)

pi@lol:~ $ dsptoolkit servers

Looking for devices

Regards

Sven

Comment actions Permalink
0
HiFiBerry team September 21, 2018 19:40
Ok, I see that you only installed the Python module. This is ok, but you don't have the daemon enabled in this case.
The easiest way to also install the start scripts is the install tool:
```
bash <(curl https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/install-dsptoolkit)


Best regards,
Daniel
```
Comment actions Permalink
0

Sven September 21, 2018 20:29

Hi Daniel,

yes thats helps to install the dsptoolkit. (dsptoolkit install-profile 4way-iir.xml)

so now i can write an profile to the dsp.

i tried the hifiberry example just for fun:

IIR_L1: lp:2000Hz

IIR_L2: mute

IIR_L3: hp:2000Hz

IIR_L4: mute

IIR_R1: mute

IIR_R2: lp: 2000Hz

IIR_R3: mute

IIR_R4: hp: 2000Hz

an then the speakers sound terrible.

i played with different frequencies and hp or lp but the speakers always sounds the same.

it seems that right now my profile have no effect on the dsp?!

is there anything i can test?

Mit freundlichen Grüßen

sven

Comment actions Permalink
0

HiFiBerry team September 22, 2018 06:08

What exactly did you do to apply these settings? Please post your command line and the output.

Best regards,
Daniel

Comment actions Permalink
0

Sven September 22, 2018 10:57

Hi Daniel,

1. nano crossover.txt

2. copy and paste the filter setting from https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/crossovers.md

3. save with ctrl + O and closed crossover.txt with ctrl+X

4. dsptoolkit apply-settings crossover.txt

5. played music via airplay and its sounds like an smartphone in a tin can.

today i tried to edit the crossover.txt but after "dsptoolkit apply-settings crossover.txt" i got an error message:

can't parse XML profile

Friendly Regards

Sven

Comment actions Permalink
0

HiFiBerry team September 22, 2018 12:31

Just adding some filters can result in a horrible sound. Most likely you applies a LP filter to tweeters and a HP filter to the bass units.

The message "can't parse XML profile" tell you, that either no DSP profile is downloaded to the DSP or the DSP profile in the DSP doesn't fit the XML profile.

Run "dsptoolkit check-eeprom".

My guess is that you did not install a profile or there was a problem when installing the profile.

Best regards,
Daniel

Comment actions Permalink
0

Sven September 29, 2018 16:14

Hi Daniel,

Today I had time to take care of the Beocreate again.
Unfortunately, no sound came from the board.

As result for the Eeprom:

pi@lol:~ $ dsptoolkit check-eeprom

Traceback (most recent call last):

File "/usr/local/bin/dsptoolkit", line 7, in <module>

cmdline.main()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 837, in main

self.command_map[self.args.command]()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 662, in cmd_check_eeprom

self.dsptk.reset()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/dsptoolkit.py", line 295, in reset

self.sigmatcp.reset()

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/client/sigmatcp.py", line 303, in reset

int_data(1, self.dsp.REGISTER_WORD_LENGTH))

File "/usr/local/lib/python3.5/dist-packages/hifiberrydsp/client/sigmatcp.py", line 100, in write_memory

self.socket.send(packet)

BrokenPipeError: [Errno 32] Broken pipe

Do you know what this mean?

Regards

Sven

Comment actions Permalink
0

HiFiBerry team September 29, 2018 16:48

Hi Sven,

this means the the server isn't running. Check the output of systemctl status sigmatcp

Best regards,
Daniel

Comment actions Permalink
0

Sven September 29, 2018 17:28

pi@lol:~ $ systemctl status sigmatcp

● sigmatcp.service - SigmaTCP Server for HiFiBerry DSP

   Loaded: loaded (/lib/systemd/system/sigmatcp.service; enabled; vendor preset:

   Active: active (running) since Sat 2018-09-29 16:52:17 UTC; 34min ago

Main PID: 566 (sigmatcpserver)

   CGroup: /system.slice/sigmatcp.service

   └─566 /usr/bin/python3 /usr/local/bin/sigmatcpserver --alsa

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

Sep 29 17:26:07 lol sigmatcpserver[566]: ERROR:root:Got incorrect write request,

lines 1-17/17 (END)

Comment actions Permalink
0

HiFiBerry team September 29, 2018 17:31

That looks very strange. Almost as there is an older version of either the client or server running.

Try installing the latest version:
sudo pip3 install --upgrade hifiberrydsp

Then reboot and try again.

Best regards,
Daniel

Comment actions Permalink
0

Sven September 29, 2018 17:40

Hi Daniel,

still not running

pi@lol:~ $ systemctl status sigmatcp

● sigmatcp.service - SigmaTCP Server for HiFiBerry DSP

   Loaded: loaded (/lib/systemd/system/sigmatcp.service; enabled; vendor preset: enabled)

   Active: active (running) since Sat 2018-09-29 17:37:24 UTC; 1min 5s ago

Main PID: 549 (sigmatcpserver)

   CGroup: /system.slice/sigmatcp.service

   └─549 /usr/bin/python3 /usr/local/bin/sigmatcpserver --alsa

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

Sep 29 17:38:04 lol sigmatcpserver[549]: ERROR:root:Got incorrect write request, length < 14 bytes

pi@lol:~ $

Regards

Sven

Comment actions Permalink
0

HiFiBerry team September 30, 2018 06:24

Do you still get an error message when running

dsptoolkit check-eeprom

Try something else:

dsptoolkit get-xml
dsptoolkit servers

Best regards,
Daniel

Comment actions Permalink
0

Duncan October 01, 2018 09:37

I can comment that after about a month of waiting for new kit to arrive (Amp was off, unplugged during that time), assembling a new speaker and trying to get some sound out I had exactly the same issue as above "can't parse XML profile".

I don't understand why it would stop working after being unplugged for a period of time. the speakers 'ticked' when turning amp on/off and I couldn't even play a sine wave so assumed it was a DSP programming error.

Only way I could get some sound via airplay like this "5. played music via airplay and its sounds like an smartphone in a tin can." was to sudo update, upgrade, reinstall using your script, new 4way-default.xml

Cant set or get volume "profile doesn't support volume control"

Cant write crossover.txt (as per above error)

check eeprom results in 'current profile is the one that's loaded' message with a checksum

servers finds the server running as it used to, expected

Ill work through the above recommendations and see if I end up at a different place, otherwise only option is to start from scratch... I see Max2Play has an option for profiles so that might be a new direction to try and assume

Comment actions Permalink
0

HiFiBerry team October 01, 2018 09:42

Hi Duncan,

if dsptoolkit tells your that the profile doesn't support volume control, most likely you have installed your own profile with SigmaStudio. Is that right? Otherwise, what profile did you install?

Best regards,
Daniel

Comment actions Permalink
0

Duncan October 01, 2018 09:57

Hi,

I tried both of the following, they both give the same error so I assumed something has changed in either the profile or the way the server reads the XML:

https://github.com/hifiberry/hifiberry-dsp/blob/master/sample_files/xml/4way-default.xml

https://github.com/hifiberry/hifiberry-dsp/blob/master/sample_files/xml/4way-iir.xml

I have given up for now playing with Sigma, its too sensitive and the method of the new server is all I require for now.

When I did the upgrade I recall an upgrade going from 0.12 to 0.13.1 or something similar. Was late last night!

D

Comment actions Permalink
0

HiFiBerry team October 01, 2018 10:01

Ok, now it makes sense. There is still the profile active that you've deployed directly with SigmaStudio. Looking at the URLs you've posted, none of these will work as these URL won't serve the plain XML profile, but an HTML page. DSPToolkit can't handle this. You need to use the URL with the raw profile, e.g.:

dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-default.xml

Best regards,
Daniel

Comment actions Permalink

Duncan October 01, 2018 10:28

Sorry, I didn't explain what I did. Above post I just copied the link on the website to direct you to what profile I used. The code I ran was:

dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-default.xml

AND

dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml

0

HiFiBerry team October 01, 2018 11:13

Ok, please try that again and post the output of this command.

Best regards,
Daniel

Comment actions Permalink
0

Duncan October 01, 2018 15:43

"DSP profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-default.xml installed"

Comment actions Permalink
0

Duncan October 01, 2018 15:47

pi@livingroom:~ $ dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_file s/xml/4way-default.xml
DSP profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-default.xml installed
pi@livingroom:~ $ dsptoolkit apply-settings crossover.txt
can't parse XML profile
pi@livingroom:~ $ dsptoolkit
usage: dsptoolkit [-h] [--delay DELAY] [--host HOST]
{apply-fir-filter-left,apply-fir-filter-right,apply-fir-filters,apply-rew-filters,appl y-rew-filters-left,apply-rew-filters-right,apply-settings,check-eeprom,clear-iir-filters,get-checksum,ge t-limit,get-meta,get-prog,get-samplerate,get-volume,get-xml,install-profile,load,loop-read-dec,loop-read -hex,loop-read-int,loop-read-reg,mute,read-dec,read-hex,read-int,read-reg,reset,save,servers,set-limit,s et-volume,store,store-filters,store-settings,unmute,version,write-mem,write-reg}
[parameters [parameters ...]]
dsptoolkit: error: the following arguments are required: command, parameters
pi@livingroom:~ $ dsptoolkit get-xml
None
pi@livingroom:~ $ dsptoolkit install-profile
profile filename missing
pi@livingroom:~ $ dsptoolkit check-eeprom
EEPROM content matches running profile, checksum A864F3AC2C7B30085E10DBECB145EE2D
pi@livingroom:~ $ dsptoolkit reset
Resetting DSP
pi@livingroom:~ $ dsptoolkit check-eeprom
EEPROM content matches running profile, checksum A864F3AC2C7B30085E10DBECB145EE2D
pi@livingroom:~ $ dsptoolkit get-xml
None
pi@livingroom:~ $ dsptoolkit get-volume
Profile doesn't support volume control
pi@livingroom:~ $ dsptoolkit set-volume 50
Profile doesn't support volume control
pi@livingroom:~ $

Comment actions Permalink
0

HiFiBerry team October 01, 2018 16:25

Hmm, looks like some bug in the TCPServer dsptoolkit.

try the install-profile again (and no other commands), then post the output of

systemctl status sigmatcp

Thank you
Daniel

Comment actions Permalink
0

Duncan October 01, 2018 16:30

OK, think I found some part of an error. It seems like something is not starting at boot? See below code I ran:

pi@livingroom:~ $ dsptoolkit get-volume
Profile doesn't support volume control
pi@livingroom:~ $ dsptoolkit store-settings crossover.txt
can't parse XML profile
pi@livingroom:~ $ bash <(curl https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/install-dsptoolkit)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 790 100 790 0 0 1733 0 --:--:-- --:--:-- --:--:-- 1732
Reading package lists... Done
Building dependency tree
Reading state information... Done
libxml2-dev is already the newest version (2.9.4+dfsg1-2.2+deb9u2).
libxslt1-dev is already the newest version (1.1.29-2.1).
zlib1g-dev is already the newest version (1:1.2.8.dfsg-5).
python3-pip is already the newest version (9.0.1-2+rpt2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Requirement already up-to-date: hifiberrydsp in /usr/local/lib/python3.5/dist-packages
Requirement already up-to-date: spidev in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)
Requirement already up-to-date: xmltodict in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)
Requirement already up-to-date: lxml in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)
Requirement already up-to-date: pyalsaaudio in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)
Requirement already up-to-date: zeroconf in /usr/local/lib/python3.5/dist-packages (from hifiberrydsp)
Requirement already up-to-date: ifaddr in /usr/local/lib/python3.5/dist-packages (from zeroconf->hifiberrydsp)
Requirement already up-to-date: ipaddress in /usr/local/lib/python3.5/dist-packages (from ifaddr->zeroconf->hifiberrydsp)
Removed /etc/systemd/system/multi-user.target.wants/sigmatcp.service.
mkdir: cannot create directory ‘/home/pi/.dsptoolkit’: File exists
Created symlink /etc/systemd/system/multi-user.target.wants/sigmatcp.service → /lib/systemd/system/sigmatcp.service.
pi@livingroom:~ $ dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml
DSP profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml installed
pi@livingroom:~ $ sudo nano crossover.txt
pi@livingroom:~ $ dsptoolkit store-settings crossover.txt
writing back updated DSP profile
DSP profile updated on server
pi@livingroom:~ $ dsptoolkit store-filters
writing back updated DSP profile
DSP profile updated on server
Stored filter settings
pi@livingroom:~ $ ^C
pi@livingroom:~ $ sudo reboot

THEN I ran this below and it seems the memory of the DSP/EEPROM has been lost?

pi@livingroom:~ $ dsptoolkit store-settings crossover.txt
can't parse XML profile
pi@livingroom:~ $ dsptoolkit servers
Looking for devices
livingroom._sigmatcp._tcp.local.: 127.0.1.1:8086 (version 0.13)
pi@livingroom:~ $ systemctl status sigmatcp
● sigmatcp.service - SigmaTCP Server for HiFiBerry DSP
Loaded: loaded (/lib/systemd/system/sigmatcp.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-10-01 16:19:34 UTC; 3min 30s ago
Main PID: 518 (sigmatcpserver)
CGroup: /system.slice/sigmatcp.service
└─518 /usr/bin/python3 /usr/local/bin/sigmatcpserver --alsa

Oct 01 16:19:34 livingroom systemd[1]: Started SigmaTCP Server for HiFiBerry DSP.
Oct 01 16:19:37 livingroom sigmatcpserver[518]: INFO:root:running as root, data will be stored in /var/lib/hifiberry
Oct 01 16:19:37 livingroom sigmatcpserver[518]: INFO:root:initializiong ALSA mixer control
Oct 01 16:19:37 livingroom sigmatcpserver[518]: INFO:root:reading profile /var/lib/hifiberry/dspprogram.xml
Oct 01 16:19:38 livingroom sigmatcpserver[518]: ERROR:root:couldn't find program end signature, something is wrong with the DSP program memory
Oct 01 16:19:38 livingroom sigmatcpserver[518]: ERROR:root:Can't calculate checksum from None
Oct 01 16:19:38 livingroom sigmatcpserver[518]: INFO:root:checksum memory: None, xmlfile: bytearray(b'\xa8d\xf3\xac,{0\x08^\x10\xdb\xec\xb1E\xee-')
Oct 01 16:19:38 livingroom sigmatcpserver[518]: ERROR:root:checksums do not match, aborting
Oct 01 16:19:38 livingroom sigmatcpserver[518]: INFO:root:Announcing via zeroconf
Oct 01 16:19:38 livingroom sigmatcpserver[518]: INFO:root:Starting TCP server
pi@livingroom:~ $ dsptoolkit check-eeprom
EEPROM content matches running profile, checksum A864F3AC2C7B30085E10DBECB145EE2D
pi@livingroom:~ $ dsptoolkit get-xml
None

Comment actions Permalink
0

Duncan October 01, 2018 16:33

To your previous posted question:

pi@livingroom:~ $ dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml
DSP profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/4way-iir.xml installed
pi@livingroom:~ $ systemctl status sigmatcp
● sigmatcp.service - SigmaTCP Server for HiFiBerry DSP
Loaded: loaded (/lib/systemd/system/sigmatcp.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-10-01 16:19:34 UTC; 13min ago
Main PID: 518 (sigmatcpserver)
CGroup: /system.slice/sigmatcp.service
└─518 /usr/bin/python3 /usr/local/bin/sigmatcpserver --alsa

Oct 01 16:32:20 livingroom sigmatcpserver[518]: 00 00 00 82 0E 00 DA C0 00 00 00 82 1F 01 8E 06 08 13 0E 06 18 40 31 F1 6C 80 01 88 00 01 22 FC 6C 80 21 81 82 04 23 03 03 01 E5 FD 74 A2 05 81 80 01 25 E0
Oct 01 16:32:20 livingroom sigmatcpserver[518]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 01 16:32:20 livingroom sigmatcpserver[518]: 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
Oct 01 16:32:20 livingroom sigmatcpserver[518]: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 01 16:32:20 livingroom sigmatcpserver[518]: drIncr="4" len="1106" addr="24576" ParamName="DM1 Data" DspName="IC 1">00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
Oct 01 16:32:20 livingroom sigmatcpserver[518]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 01 16:32:20 livingroom sigmatcpserver[518]: </action>\n\t\t<action instr="writeXbytes" AddrIncr="0" len="4" addr="62464" ParamName="IC 1.HIBERNATE" DspName="IC 1">00 00</action>\n\t</page>\n</ROM>\n'
Oct 01 16:32:20 livingroom sigmatcpserver[518]: INFO:root:preparing for memory update
Oct 01 16:32:37 livingroom sigmatcpserver[518]: INFO:root:finished memory update
Oct 01 16:32:37 livingroom sigmatcpserver[518]: INFO:root:caching program memory checksum

Comment actions Permalink

Please sign in to leave a comment.