- 1 Me
- 2 MusicBrainz
- 3 MusicBrainz Philosophy
- 4 MusicBrainz Editing
- 5 Musicology
- 6 puid_submit.py
- 7 Dev Stuff
I'm BrianFreud on the site and in IRC. My Profile: Editor:BrianFreud
You can find also me at last.fm.
I edit a lot. I'm tend to work on classical these days. I've written some search plugins for PicardQT, I help handle the MB info/support requests, and I've done some (very) minor bug fixing on the server code.
Currently rereading Cathedral and the Bazaar for the 20th or so time. I`d suggest autoeditors reread the Homesteading section, mapping "editor" concepts to "hacker" there... Beyond the stated concepts, there's plenty to work with when the theories are mapped to a data contribution level, rather than leaving it merely at the code contribution level. I'm considering writing a response/followup on this. Also, for the next section, something for me to look at more later, when I have the access to do it: He describes code contribution as breaking the TotCommons concept because it causes the grass merely to grow taller. However, I wonder if MB demonstrates (due to the sheer size of the db, even when compared to the size of a Linux-sized codebase) how this is not really so? If you consider the editor/edit count/voter/much lower amount of voting issues we're always trying to solve, is it perhaps more that the grass doesn't just grow taller, but rather than the commons area simply grows progressively larger? Extending the metaphor, an ever larger commons does indeed provide ever more room for sheep to graze... but it also requires an ever larger amount of effort to ensure that the commons itself is maintained (or to breed the larger numbers of sheep that the commons can now support). Is there any research or anything written in game theory which might suggest potential solutions for us in such an Anti-TotCommons situation as we seem to face? (Ever larger areas of grass, but not enough breeding of sheep such that there remain sufficient numbers of sheep to keep the grass from growing too thick and choking itself by overgrowth - ie, ever more edits, in an ever increasing breadth of covered area, but not enough editors also becoming at the same time voters, esp considering that in a best possible world, we need not 2% of editors to be voters, but rather, 300% of editors to be voters?) Wiki's solution (delete low-interest/data amount pages) obviously would be terribly bad for us, so can we find some alternate solution? - -- BrianSchweitzer 05:05, 09 October 2008 (UTC)
I play the alto, tenor, and baritone saxophones, as well as the recorder. I also sing tenor II; typically classical, chamber, or barbershop - though karaoke is fun too. ;)
I'm into soundtracks, Nirvana, R.E.M., Led Zeppelin, Mozart, Tori Amos, jazz, and just about anything else...
...except for gospel, Christian contemporary, "hate" music, and country - except maybe for Willie Nelson.
- In no particular order...
Just about any release of Mozart's Requiem, though I much prefer the Sussmayr version to any of the others.
- Only exception is the 1945 Berlin, Germany Nazi recording, which just sounds incredibly overpowered, and lacks finesse.
Thomas Newman's soundtrack to The Shawshank Redemption
- The perfect work for a rainy day - or a day you wish it would rain, and need your spirits lifted. (I've also pretty much memorized every line of the movie)
- Even as a soundtrack fan, this is one of the few soundtracks I can put on repeat play all day, and still enjoy it at the end of the day. Just a very powerful work. This version is missing Brian Eno's Prophecy Theme, which is the one negative, so sometimes it's nice to alternate this version with the shorter version, which includes that track. (And yes, I do have this movie memorized as well.)
Aphex Twin's Milkman, on the Girl/Boy EP
- First time I heard this track, I started laughing so hard, I nearly crashed my car. It's still able to make me break out laughing all these years later...
- Not nearly as well crafted as the Aphex Twin song, but again, one of the few songs that can always make me smile.
Projects I need to do
- Revised OTR RFP
- Revised ChangeDataQualityProposal
- CSGStandard/Chopin: Complete List, in correct CSG style, of every single work by Chopin
- CSGStandard/Mozart: Complete List, in correct CSG style, of every single work by Mozart - done, just error checking now
- trying to get a "changed name to" AR added
- Varèse Sarabande
- X-Ray Dog Music, Inc. - one more release and it's done, yay!
- The rest of Trailer Music:
- All of 300 Years Later
- All of 615 Music
- All of Ars Arcana
- All of Audio Machine
- All of Beat Box Music
- All of Brand X Music
- (Figure out the label for the Brand X / Music Box Music release)
- All of Cinetrax
- The rest of of Corner Stone Cues
- All of Director's Cut
- All of Epic Score
- All of Future World Music
- All of Groove Addicts
- All of Hybrid
- The rest of Immediate Music
- All of Justin Durban
- All of Media Ventures
- All of Music Junkies
- All of Musikvergnuegen
- All of Non-Stop Music
- All of ParodiFair
- All of Pfeifer Broz. Music
- All of Picture Perfect Music
- All of QFactory
- All of QL Music
- All of Position Music
- All of Riptide Music
- All of Teargas & Plateglass
- All of Two Steps From Hell
- All of West One Music
- The rest of Trailer Music:
- Keeping new bootleg add edits clean - There's no good way currently to search for these
- Keeping new soundtrack add edits clean - There's no good way currently to search for these
MusicBrainz Projects of Interest
- ArtistPageRedesign ArtistPageRedesign/ScreenShots
- XHTML 1.1 revamp / code cleanup
This will probably be a continually morphing part of this page. I so enjoy most of what goes on here. Music ought to be about emotion, enjoyment of the experience. This database, it's a collection of information, but also a gathering ground for music fans from all of the world and all different types of music. This is great, as we get all sorts of diversity.
In a way, though, it's also a bad thing. We have so much diversity, but seem to have so little communal spirit. The bigger projects - PicardQt, supporting MusicBrainz itself - those get everyone behind them. But smaller things, like voting, learning the styleguides completely, group projects... they seem to often be forgotten. With 3000 editors editing each day, even with 17 thousand edits open, we ought to be able to clear the database quickly. No open edit ought to have a reason to be unvoted in or out - let alone slip into the database without ever even having had a single vote cast on it. Even if people abstain on half the edits they see, it's still only a handful each day, and we who like to vote would be left begging for more editing. I don't know how to fix it though; it just saddens me to see so much editing, but so little voting.
Projects like my Nirvana project, or the Collaboration of the Month, have problems as well. Suddenly there's a mass of edits all in one place, scaring the subscribers to that artist. Or there's complex decisions to be made on how to interpret the works of an artist, but not enough people, or at least, not enough people talking together, to be able to come to resolutions about those questions. This leaves these types of projects either burning out, as the editors tire of the project, or they blow up, as new editors come in and disagree with the resolutions to the complex problems, viewing them without the perspective gained from the deep exploration into the issues involved. Again, I don't know how to solve this.
Last, the RFP process seems, well, kind of broken. Again, we're all pushing the ship, but everyone's pushing it in different directions. There's several style proposals that are now going into their third year as a proposal, seemingly stuck there. There's style guidelines that literally end mid-sentence, unresolved. Then there's the RFP's that just kind of get lost, a few comments then forgotten. And, though this at least is fixable, it's pretty much all on the wiki - but we seriously need to get this thing into shape, as so many guidelines are basically hidden, unless you know just where to look for them... which brings us right back to the learning the guidelines.
Anyhow, I don't know the answers. I'm swimming in the same pool as everyone else, just trying to find a ledge to stand on. My edits sometimes seem to have a knack for drawing controversy, and I wish that weren't so. But I'll keep muddling on, trying to keep my balence, trying to make this place, as well as the database, a better place than it was when I got here... and no, I'm not leaving. No matter how much chocolate anyone offers. :)
Some of the editors I'm inpressed by, new and old...
- A partial list of people I've run into who just seem to "get" what MusicBrainz is all about... * Editor:aCiD2 * Editor:bogdanb * Editor:bplatt * Editor:Citizen * Editor:cooperaa * Editor:daydreamer * Editor:dmppanda * Editor:drsaunde * Editor:Gecks * Editor:gfmorris - Generally doing a nice job with bootlegs * Editor:grenzelm * Editor:Jugdish * Editor:kuno * Editor:Liff * Editor:lukz * Editor:mo * Editor:-nils- * Editor:PhantomOTO - Seemingly importing the entire metal database :) * Editor:SenRepus * Editor:Shepard * Editor:thewilkybarkid * Editor:xrayx * Editor:zos18
Editors to keep an eye on
- Editor:DSHEPHERD - Almost 400 releases added, nary an edit note, and 30%+ duplicates or bogus
- Editor:blogmusikst1 - Lots of releases added and changes made, ignores style, no edit notes. (Added by voiceinsideyou as a plea for help :p )
- Editor:GeorgeWChubby - ARGH!!!!
- Editor:yoyox - Incredibly sloppy freedb importing, never an edit note, doesn't seem to know ANY of the guidelines
- Editor:siren313 - A.k.a. Apraxia and overly possessive of (t)his artist name.
Edits for follow-up
Useful MusicBrainz Wiki Pages
Useful Reference Pages
How to make puid_submit.py work on Windows:
- First install python. Specifically, you want version 2.4.4 not version 2.5.
- Now snag the puid_submit.py script from luks' page here in the wiki.
- Now snag a copy of OldPicard (0.7.2) and install it.
- Move puid_submit.py to an empty directory.
- Move every file in the Picard 0.7.2 directory except picard.exe (which you can delete) and library.zip (which you will need) into the puid_submit.py directory.
- Unzip library.zip into the puid_submit.py directory - make sure you keep the directory structure from the zip file. (You can then delete library.zip.)
- Open a command prompt. Run "chcp" and note which active code page it tells you you are using.
- Open puid_submit.py in a text editor.
- In puid_submit.py, change the line "server = 'test.musicbrainz.org'" to read "server = 'musicbrainz.org'".
- In puid_submit.py, change the username and password lines to your MusicBrainz username and password.
- In puid_submit.py, change the line "encoding = 'utf-8'" to read "#encoding = 'utf-8'".
- In puid_submit.py, change the line "encoding = 'windows-1250'" to "encoding = 'cpxxx'", where xxx is your active code page. (So if your code page is 437, you would use cp437.)
- Save your modified puid_submit.py.
- Now, from a command prompt, change directory to your puid_submit.py directory. Run "puid_submit.py c:\foo" where "c:\foo" is your music directory.
- Get coffee and wait many many hours for puid_submit.py to finish.
True back-of-the-napkin planning! :D