"Recently added albums" doesn't update fast enough (subsonic provider)

Issue description:

When I add an album to my subsonic server, it doesn’t show up in Symfonium for quite some time. I haven’t really been able to figure out exactly what causes it to finally show up, but it often seems to take hours, and there appears to be no way to “force” a refresh.

Other clients do show the new album immediately, so I know it’s not a server-side issue.

I’d be okay if I needed to do some kind of manual refresh, but haven’t found a way to do that either. Obviously better would be if it just showed up right away.

Thanks!

Logs:

Upload description: nick-logs.for.recent.issue

Additional information:

 

 

Reproduction steps:

 

  • Configure a subsonic server
  • Connect to it with Symfonium
  • Add an album
  • Observe it doesn’t show up in Recently added albums
     

Media provider:

Subsonic

Screenshots:

     

Have you tried he docs ?

Symfonium auto sync on some events when here’s song count change, but if he app is never killed by the OS and your network status does not change then the verification are a lot more rare.

Thanks, “sync” does help. I didn’t find it because I was searching for “update” and “recently added”.

However, sync takes a pretty long time. Order minutes for it to notice new albums, and over an hour to fully finish. That’s quite long to wait for something that subsonic has a dedicated api for which will return the list in under a second.

Additionally, it’s not obvious to me how I can cancel the sync, so if I add another thing in that hour, I have to wait and then start all over again.

I get that symfonium is trying to support lots of providers. But as a “subsonic player” this makes it fall rather short. Just a simple “refresh recently added” that polled that API would help a lot. It’s a quick api call, it could probably even happen every time you redisplay that page. That’s what most subsonic clients do.

I love lots of the other features, but I add new stuff to my library enough that this will be difficult to live with.

Symfonium is offline first it’s not an issue of making calls …

And sync should be fast unless you use an outdated server that requires compatibility mode.

There’s no other client like Symfonium and Symfonium can’t act like “other clients”, so if you can’t change your server to something that works better, then the app is probably not the proper one for your needs.

Do you have a list of servers that support or don’t support fast sync, or can you let me know how I can check?

I agree, if Symfonium is a bad subsonic client, it’s probably not the right thing for me since I use subsonic. But you’ve choosen to add subsonic as a media provider, so maybe you’d rather be a good subsonic client.

You are funny :wink: For the record I created OpenSubsonic to enhance all subsonic servers via a better API surface. So no it’s not a bad Subsonic client, it’s a client that requires up to date servers to be able to perform better …

There’s documentation about all subsonic servers in the well documentation

Recommended are GitHub - navidrome/navidrome: 🎧☁️ Your Personal Streaming Service and GitHub - epoupon/lms: Lightweight Music Server. Access your self-hosted music using a web interface.

Cool! Thanks for making OpenSubsonic.

I’m using Ampache 7 which does have the opensubsonic extensions. I also verified I do not have “Compatibility Mode” enabled for this provider.

I verified that https://my-server/rest/getOpenSubsonicExtensions.view returns:

{
    "subsonic-response": {
        "status": "ok",
        "version": "1.16.1",
        "type": "ampache",
        "serverVersion": "6.6.7",
        "openSubsonic": true,
        "openSubsonicExtensions": [
            {
                "name": "formPost",
                "versions": [
                    1
                ]
            },
            {
                "name": "transcodeOffset",
                "versions": [
                    1
                ]
            }
        ]
    }
}

But I still see sync taking multiple minutes for the first bit (getting Artists, Albums, Tracks), and then close to an hour for “Gathering metadata”.

Any idea why it would still be so slow?

Probably some issues with getArtistInfo2 but no logs no chocolate;)

You can disable the additional artist metadata fetch on the provider settings, it should only be run once per artist.