Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [AE] Love You Adobe
From: James Culbertson <albion@speakeasy.net>
In-Reply-To: <list-4620772@media-motion.tv>
Date: Wed, 8 Feb 2012 17:12:29 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF5FE343-94C9-4531-86B7-D6ADCF7A10BD@speakeasy.net>
References: <list-4620772@media-motion.tv>
To: "After Effects Mail List" <AE-List@media-motion.tv>

Depends I suppose upon the power of your system and how much you are =
manipulating the footage in the timeline.

Plus if you render during idle time you have less to render on final =
output.

I imagine at some point even the daintiest little macbook will eat 1080p =
effects for breakfast. But at the moment not so much. Nice to have =
options depending upon your working situation.

James


On Feb 8, 2012, at 4:52 PM, John Morgan wrote:

> Appreciate the explanation. Not sure I understand why anyone would =
want/need the option of working with native footage OR a proxy if the =
native processes 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 going on that you can turn on or off and control in various =
ways including codec type of course.
>=20
> 1.  You can choose whether to transcode in the background any native =
source 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 immediately begin to playback and/or edit with the footage. When =
the footage is done transcoding FCPX seamlessly starts to use the =
optimized transcodes rather than the native footage. You can delete the =
intermediate footage at any time and go back to using the original =
native source.
>=20
> 2. You can turn on or off background rendering in the timeline (or in =
compound clips) of effects, composites, and other clip modifications. =
But if you turn off background rendering you can still playback the =
timeline without rendering. Even on my old MacPro I can edit most =
everyday type of projects without rendering (couple of composited clips =
with or without alpha, titles, graphics, effects and color correction on =
each clip, audio effects). I did try 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 depending upon your CPU/GPU combo. I'll =
be curious to upgrade my CPU and test this again.
>=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 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.
>>=20
>> John
>>=20
>> -----Original Message-----
>> From: After Effects Mail List [mailto:AE-List@media-motion.tv] On =
Behalf Of 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 thrown at it so far (on my 4.5 year old first generation dualcore =
MacPro with upgraded 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 exception I can think of is XDCAM at =
this point. I initially followed Apple's recommendation of transcoding =
to proRes but have found that for short projects at least I don't really =
need to -- I imagine this will be especially true for newer Macs.
>>=20
>> I don't think I will be doing 20-layers on my old MacPro with any =
existing 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 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.
>> +---End of message---+
>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>>=20
>=20
>=20
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>=20