Uwe Actually, I do not limit rendering to only for preview. Rendering always has to be done unless there are no edits of any kind on the timeline and not just for preview. Rendering can optionally be initiated by the user in advance of playback, but ultimately rendering has to be done whether or not one performs a pre-render for preview. Adriane mentioned that manually rendering, even in bits and pieces, fails, unless the duration selected is very short, but no mention was made re: how short these were. We do know the timeline is 18 minutes and that it cannot be rendered in one pass. Adriane also stated there are many cuts & effects to render, which suggests a lot of memory will be required. But that machine has 8gb so PPro should have up to four 2gb blocks available, I think. So what is going wrong? Like you, when I export I let it redo the entire rendering; it protects me when I am make a mistake. Lee From: [email protected] [mailto:[email protected]] On Behalf Of Uwe Soltau Sent: Saturday, October 23, 2010 6:49 PM To: [email protected] Subject: Re: [AP] render vs export ( WAS "crashing again- background programs?") Thanks Lee, Now we are getting back on the same wave length. So, what you call rendering is rendering for "PREVIEW". Usually one would hit ENTER and rendering would start or you would select the different options under Sequence. If I now relate this to Ariane's problem I don't understand that she has a problem at all. Rendering for preview does NOT have to be done in one go. You can render bits and pieces as you go along, you can render a section of a long clip or only one effect and do the rest later. That way your processor should not get hot, your memory should not be a problem etc etc etc.
Contrary to that export rendering has to be done in one go and I would understand if she had problems with that. I hope she will still let us know when exactly she has a problem. A precise description of a problem always helps to suggest a solution. Getting back to export rendering I never use the preview files as I do preview rendering at a low quality to save time. Thanks again Uwe > Uwe > > "What is the reason for rendering"? > 1. As you know, Premiere Pro can display the intended edited > video/audio frames in the Program panel. It does so by making the display > frames from the individual tracks in the sequence. That process of making > those display frames is what they call rendering. But what if the computer > cannot render the frames at 30fps or whatever -- taking longer per > frame than > the display rate of one frame every 1/30th second? For that case, > Adobe gave > us the ability to actually pre-render the sequence: telling Premiere > Pro to > "render" the sequence ahead of time and save the rendered frames in a > file. > Then when you play that sequence in the Program panel, Premiere Pro > doesn't > need to rebuild the individual frames (render), instead, it displays > frames > from the pre-built rendered file, allowing PPro to play at 30fps for the > smooth playback look. Often these rendered files are referred to as > "preview" files. When you see playback jerky or stuttering, all that is > happening is that it is taking PPro longer that 1/30th of a second to > build > and display each frame. > 2. Those five menu commands under Sequence with the word "render" are > the commands that allow you to pre-render or delete obsolete pre-rendered > files. (Note the audio may also have to be converted to fit the video and > that is what "conforming" is about.) > 3. As you know, once a sequence is rendered it displays the green line > under the timeline. Adobe keeps track of changes made in the sequence, and > when a change is made it knows the pre-rendered files are no longer > valid so > it changes the color of that line to yellow or red. Yellow means the > timeline needs to be rendered but that it probably can play it back in > real > time so building rendered files for preview is not necessary; however, for > export it will be necessary. Red means it probably cannot playback in real > time; stuttering is likely. > 4. Exporting requires use of rendered frames before it can apply the > codecs or do frame resizing. If you have previously pre-rendered the > timeline, you can tell AME to use those files prior to exporting (in the > Export Settings window, there is a check box in the lower right > labeled Use > Previews), otherwise, the export process will spend the extra time to > render > while exporting. > 5. You had the right idea all along -- perhaps what seemed confusing is > only the fact that export needs rendered frames, too, and will > automatically > build them if none are present or current. But the algorithmic process of > rendering and the algorithmic process of exporting are distinctly > unique and > separate processes, as I described. > > Hope this helps > > Lee > > From: [email protected] <mailto:Adobe-Premiere%40yahoogroups.com> > <mailto:Adobe-Premiere%40yahoogroups.com> > [mailto:[email protected] <mailto:Adobe-Premiere%40yahoogroups.com> > <mailto:Adobe-Premiere%40yahoogroups.com>] > On Behalf Of Uwe Soltau > Sent: Saturday, October 23, 2010 2:27 PM > To: [email protected] <mailto:Adobe-Premiere%40yahoogroups.com> > <mailto:Adobe-Premiere%40yahoogroups.com> > Subject: Re: [AP] render vs export ( WAS "crashing again- background > programs?") > > Lee, > Now I am somewhat confused. What am I missing? > What is the reason for what you call rendering. > Please give me the steps how you do that in CS4 or CS5. > Do you use the rendered files for exporting? > Thanks > Uwe > [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Adobe-Premiere/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/Adobe-Premiere/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
