The 250k number is what's advertised on the RipIt website: “We'd like report that RipIt has just been verified to work with its 250,000th unique disc!”.
Although that might not be what's in the DiscIdent database. So much for my confusion.
19 March 2010 at 10:24
Anonymous said...
So, you're bundling a service that: > They have a database of some 250k DVDs ; ss small > isn't open > the API doesn't seem to allow submission
Anonymous: The good news is that we have API to query the database, and that it's easy to use. The API will be augmented as we get more data on the protocols used.
thanks for the info and explanation provided very informative to read ;-)
7 June 2010 at 03:24
I just pushed discident-glib to GNOME git, a small library that uses discident.com's service to guess the title of DVDs. They have a database of some 250k DVDs, though the database itself isn't open, and the API doesn't seem to allow submission. Still a few FIXMEs to go through and API docs to write, and it should be ready to be integrated in your favourite DVD ripper. Drop me a line if you're interested in using it in your app.
"Guessing DVD titles"
7 Comments -
This comment has been removed by a blog administrator.
18 March 2010 at 04:11
hey, thats pretty cool. exactly what i need for my media indexer app!
19 March 2010 at 00:29
Is 250k correct count? The website says they have about 53000 discs in database.
19 March 2010 at 10:14
The 250k number is what's advertised on the RipIt website: “We'd like report that RipIt has just been verified to work with its 250,000th unique disc!”.
Although that might not be what's in the DiscIdent database. So much for my confusion.
19 March 2010 at 10:24
So, you're bundling a service that:
> They have a database of some 250k DVDs ; ss small
> isn't open
> the API doesn't seem to allow submission
Where exactly are the good news in this post?
22 March 2010 at 23:04
Anonymous: The good news is that we have API to query the database, and that it's easy to use. The API will be augmented as we get more data on the protocols used.
22 March 2010 at 23:32
thanks for the info and explanation provided
very informative to read
;-)
7 June 2010 at 03:24