FCPX USers some user thoughts please.

As for Compressor, notice it is not getting updated at all? Notice that OS X 10.8 does half of Compressor's work in the OS itself (right-click a video file, what's at the bottom of the pop-up menu)? I sure hope Compressor evolves, too. But I'm not hopeful. I can see it being dropped soon. Logic Pro gets folded into GarageBand, called Logic X, or GarageBand X, and we get the downgrade just like we did going from Color to FCP X, or from Shake to Motion, or from Final Cut Server to FCP X. None of that was good.

Aside from no support for pro audio and no shared network media management support, I love FCP X a lot.
 
Has anyone had a big drop in stability with the new version 10.0.6? It crashes more times than a Microsoft tech demo. Mostly to do with outputting via Sharing. I also have a problem now where the saved .mov files crash when loaded into Adobe Media Encoder. With the improvement in stability over the various versions the latest update seems to be a step backwards. I'd be interested to find out if anyone else is having issues, or if it's just my machine.
 
Matt Turner said:
Has anyone had a big drop in stability with the new version 10.0.6? It crashes more times than a Microsoft tech demo. Mostly to do with outputting via Sharing. I also have a problem now where the saved .mov files crash when loaded into Adobe Media Encoder. With the improvement in stability over the various versions the latest update seems to be a step backwards. I'd be interested to find out if anyone else is having issues, or if it's just my machine.
Click to expand...

I've seen just the opposite. More stability. The one thing that does bug me with this update is, I preferred just exporting a master file the old way and actually having it tie up FCPX for me briefly to render. I like the benefit of the background rendering that lets me keep working, but what about the times when I just want the program to use as much power as possible? It seems to me that even sending it to Compressor is a step backwards. FCPX used to export for me a master file like a snap of the fingers...they've actually made it harder/slower to do that now for the benefit of being able to keep working while it does it. I'm not really a fan of that. Sometimes I want to see something fast and can't really keep moving until I see it.

Am I missing something here?
 
KyleProhaska said:
I've seen just the opposite. More stability. The one thing that does bug me with this update is, I preferred just exporting a master file the old way and actually having it tie up FCPX for me briefly to render. I like the benefit of the background rendering that lets me keep working, but what about the times when I just want the program to use as much power as possible? It seems to me that even sending it to Compressor is a step backwards. FCPX used to export for me a master file like a snap of the fingers...they've actually made it harder/slower to do that now for the benefit of being able to keep working while it does it. I'm not really a fan of that. Sometimes I want to see something fast and can't really keep moving until I see it.

Am I missing something here?
Click to expand...
Then just export and stop working. Walk away for a bit. Let yourself tie you up.
 
dustylense said:
Then just export and stop working. Walk away for a bit. Let yourself tie you up.
Click to expand...

What I mean is from the tests I've done, the background rendering it's doing when I export to master file now seems way slower then it used to be the way it exported before...NOT in the background. That's what I meant. :)
 
KyleProhaska said:
What I mean is from the tests I've done, the background rendering it's doing when I export to master file now seems way slower then it used to be the way it exported before...NOT in the background. That's what I meant. :)
Click to expand...
I'll do a test as I still have 10.0.5 on my 17 mbp and 10.0.6 on my MBP retina. Although my MBPR is a bit beefier I should be able to see if there is a substantial difference in export. Either way, I'll take the benefits in 10.0.6 any day.
 
Last edited:
Since I upgraded my personal computer and all the lab machines I manage to 10.0.6, it has become blazing fast, and rock solid. I was quite surprised at the change from .05 to .06. It feels beefy.

Dillon
 
dustylense said:
Every action you do is saved. It's never failed me and I went FCPX since it released. If you are going to make an alternate version of a sequence, just make a duplicate of the project.
I just felt that from the start, the editing IQ of FCPX was the future. I opened FCP7 the other day and it was the last time I ever will. I just can't see editing that way anymore. FCPX got off to a slow start, but this last update gets me where I need to be. But, Apple won't stop there. As it is, I love FCPX. Every update from this point forward will just be the finishing touches on an already incredible NLE. FCPX as I know it has a 10 year roadmap already planned out.
Click to expand...

The save wouldn't bother me if I could go back to a previous save. With Premiere you can load any of the files from the autosave folder. I had a situation recently where I was working on a multicam clip and I made a mistake I didn't notice until after I had closed the program more than once. The mistake, while minor, meant that it was actually faster to do the whole job over again because there was no way for me to go back a couple of versions. I'd like to be able to either specify how many versions I'd like to keep or have all of my steps saved in a master undo file that the program never loses.

PS - I know there's an "Old Versions" folder, but that doesn't seem to keep more than one version in there. If someone knows a way to have FCPX store multiple backup files I'd really love to know how...
 
^ This is a key point, and one of the bigger puzzles about FCPX's architecture. The exact scenario described can be counted on to occur with some regularity.
 
dustylense said:
Easy... DUPLICATE THE PROJECT.
Click to expand...

I know you can duplicate the project. That doesn't help very much when you find yourself in a bind or possibly needing to go back several versions. For instance what if I backed up the project right after I made the mistake? The reason manually duplicating and managing projects is not as good as having the program automatically do it is well... because it's not automatic. The whole point of a feature like this is to take away the task of doing it from the user who may not be good at it or be under pressure or what have you.
 
Dusty, I did a test and I don't know what was happening before but things are fast like before, perhaps even faster. Just exported a 1:25 ProresHQ CC'd sequence back out to ProresHQ in about 25 seconds.

So nevermind...it's snappy like I remember.
 
BenB said:
Yes, apps should telepathically read my mind and know what to do! Stupid apps!

But yes, there is a place for traditional Auto-Save, as we still have inside of Motion.
If you really do need it NOW, get ProVersioner.
http://www.digitalrebellion.com/proversioner/
Click to expand...

Hey we're not talking about some mind blowing new holographic time traveling space save where you go talk to your younger self about the project. As you said it's there in Motion. As I said it's there in Premiere. Hell I even think it was in the old FCP7. Not unreasonable to expect it here, too, is it?

That software looks great. Unfortunately I really believe this should be built in (as it is with the supposedly less advanced NLE alternative), so the idea of paying $60 to a third party and having it possibly break with a new version is out on principle. What FCPX does well it does extremely well and I'm glad I own it, however it's still not fully mature which means that when I'm being paid to work I generally do it in Premiere unless there is a feature FCPX has that I really need to do the job faster (like audio sync). With every new version make great strides, so I'm sure it'll get there. Maybe even with the next version at their rate...
 
KyleProhaska said:
Dusty, I did a test and I don't know what was happening before but things are fast like before, perhaps even faster. Just exported a 1:25 ProresHQ CC'd sequence back out to ProresHQ in about 25 seconds.

So nevermind...it's snappy like I remember.
Click to expand...

That and I'm seeing MASSIVE increase in render times. MASSIVE.
 
You must log in or register to reply here.
Back
Top