Timothy Lee says:
After a month of trying universal builds through macports unsuccessfully, using a tool named ‘unify’ (h/t John) to lipo i386 and ppc arch bins together unsuccessfully, and bugging just about everyone I know to use their i386 tiger machine (I have an i386 leopard and a ppc tiger) unsuccessfully I’ve made the decision to halt my progress on trying to deliver a UB.
What I do have though is two builds. I have one PPC build that was built on a tiger machine and one i386 build that was built on a leopard machine. I have not had a chance to test my i386 leopard build on a tiger machine (read above failure to ‘borrow’ a tiger machine) but there is a chance it may work. If you feel like you have a better handle on the ‘lipo’ process, please, take my builds and smash them together and let me know! (It may be desirable NOT to deliver a UB as
each separate build of Picard is fairly large).
Timothy is looking for feedback on these builds. If you’ve been waiting for a complete version of Picard that includes working PUID generation, then please try these builds:
Picard for OS X Intel i386 (md5)
Picard for OS X PPC (md5)
If you have problems running these please enter a bug report and use the component “Picard Tagger (Mac OS X Packaging)“. Thanks very much Tim and everyone else who has helped along this somewhat frustrating process.
If you have a PPC Mac that runs 10.4/10.5 and have been waiting for a DMG of Picard, please try download and install this version. Please let us know if it works in the comments.
Jon Hermansen and I have been working on building Picard with only MacPorts prerequisites — that is how this DMG has been built. If this install works then we can proceed to work on a Universal Binary that should work on 10.4/10.5. If we can reach that, we should be able to release Mac binaries at the same time as we release binaries for other platforms.
Thanks for all your hard work Jon!
UPDATE: We’ve found a problem with PUID generation and have fixed it — we hope. The above link now points to the updated dmg. May not work on Tiger yet — if you have a Tiger PPC box, please try it and let us know.
After many days of tinkering, the new search server has passed its tests and is nearly ready for deployment next week. After my last post on the search services, there were lots of questions, so I’ll give some more history on why I’m working on this now:
- The old Lucene based search services worked well, but installing them was a major pain. Installing compilers by hand, sacrificing chickens and hoping that things would work wasn’t my idea of fun.
- Lucene has a philosophy of working out of the box without significant tweaks. That’s great if you’re indexing a bunch of text, but indexing music metadata from an SQL database is a bit of a different beast. The usual Lucene tricks didn’t work so well for us, so we couldn’t tweak it to work better for us. Xapian requires a little more tuning out of the box, but our search results are much better now than they were before.
- Sending metadata lookup traffic to a service like Xapian is generally a good idea, as a single Xapian server can handle lookup traffic more elegantly than a Postgres database. And adding more search servers is easier than adding more database servers.
- Our traffic is growing — I expect us to handle twice as much traffic in July as we did the July before. A lot of this traffic growth is coming from people using our web-service to look up music. If the web-service slows down, the rest of the site slows down as well. So I’m trying to stay ahead of the curve an anticipate when we reach capacity and be able to add more machines as necessary
As of next week, MusicBrainz will have twice as much rack-space (20U’s of space!) and we can finally rack the two new servers that were donated a few months ago. Fortunately due to dropping bandwidth costs, this new space doesn’t really come at a greater expense to us — I expect our hosting costs to stay nearly the same as they are now. (about $1000/mo, btw)
This will allow us to have 3 times the search capacity we have now, which should keep the site working for a while longer. In fall I hope to start moving our web-service to Amazon’s EC2 service, which should allow us to get as much capacity as we need.
As soon as I get the new search services deployed I’m putting my head down and coding the next server update. So, keep your fingers crossed that this process goes smoothly.
Its clear that I won’t find the time to package up Picard for OS X anytime soon. I’ve put out one Intel based DMG, but haven’t found the time to create a Universal Binary package of Picard. 😦
If you have the following:
- Knowledge of building Mac OS X Application Bundles
- Python knowledge
- Love for Picard
- Access to Intel and PPC Macs
We would very much like to talk to you. The last item isn’t crucial — I suppose we can get people in the community to test your builds for platforms you have no access to. Please leave a comment if you’re interested in helping out.
What started out as a joking suggestion has actually extended the life of the Classic Tagger! 🙂
One jokester at the recent summit suggested that we return random TRM values (as opposed to matched acoustic fingerprint ids) and just switch the TRM server off. Turns out, that suggestion was actually brilliant!
Doing this essentially makes every TRM lookup return “I don’t know this one”. But in that case the MusicBrainz server falls back to doing a metadata match (without the acoustic fingerprint). And it turns out that works pretty well all around! And I think some people may prefer this method, since you won’t have to clear up TRM collisions anymore.
So, what does mean for when we switch off the TRM server? The Classic Tagger lives on and may match fewer files than before — life may actually be better once we shut it off! But I think that many people will find it useful still.
If you have an intel Mac and would like to try out the first test of a PUID enabled Picard on OS X, please download this DMG and post a comment to let me know if it works.
- Is for INTEL only
- Only runs on OS X 10.5 (Leopard)
- Probably does not have working CD Lookup
- Might be buggy
- Is based on the 0.9.0 Picard tarball
- Is NOT a Universal Binary
If this DMG works for people then I will proceed to try to get 10.4/PPC/disc lookup support working.
Hi! The first episode in my series of “Working with Picard” screencasts has now been recorded, and is available for public consumption 🙂 A YouTube link to the video is available, and a higher resolution Ogg Theora file is also also available. You’ll probably find the Ogg Theora easier to read due to the higher … Continue reading “Working With Picard, Episode 1”
The first episode in my series of “Working with Picard” screencasts has now been recorded, and is available for public consumption 🙂 A YouTube link to the video is available, and a higher resolution Ogg Theora file is also also available. You’ll probably find the Ogg Theora easier to read due to the higher resolution.
In this first screencast I go through the basics of Picard – how to load files, how the interface works, and basic usage with clusters.
If there’s something that’s unclear, or you have future ideas for screencasts – let me know! Other wise, enjoy the screencast – and show you’re friends and convince why MusicBrainz is so cool (if you haven’t already 🙂
Given the number of clueless/negative comments on the TRM announcement, I feel it necessary to clue people in to the fact that Picard QT’s interface has been revamped. The workflow has been greatly improved, the user interface is more stable and it does an amazing amount of work for you before you need to use … Continue reading “In case you didn't catch it: Picard != Picard QT”
Given the number of clueless/negative comments on the TRM announcement, I feel it necessary to clue people in to the fact that Picard QT’s interface has been revamped. The workflow has been greatly improved, the user interface is more stable and it does an amazing amount of work for you before you need to use acoustic fingerprinting.
If you feel the need to trash months of hard work that Lukas has done, please at least download it and try it before you make an idiot of yourself.
I’m pleased to announce that Lukáš has released Picard QT version 0.9.0 beta1! Picard QT is the port of Picard away from the troublesome wxWidgets toolkit and over to the much more stable QT toolkit. Along the way Lukas reworked the UI to be more intuitive and added the much anticipated TaggerScript language that gives … Continue reading “Picard QT enters beta testing”
I’m pleased to announce that Lukáš has released Picard QT version 0.9.0 beta1!
Picard QT is the port of Picard away from the troublesome wxWidgets toolkit and over to the much more stable QT toolkit. Along the way Lukas reworked the UI to be more intuitive and added the much anticipated TaggerScript language that gives the user total control over how to tag their music collection. The great news amidst all this is that with QT Picard now runs well on OS X — something that we could never achieve with the wxWidgets toolkit!
We have installers for Windows and Mac OS X and a tarball for our Linux users — grab them from the Picard download page. We’re hoping to have a final release of Picard QT in about a month. In the meantime, please report any bugs you may find.
We’ve been able to improve the performance of the database server, so that we’ve been able to turn on TRM support again. Happy tagging!
We’ve been able to improve the performance of the database server, so that we’ve been able to turn on TRM support again.