Previous 1 2 3 4 5 Next 100 Replies Latest reply: Sep 29, 2012 2:02 PM by Tom Wolsky Go to original post Branched to a new discussion.
  • the black sun Level 1 Level 1 (100 points)

    And this is somehow Apples fault?

    You should seriously start to look at the way you do things mate.

    Making blank statements like this helps nobody - including your good self!

  • iPhone 4ness Level 1 Level 1 (0 points)

    Actually yes it is Apple's fault. Austosave not working? I must be doing something wrong...like using FCPX to edit a video.

  • the black sun Level 1 Level 1 (100 points)

    Using Snow Leopard of Lion? The autosave is a LION thing as I pointed out on several occasssions before...

  • hafken Level 4 Level 4 (1,225 points)

    the black sun wrote:

     

    Using Snow Leopard of Lion? The autosave is a LION thing as I pointed out on several occasssions before...

    ...and on every single one of those occasions you are incorrect.

     

    Lion is an operating system. It provides autosave only for applications that have been written to take advantage of that feature.

     

    FCP X is an application meant to run on Snow Leopard, as well as Lion.

     

    FCP X has a built-in autosave regardless of whether you run on Snow Leopard or Lion. In fact, it doesn't use Lion's autosave features (yet). It's own built-in implementation DOES NOT WORK for some people. Even for some people on Lion.

  • andynick Level 5 Level 5 (4,925 points)

    Reluctantly, I must join this long list of complainants.

    I'm using 10.7.1 (Lion) and I've been a keen supporter of FCP X. Some of its features are amazing but today I lost around six hours of keywording because Autosave didn't work.

     

    I'll keep checking the Undo in future in the hope that it will let me know when Autosave isn't working.

     

    I'm sure Apple will come in with an update very soon, otherwise, I must begin to look around. My project won't wait for Apple.

    Andy

  • Pancenter Level 6 Level 6 (8,745 points)

    andynick wrote:

     

    I'm sure Apple will come in with an update very soon, otherwise, I must begin to look around. My project won't wait for Apple.

    Andy

     

    Unfortunately, for some... "soon" has come and gone.

     

    Should never have been released with this stuff happening... I mean, if you're a "youtube" producer I guess it can be lived with but this is unlike Apple.

  • andynick Level 5 Level 5 (4,925 points)

    FCP 7 seems to work OK in Lion, so I guess I'll go back there for now.

    It will seem very crude compared to FCP X but at least my work will be saved!

  • andynick Level 5 Level 5 (4,925 points)

    I agree, Pancenter.

     

    Fabulous application, but released way before it was ready.

     

    I wonder how many man-hours have been wasted worldwide by people who bought it (me for one).

    Andy

  • Tiberio1986 Level 1 Level 1 (0 points)

    Essentially, with this problem, there is no way we can actually finish our projects! It's actually just a huge tease, the whole thing.  We can look at our projects make it to a certain point, but as soon as that skimmer or undo option is gone, fear for your lives.  This is ridiculous.  My business is depending on this program working and it is not.  I think maybe we should all get together and picket outside of Steve Jobs' house until we are granted with a royal revision of this program.

  • alicanlondon Level 1 Level 1 (90 points)

    Tiberio1986 wrote:

     

    This is ridiculous.  My business is depending on this program working and it is not.  I think maybe we should all get together and picket outside of Steve Jobs' house until we are granted with a royal revision of this program.

     

    Your business is depending on this program working?  Is this your first and only editing application? 

  • andynick Level 5 Level 5 (4,925 points)

    Tiberio1986 wrote: My business is depending on this program working and it is not.

     

    I'm glad I'm not in business with you if you sail that close to the wind!

  • Tiberio1986 Level 1 Level 1 (0 points)

    No and that question really has no relevance to the issue.  I've worked on most versions of most editing systems (Avid, Final Cut, Adobe) but this is what I have to work with now because it's most affordable and up-to-date and my business is a start-up; currently just me.  If this is the future layout we might as well be learning it, but we need to be getting better than a program that loses saved progress.  Anything wrong with that argument?

  • RedTruck Level 4 Level 4 (2,145 points)

    FYI: The maximum "open files" limit on Mac OS is 256. You can find this by opening Terminal and typing:

     

    ulimit -n

     

    Whenever you have a program that has an autosave, as well as an unlimited amount of undos, the computer has to keep every version of the file open to that you can return to it when you hit cmd-z. There actually isn't such a thing as "undo". It's a figure of speech. What's really happening is, the program reverts to the most recent "save". Therefore, any action you do in FCPX that is able to be undone creates a new open file. Once that limit reaches 256, you will not be able to save anymore. Sounds like most people are losing about 3 hours at the low end. I would assume, then, that it takes the average FCPX user about 3 hours (maybe less) to execute 256 undoable actions.

     

    There are two things that can be done to alleviate this problem. The first is to find out where FCPX stores these temporary files. I don't have FCPX, so I can't tell you exactly where, but I would assume it's somewhere in:

     

    private/var/

     

    If you find either the folder where the open files are in, trash them. Or, if those files are stored in a .db file, trash that. The issue here is that you will lose ALL ability to undo from that point backwards. It's essentially the same as quitting and opening the project again. Which is your second option.

     

    Option 2: quit FCPX every hour or so. If you're a heavy editor, quit more often. It may seem like a hassle, but it's a lot less of a hassle than losing work.

     

    It used to be that having File Sharing activated lessened your open file limit, but I don't know if that's still the case. At one time Mac OS had something like 12800 files that could be open. But I just turned off file sharing and still got the same 256 file limit.

     

    Anyway, the point is, you can't have any more than 256 files in your undo stack. Either find where the stack is stored, or quit and restart regularly.

     

    Hope this helps someone.

     

     

    p.s. if you recall, the reason you never hit this wall in previous versions is becasue undo was limited to 99 at most, set in User Preferences.

  • andrewfromcincinnati Level 1 Level 1 (0 points)

    I successfully requested and received a refund for FCPX...and I would recommend everyone who is having issues do the same. I tried to do a couple of projects, but after a couple of weeks working through the new interface, the bugs and lack of some familiar features, I had to throw in the towel. You can still "use" the software, but can always re-purchase once a useable update becomes available.

    My 2¢

  • Tiberio1986 Level 1 Level 1 (0 points)

    My business is a start-up, it's only me at this point, and this program and system (iMac 27" i7) are most up-to-date and more affordable than purchasing FCP Studio 3 since Apple discontinued it.  If you disagree with my issue, which would mean you justify a program that can't successfully save data, I suggest you make that point rather than randomly attack me.

Previous 1 2 3 4 5 Next