Return-Path: Received: from mail-iy0-f169.google.com ([209.85.210.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4620794 for AE-List@media-motion.tv; Thu, 09 Feb 2012 02:07:46 +0100 Received: by iagz16 with SMTP id z16so1869383iag.28 for ; Wed, 08 Feb 2012 17:13:49 -0800 (PST) Received: by 10.50.89.197 with SMTP id bq5mr37710708igb.24.1328750029365; Wed, 08 Feb 2012 17:13:49 -0800 (PST) Return-Path: Received: from [192.168.1.229] (c-71-63-186-29.hsd1.mn.comcast.net. [71.63.186.29]) by mx.google.com with ESMTPS id gw1sm2662406igb.0.2012.02.08.17.13.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 08 Feb 2012 17:13:48 -0800 (PST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <9D9E43C9-352E-4D17-BFCA-2402DFFB52F1@imugonline.com> Cc: After Effects Mail List X-Mailer: iPad Mail (9A405) From: Carey Dissmore Subject: Re: [AE] Love You Adobe Date: Wed, 8 Feb 2012 19:13:47 -0600 To: After Effects Mail List I edit in Premiere Pro professionally. I barely dabble in FCPX at this point= , but I have to say the combination of native support and seamless transcode= -to-prores replacement of that media is a beautiful thing. Excellent softwar= e design. I want that integrated capability very bad in Premiere Pro. As to the reasons why you would want this? They center around workflow and performance. I actually have a lot I could s= ay on this subject but for now it will have to wait. Suffice it to say that I= value native codec workflows but also find times when a common codec workfl= ow are clearly superior. This is decided on a project by project basis, some= times mid-project. That mid-project conversion is Quite problematic in PPro a= s there are no integrated tools like FCPX, nor is there a transcoding-capabl= e Media manager like old FCPX had. These are items in my top 5 wishes for Pr= emiere Pro. Sorry so short, I'm on the run... Carey Sent from my iPad On Feb 8, 2012, at 6:52 PM, John Morgan wrote: > Appreciate the explanation. Not sure I understand why anyone would want/ne= ed the option of working with native footage OR a proxy if the native proces= ses offer render-free timeline playback during editing. >=20 > John >=20 > ________________________________________ > From: After Effects Mail List [AE-List@media-motion.tv] On Behalf Of James= Culbertson [albion@speakeasy.net] > Sent: Wednesday, February 08, 2012 4:37 PM > To: After Effects Mail List > Subject: Re: [AE] Love You Adobe >=20 > As Eric mentioned there are two different possible background processes go= ing on that you can turn on or off and control in various ways including cod= ec type of course. >=20 > 1. You can choose whether to transcode in the background any native sourc= e video to an intermediate like Prores on ingest of source footage (or later= at any time during the edit; FCPX also unwraps source footage automatically= if necessary). Whether you are transcoding source or not, you can immediate= ly begin to playback and/or edit with the footage. When the footage is done t= ranscoding FCPX seamlessly starts to use the optimized transcodes rather tha= n the native footage. You can delete the intermediate footage at any time an= d go back to using the original native source. >=20 > 2. You can turn on or off background rendering in the timeline (or in comp= ound clips) of effects, composites, and other clip modifications. But if you= turn off background rendering you can still playback the timeline without r= endering. Even on my old MacPro I can edit most everyday type of projects wi= thout rendering (couple of composited clips with or without alpha, titles, g= raphics, effects and color correction on each clip, audio effects). I did tr= y compositing 20 1080p clips together which was easy to do when the playhead= was parked, but my old mac choked on playback, so there are limits dependin= g upon your CPU/GPU combo. I'll be curious to upgrade my CPU and test this a= gain. >=20 > James >=20 >=20 > On Feb 8, 2012, at 2:34 PM, John Morgan wrote: >=20 >> 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 render= ing 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 back= ground, then that is still not "working with files natively" in my book. Pre= miere 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 n= ative and do not change during the edit. >>=20 >> John >>=20 >> -----Original Message----- >> From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf O= f James Culbertson >> Sent: Wednesday, February 08, 2012 2:01 PM >> To: After Effects Mail List >> Subject: Re: [AE] Love You Adobe >>=20 >> 30 minutes is still a good data point. Thanks for the feedback. >>=20 >> And just for the record, FCPX does playback natively everything I have th= rown at it so far (on my 4.5 year old first generation dualcore MacPro with u= pgraded ATI Radeon HD 5770). Certainly all H.264/MPEG4/AVCHD variants of any= SD/HD resolution or frame rate (and all legacy formats of course). Only exc= eption I can think of is XDCAM at this point. I initially followed Apple's r= ecommendation of transcoding to proRes but have found that for short project= s at least I don't really need to -- I imagine this will be especially true f= or newer Macs. >>=20 >> I don't think I will be doing 20-layers on my old MacPro with any existin= g editing app though. Time to upgrade my hardware. >>=20 >> James >>=20 >>=20 >>=20 >>=20 >> This message, and any attachments, is intended only for the use of the ad= dressee and may contain information that is privileged and confidential or o= therwise exempt from disclosure under applicable law. If the reader of this= e-mail is not the intended recipient, you are hereby notified that any unau= thorized use, dissemination, distribution or reproduction of this message is= prohibited. If you have received this communication in error, please notif= y the sender by return e-mail and delete this e-mail and any attachments fro= m your system. >> +---End of message---+ >> To unsubscribe send any message to >>=20 >=20 >=20 > +---End of message---+ > To unsubscribe send any message to > +---End of message---+ > To unsubscribe send any message to