xvidcore message, and avisynth

cinnamon-baka · Post by **cinnamon-baka** » Sat Mar 31, 2007 9:47 pm

Sorry that this is kinda long, and probably confusing, but this is really frustrating me.

Problem Number Uno: Apparently, WMM doesn't like Avisynth, because when I have the program downloaded on my computer and I try to open one of my AMV projects on WMM, WMM shuts down. Well, then I unstalled all the 75,000 programs that are attached to avisynth, and lo and behold, WMM's working dandy again. Since I ripped the DVDs I'm using with another program (I used BitRipper), I figured that I didn't need Aviynth. However, the video comes out of BitRipper with a lot of interlacing going on, so it looks like I'll be needing Avisynth after all to get rid of it. Which leads me to...

Problem Numero Dos: I reinstalled Avisynth, went back to WMM, and opened the project I was working on. Oh, but wait! It won't let me -- instead, I get a message saying, "xvidcore.dll not found", then freezes up, so I have to CTRL-ALT-DEL so I can get out of the stupid program. Now, this has never happened before, even after I had downloaded Avisynth the first time, so I don't know if the two are connected. Just for the heck of it, I actually went and downloaded xvidcore, just to see if it'll fix the problem. Alas, it didn't.

So, I ask you: how can I get Avisynth and WMM to exist together in perfect harmony, and just what in the world is xvidcore, and why is it suddenly causing a problem now?

JaddziaDax · Post by **JaddziaDax** » Sat Mar 31, 2007 10:16 pm

#1 what are you importing into windows movie maker? avs files? wmv? avi?

#2 are there already files in your wmm (previously saved project) or are you opening an entirely new project?

#3 you can deinterlace (though its not as good) in Virtualdub Mod (which is the program you SHOULD be using avisynth in, not wmm)..

#4 i would guess (and this really is a guess) that xvidcore is something to do with the xvid codec... what is the compression of your video files (if they are avi..) you can get a program called GSpot to find out if "right click"->"Properties"->"summery" doesnt tell you...

cinnamon-baka · Post by **cinnamon-baka** » Sat Mar 31, 2007 11:17 pm

#1 what are you importing into windows movie maker? avs files? wmv? avi?

AVI.

#2 are there already files in your wmm (previously saved project) or are you opening an entirely new project?

It was a project already saved. (Sorry, I should've made this clearer.)

#3 you can deinterlace (though its not as good) in Virtualdub Mod (which is the program you SHOULD be using avisynth in, not wmm)..

But I'm not using Avisynth in WMM. All I know is that when I have the program installed, WMM won't work; but when I uninstalled it, WMM was working fine again.

cinnamon-baka · Post by **cinnamon-baka** » Sat Mar 31, 2007 11:27 pm

JaddziaDax wrote: #4 i would guess (and this really is a guess) that xvidcore is something to do with the xvid codec... what is the compression of your video files (if they are avi..) you can get a program called GSpot to find out if "right click"->"Properties"->"summery" doesnt tell you...

Well, I haven't saved the project; it gives me that message when I open the actual WMM project, but the original video files I had imported were AVI, and are about 1 gig each, if that's what you're talking about with the compression. (I'm still not quite savvy with all the lingo yet.)

Actually, just now when I went to the files I ripped from my DVD and checked the properties, I got the same message about xvidcore as I did when I tried to open the WMM file. The problem, must be with the files I ripped, not the WMM file itself.

Willen · Post by **Willen** » Sun Apr 01, 2007 1:04 am

Do you have XviD installed?

Keeper of Hellfire · Post by **Keeper of Hellfire** » Sun Apr 01, 2007 2:40 am

Willen wrote:Do you have XviD installed?

While it may be the reason for the error message and it is necesary to have XviD installed to read the files at all, there is one important thing: Don't edit with XviD files! The chances are high that it will crash WMM too.

cinnamon-baka · Post by **cinnamon-baka** » Sun Apr 01, 2007 8:38 am

