[Jeremy Salo]

I am editing footage from Sony EX1 cameras in Premiere Pro CS5, and using the YC Waveform scope. The levels look broadcast safe while previewing, but when I render the work area, they exceed past 100 and below 0.

Any idea why?

I also posted on the Adobe forums with more information.
https://forums.adobe.com/message/4107830

[Jeremy Salo]

I’m exporting to DVCAM.

They haven’t tested the final tape at a post house yet so don’t blame to deck. Once I render, before any export of any kind the levels expand on the Premiere waveform monitor.

The black was less of a concern. The main concern is the luminance being over 100.

Is there a plug-in or way to change to a different rendering codec in Premiere that will actual render with the setting you adjust it to?

[Jeremy Salo]

Sure:

I’m just using the built in Waveform Monitor in Premiere. I’m looking at the actual representation in the middle of the scope as well as the green bar graphic representation on the right side of the scope.

Ah yes, the black levels also pop/expand downwards after the render. It’s hard to judge the mid levels but they seem to be the same. The black jumps from 7.5 to 0 after the render.

I do not own an external waveform monitor. For this episode I had to send it out to a post house to run it though a broadcast legalizer. I really need get Premiere to render legally, possibly by having it render with a different codec.

[Jeremy Salo]

Yes but how do I get Premiere to actually render with the levels it’s effects are set to?

Regardless of how it previews on any of the monitors I have set-up, the video limiter effect is set to a numeric value of 100 IRE maximum. That and all the other filters I tried to lower the luminance values numerically in preview mode raise past those settings when rendered. They still bleed past 100 IRE, some up to 110 IRE.

This problem isn’t about how it looks on my screens or a graphics problem but how the default NTSC Premiere render is boosting certain luma values past broadcast legal specs of 100 IRE.

[Jeremy Salo]

I am rendering to the default; DV NTSC, Millions of colors

[Jeremy Salo]

So no one has any input?

[Jeremy Salo]

Cool, that worked with filters, but what I really wanted to do in this case was an image adjustment called “replace color”. That is grayed out when I apply a smart filter. Is there any way to use the images adjustments, such as replace color on a whole video clip?

[Jeremy Salo]

I figured the x64 had something to do with it. I was told by Adobe that CS3 also isn’t supported by Windows x64.

I bought extra RAM primarily for After Effects, and use that a lot, so I can’t go back to XP 32.

I’ll be upgrading to CS3 production suite within the next few days/weeks, and hope for the best. They did however tell my that they integrated Nucleo (a plug-in that will use whatever processing power you have or assign) into After Effects CS3, so I’m excited to see how that performs.