Return-Path: Received: from mail-qc0-f169.google.com ([209.85.216.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4873239 for AE-List@media-motion.tv; Mon, 15 Oct 2012 22:38:09 +0200 Received: by mail-qc0-f169.google.com with SMTP id t2so4439168qcq.28 for ; Mon, 15 Oct 2012 13:40:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer:x-gm-message-state; bh=wfb7oj5cc3d7KG5mTygddlrKWhcew3vpXmirFszOSH0=; b=lpRGimQBaW2t0jqAgItxzsHOaiZAsDsufCY6Jvm9c2ogMwNJ62rmPmakTd4kXeIMzC GE/tH1w+5ThnD+EQic9vd7tdqyrs40E+DaxxV3Txy9eUNFcePqo8vf+JeE1rBTXndfqm FxPq3QkniOp/LbtgrIkzlQQUnnA6xCQf6OKx7bKZNa8V4kpWClt9QlJEeE1M1gu9ZuZs zrHcucFtXPvIKj1pOqG9OfFlUFBYWBOYab+s90JBtItFhjYXD/enlZH0cF+5wUhKX38E TyBWwFb41l94Lboe69sz1TAznUtOmhoeacxBqaTdkpf/FA53wIvc3BRBTA98wAuxlGMf VeEQ== Received: by 10.224.221.144 with SMTP id ic16mr22712227qab.20.1350333627665; Mon, 15 Oct 2012 13:40:27 -0700 (PDT) Return-Path: Received: from new-host.home (pool-96-246-39-39.nycmny.fios.verizon.net. [96.246.39.39]) by mx.google.com with ESMTPS id gz7sm16406186qab.8.2012.10.15.13.40.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 15 Oct 2012 13:40:26 -0700 (PDT) From: Alex Czetwertynski Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-103-511754506 Subject: Re: [AE] RED Workflow Date: Mon, 15 Oct 2012 16:40:25 -0400 In-Reply-To: To: "After Effects Mail List" References: Message-Id: <2D781345-D5F3-41DA-A07D-263EEC56DF33@disciplefilms.com> X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQkkDHTzq8MKotduy9dVL3Tup0hQb4i79NE8OZPy5O3JtdrP5bWGCu1ppU2Kqx9DJJhT5ksL --Apple-Mail-103-511754506 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii A workflow previously mentioned here was to export the XML from FCP, = then find and replace using a text editor from all the proxies to the = actual source footage. Then import that into AE. You might have to re-fit all your media in = your comps as they will probably come in at the size of the proxies... HTH Alex On Oct 15, 2012, at 4:31 PM, Jack Tunnicliffe wrote: > Phil: >=20 > I guess there isn't a simple answer to this. It sometimes depend on = how deep the directory structure is. We know here we sometimes end up = with 35 days of shooting, so the tree can be rather complex.=20 >=20 > My one editor said that after the Automatic Duck export if the option = doesn't connect to the R3D footage, he said reconnect the footage = manually navigating to the R3D file. Connect to the first one in the = list, as you know often R3D files can be multi segment, so pick the = first one. >=20 > Others may connect in that directory once you do that but you may have = to manually reconnect the other R3D's as well. I guess they are = accustomed to doing this all the time so don't find it onerous but it = doesn't sound like fun to me. >=20 > Hope this helps.=20 >=20 > Jack Tunnicliffe > Java Post Production > 402, 2206 Dewdney ave. > Regina, SK > Canada > S4R 1H3 > P. 306-777-0150 > cell. 306-536-4321 > www.javapost.ca > ______________ >=20 >=20 >=20 > On Oct 15, 2012, at 1:55 PM, Phil Spitler = wrote: >=20 >> Wow... I never spotted that option... >>=20 >> I just tried it though and it didn't work swap out (or through up an = errors). >>=20 >> Does the media need to be in specific locations? >>=20 >> Thanks Jack. >>=20 >> Phil >=20 --Apple-Mail-103-511754506 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii A = workflow previously mentioned here was to export the XML from FCP, then = find and replace using a text editor from all the proxies to the actual = source footage.
Then import that into AE.  You might have to = re-fit all your media in your comps as they will probably come in at the = size of the = proxies...

HTH
Alex

=
On Oct 15, 2012, at 4:31 PM, Jack Tunnicliffe wrote:

Phil:

I = guess there isn't a simple answer to this. It sometimes depend on how = deep the directory structure is. We know here we sometimes end up with = 35 days of shooting, so the tree can be rather = complex. 

My one editor said that after = the Automatic Duck export if the option doesn't connect to the R3D = footage, he said reconnect the footage manually navigating to the R3D = file. Connect to the first one in the list, as you know often R3D files = can be multi segment, so pick the first = one.

Others may connect in that directory once = you do that but you may have to manually reconnect the other R3D's as = well. I guess they are accustomed to doing this all the time so don't = find it onerous but it doesn't sound like fun to = me.

Hope this helps. 

Jack = Tunnicliffe
402, 2206 = Dewdney ave.
Regina, SK
Canada
S4R = 1H3
P. 306-777-0150
cell. 306-536-4321

On Oct 15, 2012, at 1:55 PM, Phil Spitler <phil@bonfirelabs.com> = wrote:

I just tried it though and it didn't = work swap out (or through up an errors).
Does the media need to be in specific = locations?

Thanks = Jack.