From: "Brian Higgins" Received: from mail-pg0-f50.google.com ([74.125.83.50] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6328862 for AE-List@media-motion.tv; Mon, 02 Oct 2017 16:49:48 +0200 Received: by mail-pg0-f50.google.com with SMTP id b192so3681pga.2 for ; Mon, 02 Oct 2017 07:51:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flavor-tv.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=5kZssaYpzg7/x9NlpyP9litf4dbgZ4EUdPODRNKEFqU=; b=IldDbWDv8I5x3OeUl23M3sr+fLzziFc87Pue9UR10A+lmqVl7G203tgtlrETvPyTta iARjibBsuRvJR9pRSlK+FezNW6J82sGXqVJPVcauJt5POMXKwiBtXyhbTTw7UjlYnQNQ nTf4wsOVSlwCnHaPsYBlBAghJ5OdnvC3b2J5o6qeorqE5GLJD3GqPtdXHPMXG7uh7sEb a/GGvR27pLt9aQA7R3y8c96gUe2ARY77JhSFJ8PvUdg5+6xwcPnrhMUn7XUvqQe/GFgl oYoWEiRp7fOufjdPzXwfdHVEhE/ixgyCO9lI0dTvx8i9EL9jorwF15xwW8W30DeBuyzv 8R8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=5kZssaYpzg7/x9NlpyP9litf4dbgZ4EUdPODRNKEFqU=; b=f0tBhvT4K0VvPmEw1sHYve5MON9A23jmUHFBk34xOB0G8SN16Am9zWed4kvTryyw7/ 4yYanUX8EJrHasgkz+9OtZ+en5Pr4a7dbH3iHUK9uvs6q9ed0MAHxgSdTHbNcQGXPoo6 oE7YL08hzvfRbwypXq1+lxDmDtQv5RnDnEhs1KFHnqNBpkxR91k/tx2YK+DLnqsR3aih auLMIs408Wlu24EDF6PQ7nM5mu9lqlr39jXQDAsXei1szV8qyHKt1cO0jGLZ2aSjL0Yx jMkDt57libDqHjDdIvfRjO34/OWvrTkmr9tbt9UUMmRvpeyjnWfAxTv07jUvkf6sWcJv 2/jA== X-Gm-Message-State: AHPjjUgfgqJzuQjyBzE+IdhLzMn+vbhxCh1aOuJACntpQcy3VuLCOhY7 l6dgxniShzgIIDfX0fga3rFEDrXw+lZX6EjeudXS X-Google-Smtp-Source: AOwi7QDdBTuHqYCQkJ05lEG+OMVIEdgBCYWGa1Z1v4FnFpyTR8nAdh8T9K63vQZN1CStTBKdZ0i9Ka139RNEYYRsTIg= X-Received: by 10.99.115.30 with SMTP id o30mr12694882pgc.449.1506955892796; Mon, 02 Oct 2017 07:51:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.237.143 with HTTP; Mon, 2 Oct 2017 07:51:12 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Oct 2017 09:51:12 -0500 Message-ID: Subject: Re: [AE] 3:2 pulldown, frame blending, and camera tracking To: After Effects Mail List Content-Type: multipart/alternative; boundary="f403045c6530aec4d4055a91820b" --f403045c6530aec4d4055a91820b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Can you blow up the 23.98 SD and track it in HD? It'll probably work. -b On Mon, Oct 2, 2017 at 9:49 AM, Byron Nash wrote: > Yes, we air interlaced. I think what's messing this up is the need to > output in HD from a SD source plus the time stretch. Camera tracker doesn= 't > work on stretched footage, and when I collapse the precomp it screws up t= he > camera. I need the text clean, not scaled from SD. > > On Sat, Sep 30, 2017 at 12:55 PM Jim Curtis > wrote: > >> Do you broadcast interlaced? >> >> Once I=E2=80=99ve converted my 29.97 interlaced to 23.976, I render it o= ut at >> that frame rate and leave it there. I can reintroduce the pulldown and >> fields later if necessary, but it=E2=80=99s rarely necessary. One of my= spot >> delivery services demanded 59.94 for a while; then they relaxed it and >> started taking 23.976. >> >> This is pretty basic, so I suppose you know that if you have interlaced >> footage, it=E2=80=99s best practice to put it in a comp that=E2=80=99s d= ouble the frame >> rate - 59.94 so that you are tracking or roto-ing the fields separately = as >> frames. You can recombine the fields later in output. >> >> >> >> >> >> On Sep 29, 2017, at 3:58 PM, Byron Nash wrote: >> >> We get a lot of older SD footage here that we up-res to HD for our >> network broadcast. Some shot need camera tracking, roto, and vfx. I have= a >> shot that is confounding me and wanted to see what steps some of you wou= ld >> take differently. >> >> Here's my normal procedure for dealing with footage shot on 24 and comin= g >> to us at 29.97. >> >> 1. remove 3:2 pulldown and interpret fields correctly >> 2. put footage in a 23.976 comp >> 3. enable any speed changes and enable pixel motion frame blending >> 4. perform roto and tracking >> 5. render to 29.97 with 3:2 pulldown and appropriate fields >> >> The goal is to work on the footage in it's original cadence. We often ge= t >> shots that have been scaled or stretched in time.This greatly exacerbate= s >> the issue. This brings me to my current problem. I'm trying to camera tr= ack >> a shot that is SD and has time stretch. I want the tracked in graphic to= be >> overlayed in a HD comp. However, the camera tracker doesn't want any >> scaling done to the shot first. I know this is an order of operations >> problem. Just having trouble getting the pieces lined up. >> >> Thanks for any input. >> >> Byron >> >> >> --=20 brian higgins | creative director Flavor ny =E2=80=A2 chicago =E2=80=A2 la =E2=80=A2 detroit =E2=80=A2 tokyo 312.706.5500 brian.higgins@flavor.tv flavor.tv --f403045c6530aec4d4055a91820b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can you blow up the 23.98 SD and track it in HD? It'll= probably work.

-b

On Mon, Oct 2, 2017 at 9:49 AM, Byron Nash = <AE-List@media-motion.tv> wrote:
Yes, we air interlaced. I think what's m= essing this up is the need to output in HD from a SD source plus the time s= tretch. Camera tracker doesn't work on stretched footage, and when I co= llapse the precomp it screws up the camera. I need the text clean, not scal= ed from SD.

On Sat, Sep 30, 2017 at 12:55 PM Jim Curtis &= lt;AE-List@med= ia-motion.tv> wrote:
Do you broadcast interlaced?
Once I=E2=80=99ve converted my 29.97 interlaced to 23.976, I render= it out at that frame rate and leave it there.=C2=A0 I can reintroduce the = pulldown and fields later if necessary, but it=E2=80=99s rarely necessary.= =C2=A0 One of my spot delivery services demanded 59.94 for a while; then th= ey relaxed it and started taking 23.976.

This is pretty = basic, so I suppose you know that if you have interlaced footage, it=E2=80= =99s best practice to put it in a comp that=E2=80=99s double the frame rate= - 59.94 so that you are tracking or roto-ing the fields separately as fram= es.=C2=A0 You can recombine the fields later in output.




On Sep 29, 2017, at 3:5= 8 PM, Byron Nash <AE-List@media-motion.tv> wrote:

We get a lot of older SD footage here that we up-res to HD for our net= work broadcast. Some shot need camera tracking, roto, and vfx. I have a sho= t that is confounding me and wanted to see what steps some of you would tak= e differently.=C2=A0

Here's my normal procedure for = dealing with footage shot on 24 and coming to us at 29.97.
    remove 3:2 pulldown and interpret fields correctly
  1. put footage in= a 23.976 comp
  2. enable any speed changes and enable pixel motion fra= me blending
  3. perform roto and tracking
  4. render to 29.97 with = 3:2 pulldown and appropriate fields
The goal is to work on th= e footage in it's original cadence. We often get shots that have been s= caled or stretched in time.This greatly exacerbates the issue. This brings = me to my current problem. I'm trying to camera track a shot that is SD = and has time stretch. I want the tracked in graphic to be overlayed in a HD= comp. However, the camera tracker doesn't want any scaling done to the= shot first. I know this is an order of operations problem. Just having tro= uble getting the pieces lined up.

Thanks for= any input.=C2=A0

Byron




--
=

brian higgins | creative director

Flavor

ny =E2=80=A2 chicago =E2=80=A2 la =E2=80=A2 detr= oit =E2=80=A2 tokyo

312.706.5500

brian.higgins@flavor.tv

flavor.tv


--f403045c6530aec4d4055a91820b--