musicbrainz
Here are 128 public repositories matching this topic...
-
Updated
Mar 20, 2018 - CoffeeScript
When using Subsonic (or compatible server), a scrobbler can be configured in personal preferences. This means that you can configure the scrobbler once and supported clients will use it. The client-side configuration is as simple as checking a box. The client starts playing a song and the Subsonic server takes care of sending the info to the scrobbler service. In Airsonic, ListenBrainz and Last.fm
-
Updated
May 21, 2020 - Perl
-
Updated
May 20, 2020 - Python
-
Updated
Apr 25, 2020 - JavaScript
-
Updated
May 19, 2020 - C#
-
Updated
May 15, 2020 - JavaScript
-
Updated
Apr 11, 2019 - JavaScript
-
Updated
May 6, 2020 - Python
-
Updated
Aug 5, 2017 - Perl
-
Updated
Jul 4, 2019 - Scala
Not a new issue but it's true that it is done very crappy that it warns you for each step for each recording instead of only once and break the mass click (which is difficult to do, though).
https://community.metabrainz.org/t/merge-duplicate-recordings-between-two-editions-of-the-same-album-with-mb-mass-merge-recordings/203168/54?u=jesus2099
-
Updated
Mar 2, 2019 - Python
-
Updated
Sep 3, 2019 - Go
-
Updated
Apr 25, 2020 - JavaScript
-
Updated
Jan 30, 2020 - Swift
Implement browse function for
- Artist
- Implementation
- Unit tests
- Documentation
- Label
- Implementation
- Unit tests
- Documentation
- Recording
- Implementation
- Unit tests
- Documentation
- Release
- Implementation
- Unit tests
- Documentation
- Release Group
- Implementation
- Unit test
-
Updated
May 6, 2020 - Python
-
Updated
Dec 23, 2016 - PHP
-
Updated
Feb 3, 2018 - Haskell
-
Updated
Apr 12, 2020 - PLpgSQL
-
Updated
May 20, 2020 - Java
-
Updated
May 9, 2018 - Go
Improve this page
Add a description, image, and links to the musicbrainz topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the musicbrainz topic, visit your repo's landing page and select "manage topics."


Some of our wiki pages are outdated. User manual or developer guide type information should move into the sphinx docs for better visibility and so that it's versioned with the code. I think it makes sense to use the wiki for longer-term planning or planning of big changes, with the target audience being beets contributors. Where possible smaller plans can go to issues on beets with appropriate lab