Aarch64 plexamp cannot see audio devices

Plex Labs
1

Hey there- I’m running this on a Rock64 (very similar to rpi) running NixOS, and while I can get the software running and communicating, it seems like it cannot see any audio devices.

When I start the web interface, under Settings > Playback > Audio Output > Audio Device, there’s simply an empty page. No devices. On the RPi4 I’ve got, this is populated with all kinds of permutations of “Default”, “dmix device”, the usb audio interface plugged into that rpi, etc etc. Here there’s nothing. I’m not sure where to go further here attempting to debug, but this is in the startup logs:

May 07, 2022 23:05:44.631 [Javascript] INFO - Audio: Initializing.
May 07, 2022 23:05:44.634 [Javascript] INFO - Audio: Binding settings.
May 07, 2022 23:05:44.634 [Javascript] INFO - Audio: Setting player info.
May 07, 2022 23:05:44.637 [0xb2093120] DEBUG - BASS: Starting up.
May 07, 2022 23:05:44.637 [0xb2093120] DEBUG - BASS: Created bass audio renderer.
May 07, 2022 23:05:44.637 [0xb2093120] DEBUG - BASS: Using plugin path '/home/pjjw/plexamp/plexamp/treble/'.
May 07, 2022 23:05:44.638 [0xb2093120] DEBUG - BASS: Reloading ourselves for symbol visibility.
May 07, 2022 23:05:44.646 [0xb2093120] INFO - BASS: Loaded AAC plug-in version 2.4.5.11
May 07, 2022 23:05:44.653 [0xb2093120] INFO - BASS: Loaded ALAC plug-in version 2.4.0.3
May 07, 2022 23:05:44.657 [0xb2093120] INFO - BASS: Loaded FLAC plug-in version 2.4.4.5
May 07, 2022 23:05:44.663 [0xb2093120] INFO - BASS: Loaded OPUS plug-in version 2.4.2.1
May 07, 2022 23:05:44.667 [0xb2093120] INFO - BASS: Loaded APE plug-in version 2.4.2.0
May 07, 2022 23:05:44.671 [0xb2093120] INFO - BASS: Loaded MPC plug-in version 2.4.1.3
May 07, 2022 23:05:44.673 [0xb2093120] INFO - BASS: Loaded DSD plug-in version 2.4.1.2
May 07, 2022 23:05:44.673 [0xb2093120] INFO - BASS: Core version 2.4.16.7
May 07, 2022 23:05:44.673 [0xb2093120] INFO - BASS: Mixer version 2.4.11.1
May 07, 2022 23:05:44.673 [0xb2093120] INFO - BASS: FX version 2.4.12.1
May 07, 2022 23:05:44.673 [0xb2093120] INFO - BASS: Curl version is 7.83.0 (protocols: dict file http https mqtt; ssl: OpenSSL/1.1.1n; libz: 1.2.12; DNS: threaded).
May 07, 2022 23:05:44.673 [0xb2093120] DEBUG - BASS: Setting audio interface:  -> .
May 07, 2022 23:05:44.693 [0xbc206010] ERROR - BASS: Error [BASS_ChannelSlideAttribute(m_mixer, BASS_ATTRIB_VOL | BASS_SLIDE_LOG, vol, ms)] - 5
May 07, 2022 23:05:44.693 [0xbc206010] DEBUG - BASS: Sliding volume to 1.0 over 0 ms.

For the record, this device is currently serving as my bedroom stereo, with pulseaudio/librespot/shairport-sync all running and outputting audio without complaint.

Fully recognize that there are a number of uncontrolled variables in my current setup, but thought I’d post to register the bug in the hope I get someone curious enough to point me in possibly the right direction on what to debug- how does BASS probe for devices, and what’s missing here?

2

there’s not enough in the logs to be able to tell, try playing something and we can get more details. it should just need ALSA.

3

Sure. Here’s a log from startup to switching my desktop plexamp to play through this plexamp to failure: plexamp logs · GitHub (log too big for a forum post, so made a gist)

I read that as Bass is initializing a device index that indicates an error, but nothing about how it’s probing the devices, which seems to be the issue that needs solving.

An alsa-info report for this box is at http://alsa-project.org/db/?f=e42e202033f62edefd311722d86612ecccee5934

4 
May 08, 2022 14:49:45.008 [0x9ecd3120] ERROR - BASS: Error initializing device -1 with sample rate 44100 and flags 00004000 (23).

Error 23 is BASS_ERROR_DEVICE (illegal device number).

You can get a real-time view of what devices the app sees by doing this:

$ curl http://localhost:32500/settings/values\?name=audioDeviceUuid
[["default","Default",""],["sysdefault","Default Audio Device",""],["hw:2,0","Loopback: Loopback PCM",""],["hw:2,1","Loopback: Loopback PCM",""],["hw:1,0","snd_rpi_hifiberry_digi: HifiBerry Digi HiFi wm8804-spdif-0",""],["hw:0,0","vc4-hdmi: MAI PCM i2s-hifi-0",""]

I’m not going to be able to provide much support outside of the Raspberry Pi.

5 
[pjjw@oontz:~]$ curl http://localhost:32500/settings/values\?name=audioDeviceUuid
500 Internal Server Error

and from the logs when this happens

May 08, 2022 17:24:42.368 [Javascript] ERROR - HttpServer: 500 Internal Server Error (/settings/values): Cannot read property 'uuid' of undefined`

for fun i tried compiling the Bass test apps on this platform and they all bail being unable to find an audio device, so maybe I need to pick this back up there. thanks!

6

Thanks for the extreme level of competence! Does seem like there’s something amiss with ALSA.

(If nothing else, their forums are very responsive)

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.