DirectShow version of Avisynth

[Gabrielgoc]

It is possible a DirectShow version of Avisynth? so you should make a DS grapho to avoid .avs compatibility.

THK

[LigH]

This would probably be a great idea, BECAUSE: Several applications (e.g., MainConcept MPEG Encoder) load and analyse AVIs by themselves, instead of using the most compatible Windows functions. Such applications will never be able to open AviSynth script files (unless someone creates another import module for "compatibility mode").

But to pick up my example again: Besides the AVI import module, the MainConcept MPEG Encoder also has a DirectShow import module. With a DirectShow file handler for AviSynth (just like those for OGM or Matroska file formats), we could be able to serve the MCME using this path.

My latest work-around for this case was using the VFAPI Converter, creating a pseudo AVI on the AVS script file; fortunately, this worked because I had an AviSynth reader plugin for VFAPI registered (I'm not sure how it got registered, but because I found it in a DVD2SVCD subdirectory, therefore I guess it must have been installed with DVD2SVCD). Definitely not the fastest road...

[mf]

Originally posted by LigH
But to pick up my example again: Besides the AVI import module, the MainConcept MPEG Encoder also has a DirectShow import module.
Dshow uses an AVS compatible AVI parser. So, with Dshow, you can open any AVS. Give me one good reason why you need something else than the Dshow AVI parser. Or better yet: have you even TRIED using AVS files with that "DirectShow import module" ?

[LigH]

I tried to change the priority of either the AVI or DShow import module to be the highest - MCME always just crashed. Did it work for you?!

[mf]

Originally posted by LigH
I tried to change the priority of either the AVI or DShow import module to be the highest - MCME always just crashed. Did it work for you?!
And a AVS-specific Dshow parser would solve that problem ? What makes you think that ? It's clearly a problem in their importer, so submit a bug report.

[LigH]

So you are probably right: I checked this issue with GraphEdit - it was easily possible to "render" an AVS file. But MCME crashes in any configuration I tried. Well - I just hope that MainConcept will react on such a "bug report"... We'll see.

[LigH]

UPDATE:

It works. You can use AviSynth scripts as source in MCME.

Don't ask me why it didn't work yesterday, but later I could successfully load AVS files in the following environments:

- Windows 98 SE, AviSynth 2.08 in YUY2 and RGB
- Windows 98 SE, AviSynth 2.51 (VDubMod plugin syntax-hl. modification), in RGB and even in YV12!
- Windows 2000 SP2, AviSynth 2.08 in YUY2 and RGB

Of course, it is necessary to raise the priority of the AVI import module (or disable the DirectShow import module).