Fix interlaced footage previously saved as progressive?

[spoRv]

I have always to call the plugin, even if it's in the AviSynth plugin folder...

Code:

Loadplugin("C:\Program Files (x86)\AviSynth 2.5\plugins\DGDecode.dll")

It's one of the few ones which does not automatically load...

I still use Windows XP 32bit, and the FFTW dlls are in the Windows/System32 folder - don't know if they should be in another folder when a 64bit operating system is used, though.

[Valeyard]

What? Jesus! You can buy Windows 7 for just $20 you know.

[Booshman]

Ok, I reinstalled, and after 3 hours of dicking about with plugins it finally worked! The install directory was just avisynth as you said. The clip looks much better. There is some ghosting, which I'm not sure is to do with the filters at work, or a seperate issue that will need to be dealt with.



Now that I'm trying to save the video I have hit another snag. When I select tools/ script encode (VFW). I get multipke consecutive errors. avs2avi.exe - Bad Image

It lists 92 plugins with this same error.



If I click through all of them, I get to the select codec box, and it encodes.

Any thoughts on how to remedy the errors?

[spoRv]

What? Jesus! You can buy Windows 7 for just $20 you know.

I know; but some hardware and software will not work properly with my old peculiar PC (I know that for sure!); waiting for the new (old) one, though!

[zoidberg]

I had the same problem when I upgraded my old Dell to Win7, drivers didn't exist for the old hardware and had to use generic ones.

[Booshman]

I sorted the errors. I went though every one of the dll files mentioned and removed them.

[Valeyard]

There is some ghosting, which I'm not sure is to do with the filters at work, or a seperate issue that will need to be dealt with.

The ghosting is in the source. You can easily load the clip without any filters and use separatefields() to see it. I don't know of any way to deal with the ghosting unfortunately.

As mentioned though you'll need to check the parity of the decimated fields, I suspect quite a lot of work to keep it removing the blended fields. You can always use srestore() if you want a less perfect result but much faster.

[Booshman]

There is some ghosting, which I'm not sure is to do with the filters at work, or a seperate issue that will need to be dealt with.

The ghosting is in the source. You can easily load the clip without any filters and use separatefields() to see it. I don't know of any way to deal with the ghosting unfortunately.

As mentioned though you'll need to check the parity of the decimated fields, I suspect quite a lot of work to keep it removing the blended fields. You can always use srestore() if you want a less perfect result but much faster.

Thanks for the info. It's already looking much better so I'll probably just go with srestore to save time. I've spent a load of hours on this over the last few days, so quicker will be better.

I have another source, different capture of the same movie, which I will be checking tonight after work. It's PAL and not NTSC. Can the same script be used or will it need adjusting?

And one last thing that I just spent over an hour of my lunch on with no joy:

After reinstalling avisynth, removertdirtmc.avsi no longer works. I get get an error, even if I add an import line to the script. The avsi file is in the plugins directory, so I'm mot sure why it won't autoload, I've even more confused as to why the manual load fails.

[Valeyard]

Can the same script be used or will it need adjusting?

I suggest reading my thread here. Have a look first and see what the source looks like (mpeg2source with no filters). It may not even need to be de-interlaced. If it does then you need to figure out what kind of source you have first, and then de-interlace it accordingly.

And one last thing that I just spent over an hour of my lunch on with no joy:

After reinstalling avisynth, removertdirtmc.avsi no longer works. I get get an error, even if I add an import line to the script. The avsi file is in the plugins directory, so I'm mot sure why it won't autoload, I've even more confused as to why the manual load fails.

Perhaps try Removedirt.avsi instead, multi-thread stuff is known to sometimes be problematic.

[Booshman]

Can the same script be used or will it need adjusting?

I suggest reading my thread here. Have a look first and see what the source looks like (mpeg2source with no filters). It may not even need to be de-interlaced. If it does then you need to figure out what kind of source you have first, and then de-interlace it accordingly.

And one last thing that I just spent over an hour of my lunch on with no joy:

After reinstalling avisynth, removertdirtmc.avsi no longer works. I get get an error, even if I add an import line to the script. The avsi file is in the plugins directory, so I'm mot sure why it won't autoload, I've even more confused as to why the manual load fails.

Perhaps try Removedirt.avsi instead, multi-thread stuff is known to sometimes be problematic.

I finally got all the new plugins and the avsi scripts working at the same time. Massive pain in the arse since I'm not sure exactly what was wrong. all good now though, just wanted to say thanks again for you taking the time to help out on this.