FCPX imports and exports low quality

[Nick Toth]

The issue is not with FCP X. More info is needed before anyone can help you. What format is going in, what are your project settings, what format are you exporting to? You don’t have to use proxy or optimized footage. Those are preference settings.

[Vesko Urukov]

Thank you for your answer.

I’m importing 1920 x 1080, Apple ProRes 422 (HQ)
Color profile: HD (1-1-1)

[Vesko Urukov]

Thank you for your answer.

I’m importing 1920 x 1080 | 25p Apple ProRes 422 (HQ), Timecode
Color profile: HD (1-1-1)

My project settings are:
1080p HD 1920 x 1080 | 25p

[Nick Toth]

Pro Res is native to FCP X. What comes out should not look any different than what goes in. What are your project settings?

[Nick Toth]

How are you determining the quality of the video? What are you viewing it on? From what you have said so far there should be no problem. Some screenshots might be helpful.

[Vesko Urukov]

screenshot2016-05-06at7.40.53pm.png

[Nick Toth]

Is the viewer in FCP X set to Better Quality or Better Performance? You say your exports are low quality. What format are you exporting too? I see the difference. Where is the screen grab coming from?

[Bill Davis]

Version.
I suspect that lke many of us coming to X from other NLE approaches, you don’t yet understand the nature of how The program actually functions.
Initial import does nothing but create pointers to what will become calculated “pools” of footage. To let you get to work instantly, X creates instant “OK for now” low Rez reference files that might not be high quality depending on the shooting format and codec you used. This is by design. Why? Because often getting started making your editing decisions FAST might be important. So you can edit in X nearly instantly because while the background file processing to render out the footage in high quality, the program can capture all your editing decisions as metadata in a separate file. As the high quality transcoding engine inside X imports, you elect what mezannine codecs like Optimized or Proxy files to have X place in separate footage pool buckets. Only when all this transcoding is complete, can you switch the pointers between the footage pools and stream video out in any resolution you need from original to proxy with the flip of a switch.
If you stop at any stage, select a range of your storyline, and do a test output, you can see the full quality you are working with. Also, parking your play head on a frame, even if the underlying footage is unrendered – will calculate a still monitor image at full quality.
X is not what you are used to. Until you learn its nature, just be patient and the magic of its approach will reveal itself to you over time.

New signature under construction and coming soon. Please stand by…

[Vesko Urukov]

The screen capture on the left is from the original file played in the finder and the image on the right is exported as source from FCPX

[Vesko Urukov]

OK, Thank you! I think I now understand they the footage looks low res during the editing process, but why does the exported file (exported as source) look low res?