Willen wrote:Do you have XviD installed?

No, but that hasen't been a problem until now; I've made three AMVs with WMM before, and they all work fine. It wasn't until now that I suddenly hear something about XviD. Plus, it's not like it started doing this straightaway when I imported the DVD footage; I was actually about a third of the way finished with the video, saved it as a WMM project, but when I tried to open the project up again I got the message.

Willen · Post by **Willen** » Sun Apr 01, 2007 10:05 am

Hrm, let's back up. It really sounds like XviD is somehow getting involved here, xvidcore.dll is the core libraries of the XviD codec. Are you sure you didn't uninstall more than just AviSynth? I'm pretty sure that AviSynth itself isn't composed of or attached to "75,000 programs". There should be an avisynth.dll in your Windows directory and various filters (and their documentation) in the AviSynth\Plugins directory. All in all, no more than a few hundred files.

I'm curious about the AVI file(s) you are using. If none of the AVI files are XviD, then you shouldn't get a "xvidcore.dll not found" message. Right click on the AVI file and check it's Properties. Select the Summary tab and choose the Advanced view option. At the very bottom, under Video compression it should state what codec was used to encode the video. If that doesn't reveal the proper info, download and install GSpot like JaddziaDax suggested and use it to analyze the AVI file.

AFAIK, AviSynth should have no effect on WMM unless you are using AVS scripts as fake AVI files for your sources. Which, if this was the case, you wouldn't be even able to open the files for editing or viewing unless AviSynth was installed. Since you have the opposite scenario, this baffles me. It's possible that ffdshow is interacting with AviSynth provoking the crashes you are experiencing. BTW, what version of AviSynth are/were you using? If it is 2.5.7, try regressing to 2.5.6a. If you have 2.5.6a, try 2.5.7, it may have fixed a bug that is causing your troubles. http://sourceforge.net/project/showfile ... p_id=57023

At a worst case scenario, install AviSynth, deinterlace (and pre-process, etc.) along with VirtualDub/Mod your DVD footage. Then uninstall AviSynth, edit and export the video directly from WMM (I'm assuming you are doing this since your 2 previous videos are WMV).

Also, I prefer using DVD Decrypter for ripping DVDs. It's free, is fairly easy to use, and has many guides available on using it if you need help.

cinnamon-baka · Post by **cinnamon-baka** » Sun Apr 01, 2007 1:39 pm

Are you sure you didn't uninstall more than just AviSynth? I'm pretty sure that AviSynth itself isn't composed of or attached to "75,000 programs".

Well, that was of course an exaggeration. ^^;; But, yeah, I was just referring to the other files that come with the program (DVD Decrypter, Virtual Dub Mod, etc.); it just takes a little while to get it all installed, so it just seemed like a lot.

If none of the AVI files are XviD, then you shouldn't get a "xvidcore.dll not found" message.

Actually...it turns out that they are XviD files, as I saw when I checked the properties. Whoops.

It's possible that ffdshow is interacting with AviSynth provoking the crashes you are experiencing. BTW, what version of AviSynth are/were you using? If it is 2.5.7, try regressing to 2.5.6a.

Yeah, I think that ffdshow does has something to do with the crashes, because when I open WMM, the little ffdshow icon shows up on the bottom-right part of the toolbar by the clock. The version I'm using is whatever version was linked to by the "Preparing DVD Footage for WMM2" tutorial (which is Avisynth 2.56beta1, as it says on the download page).

Also, I prefer using DVD Decrypter for ripping DVDs. It's free, is fairly easy to use, and has many guides available on using it if you need help.

Yeeeaaaah, I think I'd better start doing that.

JaddziaDax · Post by **JaddziaDax** » Sun Apr 01, 2007 2:00 pm

sounds like the amvapp is causing problems... when in install the app i usually skip over ffdshow cause i just dont like it personally O.o

not sure if that will help you or not O.o