Picoreplayer 7 + RPi4B. USB DAC output problems

[coyrls]

I am a bit lost as to how an upgrade vs a fresh install will address the problem. I think bigq started with 7.0.0, so it's not as if it was ever working under 6.0.1.
My suggestions would be:

1) Check what is specified as the output under Squeezelite settings and if it's not already "hw:CARD=v12,DEV=0", change it to that and retest
2) Try changing the USB cable

[chill]

Can you perhaps post a couple of dmesg logs (get to them via 'Main page' -> 'Diagnostics' -> 'Logs', or just type dmesg at the command prompt)?

For the first one, boot the Pi with the dac connected and powered. I understand that in this state you get no sound.
For the second one, boot the Pi with the dac disconnected, then connect the dac when the pi has finished booting. I understand that in this state you get sound. If you only sometimes get sound in this state, keep disconnecting and reconnecting the dac until the sound works, then save the dmesg log.

[slartibartfast]

Man in a van and coyrls, thanks for your advises.
So I tried to save (sudo alsactl store), backup and then reboot.
The same situation, only replugging helps after boot.

As far as I can see the problem is in initializing 'USB' soundcard on boot. For some reason it's not found.
May be there is a command to add in tweaks that could initialize it manually?

One thing you could try is to toggle the power to the USB socket your DAC is connected to. Install uhubctl from the extensions list then add a couple of commands to run after start up. For my Pi3 with the DAC connected to socket 4 I use

uhubctl -l 1-1 -p 4 -a 0
uhubctl -l 1-1 -p 4 -a 1



Sent from my Pixel 3a using Tapatalk

[Man in a van]

I am a bit lost as to how an upgrade vs a fresh install will address the problem. I think bigq started with 7.0.0, so it's not as if it was ever working under 6.0.1.
My suggestions would be:

1) Check what is specified as the output under Squeezelite settings and if it's not already "hw:CARD=v12,DEV=0", change it to that and retest
2) Try changing the USB cable

Well, there is more than one way to skin any cat

Try pCP v6.0.1 and if it works, copy logs and upgrade to v7.0.0

My Cirrus Logic dac works in pCP v6.0.1, does not work in pCP v7.0.0 and does work in Raspberry PI OS Lite (with the 5.10 kernel)

Go figure

ronnie

[bigq]

No, I don't think that's the problem. I think alsactl is a red herring, unless you are setting an ALSA level, which you are not, it's not needed. The error messages you are seeing are to do with part of a script that is only executed when ALSAlevelout is set to "Custom". Your problem was happening before this change was made and, as you are not setting an ALSA level it is not needed. Everybody with a USB DAC who sets ALSAlevelout to "Custom" will see this problem but the only consequence is that the ALSA level is not restored on reboot, not that the USB DAC doesn't function.

Your USB card is found, as that is confirmed by the message "Waiting for soundcard USB to populate. Done (1)." that you have reported. The only odd thing that I can see in what you've posted is that alsamixer shows two dbGain bars for your DAC, I have only ever seen one. What output setting do you have under Squeezelite settings? Have you tried: "hw:CARD=v12,DEV=0"?

Tried all of them, but no success.

@bigq

Load up pCP v6.0.1 and see how you go

ronnie

So I need to delete 7.0.0 and install 6.0.1?

[bigq]

Can you perhaps post a couple of dmesg logs (get to them via 'Main page' -> 'Diagnostics' -> 'Logs', or just type dmesg at the command prompt)?

For the first one, boot the Pi with the dac connected and powered. I understand that in this state you get no sound.
For the second one, boot the Pi with the dac disconnected, then connect the dac when the pi has finished booting. I understand that in this state you get sound. If you only sometimes get sound in this state, keep disconnecting and reconnecting the dac until the sound works, then save the dmesg log.

Hi chill, here are the logs:
when booted with connected DAC and no sound:
no sound.txt

when booted with no dac and then plugged, sound is there:
sound.txt

[bigq]

One thing you could try is to toggle the power to the USB socket your DAC is connected to. Install uhubctl from the extensions list then add a couple of commands to run after start up. For my Pi3 with the DAC connected to socket 4 I use

