-
1. Re: Wow! I feel like a "Crash-Test" Dummy!
John T Smith Aug 12, 2009 7:18 AM (in response to Shao Lung)First, work through all of the steps here http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of that link
-
2. Re: Wow! I feel like a "Crash-Test" Dummy!
Shao Lung Aug 12, 2009 8:01 AM (in response to John T Smith)I have applied all available updates and followed the steps in the WIKI as a precursor to posting. The details in the dialouge box that pops up is a "run-time error in C:\program files\adobe\ - and I cannot then see the end of the message. I hate to assume, but I surmise it is in the program executable as this is what the crash occurs in. G spot reports my codec as "Direct Show" with AVI audio splitter. I am simply saving the project file or auto-saving. All the other details of my system are posted on the previous message.
-
3. Re: Wow! I feel like a "Crash-Test" Dummy!
Jeff Bellune Aug 12, 2009 8:11 AM (in response to Shao Lung)This sounds ominous. Like a full re-format and re-install of your
system is looming.
Before you resort to that, though, try installing the latest version of
the Microsoft Visual C++ Runtime distributable package.
-Jeff
-
4. Re: Wow! I feel like a "Crash-Test" Dummy!
tclark513 Aug 12, 2009 8:16 AM (in response to Shao Lung)Have you turned off all of your widows "themes" and shut down everything in the back ground?
-
5. Re: Wow! I feel like a "Crash-Test" Dummy!
Bill Hunt Aug 12, 2009 9:36 AM (in response to Shao Lung)Runtime errors can be common. They usually stem from a bad, outdated, or otherwise corrupt C++ Runtime.dll.
I would address that issue first and foremost. Google "runtime error," and begin reading. There will be many hits, but if you refine your search with words like Adobe, Premiere, etc., you'll narrow things down. There will be links to the MS site for updated runtime.dll's. Note: make sure that you get the one that perfectly matches your version of the OS. Do NOT get one for any other version, than yours. Check this carefully.
Good luck,
Hunt
-
6. Re: Wow! I feel like a "Crash-Test" Dummy!
Huntrex Aug 12, 2009 7:59 PM (in response to Shao Lung)Well, I used to have the same problem. Premiere was completely unusable. It turned out that an older installation of Premiere Elements was interfering with Premiere Pro and causing all the problems. A simple uninstallation of Premiere Elements did no good. I ended up having to re-format the hard disk and re-install the operating system. Problem solved.
-
7. Re: Wow! I feel like a "Crash-Test" Dummy!
Bill Hunt Aug 12, 2009 8:22 PM (in response to Huntrex)That is a horror story. Now, going back a bit, there was a problem, if one installed PrE4 AFTER they had installed PrPro 2.0. The fix was to do a repair of all programs in the CS2 Production Studio, as PrE 4 killed them all. Apparently, Adobe never figured that anyone would install PrE AFTER CS2 Production Studio. Obviously, many did, as there was an Adobe KB Article on how to fix things.
Other than that, I have heard of no other issues. You case is totally new to me.
Hunt
-
8. Re: Wow! I feel like a "Crash-Test" Dummy!
Shao Lung Aug 14, 2009 2:34 PM (in response to Shao Lung)In this project (the only one I have ever used CS4 in) I have about 30 or so nested sequences, due to the time remapping bug that does not allow for opacity control AFTER applying time-remapping....therefore in my timeline I have 30 or so nested sequences that contain remapped footage. Would this cause this as well? I know nested sequences would cause trouble in previous versions of production studio..........




