-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
I just upgraded to the newest version and I am observing strange effects when trying to install a new profile:
pi@hifiberry:~ $ curl -X POST http://localhost:13141/dspprofile -H "Content-Type: application/json" -d '{"file": "/home/pi/dspprofiles/beocreate/beocreate-universal-11.xml"}'
{"status":"success","message":"Profile from file successfully written to EEPROM","checksums":{"md5":{"memory":"D41D8CD98F00B204E9800998ECF8427E","profile":"97C9C5A88582888D111259BF70D6D79E","match":false}},"match":false}
pi@hifiberry:~ $ curl -X GET http://localhost:13141/program-info
{"program_length":0,"checksums":{"md5":null,"sha1":"DA39A3EE5E6B4B0D3255BFEF95601890AFD80709"}}
(the profile is https://github.com/hifiberry/dspprofiles/blob/4c0f0697bcd500092ba63f00c7c242317f3706c3/beocreate/beocreate-universal-11.xml and the hardware a Beocreate v2.1).
So apparently the profile was not installed correctly since the program length is 0 and match:false or do I misinterpret the output?
How can I debug this?
Also, there is no sound output, but that was always a constant struggle for me with this hardware that usually solves itself somehow magically after reinstalling the profile and rebooting a few times... But this time no luck and this strange output.
Metadata
Metadata
Assignees
Labels
No labels