SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Probablistic handling of Discog queries

#1

I routinely (well, ever so often) use Jaikoz to go over my library and improve tags. What happens is that it queries Discog for 5 000 songs and then gets blocked for a day. When I run it later on it appears to run over the songs in the same order, and only query the same 5 000 songs.

Iff that actually is case: I would like is that Jaikoz keeps track of songs it has queried and skips them the next time (unless there is still room in the 5 000 queries quota). Maybe in an LRU fashion. This would mean all songs get the Discog treatment once in a while.

#2

Jaikoz does cache lookups, for example if a query find three possible matches and those three songs are looked up they are then stored. So if you were to run the query again you’ll only need to do 1 query instead of 4.

But the queries themselves are not cached, after all the reason you run this every so often is in case more songs can now be matched to Discogs because of new entries added to Discogs, or is it ?

If you just want to update songs that have already been matched with any additional info that has been added you should be using Update Metadata from Discogs rather than Correct Metadata from Discogs. This doesnt do any queries only lookups, so your lookups will be cached as requested allowing you to do the whole system. However if they are cached then you wont pick up any new data, so eventually at some point you’ll have to empty the cache any way.

At some point in the future there will be a way to override this 5000 songs limit, and I think that is going to be the solution here.

#3

I think my thing is that I have more than 5000 songs that are not in Discogs. So every time I run Jaikoz over my library, it will burn through the 5000 limit, and then never ever reach the last part of my library.

So even if that last part is all in Discog (every song is in their database) it will never find out. Ever.

#4

The discog 2.0 api is supposed to eliminate the 5000 song limit.

I too have the same issue.

Are you going to be supporting the discog 2.0 api soon so this issue can be resolved?

Thank You

#5

This issue is being addressed.

#6

the 5000 queries limit now removed in the new beta if you have a Jaikoz Pro license http://www.jthink.net/jaikoz/jsp/beta/start.jsp

#7

Thanks,

Upgraded to pro!