problem in making titles

ARK wrote on 5/6/2003, 11:46 AM
I'm using V4 for my NLE of avi files. I use ProCoder by Canopus for encoding from avi to mpg-2. After editing avi file and adding title to the beginning of clip, I save render as avi files and use stand-alone procoder to encode my clip. The problem that I see is there is a very noticeable staircase or jagged line on the edge of every font if it is Italic or slanted. I'm not sure if this is caused by V4 creating avi files or ProCoder encoder. I have tried to do the same thing with P6.5 which uses MainConcept encoder and did not see the same jagged edge on slanted fonts.

Please help if anybody has any idea.

Thanks

Comments

Chienworks wrote on 5/6/2003, 12:41 PM
Try some experiments for comparison. Look at the .avi file created by Vegas; does it have the jaggies? If not, then procoder is probably adding them. Try rendering to MPEG right from Vegas' timeline; how does that file look? That way you'll be using the Main Concept encoder and won't even have to create the .avi file first.
mikkie wrote on 5/6/2003, 2:38 PM
Also might try playing with the encoder settings, if you haven't already.
farss wrote on 5/6/2003, 6:18 PM
I've had much the same problem using the Mainconcept encoder that SoFo supplies but one thing to check first. Are you using VV 4.0b?

First release rndered most fonts really badly, when that went through the MPG encoders (any of them) they really fell apart. Check carefully how you text looks before encoding, any staircasing is going to get worse after encoding.
ARK wrote on 5/6/2003, 8:02 PM
Hi Chienworks,
Thanks for reply. Noop. The avi file looks fine. I was wrong and I did see the same artifact with Premiere 6.5 and MainConcept encoder and V4 with built-in MainConcept encoder. As a matter of the fact I tried the same avi file with CCE 2.67 and result was the same and avi file looks fine with no jagged edge. In all cases I'm setting to multi pass VBR, 8000kbs and HighQ.

One more thing I tried, using MyDVD, which has build-in encoder, I'm not sure what it is and notice the final result is not as bad as others.

ARK,

ARK wrote on 5/6/2003, 8:09 PM
Hi mikkie,

The only setting I did for all encoders CCE, Procoder and MainConcept was, multi pass VBR, 8000kbs and HighQ. Are there any other setting that I am missing and might effects this jagged edge? I'm too new to this stuff. Is this some kind of pixelization error that I am getting? if so why the rest of the clip is fine and it's just the generated text has the problem.

Thansk
ARK
ARK wrote on 5/6/2003, 8:18 PM
Hi Frass,

Thanks for reply, I am using the latest V4.0b with build in Mainconcept encoder which has the same problem with Generated slanted text. The same text in preview windows looks great with no artifact, some how encoding does that to text. I was thinking to take a shot of slanted edge with my camcorder like the edge of the table and see if encoder makes the edge staircase or just this behavior shows on generated text.

Thanks
ARK
HPV wrote on 5/6/2003, 11:20 PM
Try using the waveform monitor and see if your levels are hot - over 100% IRE levels. Broadcast fx at event/track/or master stage will clamp/limit the "hot text". To make the broadcast filter fx work, click on the one and only keyframe at the bottom. Select one one of the presets like "Lenient - 7.5 Setup".
Or better, you can turn down your levels in the CG media to fall between
16-235 RGB. Gaussian or Quick blur fx/filtering can help tons also on those tough angles your avi DV to MPEG II setup is grinding on. You could go avi uncompressed to MPEG II. Lot's more HD space and slower output though.
I use fx plugged in at the track level for my CG tracks. Nice and clean use.
All though cut and paste of event attibutes in V4 is great for event level fx use. BTW, If you want to tweak your mind (and find tons of looks), load up the film effect on some text. Crazy stuff.

Craig H.
farss wrote on 5/7/2003, 6:47 AM
Hot levels might have something to do with the problem. My problem improved when I backed off from 100% red but it was still pretty crook. I also noticed it wasn't just the edges that were going bad, there was pixels dropping out inside the letters.

I went to just plain white text and no problem. I might do a bit more work on this issue when I have the time, I'll try running the AVI through TMPEGEnc and see how it turns out
mikkie wrote on 5/7/2003, 12:20 PM
"The only setting I did for all encoders CCE, Procoder and MainConcept was, multi pass VBR, 8000kbs and HighQ. Are there any other setting that I am missing and might effects this jagged edge? I'm too new to this stuff. Is this some kind of pixelization error that I am getting? if so why the rest of the clip is fine and it's just the generated text has the problem."

I've not used procoder, and couldn't find anything useful on their site, so alas I'm dealing with generalities - please forgive...

MPEG 2 compression involves a matrix that it (the encoder) uses to divide up the original frame you feed it, and based on this matrix it decides what data to hold onto. It also involves looking ahead into the video to see how much motion is there, how the amount of motion changes and so on (often given as a quality setting to my knowledge, when the actual look ahead is not referenced). Depending on the software, there can be quite a few other options, to fine tune the look ahead and the matrices used etc.

Stuff gets much like a black art, so a lot of these controls aren't always visible or adjustable by the user - VV4b doesn't give you an option that I could see for changing the matrix as an example.

I'm guessing that if VV4b creates avi files that when encoded by procoder show the problem, then perhaps VV4b may not be anti-alliasing &/or feathering the text as much. In theory the text should be feathered into a shadow that's also feathered - for TV display anyway. While this might not be apparent viewing the video, at the individual pixel level procoder might be having trouble, pixelating on the edges, and setting it to use a different matrix or algo for the matrix might eliminate the problem by forcing procoder to look at and treat the edges differently.

If procoder can't be adjusted to handle it well, then I'd look at ways to dirty up the title track in VV4b, probably by adding noise as this doesn't have the same visual effect of softening the entire picture as blur does. Another advantage is that with mpeg 1/2 and winmedia encoders the noise registers as movement that the encoder will try and keep in the compressed video - pixilation often comes from the encoder tossing out in this case part of the edge data it feels are more static.

I'm sure there are better methods, I'm really just thinking aloud here, but if something like adding the noise FX in VV4b or through V/Dub filters didn't do it: I'd consider rendering the title clip to avi with the background color the same as the shadow color used. For compression I'd use something like picvideo, but with quality set to half way, or maybe 3/4 to add the noise. Reimporting the title clip, setting the background to chroma key out, might just be noisy enough to force the mpeg 2 encoder to keep everything and give a nice blended edge.
ARK wrote on 5/8/2003, 11:51 AM
Hi All,
First, I would like to thank everybody for their comments/suggestion and helps.

I found some interesting discovery last night. From the reply by "farss", I did change my text color from bright red to different one like pure Blue, Green and Yellow and made some differences.

I believe my problem is VV4 build-in codec. From "HPV" response when I select Uncompress video, which is one the choices under "File" and "Render AS" in V4 then slanted red font looks much better.

Also, when I use pure White color in slanted text the edges are perfect. Pure Red and Blue are the worst case. Green color has a little symptom. Thus, Procoder encoder has nothing to do with this problem.

mikkkie, I could not change the matrix value in Procoder, it's not like CCE or TMPGEnc that you have options to change matrix value.

I am going to try Frame serving (going directly from VV4 to procoder) seeing if I can bypass the rendering.

One more note that I did use different codec i.e. Main Concept, Canopus too and they all demonstrate the same jagged edge symptom on pure RED and Blue color.

I guess I can solve my problem by not using any pure red (R=255,G=0,B=0)or blue in my slanted text.

Thanks again
ARK