User:MClemo: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(43 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{| border="1"
{| border="1"
| MusicBrainz: [http://musicbrainz.org/show/user/?username=MClemo MClemo]
|-
| MB: Editor:MClemo | IRC: MClemo | Last.fm: [http://www.last.fm/user/MClemo/ MClemo]
| Last.fm: [http://www.last.fm/user/MClemo/ MClemo]
|}
|}

==Software==

* [[User:MClemo/flac2foo|flac2foo]]: Transcode flac files to mp3, ogg or aac.


==References==
==References==


* Edits
* Edits
** [http://musicbrainz.org/show/edit/?editid=7830244 edit #7830244]: Featuring artists in track names.
** [http://musicbrainz.org/show/edit/?editid=10757908 edit #10757908], [http://musicbrainz.org/show/edit/?editid=10971039 edit #10971039] & [http://musicbrainz.org/show/edit/?editid=10761962 edit #10761962]: Removing classical releases of very low quality.
** [http://musicbrainz.org/show/edit/?editid=10757908 edit #10757908] & [http://musicbrainz.org/show/edit/?editid=10761962 edit #10761962]: Removing classical releases of very low quality.


==Edit note templates for edits of other editors==
==Edit note templates for edits of other editors==


===Add Release: No proof, no release event===
===Add Release (no vote): No proof, no release event===


<nowiki>
<nowiki>
Please provide some information that what you are adding has been actually released somewhere. See [HowToWriteEditNotes] about how to write proper edit notes with such proof. I will change my vote after your release has been verified.
Please provide some information that what you are adding has actually been released somewhere. For example, information about release date, label, barcode, or catalog number can be proof itself or lead to good proof. See [How_To_Write_Edit_Notes] about what constitutes good proof and how to write proper edit notes. I will change my vote after your release has been verified. Thanks!
Also, a [ReleaseEvent] with information about release date, label, barcode and catalog number can be proof itself or lead to good proof.
</nowiki>
</nowiki>


==Picard: File Naming==
==Edit note templates for my edits==

===Remove Release: Very low quality classical releases===

<nowiki>
No edit notes, no release event, no ARs. For classical this makes the release unidentifiable (no performer info). See edit #10757908, edit #10971039, and edit #10761962 for lengthy discussions why those releases are not worth staying in the database.
</nowiki>


My file-naming scheme for Picard:
===Remove Release Group: Empty release group due to clean-up of very low quality classical releases===


<nowiki>
<nowiki>
$if($in($lower(%genre%),classical),+ Classical +)/$if($or($eq(%releasestatus%,promotion),$eq(%releasestatus%,bootleg)),+ %releasestatus% +,)/$if($or($eq(%releasetype%,soundtrack),$eq(%releasetype%,audiobook)),+ %releasetype% +,)/$if($eq(%albumartistsort%,Various Artists),+ VA +,%albumartistsort%)/%album%$if(%_releasecomment%, \(%_releasecomment%\),)/$if($gt(%totaldiscs%,1),disc %discnumber%,)$if(%discsubtitle%,_ %discsubtitle%,)/$num(%tracknumber%,2) - %artist% - %t
Empty release group due to removing low quality classical release that was once in this release group.
</nowiki>
</nowiki>


It relies on Picard 1.2 and that the feature of folksonomy tags is enabled for your own tags. It enter the tag 'classical' with classical releases in the MusicBrainz web interface at the page of the release. Now, my file-naming scheme puts all classical releases in one folder. Further, promotion releases, bootlegs, soundtracks, and audiobooks go into their own folder. For releases with several discs, files for each disc go into one folder.


{{lang de-native}} {{lang en-fluent}}
[[Category:Bio]]
[[Category:Bio]]

Latest revision as of 13:24, 22 May 2016

MusicBrainz: MClemo Last.fm: MClemo

References

Edit note templates for edits of other editors

Add Release (no vote): No proof, no release event

Please provide some information that what you are adding has actually been released somewhere. For example, information about release date, label, barcode, or catalog number can be proof itself or lead to good proof. See [How_To_Write_Edit_Notes] about what constitutes good proof and how to write proper edit notes. I will change my vote after your release has been verified. Thanks!

Picard: File Naming

My file-naming scheme for Picard:

$if($in($lower(%genre%),classical),+ Classical +)/$if($or($eq(%releasestatus%,promotion),$eq(%releasestatus%,bootleg)),+ %releasestatus% +,)/$if($or($eq(%releasetype%,soundtrack),$eq(%releasetype%,audiobook)),+ %releasetype% +,)/$if($eq(%albumartistsort%,Various Artists),+ VA +,%albumartistsort%)/%album%$if(%_releasecomment%, \(%_releasecomment%\),)/$if($gt(%totaldiscs%,1),disc %discnumber%,)$if(%discsubtitle%,_ %discsubtitle%,)/$num(%tracknumber%,2) - %artist% - %t

It relies on Picard 1.2 and that the feature of folksonomy tags is enabled for your own tags. It enter the tag 'classical' with classical releases in the MusicBrainz web interface at the page of the release. Now, my file-naming scheme puts all classical releases in one folder. Further, promotion releases, bootlegs, soundtracks, and audiobooks go into their own folder. For releases with several discs, files for each disc go into one folder.