AVISynth on Linux?

[DrPhill]

Forgive me if this is a dumb question, but......

Does AVISynth work on Linux (Mint specifically). I have migrated from windows, but was unsure if it was worth attempting the download/install at all.

Any help gratefully received

Phill

[Firebird]

http://forum.doom9.org/showthread.php?t=164386

[Yellow_]

That's AvxSynth not Avisynth, plugin functionality and audio is not the same between the two. :-)

DrPhill, avisynth works great with Wine, you'll probably be better off with the windows version for the present time, plugins compatibility wise especially any funky 16bit stuff.

[DrPhill]

Thank you both for quick responses.

It is yes and no then.......

AvxSynth sounds like a longer term thing. Shame that.

Wine it is, I guess, for the time being. I have not used Wine in anger yet so that is something new to learn about.

Anyone here used AVISynth in Wine? Any problems, gotchas, hints, or advice?

Thanks

[TheFluff]

don't use directshowsource, not sure if avisource works now or not (ffms2 is known to work reliably though)

[Yellow_]

Anyone here used AVISynth in Wine? Any problems, gotchas, hints, or advice?

Thanks

On Linux, all the time and for the last 8 years. :-)

Personally I prefer avspmod to virtualdub for avisynth script access and avs2pipemod for command line use. Again all run with wine.

don't use directshowsource, not sure if avisource works now or not (ffms2 is known to work reliably though)

On the occasions I've had to use AVISource, pretty sure it's ok, but majority is ffms2. :-)

[DrPhill]

That seems convincing then - Wine it is. Thanks.

I am running a 64 bit system - shoulld I run the official 32-bit v.2.5.8 ST or the unnofficial v.2.5.8 MT, 64-bit, author SET, compiled by JoshyD?

I am happy with AVSPmod - that is what I was using before the change.

I have been using MPEG2Source, is ffms2 a better/simpler option? If so where do I find some more info.

Thanks

[TheFluff]

use 32-bit single threaded, 64-bit and/or MT are unstable enough on windows, god knows how they behave on Linux.

mpeg2source is better than ffms2 if it's only mpeg2 (in mpeg ts/ps) you want to load.

[Yellow_]

Personally I use the 32bit 2.5 non MT version, even though I'm running 64bit Ubuntu, if downloading Avisynth from sourceforge do make sure it's 2.5 from 2010.

I've seen the 'download latest 2.5.8' link even under the 2.5 page, which is/was 2.6 alpha and it'll cause headaches, especially if one thinks they're running 2.5 :-)

Sourceforge setup is a freaking mess. So ensure you have tooltips on in your browser and check out the download path!

There's an AVSPmod thread here on Doom9 with latest builds in case you're running an old version as under Wine you'll get no video preview with versions prior to about 2.2.0.

Also with AVSPmod you'll need to get into Options and untick all options under 'Text' tab, except Syntax Highlighting and untick all under 'Autocomplete' tab. You'll get a crash and wipeout if deleting closing brackets from a line in a script if you don't disable autocomplete etc.

Choice of FFMS2 or MPEG2Source will be dependant on formats you're trying to decode. FFMS2 offers more choice. But interlaced h264 is a problem for ffmpeg still I think.

Also make sure if using FFMS2, to set threads to 1. ie: FFmpegSource2("myfile", threads=1) especially with HDV and h264.

I used to use MPEG2Source but it didn't automate well for batching from memory due to creating the D2V files. But it was accurate with the HV30 mpeg2 HDV sources I tried.

I use FFMS2 latest version (as most of my stuff is h264 progressive) from the FFMS2 Google site or via TheFluff's sig. I'd suggest using a recent build from the FFMS2 thread here on Doom9.

There's also Vampiredom's script which works well for everything except the progressive DSLR h264. DGAVCDecode, or whatever it's called, the free version non NV GPU accellerated version doesn't like it.

Cross Post with TheFluff.

re MT, I saw no improvement with the MT version, what i do find with multicore processors is that the 2.5 vanilla version works across all cores well, I guess this is typical behavior on Windows but Linux works well.

