AviSynth 2.5.2 and ffvfw light it tries to install

[dream-lx]

Hi,

I have installed AviSynth 2.5.2 and the ffvfw light version included. After installation I tried running the included makeAVIS which simple hangs. After that I had started Internet Explorer which hangs after a few clicks. I then decided to reboot, but the PC hangs during reboot. Then I did a restore from backup (which luckily I did a few hours before... normally when I need to restore, I have no recent backup:)) and tried to install AviSynth 2.5.2 without ffvfw light. Then everything works ok. For the case it matters, I have some Xvid version installed on my system. Did anyone have similiar problems ?

Thanks in advance

Bye,
David

[sh0dan]

What OS are you using?

Has anyone expeienced anything just slightly similar?

[dream-lx]

Hi,

I am using Windows XP Professional Service Pack 1.

Bye,
David

[DDogg]

Windows XP Professional Service Pack 1 here with no problems so far.

[sh0dan]

I also personally use ffvfw on XP SP1 and 2000, latest SP without any problems.

[dream-lx]

Do you also have Xvid installed, not that twice a codec for the same thing will cause problems ?

[digitalman]

I installed the FFVFW with 2.51 beta 3 and it crashed Ulead DVD Workshop when opening it. Windows was reporting ffvfw.dll was causing the problem. I uninstalled it and I no longer had any issues opening Workshop.

[Defiler]

Also, why does ffvfw grey out the Quantizer settings for 2pass1? It's important to be able to adjust them when using a custom quantizer matrix.

[sh0dan]

This is a light version - I'd suggest you use the full package for encoding using ffvfw.

Even though I don't like putting more strain on milan's shoulder, you should probably involve him in your problems - as he is the only one who knows the solution for these problems.

[Defiler]

k. I just tried ffvfw for the first time today, so I was curious. I never installed it alongside the CVS builds of Avisynth.

[Holomatrix]

Originally posted by sh0dan
What OS are you using?

Has anyone expeienced anything just slightly similar?

Hi, yes I had the same thing happen today on my Win2k system. I installed the whole package and could not get windows to stay stable even booted to safe mode, un-installed AVIsynth but to no avail still no go. I am going to re-image my PC clean and try again without having xvid installed and see what happens WITH ffvfw and WITHOUT.

[Gannjunior]

Hi,
I've had the same problem on XP sp1 and on Server 2k3: the system,after ffvfw light installation,becomes very slow,if I move the mouse,I have the "answer"after 15-20 seconds.I've solved the problem running both systems in safe mode unistalling ffvfw light.After that, systems work perfectly again.

ciao!!!

[sh0dan]

Thank you all for reporting. I have put up a new version of ffvfw on the AviSynth CVS page - would anyone with problems go through the pain and try this one out?

[edguit@r]

Same problem here win win2k Pro SP3.

Installed the full package and crashed my system.

:(

[Holomatrix]

We'll I've rebuilt my system and installed the full package again, no problems so far, I didn't test it with xvid installed since I don't encode to AVI so if I get a chance I'll try it out and see what happens, if that was what happened originally, who knows.

@Gannjunior - are you talking about when you click on the Start button or a Program group, it takes a sec or two to respond? because I get that now.

Maybe I'll download the new ffvfw and un-install the other version and see if my system pickes up.


EDIT: does makeAVI frame serve faster than Link2? ( Sorry to through that one in :) )

[sh0dan]

does makeAVI frame serve faster than Link2?
Compared to the unregistered - yes, definately. Compared to the registered - I don't know. If their colorspace conversions are fairly good they should be close in speed.

[JimBryce]

I installed v2.52 and the ffvfw lite. WinXP SP1. No problems. I've installed every beta build of v2.5 you released w/no problems. I had previoulsy installed ffvfw, but then removed it simply because I didn't need it them. Again, no problems.

If the installation of v2.52 and ffvfw were really causing problems, wouldn't a majority of people have problems, not just a few?

While I'm pretty much of a "newbie" to this kind of stuff, I'm definitely not a "newbie" to system installation, system admin, upgrades and maintenance. In fact, I teach classes in that stuff.

