-
Demo Version Crashes When Trying To Render AVI
Hello, all. I just found out about this great program, and downloaded the V3 demo, and installed it on my system. I run WinXP Pro SP2, a P4 2.8HT, and have 2 Gigs of memory. I use an ATI Radeon 9800 Pro graphics card. Anyways, my problem is that when I try to save the output as an AVI file, I get the first box asking what to name it, and where to save it, and in what format. I complete that box, and the second render box shows up, and I complete that just by clicking the OK selection. But when it comes time for the Compression settings box to come up, the program ALWAYS encounters an Exception, and crashes.
Anyone have any ideas what I can do about this issue? I’d love to really give this program a trial run, because I have been looking to purchase just this very thing!
Thanks for your time!!
-
16 Replies
-
Update: The error message I get each time is as follows:
Access violation at 0x1D6A2425 (Tried To Read From 0x00000048), program terminated.
I’ve found that I can save the sequence as .bmp or .png files, but it will just not render to avi.
Any ideas anyone?
-
I’m not too sure what it could be, other than perhaps a driver issue. Try this:
Under View>Preferences, click the OpenGL tab and uncheck ‘Use hardware acceleration’. Restart pI, and try rendering an AVI again.If AVIs no longer crash, then its a driver issue so you’ll need to grab the latest certified ATI driver.
—
Elvis Deane!
The particleIllusion FAQ
particleIllusion Resources and tutorial CD
Astounding Adventures -
Thanks for your reply, Elvis. I tried what you suggested, but got the same exception as before, and always. I do have the latest ATI drivers, btw, but I tried your suggestion anyway. This is very disappointing for me, because this program looks to be exactly what I’ve been looking for. Bummer.
-
I think there’s a codec that you have installed that is causing problems for pIllusion. Can you give me a list of the codecs that are installed on your machine?
Alan.
wondertouch -
I forgot to say how to do this: Start – Settings – Control Panel – Sounds and Audio devices. Then click the “hardware” tab, select “video codecs” from the bottom of the list, then click the “properties” button. Then switch to the “properties” tab.
You can take a screengrab of that and send it to me as a jpg or something (at wondertouch support).
Alan.
wondertouch -
Very well then. What I’m going to do is to post the information here, so that if anyone else has the same problem in the future, they can just refer to this thread. Sound good? Alright then, here is what is listed in the results, including all capitalization and such:
ATIYUV12.DLL
CineForm HD VFW Codec
DivX 🙂 MPEG-4 Video Codec (Fast-Motion)
DivX 🙂 MPEG-4 Video Codec (Low-Motion)
DivX 5.0 codec
ffdshow Video Codec
Fraps Video Decompressor
Indeo codec By Intel
Indeo video 5.10
ir41_32.ax
IYUV_32.dll
IYVU9_32.dll
mcdv-pro.dll
Microsoft MPEG-4 Video Codec
Microsoft RLE Codec
Microsoft Video 1
Microsoft Windows Media Video 9 VCM
msh261
msh263
msyuv.dll
msyuv.dll << YES, it's listed twice >>
PICVideo MJPEG Codec
Pinnacle PIM1 32-bit AVI Codec
XviD MPEG-4 Video CodecOK, there you have the complete list. I really hope you can figure out which one is the issue!! Thank you very much for your time and efforts on this!!
-
If it were my system, I’d remove one of the duplicate codecs as a first step.
If that doesn’t do it, I think we’ll need people to help out here and list their codecs as well, so we can figure out which ones are fine, then by a process of elimination, we should be able to narrow it down to a couple of codecs that might be the problem.
Alan.
wondertouch -
I did as you suggested, without any change. Still gets the exception. Does WinXP Pro store all the video codecs in just one directory, and if so, where is that directory? I can try moving them out one by one to see if that helps.
Otherwise, I think your last suggestion would be great! I would suggest that you be the one to make the new thread requesting that information, seeing as how I’m just a newbie and all… 🙂
-
I would start with the DivX codecs and ffdshow. I primarily use Adobe Video Production software, and these codecs have caused no end of grief to Adobe users. Maybe pI doesn’t like them, either.
-Jeff
-
Thanks for the idea, however, after removal via the control panel applet, PI still gets the same old exception and crashes…. It was worth a try, however! 🙂
Reply to this Discussion! Login or Sign Up