[DrPhill]

Thank you both for that info. You have probably saved me some headaches.... I get confused enough trying to edit video without having to work out if it is me, thee operating system or the version of the software.

I am going to be doing a two-step process:
(1) merge a JPG and an MPG from my camera and create an intermediate file
(2) combine several intermediate files (mainly dissolve) into a full length video and mix in audio (mp3).

The intermediate file format was previously m2v from HCEnc but I am agnostic on this - any better ideas?

I seem to recall that HCEnc does not do audio. I have a MKV video with audio added. I am ashamed to say that I have forgotten how I did that. Can anyone jog my memory.

[Yellow_]

I really like HCEnc and it works great on Linux via Wine with an avs script. :-)

For creating mkv's mkvmergeGUI is available for Linux, I use it on occasions and it's available via bunkus's PPA (if on Ubuntu or download otherwise) which is at:

http://www.bunkus.org/videotools/mkvtoolnix/downloads.html

[DrPhill]

Thanks for that reassurance.

For the MKV tools can I assume that you mean
x86_64 Extra mkvtoolnix-gtk 5.6.0-1 Set of tools to create, edit and inspect Matroska files - wxGTK GUI 2012-05-27
(I am running a 64 bit intel based system).

from here (http://www.archlinux.org/packages/?sort=&q=mkv&maintainer=&last_update=&flagged=&limit=50)?

Does mixing the 64 bit and 32 bit stuff work? I guess that if they do not need to talk to each other directly it is all fine. Anyway, producing the silent video is the first task. Grafting the sound on will happen last.

Thanks

[DrPhill]

OK,

Installed AviSynth 2.5.8 under Wine. Seems to have worked fine. How do I test that? I have some scripts but they need to be called by video program..... Do I need to install WMP in wine? I tried by Microsoft could not validate my version of Windows (no big surprise there....:p)

Installed AvsPmod - but I get errors on start up and I have no clue what to do now.... any hints?
Traceback (most recent call last):
File "run.py", line 5, in <module>
File "AvsP.pyo", line 73, in <module>
File "pyavs.pyo", line 31, in <module>
File "avisynth.pyo", line 4, in <module>
File "ctypes\__init__.pyo", line 415, in __getattr__
File "ctypes\__init__.pyo", line 340, in __init__
WindowsError: [Error 1114] DLL init failed

My guess is that this is a Wine specific thing that I do not understand.

[Yellow_]

I've had it running for so long, forgot what's required :-) however it could be needing a Windows runtime library or something.

Try installing the C++ redistributable package:

http://www.microsoft.com/en-us/download/details.aspx?id=5555

For testing AVISynth you could open an .avs file with Virtualdub http://www.virtualdub.org/download.html or even a windows binary of ffplay part of a Windows ffmpeg install available here, http://ffmpeg.zeranoe.com/builds/ as long as it was compiled with avs support.

Or you can process .avs scripts with Avs2yuv http://akuvian.org/src/avisynth/avs2yuv/ and Avs2pipemod http://forum.doom9.org/showthread.php?t=160383&page=6 on the CLI serving to Windows binaries of x264 http://x264.nl/ or ffmpeg etc, both avs2yuv & avs2pipemod also allow possibility of 10 & 16bit data out of Avisynth to x264 10bit build and Imagemagick 16bit image formats, http://forum.doom9.org/showthread.php?p=1386559#post1386559, but one step at a time. :-)

[DrPhill]

I've had it running for so long, forgot what's required :-) however it could be needing a Windows runtime library or something.

Try installing the C++ redistributable package:

http://www.microsoft.com/en-us/download/details.aspx?id=5555

For testing AVISynth you could open an .avs file with Virtualdub http://www.virtualdub.org/download.html or even a windows binary of ffplay part of a Windows ffmpeg install available here, http://ffmpeg.zeranoe.com/builds/ as long as it was compiled with avs support.

