Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Boris FX Autorecovery file

  • Autorecovery file

    Posted by Alison Stevenson on August 24, 2007 at 9:08 am

    When I start the red engine, I’m told that there’s an autorecovery file, and invited to save it. Whether I save or cancel, the same thing happens next time I start up.

    I also get this running red as a filter in Final Cut Pro.

    Where is this autorecovery file, and how do I get rid of it?

    Alison

    Stable Recordings
    Scotland

    **better a has-been than a never-was**

    Chaim Mehlman replied 18 years, 1 month ago 3 Members · 9 Replies
  • 9 Replies
  • Peter Mcauley

    August 24, 2007 at 3:44 pm

    Hi Alison,

    You can disable this feature by going into the RED preferences window, then selecting the Tools tab and un-checking the Auto-Save feature.

    Cheers,

    Peter.

  • Alison Stevenson

    August 25, 2007 at 10:22 am

    Autosave is off, and has been throughout.

    Stable Recordings
    Scotland

    **better a has-been than a never-was**

  • Peter Mcauley

    August 26, 2007 at 2:24 pm

    Interesting alright. What is your system configuration?

    Thanks,

    Peter.

  • Alison Stevenson

    August 29, 2007 at 7:25 am

    Sorry for the slow response.

    It’s Boris Red 4.1, either standalone or in Final Cut Pro 5.1.4.

    The computer is a G5 2.7 Dual with 2 GB ram and OS 10.4.10.

    Graphics card is ATI Radeon X850 XT.

    Alison

  • Peter Mcauley

    August 29, 2007 at 4:58 pm

    Hi Alison,

    We’re looking into this and I expect that we should have some more information regarding this anomaly either today or tomorrow.

    Cheers,

    Peter.

  • Peter Mcauley

    August 29, 2007 at 5:19 pm

    Hi Alison,

    Good news – it’s a problem that we have seen before and have a fix for. Here’s what to do:

    https://www.borisfx.com/download_files/CalligraphyForFCP.dmg
    where download_files has an underscore instead of a space

    Then copy the plugins from the .dmg into the folder
    /Library/Application Support/Final Cut Pro System Support/Plugins

    Please let me know how this works for you.

    Cheers,

    Peter.

  • Peter Mcauley

    August 29, 2007 at 8:11 pm

    hi Alison,

    Here’s the information that you need to find and delete the offending file. Once you delete this file the problem should disappear.

    Cheers,

    Peter.

    From the program /Applications/Utilities/Terminal, you can enter the line:

    ls -R -l / | grep -B 15 _autorecovery

    (where | is the shift-\ symbol, and where the -l is dash letter-L-lowercase )
    and see if anything comes up on the hard drive. You can copy and paste that line into the Terminal window. It will take a long time to search. You can ignore the Permission denied errors, since the file of interest was written by this user and can be seen. If you see the file, but this doesn’t list the folder, then increase the 15 to a higher number of lines to look back, like 100, and you should see the path and the file in the output.

  • Alison Stevenson

    August 30, 2007 at 7:49 am

    Thanks Peter.

    Deleting the autorecovery files did the trick.

    Now I’m trying to work out what the search command was actually doing – I must learn Unix one day. 🙂

    Alison

    Stable Recordings
    Scotland

    **better a has-been than a never-was**

  • Chaim Mehlman

    July 7, 2008 at 4:33 pm

    I’m sorry but I need more information on this answer. What do you mean “see if anything comes up on the hard drive”? Comes up where? Paste it from where? And how will that delete the file?

    I have tried this several times and the closest thing to what you’re talking about looks like this:

    /Applications/Final Cut Pro.app/Contents/MacOS:
    total 37720
    -rw-r–r–@ 1 Chaim admin 21240 11 May 13:41 BorisFX_autorecovery

    When I try pasting this back it says “no such file or directory”.

    Can you please give me some more help or someone please fix this bug????!!!!

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy