From: "Chris Zwar" Received: from mail-pl1-f169.google.com ([209.85.214.169] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7171031 for AE-List@media-motion.tv; Wed, 10 Oct 2018 00:43:13 +0200 Received: by mail-pl1-f169.google.com with SMTP id 30-v6so1525095plb.10 for ; Tue, 09 Oct 2018 15:54:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriszwar-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=4cHDa2WLH0c4E96WwqsOtJa401PBVTiJEVucF2+NJeY=; b=tAY2f8JafUrpyhgVxVjYD6h0HgYDSt7xcQAhi439KIUi3ug6Du56hzFX1SGULE6JLa mLxv50MmOR5FUh2lGnjzIMATI5qyAG9mPRzWhxlDHvAJ2v5KmW8HeFRY3MvIplrbsi3g Dk39NmkpmpvWqlohkhiJCdYqJzIuHNgbIsBFbmkTiOHkQfNgdlnAlK4mQ6k9e6tUbZnf nii4/LfzG/Cyz/Ks+LoACn/3uwiEWuKNPOFxJ79zsVxfvuyvDEkQvXA8/WZ9uEgiOuQE F2eP1UqfofCxQcbeSU1RCac+++jwl9cPf/7Q19L5nYdRJJnpjd76P8Ai9Uz+xDB4sT6v jIZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=4cHDa2WLH0c4E96WwqsOtJa401PBVTiJEVucF2+NJeY=; b=YRbs/f7fXsyArFRgKf3wtfa7ln4pjjmETijr8AmJhQlbATZEu9g+xPFfHweEkkHHVE J5YVNOX2d9fhddaFF7qe69guhuJU2xJg9NuvM6keqF5beojjSsf2teBYh8ZgbEayucb0 IKWvF2DNSk6MvW/eOT7zgKmrLT3doSkMOQQp+OGF3blcWD2/Dc+ss+K/06Zprev9fyOo 9u/Zq/J7uHgSmRCRXC4Udwyb0yqmLs2Cif90D6srMUR1DL/7wh42zGvlXgfDpbNs3Eay kgnUaj4xGy7p9yxsijxHsrYK+pzwhra8YdX4Fp2shRTNVEf3Xb1ow1OyBx6BJb6abex0 yykQ== X-Gm-Message-State: ABuFfohfodfl6kxAnP7QYEgIEpLK9p9oFJvY0CmSwQrq4LuX4NnQgUr3 pnYdltJqruspTNJCQGu8cBGKg3V4UcI= X-Google-Smtp-Source: ACcGV62X1mEWxKeOWfCTNQev/Btol0EX3asoRXzg3oM1XsQLalOXk3lvpsuhuL7Pe1HkskfvAlDcOw== X-Received: by 2002:a17:902:7142:: with SMTP id u2-v6mr30979186plm.154.1539125683416; Tue, 09 Oct 2018 15:54:43 -0700 (PDT) Return-Path: Received: from chriss-mbp.corp.artistsinmotion.co (7.130.233.220.static.exetel.com.au. [220.233.130.7]) by smtp.gmail.com with ESMTPSA id x23-v6sm9375650pfh.56.2018.10.09.15.54.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Oct 2018 15:54:42 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_8C0DBD10-C26B-4291-A392-06F6516CD284" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] Organising cameras Date: Wed, 10 Oct 2018 09:54:38 +1100 References: To: After Effects Mail List In-Reply-To: Message-Id: <47253DBC-32A8-401C-B117-470EE42F206D@chriszwar.com> X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_8C0DBD10-C26B-4291-A392-06F6516CD284 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Finally catching up=E2=80=A6 Thanks Robert, yes that=E2=80=99s what I should have done - but as David = asks, I should=E2=80=99ve worked out what I was trying to actually do = before posing the question. The problem I had was that I had multiple/individual AE projects with = various states of R&D. These individual projects all had cameras = imported into them, the cameras continued to evolve in the 3D department = while I was working on FX. All the individual AE projects were then = imported into 1 master project, and so I ended up with various cameras = and no version control. The silly thing is that I=E2=80=99ve posted at least two tutorials which = demonstrate making a =E2=80=9Cmaster=E2=80=9D camera and then making a = clone. As Phil said, copying with links is all I need. So I should = practise what I preach! Part of the reason I posted was that, as a result of sleep deprivation, = I was thinking of the camera layer as a single imported object. I was = wondering if there was a way to =E2=80=9Creveal=E2=80=9D the original = camera in the project window and =E2=80=9Creplace=E2=80=9D as you would = a footage item. I was also wanting to know how many times an individual = camera was used in the project, like with footage. It would be nice to be able to do that=E2=80=A6 -Chris > On 3 Oct 2018, at 12:08 am, Robert Kjettrup = wrote: >=20 > Hi Chris >=20 > im a bit late on this thread, but i think i have a solution that i = came up with recently that might work in your case too. >=20 > In one comp i have a "Linker Camera" that i have setup as the camera = that is all other comps cameras are linked to. And this "Linker Cam" is = parented to the 1 instance of an animated camera that can be imported = from eg Cinema4D, just remember to hold Shift while parenting the = "Linker Cam" to the animated camera so it will take on the transform = values from the animated camera, then i have expression on all relevant = parameters and extract them with the "parent." method. >=20 > maybe its easier to follow just taking a look at a simplified project.=20= > in "Comp 1" you find the only cameras you need to adjust, the "Linker = Cam" you shift+parent to what imported camera you have here, cameras in = Comp 2 and Comp 3 will follow. >=20 > https://adobe.ly/2y7w7VL >=20 > hope this maybe can help in future projects :-) >=20 >=20 >=20 > Den man. 24. sep. 2018 kl. 18.24 skrev David Torno = >: > Hi Chris, >=20 > What exactly are you trying to accomplish? This sounds like a script = automation thing so far. You want to replicate a camera build in all = comps? >=20 >=20 >=20 > David Torno > 818.391.6060 > -------------------- > www.sydefxink.com (work history) > https://vimeo.com/davidtorno (work = samples & breakdowns) > https://gumroad.com/davidtorno > http://provideocoalition.com/dtorno = (tutorials) >=20 > "The most useless day is that in which we do not laugh" > -Charles Field >=20 > On Sep 23, 2018, at 10:42 PM, Chris Zwar > wrote: >=20 >> Yes, if I was starting fresh I=E2=80=99d do it that way, I might go = through the whole project and replace the cameras with ones that have = linked properties, just to tidy it up a bit. >>=20 >> I=E2=80=99m really just thinking out lout, but basically if I have 10 = comps with the same camera in them, and I want to duplicate them all but = then swap the camera, then I=E2=80=99m still manually copying & pasting = 10 times. I keep wanting to do something like an alt-drag / replace = footage but with a camera. I=E2=80=99m only thinking about it now = because many of my comps have nulls and location markers parented to the = camera, so even pasting a new camera into the composition means I=E2=80=99= m having to manually re-parent. >>=20 >>> On 24 Sep 2018, at 1:34 pm, Phil Spitler > wrote: >>>=20 >>> Seems like the you could just copy the camera with linked properties = into each comp. >>>=20 >>> Seems really clean and efficient workflow to me. >>>=20 >>> Phil >>>=20 >>>=20 >>> >>> Phil Spitler Creative Technologist >>> t 415.394.8200 c 415.571.3139 = = = = >>>=20 >>>=20 >>>=20 >>>> On Sep 23, 2018, at 6:38 PM, Chris Zwar > wrote: >>>>=20 >>>> Hi all, >>>>=20 >>>> Just wanting to pick the collective brains on how everyone is = keeping track of multiple cameras in large projects. I like to think my = projects are well organised but this is one thing that I haven=E2=80=99t = cracked yet. >>>>=20 >>>> Currently I=E2=80=99m working on a sequence that has over 20 shots = in it, compositing multipass-renders from 3D. I get a camera for each = shot, which I=E2=80=99m then using to roll out multiple FX that are = being generated in After Effects for the composites. I would guess that = each camera is used in 10 - 15 additional precomps for each shot. >>>>=20 >>>> The problem is that as the animation progresses, the cameras are = often changed and updated. Swapping out 3D renders is simple, but so = far I=E2=80=99m importing each new camera and manually pasting it into = each composition. This means I can miss comps because the process is = manual. And as the new cameras have new names, this can also break = expressions and parenting. >>>>=20 >>>> In previous projects I=E2=80=99ve had a =E2=80=9Cmaster=E2=80=9D = camera that I=E2=80=99ve then linked to with expressions to create a = version that I can roll out in precomps, and always use that one = instead. If I planned ahead a bit better I would have done that here, = but it=E2=80=99s not something I=E2=80=99ve done with 20+ shots, each = with individual cameras. >>>>=20 >>>> Does anyone have a better & cleaner method than making a master = camera comp that is always linked to via expressions? >>>>=20 >>>>=20 >>>> -Chris >>>> +---End of message---+ >>>> To unsubscribe send any message to > >>>=20 >>=20 --Apple-Mail=_8C0DBD10-C26B-4291-A392-06F6516CD284 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Finally catching up=E2=80=A6

Thanks Robert, yes that=E2=80=99s what = I should have done - but as David asks, I should=E2=80=99ve worked out = what I was trying to actually do before posing the question.

The problem I had was = that I had multiple/individual AE projects with various states of = R&D.  These individual projects all had cameras imported into = them, the cameras continued to evolve in the 3D department while I was = working on FX.  All the individual AE projects were then imported = into 1 master project, and so I ended up with various cameras and no = version control.

The silly thing is that I=E2=80=99ve posted at least two = tutorials which demonstrate making a =E2=80=9Cmaster=E2=80=9D camera and = then making a clone.  As Phil said, copying with links is all I = need.  So I should practise what I preach!

Part of the reason I posted was that, = as a result of sleep deprivation, I was thinking of the camera layer as = a single imported object.  I was wondering if there was a way to = =E2=80=9Creveal=E2=80=9D the original camera in the project window and = =E2=80=9Creplace=E2=80=9D as you would a footage item.  I was also = wanting to know how many times an individual camera was used in the = project, like with footage.

It would be nice to be able to do that=E2=80=A6


-Chris

On 3 Oct 2018, at 12:08 am, = Robert Kjettrup <AE-List@media-motion.tv> wrote:

Hi Chris

im a bit late on this thread, but i = think i have a solution that i came up with recently that might work in = your case too.

In one comp i have a "Linker Camera" that i have setup as the = camera that is all other comps cameras are linked to. And this "Linker = Cam" is parented to the 1 instance of an animated camera that can be = imported from eg Cinema4D, just remember to hold Shift while parenting = the "Linker Cam" to the animated camera so it will take on the transform = values from the animated camera, then i have expression on all relevant = parameters and extract them with the "parent." method.

maybe its easier to = follow just taking a look at a simplified project. 
in "Comp 1" you find the only cameras you need to adjust, the = "Linker Cam" you shift+parent to what imported camera you have here, = cameras in Comp 2 and Comp 3 will follow.

https://adobe.ly/2y7w7VL

hope this maybe can help = in future projects :-)



Den man. 24. sep. 2018 = kl. 18.24 skrev David Torno <AE-List@media-motion.tv>:
Hi Chris,

What exactly are you trying to accomplish? This sounds like a = script automation thing so far. You want to replicate a camera build in = all comps?



David Torno
818.391.6060
--------------------
www.sydefxink.com (work history)
https://vimeo.com/davidtorno (work samples & = breakdowns)
https://gumroad.com/davidtorno
http://provideocoalition.com/dtorno = (tutorials)

"The most useless = day is that in which we do not laugh"
-Charles = Field

On Sep 23, 2018, = at 10:42 PM, Chris Zwar <AE-List@media-motion.tv> wrote:

Yes, if I was starting fresh I=E2=80=99d do it that way, I = might go through the whole project and replace the cameras with ones = that have linked properties, just to tidy it up a bit.

I=E2=80=99m really just thinking out = lout, but basically if I have 10 comps with the same camera in them, and = I want to duplicate them all but then swap the camera, then I=E2=80=99m = still manually copying & pasting 10 times.  I keep wanting to = do something like an alt-drag / replace footage but with a camera.  = I=E2=80=99m only thinking about it now because many of my comps have = nulls and location markers parented to the camera, so even pasting a new = camera into the composition means I=E2=80=99m having to manually = re-parent.