Or you can process .avs scripts with Avs2yuv http://akuvian.org/src/avisynth/avs2yuv/ and Avs2pipemod http://forum.doom9.org/showthread.php?t=160383&page=6 on the CLI serving to Windows binaries of x264 http://x264.nl/ or ffmpeg etc, both avs2yuv & avs2pipemod also allow possibility of 10 & 16bit data out of Avisynth to x264 10bit build and Imagemagick 16bit image formats, http://forum.doom9.org/showthread.php?p=1386559#post1386559, but one step at a time. :-)

Excellent advice. I will sit down after the dog walk and work my way through that. I spent an hour or so lookking around the we but found nothing so you advice is very welcome.

I am new to Linux (Mint 13/Mate), and not very experienced in the world of video editing so it all seems very confusing.

I will let you know how I get on.

[Yellow_]

No problem, btw I don't think that there's much over what you'd have to install on windows to get it all up and running apart from Wine and I've found that certain odd .dlls might need copying into your /home/name/.wine/can'trememberfullpath/system32 sub folder. :-)

[DrPhill]

No problem, btw I don't think that there's much over what you'd have to install on windows to get it all up and running apart from Wine and I've found that certain odd .dlls might need copying into your /home/name/.wine/can'trememberfullpath/system32 sub folder. :-)

OK here is the state of play.

VirtualDub runs, and will load an mpg without complaint, but throws an error loading an AVS file:- AVI Import Filter error: (Unknown)(80040154)

(The AVS file contains only a version() command).

I have installed the VC runtime but that made no difference.

Where is the meat of AviSynth? Should I have a AViSynth.dll somewhere? What should I be looking for? I cannot find it..... maybe running the setup in wine does not work as it should? I could not find any sign of a vc*.dll either.

(I am looking in the Wine C drive ;-)

[Yellow_]

hi, Wine's C drive is a hidden folder, in Linux it's hidden simply by having a '.' dot in front of a folder name, so in your file manager nautilus in Gnome or Dolphin on KDE, you need to choose view, show hidden files and folders.

This will then show the .wine folder in your /home/... folder.

In there will be the typical Windows C:\ etc including Program Files folder. In there a Avisynth 2.5.

Make sure that the avisynth.dll is in the windows/system32 folder under that .wine path.

There will also be a Wine menu item on your Desktop 'Applications' start bar thing, :-) again depending on whether you're running KDE or Gnome.

[DrPhill]

hi, Wine's C drive is a hidden folder, in Linux it's hidden simply by having a '.' dot in front of a folder name, so in your file manager nautilus in Gnome or Dolphin on KDE, you need to choose view, show hidden files and folders.

This will then show the .wine folder in your /home/... folder.

In there will be the typical Windows C:\ etc including Program Files folder. In there a Avisynth 2.5.

Make sure that the avisynth.dll is in the windows/system32 folder under that .wine path.

There will also be a Wine menu item on your Desktop 'Applications' start bar thing, :-) again depending on whether you're running KDE or Gnome.

Thanks - I had figured out the C drive thing, but you were not to know so it was well worth mentioning.

The system32 has no avisynth.dll. I rather suspected that it should, so something went wrong with the install.

I just ran the install again (simply by double-clicking it in the file browser), from an install executable on the C: drive, and the output of the installer does say

Output folder: C:\windows\system32
Extract: avisynth.dll
..........

but it is not there. The C:\Program Files(x86)\AviSynth 2.5 folder is there, so it did that right.

Should I get the dll from somewhere else and insert it manually? If so where (I mean where should I get it not where should I insert it:D). Or is one error with the install enough to throw doubt on the whole enterprise?

[StainlessS]

Perhaps nothing to do with your problem but, if you're trying to install v2.6,
I seem to recall that either alpha 1 or alpha 2 required that v2.58 needed
install first, then install v2.6 worked ok. Check that you have alpha 3 if
installing 2.6.

[Yellow_]

Yes, manually copy the avisynth.dll into system32, unfortuneatly not at my Linux boxes to check all the files, from memory there maybe a couple of others. :-)

