Apple introduces new version of Final Cut Pro X

Having finished a feature in FCP X and going through the process of trying to export my project, I have to say I hate this program more now then ever. Failed exports. Odd visual glitches showing up in the final render. Audio effects not rendering properly. Transcoding even though the export is in the same codec as the source. It's been a nightmare. And send to compressor won't render out a working blu-ray, making coaster after coaster. ARGGH!!!! FCP 7 just works. Every time. In less time.
 
Batutta said:
Having finished a feature in FCP X and going through the process of trying to export my project, I have to say I hate this program more now then ever. Failed exports. Odd visual glitches showing up in the final render. Audio effects not rendering properly. Transcoding even though the export is in the same codec as the source. It's been a nightmare. And send to compressor won't render out a working blu-ray, making coaster after coaster. ARGGH!!!! FCP 7 just works. Every time. In less time.
Click to expand...

Just so potential viewers/readers can see two different opinions...

On my end, literally zero issues in 7 years. Sure an occasional crash here and there, but nothing like you've described.

I mean...if I literally experienced any failed exports, any odd visual glitches, any audio issues, and any transcoding malfunctions at least ONCE, I would honestly share, but nothing.

It has been so flawless for me.
 
cpreston said:
Compared to what? I will send anything requiring tracking or advanced color selection to Resolve, but it doesn't seem that Premiere is any better at color correction.
Click to expand...

Exactly. Compared to Resolve, the CC tools in FCP X and Premiere are very primitive, node-based CC with power windows and much easier ability to isolate color areas in Resolve makes the Apple and Adobe CC look like kindergarten tools. It's not that they are bad, they are fine but so simplistic compared to what Resolve can do. I've been watching some instructional videos done by colorists with Resolve and it's kind of breathtaking how far you can take it if you have the skills.

The audio tools in FCP X are clunky and non-intuitive, not mention not that capable and plug-ins are not that great sounding either. Well worth your time to get proficient in Fairlight in Resolve, then you'll see what I mean. In FCP X, clicks/ambient level mismatches on a hard cut edit point, as most will have, are a PITA to smooth out, takes about 4-6 mouse clicks. That's a lame way of doing it. It works, but it is a non-elegant way of handling and at least 20-30% of hard cut edits need it. Wastes time and time is money, right? At least FCP Studio had audio fade transitions. I was a beta tester before FCP 1.0 and had been on it since it was conceived by Randy Ubilios after is was bought from Macromedia. The old FCP wasn't a great audio editor, but it worked and they slowly added good features like mixer automation over the years. And yes, was a ProTools user for a few decades as well. In the old days, audio tools in video editing programs didn't matter because it all got sent to a sound mixer via OMF. These days, how many projects are you doing that get sent to an audio post team? VERY few for me, although both of my current documentaries will, even if I have to pay for it out of my own pocket. So if we all have to do our own sound mixing because clients are too cheap to pay for audio post anymore, I at least want capable tools that make it all easy.
 
Last edited:
I wasted about a week debugging my whole sequence. Things I've learned -- don't render in the sequence, and then export, as it can cause odd glitches. Delete all your renders and then export. Transcode all your audio to 48khz before importing. If it's 44khz, FCP X will upsample it on the fly, but this can cause audio filters to render improperly, causing audio glitches. In compressor, selecting render at 100 percent of sequence causes audio to go out of sync. Choose the sequence running time option instead. I really wish FCP X had a Quicktime Movie version like FCP7, where, if the export is in the same codec, and it is already rendered, or there are no effects to render, it will just copy out the sequence instead of transcoding. I can export in minutes what takes a few hours in FCP X, because it transcodes always no matter what. Another annoying thing. FCP X always uses up all available ram. With my 90 minute 4k project, it maxes out my 32gb after a couple hours and starts accessing VRAM, which slows down the system. They need a RAM management preference so you can limit and adjust how much the program uses.
 
NorBro said:
Maybe take a look at this and see if it helps? (there are other articles/videos out there too):

https://support.apple.com/kb/PH16032?locale=en_US

https://support.apple.com/kb/PH16056?locale=en_US&viewlocale=en_US

