-
OK! Enough of this crap! Does anyone know. . .
one project of mine renders from between 60 to (ooh you S.O.B.) 98% before it barfs out a:
Premiere Pro Debug Event
Src\Win\WinPathUtils.cpp.427popup, followed by:
Microsoft Visual C++ Runtime Library
-This application has requested the Runtime to terminate in an unusual way . . .Sounds almost comical. Except it’s not funny.
Does anyone know if this could be a PPro issue or Vista issue?
I’m going off somewhere to cry now. Be checking for replies tomorrow. kthxbye.
-
8 Replies
-
I get this Error all the time. Not sure if its a vista only thing, but my way around it is to render little peices of the sequence at a time, like start rendering and go from 0-50, then cancel, Save, then Render again. It saves the render progress at least so if it does crash, you dont loose everything.
This method works for me a lot. Its a very annoying bug though…
-
Or you could render out PNGs or TIFFs. That way, no matter where it crashes, just pick up where you left off.
— TL
-
-
a-ha!
Comes the dawn!Thank you, good sir.
This gives me the energy to keep going at this.
(not that I have much else of an option . . .) 😉Thank you again,
Brad -
I’ll give that a go as well.
Right now I’ve had the thought the ‘title’ templates are the problem, so I’ve deleted all traces of them and just made .gif images (which worked fine for me on other projects) right out of Fireworks (of all things . . )If you don’t hear back from me.
It’s worked. (knock on wood)Thanks again,
Brad -
Hi. Thanks for letting me know. Sometimes knowing you’re not alone with a problem helps more than advice.
(at least for me, anyway)Yes, I figured that out and all seemed to got well (although annoying as you mentioned).
But, when it came down to exporting it, it would crash again.
Now I’ve decided if it doesn’t render in one full shot, there’s got to be something wrong . . .
What I’ve done is delete all the Titles I used as templates and made what I wanted via Fireworks as .gif
It rendered fine. Straight through. I’m attempting to export it to Encore . . . If you don’t hear from me in 20 minutes swearing and cursing, you know it worked.
😉 -
Just wanted to throw my two cents in here.
I’ve been working on a video for my company and was having absolutely no problems with Premiere Pro CS3. I left to go home one day and come back to work on the project the following day and BOOM! C++ Runtime error with some Low System Memory errors on the side.
After that first error, I found that there are several things that can be done to remedy the situation on many of the various forums out there. Every single time though the dreaded C++ errors would return.
Since it was quite bothersome to try each of the prescribed fixes each time this happened I continually went back from time to time to see if anyone had uncovered a permanent fix for this issue.
This is what I found. A microsoft hotfix for Windows XP SP2.
https://support.microsoft.com/default.aspx?scid=kb;en-us;884538I wasn’t sure that it would work but decided to go out and check the versions of the files that the hotfix references and sure enough they the versions on the files match the version listed in the hotfix.
I crossed my fingers and ran the hotfix.
Afterwards, Premiere Pro seems to spread the load out across all 4 of my CPUs more effectively and my system memory usage dropped by more than half.
I cannot say that this is a permanent fix, since I’ve only worked on 5 projects since that time, but all of those projects have been huge with lots of effects and titles and I haven’t experienced any C++ errors or the Low System Memory errors yet.
If you would like to try the hotfix I would definitely backup everything on that system before you run it. It may work fine and be unnecessary but its always better to be safe when there’s the chance that something could go horribly wrong.
Hope this helps.
-
May the Gods bless you forever. Amen.
I’m currently in the process of ‘upgrading’ from this un-trustworthy Vista back to XP.
(Same amount of problems really, but at least I don’t have to re-learn a blasted new OS)Anywoo,
I will be running the ‘fix’ afterwards.Thanks bunch.
There has just been so many problems, I dread turning the program (CS3) on at all.
In fact, I haven’t used the damn thing since last November. . .
*sigh*But, it is a big part of my chosen profession and it costs too much to throw out and try something else.
Boo to either Vista or Adobe or both.
Reply to this Discussion! Login or Sign Up