[DrPhill]

Yes, manually copy the avisynth.dll into system32, unfortuneatly not at my Linux boxes to check all the files, from memory there maybe a couple of others. :-)

OK, but where do I get an avisynthdll? Anyone got one for me to download? Or someone prepared to email me one? Or can I extract it from the install file?

[Yellow_]

The .dll should be in the .wine Program Files Avisynth 2.5 folder. :-)

If it's not then I'd assume as per Stainless's comment that you may be using 2.6?

A few posts up I described the mess on Avisynths sourceforge site. :-)

[DrPhill]

I think I used the download:
http://sourceforge.net/projects/avisynth2/files/AviSynth%202.5/AviSynth%202.5.8/Avisynth_258.exe/download

But I am trying again.... nope, no avisynth.dll anywhere. I even tried 257, but got the same results. Could my wine be broken?

I just installed the 258 on an old windoze machine, and copied the dll to the unix maachine (wine c drive, system32). No difference - still broken. Hmmmm

Any some bright ideas anyone?

[StainlessS]

You could perhaps try copying the code below into a file called "Avisynth.reg" and execute it.


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}]
@="AviSynth"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\InProcServer32]
@="AviSynth.dll"
"ThreadingModel"="Apartment"


Adds an entry to the registry. EDIT: May require a logoff/logon.

EDIT: v2.6 currently also uses the AviSynth 2.5 folder.

[Yellow_]

DrPhill, I tried the link you gave and it installed avisynth.dll to /home/mymachine/.wine/drive_c/windows/system32 and the .dll is dated 21.12.2008 so no doubt it's 2.5 not 2.6

The installation took a minute or two and the final entry in the avisynth install dialogue was 'Completed', light blue text on black. Do you get that far?

You can get a Wine console up to check that works by doing wineconsole cmd in a Linux Terminal. Also can get the wine configuration up with winecfg from a Linux Terminal. Just to see if Wine appears successfully installed. But if Virtualdub is working then assume it is. :-)

[DrPhill]

You could perhaps try copying the code below into a file called "Avisynth.reg" and execute it.


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}]
@="AviSynth"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\InProcServer32]
@="AviSynth.dll"
"ThreadingModel"="Apartment"


Adds an entry to the registry. EDIT: May require a logoff/logon.

EDIT: v2.6 currently also uses the AviSynth 2.5 folder.

I tried this.
Created the file in the root of my wine C drive.
I made it executable (changed permissions).
double clicked it (not a lot happened - not sure what I should see)
logged off
logged on
Still got the same problems.

I may have done something wrong through ignorance.

They used to love me in system test. I can break anything just by following the instructions.

EDIT:
Just tried to run it in a console - got this
bash: /usr/bin/mint-fortune: No such file or directory
phill@phill-xps ~/.wine/drive_c $ avisynth.reg
avisynth.reg: command not found
phill@phill-xps ~/.wine/drive_c $ ./avisynth.reg
./avisynth.reg: line 1: Windows: command not found
./avisynth.reg: line 3: [HKEY_CLASSES_ROOTCLSID{E6D6B700-124D-11D4-86F3-DB80AFD98778}]: command not found
./avisynth.reg: line 4: @=AviSynth: command not found
./avisynth.reg: line 6: [HKEY_CLASSES_ROOTCLSID{E6D6B700-124D-11D4-86F3-DB80AFD98778}InProcServer32]: command not found
./avisynth.reg: line 7: @=AviSynth.dll: command not found
./avisynth.reg: line 8: ThreadingModel=Apartment: command not found
phill@phill-xps ~/.wine/drive_c $


I tried to run it in a wine console and got 'file not found'.

I checked the registry, though, and those values are already set correctly.

[DrPhill]

DrPhill, I tried the link you gave and it installed avisynth.dll to /home/mymachine/.wine/drive_c/windows/system32 and the .dll is dated 21.12.2008 so no doubt it's 2.5 not 2.6

