all avs files broken after format

[Vivaldi]

(Windows XP SP3 32bit)

I recently reformatted my computer (for a variaty of reasons) and as a result, also had to reinstall avisynth and all it's relevant plugins. My problem is that since then, all my old and new avs files (kept on an external) have become unusable. Particularly the problem seems to be stemming from directshowsource and ffmpegsource2. With Directshowsource I get the error:

Code: Select all

video returned: "Directshowsource: couldn't open file "file path": The device is not ready.

And it repeats that message for the audio, I have reinstalled CCCP and Haali media splitter but it doesn't seem to make a difference.

For FFmpegsource2: the error is:

Code: Select all

Avisynth open failure:
FFIndex: Can't open "file path"
(ffms2.avsi, line 22)
("File.avs, line 1)

Any ideas what the problem could be? This is happening across all avs files, new and old, so it's not just a scripting error, and it's getting pretty annoying to not be able to use avisynth at all.

Many thanks for helping me with my problem.

[Qyot27]

Perhaps the most obvious question, but did you make sure the files you're trying to open are where the scripts are looking for them? Drive letter assignment is apt to change sometimes upon reformatting, and it can screw with the scripts if you used absolute paths (i.e. C:\Program Files\YADDAYADDAYADDA and so forth). AviSynth is perfectly fine with relative paths (i.e. just the filename itself), so long as the script and file reside in the same folder.

That's what both errors read like to me, although the 'The device is not ready' error from DirectShowSource looks odd.

[Mister Hatt]

The source plugins are not your problem, they are just first in the load chain and so they error before everything else does. Your scripts are using absolute paths as Qyot said; you'll need to fix the paths or change them to relative. Note that relative doesn't require being in the same directory, you can use ..\ to access a higher level.

[Vivaldi]

Indeed, it seems it was simply a case of my directories ordering having changed. Thanks for helping with such a simple problem.