Can't run apptests successfully

[Shiroferetto]

2 significant points to make.

1) WMP is an inferior media player.
2) You shouldn't be using a media player to see if things are working correctly. If you're converting to lossless to edit with, you're not going to be able to play the files back correctly anyway.

Hi,

Agreed re: MP.

Re: using it to test, I'm following the tutorial recommended on this Forum. It shows newbies how to make some basic AVS files and instructs the student to test them in MP to see how AviSynth works. Since it doesn't work, I'm learning with DivX instead

Piglet's right: The Guide (Beta, at least) recommends testing AVS scripts in WMP to see if they work. Recommend this be changed if WMP is considered inferior.

Important note: I did actually get WMP 11 to run the tutorial .avs by downloading the VERY LATEST version of Avisynth from Sourceforge. The date of the release is 6-22-08. (It doesn't get much more up-to-date than that).

Note that the 6-22 release is an alpha version. It did, however, correct the problem I was having with running the tutorial.

Now if only I could get .avs to load easily in VirtualDubMod... The tutorial /says/ you can just load those suckers using the pull-down menu, but alas the reality is somewhat different. Typing in the full path name seems to do the trick, even if it's a pain.

IMO, the Guide is in need of updating for those of us running Windows Vista (32) and/or Vista (64). Just about anyone with dual/quad-core machines is going to be running Vista. My dual-core machine is 1.5 years old, but the guide doesn't really address any of the technical issues associated with the newest releases of both commercial and open-source software, even the error messages that one gets when installing Avisynth from the AMVapps.

Again, as in the other thread: I hope this is taken as constructive criticism. Obviously, the Guide and AMVapps are still monumentally helpful to newbs like me. There are just a few sticking points that need to be addressed.

(Well, the warning DOES say it's a beta version...)

[BasharOfTheAges]

Piglet's right: The Guide (Beta, at least) recommends testing AVS scripts in WMP to see if they work. Recommend this be changed if WMP is considered inferior.

WMP 6.4 (mplayer2) is far different than the WMP series after that point. Media Player Classic is essentially the same design, upgraded and is what I'd recommend.

IMO, the Guide is in need of updating for those of us running Windows Vista (32) and/or Vista (64). Just about anyone with dual/quad-core machines is going to be running Vista. My dual-core machine is 1.5 years old, but the guide doesn't really address any of the technical issues associated with the newest releases of both commercial and open-source software, even the error messages that one gets when installing Avisynth from the AMVapps.

The tests are known not to work with Vista. If you would like to help with portions of the guide for Vista, that's all well and good, but the individual re-writing the guides (and many other tech-savvy individuals) will not touch Vista with a 10 foot pole. Personally, I run XP x64 and will never let that PoS OS anywhere near my computer.

[LivingFlame]

Now if only I could get .avs to load easily in VirtualDubMod... The tutorial /says/ you can just load those suckers using the pull-down menu, but alas the reality is somewhat different. Typing in the full path name seems to do the trick, even if it's a pain.

Is the pull down menu you're talking about that "Open with AviSynth Template" (or whatever the actual text is) in the Open dialogue box? If that is the pull down menu you're talking about, then that isn't used to open an .avs file. That menu is for automatically creating an .avs script for another media file. To open an .avs file, just navigate to it and click open. No need for the .avs template (since that would essentially just try to create a script to call a script...which will fail).

IMO, the Guide is in need of updating for those of us running Windows Vista (32) and/or Vista (64). Just about anyone with dual/quad-core machines is going to be running Vista. My dual-core machine is 1.5 years old, but the guide doesn't really address any of the technical issues associated with the newest releases of both commercial and open-source software, even the error messages that one gets when installing Avisynth from the AMVapps

I can see where it would be nice to have some Vista-specific stuff in the guide, but I also completely understand what Bashar is saying. Vista sucks. I wouldn't touch at all, regardless of the specs of my comp. (Hell, we have a octo-core machine with 16 gigs of RAM at work, and we still won't touch Vista (it runs XP x64). Vista just plain sucks; it's one of those things that should have never been created. Hence Microsoft is already working on a new OS.)

[Shiroferetto]

Yes, yes. Vista sucks. Been there, heard that, got the teeshirt already.

Be that as it may... I'm still sticking with it. I ain't even gettin' into that argument.