Just out of curiosity @Dadoo are you on the latest EA Roon build?
I fully remove the container and data folder. Deleted Roon and installed the latest EA. Reinstalled my extension and I get the same as you. Another user has reported the same.
Roon API is bust for extensions pulling from Roon. The TV:Remote app on my Apple TV doesn’t work.
Playing an Album in Roon remote will show playing in the extension because Roon API is sending it.
Yes, running the latest EA Roon build (2.71 1674).
I see this event in my Roon logs after clicking an album to play in the extension UI:
System.ArgumentNullException: shared-query acquire must be attributed to a connection owner (Parameter ‘owner’)
That was taken from the below…
07/14 16:33:36 Trace: [roonapi] [apiclient 192.168.205.2:38468] GOT com.roonlabs.browse:1/browse {"hierarchy":"albums","pop_all":true,"multi_session_key":"rra_s9"}
07/14 16:33:36 Trace: [music/query] performing album query
07/14 16:33:36 Critical: scx: System.ArgumentNullException: shared-query acquire must be attributed to a connection owner (Parameter 'owner')
at Sooloos.Broker.Query`3._AttributeTo(Object owner)
at Sooloos.Broker.Query`3.AttributeCreatingRef(Object owner)
at Sooloos.Broker.Music.LibraryApi._SharedOrNew[CONCRETEDATATYPE,DATATYPE](Byte[] sharekey, Object owner, Func`1 create)
at Sooloos.Broker.Music.LibraryApi._FinishQuery[CONCRETEDATATYPE,DATATYPE](Func`1 makecriteria, ResultCallback`1 cb_result, ClientContext clientcx, IEqualityComparer`1 eq, Byte[] sharekey)
at Sooloos.Broker.Music.LibraryApi.<>c__DisplayClass87_0.<AlbumQuery>b__0(ClientContext clientcx)
at Sooloos.SynchronizationContextThread._Dispatch(SendOrPostWrapper& ret)
I wonder if Sooloos.Broker.Query.AttributeTo(Object owner) failed to get an owner object from ClientContext due to JSON parsing oddity repoerted after today’s EA release:
I also see the error in my Roon logs:
07/14 12:39:46 Debug: JsonDecodeStrict failed: ‘0x7F’ is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
Going to try and downgrade to the previous Roon version and see what happens with the interaction between Server and Extension.
Prior to the latest production release of Roon and the EA1674 I felt the extension was working well. Then behaviour changed and I feel like I’ve been tripped up by changes Roon has made.
6 builds on from the last update which was because EA1674 caused a “few issues”. This is me firefighting and not my preferred way forward.
This will be the last update for several weeks. Family vacation from Friday.
Fixed
• Tapping an album no longer throws “the library just changed — close and reopen it.” The extension used to find albums by their position in Roon’s list, and adding music reshuffles every position. Now, if a saved position is stale, it looks the album up live by name through Roon’s own search (a single lookup, not a re-scan) — so an out-of-date snapshot never blocks opening or playing. (The v1.6.47 attempt at this was broken — it forgot to pass a “zone” to Roon’s search, which Roon requires, and its title-matching was too strict; v1.6.48 fixes both.) (NOTE: May not work )
• The extension stops fighting Roon while it’s importing. Earlier it would re-scan the whole library repeatedly on a 5-minute timer, hammering an already-busy Core. That’s gone.
Changed / Added
• New “stable snapshot” model. Roon owns the library; the extension scans it once, then only re-checks every 12 hours or when you press Rescan — and never scans while Roon is adding music. It detects an active import cheaply (reads the album count, waits a few seconds, reads again — a moving count means Roon’s busy).
“Rescan library” button added to the side menu. It rebuilds the snapshot on demand, but politely refuses (“Roon is still adding albums — try again shortly”) if an import is in progress.
• Better logging & diagnostics (from the earlier observability work, still in play): timestamped logs, Roon API call traces with timings, and the new live-search path logs each step ([album:search] …) so any remaining miss is a one-line diagnosis in docker logs.
Teaser: I’m working on another Roon extension as a separate entity. If it works well I’ll think about integrating it. Think shortcuts.
Hello @MusicD,
Thanks for this version.
Just a quick question: are you no longer on version E.A. 1674?
If so, how did you manage to change your server version?
Have a great vacation.
@MusicD, I am using Roon Optimized Core Kit Version 1.0 (build 257) Early Access on an Intel NUC7I7BNH barebone PC. I’m going to wait for the next Roon Server Software update and skip this Version 2.71 (build 1674) Early Access release, as it prevents me from using my favorite extensions: “TV:Remote” and “MusicD Remote”.
)
