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 doesnt
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:[email protected]]
On Behalf Of Uwe Soltau
Sent: Saturday, October 23, 2010 2:27 PM
To: [email protected]
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
> 1. Rendering is the process of merging all video tracks, effects,
> transitions, etc. frame-by-frame into the edited video frames that the
> user
> will view. The more tracks, effects, transitions, etc. used, the more
> processing must be done. Some of the input tracks may be in different
> codecs
> and file formats, which must all be converted into a common format
> specified
> by the sequence settings. Lots of source and output frames must be in
> memory
> simultaneously, thus the more tracks, effects, etc., involved, the more
> memory is required. Since there is a lot of repetitive processing
> involved,
> multi-CPU's running in parallel can greatly reduce the processing
> time. The
> CUDA "technology" uses some processing capabilities present on some NVidia
> graphics cards, but this is happening separate from display processing.
> 2. Exporting is the process of taking those final, rendered frames
> and converting each of them, frame-by-frame, into the final useable video
> file. The actual processing varies according to which CODEC's to apply,
> frame resizing, and the output file format. As with rendering, this
> process
> can also require a lot of CPU power, and also can benefit from multi-CPU's
> running in parallel.
>
> The problem of "freezing to locking up while rendering very short
> clips" is
> something that should be avoidable because most users don't have that
> problem. Since the problem seems to be dependent on video length, we
> should
> focus on the memory itself, such as its quantity, integrity, or anything
> that can starve the rendering process. The number and speed of CPU's are
> probably not relevant, since they affect the speed but not the
> "freezing and
> locking" problem.
>
> Lee
>
[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/
