In addition, there are rare syncing issues where Plex does not reflect the Release Type on MusicBrainz.
I propose a Feature Suggestion, a single dropdown field that would allow for a manual Release Type edit. The new feature would probably require 20 or fewer lines of code.
I am looking at a single that is listed as a single internally in the metadata and is also listed as a single at musicbrainz but plex is insisting that it is an album. Canât do an override which is nuts.
Really need this. Grouping into singles and albums is worthless to me while the feature depends on third party data. I have a very large music library, and the groupings are just too hit and miss. I donât have the time to devote to submitting edits to Musicbrainz and just hoping theyâre accepted. I want to be able to categorise my own library.
I had no idea that paying for the Plex service required making personal sacrifices to perform volunteer work for an open metadata project.
A simple review of the voting system explains just how complicated the process is for committing a change. New users who submit change requests are impacted by multiple week delays. The voting system allows for a mass of uninformed users to revert changes back to an inaccurate state.
This is more like a bug than a feature request. Plex thinks anything not on MusicBrainz is an album. The release type is (one of?) the only field that canât be manually edited.
How come this isnât a more popular request? And how come it hasnât been implemented, yet? We should be able to edit and change release types manually.
COMPLETELY agree!! I abandoned PLEX as my music server several years ago because, with a really large library of music, it seemed it was waaaay too âbuggyâ. About a month ago, I decided to try it again and, so far, have been extremely impressed with how much itâs music library features/functions have improved. So far, the only negative aspect I have encountered that I feel MUST be fixed IS the inability to manually adjust/correct the ârelease typeâ categorization PLEX pulls from Musicbrainz. Itâs hard to believe that this wasnât built in from the beginning. Musicbrainz integration is really niceâŚBUTâŚitâs a public DB and without any local override, everyoneâs music library organization is at the mercy of every random and/or strange update that any user might make to a listing there. As of now, the only way users of PLEX can counter this involves a terribly inconvenient process of creating an account with Musicbrainz (So far have tried creating an account 4 times and, most recently, Iâve been waiting a week for an email verification process which, until that is done, no editing is allowed), make an edit, then wait a few days before the PLEX music library can be updated with the new infoâŚIFâŚanother edit wasnât made by someone else between the time the correction was made and my PLEX library refreshing to recognize the change. PLEASE PLEASE PLEASE!!! We need more local and manual control options for our own local PLEX music serverâŚespecially THIS one. Itâs got my vote for sure. #release-type
This would be cool as Iâve got a couple of releases in my collection that donât match up, even though theyâre correct on MusicBrainz (from what I can see). Itâs annoying when this happens, so way to override would be great.
Absolutely agree. In a data based system like Plex, EVERYTHING should be adjustable by the (admin) user. Only that way can Plex avoid all the ârequestsâ such as this, to fix a problem caused solely by our inability to correct data that someone else got wrong.
If a CD booklet uses stylization that goes against the standard English title capitalization rules, MusicBrainz says âtoo badâ. MusicBrainz requires proof of Artist Intent. The documented example was a band member performing an edit on their own work, claiming all tracks in the release should consist of only lowercase letters. The band member had to confirm the Release metadata was their intent!
Also, what? The booklet of my video game OST shows the intended capitalization. Why do I need to record an interview with the artist just to satisfy some archival junkie whose only goal is a one-size-fits-all uniform database?
Debates on MusicBrainz are riddled with cognitive biases. I will not apologize for declining membership to the collective. The need to vote on edits highlights a past filled with opinion-centered conflicts. If the rules which govern MusicBrainz were good enough for users to enforce them literally, there would be no need to vote. An edit would either be right or wrong, instead of a majority rule.
I feel bad for those who run the MusicBrainz project, though.
The community leaders are genuinely nice and want users to succeed, especially new users.
Is anyone up for a play debate while we wait for the feature rollout?
Edit This Title!
The internet's favorite "I am smarter than you, take this downvote you fool!" children's game!
Alright, everyone. The rules are simple. Edit the title of this video game OST and win the debate. Simply convince the community that your edit contains the one and only proper title. Your prize is a forced metadata push to everyone who uses Plex! Force your opinions onto others and become the smartest editor on the internet!
Here we go, get ready to... EDIT! THIS! TITLE!
Here are some submitted edits to get your brain ticking! Do not be afraid to judge any and all of them harshly. After all, these are not your titles unless you want them to be!
Perhaps the album art (back) can guide you. It makes sense, given the text on the sides of âbackâ was meant for people to read when the CD is stored on a shelf! Letâs see, it saysâŚ
Animal Crossing⢠Your Favourite Songs
Gross! Impose your distaste for weird unicode like ⢠by removing it!
Animal Crossing Your Favourite Songs
Now everything reads like word salad! Add some symbols like colons, dashes, and parenthesis. Go ahead and make the title yours⌠and everyone elseâs at the same time!
With a greater number of edits and years attached to your account, you can be a winner!
You can be the winner!
Welcome to metadata platforms such as MusicBrainz!