Option to display full ISO 8601 release date (YYYY-MM-DD) instead of year only

Feature requests
1

Feature description

Add an option to display full release dates formatted according to the ISO 8601 standard (e.g., YYYY-MM-DD or YYYY-MM) across album views, track details, and custom text rows on the Now Playing screen, rather than truncating them to display only the 4-digit year (YYYY).

Problem solved

Symfonium already parses full ISO 8601 date metadata behind the scenes to sort albums chronologically, but the UI compresses this information down to just the release year in most views. Users who meticulously tag exact release dates (including month and day) cannot see this detailed metadata in the interface without opening the track detail dialog.

Brought benefits

Fully utilizes existing, high-precision metadata already tagged in local files or media server databases.

Other application solutions

MusicBrainz Picard / Foobar2000: Native support for rendering full YYYY-MM-DD metadata.
Plex / Navidrome / Subsonic: API layers pass exact release dates, which desktop clients display fully alongside the album title or metadata headers.

Device type

Phone

Additional description and context

Since the backend parser already reads the full date string for chronological sorting, expanding the UI display options (e.g., adding a toggle under Settings > Interface or extending custom text row options) would make full date rendering available where supported by file metadata.

I searched existing feature requests

on

2

The app already supports displaying YYYY-MM-DD date format.

Which provider are you using? I know for Local Media, the provider settings have a toggle labeled “Prefer Year tag.” Make sure that is disabled, since it will do as it says–prefer year over the date.

If you’re using custom strings, try using %releasedate% instead of %year% (the latter will, of course, display just the year).

It’s been a while since I tested this… I think there may have been some funny behavior if you tag the date in the YEAR tag vs the DATE tag or something. I’ll check my own files and get back to you on that bit.

No issue with the tag reading. IIRC I had the YYYY in YEAR and the YYYY-MM-DD in DATE instead of RELEASEDATE. So that was user error on my part.

3

I’m such an idiot, i didn’t use %releasedate% string, i apologize.

1 Like