Auxiliary output randomly stops working

Hi Josh,

Thanks for the detailed logs.

By auxiliary you mean the built-in audio jack?
Can you look at the Health Checker when playback drops? Is there a performance spike?

Do you use WiFi for your BT-setup, too? The BT and WiFi on 3B+ share the same small chip for operations so this might be a source of issue for your BT playback.

Hi Josh

I might be able to help if we work together!!

I have looked at your enclosed debug files and I can see that you haven’t done a update lately

If you go into the raspberry settings tap and scroll down to „Kernel and Package Updates and Upgrades“

next: Reboot your PI

If you haven’t installed the plugin: Remote Control do it and set it up

I need to know the status of two programs

After you have locked in with your user/password type:

sudo systemctl status shairport

look for the line „Active:“ and let me know what it says here after.

Do the same thing with:

sudo systemctl status Squeezelite

looking forward to your answer

Peter

Hi Josh

There is no overlap in your settings and boot config is also ok, I can’t see if you have marked jack instead of HDMI but you have told Heiner that you did.

Normally when we talk about software errors its more black or white (either it works or it doesn’t) It is more likely some outer interference ….. like your power supply (we are all hav’ing that problem sooner or later) I wood suggest that the next thing to try is the minimalistic approach. uninstall bluetooth and unplug your usb sound card. If you have other usb / GPIO devices pluged in remove them too.

maybe if load all on one PI and nothing on the other … does that make a difference ???

Most 5v plugs are more likely 4.6-4.75v wich is too low for the PI.

Let me know the result of your test, I will try to think of any other possible solution.

Peter

Okay

There is nothing wrong with the basic settings

We can take a look at the log for hardware to see if there is any error message:

Open Remote Control plugin and type:

dmesg

The last thing I know of that we can do… making the audio jack output the default output and/or secure that it stays that way

I need the readout of those two commands:

cat /proc/asound/cards

and

aplay -l

This will show us in which ordre the sound cards are loaded there after we can set up a new file to make sure we that always get the same order!!

• This reply was modified 5 years, 9 months ago by Cassio299.

Hi Josh

Your boot up file (Dmesg file looks ok) you do however have a hang on boot (just a delay):
[ 4.297395] random: crng init done
[ 4.297411] random: 7 urandom warning(s) missed due to ratelimiting

this can be avoided by installing:

sudo apt update
sudo apt install haveged
sudo systemctl enable haveged

If you want!!!

You should also expand your SD card if you haven’t already done so (to avoid future hang ups)

You do so in the settings/reboot tab click on „expand filesystem“ then Reboot

The following settings are important for your device to work as intented:

Audioplayer tab
turn off Squeezelite
turn off Shairport

Bluetooth tab
Sound Device: Alsa – hw:0.1 HDMI (because you are using the 3,5mm jack wich needs the Alsa – hw:0.0 driver to run)
(if you have set it to hw:0.0 unload bluetooth speaker change the setting and click save)

Multisqueeze tab
Your cards readout said that card 0 was the Alsa driver and card 1 was the USB DAC (this is the normal standard so nothing was changed here)

Set the instances according to that

Instance 0 : sound card: default bcm2835 ALSA……..card = ALSA (your 3,5mmm jack)
Instance 1 : sound card: default – USB AUDIO DAC, or front – USB Audio DAC
Instance 2 : sound card: Your Bluetooth Device (if you have a bluetooth audio speaker)

Set Audio Output on Raspberry PI: Force Headphone Jack

Let me know if this did anything !!

Peter

• This reply was modified 5 years, 9 months ago by Cassio299.

Hi Josh

Thats weird … in AudioPlayer tab try this: Squeezeligt: stop Squeezeligt then unmarked auto startup then click save next to it
do it the same way for Shairport.

reboot

and go back and check.

Have you checked bluetooth settings that you have picked the 2nd from top ALSA HDMI ?

Peter

Hi Josh

Okay lets take a different aproche before those PI’s will be unwillingly flying out of the window!!.

I think, there must be something odd going on in the settings department…

Let us recap, there might be something we have overlooked.

1. On the ‚Mainroom‘ Raspberry Pi 3+ you have Squeezelite, Bluetooth and Multi-squeeze running. You are streaming sound from your USB soundcard and a device connected to the 3.5mm audio jack.You own a 3a 5v power supply wich you are using with your ‚Mainroom‘ Raspberry Pi+

Your ‚Mainroom‘ Pi 3+, was working fine until suddenly the audio jack stoped working.It started working again After a software reinstall. The audio jack worked for aprox. 5 days before it stoped working again.

At the end of January the audio jack still doesn’t work, and you have almost given up on bluetooth to work also. However you do not uninstall the plugin.

2. February: Your installation has changed you are no longer streaming/playing from one Raspberry pi 3+ ‚Mainroom‘ with a USB card and a 3,5mm audio device. The second device is called ‚desk‘ player. The second player also have a defect audio jack. You tried with the same SD card and sound cards with the same result and therefore think that the problem is the software.

3. On the 18th you send me your Pi’s boot report (Demsg) from a Raspberry Pi called ‚Soundsystem‘ properly with new installed software and clearly not the same as the Pi called ‚Mainroom‘. Maybe a third PI??.

A finally one of the first thing I asked you to do was telling me the status of the settings of Squeezelite and Shairport in the Audioplayer tab. On the 15th. you told me that the status was: Active: inactive (dead). also not running.

On the 18th you wrote: I disabled the autostart of Squeezelite and Shairport in the AudioPlayer tab, however they still seem to start and run and the 19th you wrote: I cannot stop squeezelite and shairport (Trying to stop … could NOT stop process – try kill instead) and sometimes kill does not work. When I do manage to kill the processes, once I reload the page they have started again. The checkboxes are unticked.

I now know that there are only one person who can solve the mystery of the sudden death of the auxiliary output!!!

And that person needs to find out who, how and what in the chase of the unstoppable process!! first.

Until then I wish you a happy reinstalling!!

Peter

Hi Josh

Im sorry, but Im not able to help you.

Peter

Hi Josh,

At this point I understand your main issue is the audio jack not working? I’d recommend trying to burn a fresh image on a separate sd card (if you have not yet, just use the one from the Pi that’s working fine) and checking if the playback still doesn’t work. If this is the case, your audio jack port might just be faulty.

However, behaviour like the audioplayers not being able to be properly shut down and somehow autostarting despite it being unticked indicate that your system might also be impeded by further issues stemming from your customization.

My general recommendation would really be to burn a fresh image. As mentioned you can create a backup of your current one through various channels (burner software, our burner plugin, etc.)