Skip to main content
A
angelodc
Participating Frequently
December 1, 2016
Answered

AE 2017 Bug - Time Remapping

  • December 1, 2016
  • 1 reply
  • 1803 views

Hi there. I only just updated to AE 2017, but when I reopened a certain project---which relied heavily on time remapping---the animation was completely out of sync with the voice over. Has anyone else run in to this? (Just in case you're wondering what exactly I was time remapping, a client had asked me to make animation based on their Power Point slides. So, I made screen recordings of the slides and retimed them in After Effects according to the voice over.) The project was fine before I updated to 2017.

This topic has been closed for replies.
Correct answer Roei Tzoref

I did as you recommended. I successfully reproduced the bug. I've uploaded the test to creative cloud: http://adobe.ly/2gqECDM

Let me explain what I did to execute the test.

1) I created a screen recording using Quicktime. (I saved the file as "screen_recording")

2) Using AE2015, i time-remapped the file. (I saved the file as "2015_time_remap.aep")

3) I opened the AE2015 file in 2017. Low and behold the time remap was different!!! (I saved the file as "2017_time_remap.aep")


thanks for taking the time. ok I see where the problems is. it seems the footage you recorded has a weird frame rate. I got it by using VLC player which is a free software that is more than just a reliable video player. notice the weird frame rate: 56.17

in Ae it get's interpreted one way in CC2015 and another in CC2017 and actually CC2017 is in the right because it is trying to play the video in the frame rate of 60 which will make it 5 seconds and 44 frames.

and not like previous version that does interpret it at 56.17 but says it's 60fps and the video is now 6 seconds and 7 frames (as it should be)

so what you can do is in CC2017 change the interpret footage to the real frame rate (right click on the footage-interpret footage) and insert the correct frame rate

now it will interpret correctly

this is a workaround, the real solution would be to record in a video capture software that can encode the video in the exact specified frame rate, and not give this weird frame rate.

1 reply

Roei Tzoref
Roei Tzoref
Legend
December 1, 2016

did you open the same project in another version and it behaved as expected? you can run alongside 2015 and 2017 (and all other version from CS6 and above)

are you using mp3 for audio? show us some screenshots or video capture if possible.

A
angelodcAuthor
Participating Frequently
December 1, 2016

Thanks for the reply.

Yes, I made the original project in 2015 and it was working fine. (But, again, when I updated to 2017, it doesn't work.)

How do I access 2015? Is it still on my computer? (I'm on a Mac, and I don't see it in my Applications folder anymore. Does Adobe automatically remove it upon updating?)

Audio was .wav and is working fine.

I'm not sure if my employer would be okay with me posting screen shots.

Roei Tzoref
Roei Tzoref
Legend
December 1, 2016
How do I access 2015? Is it still on my computer?

by default upon updating, the CC APP removes previous versions. so if you don't see it on applications, it's probably uninstalled. you can always re-install it through the CC App. you can see it under previous versions section. this could help solve this problem if you could determine that in CC2015 it works fine.

there is not TR bug in recent version that AFIK. could it be just a preview issue? are you previewing cached frames? (the green bar is totally green). do you notice the waveform itself visually is not in sync with the animation? you can post screenshots not showing your composition window, just the timeline and the keyframes. obscure what you need to so we can try to examine what is wrong.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices