Return-Path: Received: from eatspam.slcc.edu ([144.35.15.69] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4620696 for AE-List@media-motion.tv; Wed, 08 Feb 2012 23:59:25 +0100 X-ASG-Debug-ID: 1328742328-0437c61280930930001-edO5QZ Received: from vCAS2.slcc.int (vcas2.slcc.int [10.1.11.53]) by eatspam.slcc.edu with ESMTP id hZitkHJKz9zoBhYN for ; Wed, 08 Feb 2012 16:05:28 -0700 (MST) X-Barracuda-Envelope-From: John.Morgan@slcc.edu Received: from EXCH.slcc.int ([127.0.0.1]) by vCAS2.slcc.int ([fe80::8031:551b:9a53:7716%11]) with mapi; Wed, 8 Feb 2012 16:05:28 -0700 From: John Morgan To: After Effects Mail List Date: Wed, 8 Feb 2012 16:05:27 -0700 Subject: RE: [AE] Love You Adobe Thread-Topic: [AE] Love You Adobe X-ASG-Orig-Subj: RE: [AE] Love You Adobe Thread-Index: AczmtFHRiQfyx2N3R1SFLpoUlLN9kwAAIE0Q Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: vcas2.slcc.int[10.1.11.53] X-Barracuda-Start-Time: 1328742328 X-Barracuda-URL: http://eatspam.slcc.edu:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at slcc.edu X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.88002 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 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 rend= ering if it doesn't take up CPU cycles and doesn't slow down real time play= back. <.....to work faster, etc in the timeline.> That's what I'm saying. You wo= rk faster in the timeline ALL the time now in Pr with a system like mine. I= t'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 Wind= ows 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 t= he "selling points" in the demo that I watched was that "now all this rende= ring 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 b= ackground, then that is still not "working with files natively" in my book.= Premiere has no background render processes that occur automatically unles= s 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 timelin= e that has native dslr footage, with AE comps in there, and color correctio= n in PPro, it takes time to get a final file out. It is not a couple of sec= onds. 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 d= ata 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 diffe= rently. Now doing it in fcp is a two step process in the real world, you export a D= I in ProRes then have to make a h.264 for web delivery, where in PPro, i ju= st 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 wou= ld need. PPro i tend to export the timeline more times than exporting a DI master. --=20 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 This message, and any attachments, is intended only for the use of the addr= essee and may contain information that is privileged and confidential or ot= herwise exempt from disclosure under applicable law. If the reader of this= e-mail is not the intended recipient, you are hereby notified that any una= uthorized use, dissemination, distribution or reproduction of this message = is prohibited. If you have received this communication in error, please no= tify the sender by return e-mail and delete this e-mail and any attachments= from your system.=