Discussion in 'AnyDVD HD (UHD only)' started by peterbus, Jan 16, 2019.
Any one have any luck in backing up this disc ?
Yes, I backed it up on January 4th.
Amazon US version.
yep thats the one i have, wont work ( CANNOT PROCESS THIS DISC),did you do an ISO or MKV ? WHAT REDFOX VERSON?
The anydvd version doesn't matter, support is added via the online database which doesn't require an up-to-date version in order to use the fix correctly.
Verstuurd vanaf mijn Nexus 6P met Tapatalk
I backed it up to .iso using the AnyDVD ripper.
But regardless of backup method and as Ch3vron pointed out, regardless of what release you're running, as soon as you mount the UHD, it should immediately decrypt if you have the Amazon US version.
I just double-checked and it still decrypts as it should...
What exactly does your AnyDVD Status say?
The discs have different naming. So the discs should be different too.
Hint: You can copy & paste out of AnyDVD's status window. No need for screenshots.
But more important, hint2: The logfile contains disc hashes to distinguish discs.
Naaah. I re-do my UHD labels and append "UHD" to distinguish them from regular Blu-Rays.
The sizes are exactly the same so that's a good sign but something must be different .....
Well, I know how to create a logfile (ofc) but never read one. I thought you needed special tools to read the logfiles.... ????
@peterbus I guess we must have different versions somehow, even though so far it seems it's the same version.
Per James' suggestion, we'll have to compare hashes -- as soon as I figure out how to read a logfile to get my disc hash...
@James, am I right to think the disc hash (or part of it) is embedded as the suffix of the logfile that AnyDVD creates for a disc?
It's how you can easily tell if your logfile is for the same disc edition that someone else has posted to the forums. Just hover your mouse over the logfile name and it will show the whole name...and the suffix is the hash. If your suffix is the same, then you've got the same disc and don't need to post another logfile.
Nope, the logfile name is based on the disc volume name. Not the decryption/encryption hasn.
You are correct, I actually forgot about this.
It is based on both.
Well i was half right then
My cup is half full, too!
Yes, of course !!!!!!
What was I thinking?
@peterbus I've attached my logfile for Venom UHD.
Does yours have the same name?
all good as with 8334
Ok, peterbus I forgot about this thread!
(Glad you posted in the other too, btw. Trying to keep track of the unsupported there).
Do you think if you reverted back to the previous release, Venom UHD will stop working?
Would be an interesting test, since release is not supposed to be a factor, just the OPD...
... if that was the case, maybe there could have been another issue, maybe related to the logfiles with no numbers, that was fixed this last release?
Guess, anything's possible.
EDIT: peterbus, I think you mean 220.127.116.11....
I created a logfile for still-unsupported Oceans in 18.104.22.168.
Logfile still lacks ending numbers -- so that has nothing to do with this.
It was just a thought...
well heres another one...
tried to rip Superman the movie ( UK )using an Asus friendly drive ,got an error , swapped it to an Lg FRIENDLY DRIVE AND IT RIPS....
SORRY 8340 of course....
Separate names with a comma.