FFT3D filter dehalo call is glitchy on my new pc

[grannyGeek]

I'm sorry if this post is long, but I don't know which little scrap of information might turn out to be the key to solving my *sporadic* VirtualDub / VirtualDubMod lock-ups.

My rock-steady old HP died, and I had to get a replacement- Vista was pre-installed, an IT friend tried to partition so I could dual-boot to XP, but Vista security wouldn't let the XP installation complete properly. He ended up wiping the drive, and installing XP only, since no Vista System Recovery disks got made.

I have tracked down and installed drivers and codecs, and *almost* everything is working fine.

HP 3.20 ghz dual processors, running XP-Pro SP2.
Using AviSynth 2.57 (I also tried rolling back to 2.55, no joy)
VirtualDub 1.6.17
mostly using VirtualDubMod 1.5.10 with Script Editor, but problem occurs in VirtualDub as well.

Source files are retail vhs tapes, captured and/or encoded with Huffyuv or Lagarith to YUY2.

I have tried FFT3D filter both version 1.91 AND 1.92, and I get the same *sporadic* lock-up problem when adding calls to the FFT3d dehalo function. Calls to de-noising parameters have never caused a problem.
I NEVER had a problem on my old pc, so I don't know if it is hardware or codec-related.

script lines are something like this:

JDL_ApplyRange(1000,2000,
\"fft3dfilter(bt=-1, plane=0, dehalo=1.0, hr=2.0, ht=50, svr=0)")

I can add a number of calls like this without problem, then suddenly adding one or going back and changing parameter settings on a previous one, and using script editor F5 key to "Save & Refresh" causes a silent lock-up, VDM screen goes white, and I have to end it with Task Manager. Sometimes simply re-loading the script is successful, other times same white screen and Task Manager to end it.

If I can get VDM or Vdub to load once with the "problematic" call, then it seems to be ok after that, and that particular line of code causes no more trouble.

My current script has 15 to 20 calls like this, but on my old pc, I had scripts with 50 calls or more, and no trouble at all. So I don't believe the fault lies with FFT3d.

I would prefer to continue to use the FFT3d dehalo function, so I can avoid the conversion to YV12 that dehalo_apha requires
(and FixVhsOversharp is just too aggressive for my source files, and dims out too many bright highlights.)

I'll be most grateful for any advice -
Thanks,

granny

[Didée]

Sorry I've no idea where that problem might come from, except for that "refreshing" in Vdub usually will fail sooner or later.

However, the problem I would prefer to continue to use the FFT3d dehalo function, so I can avoid the conversion to YV12 that dehalo_apha requires can be worked around quite easily:

clip_yuy2 = whatever
clip_yv12 = clip_yuy2.ConvertToYV12()
clip_yv12.Dehalo_alpha().MergeChroma(clip_yuy2)

This is because dehalo_alpha does not process chroma, anyway.

[grannyGeek]

Didee, thank you so much for the tip of how to handle the dehalo / Yv12 issue. This will make my life so much simpler!

The refresh issue is definitely related to FFT3d dehalo, but I still have not been able to isolate the exact cause.
I can put dozens of "ApplyRange" lines for other filters, refresh each time every two minutes, and Vdub never flinches.

I guess my life needed a little mystery.

Thanks again !