mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
Genre tag is not used #55
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#55
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheSylus on GitHub (Oct 18, 2021).
Hi, my audiobooks have genres filled by mp3tag (Genre 1, Genre 2 and GENRE), but audiobookshelf does not use these tags.
Is this a bug or did I something wrong.
I am on 1.4.11 using Unraid.
Besides that, great tool.
@advplyr commented on GitHub (Oct 18, 2021):
I started setting that up but I didn't have any audiobooks that set those metatags, so I didn't test it.
If you could test it that would be great, and I will add it in the next release.
In the code here you can see the prober is checking if it found some other tags I was considering using, like genre, series, releasetime, etc., and it prints a log if it find one.
In order to test:
Hopefully you see this in the log:
heads up though, debug is going to dump out a bunch of logs.
@TheSylus commented on GitHub (Oct 19, 2021):
Hm, I dont see the log you posted.
The only Notable! is
Notable! file_tag_series, which refers to the series and is working fine.
Further, I see
[Book] Mapping metadata to key tagPublisher
[Book] Mapping metadata to key tagSubtitle
but nothing related to genres.
@advplyr commented on GitHub (Oct 21, 2021):
I added a dump of the raw audio file tags to make this easier to test in v1.4.13.
If you go to the track manager page and have experimental features turned on, you will see the "Check Track Numbers" button at the bottom.
We are looking for the key that is used for genre on you audio files.
@TheSylus commented on GitHub (Oct 21, 2021):
Okay, here we go.
"genre":"Science Fiction & Fantasy/Fantasy",
"TMP_GENRE1":"Science Fiction & Fantasy",
"TMP_GENRE2":"Fantasy"
These are the 3 genres I fetched from audible.
In my case, Genre2 would be the best. It seems that genre is just adding genre1 and genre2 which would lead to a alot of genres .
@advplyr commented on GitHub (Oct 21, 2021):
Interesting... have you tested other audiobooks?
Just taking in TMP_GENRE2 doesn't seem right, but also parsing "Science Fiction & Fantasy/Fantasy" wouldn't make sense either.
@TheSylus commented on GitHub (Oct 21, 2021):
So, I tested several audiobooks and I think both (Genre1 and Genre2) are correct. Most of the time it is up to the personal preferences.
So what to do?
I would suggest, we can use both genres. When I filter for fantasy books, the book would appear and in the case I filter for Science Fiction the books would come up aswell.
So we dont have a 1 to 1 relation, but a 1 to 2 relaltion and we dont lose any information.
In the case that someone uses just one Genre, it is also fine.
@advplyr commented on GitHub (Oct 21, 2021):
How would you handle "TMP_GENRE1" in the example you posted?
It would use "Science Fiction & Fantasy" as a single genre. Is that just mislabeled?
@TheSylus commented on GitHub (Oct 22, 2021):
I think that Science Fiction & Fantasy is just bad labeled.
However, I had a look at the mp3tag forum. TMP_GENRE1 and TMP_GENRE2 are mainly placeholder tags, which are used while scrapping from audible.com
Genre is a multi-value field, which is also used to have several genres. The separator is / , //, or ;
So my idea would be to use only "genre" and extract both genres and use them.
@advplyr commented on GitHub (Oct 23, 2021):
In
v1.4.14I included mapping the genre meta tag.I haven't actually tested this yet, but it should split the genre tag by the separators you showed.
Once I confirm this is all good I will put out a release and update the docs. The update is available now though if you get a chance to test it out.
@TheSylus commented on GitHub (Oct 23, 2021):
The logger shows:
Notable! file_tag_genre
However, for the same book the Genres is still empty when I click on edit book
and when I filter for genres, still no genres are listed.
@advplyr commented on GitHub (Oct 23, 2021):
I just pushed a patch and actually tested this time and it is working. If you open the edit modal to an audiobook and press re-scan it will re-map metatags now.
Just make sure that there are no genres on the audiobook you are re-scanning (dont forget to save after removing genres).
Let me know how that goes.
@TheSylus commented on GitHub (Oct 23, 2021):
It works perfectly fine. No issues at all.
Thx a lot
@advplyr commented on GitHub (Oct 24, 2021):
Included in release v1.5.0!