A big Thank You!

I just wanted to offer a HUGE thank you to g0llum a.k.a. Keschte for all the tedious work he did in updating a number of pages (well over 100) to reflect the change in verbiage from “album” to “release” and “moderate” to “edit”. This was very time consuming work and he tackled this project along … Continue reading “A big Thank You!”

I just wanted to offer a HUGE thank you to g0llum a.k.a. Keschte for all the tedious work he did in updating a number of pages (well over 100) to reflect the change in verbiage from “album” to “release” and “moderate” to “edit”. This was very time consuming work and he tackled this project along with all of his other efforts including making our site comply with web standards. If you see him on IRC be sure to tell him thanks and give him a big virtual hug.

I’d also like to thank MRudat for also being a busy bee and making lots of little edits and interwingling pages. Every little bit helps.

To everyone else contributing, thank you.

wolfsong

IRC Meeting, what's up with Musicbrainz

This is to expand on Don Redman’s post. (click on word post to visit it) First of all, I would like to take the time to say thanks (in no specific order) to ruaok, luks, g0llum, donredman, yalaforge, dave evans, shepard, tarragon, nikki, inhouseuk, the board of directors, Dan Appleman, Fred von Lohmann, Randy Heinig, … Continue reading “IRC Meeting, what's up with Musicbrainz”

This is to expand on Don Redman’s post. (click on word post to visit it)

First of all, I would like to take the time to say thanks (in no specific order) to ruaok, luks, g0llum, donredman, yalaforge, dave evans, shepard, tarragon, nikki, inhouseuk, the board of directors, Dan Appleman, Fred von Lohmann, Randy Heinig, the sponsors, those on the top moderators list (both voters and editors) as well as countless others that built the database, refine it and help make it a great place to visit and tweak.
(no, this is not an academy award acceptance speech. ;0) )

Luks is now the keeper of picard, wow, big responsibility! Remember it’s a free program and still in beta. It has growing up to do, but isn’t it great we have the ability to utilize it now, instead of after everything is polished? That’s part of beta testing. All these people get is the bugs, they need some support and love along the way! Good job as far as I’m concerned. It’s constantly developing to a more stable and useable product.

As far as the community goes. There is first a question as to what Musicbrainz purpose is. Is it a tagger, is it a repository for information on music, is it ???. I personally feel this was best summed up by ruaok

“I think our goal needs to be a comprehensible music encyclopedia with a killer tagging app.”

So that in mind, I’m taking the initiative to sum up the chat and try to define a few things, while also getting some of the community to sit back and realize a few things.

First and foremost; This is a community! We all strive to help make it work and grow. If all you are doing is pestering for something new realize developement takes time! Either we can push for some half baked fixes, or we can be patient and wait a little while for a shiny near perfect database we all have been trying to envision and some souls have spent a lot of time and effort to perfect and create for those others of us less capable in programming or lacking in time to help.

