|
|
<I think your mixing up rendering with transcoding.>
No, when I say "render-free" I'm speaking only of playback of the timeline (during editing) no matter the complexity of the layers and FX on the clips. Naturally the export/encode/transcode processes require rendering.
Not fair to say that what happens on the CUDA card is still counted as rendering if it doesn't take up CPU cycles and doesn't slow down real time playback.
<.....to work faster, etc in the timeline.> That's what I'm saying. You work faster in the timeline ALL the time now in Pr with a system like mine. It's not a choice you have to make.
I work mostly in Panasonic P2 (DVCProHD) and Sony XDCAM EX. I never export back out to either of those formats. Pretty much always go to h.264 or Windows Media in the world I live in.
John
-----Original Message-----
From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of Eric James Wood
Sent: Wednesday, February 08, 2012 3:52 PM
To: After Effects Mail List
Subject: Re: [AE] Love You Adobe
you scribbled:
> Thanks James.
> So just to clarify what I thought I saw during the FCPX rollout, one of the "selling points" in the demo that I watched was that "now all this rendering can occur in the background during low-use CPU cycles." If that means a background encode/render to a ProRes or other proxy is going on in the background, then that is still not "working with files natively" in my book. Premiere has no background render processes that occur automatically unless the user starts a render process for exporting. In Pr, with a system like mine, no rendering ever needs to occur in the background. All native files stay native and do not change during the edit.
It is a preference if you would like to transcode to proRes to work faster, etc in the timeline. I have premiere running on an approved cuda card, and trust me, there is rendering going on still, but on the card. Yes the card is fast, but it still has to render stuff.
I think your mixing up rendering with transcoding. When i output my timeline that has native dslr footage, with AE comps in there, and color correction in PPro, it takes time to get a final file out. It is not a couple of seconds.
I went thru this with adobe last year, take some prores clips and throw it into a PPro timeline and export to the same codec as your source. It takes time. Ppro deals with all codecs as cracking them open and getting to the data inside, that is why it works with everything under the sun really well.
Now take a proRes clip in fcp 7 or X and do the same thing, it will export a file wicked fast to the same codec as the source since it is just a file copy.
Ppro DOES NOT do a simple file copy, but actually deals with the data differently.
Now doing it in fcp is a two step process in the real world, you export a DI in ProRes then have to make a h.264 for web delivery, where in PPro, i just go straight to the h.264 file since it takes so long to make the proRes file, then make the h.264 file.
It is two different ways of working is all. My hangup is that if you make a 1hr movie, with lots of edits, effects, titles, AE comps, etc. Normally i would export a DI master, then use that to strike any delivery format i would need.
PPro i tend to export the timeline more times than exporting a DI master.
--
<ericwood>
Helium14 | www.helium14.com
Design | Motion + Graphic
www.helium14.com
'the next best thing to knowing something, is knowing where to find it'
+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>
This message, and any attachments, is intended only for the use of the addressee and may contain information that is privileged and confidential or otherwise exempt from disclosure under applicable law. If the reader of this e-mail is not the intended recipient, you are hereby notified that any unauthorized use, dissemination, distribution or reproduction of this message is prohibited. If you have received this communication in error, please notify the sender by return e-mail and delete this e-mail and any attachments from your system.
|
|