Shouldn’t matter, as far as I know, all the 3s are 64-bit.
Awesome, glad it’s working!
Ubuntu 22.04 LTS
iqaudio DAC+ in config.txt, alsa installed to confirm it worked
:“it just worked” ™
Rasplex worked on a 32bit install but only streamed from a laptop. this one, works from android as well.
Thanks. Virtual cheesy puffs winging their way to you, or tater tots.
2 Likes
Nom nom nom… 
Hmm, I tried 88 kHz FLACs and they worked fine, I don’t have anything higher. If they play fine the second time, then it’s likely network speed (b/c they’ll be cached the second time). Otherwise worth posting logs to see if there’s any dropout shown, as well as checking CPU usage and making sure it’s not overloaded.
I had similar experiences with extreme high bandwidth material, like 6 ch 96kHz or 192 kHz.
Material like that can exceed a bandwidth of 14mbps in some cases (although most tracks remain below 8mbps).
My suspicion would be the SD card. Plexamp’s cache is not in RAM, but in mass storage. Which in most cases is an SD card. And this is a very inferior architecture than SATA et.al. (or even a USB-attached SSD)
This is not about the data-transfer speed of the interface alone, but also about how the storage is organized and how well it can cope with several overlapping access requests.
To work around this limitation, I propose additional selectable bandwidth limits above 2mbps. (in Music Quality- WiFi)
That way, users can test out the limits of their individual hardware themselves. Anything above the limit shall be transcoded, to achieve at least play-ability.
1 Like
it’s not hard to add higher limits, but the bandwidth of the SD card (with RAM cache on top) should be more than enough. do the logs show anything interesting? it’s also quite possible we just need to adjust the ALSA buffers upwards a bit.
So I did a Fresh install of the latest Raspberry Pi OS Lite 64bit on a Pi 3B. installed plexamp as mentioned above, it’s running. I"m trying to play music through the headphone jack into a stereo receiver and it’s super garbled and quiet you can’t make out any of the music, but can tell it’s trying to play something. Went into alsamixer and playback level is @ 100% so any ideas on where I can check to see what’s going on? Also tried plugging in headphones and it does the same thing. Thank you!
1 Like
hmm, not offhand 
i’ve only played with digital output.
I already observed stuttering with 5.1 48/24 files.
Pretty sure that it happens when the next track(s) are precached.
Where are those logs again on the Pi?
RasPi 3B+
Hifiberry DAC Plus
In related news: Companion TIDAL playback at last!
P.S. I was not able to use the service. I assume it has something to do with the fact that the default user pi no longer exists in current RasPi OS releases. I was prompted to create my own user account upon first bootup.
Success!
Now able to output audio to my Soundcore Bluetooth speaker!
Needed to install pulseaudio-module-bluetooth (then pulseaudio —start, I’ll deal with auto loading all this on boot later)
(pulseaudio is a standard package on the PiOS Desktop, but not Lite)
After I ctrl-C and entering the above, plexamp starts, but fails to start on re-boot. What did I do wrong?
The file plexamp.service contains a hard coded path to the plexamp executables. It expects them to be in the home folder of user pi.
If your user name is different, loading of the service fails since the folder name of your home folder won’t be /home/pi.
Yes, its the same path.
I even tried copying the ExecStart= line in plexamp.service (/usr/bin/node /home/pi/plexamp/js/index.js), and pasting on the command line, plexamp loads.
Very strange.
Which pi log can I look at to investigate?
My Linux-fu is probably not sufficient to answer this correctly.
I assume it has something to do with user privileges.
sudo systemctl status plexamp.service tells me:
● plexamp.service - Plexamp
Loaded: loaded (/lib/systemd/system/plexamp.service; disabled; vendor preset: enabled)
Active: inactive (dead)
open the file plexamp.service in an editor.
check the path name and the user name which are named in there.
I was able to start the daemon after adapting these two lines to my user name.
[Unit]
Description=Plexamp
After=network.target
[Service]
Type=simple
User=pi <-- adapt this line
ExecStart=/usr/bin/node /home/pi/plexamp/js/index.js <-- adapt this line
Restart=on-failure
[Install]
WantedBy=multi-user.target
It was always there:
pi@pi4:~/plexamp $ cat /lib/systemd/system/plexamp.service
[Unit]
Description=Plexamp
After=network.target
[Service]
Type=simple
User=pi
ExecStart=/usr/bin/node /home/pi/plexamp/js/index.js
Restart=on-failure
[Install]
WantedBy=multi-user.target
Thanks for your report, @Casual_Tea
You answered a lot of questions I had about this that I had not yet had a chance to dig into.
(Whether this all works on a Lite Pi OS install, whether Hifiberry DACs work on Pi OS rather than Hifiberry OS, etc etc).
The only question I think I have so far is how well a 64 bit Pi OS install will work on a Pi 3B+ but I think if it’s a Lite install and I’m only using it for Plexamp, it should be able to handle it well enough.
It sounds like it’s time for me to order a Hifiberry DAC2 Pro and a new case for my 3B+!!
If you can find one, consider getting a Pi4 as well 
As a pure audio-only client, the Pi 3 is sufficient.
(Unless you are playing high-res files all the time.)
1 Like
