title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Meaning of entries in the Extraction log

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sredmyer
    dBpoweramp Enthusiast

    • May 2008
    • 186

    Meaning of entries in the Extraction log

    I have asked this question before but I am still confused so I will reform the question and ask again. I am trying to understand what exactly the extraction log is telling me. So, to form the question as accurately as possible (and therefore hopefully elicit the answers I need) I will split the question into two parts.

    The first part:
    Defining the meaning of the various possible results.
    1. Accurate (confidence n):
    This means that the AccurateRip CRC calculated from the extracted audio of this track matches with (n) entries for this same track in the AccurateRip database.

    2. Inaccurate (confidence n):
    This means that the AccurateRip CRC calculated from the extracted audio of this track does not match with (n) entries for this same track in the AccurateRip database.

    3. Secure:
    This means that the track did not match the AccurateRip database entry (or there was no entry) for this track. However, there were no errors found during the extraction process and the CRC calculated from the extracted audio from 2 passes did match.

    4. Secure (warning):
    This means that the track did not match the AccurateRip database entry (or there was no entry) for this track and there were errors found during at least one pass of the extraction process. However, the CRC calculated from the extracted audio from 2 passes did match.

    5. Insecure:
    This means that the track did not match the AccurateRip database entry (or there was no entry) for this track and the CRC calculated from the extracted audio from N (where n = the number of passes defined in the ultra settings) passes did produce at least 1 match.

    Lastly, any of these result designations can be augmented by a re-rip requirement. Which simply means that the result stated was reached after attempting to re-rip some number of individual frames.

    The questions for this first part are:
    1) Are the descriptions of result designations given above correct?
    2) Are the descriptions complete (are there other possible results)?


    The second part:
    Here my question has to do with the “Pass” portion of the extraction log. I simply do not understand this information.

    Here are some examples of extraction log entries (these are all from a single log file):
    1)
    AccurateRip: Accurate (confidence 12) [Pass 1]
    To me it is obvious that what is being reported is that the extraction achieved the stated result (Accurate) in a single pass.

    2)
    AccurateRip: Accurate (confidence 12) [Pass 1 & 2]
    To me this means that it took 2 passes to achieve an accurate result.

    3)
    AccurateRip: Accurate (confidence 12) [Pass 1 & 2, Cross-Check Match ]
    To me this also means that it took 2 passes to achieve an accurate result

    4)
    AccurateRip: Inaccurate (confidence 12) Insecure [Pass 1 & 2, Ultra 1 to 6, Re-Rip 47 Frames]
    Although I can see that this track is inaccurate and insecure after re-ripping 47 frames. However, I have no idea what is being reported as to the number of passes.

    5)
    AccurateRip: Accurate (confidence 12) [Pass 1 & 2, Ultra 1 to 4, Re-Rip 8 Frames]
    Again I can see that the track is accurate after re-ripping 8 frames but how did it get there and why?

    The following examples are taken from different log files.
    6)
    Secure [Pass 1 & 2, Ultra 1 to 2]
    Obviously the track is secure but was it completed in 2 passes or 4 (2 regular plus 2 ultra)?

    7)
    AccurateRip: Inaccurate (confidence 61) Secure (Warning) [Pass 1 & 2, Ultra 1 to 3, Re-Rip 11 Frames]
    How many passes were actually done here?

    8)
    AccurateRip: Inaccurate (confidence 61) Secure (Warning) [Pass 1 & 2, Ultra 1 to 4, Re-Rip 130 Frames]
    This entry is from the same log as the entry above. Why only 3 ultra passes above and here we have 4?

    Thanks in advance for helping me to understand this output.
    Steve
  • Spoon
    Administrator
    • Apr 2002
    • 44509

    #2
    Re: Meaning of entries in the Extraction log

    >1) Are the descriptions of result designations given above correct?

    Yes

    >2) Are the descriptions complete (are there other possible results)?

    The Inaccurate can be a false positive, in that there could be another pressing in the database.

    >Although I can see that this track is inaccurate and insecure after re-ripping 47 frames. However, I have no idea what is being reported as to the number of passes.

    The ripper was instructed to do the Ultra Secure passes.

    >Again I can see that the track is accurate after re-ripping 8 frames but how did it get there and why?

    Often errors are present until the drive tries a number of times to recover them.

    >Obviously the track is secure but was it completed in 2 passes or 4 (2 regular plus 2 ultra)?

    4 complete passes.

    7. 5 passes

    8. More errors were discovered on one of the passes,
    Spoon
    www.dbpoweramp.com

    Comment

    • sredmyer
      dBpoweramp Enthusiast

      • May 2008
      • 186

      #3
      Re: Meaning of entries in the Extraction log

      Originally posted by Spoon
      >1) Are the descriptions of result designations given above correct?

      Yes

      >2) Are the descriptions complete (are there other possible results)?

      The Inaccurate can be a false positive, in that there could be another pressing in the database.

      >Although I can see that this track is inaccurate and insecure after re-ripping 47 frames. However, I have no idea what is being reported as to the number of passes.

      The ripper was instructed to do the Ultra Secure passes.

      >Again I can see that the track is accurate after re-ripping 8 frames but how did it get there and why?

      Often errors are present until the drive tries a number of times to recover them.

      >Obviously the track is secure but was it completed in 2 passes or 4 (2 regular plus 2 ultra)?

      4 complete passes.

      7. 5 passes

      8. More errors were discovered on one of the passes,
      Spoon,

      Thanks for the reply but there is still one point I do not understand. When looking at numbers 2 & 3 in the sample data I provided, both show that 2 passes were required to achive the AccurateRip result. However, *blooper*3 says it was done using a "Cross-check match"...what does this mean? How is this check different than the one recieved in *blooper*2 which just states "[Pass 1 & 2]"?

      Thanks,

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 44509

        #4
        Re: Meaning of entries in the Extraction log

        Cross match means parts from pass 1 and parts from pass 2 were used to get a matching 'accurate' rip.
        Spoon
        www.dbpoweramp.com

        Comment

        • EliC
          dBpoweramp Guru

          • May 2004
          • 1175

          #5
          Re: Meaning of entries in the Extraction log

          Originally posted by Spoon
          Cross match means parts from pass 1 and parts from pass 2 were used to get a matching 'accurate' rip.
          The technology is already there. Now if only we could do the same thing with multiple drives ;-)

          Comment

          • sredmyer
            dBpoweramp Enthusiast

            • May 2008
            • 186

            #6
            Re: Meaning of entries in the Extraction log

            Originally posted by Spoon
            Cross match means parts from pass 1 and parts from pass 2 were used to get a matching 'accurate' rip.
            To verify I understand you correctly then:

            When the track with Crass match ripped the first pass there were errors. Then when it ripped the second pass those same errors did not exist (although there may have been others in different places on the track). Then the software assembled a pseudo 3rd pass using only the error-free frames from pass one and the error-free frames from pass two. This 3rd pseudo pass was then checked against accuraterip successfully.

            For the track that reported "Accurate [Pass 1 & 2]", we can assume that pass 1 did not result in an accurate rip but pass 2 did since had pass 1 been accurate there would have been no pass 2.

            Are these accruate statements?

            thanks,

            Comment

            • EliC
              dBpoweramp Guru

              • May 2004
              • 1175

              #7
              Re: Meaning of entries in the Extraction log

              Originally posted by sredmyer

              For the track that reported "Accurate [Pass 1 & 2]", we can assume that pass 1 did not result in an accurate rip but pass 2 did since had pass 1 been accurate there would have been no pass 2.
              That is my understanding.

              Comment

              • Spoon
                Administrator
                • Apr 2002
                • 44509

                #8
                Re: Meaning of entries in the Extraction log

                Correct
                Spoon
                www.dbpoweramp.com

                Comment

                • sredmyer
                  dBpoweramp Enthusiast

                  • May 2008
                  • 186

                  #9
                  Re: Meaning of entries in the Extraction log

                  Ok Spoon, sorry to be such a bother but now I have one more extraction log entry I can not decipher.

                  What is this log entry telling me?
                  Re-rip Frame: 152379 (00:00:39.160). Insecure (c2 dropped 39) [c2 best match]
                  Specificaly what is meant by "c2 dropped 39" and "[c2 best match]"?

                  Thanks

                  Comment

                  • EliC
                    dBpoweramp Guru

                    • May 2004
                    • 1175

                    #10
                    Re: Meaning of entries in the Extraction log

                    Originally posted by sredmyer
                    Ok Spoon, sorry to be such a bother but now I have one more extraction log entry I can not decipher.

                    What is this log entry telling me?


                    Specificaly what is meant by "c2 dropped 39" and "[c2 best match]"?

                    Thanks
                    I don't know either. I have looked around for an explanation for all of these logs to link to for you but cant find one.

                    Comment

                    • Spoon
                      Administrator
                      • Apr 2002
                      • 44509

                      #11
                      Re: Meaning of entries in the Extraction log

                      It means that normally that frame would be marked as insecure, but one the frame passed c2 pointer verification, so this potentially good frame will be used.
                      Spoon
                      www.dbpoweramp.com

                      Comment

                      Working...

                      ]]>