From: "Jim Curtis" <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DBEE2F2D-4A77-46CD-8983-0F89CD64F9F6"
Message-Id: <7521AF8D-169D-498D-B713-442ED7B9741D@flash.net>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [AE] 3:2 pulldown, frame blending, and camera tracking
Date: Sat, 30 Sep 2017 11:54:42 -0500
References: <list-6327161@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>
In-Reply-To: <list-6327161@media-motion.tv>


--Apple-Mail=_DBEE2F2D-4A77-46CD-8983-0F89CD64F9F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

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.  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 =
double 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 <AE-List@media-motion.tv> =
wrote:
>=20
> 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 =
would take differently.=20
>=20
> 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
> put footage in a 23.976 comp
> enable any speed changes and enable pixel motion frame blending
> perform roto and tracking
> 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 =
get shots that have been scaled 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 trouble getting the pieces =
lined up.
>=20
> Thanks for any input.=20
>=20
> Byron


--Apple-Mail=_DBEE2F2D-4A77-46CD-8983-0F89CD64F9F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Do you broadcast interlaced?</div><div =
class=3D""><br class=3D""></div>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. &nbsp;I can reintroduce the pulldown and fields later if =
necessary, but it=E2=80=99s rarely necessary. &nbsp;One of my spot =
delivery services demanded 59.94 for a while; then they relaxed it and =
started taking 23.976.<div class=3D""><br class=3D""></div><div =
class=3D"">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 frames. &nbsp;You can recombine the =
fields later in output.<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Sep 29, 2017, at 3:58 PM, =
Byron Nash &lt;<a href=3D"mailto:AE-List@media-motion.tv" =
class=3D"">AE-List@media-motion.tv</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">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 would take differently.&nbsp;<div class=3D""><br =
class=3D""></div><div class=3D"">Here's my normal procedure for dealing =
with footage shot on 24 and coming to us at 29.97.</div><div =
class=3D""><ol class=3D""><li class=3D"">remove 3:2 pulldown and =
interpret fields correctly</li><li class=3D"">put footage in a 23.976 =
comp</li><li class=3D"">enable any speed changes and enable pixel motion =
frame blending</li><li class=3D"">perform roto and tracking</li><li =
class=3D"">render to 29.97 with 3:2 pulldown and appropriate =
fields</li></ol><div class=3D"">The goal is to work on the footage in =
it's original cadence. We often get shots that have been scaled 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 =
trouble getting the pieces lined up.</div></div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks for any input.&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D"">Byron</div></div>
</div></blockquote></div><br class=3D""></div></div></body></html>=

--Apple-Mail=_DBEE2F2D-4A77-46CD-8983-0F89CD64F9F6--

.