From: "Greg Balint" Received: from mail-yw1-f41.google.com ([209.85.161.41] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7176055 for ae-list@media-motion.tv; Fri, 19 Oct 2018 16:38:39 +0200 Received: by mail-yw1-f41.google.com with SMTP id j202-v6so13266555ywa.13 for ; Fri, 19 Oct 2018 07:50:32 -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=tXZTEGxI5Plqm004fqnSS0d/HLd9GhnTmCoSTf/EULw=; b=Jhae78h6qC+5B3lQDx0xGio75Ht8RneywCM8DB9BeJ4cb3mETyZ/fmzAZlxS9106Uq gn7rLRqoKu/R2kfR4N9GSMl9UiiUtYkn00n0ACwrG1WfI5KFIh5wHFWi0CaCMSceKGwu E8NFP7de5upmtlA2NqOsVyoPBA5SZSVq8gvlF07AUX/QPXl0EDx4oxZBuyutQ1DOJ4SR 4DpQEzClAyg02J6/+2rhv7lb8YXZsBTwqdj+ZAbelYA7RqKJIzL1YbSD2AWOMUFyU4jq PgQv5uicxonOJI2tCOLTvv9avMbCi58De5S07ndM45DbBYlv4xB/qgP/3D/QoWiZ0Qv5 uJzg== 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=tXZTEGxI5Plqm004fqnSS0d/HLd9GhnTmCoSTf/EULw=; b=unq8UgUImhdfCEj0P4yxEUQB4n46W66sgEnsmJBgBlhohzd5+nhNEr4+k2BcSZtEG8 1iIibXvUhOGMDZaaMOfH3xBen35wmbaj3uf0VWUPjokh8BgoNB2+0Na9kDLOJtNIS5jP 1Wr1LDD6uriT0cAM91V1OdQkWGJWfHqNhq9EUzAPBMepTN+/hi74mlQeExdBiy6u3TWJ 28rrjNtqCfQrYJlMfvPximOpDg1AEcHg2VRjMhaO0BTvRjn93TXwFJ0Fq7lD70Dot7WO isXTTII5MEnQdVoiMU2T2tQR5Qz5J+Ni+NGc4nlurYbvzcj3sS7kV7aSu/JH2mwjZTBu 32jg== X-Gm-Message-State: ABuFfoid+CAs1ITerKfKFHUP6HfXBDjNu+zEDBbAgnoGKXxltjVKC6pF sGGZjN4Rk6uYdIEjJQu9bVlkvwAL X-Google-Smtp-Source: ACcGV62qA//XXEKDF7FiyrB/F+aHC1M/7YvvWP2RpqvdXB6Wi2LDpxN5jHwmU+RCuzQhcYEqa/3G2w== X-Received: by 2002:a81:3c57:: with SMTP id j84-v6mr23119177ywa.448.1539960631052; Fri, 19 Oct 2018 07:50:31 -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 p185-v6sm7236340ywc.14.2018.10.19.07.50.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 07:50:30 -0700 (PDT) Content-Type: multipart/alternative; boundary="----=_NextPart_61416146.648070397520" MIME-Version: 1.0 Date: Fri, 19 Oct 2018 10:50:09 -0400 Message-ID: <6e92706b-382c-45a9-b3b1-6198fd754d90@getmailbird.com> Subject: Re: [AE] Improper Timecode Issues in AE v16.0.0 To: "Greg Balint" In-Reply-To: References: User-Agent: Mailbird/2.5.20.0 X-Mailbird-ID: 6e92706b-382c-45a9-b3b1-6198fd754d90@getmailbird.com ------=_NextPart_61416146.648070397520 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On a related note.. Where is the best place to report bugs for After Effect= s? =C2=A0I'm finding some pages that don't even list AE as a possible progr= am 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 available for reporting there. =C2=A0 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..=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_61416146.648070397520 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
On a related note.. Where is the be= st place to report bugs for After Effects?  I'm finding some pages tha= t 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" fr= om 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 s= een or have importance.

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

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

Hey all.. <= /span>

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

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 s= ome compositing, tracking, logo removal, and send the shortened clips back.=

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

Apparently, v16.0.0 d= oesn'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 solutio= n at the time was to open the clips in Premiere.. trim them there, place th= em on a timeline, and then save that project and import that Premiere proje= ct 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 clien= t provided)

I've fixed my issue with a workaround for this mo= rning's fires to be put out, and now I've started to look into the issue mo= re.  Just opened the same footage in v15.1.2 and it had no problem wit= h timecode syncing to the correct spot in the mxf files.  So this seem= s to be a problem with v16.0.0 currently.

Just wanted to give e= veryone a heads-up about this in case you're taking timecodes from clients = and trimming things in AE. 
<= br>
I'll go find the proper channe= ls to report this bug with the AE team and hopefully get it patched out soo= n.


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