SROVA V2.0 — a little post-launch technical update, and what comes next
Now that V2.0 has been out for a little while, I thought I’d share a short technical update on two of the bigger additions —
Qobuz and Spotify Connect — because they actually arrived in SROVA by very different routes.
Qobuz became a native SROVA source.
It is integrated into SROVA’s own browsing, search, queue, radio and playback architecture rather than being handed off to another player. The aim was to make Qobuz feel like it had always belonged there alongside TIDAL, Local Music and Internet Radio, while still using the same SROVA audio path to the DAC.
That involved rather more work than simply adding another login button, but I’m pleased with where it landed in V2.0. Qobuz now behaves as part of the player rather than as a bolt-on.
Spotify Connect took almost the opposite route.
For that I use
Soloist as the Spotify Connect endpoint. SROVA does not try to become Spotify itself; instead it manages the relationship between Soloist and the rest of the player.
The interesting part was therefore not the Spotify UI — the Spotify apps remain the controller — but
DAC ownership and handoff. When Spotify takes over, SROVA has to get out of the way cleanly; when Spotify leaves, SROVA has to recover the DAC and return to normal native playback without requiring the user to manage audio services manually.
So V2.0 ended up with two useful examples of the way I’d like SROVA to develop:
integrate something deeply when that makes sense, and coexist cleanly when it doesn’t.
October / V2.1
I’m now starting the V2.1 work.
This is primarily a
hardening and refinement release, rather than another large provider expansion. The current working list includes things such as:
- DAC hotplug/re-registration behaviour with ALSA MMAP;
- tighter Bit-Perfect / Volume Locked semantics so the displayed state reflects the real DAC digital-gain state;
- further Spotify/Soloist ownership and recovery hardening;
- Qobuz artist-navigation and library-loading improvements;
- screen-aware context menus and some smaller UI polish;
- Cast session recovery and further Cast presentation work;
- easier local-network discovery of SROVA Players from the Android Remote.
There are also a few things I want to
inspect first rather than promise, including headless Wi-Fi provisioning and whether Auto Mix really needs further work. The rule for V2.1 is fairly simple: look under the hood first, then decide whether something genuinely belongs in 2.1 or should wait.
The full working plan currently has 17 consolidated points across the Player, UI/UX, Cast and Android Remote, with the emphasis on strengthening the suite rather than forcing a short release cycle.
SROVA is still very young, and I’m enjoying this stage enormously — use it, find the rough edges, understand them properly, polish them, and add new things only when they genuinely fit.
As always, feedback from people actually using it in different systems is extremely useful.
https://srova.music