uhubctl -l 1-1 -p 4 -a 0
uhubctl -l 1-1 -p 4 -a 1

Tried these commands. Didn't help. It seems it has not the same effect as re-plugging.
Re-plugging brings sound and re-powering port doesn't.
But anyway thanks for the idea!

[slartibartfast]

Tried these commands. Didn't help. It seems it has not the same effect as re-plugging.
Re-plugging brings sound and re-powering port doesn't.
But anyway thanks for the idea!

Did you use the right port?
The Pi4 seems to act differently to the Pi3 according to this.
https://github.com/mvp/uhubctl#raspberry-pi-4b
although the info on the Pi3 is incorrect as the ports can be controlled individually and aren't ganged as stated.

Sent from my Pixel 3a using Tapatalk

[Man in a van]

Hi chill, here are the logs:
when booted with connected DAC and no sound:
no sound.txt

when booted with no dac and then plugged, sound is there:
sound.txt

Well I'm a numpty at this but both files show

[ 183.071011] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 189.771340] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

But only one file (sound) shows (that I can see, I might have missed it)

111.020862] usbcore: registered new interface driver snd-usb-audio

Both files show the dac being recognised.

For what it's worth, I would suggest a fresh image.

It's not really necessary, but maybe reformat the card using

https://www.sdcard.org/downloads/formatter/

and use

https://www.balena.io/etcher/

to make the image

remember, these are just suggestions

ronnie

[chill]

But only one file (sound) shows (that I can see, I might have missed it)

It's there in the 'no sound' case, just a little further down. In fact the dmesg entries that appear when the dac is inserted later in the 'sound' case are all there in the 'no sound' case, but interspersed with other entries.

Sound:

[   45.187324] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[   52.129078] Finished piCorePlayer v7.0.0 startup.
[  110.791698] usb 1-1.4: new high-speed USB device number 3 using xhci_hcd
[  110.922530] usb 1-1.4: New USB device found, idVendor=152a, idProduct=85df, bcdDevice= 6.f2
[  110.922548] usb 1-1.4: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[  110.922565] usb 1-1.4: Product: SABAJ DA2 v1.2
[  110.922581] usb 1-1.4: Manufacturer: SABAJ
[  110.945818] mc: Linux media interface: v0.10
[  111.008379] usb 1-1.4: 1:3 : unsupported format bits 0x100000000
[  111.020862] usbcore: registered new interface driver snd-usb-audio
[  183.071011] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  189.771340] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

No Sound:

[    1.345590] hub 1-1:1.0: USB hub found
[    1.345874] hub 1-1:1.0: 4 ports detected
[    1.681661] usb 1-1.4: new high-speed USB device number 3 using xhci_hcd
[    1.812278] usb 1-1.4: New USB device found, idVendor=152a, idProduct=85df, bcdDevice= 6.f2
[    1.812285] usb 1-1.4: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[    1.812292] usb 1-1.4: Product: SABAJ DA2 v1.2
[    1.812298] usb 1-1.4: Manufacturer: SABAJ
[    3.240241] zram: Added device: zram0
[    3.245548] zram0: detected capacity change from 0 to 491057152
[    3.248845] random: mkswap: uninitialized urandom read (16 bytes read)
[    3.311663] Adding 479544k swap on /dev/zram0.  Priority:-2 extents:1 across:479544k SSFS
[    3.386067] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    3.764786] EXT4-fs (mmcblk0p2): recovery complete
[    3.765716] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.796219] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   13.040334] mc: Linux media interface: v0.10
[   13.144305] usb 1-1.4: 1:3 : unsupported format bits 0x100000000
[   13.145644] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   13.162495] usbcore: registered new interface driver snd-usb-audio
[   13.200901] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   13.229929] brcmfmac: F1 signature read @0x18000000=0x15264345

I'm also no expert, but to me this suggests that the hardware recognition and driver loading are the same in both cases. Maybe it points to an issue with the alsa configuration, but I don't have any bright ideas.