Mailing List AE-List@media-motion.tv — Message #64512
From: Robert Kjettrup <AE-List@media-motion.tv>
Subject: Re: [AE] Improper Timecode Issues in AE v16.0.0
Date: Fri, 19 Oct 2018 17:08:43 +0200
To: After Effects Mail List <AE-List@media-motion.tv>
 Message Header

Undecoded Message
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 <ae-list@media-motion.tv> 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/
 
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to ListMaster