current Problem

Status: This Page is Glorious History! The content of this page either is bit-rotted, or has lost its reason to exist due to some new features having been implemented in MusicBrainz, or maybe just described something that never made it in (or made it in a different way), or possibly is meant to store information and memories about our Glorious Past. We still keep this page to honor the brave editors who, during the prehistoric times (prehistoric for you, newcomer!), struggled hard to build a better present and dreamed of an even better future. We also keep it for archival purposes because possibly it still contains crazy thoughts and ideas that may be reused someday. If you're not into looking at either the past or the future, you should just disregard entirely this page content and look for an up to date documentation page elsewhere.

Status: this page was hardly edited in years. The community has changed, and so our means to track defects. We now use trac. Maybe this page may be revived if more WikiZens are willing to keep it up to date. Right now, it's barely history... or even DeletedPage. At the very least badly NeedsUpdating. -- dmppanda 15:16, 19 February 2008 (UTC)

Current Problems

MusicBrainz, like any application, has some problems that cannot be resolved with a simple bugfix or implementing an idea from the NewFeatureSuggestions. In order to plan FutureWork, it is important to understand these problems and how users work around them now. Once we understand the problem better, a FeaturePage can be added and linked into the FutureWork list.

• Please don't add a lot of discussion on this page -- add it to the pages linked below (or their Discussion pages, if any). For simple problems, it is better to file a bug report -- this page is intended for general or complex issues that will require significant related work to address.

• The MusicBrainz server and client interfaces use a lot of BadTerminology that is confusing (especially to new users); while this Wiki has mostly been updated to use clearer terminology, it hasn't migrated to the rest of MusicBrainz.
• One problem that many people run into is that when they make corrections to the database, the changes are not immediately applied, and they end up WaitingForModerations to be approved before the tagger can be used to update tags on music files. This problem also encourages LazyUsers to enter DuplicateReleases or phony NonAlbumTracks.
• With the increased popularity of MusicBrainz, the number of TrmCollisions has dramatically increased, and as a result the effectiveness of TRM matching is reduced. The PicardTagger is expected to help with this problem, but ultimately the TRM system might have to be abandoned: see GettingRidOfTRM.
• The TrackNumber0Glitch, logged as bug number 834541 causes the tagger to return a track number of 0 if multiple TRM hits are found on a single release.
• There has always been a tension in MusicBrainz between QualityVersusQuantity, with some people favoring QualityImprovements and others believing that a more open system can provide both QualityAndQuantity. While the ReleaseLockingDiscussion has some specific proposals, this is a dialectic that will continue to exist as long as MusicBrainz does.
• Another chronic problem with MusicBrainz has been the VotingBacklog, where there are too many open edits for all of them to be voted on. Now that the system accepts changes with no votes after a one or two week period, this is less of an issue, but it would not be surprising if this re-surfaces in the future.
• Finally, VariousArtistsReleases, due to their different implementation in the database, suffer from a number of usability problems; from not being able to EditAll information at once, to the fact that VariousArtists has no subscribers (and as a result changes to such releases are rarely voted on).

The current bugs list may also contain other problems that should have an entry on this page.