The installation took a minute or two and the final entry in the avisynth install dialogue was 'Completed', light blue text on black. Do you get that far?

You can get a Wine console up to check that works by doing wineconsole cmd in a Linux Terminal. Also can get the wine configuration up with winecfg from a Linux Terminal. Just to see if Wine appears successfully installed. But if Virtualdub is working then assume it is. :-)

The installation dialog claimed it had been successful - I did not check the last lines, but the very first lines indicated a successful extract of avisynth.dll to system32.

Odd, very odd.

I will try again tomorrow as I am getting a little fatigued now - I will make mistakes and get confused more easily.

To recap:
- I now have the correct avisynth.dll in the system32 directory
- I have the correct registry entries (are there more?)

I think I have installed the VC++ runtimes, but how can I check? If I try to install them again I get a different dialogue - repair or remove - so I assume the installer thinks that it has already been successful.

[Yellow_]

That's great, progress. :-) Hopefully all will go well tomorrow.

re. registry. I've never had to add registry entries manually for running windows apps on Linux via Wine.

That's not to say they're not necessary to smooth the way, just never had to.

[StainlessS]

These are also present in registry (Check if they already exist)


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\AviSynth]
"plugindir2_5"="C:\\Program Files\\AviSynth 2.5\\plugins"

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="C:\\Program Files\\AviSynth 2.5"
"plugindir2_5"="C:\\Program Files\\AviSynth 2.5\\plugins"


By the way, the regedit program is auto executed on executing a .reg file (under windows),
but you can also select 'import' on the file menu in Regedit and import the .reg file.

The only other reg entries (that I think are not connected to other programs using Avisynth)
are concerned with the default icon to display for an Avisynth file, dont think they should
be terribly important (would display a system default icon instead).

The "Repair/remove" dialog would suggest that VC++ runtimes are indeed installed.
(Trust you are trying to install VC++ 6.0 version runtimes [for 2.58] and not later ones)

Cant myself think of anything else that could assist. Good luck :)

EDIT: The previously mentioned problem with 2.6 alpha1/alpha2 was I think down to the
one or both of the given registry entries being missing from the setup file, so required 2.58
install to set those entries.

[StainlessS]

The below is taken from "AviSynth_Template.reg" in the v2.58 source:


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}]
@="AviSynth"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\InProcServer32]
@="%INSTALLDIR%\AviSynth.dll"
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Media Type\Extensions\.avs]
@=""
"Source Filter"="{D3588AB0-0781-11CE-B03A-0020AF0BA770}"

[HKEY_CLASSES_ROOT\.avs]
@="avsfile"

[HKEY_CLASSES_ROOT\avsfile]
@="AviSynth Script"

[HKEY_CLASSES_ROOT\avsfile\DefaultIcon]
@="%INSTALLDIR%\AviSynth.dll,0"

[HKEY_CLASSES_ROOT\.avsi]
@="avs_auto_file"

[HKEY_CLASSES_ROOT\avs_auto_file]
@="AviSynth Autoload Script"

[HKEY_CLASSES_ROOT\avs_auto_file\DefaultIcon]
@="%INSTALLDIR%\AviSynth.dll,0"

[HKEY_CLASSES_ROOT\AVIFile\Extensions\AVS]
@="{E6D6B700-124D-11D4-86F3-DB80AFD98778}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth]
@="%INSTALLDIR%"
"plugindir2_5"="%INSTALLDIR%\plugins"


It is this file that would have been missing in the previously mentioned 2.6 alpha 1/2 version
(or a command to install it).

EDIT: the "%INSTALLDIR% entries in the .reg file must usually be replaced by eg "C:\WINDOWS\system32"
by whatever installs the .reg file.

EDIT: Below is contents of registry on my machine with the "%INSTALLDIR% stuff filled in
(have re-imported into my registry, without anything going kerplunk!).

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}]
@="AviSynth"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\InProcServer32]
@="AviSynth.dll"
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Media Type\Extensions\.avs]
@=""
"Source Filter"="{D3588AB0-0781-11CE-B03A-0020AF0BA770}"

