Colour flickering when adding any titles / generators / images over timeline

[Jagster Rana]

Hi Joe

Firstly, thanks v much … i really appreciate your response. there is nothing on the internet .. SO ..

i tried what you said .. AND YES… thats the solution IT worked.. i deleted render files at project and event level.
as you said earlier this issue seems to ” infect” all files in the project .. so thats logical .. delete render files and let fcpx rebuild files and setting manually to REC 709 does the trick.

1 last question :

so next time shld i import the files> pause background rendering > manually set all clips to REC 709 then restart the rendering ? is that work flow correct

Many Thanks again and Happy days … back to enjoying life ????

cheers Joe !

JR

[Joe Marler]

[Jagster rana] “so next time shld i import the files> pause background rendering > manually set all clips to REC 709 then restart the rendering ? is that work flow correct “

I’m glad the workaround was successful. I never use background rendering so I didn’t think about that. But in theory the flickering problem could be injected into any rendered file, so your procedure probably makes sense. Likewise for stopping auto generation of proxies on import until all the material has been manually re-flagged REC 709.

This problem is so serious I’m actually hoping Apple will fix it very soon so we don’t have to deal with workarounds. The workarounds aren’t that bad, but the problem is lots of material could be infected with these infrequent, spurious brightness fluctuations which are encoded to output files. The infrequent, fluctuating nature means it’s possible some material may have slipped by QC and been delivered or broadcast with these defects.

[Sara Blom]

Finding these posts was a huge relief even though there doesn’t seem te be a real solution for it.

I’m wondering though if anybody knows if the issue is now recognised by Apple in any way?

I’m working on a really big project and the idea of not being able to fix it is terrible (unless I spend days replacing the bits where the colour is flickering).

Thanks

[Jagster Rana]

Hi Sara

I have also send an error report to Apple .. are they doing anything about it ? doesnt look like it at th moment !

In the mean time you seen the solution bit of a pain but thankfully fairly easy. Switch to manual Rec 709 under color space override under settings on the “i” tab ( right side of screen when clicking a clip )

cheers

JR

[Sara Blom]

Thanks JR!

The problem is however that I can’t seem to make any change in that tab. I can change things like format but
the standard-rec709 tab remains non-active.

Could this be because it is a multicam clip? Do you know if there is a relatively easy way to select the right angle from a multicam clip and then ‘dismantle’ the multicam (leaving just the chosen angle clip)?

Thanks again.

I also intent to contact Apple (though not expecting much there :((

[Joe Marler]

[Sara Blom] “The problem is however that I can’t seem to make any change in that tab. I can change things like format but the standard-rec709 tab remains non-active. Could this be because it is a multicam clip? “

I think you can just select all clips in the Event Browser (not just the parent clips for your multicams) and re-flag them Rec 709. In my experience the problem is elusive and unpredictable so it’s better to re-flag everything, else it could happen again, maybe in a subtle way that eludes QC checks until your product is delivered.

I’d suggest first trying that on a small scale, such as only the parent clips of one multicam that reliably exhibits the problem. If that works, do them all, but make a backup of your library beforehand. If you are intentionally using some non-709 material, I’m not sure how to selectively re-flag only the 709 clips, or if the problem even happens on non-709 clips.

If that doesn’t solve it, you may need to delete and regenerate all render files and maybe proxies, if you’re using proxies. It’s not just a playback issue. Once the problem happens it becomes encoded in generated or rendered files.

[Sara Blom]

The problem is that I can’t reflag the clip because this function seems in-actieve when I open the tab.
This is the case when I click on the clip in the event browser as when I click on a multiclip in the timeline.
I tried uploading a file below where you can see it.

schermafbeelding2018-08-24om16.49.16.png

[Jeremy Garchow]

[Sara Blom] “The problem is that I can’t reflag the clip because this function seems in-actieve when I open the tab.”

This needs to be done in the inspector (command-4). I would change the clips inside the Multicam (that means open the angle editor and do it there, as well as the mutliclip itself, if that it possible). You have to do this on the individual clips.

See here:

[Joe Marler]

[Jeremy Garchow] “This needs to be done in the inspector (command-4). I would change the clips inside the Multicam (that means open the angle editor and do it there, as well as the mutliclip itself, if that it possible).”

Yes, you do it in the Inspector as you showed. You can do all the clips in the entire event in a single step. Just select them all then change the color space override in Inspector. They all get changed.

I’m not sure you need to open the Multicam and do those. When I re-flagged to Rec 709 the parent clips in the Event Browser for an existing Multicam clip, then looked inside the MC clip, those had inherited the change.

You can’t change the color space override of the MC clip itself.

As I said before, I’d suggest making a backup of the library before doing global changes like this. It should cause no problems but it’s easy to make a mistake or maybe later find you had Rec 601 or 2020 clips you didn’t want changed.

[Sara Blom]

Re-flagging the individual clips to rec709 worked! What a great relief.

Thanks everyone for the advice on how to get there.

Sara