From: "Greg Balint" Received: from mail-yb1-f173.google.com ([209.85.219.173] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7176054 for ae-list@media-motion.tv; Fri, 19 Oct 2018 17:02:15 +0200 Received: by mail-yb1-f173.google.com with SMTP id d9-v6so13369937ybr.12 for ; Fri, 19 Oct 2018 08:14:08 -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:in-reply-to:references :user-agent; bh=XXrPFfaBwjV5wl0p0IbXLHn3lwube5dTvA8fhfz1GgA=; b=PMgdeNnDX8UpdOCzmTTs9L+UR9DG9R85gMIbIhgMFAbTRwRYkop+/TEQ3Vskr5WJ30 gaLkBe9V4bnr1ic/yI7wzVjwOr05sSYVGwCEiSfxuRRx9Boy6UgWOuRVQFlCoZms8Inn d6vsTtkYjYboj3o1XE73mrnKwLMeVnv58H17nKqjVqQ0LWQTFhRCUtwqPbXfbzu/ScPj NiBXYBZVk0t7GYGlicF3UlPc2svt14RPHPcjckHVyJm/TLTyWhjctUOUqTOMplfKcRx2 6pX3azarFuot2VIVQQVJDGoCrgbyIHWSWiCSL1rS60iJ70M0evFfIBADHved8Wzser93 6BJw== 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 :in-reply-to:references:user-agent; bh=XXrPFfaBwjV5wl0p0IbXLHn3lwube5dTvA8fhfz1GgA=; b=pjckgTGhJX5+DGT06xSdJxI/8SAQdcxrySJeA9yz3Goc+ExIfiZUs4C4roZLi0oa9v ZyG7/m40Cb7jWxKltWhfoW7/mtwvhR4T24iMr7Z47ohgzfs2o0niqjUEW1278WvBu38e /EKrCC6UEZglmj7Jnk2hYP2bcnRDCAJqwgdGmbhK+N22H52Y0JirAalIVzf5Ak4tKo62 IadT7uvNPDCuXee6WvwPdv1qF0WiJI3TbwNCXomJn/SlInYsp2KA+veuImAdDcknHcM2 dRVecENOVxssXQ7GGt/4FgfK/CkwtjJmMQ1jd3yrJcUUiGxiyWK6Sh0+uB8Oe+Io8FJy 9RXw== X-Gm-Message-State: ABuFfoh8+eja73FsutBIGZJAxlCumnN7ehzQbVI1CG8Hz6eJ875IPIIC KSXDVSl+LOWT24iuX7a4JhL2vI/O X-Google-Smtp-Source: ACcGV60M8SK2HBPoWe086pzJo5YmVy+ZViF5u7c/EX6TkEqHbUmWChOJpUMgm+s4cYkIhJOXaXW4wA== X-Received: by 2002:a25:cd06:: with SMTP id d6-v6mr23807841ybf.500.1539962046539; Fri, 19 Oct 2018 08:14:06 -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 x185-v6sm7855929ywd.40.2018.10.19.08.14.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 08:14:05 -0700 (PDT) Content-Type: multipart/alternative; boundary="----=_NextPart_35663959.330428309603" MIME-Version: 1.0 Date: Fri, 19 Oct 2018 11:13:44 -0400 Message-ID: <41c8b80e-aef1-4ea4-96da-8d261ee9a02b@getmailbird.com> Subject: Re: [AE] Improper Timecode Issues in AE v16.0.0 To: "Robert Kjettrup" In-Reply-To: References: User-Agent: Mailbird/2.5.20.0 X-Mailbird-ID: 41c8b80e-aef1-4ea4-96da-8d261ee9a02b@getmailbird.com ------=_NextPart_35663959.330428309603 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable You're right, Robert.. I just caught that.. =C2=A0 Kinda figured they'd all= be named properly in there. I had a quick chat with Adobe Customer Support about the timecode issue, an= d they said that the engineering team knows about this specific bug, and is= working on it. =C2=A0So hopefully we'll see a little hot-fix update someti= me soon with that being addressed. =C2=A0I don't know if it happens for oth= er footage or if the MXF files were what is posing the problem. =C2=A0Good = idea to keep it in mind if you ever do this sort of trimming of footage in = AE.=C2=A0 ///Greg Balint //Art Director / Motion Graphics Designer /321.514.4839 delRAZOR.com [http://www.delrazor.com/]/ On 10/19/2018 11:09:33 AM, Robert Kjettrup wrote: The link you sent does show an "After Effects" in Chrome here for me, its n= ot 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 Effect= s? 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 [https:/= /www.adobe.com/products/wishform.html] Doesn't even have After Effects avai= lable for reporting there. The official linkage to "feedback" from the app itself, sends you to the Us= evoice 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 [http://www.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 thes= e clips I was handed. The shots were all trimmed incorrectly, usually skipp= ing 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 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. Just opened the same f= ootage in v15.1.2 and it had no problem with timecode syncing to the correc= t spot in the mxf files. So this seems to be a problem with v16.0.0 current= ly. Just wanted to give everyone a heads-up about this in case you're taking ti= mecodes from clients and trimming things in AE. 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_35663959.330428309603 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
You're right, Robert.. I just caugh= t that..   Kinda figured they'd all be named properly in there.
I had a quick chat with A= dobe Customer Support about the timecode issue, and they said that the engi= neering team knows about this specific bug, and is working on it.  So = hopefully we'll see a little hot-fix update sometime soon with that being a= ddressed.  I don't know if it happens for other footage or if the MXF = files were what is posing the problem.  Good idea to keep it in mind i= f you ever do this sort of trimming of footage in AE. 






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

On 1= 0/19/2018 11:09:33 AM, Robert Kjettrup <ae-list@media-motion.tv> wrot= e:

The link you sent does show an "After Effects&q= uot; in Chrome here for me, its not named with "Adobe" in front o= f the name as other items on that dropdown list though.

Den fre. 19. okt. 2018 kl. 16.51 skrev Gr= eg Balint <AE-List@media-moti= on.tv>:
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 sen= t 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, t= hen do some compositing, tracking, logo removal, and send the shortened cli= ps back.

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

Apparently, v= 16.0.0 doesn't handle timecode properly, or at least with these clips I= was handed.=C2=A0 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 the= re, place them on a timeline, and then save that project and import that Pr= emiere project into AE where I had the right trim points. (Although the tri= mmed points were correct, the timecodes on these were way off in AE from wh= at the client provided)

=
I've fixed my issue with a workarou= nd for this morning's fires to be put out, and now I've started to = look into the 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 fil= es.=C2=A0 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 taki= ng timecodes from clients and trimming things in AE.=C2=A0

I&#= 39;ll go find the proper channels to report this bug with the AE team and h= opefully get it patched out soon.


///Greg Balint
//Art Director / Mo= tion Graphics Designer
/321.514.4839
delRAZOR.com/
------=_NextPart_35663959.330428309603--