That's it for me - Project work disappeared...

I agree. I think the program has enormous potential. Hence why I am using this program instead of the others because as long as I'm a start-up biz I have the opportunity to learn the new layout for the future progression of the program. However, these technicalities are very inconvenient and we do need to ask Apple to give us bug-fixes/updates asap because for a lot of people like myself it is making certain tasks impossible, and there are certain deadlines we're trying to meet to get ourselves going.

Tiberio1986 wrote:

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.

I don't justify a programme that can't successfully save data - it's wrong and Apple clearly released this great application far too early.

But your reaction is somewhat 'OTT' in my opinion. It's a truly great application and once the bugs are ironed out, it will wipe the floor with the opposition.

That's why I've decided to stick with it, and use RedTruck's suggestion of quitting the app once every hour or so to clear the undo stack.

Andy

I respect your humble opinion that you find the program is 'great.' In my opinion, a program that is having such issues is decent at this point, and has the potential to be great. But keep writing to Apple and keep hounding them because that will get us where we need.

Tiberio1986 wrote:

I respect your humble opinion that you find the program is 'great.' In my opinion, a program that is having such issues is decent at this point, and has the potential to be great. But keep writing to Apple and keep hounding them because that will get us where we need.

I'm sure Apple have got the picture by now - but no reason not to keep reminding them if you want to (and have the time).

I've sent in my Bug report (the correct way to do this stuff) and now I'm concentrating on my project. If I have to restart FCP X every hour, that's no big problem - I'll try RedTruck's suggestion tomorrow.

Andy

Tiberio1986 wrote:

I respect your humble opinion that you find the program is 'great.'

Who said my opinion is 'humble'?

Andy

Don't want to interfere with your work so I'll cut it here, but also call 1-800-275-2273 and talk to a specialist in Final Cut and explain to them this same problem. Ask them to send a report to the engineering deparment so that more people on their end get the word. As even Apple employees themselves admit, often those bug reports are disregarded as opposed to direct word of mouth. Good luck on your project Andy I wish you the best.

That may be how Undo is implemented in FCX or maybe in FCP, but I'm not sure you can make a blanket statement that all Undo's follow that method.

When I implemented Undo, I atomized each operation into a series of actions that had a reversible counter command and threw that counter command on a stack. Thus the Undo was simply executing the stack of counter commands to reverse the operation.

Just saying there is more than one way to skin a cat...

Patrick Sheffield

Sheffield Softworks

andynick wrote:

I've sent in my Bug report (the correct way to do this stuff) and now I'm concentrating on my project. If I have to restart FCP X every hour, that's no big problem - I'll try RedTruck's suggestion tomorrow.

Andy

Actually, there is no "correct" way at this time and with a program so full of bugs.

The facts are.. Apple engineers have directly emailed people in relation to posts/complaints/problems that have appeared on this board.

I would say the "correct" way at this point is the one that gets results.

The facts are.. Apple engineers have directly emailed people in relation to posts/complaints/problems that have appeared on this board.

... any 'facts' to back this one up?

A funny thing happened while I was reading through some of this thread; my mac just crashed! Therefore it MUST be Apples fault.

Who, but a mad man, would base their workflow on software that is so obviously a 'work-in-progress' version?

The fault lye's, not in the stars dear Brutus, but in our selves... 😁

the black sun wrote:

The facts are.. Apple engineers have directly emailed people in relation to posts/complaints/problems that have appeared on this board.

... any 'facts' to back this one up?

A funny thing happened while I was reading through some of this thread; my mac just crashed! Therefore it MUST be Apples fault.

Who, but a mad man, would base their workflow on software that is so obviously a 'work-in-progress' version?

Facts to back the statement up...

Several posters in these threads who've relayed their correspondence with said engineers. (you have to actually read the posts)

Apple released this software with great fanfare, "Revolutionary" it was touted as... but the facts are, it's not even close to being ready for prime time.

They released a product that shouldn't have been released and made "paying" Beta testers out of their customers.

I'm sure in a year or so it will be much more stable but right now the Apple has a worm hanging out of it.

Pancenter wrote:

the black sun wrote:

Several posters in these threads who've relayed their correspondence with said engineers. (you have to actually read the posts)

And the links to these posts are where . . ?

A great many of us would be very interested to see real evidence that your statement is correct.

Andy

RedTruck wrote: 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.

I'm sure you wrote this with the best of intentions but it didn't work for me. I opened FCP X. Added no more than a dozen keywords (three new) and closed the app.

I then checked some email, hurled a few random insults at others on the Apple FCP X Discussion Group (not really) and then reopened FCP X.

None of my new keywords were present. There's no way I got near the magic 256 figure - not even 56.

I'm REALLY disappointed - Last night, when I read your post, I thought this could have been a useable workaround.

andynick wrote: I opened FCP X. Added no more than a dozen keywords (three new) and closed the app.

I then checked some email, hurled a few random insults at others on the Apple FCP X Discussion Group (not really) and then reopened FCP X.

None of my new keywords were present. There's no way I got near the magic 256 figure - not even 56.

Either I'm going mad (never rule that out) or I don't know what . . .

I just downloaded Preference Manager from Digital Rebellion:

http://www.digitalrebellion.com/prefman/

Backed up FCP X Preferences, then trashed the originals.

I reopened the application - and as if by magic, the keywords I added this morning were there!

Curiouser and curiouser.

Andy

your starting to loose it mate! 😁

I was going to mention preferences to you but, you worked it out - nice one...