There are multiple possibilities... Note that I never used XviD4PSP before (tried installing on VM before, that's about it), so I'm simply guessing...

1.   I'm pretty sure it sources stuff through DSS (99% of avisynth based encoding frontends do). Now Windows 7 uses it's own built in decoders, EVEN if you install a codec pack. Problem is, DSS is not completely compatible with these Microsoft decoders, so you can possibly end up with gay DSS errors. There is a way to fix it however, by editing the registry. Fortunately, nowadays, you don't have to do that by hand.  » http://www.codecguide.com/windows7_prefe...weaker.htm

2.  x264 had some major changes during the latest month or two, so any old unupdated command line generator will most likely generate an invalid command line. So if you updated x264, expect it to fail. That's one reason why you shouldn't use outdated GUIs.

3.  Simply not compatible with Windows 7? Try XP compatibility mode.

Senseito7 Wrote:in b 4 software recommendations.

PSP conversions?

My custom encoding script ftw lol.

Try megui if you really need a GUI.  However, I do warn you it does have some learning curve.

Senseito7 Wrote:XviD4PSP has issues with 7. I had major problems with it, but I don't use it anymore now so I wouldn't know.

What do you use now?

(This post was last modified: 12/10/2009 12:03 AM by Assassinator.)