VDubMod, .d2v, avs problem?

AaronAMV · Post by **AaronAMV** » Tue Jul 29, 2008 11:16 pm

Hmm... Okay.
Wow, I didn't know you could actually just drag and drop... Well thanks! Both of you!

AaronAMV · Post by **AaronAMV** » Tue Jul 29, 2008 11:41 pm

However, while this thread isn't dead yet...
I can't find a good script to get rid of the interlaced edges on my source. >_<
Any tips?
It's 5 Centimeters per Second if needed.

Mosc · Post by **Mosc** » Wed Jul 30, 2008 6:25 am

LivingFlame wrote:When you say "Use AVISynth template" to open the file (or "Open video file via AVISynth"), what the program is essentially going to want to do is make an AVISynth script to call another AVISynth script, which won't work.

Actually, AviSynth can open other AviSynth files just fine with either Import, AviSource or DirectShowSource. I have no idea what the problem here was because I don't use VirtualDubMod, but using AviSource to open an AviSynth file with MPEG2Source should not cause any problems. Why? Because even though an AviSynth script is not an actual video file, it appears to be one to any application that tries to open it using the VfW or DirectShow framework.

LivingFlame · Post by **LivingFlame** » Wed Jul 30, 2008 8:40 am

Well AviSynth should know the difference since it's its own file type. And obviously it wasn't working out anyway. =\
My guess is the Vdub looks at the file extensions and it knew darn well that that script file wasn't an AVI file. (Since it's already programmed to know what an .avs file is.) Just a guess, though.

And for the life of me, I can't think of the filter that would help get rid of those edges. I know there is one, but I just can't think of the name...
We are talking about rough edges left after deinterlacing, correct?

AaronAMV · Post by **AaronAMV** » Wed Jul 30, 2008 12:02 pm

LivingFlame wrote:And for the life of me, I can't think of the filter that would help get rid of those edges. I know there is one, but I just can't think of the name...
We are talking about rough edges left after deinterlacing, correct?

Correct.
The edges are still a little deinterlaced.
I mean it's not that many scenes, but you never know. I might happen to use it, so yeah...

Scintilla · Post by **Scintilla** » Wed Jul 30, 2008 5:08 pm

Mosc wrote:
LivingFlame wrote:When you say "Use AVISynth template" to open the file (or "Open video file via AVISynth"), what the program is essentially going to want to do is make an AVISynth script to call another AVISynth script, which won't work.
Actually, AviSynth can open other AviSynth files just fine with either Import, AviSource or DirectShowSource. I have no idea what the problem here was because I don't use VirtualDubMod, but using AviSource to open an AviSynth file with MPEG2Source should not cause any problems. Why? Because even though an AviSynth script is not an actual video file, it appears to be one to any application that tries to open it using the VfW or DirectShow framework.

Yes, but it appears as a Video for Windows file, not an MPEG-2 file, and certainly not a .D2V index file (which is what MPEG2Source expects to see). So of course it'll cause problems.