Log in

View Full Version : strange artifact using new koepi 1.0.1


split710
10th June 2004, 01:35
hi

Encoding with 1.0.1 I have an artifact problem watcing with Kiss 450 (firmware 2.8.5) not encountered till 1.0 final

Windows XP

I normally use Xvid codec to encode

source = 3 CD SVCD
end: 2 CD Xvid

codec configuration:

first pass

level 5
quantiz MPEG
adaptive quant OFF
B-Vop's 1
Quant ratio 1.00
quant offset 0.15
packed Bit OFF
closed GOV ON

zone:
Chroma optimiz enabled ON
BVOP sensit 1

advanced:
use chroma motion ON
quantiz 1/31 1/31 1/31
trellis ON


second pass:
overflow control 0
max overflow improv 4
max overflow degrad 9
all the rest as default

zone:
as first pass

advanced:
use chroma motion ON
quantiz 1/12 1/12 1/12
trellis ON

I normally use these setting changing just some little things like for example quantization, I use sometimes H.263

I normally don't have big problems with good result

Using 1.0.1 I have a new problem never seen before

first at all

first pass DONE
second pass DONE (warning)

AVI was created but never seeen "(warning)" before

problem is:

watching with PC AVI was WELL, no strange artifact

watching with Kiss 450 there are a lot of "little-ball snow" (many many) in all black colour (not on the darkness scenes but only in the "BLACK" colour).

I just reencoded first 2 minutes (with a lot of black colored scenes) using 1.0 final and asame configuration and watching with Kiss I have not encoutered the same problem.

Problem is with Stand alone player only, I think 1.0.1 is not 100% compatible with them. or...... I don't know

ciao

madman_looney
10th June 2004, 07:51
Did you try watching it using firmware 2.8.3? 2.8.5 is known to be shitty.

split710
10th June 2004, 12:11
thanks madmann

sorry I made a mistake writing....... I am using 2.8.3 firmware already (2.8.5 suffer to crash), i have the problem with 2.8.3.

I forgot to mention I use:

AVS script + Virtualdubmod 1.5.10

All non black colours have no problems. It's a kind of video noise never seen before.

ciao

greycortex
11th June 2004, 00:53
This issue sounds like something I have been seeing while backing up such dark films as Tomie: Rebirth and Versus. I think I shut off Chroma Optimization to clear this issue, but I'm not one hundred percent certain.

split710
11th June 2004, 08:12
thank's for the suggest but with 1.0 final (with chroma optimization ON) there aren't these artifact....

before speacking as a codec bug I will try on Magnex player this evening, I would like to be sure about Kiss firmware bug (or not updatet well for 1.0.1)

ciao

Manao
11th June 2004, 08:42
split710 : first, for the "warning" problem, do not worry. It simply means that during the encoding process, VDubMod found that another program was using a lot of resources. But it doesn't change the encode at all. However, I would recommend to use only VDubMod 1.5.4.1 for encoding ( and 1.5.10.1 for muxing ), because 1.5.10.1 has some issue with deadlocks.

Now, for your issue. What you're describing sounds a lot like a saturation issue : when during the decoding stage, the Kiss player might use 'int' for the computations, and convert them to char implicitely. However, if they are making the assumption that the 'int' is bound to be in the '0-255' range, they might be careless while making this conversion, and if by any chance one of the 'int' was -1, it will become 255 : a white dot in a black area.

This is the only explanation I can think of, and I'm afraid it's the right one. But that doesn't explain why the 1.0 doesn't have this issue. The main differences between 1.0 and 1.01 are b-frames and treillis. You're using both. Could you try to encode a specific part of the movie where those white dots appear, with and without b-frames, and with and without treillis ?

split710
11th June 2004, 20:47
yes... I can do it..

I will try to encode using 1.0.1 and VDmod 1.5.4.1 with and without trellis

I also can try to encode using 1 - 2 Bframes and NO b frames

i will report result tomorrow morning at last.

This strange matter is regarding 1.0.1 only. With 1.0 I don't have artifacts problems, I don't have artifacts watching with PC too.

could be that some config are just a little changed and not full compatibles with stand alone only.

ciao from Italia :)