https://support.apple.com/kb/PH16055?locale=en_US&viewlocale=en_US
Click to expand...

Thanks. Sounds like kind of a weird workaround to what I meant. In the old way, you could hop between Motion and FCP, and as you made changes in Motion they'd update in the FCP timeilne.
 
Yea, updating in Motion and seeing the changes in FCPX sounds ideal. One workaround (quickly off the top of my head before looking into it more) is to export the file again (after you've made the changes in Motion) and just overwrite the file you currently have that FCPX is 'linking' to.

So if you work on a title in Motion (for example) and export it to the desktop and then bring that into FCPX and put it in your timeline, just replace the file on the desktop (or wherever) with the new file (with the changes) and you'll see the changes update inside FCPX.

You won't have to physically import and put the new file in the timeline again (as long as it's the same name and it has been overwritten if that makes sense).
 
Yeah. I have not tried that yet but legacy FCP didn't like when I tried things like that and would give me "illegal (something or other)" messages until I deleted the file I was trying to overwrite.
 
The motion publish parameters tool can be extremely useful for titles. Create a title effect for a project and then use it throughout the project without having to go back into Motion.

You can even create transitions like an audio only transition for hard cuts.

You can overwrite Motion files and have it update in FCPX if you use the same name and don't consolidate media inside the project.

I have had a few render issues with FCPX over the years. I've noticed a problem with noise reduction using Izotope where it will cut off audio early before the audio clip ends in the timeline. I've also had render issues that are only solved by restarting the program.
 
Last edited:
cpreston said:
The motion publish parameters tool can be extremely useful for titles. Create a title effect for a project and then use it throughout the project without having to go back into Motion.

You can even create transitions like an audio only transition for hard cuts.

You can overwrite Motion files and have it update in FCPX if you use the same name and don't consolidate media inside the project.

I have had a few render issues with FCPX over the years. I've noticed a problem with noise reduction using Izotope where it will cut off audio early before the audio clip ends in the timeline. I've also had render issues that are only solved by restarting the program.
Click to expand...

Thats good to know, I have Izotope RX5, but haven't tried it in FCP X yet. I know that Neat Video has worked pretty well within FCP X for me.
 
I have Logic and FCPX has always been able to see all my logic plugins (compressor, EQ, etc.). Granted, they're not as fleshed out as they are in logic with the graphics and all, but I can still use those audio effects.
 
Josh Bass said:
I have Logic and FCPX has always been able to see all my logic plugins (compressor, EQ, etc.). Granted, they're not as fleshed out as they are in logic with the graphics and all, but I can still use those audio effects.
Click to expand...

My understanding is that FCPX has all of the Logic plugins built in along with some legacy Final Cut and Apple plugins. I found the compressor and EQ plugins much better in FCPX than in FCP7. I have noticed that the plugins and the interfaces seem to change on some of the FCPX updates along with Logic, though. Sometimes the FCPX updates leave me struggling to relearn my normal effects and commands which can be a bit annoying. Even so, it is a far less frustrating program to use now than it was when it was released in 2011.
 
puredrifting said:
Audio handling, color correction and motion graphics in FCP X are good but compared to Resolve? No comparison.
Click to expand...

I haven't looked at Resolve that closely and I have no doubt that is true. But where I think FCP X is peerless including with Resolve is organization and shot selection. Filmstrip view and skimming are amazing for this. Keywording to me is just superior than bin arrangement. Shot selection is what I spend maybe 60-70% of my time doing in an edit. Editing in FCP X and finishing in Resolve may be the best of both worlds. Though for me, I don't need that amount of precision in audio or color correction. I do wish Role mixing was better implemented in FCP X though.

One way FCP X is superior to Resolve in motion graphics though is Motion template development. It is amazingly powerful in Motion/FCP X. I make Motion graphics that can be continually reused. For example, I made a Newspaper template where you can make a newspaper mockup with a masthead by just pasting the article text in the Motion template. It used to take me about 20-30 minutes to do this before. Now it's like 2 minutes. When you're on a deadline that time savings makes a huge difference.
 
Last edited:
You must log in or register to reply here.
Back
Top