Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Album Record Label and Type from music files tags #10573

Merged
merged 2 commits into from Oct 1, 2016

Conversation

DaveTBlake
Copy link
Member

Albums have label and type fields that can currently only be filled by scraping from NFO files and maybe from online sources (?). Yet music files can be tagged with record label and release type information that could be used to populate these fields.

This adds processing of the LABEL (TPUB) and RELEASETYPE (MUSICBRAINZ ALBUM TYPE) tags and uses them to poplate the album library data. Both label and type fields are avaliable in smart playlist rules, so this extends the way that users can explore their music collection.

Note the album table also has a "releasetype" field, this is used internally to flag if the entry in the album table is a real "album" or a "single" e.g. a fake album created to cover all the singles by that artist. We must take care not to confuse the two.

…ote not the same as album.strRreleaseType that is used internally to flag the fake album entry used for singles)
@DaveTBlake DaveTBlake added Type: Improvement non-breaking change which improves existing functionality v17 Krypton Component: Music labels Sep 27, 2016
@MartijnKaijser
Copy link
Member

No db bump?

@FernetMenta
Copy link
Contributor

If this is no fix, and I don't see the fix label, I suggest to remove the Krypton label. DB changes are always risky and should be avoided on short final

@MartijnKaijser
Copy link
Member

i don't see short final happening soon with current issues popping up

@FernetMenta
Copy link
Contributor

FernetMenta commented Sep 27, 2016

we can focus on current issues and try to resolve them. if some of us try and others use this time to throw new risky code in, we'll never get somewhere.
we did agree on fixes only on devcon, didn't we?

@DaveTBlake
Copy link
Member Author

No db change needed guys, the data is already in the structure we just aren't filling it. Could call that a broken thing and this a fix rather than an improvement.

No risky code changes either, I know better than that for beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Music Type: Improvement non-breaking change which improves existing functionality v17 Krypton
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants