Discogs Tagger 3.62 (Updated: 2013-02-09)

[eepman]

if you go to the last page i posted a link with a version of the script that should work even after v1 shuts down.

- It does not require an API key.
- It has the same features as the script in the first post, only backend stuff changed.

You can use this until Let's new version comes out.

Just copy and paste over your existing script installation.

THIS DOES NOT NEED API KEY, USE THIS!
http://dl.dropbox.com/u/7953706/DiscogsAutoTagWeb.vbs

[Let]

Ok guys i have already completed the coding for API V2 (not JSON but everything works with XML too) and many more features but I don't have time to wrap it up and release. I'll make final tests and and release it once have time for it (probably this weekend).

[Let]

I've released the new version V3.3. It works perfectly for the time...

[Guest]

I've released the new version V3.3. It works perfectly for the time...

Yesss! Thank you, works great!

[Guest]

Hehehe, on the Addons page it says "Updated 22/10/2009", might wanna get that fixed

[odyss3y]

I've released the new version V3.3. It works perfectly for the time...

thanks for the update

[Let]

Hehehe, on the Addons page it says "Updated 22/10/2009", might wanna get that fixed

That is a bug in the addon system. I've updated the addon page yesterday and there's no way to change that date

[Let]

I'll be glad if you can rate this script on addons page.

http://www.mediamonkey.com/addons/brows ... gs-tagger/

[Eyal]

Thanks for the update, Let.
Switched from 3.1 to 3.3 and working fine!
I love the ability to direct link to Master Release.

5 stars *****

[Let]

Discogs returns JSON formatted results although we request in XML format for some requests, which our script cannot understand. According to the discussion eepman started in discogs web site, they won't be supporting XML format in the future which is a BIG problem for us since we our script depends on it. Using JSON format in the script means lots of coding, worse we need a suitable JSON parser for VBScript.

Since I got some errors regarding this issue while testing, you might have some problems as well.

[bmcclure]

All-in-all, reading from JSON should actually be quite trivial once a suitable parser is included. As a fellow developer, If you'd like any assistance in that department I'd be happy to lend a hand getting things working.

Great work on the new version!

[Let]

I've tested the script with MM4. It seems to work fine.

One thing that annoyed me is to select cover type each time. There's nothing to do unless they provide a way to select cover type within the scripting API.

[DeFiNL]

This is a lovely tool! I have been looking for something like this for a while.. thanks for the work that has gone into this.

I hope someone can help me with the following :

I have more then 10000 folders which each contain one album and for each one of those folders i now have to lookup/tag manually. Is there anyway to do this automated for a large number of albums?

I am thinking of something like this :

1. Select the folder that contains all the folders with albums/vinylrips.
2. Select the option "Batch Tag" , this starts the process that starts the tagger for each of the folders.
3. Once it has done a lookup for the first folder/album show a dialog window that gives the option Rename or Skip or Stop.
4. If you click rename it renames, if you skip it continues to the next folder/album , if you click Stop it stops the batch process entirely.

I am open for alternatives as well, maybe some else has found a different solution to do this?

Any help is much appreciated!

[Let]

since you can't make sure if the first result will be the correct one, i suspect batch tagging would work correctly. on the other hand, once all albums are tagged, a batch update can be implemented since release id is saved in a custom field.

[Let]

discogs is shutting down api v1.0 tomorrow. hopefully v3.3 supports api v2. they also have intentions for not supporting xml. i hope they won't mess with it