Those having problems after installing v2.52 and ffvfw, probably have something else going on (or off, or installed or not installed) that only needs the install to fall apart completely. I'd look for leftover pieces of previous programs, make sure MS Windowsupdate says you're current, and run a registry utility like jv16's PowerTools. Check video and audio driver versions make sure they're current AND complete.

This kind of repair/troubleshooting I've been doing a long, long time and just because the problem started with the install of v2.52 and ffvfw, it does not mean they caused it! This isn't meant to insult anyone but 10 years of experience in this area with large (+2000 user base) customer bases have proven to me time and time again that those systems were probably on the edge anyway and ANYTHING could have pushed them over!

ps. anyone that feels they need to do a complete system re-install to "fix" their system is probably correct and IF you're going to go to that much detail BE SURE AND DO A CLEAN INSTALL, NOT OVER THE TOP OF WHAT YOU ALREADY HAVE INSTALLED (install to "c:\winnt2" or "c:\windows2")

oops! forgot to mention, those of you using the codec packages with words like "Angel", "Kristal", or "Nimo" in their names (no insult or anything else implied to their creators!) are just asking for problems for a variety of reasons. If you really need the codecs they supply, then I'd suggest you do one of three things: 1) buy the legal packages. [Deleted by moderator: Read rule 6!!!!]

Believe me, life will be much simpler if you do that...

[edguit@r]

Solved my problem! :-)

Logged on Win2k SP3 in safe mode and removed ffvfw. Restarted the system and everything just came back like before.

Thx to all of you guys.

[sh0dan]

No warez/crack discussions are allowed here. Next time strikes will fall!

[Holomatrix]

@JimBryce - not sure what your getting at but I don't think I myself was blaming my mishap to the new AVIsynth installaton but more so a conflict with ffvfw and Xvid or some other codec conflict with my computer. Sorry just had to get that out, I was starting to feel violated when I was reading your post :)

It was about time I cleaned my system :)

[JimBryce]

@Sh0dan: My apologies, I wasn't intending to discuss cracks/warez, rather solutions to problems instead of just problems. Won't mention them again...:)

@Holomatrix: I'm sorry if you feel "violated" that wasn't my intention.:( My intention was exactly what you realised and did!:) You recognized that you had a problem with your system NOT v2.52 and ffvfw and that your system needed cleaning out!

If everyone would do that BEFORE installing new software or at least do it before complaining about new software, there would be far fewer problems that -- again, no insult intended to anyone:D -- take up discussion time that just aren't "real" problems!

(by "real" problems, I mean problems relating to the topic of discussion NOT individual systems and their problems!)

[stevendm]

How do I remove the ffvfw filter? I want to keep the rest of avistnth 2.5.2 installed.

Thanks

[dream-lx]

@JimBryce: How do you manage to install more than one software on your pc when reinstalling a clean windows before an install of every new application and version ?

If I understand your opinion right, there should only exactly the same pc with exactly the same os and exactly the same applications and exactly the same periphials be sold, so there would be no more individual problem, am I right ?

I am a software developer, and I think steps should be taken to solve all problems (even if not occuring for everyone). It can't be that a software will only run on a fresh installed windows. this would be like instead of doing bugfixes, publishing a list of cases not to run into. The developers of avisynth do a really a fantastic job, and I understand that they don't have time to look at any problem, and I'm sure they probably would, if they would have the time to do so. But what I don't understand is why there are people prefering that nothing is said about a problem simply to have one less thread.

JimBryce, please think about it. This should not present any offence against you, it's only my personal opinion.

[JimBryce]

@dream-lx" (and others that didn't understand what I was suggesting) :):

I'm not sure how you got that I wanted all computers the same from what I said but I'll just put it down to not doing a good job of explaining myself and try again! :confused:

First, I'm NOT suggesting that everyone's system, software, peripherals, etc., be the same (that would be incredibly boring :)).

Second, I'm NOT saying that software can only run or be installed on a fresh system (that would be silly :)).

