From: "Teddy Gage" Received: from mail-ot1-f42.google.com ([209.85.210.42] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7176080 for AE-List@media-motion.tv; Fri, 19 Oct 2018 17:28:24 +0200 Received: by mail-ot1-f42.google.com with SMTP id 14so29609906oth.2 for ; Fri, 19 Oct 2018 08:40:17 -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=cxggopfdBu/RsrCnhYCg5s1BI+4giDUEGjVbRUyuqZs=; b=Xmqx6tNuwgFOE0yRfH+w5fB+2zmvofPGfekfWu+RhbTcpKz1jtn9K6T9FJWrSS65gV G944PVMZwp0mWuTX3GjARRvVu+v3V0D6YIVh4OjLmj5XS6PX69oeBpUjdp1UApq3a1ZM 3kHSR4fdtTcRN+DE9+MiIQTcwGR30Q0ui5E6KYy0ptGfeBsAFygT1UteT6hsreNLbSzp ECErB/SU5tEedH2Oj2xMtGfr8cborjJZw5/crXDktvNdgjCa+pvaUtDldr29mlJnbQgx jaTUAh4rPJK9awbptp1ManVYimGesaBG1fd7WkqDsWyZ9h41Yd4W53B507vrGESHXliW 1uyQ== 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=cxggopfdBu/RsrCnhYCg5s1BI+4giDUEGjVbRUyuqZs=; b=KKkMM41Ah66h42R0qrydVLAociRB4dxrIoeQnzw3uaNk+6ayPK5X+BJxPnGYvn03Cv hYmzFnyZKUXH74CdJVJkyOevfEFC9HJzZeiVnfCHgwih41J3R2/sBULC4kaXxmnY2Un2 96fjFpXuKeh+LhE94AP1nwgQuxYAl7BceTLSXU9U6pNddLtxRWgTgw941nTp9IAKUiYc 1IjJodo25j3SUqQ7btYddKXY9V51FvplrQbjqiYVMAjwbHOvxejKXhEQ2nR7GfKBXIsu E741nCELOGbaX9N5RaUBctbxoPx7h4lstUDVfbIuuxq3wDxlymWcmgrkO7k66mM6xumd 7Zgw== X-Gm-Message-State: ABuFfojPxgwNOB/vkWSckGZJtWrqB8nBEKh6nqZeqoPdd/TnlsiXtCKe 4TcSkJ43I7WtI+6x6WQgDIzAm+kua7aa6J1urX2zyQ== X-Google-Smtp-Source: ACcGV61SA3sIniFczATyXnrqRTggc8G0d4TMXFkos1Bt+W6ODyUKBs6Qp8hL54dCn2Ws1ELHOTpyWXm89sXael+A1is= X-Received: by 2002:a9d:59ae:: with SMTP id u46mr21113010oth.243.1539963615616; Fri, 19 Oct 2018 08:40:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 19 Oct 2018 11:39:39 -0400 Message-ID: Subject: Re: [AE] Improper Timecode Issues in AE v16.0.0 To: After Effects Mail List Content-Type: multipart/alternative; boundary="00000000000046a25c057896b8de" --00000000000046a25c057896b8de Content-Type: text/plain; charset="UTF-8" wow that's a big one and potentially huge if you hadn't noticed. Could be easy to miss it with a lot of footage and no picture references. Good catch Greg On Fri, Oct 19, 2018 at 11:14 AM Greg Balint wrote: > You're right, Robert.. I just caught that.. Kinda figured they'd all be > named properly in there. > > I had a quick chat with Adobe Customer Support about the timecode issue, > and they said that the engineering 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 addressed. 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 if you ever do this sort of trimming of footage in AE. > > > > > > > ///Greg Balint > //Art Director / Motion Graphics Designer > /321.514.4839 > 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 > 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 < > AE-List@media-motion.tv>: > >> 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 / >> >> -- _____________________________ Teddy Gage President Shotgun Inc. 360 VR | MOGRAPH | VFX SHOTGUNPOST.COM BKLYN NY 11215 --00000000000046a25c057896b8de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
wow that's a big one and potentially huge if you hadn&= #39;t noticed. Could be easy to miss it with a lot of footage and no pictur= e references. Good catch Greg

On Fri, Oct 19, 2018 at 11:14 AM Greg Balint <AE-List@media-motion.tv> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
You're right, Robert.. I just c= aught 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, and they said that t= he engineering team knows about this specific bug, and is working on it.=C2= =A0 So hopefully we'll see a little hot-fix update sometime soon with t= hat being addressed.=C2=A0 I don't know if it happens for other footage= or if the MXF files were what is posing the problem.=C2=A0 Good idea to ke= ep it in mind if you ever do this sort of trimming of footage in AE.=C2=A0<= br>





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

On 10/19= /2018 11:09:33 AM, Robert Kjettrup <ae-list@media-motion.tv> wrote:

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 <= AE-List@media-= motion.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
//Art Director / Motion Graphics Designer
/321.5= 14.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 cli= ps a client sent me.=C2=A0

They sent me 6 MXF files and a document w= ith timecode in and out points.=C2=A0 I was to trim them down to those exac= t time-spans, then do some compositing, tracking, logo removal, and send th= e shortened clips back.

<= div style=3D"font-size:13.3333px">Unfortunately, I stumbled across a pretty= glaring bug in the latest version of AE while doing so.=C2=A0

Ap= parently, v16.0.0 doesn't handle timecode properly, or at least with th= ese clips I was handed.=C2=A0 The shots were all trimmed incorrectly, usual= ly skipping between 100 to 130 frames of the in-point my client actually ne= eded.

My solution at the time was to open the clips in Premiere.. tr= im them there, place them on a timeline, and then save that project and imp= ort that Premiere project into AE where I had the right trim points. (Altho= ugh 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 st= arted to look into the issue more.=C2=A0 Just opened the same footage in v1= 5.1.2 and it had no problem with timecode syncing to the correct spot in th= e mxf files.=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 taking timecodes from clients and trimming things in AE.=C2=A0

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


///Greg Bali= nt
//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/


--
________________= _____________
Teddy Gage
President
Shotgun Inc.
360 VR | MOGRAPH | VFX
BKLYN NY 11215

--00000000000046a25c057896b8de--