Pisound red error screen

Hi everyone,
I try to install a headless zynthian on raspberry pi 4 8Gb.
This seems to work well with an hifiberry dac+ and VNC.

But I’m completely blocked with my pisound. Always the red error screen with the IP address (webconf, ssh and vnc worked).

In the webconf, I set :

Soundcard = pisound
Display = Generic HDMI Display
wiring = custom (and try several combinaisons for the MCP23017 pins)

Does someone have an idea of where there’s the conflict with the pisound ?

Thanks a lot

Hi @gnuv! Welcome.

Please post info from http://zynthian.local. This webconf home page has useful information to assist diagnose issues.

You mean these infos ?

HARDWARE
Raspberry Pi 4 Model B Rev 1.4
Soundcard: PiSound
Display: Generic HDMI Display
Wiring: CUSTOM
GPIO Expander: Not detected

SYSTEM
Raspbian GNU/Linux 10 (buster)
Build Date: 2020-09-05
Memory: 2% (219M/7966M)
SD Card: 70% (9.3G/14G)
Temperature: 39.0ºC

MIDI
Profile: default.sh
Fine Tuning: 440 Hz
Master Channel: 16
Single Active Channel: on
ZS3 SubSnapShots: on

SOFTWARE
zyncoder: master (aa91afe)
zynthian-ui: master (94854cb)
zynthian-sys: master (dcf8d8a)
zynthian-data: master (336eadc)
zynthian-webconf: master (17b44ff)

LIBRARY
Snapshots: 1
User Presets: 5
User Soundfonts: 0
Audio Captures: 0
MIDI Captures: 0

NETWORK
Hostname: zynthian
Wifi: hotspot
IP: 169.254.132.65 192.168.50.1
RTP-MIDI: off
QMidiNet: off

Note : I use the last stable zynthian OS

Hi @gnuv

I’m a newish user myself but I notice that you have:

Wifi: hotspot
IP: 169.254.132.65 192.168.50.1

Are you wanting to connect to it as a WiFi Hotspot (which your webconfig page shows is set) or via your local network - with the Pi connected via wired Ethernet or with the Pi WiFi set to “on” in webconfig ?

As I say I don’t know for sure, but maybe the WiFi setting got changed accidentally when you changed to the PiSound perhaps?

Sorry if this is not relevant, but thought I’d mention it in case it is.

I just change the wifi to hotspot after the test.

But my normal config is : wired ethernet directly to the computer and wifi on my internet (so not hotspot) to upgrade and install VNC.

So to confirm, the Pi is connected via wired Ethernet?

You have an HDMI monitor connected to the Pi? If so what is showing ?

When you had the Hifiberry sound card did you have it set to a WiFi hotspot?
You said you used VNC to connect, did you got the proper UI screen?

Have you tested it with it not set to a Hotspot? Edit: With the PiSound.

The reason I ask is that you mentioned a “red error screen with the IP address”

So to confirm, the Pi is connected via wired Ethernet?

Yes

You have an HDMI monitor connected to the Pi? If so what is showing ?

ERROR in Red with the ip address.

When you had the Hifiberry sound card did you have it set to a WiFi hotspot?

Not at the begining. I just set the hotspot after for testing direct VNC connection with my smartphone.

You said you used VNC to connect, did you got the proper UI screen?

The same as the HDMI monitor (red error)

Have you tested it with it not set to a Hotspot? Edit: With the PiSound.

Yes

The error message shows when Zynthian could not start. This is most likely due to JACK failing to start. You could look at the service journal output with:

journalctl -ru jack2

This displays the service log in reverse order (newest at top). (‘q’ to quit).

Also show us the output of http://zynthian.local/hw-audio.

Here’s the audio config :

Soundcard: Pisound

Config: dtoverlay=pisound

Jackd Options:
-P 70 -t 2000 -s -d alsa -d hw:0 -r 44100 -p 256 -n 2 -X raw

Aubionotes Options:
-O complex -t 0.5 -s -88 -p yinfft -l 0.5

And the service journal output :

