View Full Version : Bug in BicubicResize

Bonzo
3rd December 2002, 00:28
I've got a full green frame (see the attached picture) in virtualdub when i run this script:

LoadPlugin("I:\Utilidades A-V\Avisynth\MPEG2DEC.dll")

mpeg2source("I:\0782192\lvi.d2v")
BicubicResize(448,432,24,0,672,576)

I'm currently using avisynth 2.07 but 2.06 and 2.05 have the same bug. BilinearResize or Lacnzos works just fine:

mpeg2source("I:\0782192\lvi.d2v")
LanczosResize(448,432,24,0,672,576)

Bonzo.
Bonzo
3rd December 2002, 00:32
I don't know how to attach to pictures in a post, so in this post i include the LanczosResize result in VirtualDub.

Bonzo.

PD: BicubicResize outputs all frames as an ugly green frame, not only the one showed in the picture attached in my last post...
Kyo
3rd December 2002, 00:59
Try First: BicubicResize(448,432,0,0.5,24,0,672,576)

And also if you take out the crop you gain in speed(maybe a 0.5fps :))
Guest
3rd December 2002, 01:42
I disapproved the pictures, because you can easily use words to say the frame is all green, or that it is not all green. :)
scmccarthy
3rd December 2002, 02:08
At one point Sh0dan said he plans to discontinue using the resize filters to clip. The idea being it is buggy and is really slower than using Clip followed by a resize filter. I think the BicubicResize filter will work if you use the Clip filter first instead.

Stephen
sh0dan
3rd December 2002, 08:53
@Bonzo: Ever tried just crop(24,0,672,576) / BicubicResize(448,432) - I bet it will work. (Kyo is right - the crop parameters are used as b/c parameters)
Bonzo
4th December 2002, 22:54
Er... I didn't know that cropping in the resize filter where slower. I thought just the opposite; may be the documentation should mention this issue.

Well, now i use crop before any resizer and everything works fine again... :D

Bonzo.
scmccarthy
5th December 2002, 02:05
Well, you know, the orignal idea was that it would be faster, but it's not. And since it is not, there is no real need to fix the problem with BicubicResize other than to remove the new feature entirely. As you can tell, giving BicubicResize two sets of optional arguments is confusing for the user and tricky to code for the developer. It likely would have been fixed right away if it had been a speed improvement though.

Stephen