[Russel Xander]

most probably Larry Jordan missed my tip… 🙂

[Russel Xander]

Just for a reference in case I forget by the time:

seems like it’s not only the Animation codec set as sequence codec that can help resolve this issue,
but it’s possible with ProRes as sequence codec as well.

Here are the necessary settings to be set that are affecting processing of white:

– Sequence Settings/Render all YUV material with high-precision YUV
– and here also set Process Maximum White as ‘Super White’
– Motion Filtering quality ‘Best’
– User Preferences/Editing… Imported Still/RGB Video Gamme/Gamma Level: ‘Source’

and the most important part:
– do not use a FCP generated solid, create a 255/255/255 white picture and save it as PNG with Photoshop!!!

[Russel Xander]

Your are both right, still I think it’s such a simple thing it should be possible to be done in FCP,
instead of wasting unnecessary time in a compositing app.

After experiencing with different sequence codecs this morning, I found out that what’s causing the coloration is a BUG that happens with certain sequence codecs> any Apple ProRres XXX, same thing with Intermediate codec, but does’t happen if I use the Animation codec.

Rendering the output with Animation codec + creating an mp4 with compressor +uploading to Youtube gives the expected result.

Anyway it was a good lesson not to use FCP for any kind of compositing if the background is a clear white. Thank you for convincing me about that.

[Russel Xander]

It gets attributed to FCP so that the visual BUG that appears on youtube version of the video clearly shows that there are 2 track overlapping. And the overlap/coloration is exactly there as in FCP (but visually not visible).

[Russel Xander]

both whites are the same even by the eyedropper. the problem is that it should work with 2 tracks only. white solid on the bottom and the cropped clip on track 2.

now, in some parts of the video the clip is rotated, zoomed constantly, and I would end up with 4 extra tracks ( to add the missing white on each side), and that slows down everything – 6 tracks altogether.
And I would have to keyframe/track the movement of each of those 4 tracks to follow the content of the clip.

If I use color key to mask my model then a very light (hardly visible, but I do see it) aura appears around my model and in this case the white of the solid on track 1 is perfect but the aura around my model gets a slightly blueish color after being uploaded to youtube.

As I mentioned before, this color shift is not visible in FCP, nor in the output render, or in the mp4 made by compressor, but It does appear after youtube upload. So it’s definitely a rendering problem of FCP.

[Russel Xander]

I’ve tried that earlier and it seems to solve the problem, however it takes much more time to render.

I can’t accept the fact that a white solid (or a simple white PNG made with Photoshop) as an underlaying background is treated/rendered differently and gets slightly colored regardless that it’s values are the same as the white of the clip next to it (255/255/255 RGB).

It’s really a basic thing and FCP seems unable to handle it correctly or there’s a trick I’m not aware of 🙂

[Russel Xander]

see my fix for this bug here> https://forums.creativecow.net/readpost/8/1138433

[Russel Xander]

if you are exporting your FCP footage with Compressor, then simply turn off the ‘Add clean aperture information’ in Encoder tab of compressor settings. That helped in my case, now QuickTime X plays the 1280×720 movie without overscan / cropping.