logo Sign In

DGIndex and CCE settings for progressive NTSC material.

Author
Date
Author
Time
Post link
I want to re-encode Star Wars NTSC version (resizing to anamorphic). Normally I only work with PAL so I could use some advice. I hope someone can help me with this.

1) In DGIndex I think it's best to set field operation to forced film since I'm dealing with progressive material. Is this correct?

2) Should I set YUV -> RGB to TV scale or PC scale. I guess if I use a luminance level of 0 - 255 in CCE I should use TV scale. (If I use PC scale the luminance level in CCE has to be 16 - 235.) Is this correct?

3) I want to encode it as progressive frames in CCE so I select a frame rate of 23.976. Will CCE set the pulldown flags automatically or do I have to use a program later to insert the flags in the m2v stream (I did this once a long time ago but I forgot the program's name). What are the best settings? What is the difference between 2:3 en 3:2 pulldown (I know that the order of inserted fields is different but I don't understand what this matters for playback)?

4) In the picture settings of CCE I check the progressive frame box and I set the block scan order to zigzag. Is this the good setting for progressive NTSC material?

I use CCE SP2.
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Post link
1) - Correct.

2) Doesn't matter, because you will probably be staying in YV12 colourspace, so there will be no conversion to RGB.

3) Yes. If you tick the box "for DVD" then the pulldown flag will be inserted for you. 2:3 pulldown is the norm, but there's no difference.

4) Yes, although you can leave block scan to auto if you like.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Post link
2) Doesn't matter, because you will probably be staying in YV12 colourspace, so there will be no conversion to RGB.

And if I use an avisynth script with rgbadjust?
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Post link
Then AVISynth will handle the conversion to RGB.

The YUV->RGB setting in DGIndex only affects VFAPI upsampling (and the display window?). I've never used the VFAPI plugin (DGVfapi.vfp), I've always used AVISynth/MPEG2Source().

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Post link
OK. So the data CCE receives will be the same whether I use PC scale or TV scale?
And the 16-235, 0-255 setting in CCE? Will that effect the brightness of the output video?

EDIT: I just tried to encode, but cce said there was no yv12 decoder installed. When I add converttorgb in the script it encodes fine. But do I loose video quality because of the conversion to RGB?

EDIT2: I did a small test. My script ends with "converttorgb". I encoded with 16-236 and 0-255 levels. In the 0-255 video the blacks are darker and the brights are brighter. Well, I guess that's what could be expected when the range is increased.

Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Post link
CCE uses YUY2, and cannot accept YV12 input. If you have the XviD codec installed, then that will act as the YV12 decoder. Or you could use ConvertToYUY2 in your script.

You've done the right thing by carrying out a test. By comparing the input to the encoded output you can satisfy yourself that the correct luminance range is retained.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time
Post link
Thanks for the help Moth3r.
Fez: I am so excited about Star Whores.
Hyde: Fezzy, man, it's Star Wars.
Author
Time
Post link
You're welcome.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here