Topic: Picard 0.15 BETA released

The first beta version of a NGS-enabled Picard has been released. All work on this release has been done by bitmap! This does not add complete support for all NGS features, just enough to be able to properly tag multi-disc releases and standalone recordings. More features will be added later.

Picard 0.15 BETA packages for Windows, OS X and the source code tarball can be download here: http://musicbrainz.org/doc/MusicBrainz_Picard

There are currently some known problems with relationships, but other things should work fine. If they don't, please submit bug reports.

Loading of relationships in general doesn't work due to a server bug (http://tickets.musicbrainz.org/browse/MBS-2395). Additionally, enabling track-level relationships will cause all albums to fail to load.  You have to disable that option for now. This is caused by another server issue (http://tickets.musicbrainz.org/browse/MBS-2396). I have patches for both of these and I hope that they will be fixed with the next server update.

I've changed the plugin API version, so all plugins will stop working. I've done this because the internal structure of the MusicBrainz data has changed. Plugins that are known to work should be marked to support the 0.15 API. I'd also like all plugins to be moved to the Picard source code, for easier management. I've setup http://users.musicbrainz.org/~luks/picard-plugins/ which is automatically updated from the Picard source directory. If you have a plugin that is missing, please let me know and I'll add it there.

Re: Picard 0.15 BETA released

Using the "Open in tagger" feature on the MB website doesn't work for me anymore (nothing happens in Picard). Restarting the browser didn't help. It used to work with 0.14.

Picard seems to be listening on the local port however. Manually requesting a link like

http://127.0.0.1:8000/openalbum?id=0b47 … 1306704939

yields a "nothing to see here" message...

Re: Picard 0.15 BETA released

If a discid lookup is attempted and none are found, the box with the button for Lookup Manually does not appear.  Works fine if it finds at least one.

Re: Picard 0.15 BETA released

d41k4n wrote:

Using the "Open in tagger" feature on the MB website doesn't work for me anymore (nothing happens in Picard). Restarting the browser didn't help. It used to work with 0.14.

Picard seems to be listening on the local port however. Manually requesting a link like

http://127.0.0.1:8000/openalbum?id=0b47 … 1306704939

yields a "nothing to see here" message...

Hm, I can't reproduce this on my machine (OS X). Clicking that link adds the album to the interface for me.

jdc0730 wrote:

If a discid lookup is attempted and none are found, the box with the button for Lookup Manually does not appear.  Works fine if it finds at least one.

Thanks for reporting this, I have a fix that will probably be in beta2 tomorrow.

Re: Picard 0.15 BETA released

bitmap wrote:
d41k4n wrote:

Using the "Open in tagger" feature on the MB website doesn't work for me anymore (nothing happens in Picard). Restarting the browser didn't help. It used to work with 0.14.

Picard seems to be listening on the local port however. Manually requesting a link like

http://127.0.0.1:8000/openalbum?id=0b47 … 1306704939

yields a "nothing to see here" message...

Hm, I can't reproduce this on my machine (OS X). Clicking that link adds the album to the interface for me.

This problem occurred on Win7 Pro 64bit. Also, I didn't remove the previous version of Picard.

Currently I'm on a different machine running Vista 32bit and it's working fine here. However, this is after a clean install of Picard 0.15Beta (no previous version installed).

I will try a clean install on my Win7 box sometime later today and let you know if that helped.

Re: Picard 0.15 BETA released

As a general thought, which may have already been brought up somewhere, I think the UI needs some kind of disc amount indicator on the release level, at least when there is more than one disc. A simple (3 discs) after the release name would suffice I think, but it also needs to look different somehow so people won't think it's part of the release title. Color coding? I don't know. Someone else will probably have a better idea. :p



d41k4n wrote:
bitmap wrote:
d41k4n wrote:

Using the "Open in tagger" feature on the MB website doesn't work for me anymore (nothing happens in Picard). Restarting the browser didn't help. It used to work with 0.14.

Picard seems to be listening on the local port however. Manually requesting a link like

http://127.0.0.1:8000/openalbum?id=0b47 … 1306704939

yields a "nothing to see here" message...

Hm, I can't reproduce this on my machine (OS X). Clicking that link adds the album to the interface for me.

This problem occurred on Win7 Pro 64bit. Also, I didn't remove the previous version of Picard.

Currently I'm on a different machine running Vista 32bit and it's working fine here. However, this is after a clean install of Picard 0.15Beta (no previous version installed).

I will try a clean install on my Win7 box sometime later today and let you know if that helped.

Win7 64bit here as well, installed over previous picard and the the "tagger" icon is working fine over here.

Re: Picard 0.15 BETA released

Did the clean install but still no joy :(

Looking at the log I found a lot of errors like this:

E: <sip.voidptr object at 0x08275E30> 21:11:36 u'Error downloading http://musicbrainz.org:80/ws/2/release/86e23f11-4b44-4586-ba1d-949253e2f1d5?inc=release-groups+recordings+puids+artist-credits+labels+isrcs+artist-rels+release-rels+url-rels+work-rels+recording-level-rels+work-level-rels - server replied: HTTP/1.1 400'

Any idea?

Re: Picard 0.15 BETA released

Yes, see the first post of this thread. ;)

luks wrote:

Loading of relationships in general doesn't work due to a server bug (http://tickets.musicbrainz.org/browse/MBS-2395). Additionally, enabling track-level relationships will cause all albums to fail to load.  You have to disable that option for now. This is caused by another server issue (http://tickets.musicbrainz.org/browse/MBS-2396). I have patches for both of these and I hope that they will be fixed with the next server update.

So, you'll have to go in the preferences and disable relationships for now. Under "Metadata" uncheck "Use track relationships" and "Use release relationships."

Re: Picard 0.15 BETA released

luks wrote:

The first beta version of a NGS-enabled Picard has been released. All work on this release has been done by bitmap! This does not add complete support for all NGS features, just enough to be able to properly tag multi-disc releases and standalone recordings.

Please pardon my ignorance, but what exactly does "...to properly tag multi-disc releases..." mean?

I still get one big release without separate discs for multi-disc releases.

Re: Picard 0.15 BETA released

bitmap wrote:

Yes, see the first post of this thread. ;)
So, you'll have to go in the preferences and disable relationships for now. Under "Metadata" uncheck "Use track relationships" and "Use release relationships."

Duh. For some reason I thought I did just that but when I checked again those options were enabled.... Sorry for all the trouble ;)

However, I noticed that Picard needs a restart after disabling relationships otherwise albums can't be loaded.

Re: Picard 0.15 BETA released

mbstm wrote:

Please pardon my ignorance, but what exactly does "...to properly tag multi-disc releases..." mean?

I still get one big release without separate discs for multi-disc releases.

Your files get tagged with disc numbers, as opposed to 0.14 loading and saving everything as a single disc. All of the discs are still displayed under one "album" in the interface; the only visual change is that disc numbers prefix the track numbers on multi-disc releases. Further visual changes will probably happen, but all of that's sort of up in the air right now.

Re: Picard 0.15 BETA released

[What does proper tagging of multi-disc releases in Picard mean?]

@bitmap: Thanks for the clarification.

Re: Picard 0.15 BETA released

On Mac OS X 10.6, the beta tells me it “could not load album” every time…

Re: Picard 0.15 BETA released

Salocin wrote:

On Mac OS X 10.6, the beta tells me it “could not load album” every time…

Are you sure you have the "Use track relationships" option is disabled?

Re: Picard 0.15 BETA released

A new beta version with bug fixes has been released. You can download as usually from http://musicbrainz.org/doc/MusicBrainz_Picard

Re: Picard 0.15 BETA released

bitmap wrote:

Your files get tagged with disc numbers, as opposed to 0.14 loading and saving everything as a single disc. All of the discs are still displayed under one "album" in the interface; the only visual change is that disc numbers prefix the track numbers on multi-disc releases. Further visual changes will probably happen, but all of that's sort of up in the air right now.

I'm hoping this is done away with or becomes an optional setting of some kind. I'd much rather the tagger fill in the discnumber field without having to rely on a plugin or cracking together some script (complex or not) to accomplish something that should happen naturally.

Re: Picard 0.15 BETA released

TheMonkofDestiny wrote:

I'm hoping this is done away with or becomes an optional setting of some kind. I'd much rather the tagger fill in the discnumber field without having to rely on a plugin or cracking together some script (complex or not) to accomplish something that should happen naturally.

I'm not sure I understand. I was explaining that Picard does fill in the discnumber field, which is an improvement over 0.14.

18 (edited by TheMonkofDestiny 2011-06-01 01:45:41)

Re: Picard 0.15 BETA released

Sorry - the way I'd read it I took it to mean that it only appended a disc number in front of the file name (1-01, 1-02, 2-01, etc.) (which is a big improvement over the nothing in .14 currently by far but still somewhat a pain to deal with) and didn't write anything into the tag fields (ex. discnumber) themselves, which seemed bizarre. My mistake.

19 (edited by soulsearchingsun 2011-06-02 17:30:15)

Re: Picard 0.15 BETA released

Will the multi disc album behavoir be user configurable, e.g. switchable between 'old style' (disc n: subtitle) and 'new style'? Most DAP's (including mobile phones) don't handle discnumbers in tags properly (//at all). For this reason I wanted to keep my tags as simple as possible, which means that title, tracknumber, artist and album are the only tags needed. That doesn't work if Picard defaults to relying on disc number tags.

Re: Picard 0.15 BETA released

soulsearchingsun wrote:

Will the multi disc album behavoir be user configurable, e.g. switchable between 'old style' (disc n: subtitle) and 'new style'? Most DAP's (including mobile phones) don't handle discnumbers in tags properly (//at all). For this reason I wanted to keep my tags as simple as possible, which means that title, tracknumber, artist and album are the only tags needed. That doesn't work if Picard defaults to relying on disc number tags.

Then you'll want the classicdiscnumber.py plugin from here: http://users.musicbrainz.org/~luks/picard-plugins/

Re: Picard 0.15 BETA released

bitmap wrote:

Then you'll want the classicdiscnumber.py plugin

Great, thanks.

Re: Picard 0.15 BETA released

Great that the new Picard is available! Many thanks!

I noticed that Picard now fills disc number and total discs tags even for single disc releases. Is it intended? I must say that I do not like it and I prefer to leave these tags unset for single disc releases.

Re: Picard 0.15 BETA released

I think that's the behaviour I would expect. Pretty easy to use tagger script to unset both if totaldiscs=1 I guess.

Re: Picard 0.15 BETA released

voiceinsideyou wrote:

I think that's the behaviour I would expect. Pretty easy to use tagger script to unset both if totaldiscs=1 I guess.

Well, it certainly would be if you assumed we started from a blank slate.

However, it's been sort of a convention that single-disc releases don't have discno/totaldiscs set, and this has been exploited to influence how data is presented and used. E.g, tagging/renaming software that will prepend "<discno>-" to filenames if discno/totaldiscs tags are present, but using just "<trackno>-<title>" for single-disc releases (which often lack them).

25 (edited by SamDeRe81 2011-06-04 20:25:01)

Re: Picard 0.15 BETA released

I want someone to acknowledge and finally accept the Advanced Title Case plugin created by Carlin Mangar to replace the current one available. I found it here http://bazaar.launchpad.net/~openshift/ … tlecase.py which explains what they did and why, the actual file can be downloaded here http://bazaar.launchpad.net/~openshift/ … tlecase.py

CAN THIS PLEASE BE ADDED!