Any reason not to encode from the preview file(s)?

[Steven L. gotz]

Yes. There is a reason.

The material that started out as DV AVI will not be any different, but there are materials, like photographs, that will not look as good if you encode to DV AVI before transcoding to MPEG2.

Is it important? Not usually. Not for most people. But if you want to avoid that one generation of loss, then encode directly from the timeline using the original material, and not the DV AVI it was encoded to for preview purposes.

Many people prefer to export a DV AVI and then let Adobe Encore do the transcoding.

Steven
Adobe Premiere Pro 1.5 / After Effects 6.5 Pro https://www.stevengotz.com
Learning Adobe Premiere Pro 1.5 https://www.lynda.com
Contributing Writer, PeachPit Press, Visual QuickPro Guide, Premiere Pro 1.5

[Vjohn]

Thanks for the insightful reply, Steven.

[Perry Cheng]

So, is there a way to encode from previews? Import all the previews files and then butt them together? Or? I think for most people, that will be much faster… for a quick project.

perry

[Vjohn]

That’s just what I did to experimentally verify the process. It’s a bit of a chore since the program creates a gaggle of preview files, not just one, and I think they need not sum to the work area – if a snippet didn’t need rendering, it’s left out. But given that it’s pretty easy to apply effects that take 5:1 or 10:1 to render, avoiding re-rendering can save a ton of time.

An interesting workflow might involve incremental export to DV AVI for preview; those files could be brought back into the project on a new track and time-aligned. Clip boundaries would be obvious and clips in the original could be further edited as necessary and then copied over the new working track, or the clip bounds could be duplicated into the working track.