[Larry Andersen]

Digging deeper, I found a post that suggested updating the AJA Kona Software. I switched to version 10.0.1 and everything is suddenly better. I hope this helps someone else.

Best,
Larry

[Larry Andersen]

…and 16 Gig RAM.

[Larry Andersen]

Very nice solution, Steve. Thanks.
Larry

[Larry Andersen]

I wonder if PluralEyes from singular might be helpful. I’ve used it in more simple applications – syncing HDSLR footage with free-running audio recording. It was great for that. Your issue is quite similar…

[Larry Andersen]

Bingo! There is a Use Previews checkbox. If not selected, PP re-renders everything in your sequence. When selected, it takes and hour and 20 minutes off my render and looks just fine for client posts.

PP’s “Previews” are a notion I’ve been grappling with in general. In FCP, You’re generally rendering to the quality of your sequence settings. PP has a more mysterious set of “preview” options, where it appears that I’m rendering just for quick playback, or not, if I choose QT ProRes or uncompressed for my sequence Preview option. I can see advantages in PP’s approach.

Thank you Vince.

[Larry Andersen]

I’m finally having a moment to troubleshoot. In a very interesting development, I just removed ALL of the effects from my timeline. My QT movie is now allegedly going to take 7:30 the render instead of 1:25:00. This suggests that rendering effects in a timeline does not leave them rendered for final output. The encoder seems to re-render everything. That can’t be right. Can it???? That would make it ridiculous to use PP for anything project that both uses effects and needs occasional posts…like every project.

[Larry Andersen]

I discussed this problem in another thread and got some feedback. Here’s my response to the feedback, which centered on my sequence type and computer types:

This goes way beyond what machines I’m using. The render times are, without exaggeration, 40 times slower than Compressor. I might expect a somewhat slower render on my Macbook Pro, but my work computer was the very best mac money could 8 months ago, prior to the most recent MacPro release. My render times are almost exactly the same on that machine.

I just started a test using the H264 codec sans QT per your suggestion. I’m getting the same render time – an hour and 25 minutes for an under 3 minute sequence.

I’m editing with raw P2 footage from an HVX 200. I’m putting the DVCProHD footage into a 1920×1080 sequence instead of a 1440×1080 sequence so my graphics can be full res. I’ve fully rendered everything in the sequence before export. I do have a couple of Boris filters on most of the shots, but again, everything is rendered.

[Larry Andersen]

This goes way beyond what machines I’m using. The render times are, without exaggeration, 40 times slower than Compressor. I might expect a somewhat slower render on my Macbook Pro, but my work computer was the very best mac money could 8 months ago, prior to the most recent MacPro release. My render times are almost exactly the same on that machine.

I just started a test using the H264 codec sans QT per your suggestion. I’m getting the same render time – an hour and 25 minutes for an under 3 minute sequence.

I’m editing with raw P2 footage from an HVX 200. I’m putting the DVCProHD footage into a 1920×1080 sequence instead of a 1440×1080 sequence so my graphics can be full res. I’ve fully rendered everything in the sequence before export. I do have a couple of Boris filters on most of the shots, but again, everything is rendered.

I’m moving this discussion to the main PP thread to get more input. If you have any other notions, please go there.

Thanks.
Larry

[Larry Andersen]

I’ve been having the exact same thoughts about leaving FCP behind and am just about done with a test project. I’ve been taking extensive notes on the good and the bad points of switching over, and there are plenty of each, but the reasons not to are winning. I’m going to do a more extensive post in the next couple of days to see if operator error is playing any part in some massive issues I’ve faced.

All that ignores your Color question. I don’t believe there is a comparable program on the Adobe side of the fence, but Colorista and Synthetic Aperture both do nice things, as does Boris’s 3-way color grade module. To fake the secondaries, you’d need to work multiple layers. I think the best solution is trying out ways suggested in this thread to get PP projects out to Color.

[Larry Andersen]

An apology…There is a scroll bar I missed in the QT settings. Unfortunately this has not sped anything up.I’m still looking at an hour and 20 minutes to render a an H264 QT at half resolution, 960×540, and 50% quality. I’m going to start a new thread. This can’t be right.