DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=crishdesign.com;
	h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-BWhitelist:X-Source:X-Source-Args:X-Source-Dir:X-Source-Sender:X-Source-Auth:X-Email-Count:X-Source-Cap;
	b=A8HUbrPCSv58f34Yvku0EPTyC1XK+/p/Nbf6C2dJHstby9jcX/YxWfSnCONti9PJB3G63mYKe3fgVJu6HdFtTaeKhgEfqsS5Rq7e4IBTeB8PooMWbgNOpwpaL5XpwHuP;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: [AE] 24fps workflow
From: Chris Meyer <chris@crishdesign.com>
In-Reply-To: <list-4670925@media-motion.tv>
Date: Thu, 29 Mar 2012 10:10:49 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABD948F6-A52D-4509-835A-06054D0AA6FE@crishdesign.com>
References: <list-4670925@media-motion.tv>
To: "After Effects Mail List" <AE-List@media-motion.tv>

If I was to add anything to this discussion, it is to be aware of audio =
sync if you move between 23.976 and 24. We got caught out once on a film =
job where we were delivered the music at the speed it was going to play =
in the film, but a telecine slowed-down video dub of the film to cut =
against the music (i.e. 24 dropped to 23.976) - which was then going to =
be sped back up on output. Things slipped by a frame here and there. You =
really need to get the people before and after you in the chain to spell =
out precisely what they did with the assets before they gave them to =
you, and precisely what they will do with them afterward. (Plus keep =
track of your own workflow - i.e. don't reconform the frame rate just =
for convenience of video monitor playback etc.; do it for a reason, and =
undo it before delivery if necessary.)

 - Chris


On Mar 29, 2012, at 9:57 AM, Eric James Wood wrote:

> As someone else replied, you should really only be using true 24p if =
you are going to film out. You could also use it if you know 100% in =
fact it is ever going to be used on the web, but why bother? iI our =
place, if we know we are not going to film(almost never), we do =
everything in 23.976. Easy enough to get to 29.97 if we have to.
>=20
> That being said, i do get a lot of footage at 59.94 from go pro's and =
canon dslr's. If there is not a ton of high speed stuff, i will drop =
into a 23.976 timeline and if it looks good and no jutter, i go with it. =
If i need to fix the jutters, i can mark all the frames where it jumps =
and use frame restorer on it. Learned that trick from i think it was =
steve o. on the list with some go pro footage. Please forgive me if it =
wasn't steve, and maybe jack t.
>=20
> On 2012.03.29, at 08.18, Byron Nash wrote:
>=20
>> We work a lot in 23.976 all the way from capture to master. We make =
29.97i copies for delivery to stations. Once or twice we tried 24p and =
had trouble getting the shots to play back from FCP through the AJA or =
Blackmagic cards. It seems to view stuff in a suite it needs to be =
23.976, 29.97, or 59.94 (for NTSC places that is).=20
>=20
> --=20
> <ericwood>
>    Helium14 | www.helium14.com
>    Design | Motion + Graphic
>    www.helium14.com
>=20
> 'the next best thing to knowing something, is knowing where to find =
it'
>=20
>=20
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>