Log in

View Full Version : problem with xlogo


killingspree
28th May 2003, 08:21
hi folks,
i'm currently testing some delogo filters/methods for both vdub and avisynth and came upon a problem when trying to use xlogo in avisynth.

here's my script to start with :

loadplugin("c:\programme\avisynth 2.5\plugins\decomb.dll")
loadplugin("c:\programme\avisynth 2.5\plugins\convolution3dyv12.dll")
loadplugin("h:\warpsharp\loadpluginex.dll")
loadplugin("h:\warpsharp\xlogo\xlogo.dll")

#import("dekafka.avsi")
clip=avisource("capture000.00.avi")
clip=Trim(clip,694,0)
clip=FieldDeinterlace(clip)

clip=converttorgb32(clip)
#Xlogo(Clip, filename, X, Y, ALPHA, T1, T2, T3, B1, B2, B3, WHITE, SIDE, SCENE, FEATHER, NOISE)
xlogo(clip, "h:\capture\orfmask2_2.bmp", 561, 81, 255)

i'm using avisynth 160403 (2.51 i guess :)) but it should work with loadpluginex.dll?

anyway, when loading the script into virtualdub i get the following error:
Avisynth open failure:
X-Logo: Could not load tables
(H:\capture\capture.avs)

the bitmap is definitely RGB24 as required

i know that Wilbert who is also doing some testing ecnountered the exact same problem.

thanks for your help
steVe

Leuf
1st June 2003, 06:26
The "Could not load tables" error message almost invariably is caused by the interpolation bitmap not having the required border of background color around the entire edge of the bitmap. So whenever you see this message double and triple check the bitmap. I find the easiest way to do this is to open it in photoshop or whathaveyou, enlarge the window around the bitmap and then go around just to the outside of the edge with the pencil tool. The only other way that error should be generated would be if you were out of memory.

Also, you have ALPHA backwards. 0 means all interpolated, 255 means no interpolation, so setting 255 and only an interpolation bitmap will just give you the source back. I should really change that to a floating point 0.0-1.0 at some point, that's a vestige of the vdub logo filter ;)

I've never been completely happy with the interpolater. It flickers too much to be practical by itself. I have an alternate interpolation routine in the works that is showing some promise for odd shaped logos, hopefully I can release that in a few weeks.

killingspree
1st June 2003, 06:31
thank you for your valuble info. i'm going to check right away!!
going to post back as soon as i got some results!

steVe

edit: ok i wasn't very successfull ): i added a ton of lines on the outside, but it still gives me the error. i don't think that i'm out of memory either since i have a gig of DDR ram which should be sufficient!
if it helps i can email you my bitmap for examination!

Leuf
1st June 2003, 08:26
Sure I'll have a look, legend65@yahoo.com

killingspree
1st June 2003, 10:23
thanks,
i've sent the email!

steVe

Leuf
1st June 2003, 21:50
That bitmap works fine for me in both the vdub and avisynth versions. You might try the vdub version, if it works there but not in avisynth that should help narrow down the problem.

killingspree
1st June 2003, 21:56
ok... i will try that tomorrow. i've got an encode running at my enc machine so i can't do it right now... i'll report back as soon as i've got some results!

perhaps it has something to do with my avisynth version. i'm currently using v2.51 (16042003)

thanks
steVe