Strange Error Message

[HellSpawn]

Hello everybody.
I have come across a problem I have not met before.I am trying to encode the movie Sighns.I use the XviD-17022003-1 build and the following avs file.

LoadPlugin("E:\DivX\Ogg\mpeg2dec3 v0[1].94\MPEG2Dec3.dll")
LoadPlugin("E:\DivX\Ogg\Convolution3DYV12\Convolution3DYV12.dll")
LoadPlugin("E:\DivX\Ogg\UnFilter\UnFilter_Avisynth_2.5_Alpha\UnFilter.dll")
mpeg2source("F:\Sighns\sighns.d2v",cpu2="ooooxx")
crop(16,12,688,552)
Convolution3D(preset="movieHQ")
LanczosResize(640,352)
UnFilter(-5,-5)
LumaFilter(-2)
SelectRangeEvery(280,14)

I was trying to make a compressibility check.When I tried to open the stats file in Gordian Knot I got the error message saying

"Floating Point Division By Zero".

I am using that procedure for some time but I have never seen that before.Any ideas what is going wrong?
Thanks in advance.

[TelemachusMH]

I have gotten that error almost everytime I try to open an Xvid stats file with GordianKnot, and I don't know what it is though. So, I'll be checking in later and hopefully someone knows.

TelemachusMH

[MoonWalker]

Well I think that the structure of the stats file has changed a little (for skipped/pad/delayed frames) thats why this happens..Try opening it normaly(not from the load button) and press NO at the message tha says about wrong frame numbers

MoonWalker

BTW Try it without B-Frames to see if it has still the same problem

[HellSpawn]

I tried it without the B-frames and it worked.I guess you were right MoonWalker.Thanks for the tip.However this is going to be a problem when trying to make acompressibility test.Am I supposed to assume that the movie will be even more compressible when using the B-frames?

Thanks for the help Great Master:D

[cult]

you can open them,from nadbub files/open and answer no.It will show you the compcheck with bframes

[HellSpawn]

Thank you very much cult.:D

[kxy]

Originally posted by HellSpawn
mpeg2source("F:\Sighns\sighns.d2v",cpu2="ooooxx")
crop(16,12,688,552)
Convolution3D(preset="movieHQ")
LanczosResize(640,352)
UnFilter(-5,-5)
LumaFilter(-2)
SelectRangeEvery(280,14)


Care to expalin why you choose this particular script?

[cult]

I dont see anything wrong with his script...You mean that you want to explain what the filters do?

[HellSpawn]

I only gave you that script because I wanted to know if the problem I faced resulted from it.It proved that certain things have changed in the Xvid codec that resolved to that error which was nothing more than a storm in a teacup.

[kxy]

I am not saying that his is wrong.

Yes I want explanation, like how is works. See this thread.
http://forum.doom9.org/showthread.php?s=&threadid=46273

[cult]

sorry kxy
he usesConvolution3D(preset="movieHQ") as a smoother with low seetings to gain some compresability.He puts it before resize to gain better quality.If c3d was after resize he would gain a little more compressability and speed in encoding but he would sacrifice quality.
LanczosResize(640,352) .He uses lanczos as it mentioned as the best resize filter in terms of quality,for the time.
UnFilter(-5,-5)
LumaFilter(-2)
The combination of these 2 filters helps to avoid blocks in dark areas.Unfilter (-5,-5),blurs the image a little.If it was (5,5),it would sharpen it.
Lumafilter(-2)darkens the image alittle
SelectRangeEvery(280,14) .This I think was put there just for a compecheck as gknot does.It means that 14 frames every 280 will be encoded(5% of the film).You dont need it if you are doing a full 2pass encode of course.
The explanations is little non-technical but hope it helps

[kxy]

Thanks cult, for taking your time to explain. I pretty much understand what they do, as you can see from the thread that I linked. It just that some people didn't like the particular order, but didn't really say why. Therefore I am trying to find out the good combination of the ordering...

For me, the ordering of his script didn't make a lot of sense. He is using c3d, which blur the pic a bit then he uses lanczos, which is a sinc function that keeps great amount of detail, in another words it sharpen the pic to a great deal. But then he uses UnFilter(-5,-5) which soften the picture again.

Won't it make more sense to do whatever filtering you need and afterwards use lanczos to keeps the what ever sharpness is left. I purpose the following, what do you think?


crop(*,*,*,*)
LumaFilter(-2).UnFilter(-5,-5)
Convolution3d(preset="movieHQ")
LanczosResize(*,*)

[cult]

as I said before,putting them before resize results in better quality but slower encoding.Its usal better to put c3d before resize and have better quality.Lumafilter and unfilter dont need any to be before resize,their job is easily done after resize without sacrifising quality.Thats my opinion though :).I do something similar too

[HellSpawn]

If I used the filters in the order given by kxy,the only thing I would manage to accomplish would be to sharpen the picture.You are right cult this way causes slow encoding(12 frames/sec on an AMD Athlon 1800+ XP) but results in higher quality.:D