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.
--------------------- Stancing is for drivers trapped in an abusive relationship of their own lives.
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...
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 :))
--------------------- 1995 M3 Alpine White 4/94 production date. Clear Corners, E46 metal pedals, X-brace, Euro Floating Rotors, Motorsport Strut Brace, H&R Coilover Suspension, Kmac Camber Plates, Ground Control Adjustable Sway Bar End Links, UUC TME's, UUC TSE, JC Euro
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
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
Поиск 
Users
Entrance
RE: Bug in BicubicResize
