SOLVED - Switching to headphones in V4.5 kit gets stuck boot screen

Using Zynthian
,
1

Hi,

I purchased a used V4.5 kit. I took the latest stable image and updated to oram staging.

So far, things work as expected and it’s nice to build mustle memory for the zyncoders :flexed_biceps:. The main outputs work fine, however I also want to use the headphone out(s) on occasion.

I understand that by default, these are not available to use from the mixer.

I see the 2 headphone out mini jacks:

  1. Raspberry Pi headphone out mini jack one next to the HDMI outs.
    To use, enable RBPi Headphones in the Admin menu or in Hardware-Audio in webconf.
    Strangely, the settings doesn’t seem to add the headphone to the mixer outs, so I disabled it again.
  2. Mini jack with the hardware volume control on the right side panel of the V4. I suppose this is a better quality output, and connected to the HifiBerry DAC+ ADC PRO?
    I tried to enable this by switching to the setting below, however this resulted in a stuck Zynthian GUI with the Audio/MIDI error.
    Is this an expected result? I can troubleshoot via SSH.
    Also, is there a way to rollback this change via SSH to avoid a full reset of the system?

image
image996×924 94.8 KB

Thanks,

Bernard

ZynthianOS Oram-2511-3

Timestamp: 2025-11-05
Built from RaspberryPiOS Bookworm (aarch64)

Kit: V4

Display: ZynScreen 3.5 (v1)
Soundcard: HifiBerry DAC+ ADC PRO
Wiring Layout: MCP23017_ZynScreen

zynthian-ui: oram (171d3b)

zynthian-webconf: oram (95043f)
zyncoder: oram (840c6f)
zynthian-sys: oram (dc8012)
zynthian-data: oram (e4e24b)

2

Revert your changes. You don’t need to config anything to use the left-side headphones output. it’s connected directly to the DAC audio output.
You can also enabled the RPi headphones output (check the checkbox!), that adds some extra CPU consume, but not too much. Quality is lower, but it’s independent from the main DAC. So you can, in theory, get a different mix, although this is not currently implemented.

Regards,

2 Likes
3

I reverted using the set_first_boot.sh script.

Then I still didn’t hear any output, until I removed the jack cables from the regular output.

It works, and in retrospect, it works as expected :sweat_smile:.

Thanks for the fast reply @jofemodo !