Difference between revisions of "User:Kepstin/Ideas:DR14 Meter"

From MusicBrainz Wiki
(New page: Similar to how Acoustids are currently handled, it would be nice to have an external database linking to musicbrainz that adds support for storing Pleasurize Music Foundation-compatible dy...)
 
Line 1: Line 1:
 
Similar to how Acoustids are currently handled, it would be nice to have an external database linking to musicbrainz that adds support for storing Pleasurize Music Foundation-compatible dynamic range values.
 
Similar to how Acoustids are currently handled, it would be nice to have an external database linking to musicbrainz that adds support for storing Pleasurize Music Foundation-compatible dynamic range values.
  
== Implementation Thoughts
+
== Implementation Thoughts ==
 
http://dr14tmeter.scienceontheweb.net/index.php?title=Main_Page is a free, open-source command line tool for calculating dr14 values. It could be hooked up with a picard plugin to allow submission and tagging. THis picard plugin could also make them available as internal tags (_release_dr14, _track_dr14)
 
http://dr14tmeter.scienceontheweb.net/index.php?title=Main_Page is a free, open-source command line tool for calculating dr14 values. It could be hooked up with a picard plugin to allow submission and tagging. THis picard plugin could also make them available as internal tags (_release_dr14, _track_dr14)
  

Revision as of 17:48, 21 August 2012

Similar to how Acoustids are currently handled, it would be nice to have an external database linking to musicbrainz that adds support for storing Pleasurize Music Foundation-compatible dynamic range values.

Implementation Thoughts

http://dr14tmeter.scienceontheweb.net/index.php?title=Main_Page is a free, open-source command line tool for calculating dr14 values. It could be hooked up with a picard plugin to allow submission and tagging. THis picard plugin could also make them available as internal tags (_release_dr14, _track_dr14)

Site must have an API to allow lookups by release mbid. Submissions would be by api key, probably with musicbrainz authentication (like acoustid). How to handle multiple varying submissions for one release? I like medians.

A userscript could be written to allow displaying DR numbers on the release group, release, recording pages. (This is the main draw, really.)