Boot Screen Error

It might be this:

@Baggypants Thanks, but even with this change I get the same results and same kind of logs :

root@zynthian:~# jackd -Rd alsa -d hw:1 -r 48000 -p 1024 -n 2
jackdmp 1.9.14
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2019 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
creating alsa driver ... hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
JackGraphManager::Connect already connected port_src = 33 port_dst = 30
JackGraphManager::Connect already connected port_src = 10 port_dst = 32
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 13 err = Connection reset by peer
Could not read notification result
ClientNotify fails name = jackpeak notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 13 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jack_transport notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jack_transport notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackGraphManager::Connect already connected port_src = 33 port_dst = 30
JackGraphManager::Connect already connected port_src = 10 port_dst = 32
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 13 err = Connection reset by peer
Could not read notification result
ClientNotify fails name = jackpeak notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 13 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackGraphManager::Connect already connected port_src = 33 port_dst = 30
JackGraphManager::Connect already connected port_src = 10 port_dst = 32
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = ZynMidiRouter was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 13 err = Connection reset by peer
Could not read notification result
ClientNotify fails name = jackpeak notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 16 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 13 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 13 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = ZynMidiRouter notification = 1 val1 = 0 val2 = 0
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = jackpeak was not finished, state = Triggered
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 13 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jack_transport notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jack_transport notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jack_transport notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 3 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0
JackEngine::XRun: client = zynthstep was not finished, state = Triggered
Cannot write socket fd = 22 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = jackpeak notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = zynthstep notification = 1 val1 = 0 val2 = 0
Cannot write socket fd = 25 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = Zynthian_autoconnect notification = 3 val1 = 0 val2 = 0

Is there something else I have to do after having modified /etc/dbus-1/system-local.conf ?

BR,

Uru

Looks like this is also a problem. Zynthian is expecting a lot of things to be card0.

Jul 26 21:42:53 zynthian startx[18667]: ERROR:zynthian_engine_mixer.get_controllers_dict: Command 'amixer -M -c 0' returned non-zero exit status 1.

@Baggypants thanks !

Do you know where the card number in this command line is defined ?

in fact, in my case card number has to be number 1.

When I launch with card 0 :
root@zynthian:~# amixer -M -c 0
Invalid card number.
Usage: amixer [command]

When I launch with card 1 :
root@zynthian:~# amixer -M -c 1
Simple mixer control ‘Speaker’,0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 37
Mono:
Front Left: Playback 28 [71%] [-9.00dB] [on]
Front Right: Playback 28 [71%] [-9.00dB] [on]
Simple mixer control ‘Mic’,0
Capabilities: pvolume pvolume-joined cvolume cvolume-joined pswitch pswitch-joined cswitch cswitch-joined
Playback channels: Mono
Capture channels: Mono
Limits: Playback 0 - 31 Capture 0 - 35
Mono: Playback 0 [0%] [-99999.99dB] [off] Capture 20 [41%] [8.00dB] [on]
Simple mixer control ‘Auto Gain Control’,0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]

BR,

Uru

Don’t use card number in JACK startup. Use card name as detailed here, e.g. -d hw:DEVICE. (It is the name shown in aplay -l after card x: before the friendly name in square brackets but remember to prefix with hw:.
ALSA enumerates sound devices (including audio and MIDI interfaces) as it detects them which can result in different index on each boot, especially if you have USB devices plugged in which may be detected at different time. Advice is to unplug everything and set zynthian soundcard to “Dummy Device” in webconf and check if Zynthian boots then change soundcard in webconf to correct device (and adjust jack parameters as describe above if necessary) and reboot.

Note that there are several services which depend on JACK and upon which Zynthian depends and it is challenging to restart JACK and get everything working so a reboot is often the simplest / quickest way to get things working after changing JACK settings, especially in webconf which won’t be picked up by any currently logged in (ssh) sessions.

Thank you so much !!!

I solved my issue, not the cleaner way but it works and I’ve made my first jam with the beast ! :slight_smile:

In fact :

  1. I edited /etc/systemd/system/jack2.service to change my card number on this line and get the following result : ExecStart=/usr/local/bin/jackd -P 70 -t 2000 -s -d alsa -d hw:1 -r 44100 -p 256
  2. I followed this tuto to make calibration on the touchscreen : Could this be the end of all touch screen calibration issues?

And that’s all !!!

Many thanks !

BR,

Uru

Hey! I’ve been trying to understand how to do this on my Zynthian. Can you tell me what SD image version you used?

Fantastic! Would you mind sharing a sound from your Zynthian here on the forum? We would love to hear what it can do!

Excellent! Unfortunately I see NO evidence of this…
:face_with_monocle:

@Jtunes

I downloaded 2020-05-27-zynthianos-buster-lite-1.0.0-RC2 iso

I’ve just made a new fresh install with this only 2 steps and everything was fine for me :partying_face:

@wyleu unfortunately this jam was an ephemeral topic experience work :wink:

But still, we need some evidence that your Zynthian is alive! A sound, a melody, a whole song - it doesn’t matter! We would love to hear anything you can make your Zynthian do!

(For future reference, that’s what :face_with_monocle: stands for around here.)

@Jtunes

Oh ! sorry ! is there a special method to share something ? I’ll need to test how to record ! :slight_smile:

I’ll use my Zynthian on ma guitar pedalboard. I’ll use an ABY switcher with 1 loop for pure guitar sound and 1 loop for a guitar-to-midi encoder (https://www.sonuus.com/products_i2m_mp.html) plug to the pi

Maybe first, I’ll show you picture of the whole thing, but I need to finish first (I’m not a very fast guy :slight_smile: )

Read this.

1 Like

Then after recording, converting to ogg and downloading (all described in the link @Jtunes gave), just copy the ogg file to a message in this Discourse topic.

1 Like

Sorry guys, I encountered new issues on the same thing :
1. the card number config was not persistent after an unplug of battery power
I changed the hw:0 by hw:1 in the audio web config, in advanced fields, and now it’s persistent at each boot :slight_smile:
2. the screen calibration is not persistent after a simple reboot
I didn’t read the topic till the end … I have the same issue.
I tried to make the calibration script launched at startup with crontab and rc.local but without success :sleepy:

BR,

Uru

You are better off using card name. If you plug in a USB audio or MIDI device then the hw index will change and may change on each boot. We considered a mechanism for fixing the hw index but decided the support overhead would be significant and found that using the card name was reliable and simple. Why are you not using the card name? Have you found an issue we need to know about?

Hi @riban,

Sorry for the delay. How can I retrieve the card name ? when I make a aplay -l I only have this infos :

root@zynthian:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

BR,

Uru

In your example the JACK configuration would be: -d hw:Device.

@riban thanks for your quick reply i made a test right now ! :slight_smile:

BR,

Uru

@riban Many thanks !!! Indeed it seems to work like a charm !

BR,

Uru

I don’t understand, why the default AudioInjector selection doesn’t work. We are not using the number but the name