Return-Path: Received: from mail-ee0-f49.google.com ([74.125.83.49] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4972802 for AE-List@media-motion.tv; Mon, 11 Feb 2013 23:51:44 +0100 Received: by mail-ee0-f49.google.com with SMTP id d4so3480890eek.8 for ; Mon, 11 Feb 2013 14:57:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=YYv567kl/A0Z6evAK2jZSpv5J45Dat+90ldf/585FbY=; b=nRWHLnPrquBee2aAGByq4TSj9g1uV+kEt4e+wax39oHudQ4S/jQX8vu4wWjgdno5Km xLfiSqGLyzfX2SzFCh9j+OGFUfRT47QCGk0QYbBSGxDDTyxMpOywDrNHJboICwRKTMGS KWE4TscjJJHtXmYD73PZvlFqGE+HZeZqPYCRX8GwPy+LsSrYnkhlAEY8kMYyPREgYozs NozM8Xw2hf3kB0cLkFAj/IJM6JRXL8ubDM3DF+DOHUjUln7faBVcDFU8BaK9n7Vttq9c Cv12UU+rGxWVgLwoncHYvnVqCN4V6luFrT/qgazirY3/FpuRu9za+R2DHTX/D3hAj30i 5d4g== X-Received: by 10.14.182.5 with SMTP id n5mr54829194eem.9.1360623469343; Mon, 11 Feb 2013 14:57:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.36.193 with HTTP; Mon, 11 Feb 2013 14:57:29 -0800 (PST) In-Reply-To: References: From: Bruce Wainer Date: Mon, 11 Feb 2013 17:57:29 -0500 Message-ID: Subject: Re: [AE] OT: Premiere Pro Question To: After Effects Mail List Content-Type: multipart/alternative; boundary=047d7b3433309033c704d57ad627 --047d7b3433309033c704d57ad627 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Well maybe do both: start editing immediately in PP, and at the same time transcode into something that will export quicker. Any shot that doesn't specifically need the color latitude and/or raw resolution can then be swapped out right before export. Bruce Wainer On Mon, Feb 11, 2013 at 5:54 PM, Phil Spitler wrote: > We usually use REdCineX to transcode all our footage before editing in FC= P > but we are trying to avoid that step as it takes a long time and usually > after we shoot, we want to start editing. > > So far, PP CS6 seems pretty solid except for this issue of taking a while > to export the footage. > > Phil > > > > > > > *Phil Spitler* | Creative Technologist | *Bonfire Labs* | t : > 415.394.8200 m : 415.571.3139 > > Website | Facebook| > LinkedIn > > On Feb 11, 2013, at 2:31 PM, Jim Curtis wrote: > > > On Feb 11, 2013, at 4:08 PM, John Morgan wrote: > > The =93wicked=94 in Jim=92s reply depends on the RAM and number of proces= sors on > your machine. J**** > ** ** > John**** > ** ** > > > > > True. I have an 8x3GHz with CUDA card, 32G RAM, and the aforementioned > RAID. > > In 1/1 mode, my CPU meters maxed and spiked (Same experience in the > REDCINE X app). Far less so at =BC. So, my weak link for smooth playba= ck > was CPU, not io. > > I did a series of web videos several months ago. I edited in 1280x720, > since that was the destination spec. So, the REDRAW footage was scaled > down in the Sequences. There was only a layer or two of supers, a fair > amount of Ultra Keying, and my GFX were Dynamically Linked to Ae Comps. > > The five minute videos exported to H.264 in around three minutes each. > So, I'm comparing the RED exports to other projects with say XDCam HD or > EX or P2 seemed pretty favorable, just based on expectations and experien= ce > with other codecs. I expected that a codec that weighed the CPU down as > much as RED footage would have taken much longer. > > Overall, I enjoyed editing RED RAW in Pr w/o having to use proxies. > Source side color correction is great. > > > > *From:* After Effects Mail List [mailto:AE-List@media-motion.tv] *On > Behalf Of *Jim Curtis > *Sent:* Monday, February 11, 2013 3:03 PM > *To:* After Effects Mail List > *Subject:* Re: [AE] OT: Premiere Pro Question**** > ** ** > I've had the reverse experience. I can't play 3 and 4K and not drop > frames without going to =BC or less resolution. I have a >1.8 GB/s RAID.= *** > * > ** ** > But, exporting small low res sequences using AME is wicked fast. I use > H.264 for reviews.**** > ** ** > ** ** > ** ** > ** ** > On Feb 11, 2013, at 3:48 PM, Phil Spitler wrote:**** > > > **** > We can playback RED footage no problem but rendering it or exporting it > takes forever. How can we export a low quality version for client approva= l > without a huge render?**** > ** ** > Any ideas?**** > ** ** > ** ** > Phil**** > ** ** > ** ** > ** ** > *Phil Spitler* | Creative Technologist | *Bonfire Labs* | t : > 415.394.8200 m : 415.571.3139 > > Website | Facebook > | LinkedIn **** > ** ** > ** ** > > 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 o= f > this e-mail is not the intended recipient, you are hereby notified that a= ny > 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. =AD=AD > > > > --047d7b3433309033c704d57ad627 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Well maybe do both: start editing immediately in PP, and a= t the same time transcode into something that will export quicker. Any shot= that doesn't specifically need the color latitude and/or raw resolutio= n can then be swapped out right before export.

Bruce Wainer


On Mon, Feb 11, 2013 at 5:54 PM, Phil Spitler <phil@bonfir= elabs.com> wrote:
We usual= ly use REdCineX to transcode all our footage before editing in FCP but we a= re trying to avoid that step as it takes a long time and usually after we s= hoot, we want to start editing.

So far, PP CS6 seems pretty solid except for this issue of t= aking a while to export the footage.=A0

Phil

=



<= br>
Phil Spitler= =A0 |=A0 Creative Technologist =A0 |=A0 Bonfire Labs=A0 |=A0 t : 415.394.8200=A0 m : 415.571.3139

Website | Facebook | <= a href=3D"http://www.linkedin.com/company/235257?trk=3Dtyah" target=3D"_bla= nk">LinkedIn

On Feb 11, 2013, at 2:31 PM, Jim Curt= is wrote:


On Feb 11,= 2013, at 4:08 PM, John Morgan wrote:

= The =93wicked=94 in Jim=92s reply depends on the RAM and number of = processors on your machine.=A0=A0J
=A0
John
=A0



True. =A0I have an 8x3GHz with CUDA card, 3= 2G RAM, and the aforementioned RAID. =A0

In 1/1 mode, my CPU meters maxed and spiked (Same experience in the REDCINE= X app). =A0Far less so at =BC. =A0 So, my weak link for smooth playback wa= s CPU, not io.

I did a series of web videos several mont= hs ago. =A0I edited in 1280x720, since that was the destination spec. =A0So= , the REDRAW footage was scaled down in the Sequences. =A0There was only a = layer or two of supers, a fair amount of Ultra Keying, and my GFX were Dyna= mically Linked to Ae Comps.

The five minute videos exported to H.264 in around thre= e minutes each. =A0So, I'm comparing the RED exports to other projects = with say XDCam HD or EX or P2 seemed pretty favorable, just based on expect= ations and experience with other codecs. =A0I expected that a codec that we= ighed the CPU down as much as RED footage would have taken much longer.

Overall, I enjoyed editing RED RAW in Pr w/o having to = use proxies. =A0Source side color correction is great.

=


From:= =A0After Effects Mail List [mailto:AE-List@media-motion.tv]=A0On Behal= f Of=A0Jim Curtis
Sent:=A0Monday, February 11, 2013 3:03 PM
To:= =A0After Effects Mail List
Subject:=A0R= e: [AE] OT: Premiere Pro Question
=A0
I've had the reverse experience. =A0I can't play = 3 and 4K and not drop frames without going to =BC or less resolution. =A0I = have a >1.8 GB/s RAID.
= =A0
But, exporting small low res sequences using AME is wicked fast. =A0I use H= .264 for reviews.
=A0
=A0
=A0
=A0
On Feb 11, 2013, at 3:48 PM, Phil Spitler wrote= :


We can playback RED footage no problem but rendering it or exporting it tak= es forever. How can we export a low quality version for client approval wit= hout a huge render?
=A0
Any ideas?
=A0
=A0
Phil
=A0
=A0
=A0
Phil Spitler=A0 |=A0 Creative Technologist =A0 |=A0= =A0Bonfire Labs=A0 |=A0 t : 415.394.8200=A0 m : 415.571= .3139

Website=A0|=A0Facebook=A0|=A0LinkedIn
=A0
=A0

This m= essage, and any attachments, is intended only for the use of the addressee = and may contain information that is privileged and confidential or otherwis= e exempt from disclosure under applicable law. If the reader of this e-mail= is not the intended recipient, you are hereby notified that any unauthoriz= ed use, dissemination, distribution or reproduction of this message is proh= ibited. 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 yo= ur system.=A0=A0=AD=AD=A0=A0


--047d7b3433309033c704d57ad627--