[Pierre Jasmin]

After Twixtor
Raise the Amount maybe?

[Pierre Jasmin]

The main thing is the less motion blur in the actual source footage the easier it is for Twixtor. One can always apply RSMB in post if the footage is too strobby at lower frame rate.

As such you might want to invest in Twixtor Regular and RSMB instead of Twixtor PRO. The worst in your scenario would be a closer up shot where someone is sideways and move real fast a knife that has reflections back and forth to chop something… You also have to be careful with semi-transparency (like a fast blender blade moving some transparent liquid you see through the jar… – that might look weird at 60 FPS sources with Twixtor applied).

Within Premiere, you will note some tutorials at our website if you press the Help button at the top (techsupport@ can help you from there). That aside what works in Premiere is to interpret the footage to the actual FPS you will use in the end. And work at that frame rate. The other question is if you need to maintain the audio – sometimes when doing small amount of slow-mo (or straight frame rate conversion) you might need to unlink the audio and apply Premiere Speed to audio and then relink. We go a bit over that in Twixtor for Premiere last tutorial. If you plan to do something more fancy with slowmo and audio is important, you might want to learn the precompose in AE part as we explain to make speed ramps…

Pierre

[Pierre Jasmin]

The main thing is the less motion blur in the actual source footage the easier it is for Twixtor. One can always apply RSMB in post if the footage is too strobby at lower frame rate.

As such you might want to invest in Twixtor Regular and RSMB instead of Twixtor PRO. The worst in your scenario would be a closer up shot where someone is sideways and move real fast a knife that has reflections back and forth to chop something… You also have to be careful with semi-transparency (like a fast blender blade moving some transparent liquid you see through the jar… – that might look weird at 60 FPS sources with Twixtor applied).

Within Premiere, you will note some tutorials at our website if you press the Help button at the top (techsupport@ can help you from there). That aside what works in Premiere is to interpret the footage to the actual FPS you will use in the end. And work at that frame rate. The other question is if you need to maintain the audio – sometimes when doing small amount of slow-mo (or straight frame rate conversion) you might need to unlink the audio and apply Premiere Speed to audio and then relink. We go a bit over that in Twixtor for Premiere last tutorial. If you plan to do something more fancy with slowmo and audio is important, you might want to learn the precompose in AE part as we explain to make speed ramps…

Pierre

[Pierre Jasmin]

You should be able to use a different version of RE:Flex without loosing anything in your project.

The plugins are installed here:
CC and CC 2014
Windows: C:/Program Files/Adobe/Common/Plug-ins/7.0/MediaCore
Mac: /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore

You can always to be sure,
1) Make a copy of your AEP
2) move the RE:Flex folder somewhere outside of the plug-ins folder, install the current version and check.

The only issue is if someone saves from RE:Flex 5 to 4. For example RE:Flex 5 has a GPU menu, that value will not be saved. Similarly saving from CC 2014 as CC 12.0 and loading in CC AE 12.0 should work.

The

[Pierre Jasmin]

You should be able to use a different version of RE:Flex without loosing anything in your project.

The plugins are installed here:
CC and CC 2014
Windows: C:/Program Files/Adobe/Common/Plug-ins/7.0/MediaCore
Mac: /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore

You can always to be sure,
1) Make a copy of your AEP
2) move the RE:Flex folder somewhere outside of the plug-ins folder, install the current version and check.

The only issue is if someone saves from RE:Flex 5 to 4. For example RE:Flex 5 has a GPU menu, that value will not be saved. Similarly saving from CC 2014 as CC 12.0 and loading in CC AE 12.0 should work.

The

[Pierre Jasmin]

If you have CC 2014 it’s because you are on subscription, so you can download CC. Run Adobe Creative Cloud app, and in the old version section, select CC. I don’t think there is a way to revert back to 2014.1 (AE 13.1).

Or alternatively as I said, update RE:Flex to latest version.

Pierre

[Pierre Jasmin]

If you have CC 2014 it’s because you are on subscription, so you can download CC. Run Adobe Creative Cloud app, and in the old version section, select CC. I don’t think there is a way to revert back to 2014.1 (AE 13.1).

Or alternatively as I said, update RE:Flex to latest version.

Pierre

[Pierre Jasmin]

The last update of CC 2014 – (2014.2) requires the last version of RE:Flex (5.2) otherwise there is some caching issues introduced by AE we were able to workaround hopefully with RE:Flex 5.2.

If someone is still at RE:Flex 4, they will need to either upgrade to RE:Flex V5 or they need to use Save As – Save a Copy as CC (12)… and render in CC (AE 12). If someone has not updated to 2014.2, is still at 2014.1 for example, not sure I would recommend to upgrade AE to latest.

Pierre

[Pierre Jasmin]

The last update of CC 2014 – (2014.2) requires the last version of RE:Flex (5.2) otherwise there is some caching issues introduced by AE we were able to workaround hopefully with RE:Flex 5.2.

If someone is still at RE:Flex 4, they will need to either upgrade to RE:Flex V5 or they need to use Save As – Save a Copy as CC (12)… and render in CC (AE 12). If someone has not updated to 2014.2, is still at 2014.1 for example, not sure I would recommend to upgrade AE to latest.

Pierre

[Pierre Jasmin]

Also, alternatively save as CC (previous version) and rendering in CC should also work.

Pierre