On 24 Sep 2018, at 1:34 pm, = Phil Spitler <AE-List@media-motion.tv> = wrote:

Seems like the you could just copy the camera with linked = properties into each comp.

Seems really clean and efficient workflow to me.

Phil


3D"bonfire-logo"
Phil = Spitler  Creative = Technologist
t  415.394.8200  c  415.571.31393D""3D""3D""3D""



On Sep 23, 2018, at 6:38 PM, Chris Zwar <AE-List@media-motion.tv> wrote:

Hi all,

Just = wanting to pick the collective brains on how everyone is keeping track = of multiple cameras in large projects.  I like to think my projects = are well organised but this is one thing that I haven=E2=80=99t cracked = yet.

Currently I=E2=80=99m working on a = sequence that has over 20 shots in it, compositing multipass-renders = from 3D.  I get a camera for each shot, which I=E2=80=99m then = using to roll out multiple FX that are being generated in After Effects = for the composites.  I would guess that each camera is used in 10 - = 15 additional precomps for each shot.

The = problem is that as the animation progresses, the cameras are often = changed and updated.  Swapping out 3D renders is simple, but so far = I=E2=80=99m importing each new camera and manually pasting it into each = composition.  This means I can miss comps because the process is = manual.  And as the new cameras have new names, this can also break = expressions and parenting.

In previous = projects I=E2=80=99ve had a =E2=80=9Cmaster=E2=80=9D camera that I=E2=80=99= ve then linked to with expressions to create a version that I can roll = out in precomps, and always use that one instead.  If I planned = ahead a bit better I would have done that here, but it=E2=80=99s not = something I=E2=80=99ve done with 20+ shots, each with individual = cameras.

Does anyone have a better & = cleaner method than making a master camera comp that is always linked to = via expressions?


-Chris
+---End of message---+
To unsubscribe send any = message to <ae-list-off@media-motion.tv>



= --Apple-Mail=_8C0DBD10-C26B-4291-A392-06F6516CD284--