[Mathieu Ghekiere]

Also check in the preferences of FCPX if your playback quality is set on High Quality or Better Performance.

[Mathieu Ghekiere]

Thanks for the resonse, Edgar!

[Mathieu Ghekiere]

Hey Edgar,

Thanks for the Manual. I have some questions:

1. Will the book also be available on iBooks?

2. If so, are there advantages functionality wise at buying it as pdf vs the, I presume, ePub format on the iBooks store?

3. If Apple would update FCPX and LOGIC PRO X soon to work better together, could the customers get an upgrade if there was one of your book?

Kind regards,

[Mathieu Ghekiere]

+1 for the Pegasus R6. At that point I would buy the now announced Thunderbolt 2 Pegasus, which even will have up to an 8-bay version.

The Promise Pegasus Raids are still the fastest Thunderbolt Raids on the market and they are user friendly. They are not cheap, but they are not priced crazy expensive either, considering their performance and their market.

We use them for over a year and they have been wicked fast.

[Mathieu Ghekiere]

No this is the case:

You get a file with a certain resolution in H.264. You don’t know if it has a bitrate of 10 Mbps or 15 Mbps (you could check it, if you know the length and you have the size of the file, you know) or 20Mbps or 2, or etc. …

If you export H.264 out of FCPX it will also have a certain bitrate. Depending on that bitrate, which you can make a custom setting for in Compressor, you would also be able to make the file the same size (more or less) as the on you got.

But to answer your other question:

You will modify the file anyhow (adding subtitles, doing an effect, etc.) , so FCPX will need to render and re-compress anyhow. It uses Prores as a RENDER codec.
Because H.264 is a LONG GOP codec, it will need re-compression even if you just cut it up in different pieces.
That’s one of the reasons working with H.264 is not a great idea instead of working with Prores.
But for small pieces, I can imagine that it’s handy.

I would suppose you best export to Prores. That will happen the fastest. And then afterwards recompress to H.264. Prores can take much more generations of compression, and the engine in FCPX compresses from H.264 source to Prores pretty quickly. If you export as H.264 directly, it could maybe take a lot longer then going from H.264 and re-exporting as H.264. That’s the nature of the codec…

[Mathieu Ghekiere]

Yes, but Apple can add something very simple to make it A LOT better, I already sent them feedback about this for more then a year, but it’s still not there yet:

If you click the Expand option, you see all the audio expanded, which indeed lets you easily make J and L cuts.

BUT

once you put a new clip in that timeline, that is collapsed again.

So I already proposed to Apple how they could ‘solve’ this:

If you click the Expand All button, then EVERY CLIP gets expanded view, ALSO the ones you drop in the timeline after you clicked that button. If you click COLLAPSE again, everything collapses again.

Now you have to do a lot of re-clicking which is unnecessary.

[Mathieu Ghekiere]

So apparently it’s a 3D LUT effect that Denver Ridle is working on.

https://www.youtube.com/watch?v=5BizxYHoYnE

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Mathieu Ghekiere]

The problem with your colour correction is that you probably made a primary correction: affecting the whole image.

What you should do is make a color mask: Go to the Color Correction and look for the symbol next to the correction with the eyedropper. Click it and then go and click on your white background, selecting it.

Now, your correction will ONLY happen on that part of the image.

[Mathieu Ghekiere]

Well, we use Pipinator together with Squidborders, that gives us great results.

This plugin would maybe make the first timecode copy a bit less work, but not sure if it would be enough to justify the cost, because we often have sources with different aspect ratios.

Thanks for the heads up, I’ll give it some further look, though.

[Mathieu Ghekiere]

Hi Andy,

I didn’t know you can see it seperately in the X and Y indicators when you triangle down in the inspector and that there, it DOES update. Thanks for the tip!

That being said, mostly we just to a linear scale, so it’s an irritating bug that your Scale parameter stays at 100 percent when you shrink something.

Kind regards,

Mathieu