CCE FAQ Discussion

[mp3dom]

Originally Posted by Maxiuca

I'm wondering what to do when dealing with a progressive PAL film. I've usually encoded it using default CCE settings (so TFF) and then ran it through ReStream to set the progressive flags (CCE for some reason does not set them).

CCE supports progressive frametype just fine, as long as you set it to encode in a progressive way. It does not flag the progressive sequence, but it flags the progressive frametype. This means that you can still switch (if you need) some frames from progressive to interlaced (and vice-versa) between the stream. Progressive sequence does not allows this.

So should I uncheck TFF and leave the BFF flag?

If you really want to have a progressive sequence flag, the only in-specs way I'm aware of is to (looking inside ReStream):
- have picture structure set to frame (no field)
- (probably) scanning mode set to zig-zag
- have frametype progressive checked
- have top field first unchecked
- have progressive sequence checked

The problem is that after encoding, strange vertical artifacts (lines) appear at the border of the pillarbox and the actual image.
Any ideas what may be causing this?

Which CCE version are you using? SP2 or SP3? You should tells how you've setup the encoder and/or how the source was made. TMPGEnc works (in the past, don't know now if something has changed) in RGB colorspace, while CCE works in YUY2. If the source is not in YUY2 some conversion is applied. Also, have you disabled the various lowpass filters (enabled by default in all CCE versions)?

[neil wilkes]

Originally Posted by mp3dom

Also, have you disabled the various lowpass filters (enabled by default in all CCE versions)?

What circumstances should these filters be disabled under, just for information?

[mp3dom]

With all filters disabled, the encoder gets the same "input" as the source. With filters enabled (by default), prior of the encoding process, the source is filtered in some way. Lowpass filters are used to remove some "spike" frequencies, limits the flickering effect and allows the encoder to compress 'better' (with less bitrate, since there are less high frequencies) the image. Those filters can be useful by some extent when you're downscaling from HD source to SD. On a standard defs source image, probably the image is already lowpassed and so the filters are less useful (also, since the lowpass filters 'truncates' high frequencies, the side-effect is to have a sort of "localized blur" onto the image or something similar to an 'edge-enhancement' filter).

[Maxiuca]

Originally Posted by mp3dom

CCE supports progressive frametype just fine, as long as you set it to encode in a progressive way. It does not flag the progressive sequence, but it flags the progressive frametype.

CCE SP2 did flag progressive frametype, but CCE SP3 does not for some reason. Neither of them flags progressive sequence.

Originally Posted by mp3dom

If you really want to have a progressive sequence flag, the only in-specs way I'm aware of is to (looking inside ReStream):
- have picture structure set to frame (no field)
- (probably) scanning mode set to zig-zag
- have frametype progressive checked
- have top field first unchecked
- have progressive sequence checked

I've been using all those settings (both CCE and ReStream ones) for a long time now I was just unsure about the TFF/BFF (since TFF is always checked by default).

Originally Posted by mp3dom

Which CCE version are you using? SP2 or SP3? You should tells how you've setup the encoder and/or how the source was made. TMPGEnc works (in the past, don't know now if something has changed) in RGB colorspace, while CCE works in YUY2. If the source is not in YUY2 some conversion is applied. Also, have you disabled the various lowpass filters (enabled by default in all CCE versions)?

