Return-Path: Received: from nk11p03mm-asmtp002.mac.com ([17.158.232.237] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4972778 for AE-List@media-motion.tv; Mon, 11 Feb 2013 23:25:27 +0100 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_LT7hg9XEXI9I/BclrlxjXA)" Received: from [192.168.1.68] ([99.152.153.100]) by nk11p03mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MI2004EHUKDKM80@nk11p03mm-asmtp002.mac.com> for AE-List@media-motion.tv; Mon, 11 Feb 2013 22:31:27 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327,1.0.431,0.0.0000 definitions=2013-02-11_06:2013-02-11,2013-02-11,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1302110244 From: Jim Curtis Subject: Re: [AE] OT: Premiere Pro Question Date: Mon, 11 Feb 2013 16:31:25 -0600 In-reply-to: To: After Effects Mail List References: Message-id: <12D9C93A-2C56-4250-92C0-D2A30A084639@me.com> X-Mailer: Apple Mail (2.1283) --Boundary_(ID_LT7hg9XEXI9I/BclrlxjXA) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable 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. J > =20 > John > =20 True. I have an 8x3GHz with CUDA card, 32G RAM, and the aforementioned = RAID. =20 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 = playback 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 = experience 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 > =20 > 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. > =20 > But, exporting small low res sequences using AME is wicked fast. I = use H.264 for reviews. > =20 > =20 > =20 > =20 > On Feb 11, 2013, at 3:48 PM, Phil Spitler wrote: >=20 >=20 > 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 = approval without a huge render? > =20 > Any ideas? > =20 > =20 > Phil > =20 > =20 > =20 > Phil Spitler | Creative Technologist | Bonfire Labs | t : = 415.394.8200 m : 415.571.3139 >=20 > Website | Facebook | LinkedIn > =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. =AD=AD =20 --Boundary_(ID_LT7hg9XEXI9I/BclrlxjXA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable

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.  J

<= /div>


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 playback 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 experience 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 approval without a huge = render?
Any = ideas?
  |  Creative Technologist =   |  Bonfire Labs  = |  t : 415.394.8200  m : 415.571.3139

Website | Facebook |  

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.  =AD=AD  

<= /div>
= --Boundary_(ID_LT7hg9XEXI9I/BclrlxjXA)--