[HKEY_CLASSES_ROOT\.avs]
@="avsfile"

[HKEY_CLASSES_ROOT\.avs\ShellNew]
"NullFile"=""

[HKEY_CLASSES_ROOT\avsfile]
@="AviSynth Script"

[HKEY_CLASSES_ROOT\avsfile\DefaultIcon]
@="C:\\WINDOWS\\system32\\AviSynth.dll,0"

[HKEY_CLASSES_ROOT\avsfile\Shell]

[HKEY_CLASSES_ROOT\avsfile\Shell\Open]

[HKEY_CLASSES_ROOT\avsfile\Shell\Open\Command]
@="notepad.exe \"%1\""

[HKEY_CLASSES_ROOT\avsfile\Shell\play]

[HKEY_CLASSES_ROOT\avsfile\Shell\play\command]
@="\"C:\\Program Files\\Windows Media Player\\mplayer2.exe\" /Play \"%L\""

[HKEY_CLASSES_ROOT\avsfile\ShellNew]
"NullFile"=""

[HKEY_CLASSES_ROOT\.avsi]
@="avs_auto_file"

[HKEY_CLASSES_ROOT\avs_auto_file]
@="AviSynth Autoload Script"

[HKEY_CLASSES_ROOT\avs_auto_file\DefaultIcon]
@="C:\\WINDOWS\\system32\\AviSynth.dll,0"

[HKEY_CLASSES_ROOT\avs_auto_file\shell]

[HKEY_CLASSES_ROOT\avs_auto_file\shell\open]

[HKEY_CLASSES_ROOT\avs_auto_file\shell\open\command]
@="notepad.exe \"%1\""

[HKEY_CLASSES_ROOT\AVIFile\Extensions\AVS]
@="{E6D6B700-124D-11D4-86F3-DB80AFD98778}"

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="C:\\Program Files\\AviSynth 2.5"
"plugindir2_5"="C:\\Program Files\\AviSynth 2.5\\plugins"

[DrPhill]

No luck with those - not even the full set of registry changes.

I even removed wine completely (including the .wine directory) and reinstalled. I got the same results. Very frustrating.

I am now at a loss as to what to try.

(Apart from rewriting AviSynth in Java.... :P)

[Yellow_]

StainlessS mentioned getting the right Windows C runtime, The "Repair/remove" dialog would suggest that VC++ runtimes are indeed installed. (Trust you are trying to install VC++ 6.0 version runtimes [for 2.58] and not later ones)


The link I gave maybe too new.

I wasn't aware runtime version wasn't a cumulative thing, ie: a newer runtime would allow older applications to work as well.

So perhaps install this, I know I have in years past and it's been needed for certain windows apps on Linux:

http://www.microsoft.com/en-us/download/details.aspx?id=3387

http://support.microsoft.com/kb/259403

The runtime link I gave previously was for the 2010 version.

[DrPhill]

I hear what you say about the C runtime, but I wonder if there is something more fundamentally wrong with my setup. Why does the install not copy avisynth.dll to the correcct location?

Is this a process which requires the C runtime library? If so that would explain it, but I am not sure at all that this is the case. I wonder if my combination of software (Mint/Mate/Wine) has a 'defect'?

For sure I will:
(1) run the install
(2) copy in the avisynth.dll
(3) import the registry entries
(4) install the C runtimes

And test with VirtualDub.

But I am getting less optimistic.

[DrPhill]

I hear what you say about the C runtime, but I wonder if there is something more fundamentally wrong with my setup. Why does the install not copy avisynth.dll to the correcct location?

Is this a process which requires the C runtime library? If so that would explain it, but I am not sure at all that this is the case. I wonder if my combination of software (Mint/Mate/Wine) has a 'defect'?

For sure I will:
(1) run the install
(2) copy in the avisynth.dll
(3) import the registry entries
(4) install the C runtimes

And test with VirtualDub.

But I am getting less optimistic.

