Getting Frustrated help

Hi i have been using fcpx for about 4 months on a Imac getting to know this program and i love it i wanted to get a faster machine and i got the new macbook pro retina 13" the one that came with 256 ssd and 8gb of ram, this machine is super fast i like this one so much, i began to work on fcpx on this macbook pro and everything was fine until the export time came, this is a 1hour 27 minutes project that contens go pro videos and canon vixia videos and photos from a nikon d5000, the export to apple devices 1080p was taking more than 7 hours when i check i found in monitor a pro transcoder toll error in red fonts and is doing the same for every project i try to export even short ones, i try to export to master file and it work but it took 10 hours and finish been 100gb i purchase compressor to see if exporting using compressor is better but is taking so many hours too, i don't know if theres something wrong with my new macbook pro, i'm not new to mac but yes i'm new to fcpx and compressor please help me. my mac specs
2.4GHz dual-core Intel Core i5
Turbo Boost up to 2.9GHz
8GB 1600MHz memory
256GB PCIe-based flash storage1
Intel Iris Graphics
i'm using a 1tera g-drive mini 7200rpm

What are your project properties? Did you let FCPX determine them from the first clip? If so, what was the first clip?

Go Pro footage comes in a variety of flavors. it's probably a good idea to optimize those clips. The Canon could be anything (what is the format?) . And stills – particularly large ones – really challenge all but the beefiest of machines.

Guessing that you brought your movie into Compressor with Send to Compressor…correct or not? Not sure what the unresponsive message is about. But I'm surprised it's faster than sharing from FCPX.

Russ

Russ Haskell wrote: What are your project properties? Did you let FCPX determine them from the first clip? If so, what was the first clip?

Go Pro footage comes in a variety of flavors. it's probably a good idea to optimize those clips. The Canon could be anything (what is the format?) . And stills – particularly large ones – really challenge all but the beefiest of machines.

Guessing that you brought your movie into Compressor with Send to Compressor…correct or not? Not sure what the unresponsive message is about. But I'm surprised it's faster than sharing from FCPX.

Russ

Thanks Russ for the help, first when i start a project i chose 1080p hd 1920x1080 29.97p those are the settings i always use this movies i made are not for publishing on the net are for personal view, when i chose to import a movie or a photo i always chose to create proxy and optimize. i brougth the master file to compresor to create a video to view on apple devices and began to grow on time after 5 hours says that need to finish 13 hours and the number was increasing, I don't know if there is something i'm doing wrong please let me know what i can try.

So I guess he Optimize theory doesn't hold up in this case…too easy.

How long did the master file take to export?

The good news is that Compressor's History progress bar is notoriously inaccurate. It's common to see the elapsed time increasing and then when it starts to decrease to do so faster than in real time. So if you let it complete, you may be pleasantly surprised.

It's a fact that an H.264 encoding job in Compressor is lethargic at best. And it is a CPU-ontensive process, so your SSD isn't going to be much help. Nonetheless, I would think something like 5 to 6 hours on your machine for an 1.5 hour movie might be reasonable; but anything approaching 10 hours would be suspect.

One of Mavericks' claim to fame is its memory management. Nonetheless, it wouldn't hurt to keep Activity Monitor open and see whether there are indications of your MBP memory being depleted.

Russ

Russ Haskell wrote: So I guess he Optimize theory doesn't hold up in this case…too easy.

How long did the master file take to export?

The good news is that Compressor's History progress bar is notoriously inaccurate. It's common to see the elapsed time increasing and then when it starts to decrease to do so faster than in real time. So if you let it complete, you may be pleasantly surprised.

It's a fact that an H.264 encoding job in Compressor is lethargic at best. And it is a CPU-ontensive process, so your SSD isn't going to be much help. Nonetheless, I would think something like 5 to 6 hours on your machine for an 1.5 hour movie might be reasonable; but anything approaching 10 hours would be suspect.

One of Mavericks' claim to fame is its memory management. Nonetheless, it wouldn't hurt to keep Activity Monitor open and see whether there are indications of your MBP memory being depleted.

Russ

Again thanks for your help, what settings in compressor do you recommend me to try that let me lower those 100gb of video and could be a little faster without lowering the quality of the final product?

In general I've found the stock ATV settings to be very good. The 3rd generation specs have a bit rate of 10 Mb per second, which would reduce your 100GB file down to about 110 MB. And it should look quite nice.

One thing that would cut encoding time by half would be to use single pass encoding instead of multi pass. You could test a short section, using both single and multi-pass by marking a short but representative section with in and out points in the Preview window. After the files have been output look at them in Quick Time to see whether the difference in quality is detectable – and if it is, whether it is acceptable.

Russ

Did you turn off App Nap for FCP X?

lichinho wrote: Did you turn off App Nap for FCP X?

Sorry lichinho don't know what is app nap could you explain thanks

yesterday i try to convert my 100gb master file to apple devices apple tv 3d generation to stock settings on compressor and let it finish and it took 16 hours to complete and 6.4gb is that time normal for a project of that size?

App Nap is a feature of Mavericks that allows the system to put background applications in a low power state ("nap"). It is up to the application to request not to nap.
It is very likely that this is causing the very slow export (many people have reported this).

The current version (10.0.9) of FCP X is pre-Mavericks, so you need to tell the system not to let FCP X nap.
In the Finder, open the Applications folder. Click once to select but do not open FCP X. Hit Cmd-I to open the "Get Info" window. Check the box that says "Prevent App Nap". All should be back to normal.

lichinho wrote: App Nap is a feature of Mavericks that allows the system to put background applications in a low power state ("nap"). It is up to the application to request not to nap.
It is very likely that this is causing the very slow export (many people have reported this).

The current version (10.0.9) of FCP X is pre-Mavericks, so you need to tell the system not to let FCP X nap.
In the Finder, open the Applications folder. Click once to select but do not open FCP X. Hit Cmd-I to open the "Get Info" window. Check the box that says "Prevent App Nap". All should be back to normal.

Ok find it will test it now should i do this for compressor too?

something strange is that my fcpx is 10.0.8 and i look in too updates and don't find any updates is there a manual way to update fcpx? thanks again

You need to be logged in the App Store with the same Apple ID that was used to purchase the application.
Then the update should appear.

In case it somehow doesn't: look in the purchases tab. Do you see it there? It should say "installed".
If it is there, then you may redownload it.
Quit the App Store application
Temporarily move FCP X away from your Applications folder (store somewhere else, just in case this fails and you can move it back); download FCP X from the purchases area of the App Store (once the application is not "seen" on your mac, the button "Install" should become available).