illegal luma levels on render

[Chris Borjis]

I noticed this before as well.

how low are you taking your white levels down?

usually I take mine down to at least 95%. Rendered, they stay below 100.

[Jeremy Garchow]

Make sure your cc and broadcast safe filters are at the bottom of the filter stack so they get rendered last.

Jeremy

[Gregory Butner]

Are you using any composite modes like multiply? Sometimes the broadcast safe filter doesn’t work when there is more than one layer being combined. If this is the case then export that particular section that is going out of luma safe as a quicktime and then apply the broadcast safe filter to the rendered video.

[Alan Fisher]

I’m afraid we’re not doing any compositing, just cuts and dissolves, and we’re definitely doing the color correction and/or broadcast safe applying as the last filters…it just doesn’t show the adjusted levels after a render, as if it was never applied. Frustrating!

Searching around I’ve seen some references to this being a bug, maybe particularly with 10 bit footage, but so far we haven’t gotten any of the workarounds (nesting and applying the filter, or exporting and re-importing) to help. Would Color work where Final Cut is failing us? We’ll try bringing the whites down to 95 until we can convince it to work right….

I appreciate the ideas,
Alan

[Michael Gissing]

It has been reported here many times that broadcast safe is not safe after render. There are a few way to fix this.

I used to use RGB limiter rather than broadcast safe. I now use a legaliser that was part of The Grading Sweet plugins. Download the demo and the legaliser is free

https://thefilmbakery.com/store/index.php?main_page=index&cPath=1&zenid=b7d8t057du9rlrok8qphqd9m05

[Jeremy Garchow]

And if you know Color, by all means use it. It has superior quality than built
in fcp plugs.

[Mark Raudonis]

After dealing with this “10 per cent difference” upon rendering, we bought hardware legalizers. Nothing like a hardware “clamp” to guarantee you’ll be legal.

At a certain point we stopped trying to trouble shoot, acknowledged that it’s a problem, and moved on to the solution (hardward legalizers). Life’s too short!

Mark

[Rafael Amador]

I really don’t understand how can fails a filter which only mission is to clamp Y’ when its reach a certain value.
We have to notice that where in the Broadcast Safe filter says “Chroma”, It should say “Composite”.
We need to keep legal the Luma (>100%) and the composite signal (>133% and depending on the system specs).

We have to understand that we need legal four different things:
– Luma
– Chroma Amplitude
– Composite signal (Luma + Chroma)
– RGB Gamut

The Brodcast safe filter can control Luma, Composite and RGB, but have no way to control Chroma.

While the Luma and the Chroma may be legal, the resulting Composite signal can be illegal.
Or while our Composite signal is legal, we may still have RGB values out of specs.

Have been pointed here the RGB Limiter. The RGB limit filter is of not use to control Luma: a 100% Red (256) is is absolutely illegal, while the value of Y’ is perfectly legal: 30%

In FC we can monitor Luma, Composite (limited) and RGB, but no way to monitor Chroma.
In Colors we miss the possibility to monitor the Composite signal.
Both applications are limited on monitoring, so you can not get a full picture.

Anyway, I wonder if some people are using properly their WFMs. Are they monitoring proper Luma or instead are monitoring the Composite signal.
Rafael

http://www.nagavideo.com

[Steve Macmillan]

I just started my own post on this.

It has been my recent experience, that rendering breaks the Broadcast Safe filter with ProResHQ. If you export a clip as 10bit uncompressed, and then drag it back into the ProResHQ timeline, add the Broadcast Safe filter and render, it works as expected.

STeve

[Neil Ryan]

Hi Mark,
What hardware legaliser did you get or do you recommend?

Neil.