Done that, no change.

Is it possibly a probem with VirtualDub? Is there another simple easy way to check if AVISynth is working?

[StainlessS]

Suggest with a working Wine setup, install CPP runtimes first, they could well be the
reason the setup program is also failing.
I have c++ runtimes for 2005, 2008 & 2010, dont know where the one for C++ v6.0
from Visual Studio v6.0/98 is. They tend to all use the same file name which could well
be (nay, is) very confusing (vcredist.exe or something similarish) and are not
cumulative thing, ie: a newer runtime would allow older applications to work as well.


Had a look at the links given by Yellow_, the 1st one is for Visual C++ 2005 (v8 I think), ie the wrong one
(I also had a look at v2.6 source and looks to me like it also still compiles with Visual C++ v6 (98)
so would also need same runtimes [EDIT: Yes vc++v6.0]).
The second link is the correct one. As it says in 2nd link, the runtimes are now included in the
vc++ service pack, thats why I dont have them as a separate file, but are available in 2nd link
for download on systems without the compiler.
Not such a bad idea to also install runtimes for 2005, 2008 and 2010 as some plugins will require
those runtimes too (dont you just love MS).

EDIT: You also get the occasional program that requires vc++ 7.0 runtimes, not sure I think
some versions of eg Nero required it (not sure, think maybe ~2003).

EDIT: I've got a vague feeling that 2010 may require one of the dot net variants to be installed,
perhaps someone could chime in on that (maybe its just the compiler).

[Are_]

Yeah, I know it should work the other way around, but trying to replicate your problem this is the only way I was able to run avisynth:

1. Install whatever version of avisynth you want.
2. Copy Avisynth 2.6 MT (http://www.mediafire.com/file/20gn1c2s45la14w/avisynth.7z) dll in system32 folder.
3. It works for me :/

[DrPhill]

Aaaaah at last success.

First, thank you Stainless and Yellow for your patient support. I would never have perservered if it had not been for your investment in time.

In the end what I did was:

(1) Remove my wine directory (actually I renamed it out of harms way)
(2) Run ConfigureWine to create a fresh directory
(3) Download and install the VC6 redistributables from: http://support.microsoft.com/kb/259403
(4) Run AviSynth258 installer
(5) Copy avisynth.dll into system32 directory (it was not installed to there)
(6) And I still needed to import the registry stuff using regedit.

However - I can now run the test.avs (it only has one command - a call to version(), but that is a major step forward.

I will update this thread when I achieve a bit more (or hit another snag as the case may be.....).

Again, immense gratitude for the help.

(Oh, and I have learnt a lot about Wine too..... neccesity is a mother alright).

Phill

[StainlessS]

Good show old chap. Glad you got it sorted, but for selfish reasons. Will now know
what thread to look for when I eventually abandon MS. :devil:

One last thing which may or may not come in handy one day,
If you want to eg delete a registry key (perhaps accidently added and causing problems) eg


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="C:\\Pogrom Files\\AviSynth 2.5"
"plugindir2_5"="C:\\Pogrom Files\\AviSynth 2.5\\plugins"

[If you confused your Pogrom and Program files directories :) ]

then this (in a .reg file) would delete the key (and contents)


Windows Registry Editor Version 5.00

; This is a comment

[-HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]

Note the hyphen.

Good luck.

[Yellow_]

DrPhill, excellent. :-)

[DrPhill]

Good show old chap. Glad you got it sorted, but for selfish reasons. Will now know
what thread to look for when I eventually abandon MS. :devil:

FWIW abandoning windoze for Linux Mint was no harder than going from xp to w7. Upgrading from Mint 12 to Mint 13 was a doddle compared to xp -> w7. Now I am starting to get to know Linux I am feeling more in control of my system than ever I did under MSware.
This was the first real problem that I have had, if you discount the mess caused by me 'tidying up my boot menu'. doh!

DrPhill, excellent. :-) Yes, 'tis good, but I cannot take the credit...

Now to actually use AviSynth.