From: "Robert Kjettrup" Received: from mail-lf1-f43.google.com ([209.85.167.43] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7176060 for AE-List@media-motion.tv; Fri, 19 Oct 2018 16:57:00 +0200 Received: by mail-lf1-f43.google.com with SMTP id x24-v6so9754410lfe.5 for ; Fri, 19 Oct 2018 08:08:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2knIJ8Qgw+aj0usdj4DXf1oX9CQft50WRkPZN4JMoDE=; b=PXFxkeUyRJj8vWv0sN//0W8zdfiM9QVfFjl5HyOTq6YqlwhaOkkw42svrrKAjnROVt FGB4TLHZ0lt4Dy9eL/4+OQ1yeI2cyMWdw/aP8D2coIzE0gzq4o9/JM6Hn+h6e4Y8kAc7 lkPE5Tm2LSxxlgTdiWN1gX44r6r7SeibYMM08j7/hZUU7FrlzWAHBoY3yT3dOauNr1eB 1lLrbCgt4l7lbmSwGZqBdtNnSkb5a1wKnTOXqqUc9M2rfxM5R4EwMBwGdbYX9SxgWMaC 80QxGPBSxwXHSs8Bas8IdCTZ9WvpR+SBhu7XO/VSCROzvlfMcO5SW93FmJ2dmAhaK5MQ Zxfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2knIJ8Qgw+aj0usdj4DXf1oX9CQft50WRkPZN4JMoDE=; b=VUudL5GNWOsoVfgIFu9jofrcdbBs3pyEDnK8jreLw1ISDEsvNaKg0/qJ9+mIRiLEsC nldEF85XCcgw/71chdHQD4m+YlpbN5lmTUizlfcg2+tJXPrCxoQ7ujAj1+06WyA3efU8 o7r+JtdaHJAjo/7WnvMQdoXCuxR2xrjbSQPgLC9EtDHvQSQEbkimmDj6v0wLUewYaxTu xj0Mdr7kuY+1KsjutuJsKWcfE+xk2mzAcsJ/sAg+WQ1+ZIm24lAXTAxPwY7jFNkAFa/b h39aj8u430pPSoGVJKIAuUQGljDOfmOS+sfgFN/9O7gqIQqOcXESK72KSzihgx3d7Ynt F6Bw== X-Gm-Message-State: ABuFfogNjk5lx5o9Rf4DMuelq/+zyNPa6nbxgsE+1zCXjd8soREqzGVC nuLib+z2uwcoUgff2qoXwFVvPAvUTTAJvubZ+hBnLw== X-Google-Smtp-Source: ACcGV617lMNng6k7rqQHFpHR+eywvNb1ZhNbb4JZ6I3xCl14NT2X1oHq2CAHHw06sfq3Ke05+K27CLR26RFCuPjgpLA= X-Received: by 2002:a19:cd81:: with SMTP id d123-v6mr3425327lfg.104.1539961732183; Fri, 19 Oct 2018 08:08:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 19 Oct 2018 17:08:43 +0200 Message-ID: Subject: Re: [AE] Improper Timecode Issues in AE v16.0.0 To: After Effects Mail List Content-Type: multipart/alternative; boundary="00000000000003bc5f0578964836" --00000000000003bc5f0578964836 Content-Type: text/plain; charset="UTF-8" The link you sent does show an "After Effects" in Chrome here for me, its not named with "Adobe" in front of the name as other items on that dropdown list though. Den fre. 19. okt. 2018 kl. 16.51 skrev Greg Balint : > On a related note.. Where is the best place to report bugs for After > Effects? I'm finding some pages that don't even list AE as a possible > program to report a bug about.. > > Like this form here - https://www.adobe.com/products/wishform.html > Doesn't even have After Effects available for reporting there. > > The official linkage to "feedback" from the app itself, sends you to the > Usevoice site, Which doesn't feel like a place I should be submitting bugs > to as things must be "voted on" to be seen or have importance. > > ///Greg Balint > //Art Director / Motion Graphics Designer > /321.514.4839 > delRAZOR.com / > > On 10/19/2018 10:37:26 AM, Greg Balint wrote: > 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 points. > I was to trim them down to those exact time-spans, then do some > compositing, 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. > > Apparently, v16.0.0 doesn't handle timecode properly, or at least with > these clips I was handed. The shots were all trimmed incorrectly, usually > skipping between 100 to 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 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 > 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 timecode 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 everyone a heads-up about this in case you're taking > timecodes from clients and trimming things in AE. > > I'll go find the proper channels to 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 / > > --00000000000003bc5f0578964836 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The link you sent does show an "After Effects" i= n Chrome here for me, its not named with "Adobe" in front of the = name as other items on that dropdown list though.

Den fre. 19. okt. 2018 kl. 16.51 skrev Greg Bal= int <AE-List@media-motion.tv<= /a>>:
On a related note.. Where is the be= st place to report bugs for After Effects?=C2=A0 I'm finding some pages= that don't even list AE as a possible program to report a bug about..= =C2=A0

Like this form here -=C2=A0https://www.adobe.com/= products/wishform.html =C2=A0Doesn't even have After Effects availa= ble for reporting there. =C2=A0

The official linkage= to "feedback" from the app itself, sends you to the Usevoice sit= e, Which doesn't feel like a place I should be submitting bugs to as th= ings must be "voted on" to be seen or have importance.

///Greg Balint<= br>//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/

On 10/19= /2018 10:37:26 AM, Greg Balint <ae-list@media-motion.tv> wrote:

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=A0 I was to trim them down to those exact time-spans, then d= o some compositing, tracking, logo removal, and send the shortened clips ba= ck.

Unfortunately, I stumbled across a pretty glaring bug in the = latest version of AE while doing so.=C2=A0

Apparently, v16.0.0 do= esn't handle timecode properly, or at least with these clips I was hand= ed.=C2=A0 The shots were all trimmed incorrectly, usually skipping between = 100 to 130 frames of the in-point my client actually needed.

My solu= tion 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 pr= oject into AE where I had the right trim points. (Although the trimmed poin= ts were correct, the timecodes on these were way off in AE from what the cl= ient provided)

I've fixed my issue with a workaround for this= morning's fires to be put out, and now I've started to look into t= he issue more.=C2=A0 Just 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=A0 S= o 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 timecodes = from clients and trimming things in AE.=C2=A0

I'll go find th= e proper channels to report this bug with the AE team and hopefully get it = patched out soon.


///Greg Balint
//Art Director / Motion Graphics De= signer
/321.514.4839
d= elRAZOR.com/
--00000000000003bc5f0578964836--