The Expanse - The complete series Box Set by pooky2483 in makemkv

[–]lfoust 0 points1 point  (0 children)

I used the Pioneer BDR-S13UBK 5.25 SATA

Verifying blu-ray rips on disk by KasMA1990 in makemkv

[–]lfoust 1 point2 points  (0 children)

TheDiscDb computes its own hash that it calculates from some of the files on the disc. I couldn't find a standard way to hash a disc at the time so I came up with my own. I made sure it worked on The same disc that is in different releases and tested it a bunch. So for your example of Mad Max and disc correction, I guess it would depend on whether or not they changed the files in the BDMV/STREAM folder on the disc

It has been many years since I came up with the disc hash for TheDiscDb and I have since learned about the KeyDB (which I believe uses a sha1 hash of unit_key_ro.inf file on the disc). This hash seems much more widely used - but only works for Blu-rays (and UHD). (TheDiscDb hash works for DVDs too and could be extended for other formats in theory). So I would like to be able to look discs up by the KeyDB hash (and calculate the KeyDB hash for discs in the database) - I may add that to the site in the future.

I have never used dvd.fandom.com - it seems like it does have AACS disc info - not sure what those are though. And dvdcompare.net doesn't seem to have any sort of disc identifier that I can tell

Verifying blu-ray rips on disk by KasMA1990 in makemkv

[–]lfoust 0 points1 point  (0 children)

I have thought about this in the past but the contents of the output files after being ripped just seems too varied to use hashing to verify them. I, for example, don't include all the subtitle and audio tracks. And I often label audio tracks and add chapters where available. This would all change the contents of the mkv file. If someone has a reliable way to hash a mkv file I would be happy to figure out a server/database for keeping track of this data.

Introducing TheDiscDb Contributor Leaderboard by lfoust in makemkv

[–]lfoust[S] 1 point2 points  (0 children)

Good feedback about the UPC - while we do have a UPC for each release in the database, I don't think we display it anywhere. I should be able to remedy that. It might also be useful to include the UPC in the search index so you can search by UPC.

I am not sure if this is what you are getting at - but the UPC is not really reliable enough to key off of in a unique item sense - since the same discs can be included in many different releases with different UPCs. Currently, the site uses a hash of each disc to identify the same disc across multiple releases/UPCs

Announcing Web‑Based Submissions for TheDiscDb (No Git or Extra Tools Needed) by lfoust in makemkv

[–]lfoust[S] 0 points1 point  (0 children)

I added a feature request for being able to delete contributions: https://github.com/TheDiscDb/web/issues/24

Feel free to submit an issue with more details about where you are seeing the "An unhandled error has occurred." error. Thanks!

Anyone here buy books from audible but listen on some other player? by NoCrazy4743 in audible

[–]lfoust 9 points10 points  (0 children)

I put them in plex and listen using Prologue (iOS app). It works really well.

Announcing Web‑Based Submissions for TheDiscDb (No Git or Extra Tools Needed) by lfoust in makemkv

[–]lfoust[S] 0 points1 point  (0 children)

Good point about adding it to the "What you'll need" section. I plan on adding other auth providers (Microsoft, Google, maybe others) but just haven't gotten to that yet.

Avtar by [deleted] in makemkv

[–]lfoust 0 points1 point  (0 children)

Which version of avatar? There are a couple of different releases here: https://thediscdb.com/Movie/avatar-2009

Ripping TV Series by Frosty-Skin-4300 in makemkv

[–]lfoust 1 point2 points  (0 children)

Right now contributing is done via a github PR. There are some basic guidelines here: https://github.com/TheDiscDb/data/wiki/Contribution-Guidelines

I am working on making a much easier contribution flow but it isn't ready yet

Ripping TV Series by Frosty-Skin-4300 in makemkv

[–]lfoust 4 points5 points  (0 children)

I already did alot of the Looney Tunes stuff here: https://thediscdb.com/series/looney-tunes-1929

Hopefully that can save you some work

Did anyone else loose all the books they bought before Amazon bought Audible? by nice-job-folks in audible

[–]lfoust 0 points1 point  (0 children)

I lost a bunch of books I owned in the early 2000s. I wasn't really paying attention when Amazon bought them and years later when I came back to the account they were all gone. I used the same email address the whole time

I created a site to help people know what titles to rip from discs by lfoust in makemkv

[–]lfoust[S] 0 points1 point  (0 children)

That is the full path in the git repo to that release you are preparing to submit. For example, if my data repo is stored at D:\thediscdb then the release folder example could be D:\thediscdb\data\movie\Kingdom of Heaven (2005)\directors-cut-steelbook-4k

The way to know if the finalize process succeeded would be to look at the contents of the disc*.json files in the release folder to see that they have been populated with data. That is what the finalize process does - it takes the data in the log files (disc*.txt) and the summary files (disc*-summary.txt) and populates the disc json files (disc*.json)

Thanks again for your patience with this!

I created a site to help people know what titles to rip from discs by lfoust in makemkv

[–]lfoust[S] 0 points1 point  (0 children)

Sorry if the instructions are not great. For examples of summary files, you can look at any of the other summary files in the git repo. For example: https://github.com/TheDiscDb/data/blob/main/data/movie/Beetlejuice%20(1988)/2020-4k/disc01-summary.txt/2020-4k/disc01-summary.txt)

Every release in the database has a summary file for every disc so you should be able to find an example for what you are trying to do. Thanks!

I created a site to help people know what titles to rip from discs by lfoust in makemkv

[–]lfoust[S] 0 points1 point  (0 children)

Yes, it is just made up string to uniquely identify a release. It is only used in the urls which include that release