title
Products            Purchase            Codec Central            Forum & Support            Professional            About
  
Results 1 to 3 of 3

Thread: error ripping to error opening file, check no other program has it open.

  1. #1

    Join Date
    Jan 2013
    Posts
    10

    Question error ripping to error opening file, check no other program has it open.

    Hello

    I am getting the message "error ripping to ..... error opening file, check no other program has it open [cidecoder::writeidtags]" when ripping with the Multiencoder on a quad core system.

    It is occurring sporadically but on most CDs on around 1-4 tracks on the CD

    As far as I can tell by experimentation the cause seems to be that the Windows Search Indexing service has temporarily opened the file and this locks out dbpoweramp from updating the tags - re-ripping the tracks almost always works first time.

    When I says seems I ripped 6 CDs and all but one had an error on at least one track. I then paused the Windows Search Indexing service and ripped another 6 CDs with no errors. So not conclusive but highly indicative.

    I had seem previous advice that security software can cause these symptoms and have excluded the relevant folders form scanning

    Any ideas welcome on how to get round this as pausing Windows Search Indexing service seems overkill - a longer delay in dbpoweramp would be one solution but there is no user option to modify this

    kind regards

    Martin

  2. #2
    Da Man Spoon's Avatar
    Join Date
    Apr 2002
    Posts
    28,547

    Re: error ripping to error opening file, check no other program has it open.

    We shall take a look at this again, the issue can be when ripping a track, it is ripped, it is tagged, then it is retagged to add accuraterip data, we have retry loops which wait to get access to the file, it could be these need making longer.

  3. #3

    Join Date
    Jan 2013
    Posts
    10

    Re: error ripping to error opening file, check no other program has it open.

    Quote Originally Posted by Spoon View Post
    We shall take a look at this again, the issue can be when ripping a track, it is ripped, it is tagged, then it is retagged to add accuraterip data, we have retry loops which wait to get access to the file, it could be these need making longer.
    Thanks - this all makes sense as I did notice that there was plenty of metadata in the files where the problem occured.

    As a short term workaround I have excluded the rip destination from Windows indexing - in the longer term making the loop wait longer would be better.

    All the best

    Martin

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Copyright 2014 Illustrate. All Rights Reserved.