Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer ScriptSync Bug? Error syncing: the file could not be created

  • ScriptSync Bug? Error syncing: the file could not be created

    Posted by Raoul Rosenberg on August 22, 2011 at 10:11 pm

    Is this happening to anyone else? I cannot get scriptsync to work. I keep getting the same error message “error syncing: the file could not be created.” I’ve used scriptsync successfully for years, but suddenly with this new version I can’t get it to work at all.

    I’ve tried every possible script formatting for text-(Mac, Unix, Win, UTF-8), and I’ve tried multiple different audio sources. I’ve tried uninstalling and reinstalling Media Composer and scriptsync. I’ve written short test scripts and consolidated media and fixed and changed my drive permissions.

    Avid tech support spent hours on the phone with me and couldn’t figure it out. They’ve elevated the problem to their software engineers.

    I’m using Media Composer 5.53 and OS X 10.6.8. I’m wondering why no one else is experiencing this problem?

    Thanks!

    Raoul

    Raoul Rosenberg replied 14 years, 2 months ago 2 Members · 2 Replies
  • 2 Replies
  • Doug O’connor

    March 14, 2012 at 6:30 pm

    Raul,

    Did you ever figure this out?
    I have the same error occurring.
    I am just trying to run script Sync as a trial for now, bur regardless.
    The fact that I am now going to have to pay 1000 dollars and waste time messing with something that used to work just fine and for free is a bit irritating.
    This system is 7.2 Imac 2.7 and avid MC 5.53

    I appreciate any insight you may have.

    Thanks,

    Doug
    Z Post NYC

  • Raoul Rosenberg

    March 14, 2012 at 11:00 pm

    Hi Doug,

    I eventually did figure it out. Turns out the answer is quite simple. It was a matter of the sharing and permissions on a media or system drive (forget which). I made sure that everyone had read and write privileges on my drives and the problem was suddenly solved.

    Hope that helps.

    Raoul

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