View Full Version : Can't open video file via AVISynth
bozitaai
7th January 2005, 08:36
VirtualDubMod version 1.5.4.1 was installed. When opened simple version.avs,
the script looks like this:
Version()
this error message was shown,
"Avisynth open failure:
Avisynth: script open failed!"
anyone know how to fix this problem? thank you!
rfmmars
8th January 2005, 18:55
Works fine for me.
What editor did you create it in? I used Notepad
richard
photorecall.net
Wilbert
9th January 2005, 00:30
I never have seen that message.
Does emptying AviSynth plugin dir help? What AviSynth version did you install?
Cyberia
9th January 2005, 23:58
Make sure you aren't saving the script in Unicode.
I can't tell you how many times I have cut-and-pasted scripts from web pages (AviSynth's own help pages) directly into Notepad and they won't play. You may need to explicitly save the file as ANSI.
...
I would like to take this opportunity to (again) protest the Version() function of AviSynth. Firstly, Version() generates an error when played by WMP. And second, why does version have to produce an actual video clip, rather than just generating a message like the other functions?
Wilbert
10th January 2005, 00:29
I would like to take this opportunity to (again) protest the Version() function of AviSynth.
Are you joking here?
Firstly, Version() generates an error when played by WMP.
Do you also get an error?
And second, why does version have to produce an actual video clip, rather than just generating a message like the other functions?
Why not? It's also a way to check that AviSynth is correctly installed, because it plays a clip.
Cyberia
10th January 2005, 02:05
I'm not joking. The version function has NEVER worked in WMP.
Cyberia
10th January 2005, 02:10
Originally posted by Wilbert
Why not? It's also a way to check that AviSynth is correctly installed, because it plays a clip. It just looks shoddy. IMHO, all messages (including version) should be consistent. Either use text for both or clips for both, don't mix and match.
Wilbert
10th January 2005, 09:52
I'm not joking. The version function has NEVER worked in WMP.
What version of WMP are you using? The version function is not working, but avi and d2v files open fine?
Does it work in WMP6.4 and Vdub?
It just looks shoddy. IMHO, all messages (including version) should be consistent. Either use text for both or clips for both, don't mix and match.
All other messages are error messages. They can't be returned as clips, and besides it's not very convenient when you want to encode something (cause it will encode that error message if it's a clip).
edit: reading Stickboy's post below and the thread he mentioned, it seems I completely misunderstood what you meant by messages. I have nothing further to add though.
stickboy
10th January 2005, 10:01
Originally posted by Cyberia:
And second, why does version have to produce an actual video clip, rather than just generating a message like the other functions?So exactly what you prefer Version() do? What do you mean "generating a message"? Do you mean "return a string"? You are aware of VersionString(), yes?
Or do you mean "display a dialog box"? That's not an option; AviSynth doesn't generate dialog boxes. AviSynth throws exceptions for script errors, and it is the host application's responsibility to do something with it. (And displaying a version string isn't an "error".) But if you really wanted, I suppose you could do:
Assert(false, VersionString())
The whole point of Version() is for someone to be able to determine the AviSynth version number easily. Hence it generates a clip.
Good gravy, if you don't like Version(), just don't use it.
Edit:
Okay, I found your previous complaint about Version (http://forum.doom9.org/showthread.php?s=&threadid=78365), which I replied to before.
So I assume by "generating a message" you really mean "overlaying a string onto an existing video clip" (like Info(), ShowFrameNumber(), etc.). (And IMO any inconsistency is entirely warranted. Info() and ShowFrameNumber() show properties of an existing clip, so clearly they require an input clip. Version does not, and why should it? Should people be forced to create a clip just to determine the AviSynth version?)
But really, why not just use Subtitle? If you really don't like it:
function MyVersion(clip c)
{
return c.Subtitle(VersionString())
}
Cyberia
11th January 2005, 02:27
I didn't intend to aggitate anyone. Hopefully I didn't.
As I indicated, it's my opinion that Version() doesn't look good. It's just a cosmetic suggestion. Now, onto the actual problem with version not working...
I tested it earlier today on my WinXP 2Ghz Intel box at work. The version() function worked fine. I was shocked. WMP 10 and 6.4 work.
At home, I retested my XP 3200 Athlon it does NOT always work. WMP 10 does NOT work, WMP 6.4 DOES work. I believe it has not worked for several versions of WMP. This is the error returned:Windows Media Player cannot play the file. The Player might
not support the file type or might not support the codec that
was used to compress the file. But my home box plays all other avs scripts fine!
I even uninstalled AviSynth and re-installed it.
Version() worked in both machine with VDub, and Version() generated the same graph on both boxes.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.