-
Encore CS4 Timeline-Crash
-
Hmmm… I may not have the update in question…though updating my NVIDIA drivers took care of Encore.
I did have serious runnability problems with PPro CS4 until I got rid of Panda Antivirus…
Before getting rid of Panda, i couldn’t even open a sequence in Ppro…but i could import clips and the app ran until I attempted to create a sequence.
TimK,
Director, Consultant
Kolb Productions, -
Well, I had not suspected the anti-virus app to be part of the problem, but I will look into that. I’m about to the point of deciding that perchance I have pushed this older machine as far as possible without upgrading some features-most likely the video card.
In fairness, I spent the better part of the morning pouring through the Premiere CS4 user forums at Adobe and I do not appear to be alone in this, nor does it seem that my somewhat antiquated video card would be the sole culprit. There are folks who are having the same problem whose cards will run rings around mine. Further, it seems the suggested “fixes” don’t have any logical connection to a solution or to each other. These included:
Font compatibility issues -remove fonts and replace until you find the “bad” one. . . This was suggested (repeatedly and adamantly) by someone who was lucky enough to have it work on his/her system (which may have undergone some other change unbeknownst to them). They couldm’t identitfy a specific font, but they were sure that everyone else who was complaining about it had the same problem. I tend to discount this as highly unlikely, and I have hundreds of fonts installed, as I’m sure do most designers.
Log in under a new User Account -I suspect this may be a blanket “you’re running Vista aren’t you?” response, because if one account has user privileges adequate to run Premiere then a new one would likely have no more permissions for that user. However, if this were simply cleaning up a bad configuration stored in the user profile (my suspicion) would it not be better to destroy the bad config?
The common thread I saw in 99% of the posts was that the 4.0.1 upgrade patch was the cause of the problem regardless of system, and many systems ran CS3 without error (as did both of mine) and CS4 unpatched (ditto, at least as far as Premiere and media encoder, didn’t try Encore until it was too late).
Unfortunately it appears the only way to get back to the pre-4.0.1 patch is to do an un-install/re-install which with Master Collection takes about a day.
If anyone knows of a better way to backgrade from an Adobe update I’d love to hear about it.
Larry S. Evans II
Executive Producer
Digital I Productions -
yes, several people have brought up the last update…I’m running Encore 4.01.48 now without these issues, so I don’t have much to add to the conversation in that way…
TimK,
Director, Consultant
Kolb Productions, -
As I said, upgrading the video drivers on the one machine with the NVidia card did completely resolve the problem (at least as far as my present uses go) so it would appear to be some combination of video driver and the 4.0.1 patch and some other X-factor that is affecting a number of different configurations.
At any rate, I am functional on one unit, and am fully willing to admit that the other one may just need a card upgrade. Fortunately I have one I can test in a day or so, but if that doesn’t do it, then I have to go chasing ghosts. Luckily I try to keep both machines fairly parallel in terms of fonts, log-ins, and service patches because I move a lot of work between them. That pretty much leaves hardware specific drivers (which would be what most people are thinking anyway).
Will post here if I find any solution. Thanks for replying.
Larry S. Evans II
Executive Producer
Digital I Productions -
Tim,
I’m using Dynamic Link to send the entire timeline which includes sequences and transitions. It can be as simple as 2 or 3 seq. with a couple of transistions. If I attempt to play back the entire Timeline in Encore it will crash at times. Having said this, I did discover that I was using a version of Mother Board Bios that was beta. It did cause memory test 2.11 to fail. I went back to current Bios and all Memory is now tesing ok. This may have been causing Blue Screen Crashes.I hav enot seen since.
I now see the headless process you had mentioned. So your suggesting that Encore is still dependent on Pre Pro even if running Encore on its own? Both applications are running around 500k of memory. Whats odd is if I run a rendered out version of the project without the Pre Pro Headless in the background Encore is now up to 1,500K. Almost 3 times what it normally runs with Pre Pro non rendered Dynamic Linked timeline.
Again thanks for helping me understand the interface between these two applications.
-
Encore will use more memory if it’s available. Each Adobe app would love to have 2GB under ideal conditions…in Windows XP, this is usually not possible.
If PPro headless is running to load the sequences, then the two apps have to share what they can get…and when one or more apps run into a memory limitation when one is trying to serve data to another…we all fall down.
When you have a PPro timeline with Dynaimc linked AE comps that you Dynaimc Link into PPro…that will get interesting.
TimK,
Director, Consultant
Kolb Productions, -
I think it’s more accurate to say that Encore and Premiere are “sharing” the timeline component library (as well as others possibly).
From a programing standpoint this actually makes good sense in that you only have to write the code once, and presumably any fixes just apply to the one module. Unfortunately, that means any “breaks” break both systems, as well as any others that are dependent.
I’ve frequently run across the “headless” app in 3D operations, where one application is “embedded” in another (Poser to Vue, Vue to Lightwave, PoserPro to Lightwave). I have frequent memory errors from these arrangements, largely due to memory management issues rather than the amount of available memory.
That is, it’s not how much memory that is being used, but how the system is calling and releasing it. X amount of memory may be allocated to a given application, but if that memory doesn’t have a contiguous chunk the proper size to hold the data being written to it, then the chunk heads out into virtual RAM (i.e. it gets written out to the drive). Since Premiere and Encore also appear to be using the GPU and video memory for some of their processing of the timeline (based on some of the crashes I’ve had) you’ve got even more fractured memory to keep track of.
It’s a nice idea to have an application suite where you can run “hot” all your files back to their genesis in vector and paint apps as well as the video source, without having to take the time to create those pesky intermediate files (that later you can’t remember if you need to archive or not). I’d love to have that workflow. But it needs to be reliable and not require a HAL9000 to run it.
Hope your memory problems go away with the BIOS fix. Judging from a number of the BBS out there. CS4 apparently has some demons yet to exorcise.
Larry S. Evans II
Executive Producer
Digital I Productions -
I’ve had luck with having Premiere open while attempting to open the Encore project. It seems to help when I have the project open in Premiere. Not sure why, but it has helped with the crashing of Encore.
Reply to this Discussion! Login or Sign Up