What I said was that "Those having problems after installing v2.52 and ffvfw, probably have something else going on (or off, or installed or not installed) that only needs the install to fall apart completely." By that I'm refering to the incredibly large number of people that do not install or un-install software properly, leaving pieces behind both on the hard drive and in the registry (especially!). It is those "left-behind" pieces that in combination with some new software that cause the system to crash. Developers spend a lot of time trying to fix problems that they don't own!

Additionally what I said was that "anyone that feels they need to do a complete system re-install to fix their system is probably correct and IF you're going to go to that much detail BE SURE AND DO A CLEAN INSTALL, NOT OVER THE TOP OF WHAT YOU ALREADY HAVE INSTALLED ". Re-installing your system software over top of the existing problem system software will rarely fix the problem. Doing it that way you don't get a brand new registry and a lot of the existing files will remain and/or not be over-written. People do it that way so they don't have to re-install all their programs but you just putting yourself into a "pay me now or pay me later" situation regarding your time.

If a problem is specific to some specific software, the problem should show up on all systems that software is installed on or a vast majority of them. If it only shows up on a few systems, then the problem is not in the software! Instead it is in the system it is being installed on!

I've been in the HelpDesk/Network/System Administration business a long time and I've learned their are 3 basic rules or assumptions made by most people:

1) "My system is/was fine until I did..." No matter what, those people believe something else caused their problem, even if they're the ONLY one with the problem.

2) "I don't have time to do all that and I've shortcutted before (or someone else has and told me it was okay) without problems..." These people never have time for anything. They'll be proud of saving 30 minutes right now despite the fact that it will cost them 2 hours at a different time.

3) "I've been working on computers since 18xx and I know how to do it, know that my system is perfect, and can tell when something else is causing problems and IT IS..." With these people you always lose. Nothing they do is their fault and whatever they figure out (eventually) is the only correct solution--the fact that they formatted their hard drive, reinstalled everything, and by the time that was done, a new version was out, so they installed that and had no problems, to them proves that they are right!

I hope all that's not too off topic and does a better job of explaining what I was saying! :)

[dream-lx]

@JimBryce: were you also working in software development ? As software developer I know well that there might be problems with some other installed application or same special configuration that is due to an error I have in my application. I think one cannot conclude from the fact that an application is running for most people, that is 100% error free. Well there might be some other application causing the trouble, but when doing a fresh install, you don't know which application it was, and later you might have the same problem again when installing this application. So I find it is more helpfull to figure out the application causing problem. For example if the error is not in the application I written, and that some other application install destroys a dll or something I am depending on, I could say for example don't install this application together with mine. If I would simply say do a fresh install (would be much simpler for me), maybe that my application will not even run at all because the person is installing the same software as before.

[JimBryce]

@dream-lx":
You're speaking from the point of view of a developer and I agree with you 100%!:)

Also speaking as a developer, you're not going to install a program, have a problem, un-install it then write to the developer and say; "Your program has a problem! I installed it, crashed, un-installed it and everything was fine." then walk away after dumping the problem back in the developer's lap! You understand all the things that could cause the problem, you will look for them and make suggestions accordingly. That's every developer's dream and the way it should be!:)

My suggestions are for those that don't do that! I'm sure you've read the posts, not just here or this one but elsewhere as well, where the people that have problems make no effort to solve them, instead they just complain that it doesn't work, crashed their system, or whatever and just go on complaining and asking when is it going to be fixed! Those are the people that need to think about what I said--not that they will though...

To answer your question, I'm only a "wanabe" developer. I'm still learning and trying to "look over the shoulder" of real developers as much as I can (thus my involvement in most of these threads!).

[geoffwa]

Hmm, I'm fairly proficient with the whole Make-Windows-Run-Stable thing (XP boxes with uptimes in the months), but the ffvfw version bundled with AviSynth 2.52 still broke Vdub real good (albeit intermittently with XP SP1).

Don't real developers prefer no users and spend all day writing PERL scripts to attend to their daily lives?

[Guest]

This thread is now grossly off-topic. Thread closed.