There are numerous ways to help and join the community.

  • monetary contribution
  • which keeps musicbrainz on the web for all of us.

  • coding
  • which helps development of applications and will develop the new schema. Which I might add, will implement changes making obsolete many issues which are argued to death on the mailing lists at this time.

  • watching the issues
  • ordering them in a sensical fashion, guiding implemention of small changes where possible, as long as it doesn’t require code changing.

  • wiki work
  • helps new users better join in the advancement of the community.

  • Voting
  • helps to insure correct data is being put into the database

  • Editing
  • correcting in accuracies in the current data.

    So, there are many ways you can become an active, cherished participant of the community. Virtually, if you don’t like the way things are going, please, join us and help us improve it! But, be patient and always realize people are giving what they can to our project, which is improving with each line of code, each vote, and each piece of data corrected.

    Another thing to remember, these are people behind these names. People with lives, people with difficulties beyond your need to tag your audio file, or your desire to look at one page and have it perfectly laid out to your specifications. They get sick, they feel let down when they’ve spent hours, days, weeks, months on developing something and all they can hear is, that’s nice, I want this, or I want more. Or, worse of all, that’s crap, I don’t like it. Yes, bugs are important to be pointed out! Please provide answers, suggestions, if you have no idea of a suggestion, maybe you need to just file a trac ticket and walk on. Neutrality is a very good trait to embrace. Look from your own view, but look from theirs too.

    Coming soon is an update to give those in the community an idea of what is being done. What to expect, and a highlighting of those people in the project that aren’t as apparent from an average musicbrainizens point of view.

    Don Redman already gave a link to the log for anyone to read for themselves. I ask and close to demand those in our community sit back, relax and let some of the behind the scenes work progress. Or, better, become a part of the team, and help us develop what we are working toward, the great improvements rather than having our coders attempting to please the masses and direct their time to less important things that have been endlessly discussed and looked into. Ultimately leading to the developement time being taken away from those greater visions that aren’t too far around the corner!

    You can also greatly help by digging back through the archives and chat logs. It’s likely there has been a discussion already about what you’re seeking to have implemented.

    The more initiative you take, the more you will be involved and part of our community. Surprisingly, the community is very open and willing to help those that desire to help improve our community. The more complaining without answers, without constructive criticism, the more likely those people that support the community the most will not desire to be spending as much time in development, or will become bitter, or will need a break from this. Ultimately, would that be better? I don’t believe so. That’s my two cents, and thank you, once more to all the above I listed. I totally appreciate what Musicbrainz provides for my desires and I look forward to the future!

    Nyght aka Beth

    What's going on in the MusicBrainz community these days?

    There was a very good talk about the state of the MusicBrainz community and the plans for future development on irc just now. It went from 20:03 to 21:52 on 2006-05-04. It started with a kind of rant by Wolfsong, developed into a discussion about what is going wrong in the MusicBrainz community these days, … Continue reading “What's going on in the MusicBrainz community these days?”

    There was a very good talk about the state of the MusicBrainz community and the plans for future development on irc just now.

    It went from 20:03 to 21:52 on 2006-05-04.
    It started with a kind of rant by Wolfsong, developed into a discussion about what is going wrong in the MusicBrainz community these days, and led to some pretty simple steps that might help to make things better.

    I just wanted to bring this to everybody’s attention, before I go to sleep. I might get to adding a short summary tomorrow, but not now, sorry.

    Picard 0.7.0-beta3 released!

    Picard version 0.7.0 Beta 3 has been just released. Downloads: picard-0.7.0-beta3.tar.gz – source code (290 kB) picard-setup-0.7.0-beta3.exe – Windows installer (5.78 MB) various Linux packages Changes from 0.7.0-beta2: support for GNOME and KDE default browser settings, in addition to the BROWSER environment variable (#1257) fixed crashing in Pango (#1256) added tport= parameter to the CD … Continue reading “Picard 0.7.0-beta3 released!”

    Picard version 0.7.0 Beta 3 has been just released.

    Downloads:

    Changes from 0.7.0-beta2:

    • support for GNOME and KDE default browser settings, in addition to the BROWSER
      environment variable (#1257)
    • fixed crashing in Pango (#1256)
    • added tport= parameter to the CD lookup URLs (#1328)
    • new code for checking user name and password that doesn’t block Picard
      when internet connection is down (#1247)
    • fixed bug that caused directory selector to become “sticky” after drag&drop
      on Windows (#1183)
    • support for Windows-compatible file names also on non-Windows systems (#1014)
    • and a couple of other minor bug fixes

    New advanced relationship: MySpace artist URL

    (In an effort to spread the news about changes to the Advanced Relationship link types, I’m posting this and hopefully future changes here). Lukas has just added an Advanced Relationship that lets users link artists to their MySpace pages: forward: has a MySpace page at reverse: is a MySpace page for description: This relationship type … Continue reading “New advanced relationship: MySpace artist URL”

    (In an effort to spread the news about changes to the Advanced Relationship link types, I’m posting this and hopefully future changes here).

    Lukas has just added an Advanced Relationship that lets users link artists to their MySpace pages:

    • forward: has a MySpace page at
    • reverse: is a MySpace page for
    • description: This relationship type can be used to link a MusicBrainz artist to the equivalent entry in MySpace. Please, use URLs in format http://www.myspace.com/[artist]

    Technorati Tags: ,

    Fitting quote

    Yesterday at the Santa Barbara Forum on Digital Transitions, I had a chance to pick Clay Shriky’s brain about online consensus and what it means to bring about consensus in an online community. We didn’t come up with much revolutionary other than what we’ve already been doing: Watch a lively discussion (perhaps flame war) arise … Continue reading “Fitting quote”

    Yesterday at the Santa Barbara Forum on Digital Transitions, I had a chance to pick Clay Shriky’s brain about online consensus and what it means to bring about consensus in an online community. We didn’t come up with much revolutionary other than what we’ve already been doing: Watch a lively discussion (perhaps flame war) arise and subside. Then pick through the rubble to see if something akin to a consensus was found. If so, great. If not, wait a little while and ask the same question over while framing it better in light of the last discussion. Repeat as necessary and involve evil overlord as last resort.

    Clay did share a quote from David Clark that was very fitting to our discussion:

    “We reject kings, presidents and voting. We believe in rough consensus and running code.”

    While its not perfect, it does show what we do about 98% of the time.

    P.S. I was video blogged too — take a look: I won’t stand still while enthusiastically spouting off about MusicBrainz.

    Technorati Tags: ,

    Picard 0.7.0-beta2 released!

    Lukas says: Picard version 0.7.0 Beta 2 has been just released. This version contains mostly bug fixes from the previous beta version. See the full list for details. Downloads: picard-0.7.0-beta2.tar.gz Linux tarball (287 kB) picard-setup-0.7.0-beta2.exe Windows installer (5.62 MB) I’ve also compiled a packages for Ubuntu 5.10 “Breezy Badger”, so Ubuntu users can install Picard … Continue reading “Picard 0.7.0-beta2 released!”

    Lukas says:

    Picard version 0.7.0 Beta 2 has been just released. This version contains mostly bug fixes from the previous beta version. See the full list for details.

    Downloads:

    I’ve also compiled a packages for Ubuntu 5.10 “Breezy Badger”, so Ubuntu users can install Picard by “apt-get install picard” or Synaptic. See PicardLinuxInstall for details.

    Lukas

    Technorati Tags: ,

    PUIDs: WTF?

    Given that my elaborations are not making things more clear, I will try one last time to make things more clear. But before I go on, remember that there are bugs in the system right now. What I am going to explain is NOT how its currently working. If you observe behavior that is different … Continue reading “PUIDs: WTF?”

    Given that my elaborations are not making things more clear, I will try one last time to make things more clear. But before I go on, remember that there are bugs in the system right now. What I am going to explain is NOT how its currently working. If you observe behavior that is different from what I am saying, its BECAUSE THE SYSTEM ISN’T WORKING PROPERLY YET! If you’re confused and don’t understand, stop using Picard 0.7.0.

    Music analysis vs fingerprinting:

    There are two processes that MusicIP makes available. Fingerprinting and music analysis. Let’s touch on music analysis first — this is the process that takes a while (Yes, I know its slow. Yes, I know its going to take days to analyze your collection. Please stop telling me that!) The process of doing music analysis examines up to 10 minutes of a track and examines all sorts of things I know nothing about. All I know is that in order to generate a new PUID, you must analyze a track fully. This full data collection portion is what allows the MusicIP mixer to generate playlists of similar music. This is the secret sauce that makes MusicIP tick and thus this is not going to be open sourced, no matter how much we ask.

    Fingerprinting is much smaller process — it only analyzes about 2 minutes of the track. You cannot generate a new PUID to insert into the database from the fingerprinting process. There is not enough information in this process. There is enough information to create a PUID that is suitable for doing an identification, but not for submission. This works a lot different than TRM — this system doesn’t create rampant amounts of useless fingerprints that will never be used.

    Submitting PUID’s from Picard:

    When the process works, you do a full music analysis on a track and the system generates a PUID for you within 24 hours. But this is not working right now, so Picard will not likely prompt you to submit PUIDs. This means the submit button stays greyed out.

    Why can’t we have Picard generate PUIDs?

    Because we don’t have that code. Please stop asking for ponies — we’re fresh out and you can’t have one. Telling us that this sucks won’t make it any better. Please keep your comments to constructive criticism.

    I don’t understand — its not working as you say it should:

    Did I mention that there are some bugs? If it doesn’t work for you, stop using it. We’ll fix it.

    Rude comments:

    “Reading up on good interface design would also be a suggestion Just google good user interface design” — Please tell me where your FREE software is so I can download it and insult your hard work. I’m sorry that this FREE program isn’t working for you.

    Technorati Tags: ,

    Picard: Common questions answered

    There seem to be many questions about Picard at the moment and a lot of people who love the old tagger interface and are frustrated with Picard’s UI. So, let me address the feedback we’re getting from our users: “MBTagger was perfect. Picard sucks.” — Ok, this feedback doesn’t help much, but we understand that … Continue reading “Picard: Common questions answered”

    There seem to be many questions about Picard at the moment and a lot of people who love the old tagger interface and are frustrated with Picard’s UI. So, let me address the feedback we’re getting from our users:

    • MBTagger was perfect. Picard sucks.” — Ok, this feedback doesn’t help much, but we understand that you are frustrated. We’re working to improve Picard as we speak and the latest release is a beta release, so please bear with us.
    • I don’t understand the Picard interface.” — We understand that there are some people who prefer to tag tracks, not albums. We also understand that the UI is not immediately intuitive. We have plans to fix this, and to allow Picard to be usable by people who prefer to tag tracks and those who prefer to tag albums. For our thoughts on this improved interface, check out this wiki page. For more documentation on how to actually use Picard, see HowToTagFilesWithPicard. And to calm down all the people who are threatening to leave the project if the old MBTagger goes away, we plan to improve the interface of Picard way before the old MBTagger stops working.
    • Picard keeps crashing on me.” — It works for us, which is sucky since we can’t fix your crashes if it doesn’t crash for us. We’re actively soliciting feedback from people who can reproduce crashes. If you have a case where Picard crashes for you consistently and repeatably, please file a bug report.
    • Picard screws up my files!” — First, check to make sure you’re writing the right version of id3v2 tags. Depending on what other programs you use, you may need to switch to version 2.3/2.4 or vice versa. We know about some incompatibilities between the MusicIP Mixer and Picard. We’re going to start working on these issues soon.
    • How do I get PUID’s into MB?” — This answer has two parts. First, to create a new PUID for a file that MB doesn’t have a PUID for currently, you need to download and run the file through the MusicIP Mixer. (Yes, we know not everyone wants to use the Mixer application — for you we’re going to create stand-alone analyzer applications soon). Once a file goes through the MusicIP Mixer, in theory it should become available to the MusicDNS.org service (that MusicBrainz uses) within 24 hours. In practice, this is not happening yet. The MusicIP folks are working on this! Once the MusicDNS.org service has a PUID, you can re run the file through Picard and it should pick up the PUID and prompt you to submit the PUID to MB. Again, there may be bugs in the process — we’re working to iron out the bugs as we speak.

    What can you do if you’re affected by these issues? Here is a quick check list for you:

    1. Do you have an issue not addressed herein?
    2. Can you reproduce the issue?
    3. Yes: Please review the open bugs for picard and if this bug doesn’t already exist, please add a new one.
    4. No: Please stop using Picard 0.7.0 for the time being and go back to Picard 0.6.0 or the old MB Tagger. Then wait for a new release of Picard and see if your problems have improved.

    Bottom line: If you’re frustrated by how things are working right now, go back to a non-beta release and give us more time to iron out these issues. We’re aware that you are frustrated and we’re working on it. But if people keep pestering us with the same issues over and over again, it only keeps us from fixing actual bugs.

    Technorati Tags: ,