illustrate
Products            Buy            Support Forum            Registrations            About           
 

Rip status error

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • garym
    replied
    Re: Rip status error

    Originally posted by Hitarth
    sir, here is the error screen shot[ATTACH=CONFIG]1870[/ATTACH]

    This isnt a ripping error. Looks like a problem accessing the J drive. What is j? A NAS? Try ripping to c drive and see if it works.

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Originally posted by garym
    Sorry, I think you are confused. This one also shows that all tracks ripped with AR match. Keep in mind that it does not matter that the ripper has to do re-reads during the ripping, so long as the final result is secure. Perhaps that is what you are seeing.
    sir, here is the error screen shotClick image for larger version

Name:	2017-11-21 (2).png
Views:	1
Size:	27.4 KB
ID:	293749

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Originally posted by garym
    Sorry, I think you are confused. This one also shows that all tracks ripped with AR match. Keep in mind that it does not matter that the ripper has to do re-reads during the ripping, so long as the final result is secure. Perhaps that is what you are seeing.
    agreed, I am putting the screen shot of the ripped file again ... Click image for larger version

Name:	2017-11-21 (1).jpg
Views:	2
Size:	96.6 KB
ID:	293748 if u see .. one track is missing

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Originally posted by garym
    Your log shows that all 16 tracks are verified with accuraterip, including track 10. Why do you think there is an error. Did you copy the files somewhere else after ripping? If so, could be corruption when copying.
    if you see in the attached screen shot of the ripped files ... one file is missing...song no. 7Click image for larger version

Name:	2017-11-21 (1).jpg
Views:	2
Size:	96.6 KB
ID:	293747

    Leave a comment:


  • garym
    replied
    Re: Rip status error

    Originally posted by Hitarth
    and I have 1 more ... [ATTACH]1866[/ATTACH]
    Sorry, I think you are confused. This one also shows that all tracks ripped with AR match. Keep in mind that it does not matter that the ripper has to do re-reads during the ripping, so long as the final result is secure. Perhaps that is what you are seeing.

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Originally posted by garym
    Settings are fine. You have not posted anything showing an error. What you posted showed that the cd ripped with no errors.
    pls check the attached log file ... if not there, I am attaching againlog.txt

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Originally posted by garym
    Your log shows that all 16 tracks are verified with accuraterip, including track 10. Why do you think there is an error. Did you copy the files somewhere else after ripping? If so, could be corruption when copying.
    and I have 1 more ... log.txt

    Leave a comment:


  • garym
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... [ATTACH=CONFIG]1865[/ATTACH]
    Settings are fine. You have not posted anything showing an error. What you posted showed that the cd ripped with no errors.

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    Originally posted by garym
    Your log shows that all 16 tracks are verified with accuraterip, including track 10. Why do you think there is an error. Did you copy the files somewhere else after ripping? If so, could be corruption when copying.
    hi, thanks .. yes, I notices that too .... pls find attached my setting. all my ± 100 CDs are ripped ok .. this particular CD is ripped with the same error message twice ... Click image for larger version

Name:	2017-11-21.png
Views:	1
Size:	34.1 KB
ID:	293744

    Leave a comment:


  • garym
    replied
    Re: Rip status error

    Originally posted by Hitarth
    hi .. I'm not sure if this is under the correct thread ... I was ripping a CD with 16 tracks ... and all are ripped well except the 10th track ... pls find attached the error report.[ATTACH]1863[/ATTACH]

    would appreciate any assistance ...
    Your log shows that all 16 tracks are verified with accuraterip, including track 10. Why do you think there is an error. Did you copy the files somewhere else after ripping? If so, could be corruption when copying.

    Leave a comment:


  • Hitarth
    replied
    Re: Rip status error

    hi .. I'm not sure if this is under the correct thread ... I was ripping a CD with 16 tracks ... and all are ripped well except the 10th track ... pls find attached the error report.log.txt

    would appreciate any assistance ...

    Leave a comment:


  • Kevin Lowe
    replied
    Re: Rip status error

    Thanks guys - I sussed it! My drive is full. Not surprising given the number of files! I switched drives and it worked fine.
    Kevin

    Leave a comment:


  • Dat Ei
    replied
    Re: Rip status error

    Could you post the error message please?


    Dat Ei

    Leave a comment:


  • Kevin Lowe
    replied
    Re: Rip status error

    First time posting - hope correct thread. I've used the ripper for several years and loved it - ripped over 2000s CDs. But just upgraded to v16.2 and am going crazy.
    Just cannot get it to work. Keep getting message 'error initialising flac encoder'. I have switched on debugger and checked all settings as far as I can see and just run out of ideas. Please help!

    Leave a comment:


  • garym
    replied
    Re: Rip status error

    Originally posted by marty.h.au
    Very old thread but it had the answer. I turned off C2 pointers and it's rolling! Very surprisingly quickly. I have a LG drive as well as eaglescout1998. Technical Details show support for C2, test CDs show it, but it would grind through the 60 re-reads (up from the default 34 because I thought C2 was supported...) immediately after starting and then Error out on each track.

    It now takes seconds to rip each track with Accurate 8 on all tracks on the same CD. Secure and Ultra Secure enabled. It was recently bought. Another CD I bought in 2002 said Accurate 5555455 and then AR 9 / Secure on track 8. Because it's dirtier? This and quite a few of my other CDs have mould spots on them from living in moist areas. Now I just need a good way to clean CDs....
    A higher AR secure number does NOT mean it is more secure. Even an AR of 1 means you have an exact match to someone else who ripped a different copy of cd on a different machine. (Unless you are ripping your same cd again, then any AR of 2 or better means you are good.

    Leave a comment:

Working...