– Logs begin at Wed 2020-05-27 08:29:07 BST, end at Wed 2020-05-27 08:36:14 BST
May 27 08:36:07 zynthian systemd[1]: jack2.service: Scheduled restart job, resta
May 27 08:36:07 zynthian systemd[1]: jack2.service: Service RestartSec=1s expire
May 27 08:36:05 zynthian systemd[1]: jack2.service: Failed with result 'exit-cod
May 27 08:36:05 zynthian systemd[1]: jack2.service: Main process exited, code=ex
May 27 08:36:05 zynthian jackd[3919]: Failed to open server
May 27 08:36:05 zynthian jackd[3919]: creating alsa driver … hw:0|hw:0|256|2|4
May 27 08:36:05 zynthian jackd[3919]: self-connect-mode is "Don’t restrict self
May 27 08:36:05 zynthian jackd[3919]: JACK server starting in realtime mode with
May 27 08:36:05 zynthian jackd[3919]: under certain conditions; see the file COP
May 27 08:36:05 zynthian jackd[3919]: This is free software, and you are welcome
May 27 08:36:05 zynthian jackd[3919]: jackdmp comes with ABSOLUTELY NO WARRANTY
May 27 08:36:05 zynthian jackd[3919]: Copyright 2016-2019 Filipe Coelho.
May 27 08:36:05 zynthian jackd[3919]: Copyright 2004-2016 Grame.
May 27 08:36:05 zynthian jackd[3919]: Copyright 2001-2005 Paul Davis and others.
May 27 08:36:05 zynthian jackd[3919]: jackdmp 1.9.14
May 27 08:36:05 zynthian systemd[1]: Started JACK2 Audio Server.
May 27 08:36:05 zynthian systemd[1]: Stopped JACK2 Audio Server.
May 27 08:35:43 zynthian systemd[1]: jack2.service: Scheduled restart job, resta
May 27 08:35:43 zynthian systemd[1]: jack2.service: Service RestartSec=1s expire
May 27 08:35:42 zynthian systemd[1]: jack2.service: Failed with result 'exit-cod
May 27 08:35:42 zynthian systemd[1]: jack2.service: Main process exited, code=ex
May 27 08:35:42 zynthian jackd[3705]: Failed to open server

Yep, JACK is failing to start. What is the output from aplay -l?

root@zynthian:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 2: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 3: pisound [pisound], device 0: PS-1SZCQG0 snd-soc-dummy-dai-0 [PS-1SZCQG0 snd-soc-dummy-dai-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

Try replacing the jackd options with:

-P 70 -t 2000 -s -d alsa -d hw:pisound -r 44100 -p 256 -n 2 -X raw

When I try :

jackd -P 70 -t 2000 -s -d alsa -d hw:pisound -r 44100 -p 256 -n 2 -X

It seems to works just for some seconds.
Before, it was alternating between the boot screen and the error screen.
Now it’s alternating between the good zynthian screen, the boot screen and the error screen.

@riban

Don’t want to be a pain possibly but, if I select PiSound it sets “-d hw:pisound” as standard.

I notice that @gnuv has:

zynthian-data: master (336eadc)

Mine is:

zynthian-data: master (74ceb35)

Is that likely to be significant for this?

Yep! Try doing an update from webconf http://zynthian.local/sw-update

Badly, after updating, I’m back to the initial situation (alternating between the boot and the error screen)

What version does “zynthian-data: master” show now in webconfig?

Are the checks you made before still the same now after update?

Also did you do a full power off and on or reboot - might try power off/on perhaps if the “zynthian-data: master” has updated from before.

What version does “zynthian-data: master” show now in webconfig?

zynthian-ui: master (94854c)
zynthian-webconf: master (17b44f)
zyncoder: master (aa91af)
zynthian-sys: master (dcf8d8)
zynthian-data: master (336ead)

Are the checks you made before still the same now after update?

Yes, and I try after the update to run the jackd command and it’s the same.

Also did you do a full power off and on or reboot - might try power off/on perhaps if the “zynthian-data: master” has updated from before.

Yes, I try to reboot and to power off.

@gnuv @riban

What you have put:

zynthian-ui: master (94854c)
zynthian-webconf: master (17b44f)
zyncoder: master (aa91af)
zynthian-sys: master (dcf8d8)
zynthian-data: master (336ead)

Seems like it’s in a different order to what you put before:

zyncoder: master (aa91afe)
zynthian-ui: master (94854cb)
zynthian-sys: master (dcf8d8a)
zynthian-data: master (336eadc)
zynthian-webconf: master (17b44ff)

The number of digits in each pair of brackets appears to be missing the last character perhaps?

If that is a copy and paste problem (missing character) then does it not seem that “zynthian-data: master” hasn’t actually changed in the update you did?

Was there an error perhaps when you did the update, you didn’t see?

Maybe @riban or another can shed some light?