From: "Greg Balint" Received: from mail-yw1-f42.google.com ([209.85.161.42] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7176043 for ae-list@media-motion.tv; Fri, 19 Oct 2018 16:24:38 +0200 Received: by mail-yw1-f42.google.com with SMTP id g4-v6so249316ywe.11 for ; Fri, 19 Oct 2018 07:36:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:date:message-id:subject:from:to:user-agent; bh=SILpVfK0TTsFnKRWyFPoxoJ9Bk5YD48lJ4QF3EpkVJ8=; b=JFiVD3vaXfFJ/oGc8FGHCn1DwfTIoxK9UXhp9Lq64csvVZq/s1ud8uTCjDAthIV6Uv qQpWwz8KEZVZME2i5ESH2LAfE0AWPTfbnKi5W4PVifkA9niYqMU9iynWwlcZ9ZAhAJN9 pxxi2IA6ndLBPodwLqzruzvVuEZxn1faH1+i45DKV+WFnAIsKn9WvkgpwIzxVQzAml4x riAprQqCW1GAf77y6mJhBVbpfqdAfiPTYI2MUDh9lzu1eFT0UiHSvfZ0D/w8U3qK8Nxb TjVsgVuW98iiNF5yDak2Mdyu3ZmiaIfow+gc+hqyOGZD9ykiY1wjED1IkvZTi4bZMsvP azTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :user-agent; bh=SILpVfK0TTsFnKRWyFPoxoJ9Bk5YD48lJ4QF3EpkVJ8=; b=tzPaIIXdxYTyafLoAYe46VhuvBFA8PUG1ZtuAtYkMLN3HldKRdTd72hppNT95gjsig +scQK+kMlzBwQGPURmzLXkfxen/l3eoILnzQSNG6IcgMV8ameQI3+ayIMa1RTd2Qovgu HwxWPmfIZkMSglncEX+qCJb+uhiVurKo94wV4VMGr1yWDojO8WiKsNYwuYt+LLLdYMJp KxsjHnWUah+bMsZA2vJsshsCZ51LIXo4zPQAGsijqznAmh2N88A7e7GLb1AcQ23jC+/d x+v5G5WVQIVm3yYvubLKtb8gDpFuxVOY7TxtasjT/0o/89Lri9hRarGmv3OUGufKMOjv 3F0A== X-Gm-Message-State: ABuFfoi6RPPwuayyj9zDD/+36of1W2kZgO8QnzV7nZ16DMb0p3wvHRYo 7rtssm1dnsqsrz3nmlAAB8fLMvIl X-Google-Smtp-Source: ACcGV63E4qgA/z5cuY91BI41M60EvMG3zI7gslzp2zbRRumvr0pZFeJrzOAxKEzMysE8c++uaS/w0w== X-Received: by 2002:a0d:cc4b:: with SMTP id o72-v6mr22709349ywd.147.1539959788900; Fri, 19 Oct 2018 07:36:28 -0700 (PDT) Return-Path: Received: from [192.168.1.9] (static-host-66-18-44-215.epbinternet.com. [66.18.44.215]) by smtp.gmail.com with ESMTPSA id l30-v6sm14455579ywa.104.2018.10.19.07.36.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 07:36:28 -0700 (PDT) Content-Type: multipart/alternative; boundary="----=_NextPart_43055627.010023401420" MIME-Version: 1.0 Date: Fri, 19 Oct 2018 10:36:06 -0400 Message-ID: <4749530a-37fa-4da9-a76b-e6b8aab9e2c1@getmailbird.com> Subject: Improper Timecode Issues in AE v16.0.0 To: "Dennis Wilkins" User-Agent: Mailbird/2.5.20.0 X-Mailbird-ID: 4749530a-37fa-4da9-a76b-e6b8aab9e2c1@getmailbird.com ------=_NextPart_43055627.010023401420 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hey all..=C2=A0 I ran into an issue today with some clips a client sent me.=C2=A0 They sent me 6 MXF files and a document with timecode in and out points. = =C2=A0I was to trim them down to those exact time-spans, then do some compo= siting, tracking, logo removal, and send the shortened clips back. Unfortunately, I stumbled across a pretty glaring bug in the latest version= of AE while doing so.=C2=A0 Apparently, v16.0.0 doesn't handle timecode properly, or at least with thes= e clips I was handed. =C2=A0The shots were all trimmed incorrectly, usually= skipping between 100 to 130 frames of the in-point my client actually need= ed. My solution at the time was to open the clips in Premiere.. trim them there= , place them on a timeline, and then save that project and import that Prem= iere project into AE where I had the right trim points. (Although the trimm= ed points were correct, the timecodes on these were way off in AE from what= the client provided) I've fixed my issue with a workaround for this morning's fires to be put ou= t, and now I've started to look into the issue more. =C2=A0Just opened the = same footage in v15.1.2 and it had no problem with timecode syncing to the = correct spot in the mxf files. =C2=A0So this seems to be a problem with v16= .0.0 currently. Just wanted to give everyone a heads-up about this in case you're taking ti= mecodes from clients and trimming things in AE.=C2=A0 I'll go find the proper channels to report this bug with the AE team and ho= pefully get it patched out soon. ///Greg Balint //Art Director / Motion Graphics Designer /321.514.4839 delRAZOR.com [http://www.delrazor.com/]/ ------=_NextPart_43055627.010023401420 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hey all.. 

I ran into an issue today with some clips a client sent me. = ;

They sent me 6 MXF files and a document with timecode in and out p= oints.  I was to trim them down to those exact time-spans, then do som= e compositing, tracking, logo removal, and send the shortened clips back.

Unfortunately, I stumbled across a pretty glaring bug in the lat= est version of AE while doing so. 

Apparently, v16.0.0 doe= sn't handle timecode properly, or at least with these clips I was handed. &= nbsp;The shots were all trimmed incorrectly, usually skipping between 100 t= o 130 frames of the in-point my client actually needed.

My solution = at the time was to open the clips in Premiere.. trim them there, place them= on a timeline, and then save that project and import that Premiere project= into AE where I had the right trim points. (Although the trimmed points we= re correct, the timecodes on these were way off in AE from what the client = provided)

I've fixed my issue with a workaround for this mornin= g's fires to be put out, and now I've started to look into the issue more. =  Just opened the same footage in v15.1.2 and it had no problem with ti= mecode syncing to the correct spot in the mxf files.  So this seems to= be a problem with v16.0.0 currently.

Just wanted to give every= one a heads-up about this in case you're taking timecodes from clients and = trimming things in AE. 

<= /div>
I'll go find the proper channels t= o report this bug with the AE team and hopefully get it patched out soon.


///Greg Balint
/= /Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/
------=_NextPart_43055627.010023401420--