PrP obervations after an effects heavy project

[Keith Moreau]

I don’t know if it’s a matter of Adobe ‘adopting’ Prores or any other codec. Premiere Pro has the ability to use preview files of anything it can export. This can be set up in the sequence settings, and it doesn’t seem to slow normal operations down to use an iFrame codec like Prores while editing. It’s just that, at least for me, checking the ‘Use Preview Files’ on export doesn’t seem to significantly speed up rendering.

So what would be advantageous for Adobe would be to:

1) Provide the option to create preview files in the background ala FCPX or AE. When the CPU / GPU is needed for editing, all background rendering stops.
2) Improve granularity of what is rendered, for example clips, GPU vs CPU, video or audio tracks, ala FCP. Keep better track of what is rendered via what isn’t rendered at the sub clip level.
3) Provide a choice of using the rendered preview files or not while editing. Don’t lose track of the rendered files if you turn that option back on
4) Make “Use Preview files” (of your selection) for exporting appreciably faster without re-rendering or whatever else that seems to take a lot of time when exporting

[Tom Daigon]

I just finished testing out the option of using Prores ((almost ANY codec is available under the Preview Setting drop down if you choose Quicktime primarily) as my Preview and Export codec. Things went extremely well. Here are the results.

1. Custom 1920 x 1080 1 PAR 29.97 2 min. sequence chock full of animated multiscreens, color corrections, speed triggers, scaling and 2 5 sec. AE dynamic linked flying camera motion graphics pieces.

2. Previewed with MPEG I frame. Export was 7:30. Didn’t get a total for the rendering of the work area during the building phase .

3. Previewed with Prores 422. Export was 3 min. Rendering of the entire work area during the building phase was 7.5 minutes. Of course most of the stuff on the timeline didnt need rendering to play, except the AE DL clips, but I was curious to see how long it would take.I was able to catch little things like incorrect field order and other little anomalies since when blown up with the grave key the image was clean and crisp.

I would guess the results might be the same if Cineform was chosen instead of Prores.

Tom Daigon
Avid DS / PrP / After Effects Editor
http://www.hdshotsandcuts.com
Mac Pro 3,1
8 core
10.6.8
Nvidia Quadro 4000
24 gigs ram
Maxx Digita / Areca 8tb. raid

[Robert Brown]

[Keith Moreau] “1) Provide the option to create preview files in the background ala FCPX or AE. When the CPU / GPU is needed for editing, all background rendering stops.
2) Improve granularity of what is rendered, for example clips, GPU vs CPU, video or audio tracks, ala FCP. Keep better track of what is rendered via what isn’t rendered at the sub clip level.
3) Provide a choice of using the rendered preview files or not while editing. Don’t lose track of the rendered files if you turn that option back on
4) Make “Use Preview files” (of your selection) for exporting appreciably faster without re-rendering or whatever else that seems to take a lot of time when exporting
“

I’d basically agree to that. I think it comes down to – like I said in a suggestion to Adobe – making sure that the time invested in rendering while editing is not wasted by having to render it again during export as has been established in numerous other platforms. If it’s rendered then it should be rendered.

Robert Brown
Editor/VFX/Colorist – FCP, Smoke, Quantel Pablo, After Effects, 3DS MAX, Premiere Pro

https://vimeo.com/user3987510/videos

[Chris Borjis]

So what happens when you take a premiere timeline that is rendered with mercury and you edit to tape?

Does it just go immediately or does it internally export a file then output to tape?

[Gary Huff]

It creates an internal export file.