When you use Twixtor you don't use Time Remapping. It's not only redundant Twixtor doesn't work with time remapping at all. Just use Twixtor.
Rick, thanks for the reply. I think you misunderstood what I was describing. The Time Remapping is required to remap footage beyond the original length, however it is not being used to actually change the speed of the clip – that is of course, what Twixtor is supposed to do.
I sent a similar note to ReVision support, and their response was that there is an update from 5.0.4 to 5.1.5 that has to do with the way that CS6 handles caching and is contributing to those frame issues. Will give that a try and see if that works.
You're not understanding how to use Twixtor. Throw time remapping in and you've fouled things up.
Add your footage.
Add a solid.
Apply twixtor to the solid and reference the footage.
There you go. That's all there is to it.
Hi Rick, I appreciate your persistence to help. That's definitely another way to use the plugin which I've never used in the past, but does eliminate the need to enable time-remapping. Certainly not as common as the majority of the tutorials out there, including Re:Vision's own.
For the sake of argument I tried this approach, but unfortunately the problem persists. Out of curiosity, were there specific problems you avoided by using the solid method vs applying directly to the footage?
If I can dig up my serial numbers I will install the CS6 update as instructed. I'll definitely update this post if I get any positive results.
I'm pleased to say upgrading to 5.1.5 fixed the problem!
Sorry to butt in here....
I must ALSO thank Rick. I have been using Twixtor for - wel, AGES, and never knew of this procedure. I am using it now, the Solid, makes the whole process so much easier than time remapping.
Thanks Rick, and Thanks Stephen for starting the thread!
I'm using twixtor with Premiere Pro and am getting the same "pausing" as mentioned here with after effects...any ideas on how to overcome the same issues in Premiere Pro?