I’m happy to announce that the MusicBrainz Picard audio file tagger is now available for Haiku. It can be installed directly from the HaikuPorts repository.
With MusicBrainz Picard you can tag and organize your audio files using data from the MusicBrainz music metadata database. It can be heavily customized using scripting and plugins.
The port provides the latest version 2.1.3 of Picard and is fully functional, including audio CD lookups and audio fingerprinting (using AcoustID).
Porting this was actually a very pleasent experience without major obstacles. Some smaller patches where required, but nothing big really. Kudos to everyone invloved in creating Haiku, great work. I’ve written a bit more about this port in the MusicBrainz community forums:
Yes, I could try to use the Haiku Qt style. Actually Picard 2 originally was hard coded to use the fusion style everywhere, we just relaxed this for macOS a while back. This is still some cause for controversy, we might change back to the platform defined defaults.
But in this case I’ll give the Haiku style a try and patch the package accordingly.
With the current release not easily, but the upcoming Picard 2.2.0 provides a on save hook that could be used for this. Alternatively we could of course also patch it directly into Picard, but having this as a plugin sounds somewhat saner I would be interested of implementing this, can you give me some pointers how such metadata is handled in BFS?
If you are interested my main focus is actually providing patches against the development version of Picard, they are at Commits · phw/picard · GitHub
Picard currently uses the same icon on all platforms. I’m really not sure how this logo can be adapted to the isometric view of Haiku icons. Anyway, this is beyond my abilities If someone can modify the icon to be more haikuesk help is welcome. The Icon-O-Matic version of the icon is at https://github.com/phw/picard/blob/haiku-port/resources/img-src/picard-icon-haiku
Nah, that would be more customization then we do for any other platform Also I tested it by checking if there is a system provided icon first before using Picard’s customized ones. The result was not very convincing, I ended up with default Haiku icons, icons I believe come from Qt and the custom icons of Picard for special actions. If this would be done it would require special Haiku icons for every non-standard icon.
Thanks. As a proof of concept I hacked together a plugin at https://github.com/phw/picard-plugins/blob/haikuattrs/plugins/haikuattrs/haikuattrs.py . It sets the attributes by calling addattr for now. That’s not super efficient and requires a lot of forking, but it works But next step probably would be to use ctypes to actually use the proper interfaces directly.
Keep in mind that this only works with the development version of Picard, but there is a preliminary 2.2.0 recipe for this.
I just noticed you are using WebPositive as the default browser. Why not use the open command instead, which will open a URL with the user’s preferred handler?
You guys are amazing, thanks for the feedback here.
@waddlesplash: I din’t know about open. But now I actually also found out how to change the default browser, this is of course way better. Updated the patches.
I made some changes to your icon. Hopefully it is an improvement. http://0x0.st/z9hW.iom
I guess the logo symbolizes the human brains left- and right halves, with the neurons connecting them. So I had an idea to illustrate a cube split in half, but since this was my first time using Icon-O-Matic it was more than I could manage.
I agree, your changes do improve it. Good teamwork!
What’s the policy here? Surely we can’t have every 3rdparty app icon in the tree?
Should we add a “3rdparty-icons” (or just “icons”?) folder at GitHub - haiku/artwork: Artwork for Haiku and upload those there?
If so a gallery would be great addition so the developers could easily browse the available icons, and the gifted art-craftsman could have an overview what kind of icons are missing.
I would be interested of implementing this, can you give me some pointers how such metadata is handled in BFS?