As mentioned before, I'm using SP3.
In picture settings: all filters are disabled, quant characteristics set to 32, Zigzag scan order, picture type progressive.
In segment settigs: intra block DC precision set to 10-bit, quant scale to no linear and quant matrix to adaptive. I use the default (Natural 1) quant matrix instead of MPEG standard one (changing it didn't help).
The source is RGB, quicktime with no compression (I've tried AVI with no compression as well) that is exported directly from Nucoda Fuse grading/finishing system when it has been scaled to PAL from a 2K source (that underwent restoration process) and and prepared for encoding so degrained/denoised/sharpened.

I've made a lot of DVD streams and most of them for retail DVD and newer had problems until now.

I'll try converting the source to YUV2 prior to encoding and see the result.

[mp3dom]

Originally Posted by Maxiuca

CCE SP2 did flag progressive frametype, but CCE SP3 does not for some reason. Neither of them flags progressive sequence.

Uhmm, I'm using SP3 too, and it works the same as SP2. It flags progressive frametype without problems.

I've been using all those settings (both CCE and ReStream ones) for a long time now I was just unsure about the TFF/BFF (since TFF is always checked by default).

With Progressive Sequence On then you should set TFF off.

In picture settings: all filters are disabled, quant characteristics set to 32, Zigzag scan order, picture type progressive.

If you 'edit' the presets (all presets are setup as interlaced with LPF ON with different strength) you also need to save it using another name and then apply your preset to the source (double click on the first frame, check the "picture" box and choose your previously saved preset). If you don't apply your preset, the default one will be used (which is "Natural 3").

[Maxiuca]

Originally Posted by mp3dom

Uhmm, I'm using SP3 too, and it works the same as SP2. It flags progressive frametype without problems.

Strange, SP2 had a setting called "Progressive frame" in "Picture quality" and as far as I remember it was responsible for the progressive frametype flag (probably it was responsible for other things as well, but that's not the issue).

SP3 has "Picture Type" setting that allows to choose between Interlaced, Progressive and Auto Detect (with threshold that you can specify) but it does not affect the flag or am I missing something?

Originally Posted by mp3dom

With Progressive Sequence On then you should set TFF off.

Thanks for confirming that. I had no problems with TFF flag in the past but it's always best to stick to specs as closely as possible. I will set TFF off from this time on.

I know that trick with saving settings (or loading from an XML file) to avoid reverting to default (Natural 3) settings.

I've tried YUV2 source (fed CCE SP3 with simple AVIsynth script AVISource.ConvertToYUV2) but the vertical artifact is still there.

Funny thing is that CCE SP2 does not have this problem.

[TheSkiller]

I can confirm what mp3dom says.

Originally Posted by Maxiuca

SP3 has "Picture Type" setting that allows to choose between Interlaced, Progressive and Auto Detect (with threshold that you can specify) but it does not affect the flag or am I missing something?

It does work, at least for me.
If you select "Progressive" the flag "Frametype progressive" is set (but not "progressive_sequence"), if you choose Interlaced it is not. I never use Auto.
By the way, if you encode something that is entirely progressive it is not a bad idea to select "Zigzag" block scan order for improved encoding efficacy. But I see you're doing just that. For interlaced encoding never ever use Zigzag, only Alternate or Auto.

Originally Posted by Maxiuca

I've tried YUV2 source (fed CCE SP3 with simple AVIsynth script AVISource.ConvertToYUV2) but the vertical artifact is still there.

Please see this post by me explaining how to avoid any chroma smearing when serving YUY2 to CCE (any version) from a YV12 script. It's very important to have "Offset line" set to 0 for this to work.


Edit: Maybe you are simply not telling CCE SP3 to actually use your settings. It should look like this for example:

[Maxiuca]

Originally Posted by TheSkiller

It does work, at least for me.

Ok, thanks for you post. Now it works for me as well. It seems SP3 is following the DVD specs more carefully and will not add "Frametype progressive" flag if TFF is checked. With TFF unchecked and "Picture Type" set to Progressive (I never use Auto either, cause I deal with progressive material like 95% of the time) the "Frametype progressive" flag is in fact added.
And yes I use ZigZag.

Originally Posted by TheSkiller

Please see this post by me explaining how to avoid any chroma smearing when serving YUY2 to CCE (any version) from a YV12 script.

Thanks, will remember that trick. Fortunately most of my sources are pure RGB.

Originally Posted by TheSkiller

It's very important to have "Offset line" set to 0 for this to work.

Yeah, offset line was giving me a headache some time ago when I was told that my encodes have strange some bugs in bottom lines... Solved that though (thanks to forum archives).

I also found the solution to my other problem and it's rather simple and silly (kinda embarrassing in a way as well... ) It seems that I wasn't applying the "Picture settings" to the segment and I was encoding with the default (infamous "Natural 3") setting.
In SP2 the interface was somehow much more obvious and intuitive, but I've switched to SP3 recently for better scene detection (and therefore I-frame insertion, especially for B/W movies) and the interface has beaten me...

But now it's all good, thanks!!

EDIT: Funny thing, I found the solution to my problem, starting writing that post and after I've submitted it I saw your edit with the same solution

any videos link how to do these..

[TheSkiller]

What do you mean?

[tebugg]

dont mean to bring up this old thread, but i have a question about cce sp3. i keep getting the "out of memory" error at the start of the 2nd pass. i am using avs script to feed sp3 the info. also it is happening when i use a HD source as is something thats in mkv container with atleast 720p resolution. my avs script has "spline36resize(720,480)" so it is already doing the resize for sp3 but i still get the error at start of 2nd pass. is anyone else having this issue?

thank you.

[kolak]

You're using an old version- crashes with avisynth scripts were fixed long time ago.
If you have latest version than it's rather your script/avisynth problem.

[tebugg]

Originally Posted by kolak

You're using an old version- crashes with avisynth scripts were fixed long time ago.
If you have latest version than it's rather your script/avisynth problem.

you are right, i was using an older version. thank you for replying.

[subair37]

Hi Friends

Please help i am getting audio sync error when using cce sp3 , please help me to sort this out..............

[Guest]

We're going to need a lot more details than you have provided. Please open a new thread about it. This is a FAQ thread.

[szabi]

Hi

I have DV-AVI source which I want to encode DVD.
Canopus ADVC-1394 was used for it.
Canopus DV Codec is installed to the system.
For editing and deinterlacing an AVS file is created.
I try to load this AVS file to CCE SP3.
Unforunately various problems occur.
Once, this source can not be loaded.
Other case AVS is loaded but after few second, minutes of encoding start it crashes.
This time I got this log file:

14/01/05 08:52:11.072 Video output file: D:\myvideo.m2v
14/01/05 08:52:11.072 Video info file: D:\myvideo.vaf
14/01/05 08:52:11.072 Log file: D:\myvideo.txt
14/01/05 08:52:14.363 biCompression = YV12
fccHandler = YV12
14/01/05 08:52:14.377
<< Codec info >>
Name: XVID
Description: Xvid MPEG-4 Codec
Driver: C:\Windows\SYSTEM32\xvidvfw.dll

14/01/05 08:52:17.565 biCompression = YV12
fccHandler = YV12
14/01/05 08:52:17.578
<< Codec info >>
Name: XVID
Description: Xvid MPEG-4 Codec
Driver: C:\Windows\SYSTEM32\xvidvfw.dll

14/01/05 08:52:17.582 imp processor: 3 -> 2
14/01/05 08:52:17.630 exp processor: 5 -> 4

I do not understand why it is trying to use xvid codec instead of canopus DV codec?

Also i tried to start frameserver by virtualdub, but CCE can not load it.
Do you have any idea for solution?

[bigotti5]

Post your avs

[szabi]

Hi

Here:

SetMemoryMax(512)
SetMTMode(5, 6)
a=AVISource("D:\myvideo01.avi",fourCC="CDVC")
b=AVISource("D:\myvideo02.avi",fourCC="CDVC")
c=AVISource("D:\myvideo03.avi",fourCC="CDVC")
a+b+c
ConvertToYV12(interlaced=true)
SetMTMode(2)
Trim(0,271833).FadeOut(25)+Trim(272157,547882).FadeIO(25)+Trim(547917,668930).FadeIO(25)
Trim(0,215380).FadeOut(25)#1st disc end:Frame 215380 (2:23:35.200)
#Trim(215381,443113).FadeIO(25)#2nd disc end:Frame 443113 (4:55:24.520)
#Trim(443114,0).FadeIn(25)
QTGMC( Preset="Slow", EdiThreads=3, SourceMatch=1, Sharpness=0.3, TR2=1 )
SelectEven()
crop(14, 2, -2, -6)
AddBorders(8,4,8,4)

Also if ffmpgvariant huffyuv avi is saved by virtualdub, it can not be loaded to CCE SP3.

szabi

[kolak]

It's probably QTGMC problem, specially when it works fine for some time and than crashes. Try using just 1 or 2 cores and check if this works.
In case of heavy processing the best is to render an intermediate file and than do encoding.

[szabi]

I will try it out.
Thnx.