Color banding & ghosting on text

drrohle wrote on 11/22/2011, 1:45 PM

Just upgraded to Vegas Pro 11 and am still getting this color shading/ghosting effect (as in Vs. 10e 64bit) on all colored text, usually near the bottom of the characters (Except Black, White or primary colors like Red, Green, Blue). It happens when I render the clip using any compression like mpeg-2, avi, Quicktime etc. If I render it uncompressed it looks great. Doesn't matter if it has a background or not, matches the project settings, clip settings or not. This also happens using the Prototype Titler too. All in standard def.

I don't have this problem using the 32 bit version, just the 64 bit.

I ran this problem through the support center and after waiting 3 weeks for a reply (unacceptable), Sony finally said it was fixed in the "e" release (it wasn't). Now I've upgraded to VP-11 and have the exact same problem. Except now it takes everything 20% longer to render than in Vs. 10.

Can anyone help fix the color banding/ghosting on generated text? I have a weekly television program to produce and can't afford the delays & problems. Also any "tuning" hints on quicker renders would be appreciated too.

Running HP machine with i7-970 6 core processor, 12GB RAM, GEForce GT440 vid. card. Latest drivers.

Back to post

Comments

musicvid10 wrote on 11/23/2011, 10:00 PM

"here is another example with the text color as 234-129-0"

Sorry to seem intrusive, but your colors are still not in gamut as defined by BT.709 (aka REC 709). The last number (blue) needs to be at least 16, not 0.
And are the project and render properties exactly the same between versions as pointed out in my previous post? That is the first step toward being "pinned down."

In the world of Non Linear Editing, we need to be completely precise in our actions, good intentions notwithstanding. Hope that observation is well-taken.

farss wrote on 11/24/2011, 12:52 AM

Colors can be out of gamut and still within legal levels and that is a trap.
If you use out of gamut colors Vegas will let you know via a little yellow triangle when you choose the colors. If the triangle has a "N" in it you are outside the NTSC gamut and a "P" in it you're put of the NTSC gamut, nothing means you're outside of both. Here's a thing though, I have no idea what the gamut range is for computer displays.
That said I don't think out of gamut colors should cause the problems showing up there, the usual result of using out of gamut colors is they don't come out correctly and something way worse is going on in that video sample.

There's other problems there too, the background doesn't look all that good either with obvious aliasing on the curved edges.

Bob.

drrohle wrote on 11/24/2011, 10:07 AM

You're not intrusive musicvid, I really appreciate all help given. I set all the levels within 16-235 and don't really see any change. lots of cyan remnants and red shading at the bottoms. BTW the settings are identical between 32/64 bit vs'.

[IMG=http://i1129.photobucket.com/albums/m509/drrohle/235-165-16Orange64Bittest.jpg]OrangeTest235-165-16_64Bit[/IMG]

I never really had any problem like this in Vs. 6 which I used for years and since Fox Studio's never balks or seems to care much about these settings it's never been an issue. Their eq. seems to correct any out of tolerance colors etc. I just send them the weekly television show & life's good.

Just wish I could fix the way the cruddy text looks.

drrohle wrote on 1/24/2012, 2:39 PM

I knew this wasn't a problem with NewBlue Titler but I ran it by their support team anyway since I can't get a timely response from SCS. They (NewBlue) replied withing the hour! Here is what they recomended:

Even though my footage is shot in Interlaced mode, they recomended I try rendering in Progressive. This made the text look MUCH better even though the video results are not quite as smooth as before the text is now acceptable.

Anyone care to post their expereinces?