Recently Added Not Consistent with Navidrome

Issue description:

Recently added items (albums, artists) are correctly listed on Navidrome server (according to last modified file date I guess) but not consistent with Symfonium listing.

Symfonium listing is neither according to last modified nor created date of files. It seems completely random.

Symfonium probably doesn’t use file creation or modification dates, but maybe there’s a value in the subsonic db entries that could be used?

Logs:

Upload description: mi6logs

Additional information:

 

 

Reproduction steps:

 

 

Media provider:

Subsonic

Screenshots:

 

    

I need logs during a sync and reproducing the issue.

And preferably without being casting to UPnP as it spam the logs.

I uploaded a new log with the same tag during sync with local client activated. Hope this helps.

The sync fails due to your proxy so you do not have the last data.

Check your proxy and navidrome logs.

[993] 504  https://xxxx/rest/getGenres.view?u=REDACTED&t=REDACTED&s=REDACTED&v=1.13.0&c=Symfonium&f=json (90052ms, 164-byte body)
2024-06-30 14:31:43.990 Verbose/SubsonicLogger: <-- [993] <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>openresty</center>
</body>
</html>

2024-06-30 14:31:43.992 Error/SubsonicLogger: Request Error: 504 [<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>openresty</center>
</body>
</html>
]

I uploaded the logs again with tag mi6logs. I removed and re-added the media source (subsonic) and it’s scanning without problems:


Progress:

Then check the result when it’s finished and report back.

1 Like

Are user and password submitted in the api request stored in the logs?

No you can check yourself :slight_smile:

1 Like

Off topic: is this site based on xwiki?

Synced 100%, recently added data still inconsistent.
Update sync also works.
Uploaded logs again during update sync.

Could it be that Symfonium doesn’t use recently added data from the media source (e.g. Navidrome) but creates its own on every source update scan? This might result in inconsistent data for the initial scan, but media added later would probably be consistent…

Your server returns mostly the same date for all albums as date created, probably the date of the scan.

 "created": "2024-06-27T02:00:03.580658696Z",

I think there’s options in Navidrome to control the behavior.

@deluan probably knows more.

1 Like

In 0.52.5 at least, Album.Created is the oldest Birth date of all its songs. If Birth date (time the file was created in the FileSystem) is not available, it uses the time it was imported the first time.

1 Like

So apparently this was discussed in Sort by date added not working correctly with navidrome. Is there now a generic endpoint solution?

@deluan also if I may ask - I just create a simple read-only docker volume for the media files, and if, obviously, the ‘created date’ isn’t taken over by Navidrome, do I have to provide the media files with a specific volume type, such as, NTFS, or EXT4 in the docker container?

I’ll be happy to move this last issue over to Navidrome forums, if you want.

So apparently this was discussed in Sort by date added not working correctly with navidrome. Is there now a generic endpoint solution?

AFAIK, nothing changed since that message. This behaviour may change in the upcoming Navidrome refactor, which will separate BirthTime from CreatedAt.

@deluan also if I may ask - I just create a simple read-only docker volume for the media files, and if, obviously, the ‘created date’ isn’t taken over by Navidrome, do I have to provide the media files with a specific volume type, such as, NTFS, or EXT4 in the docker container?

I don’t know the answer for that, but it may be worth discussing this with other users. You may get more answers posting this on Discord than as a GH Discussion, but feel free to do both :slight_smile: