Forum Replies Created

Page 15 of 169
  • David Battistella

    April 16, 2012 at 12:12 pm in reply to: Warning about FCPX 10.0.4

    Thanks Ivan,

    I wonder if this relates to any of the problems I have been experiencing as detailed in the threads below.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://www.davidbattistella.com

  • David Battistella

    April 16, 2012 at 7:37 am in reply to: Watch out! 10.0.4 upgrade warning…

    Thanks Eric,

    Still no resolution on this one.

    I have the files sitting on a site for download if anyone wants to help out.

    They all opened in 10.0.3 but no luck in 10.0.4

    Everyone should also be aware that if you have ONE corrupt project in the project list, then it appears that NOE of the other projects in the list will open.

    Through a series of tests, I have found that once the corrupt project is isolated then the rest of the projects open fine. It’s figuring out which one is corrupt.

    It’s a good thing I run EVENT MANAGER X, because it streamlined the testing process.

    I’m also in touch with Apple on this, so hopefully we can discover what went wrong.

    I wish I could revert back o 10.0.3 for about two hours, but alas, I discovered my time machine partition was backing up “another drive with an old OS” .

    Thanks for all the help so far and hopefully I can get this resolved.

    Usually these upgrades are no problem at all, but this one project is giving me some grief at the moment.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://www.davidbattistella.com

  • David Battistella

    April 15, 2012 at 3:16 pm in reply to: Watch out! 10.0.4 upgrade warning…

    Reporting back again, it seems pretty certain that what I am dealing with here is a corrupt project file that for some reason will not allow itself to be updated to 10.0.4.

    The files opened fine in FCP 10.0.3 until the update.

    Every other project has come across painlessly, going right back to the very first project I ever did and wrote about here on the COW just one day after the public release.

    The only thing I can think of is that this was the only project I ever used “Auto remove silence” on and it seemed to put gremlins into the system.

    Now, I am just hoping I can get it opened in 10.0.3 and get an XML out of there so I do not have to rebuild a 25minute film from memory…

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://www.davidbattistella.com

  • David Battistella

    April 15, 2012 at 1:34 pm in reply to: Watch out! 10.0.4 upgrade warning…

    Eric,

    Would you consider trying to open up the 10.0.3 version of the project and send me an. XML if you can open it?

    It sitting up on a website where it can be downloaded.

    Anyone?

    I really would love to just get my last cut back up and running.

    Thanks

    You can get my email in my contact page.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    April 14, 2012 at 9:20 pm in reply to: Watch out! 10.0.4 upgrade warning…

    Thanks Bill,

    I’ll keep posting as I work toward a solution.

    Hopefully I can get an XML out of the sequence that was working in 10.0.3 so I can get this film finished.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    April 14, 2012 at 6:01 pm in reply to: Watch out! 10.0.4 upgrade warning…

    here is a breakdown of all that I have tried.

    I think I have this narrowed down to a corrupt project file which can not be updated to 10.0.4.

    I just need to get an XML out of FCP X and import the XML into the new version. My problem now is that both of my machines have been updated to FCP X .0.4 (I know, I can commit a boneheaded move once in a while)

    I have it narrowed down to one corrupt project file (unfortunately the latest version of the cut).

    Tried Digital Rebellion toolkit
    Tried ONYX
    Tried backup versions of multiple projects.
    Tried repairing permissions, etc.
    Tried to install and uninstall KONA 3 drivers.

    Let’s put it this way. It’s been a troubleshooting kind of day. All of my projects open in 10.0.4 except the current version of the latest thing I am working on.

    If anyone wants to open this file for me in FCP X 10.0.3 and export an XML and get that to me, I would appreciate it.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    April 14, 2012 at 6:13 am in reply to: Watch out! 10.0.4 upgrade warning…

    Thanks Bill,

    I’ve actually followed that exact procedure and everything is stored externally. I’ve left the software for over an hour thinking it was exactly what you describe so well.

    I’ve provided feedback to apple and will continue to troubleshoot and report back in this thread.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    February 28, 2012 at 2:45 pm in reply to: Hey Guys

    Have you tried the relink media command?

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    February 28, 2012 at 9:09 am in reply to: Hey Guys

    The file has to be named current project.

    I had this happen to me on a couple of projects and I navigated to the folder level and renamed the project file “currentversion” at the project folder level.

    If there is no “current version” then duplicate the backup and rename it current version in the folder.

    After this FCP X could see and open the file normally.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

  • David Battistella

    February 24, 2012 at 12:08 pm in reply to: custom naming on capture

    Fabio.

    It’s generally a horrible idea to rename actual media files because that file is often tied to the original media folder generates one of zillions of unique names. If you really want to this then you should do it before you import.

    Use a utility software like:

    “A better finder rename”

    This lets you rename everything you want at the finder level. Once you have renamed the clips then they will carry that name when you bring them into FCP X.

    David

    ______________________________
    The shortest answer is doing.
    Lord Herbert
    https://vimeo.com/battistella

Page 15 of 169

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