Soloist 0.6.5
Dsp on with lossless
first play ok, but same issue after
Beside the audio, an small suggestion : using the last volumio volume set on connect rather than an initial volume.
v0.6.6
Dsp on with lossless
not better…
Hey @balbuze,
Thanks - that log is clear. 0.6.6 is running, but the extra timing never fired, so it behaved like 0.6.5. FusionDSP and the DAC stayed at 44.1 kHz; Camilla was still reading the pipe at 48 kHz. Working on a follow-up that measures the real drain rate, not the write call. I’ll post when there is a build to try.
Kind Regards,
v0.6.8
Dsp off
still the issue
v0.6.9
Dsp off
still the issue, even with no lossless formats
Logs show shim 0.3.2 - this is not 0.6.9 build.
Kind Regards,
I fully understand what you’re saying and you are right, without logs it’s a needle in a haystack. However, there is some info in the logs I’m not comfortable with uploading. I will start testing again tomorrow and will try to remove sensitive information from the logs.
Not to demotivate uploading logs, but for everyone posting their logs, your api key is exposed in it, be aware of that.
Thank you guys so much for your efforts so far!
1 Like
Thanks for calling out the API key.
Will be handled with prio in the next release to obfuscate it.
As of V0.6.12 Key is obfuscated (not readable/visible)
3 Likes
Dear Volumionauts,
A Saturday field note, if you want something that is not the changelog.
A small bloodbath, some little birdies, and two people with the patience of saints
Today I treated the alpha like a piñata. Ten versions. One Saturday. If you installed 0.6.4, then 0.6.5, then 0.6.6 before the coffee had cooled, that was me. I was not “iterating.” I was guessing in public, with other people’s living rooms as the laboratory.
The music did complain. It rushed. It dragged. It chopped. It played half-speed on a USB DAC because I timed an empty buffer and decided the universe was 88.2 kHz. It stayed silent on another box because I refused a 32 KiB write that would not fit. I blamed format. I blamed resample. I blamed graphs that did not have a softvolume. I wrote a little clock that measured the wrong wait. I put it back. I took it out again.
The testers did not.
@Wheaten and @balbuze: enormous thank you. You installed, you listened, you sent the log, you installed the next one. Seldom a word about the fact that I was changing the engine while you were still in the driveway. That is a rare kind of kindness. Most people would have closed the thread and put on a record. You kept sending birdies back to the window.
And they were little birdies, too. Logs. “Still fast.” “Not better.” “Same with DSP off.” Then, this afternoon, on a Rivo that had every right to file for divorce: Three Little Birds, on time, through the same USB chain that spent the morning sounding like the tape was being eaten. Don’t worry about a thing. Apparently it took until 0.6.14.
The villain was not your DAC and not FusionDSP. Soloist writes 8–32 KiB even when we say the cushion is smaller. We smiled, kept the prefix, and threw the rest away. A full buffer and a polite lie. On a default 500 ms setting that is the whole ring, so the track played in shreds and Spotify’s own clock still said 1.00×, because it never saw the bytes we binned. The boxes that “just worked” had a little slack left. The ones that didn’t, didn’t. I made the ring honest. Pulse still sees the old target. The extra 64 KiB is for the burst we already knew was coming.
If your Saturday sounded like a cartoon fight in a kitchen, that was the bloodbath. If this evening a bird is singing at the right speed, that was you.
0.6.14 is the one I meant to ship this morning. I took the scenic route. @Wheaten and @balbuze, thank you for walking plank and take a plunge with me.
Kind Regards,
3 Likes
So far V0.6.14 is solid.
I’ve tried my absolute best to turn it into a bug report, but the software clearly didn’t get the memo. After relentless GUI and app abuse, it just kept responding like: “Harder, daddy.” 
Sound is great, controls are snappy, response is excellent.
Outstanding work!!!
1 Like
You did it !! 
@nerd you are really The Master 
!
Once again you show how you are able to transform something impossible in a something just possible, for everyone.
Thanks 
I still have to test last version though;
1 Like
After @nerd his last post I couldn’t wait till tomorrow. There is no more need to send my logs, because this version fixed all issues I had with stuttering/skipping! You’re a legend, my guy. I’m really trying to break it, it’s not letting me!
Next up: Testing for Beta Release
We need your help to get this over the finish line. There’s still a substantial amount of testing to be done, so please step up and give it a spin on your setup.
When reporting results, please include:
Device + Plugin(s) + Pass/Fail
Example:
rPi4 + FusionDSP + Soloist → PASS
or
rPi5 + FusionDSP + Soloist → FAIL
If it fails, please provide:
- A clear description of the issue
- Steps to reproduce it (if possible)
- Relevant logs
PASS means:
- Responsive controls (GUI and app)
- Clear audio
- No stuttering, dropouts, or glitches
The more configurations we test, the faster we can move toward a stable release. Thanks for helping out!
Thank you.
1 Like
Motivo V4.156 + Soloist V 0.6.14 => Fail
Moving the progress bar in the Spotify app causes Spotify Connect to disconnect.
However, when I move the progress bar directly on the Motivo, it won’t break down but there is a delay of 15 seconds before anything happens.
Sound is OK
Peppy-Spectrum fails on Primo-plus V4.187
This is caused by an error in the Image used for the rPi series.
Issue has been reported, but no reply received.
dpkg: error processing archive /var/cache/apt/archives/libpython3.11-stdlib_3.11.2-6+deb12u8_armhf.deb (--unpack):
trying to overwrite '/usr/lib/python3.11/EXTERNALLY-MANAGED', which is also in package raspberrypi-sys-mods (20250930~bookworm)
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libpython3.11-stdlib_3.11.2-6+deb12u8_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Manually fixed error to be able to test.
running:
sudo dpkg -i --force-overwrite /var/cache/apt/archives/libpython3.11-stdlib_3.11.2-6+deb12u8_armhf.deb
sudo apt --fix-broken install
1 Like
Just to validate, it sounds like this plugin supports Spotify Lossless streaming. Is that true?
It’s working perfectly for me. And Volumio is showing “Lossless” as the quality level. Awesome. Not that I (or anyone) could hear the difference between 320Kbps and Lossless, but still great this brings Spotify Lossless to the Raspberry Pi world.
Great work! Many thanks for this!
One question: all my playlists contain a mix of local/NAS, Qobuz and Spotify tracks. Currently most playlists are broken due to the Spotify plugin issue. I understand that the Soloist plugin is primarily implemented as a Spotify Connect endpoint. Will there be any chance that selecting tracks and use mixed playlists with Spotify links will be a future development? Not a request to solve this immediately of course: I realise the plugin is very new. I’m just trying to understand the intended roadmap.
Again: many thanks for developing this!