This content has been marked as final. Show 11 replies
I cannot help you on the frozen clip but you may like to know that SteadyMove does work with After Effects CS3.
Just out of curiosity, what codec was used when rendering out the AVI from After Effects?
AE's default AVI codec when exporting is lossless. That will indeed choke Premiere. Just prerender the clip.
Thanks for the tip on Steady Move!
I don't remember the codec because I made that clip a long time ago and am just now using it in this last job.
When I render it though, it still doesn't play on the timeline??? I can't figure that one out???
Thanks for the feedback!
Use GSpot to find the codec.
I have no idea what GSpot is??
I can tell you this though, This clip works fine in PPro 2, just not in CS3.
And as far as the AE codec, I don't think that it should matter because the clip in question came from AE originally, but I rendered it and exported it as an AVI from within PPro 2, so it should be a normal DV/AVI.
What are your thoughts?
GSpot is a program that will tell you whether or not it actually is a DV AVI, and whether or not it is 'normal' (meaning without errors). It's a free program, you can Google it.
Thanks Jim, I'm going to download it.
BTW The clip runs fine now after rendering. The only thing different is that I cold booted the system. I warm booted it before and the clip still wouldn't run, but once I shut the machine down completely and restarted it, the clip runs. Sometimes a system doesn't fully release memory unless it has been shut off.
Thanks Again Jim!
I have the exact same problem, but rebooting only solves it temporarily. anybody got any other explanations?
Karen, I had a similar problem when I first began automating slideshows with Premiere Pro CS3. I had previously been using consumer slide show software (Roxio) that apparently resized my sources behind the scenes when I imported them into my projects. When I began using Premiere Pro, failing to resize the stills beforehand in Photoshop caused Premiere to consume huge amounts of memory (the size of each still photo was multiplied by 30 times per second for NTSC) and soon began resulting in hit-and-miss displays of clips and stills in the program monitor on playback. Since your problem temporarily goes away on a reboot, it sounds like it could be a memory-related issue. I would check the file sizes of your clips to make sure that you are not taxing your project's performance with excessive memory requests. Also make sure you have sufficient memory capacity on your system to begin with. Good luck!