Working in CS5.5 on a lengthy project. Going along just fine, color correction, etc, and then I just couldn't render even the simplest of procedures. What happened?
Thank you, John, for your quick reply. Yes, of course, I should have included more info. (Under client pressure, aren't we all). To your questions: Pre Pro 5.0, and reluctant to upgrade to 5.5.2 in midst of project. OS Mac 10.75. And no, alas, don't have Mercury Playback. Am working on a multi-cam project, cutting Sony CX560 (AVCHD) into base Sony Z5U HDV, on 2 Vid tracks and 2aud tracks, as I've done many times before. This time, I was doing a little nip 'n tuck which necessitated dragging downstream clips to close the gap, and I noticed I lost one clip on V1. Fixed that but then noticed I couldn't render anymore. Wonder if there's a corrupted file somewhere? Back in Final Cut days one would trash preferences when things didn't work. Is that true of Premium Pro? No third party apps installed. Do get warnings to upgrade Adobe Flash. Is that an issue?
I think CS5 is up to 5.0.2 on Mac... is there some reason you have not updated?
All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/
I suppose the reason I haven't updated from CS 5.5.0 is because I'm reluctant to make changes during editing. I can render other projects on the same drive, but this one, no. Which makes me wonder if I've got a corrupted file somewhere. This used to happen in Final Cut and then it was just a simple matter of trashing preferences. Does that issue come up in Premier Pro.
Jim, Can't render this particular 1hr38min project. Can render other projects I have on my drive, but not this project. I had finished color correction, audio gain, and was just trimming a few clips and closing the gaps when one clip just disappeared on me. Replaced it, and then that's when things went South. Could it be a corrupted file if such things happen in Pre Pro as they do in Final Cut?
Yes, I did. Slapped a title over a clip. Hit render. Nothing happened. Red bar remained. But I exported that section and it played just fine - no embarrassing red frame saying "unrendered" as it would in Final Cut. As you can tell, I'm a recent convert to Premium Pro - love it, by the way - and so I marvel when you say "don't necessarily need to render." Why is that?
I'm still having a hard time getting my head around this. You say you don't necessarily need to render. So what does that red bar mean when it pops up after applying some effect? I've always assumed you needed to CMD+R (render effects in work area) after applying an effect. And I have been doing just that since coming over to Pre Pro. And the render window pops up and the progress bar progresses and the red line turns green or at least not red. Well - at least until it stopped doing that yesterday. And am I understanding you correctly, that it's not necessary to render before exporting?
Thank you, Joe. I should have read this before since not all NLE's work the same, but it still doesn't answer my original question, Why has Premier pro stopped rendering my application of effects? Is it due to a corrupted file? Do I need to trash preferences? Or is there anything else I could try to fix the problem?
I would try deleting all of your Preview files and re-render.
Find your 'Adobe Premiere Pro Preview Files' folder,
open, select and delete all, re-launch Premiere.
Premiere will pop-up asking where your Preview Files went...
Click 'Offline All', then re-render your Timeline.
Preview File location:
Project > Project Settings > Scratch Disks... Video Previews
Thank you, Joe, Jim, for your advice to this newcomer. I will do as you suggest, Joe, to delete preview files. That sounds the way to go. In the meantime, I've done a quick export and red render bars notwithstanding, it came out fine. It's a long 1hr 40min multi-cam project and I had done most of the tweaking, color correction, audio gain, etc. It was just at the very end when I was doing titles that Pre Pro ceased to render. So, Jim, yes, i'm going to deliver this to my client and then get back to solving the problem, i.e., trashing preview files.
This is embarassing. I was confusing the gray navigation bar for the gray timecode bar, aka "work area". Now that I'm emcompassing the render area inside the work area, rendering proceeds as it should. Mustn't assume one NLE is like any other. Gotta read the instructions.