VirtualDub / Avisynth setup problems

[Busty]

Hi everyone,

I hope someone here can help me figure out what is wrong in my setup.

I revived an old installation of AviSynth 2.6 and VirtualDub 1.10.4 and fail to open an AviSynth script in VirtualDub. It did work when I used it about 8 years ago, but now it doesn't. This installation is on a MacPro running El Capitan, done with PlayOnMac following l33tmeatwad's instructions from about 2016, in case that matters.



VirtualDub does open the version test script as described here: http://avisynth.nl/index.php/First_script

I can open the video with drag and drop into VirtualDub.

When I try to open an AviSynth script, VirtualDub stops responding.


I tried scripts like these:

AviSource("c:\folder\myclip.avi")

and

DirectShowSource("c:\folder\myclip.avi")

(I created the according folder and put the video in there)


My only idea is it might be an AViSynth codec issue. How can I check which codecs are installed for AviSynth? Or does anyone have a more indepth idea of what might be the problem?

[Busty]

This is a bit funny as well as embarrassing, but I just found a post over at digital faq that I did in 2016. It describes this exact problem. I might have to work on my memory....

https://www.digitalfaq.com/forum/video-conversion/7464-open-avs-virtualdub.html

Anyway, in that post I suspect a different source for the problem: The installation of wine gecko and wine mono failed. This is still the case.

I downloaded gecko and mono, but I'm at a loss how to install them with PlayOnMac. Does someone know?

[Busty]

Turns out I got the same problem about nine years ago. In the end, everything is working as expected, I was just throwing wrong codecs at avisynth. With the right codecs it all works.

So, self inflicted problem solved. sorry to have bothered you guys with my incompetence:-)

[qyot27]

To be fair, getting Wine to work with appropriate codec support (read: ffdshow VFW for AVISource; unless something's changed, DirectShow and Wine don't mix) is a chore, so using FFMS2 or LSMASHSource as the source filter is the objectively better option.

Or, if you're willing to really get in there, use MacPorts to install modern versions of the appropriate build tools and compile AviSynth+ natively, followed by FFMS2 and/or LSMASHSource. Whether the native version + the plugins that have been ported are sufficient for what you need is an open question, but it cuts out the issue of Wine entirely.

[Busty]

thanks qyot27 for pointing that out, a native mac version looks interesting. I'll see if my setup works according to my needs and if not, I might try to compile. I'm still making up my mind about which tools I want to throw at my captures. I might come up with some things doing in virtualdub directly.

Keep up the good work!