AnyDVD HD: 1, documentation? 2, log file?

Discussion in 'General Chat' started by markfilipak, Feb 7, 2020.

  1. markfilipak

    markfilipak Well-Known Member

    Howdy. I have 2 issues.

    1.
    I couldn't find documentation except the ? help-thingy. Some of the setup is obscure and doesn't lend itself to one-sentence summary. Is there more complete documentation? Thanks.

    2.
    I just ISO-ripped a DVD-9. After 5 minutes, the progress bar still indicated that it would take another 2 hours!?!
    I went shopping. When I arrived home later, I searched for a log file. I couldn't find one. I hoped to discover whether the disc -- it is brand new -- has errors. At issue is sending the disc back for replacement. Is there a log file? I'm willing to rerip in order to read a log.

    Thank you, kindly,
    Mark.

    Rest In Peace, Kirk.
     
  2. James

    James Redfox Development Team Staff Member

    Right-click notification icon, "help..."
    Right-click notification icon, "create logfile..."
     
  3. markfilipak

    markfilipak Well-Known Member

    Hi James,

    Thanks! You might want to add a "Help" function to the actual window, and also a link on the web site -- might save you having to respond to people like me. :)
    My file browser (Total Commander) was able to open the '.ziplog' file but there's question marks for included file date-times. That indicates that the '.ziplog' is not a standard ZIP file. Thus, I'm in doubt...
    Is the file list below complete?
    VIDEO_TS\ ...a bunch of IFO files
    AI_ButtonFile
    AI_StateFile
    AnyDVD_log.txt
    AnyDVD_Status.txt
    dirlist.txt
    sysinfo.txt
    traffic.klz
    traffic2.klz

    Regarding AnyDVD_log.txt: I looked through it. Is there any disc diagnostic info there?

    Actually, I was hoping to find a run-time log. "Rip to Image..." was obviously having difficulty with the disc.
     
  4. James

    James Redfox Development Team Staff Member

    Use elby CloneDVD2 instead. It creates wonderful runtime logs.
     
  5. mmdavis

    mmdavis Well-Known Member

    There is if you leave the AnyDVD log as a ziplog file and don't modify it in any way as you did. Any zip program (Winzip, 7zip, winrar, etc) can open the ziplog. If yours doesn't then you need to make a file association adjustment.
     
  6. markfilipak

    markfilipak Well-Known Member

    I didn't modify it in any way. Its name is AnyDVD_8.4.4.0_Info_B_***HIDDEN***.ziplog
    Are you familiar with Total Commander?

    So, what are the diagnostic parts of AnyDVD_log.txt? I don't know how to read it -- why would I?

    It has 1357 lines of text.

    Thanks for helping!
     
  7. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    It's a standard zipfile, it's just the extension that isn't. Or your tool wouldn't have been able to open it. As to what party is diagnostic, everything is, or three files in it, wouldn't be in it.

    Sent from my Pixel 3 XL using Tapatalk
     
  8. markfilipak

    markfilipak Well-Known Member

    Well, the list of files is:
    AI_ButtonFile <-- binary
    AI_StateFile <-- binary
    AnyDVD_log.txt
    AnyDVD_Status.txt
    dirlist.txt
    sysinfo.txt
    traffic.klz <-- binary
    traffic2.klz <-- binary

    Regarding the text files:
    AnyDVD_log.txt <-- 49 k-bytes
    AnyDVD_Status.txt <-- 833 bytes
    dirlist.txt <-- 3.8 k-bytes, media disc file info
    sysinfo.txt <-- 158 k-bytes, just system info (no media info)

    Regarding AnyDVD_log.txt:
    I see some scoreboards, lots of process status reports, and then this:

    All skipped sectors:
    297 - 26358 (26061)
    26797 - 26804 (7)
    2996230 - 3001462 (5232)
    3001488 - 3001506 (18)
    3869434 - 3869457 (23)
    3869468 - 3869476 (8)
    3916648 - 3916656 (8)
    3916667 - 3916685 (18)
    3953366 - 3953379 (13)
    3953389 - 3953408 (19)
    3962512 - 3962522 (10)
    32.78s: Adding error 297 length 26061
    32.78s: Not adding error 26797, 7 is too small!
    32.78s: Adding error 2996230 length 5232
    32.78s: Adding error 3001488 length 18
    32.78s: Adding error 3869434 length 23
    32.78s: Not adding error 3869468, 8 is too small!
    32.78s: Not adding error 3916648, 8 is too small!
    32.78s: Adding error 3916667 length 18
    32.78s: Not adding error 3953366, 13 is too small!
    32.78s: Adding error 3953389 length 19
    32.78s: Not adding error 3962512, 10 is too small!
    32.78s: compute 1 of 6
    33.16s: authenticate_drive: obtain 0
    33.16s: agid 3
    33.17s: client e0a28da5855c9b060340
    33.17s: key1 6fda1ea8df
    33.17s: variant 0
    33.17s: host c242ddb4e75e9877a387
    33.17s: key2 95c58e347a
    33.17s: challenge 6fda1ea8df95c58e347a
    33.17s: bus 57f6e1ec11
    33.28s: get_titlekey start 26367 crackstart 26368
    33.28s: compute 2 of 6
    33.67s: authenticate_drive: obtain 0
    33.67s: agid 3
    33.67s: client e0a28da5855c9b060340
    33.67s: key1 6fda1ea8df
    33.67s: variant 0
    33.67s: host 79b620c0d5ccb926f902
    33.67s: key2 ad3936dda1
    33.69s: challenge 6fda1ea8dfad3936dda1
    33.69s: bus 461aef671f
    33.73s: get_titlekey start 26842 crackstart 26843
    33.73s: compute 3 of 6
    34.19s: authenticate_drive: obtain 0
    34.19s: agid 3
    34.19s: client e0a28da5855c9b060340
    34.19s: key1 6fda1ea8df
    34.19s: variant 0
    34.19s: host 519a58589c197bea536e
    34.19s: key2 dfbfa8f017
    34.19s: challenge 6fda1ea8dfdfbfa8f017
    34.19s: bus d9a7bfdf4a
    34.55s: get_titlekey start 3001487 crackstart 3001488
    34.55s: compute 4 of 6
    34.97s: authenticate_drive: obtain 0
    34.97s: agid 3
    34.97s: client e0a28da5855c9b060340
    34.97s: key1 6fda1ea8df
    34.97s: variant 0
    34.97s: host 182440ee1482405c52fa
    34.97s: key2 ccabdff53e
    34.97s: challenge 6fda1ea8dfccabdff53e
    34.97s: bus a318901c15
    35.19s: get_titlekey start 3869467 crackstart 3869468
    35.19s: compute 5 of 6
    35.58s: authenticate_drive: obtain 0
    35.58s: agid 3
    35.58s: client e0a28da5855c9b060340
    35.58s: key1 6fda1ea8df
    35.58s: variant 0
    35.58s: host a742d736e34c170e6aba
    35.58s: key2 d8d6cd25f6
    35.58s: challenge 6fda1ea8dfd8d6cd25f6
    35.58s: bus 2e05051ee8
    35.69s: get_titlekey start 3916666 crackstart 3916667
    35.69s: compute 6 of 6
    36.13s: authenticate_drive: obtain 0
    36.13s: agid 3
    36.13s: client e0a28da5855c9b060340
    36.13s: key1 6fda1ea8df
    36.13s: variant 0
    36.13s: host b363ea0e6c1c67576734
    36.13s: key2 0de6546c2c
    36.13s: challenge 6fda1ea8df0de6546c2c
    36.13s: bus 7c4d3c0622
    36.22s: get_titlekey start 3953389 crackstart 3953390
    36.22s: compute 6 of 6
    36.22s: store
    36.22s: authenticate_drive: obtain 1
    36.23s: agid 3
    36.23s: client e0a28da5855c9b060340
    36.23s: key1 6fda1ea8df
    36.23s: variant 0
    36.23s: host 0c4d3d3f7a6d993ffb4a
    36.23s: key2 940035a27e
    36.23s: challenge 6fda1ea8df940035a27e
    36.23s: bus 0067d5abfd
    36.23s: get_disc data transfer 2052
    36.23s: response length 2050, sizeof *response 2052
    36.23s: player 1 of 34
    36.23s: player 1 of 34
    36.23s: disc 6acb11d3bf
    36.23s: title 1 range 26359-26367 26367-26797 (M 26367, T 0) 26797-26805 key 1190f42eb2
    36.23s: title 2 range 26805-26842 26842-3001426 (M 26842, T 27660) 3001426-3001463 key ca361b5c5f
    36.23s: title 3 range 3001463-3001487 3001487-3869434 (M 3001487, T 3001507) 3869434-3869458 key cb4f7355e4
    36.23s: title 4 range 3869458-3869467 3869467-3916648 (M 3869467, T 3869477) 3916648-3916657 key d651274a66
    36.23s: title 5 range 3916657-3916666 3916666-3953371 (M 3916666, T 3916686) 3953371-3953380 key cdef31e165
    36.23s: title 6 range 3953380-3953388 3953389-3962512 (M 3953389, T 3953409) 3962512-3962520 key d5177fd945
    36.25s: parse_image took 35 seconds
    36.34s:
    Number of entries: 6
    36.34s: Type: 6
    36.34s: From 3953389 to 3953408, length 19
    36.34s: Type: 6
    36.34s: From 3916667 to 3916685, length 18
    36.34s: Type: 6
    36.34s: From 3869434 to 3869457, length 23
    36.34s: Type: 6
    36.34s: From 3001488 to 3001506, length 18
    36.34s: Type: 6
    36.34s: From 2996230 to 3001462, length 5232
    36.34s: Type: 6
    36.34s: From 297 to 26358, length 26061
    36.41s: filter 1
    36.41s: keep 3
    36.41s:
    Number of entries: 31
    36.41s: Type: 6
    36.41s: From 297 to 26358, length 26061
    36.41s: Type: 2
    36.41s: From 26359 to 26367, length 8
    36.41s: Type: 5
    36.41s: From 26367 to 26797, length 430
    36.41s: Type: 2
    36.41s: From 26797 to 26805, length 8
    36.41s: Type: 2
    36.41s: From 26805 to 26842, length 37
    36.41s: Type: 5
    36.41s: From 26842 to 27660, length 818
    36.41s: Type: 5
    36.41s: From 27660 to 2996230, length 2968570
    36.41s: Type: 6
    36.41s: From 2996230 to 3001462, length 5232
    36.41s: Type: 2
    36.41s: From 3001462 to 3001463, length 1
    36.41s: Type: 2
    36.41s: From 3001463 to 3001487, length 24
    36.41s: Type: 5
    36.41s: From 3001487 to 3001488, length 1
    36.41s: Type: 6
    36.41s: From 3001488 to 3001506, length 18
    36.41s: Type: 5
    36.41s: From 3001506 to 3001507, length 1
    36.41s: Type: 5
    36.41s: From 3001507 to 3869434, length 867927
    36.41s: Type: 6
    36.41s: From 3869434 to 3869457, length 23
    36.41s: Type: 2
    36.41s: From 3869457 to 3869458, length 1
    36.41s: Type: 2
    36.41s: From 3869458 to 3869467, length 9
    36.41s: Type: 5
    36.41s: From 3869467 to 3869477, length 10
    36.41s: Type: 5
    36.41s: From 3869477 to 3916648, length 47171
    36.41s: Type: 2
    36.41s: From 3916648 to 3916657, length 9
    36.41s: Type: 2
    36.41s: From 3916657 to 3916666, length 9
    36.41s: Type: 5
    36.41s: From 3916666 to 3916667, length 1
    36.41s: Type: 6
    36.41s: From 3916667 to 3916685, length 18
    36.41s: Type: 5
    36.41s: From 3916685 to 3916686, length 1
    36.41s: Type: 5
    36.41s: From 3916686 to 3953366, length 36680
    36.41s: Type: 2
    36.41s: From 3953371 to 3953380, length 9
    36.41s: Type: 2
    36.41s: From 3953380 to 3953388, length 8
    36.41s: Type: 6
    36.41s: From 3953389 to 3953408, length 19
    36.41s: Type: 5
    36.41s: From 3953408 to 3953409, length 1
    36.41s: Type: 5
    36.41s: From 3953409 to 3962512, length 9103
    36.41s: Type: 2
    36.41s: From 3962512 to 3962520, length 8
    36.41s: hdtitles
    36.41s: Speed set to 2147483647
    36.41s: Sending Transparency 7
    36.41s: Sending Patchlevel 0
    36.41s: mode 1631 0x65f
     
  9. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    I know what the list of files is, the thing is if you want to receive help you need to post the ENTIRE ziplog for so the developers can analyze it with their diagnostic tools. Not just post the (partial) contents of one of the txt files.

    There's a reason for the sticky 'please read before you post. 'no logfile, we can't help you'

    Sent from my Pixel 3 XL using Tapatalk
     
  10. markfilipak

    markfilipak Well-Known Member

    Kindly bear with me. When I run "Create Logfile...", The results are displayed in seconds, not minutes. So, I conclude that, unlike a "Rip to Image..." run, the disc's VOBs are not read (and, indeed, the '.ziplog' contains copies of the VTS IFO files). If the disc is only partly read, then, unlike a rip, bad sectors will not be found.

    Background: Most programs make a log as they work. However, I once had a program that, when running a log function after the fact, it displayed the log of the previous operation (which it had apparently cached). For all I know, AnyDVD also works like that. ...Or not.

    Okay. It is attached.
     

    Attached Files:

  11. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    You conclude incorrect. AnyDVD scans the most part of the service, which is different from actually decrypting it. You don't need to decrypt something to detect a faulty disc sector. AnyDVD also doesn't work "like that", like your other programs. AnyDVD doesn't create a logfile until you ask it to. You can access CloneDVD2 logs after ripping by right-clicking somewhere in the white area of the "log" tab and selecting "create log. That said your log LOOKs clear to me, but i'm no expert, though such a long time would indicate a faulty disc, especially since thats a DVD release from 2000.
     
  12. markfilipak

    markfilipak Well-Known Member

    When I insert a DVD, AnyDVD scans it in about 5 seconds. If I click "Create Logfile...", AnyDVD makes a log file almost instantly.

    When I copy the contents of the DVD to a hard disk it takes 10 minutes or more.

    "Create Logfile..." can't possibly be reading the entire DVD.
     
  13. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    It doesn't need to and making a logfile isn't the same as ripping a disc.

    Sent from my Pixel 3 XL using Tapatalk
     
  14. markfilipak

    markfilipak Well-Known Member

    Kindly read my topic starter to see what the issue is.
     
  15. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    I did, and I'm telling you, anydvd does NOT create logs before, during or after a rip. It only creates logfiles on request via that right-click functionality.

    When you encounter problems during ripping, you then tell anydvd to create a logfile which analyzes the disc for the most part and puts it in that logfile. This doesn't scan the ENTIRE disc, but anydvd's 'AI Scanner' accesses the discs content based on what it detects in the structure.

    Making a logfile isn't the same as decrypting/ripping.

    2hrs+ for a dvd9 is highly unusual, even for a heavily structurally protected DVD which isn't the case here. Which leads to that it's most likely a dirty/defective disc, even more due to the age of that title. This is NOT a protection problem

    Sent from my Pixel 3 XL using Tapatalk
     
  16. markfilipak

    markfilipak Well-Known Member

    How did we get into a pissing contest?
    Really? Did you think I didn't know that?
    In a handfull of seconds, it analyzes the disc? Give me a brake.
    Really? How informative.
    Who mentioned protection? And the disc is not from 2000. It was mastered in 2006, reissued and pressed in 2017.

    The disc was not dirty. It is brand new, fresh out of the snap-case, untouched.

    I was hoping AnyDVD's log was a real log. It's not. It's useful only for profiling.

    What a disappointment.

    Warm Regards,
    Mark.
     
  17. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    Pressed on 2017 still makes it 2+ years old, unlikely to be a problem and again more likely a dirty/defective disc.

    Dirty here doesn't effectively mean fingerprints and stuff, discs often come with a near invisible oily full that can cause read errors. Then there's the fact that the human eye cannot see microscopic defects on disc sectors that happen during mastering, a drive laser on the other hand very much can. And then there's also the fact that we see this kind of behavior on a near weekly basis. Yes, even for brand new discs, straight out of the plastic wrapper.

    Nobody also said that anydvd's logfile logged the actual ripping. The logfiles are for diagnostic purposes only when troubleshooting disc problems.

    You've got all the info regards the logfile and the likelihood of it being a dirty/defective disc. It's now up to you to decide what you do with this information.

    Sent from my Pixel 3 XL using Tapatalk
     
  18. markfilipak

    markfilipak Well-Known Member

    Read errors are not the source of the 2 hour AnyDVD ripping time -- copying the entire disc to a solid-state RAID-0 takes 7.28 seconds (done 2 times and verified afterward by byte-by-byte comparison). Since AnyDVD apparently doesn't log its ripping operation, the cause of the 2 hour ripping time is completely unknown.

    Perhaps there's a bug related to the structure of this particular disc, eh? Given the lack of a log, what caused that excessively long ripping time is a mystery.
    Agreed. And that "Nobody" includes me.
    Since AnyDVD's "Create Logfile..." doesn't actually test the disc, it's pretty much useless, isn't it?
    You are kidding, right?
     
    Jaws_1 likes this.
  19. Jaws_1

    Jaws_1 Well-Known Member

    3xx0n Vald3z is never kidding or apologizing.
     
  20. markfilipak

    markfilipak Well-Known Member

    "3xx0n Vald3z" ???