Flest 9 Posted March 29 Posted March 29 Description of Issues: 1. Improper Metadata Mapping for Sorting and Series Tags The server ignores existing sorting tags even when they are duplicated in multiple industry standards (Apple/iTunes) for compatibility. Specifically, the server fails to recognize: Apple tags: series_apple_name / series_apple_index iTunes tags: series_itunes_name / series_itunes_index MediaInfo field: Album/Sorted by Current Behavior: Instead of reading these fields, the server defaults to copying the Title value into the Sort Album field, which breaks the correct sorting order for book series. 2. Book Overview Mapping Error The book summary (annotation) is read only as "Track" metadata. The main "Book" (Album) page remains empty. Current Behavior: In the case of .m4b files (one file = one book), the description is visible within the track info but is not mapped to the book’s overview page. 3. Date Parsing Error (Timezone Offset) The server applies a timezone offset when reading the "Year" tag. Current Behavior: If a file has a date set to "01.01.[Year]", the server's UTC offset often pushes the date back to "31.12.[Year-1]". Expected Behavior: The year should be read as a static value, ignoring the server's local time or timezone settings. 4. Complete Ignore of Local NFO Files This is the most critical issue. The server completely ignores existing .nfo files located in the book folder during the initial library scan. Current Behavior: Even if a user provides a correctly formatted NFO with fixed tags and collections, the server bypasses it and creates its own database entry containing the errors mentioned above. This makes external automation via scripts impossible. Expected Behavior: NFO Priority: If an .nfo file is present in the directory, its data must take priority over automated scraping. Tag Support: Full support for Apple/iTunes series and sorting tags. Proper Mapping: Automatically mirror the track description to the book overview if the album contains only one file (common for audiobooks). Static Date Parsing: Read the release year without applying timezone shifts. Environment: File Format: .m4b / .mp3 Metadata Tool used: MediaInfo / Mp3Tag / Tone
Luke 42797 Posted 11 hours ago Posted 11 hours ago @Flestnfo support is currently in testing. you can participate here: Thanks !
Luke 42797 Posted 11 hours ago Posted 11 hours ago Quote 3. Date Parsing Error (Timezone Offset) The server applies a timezone offset when reading the "Year" tag. Current Behavior: If a file has a date set to "01.01.[Year]", the server's UTC offset often pushes the date back to "31.12.[Year-1]". Expected Behavior: The year should be read as a static value, ignoring the server's local time or timezone settings. @Flestdo you have client devices in different timezones than your server? Assuming timezones are set correctly on all devices, this really shouldn't be a problem.
Flest 9 Posted 57 minutes ago Author Posted 57 minutes ago If I understand correctly, the issue is that some software writes a release date for 2010 as 01.01.2010. But if the time zone isn't UTC+0 (say, it's +6), the server shifts the time back by 6 hours. So instead of 00:00 on 01.01.2010, you end up with 18:00 on 31.12.2009. That’s why in my script I started writing 2010 as 01.07.2010 ))))))
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now