Technically, our transitions are made with high quality and maximum flexibility and with multiple repeated levels of validation and testing. Therefore, for a technical reason, it has an extremely low probability of incorrect operation. Let’s take a closer look at each of these aspects.
- Absolutely all transitions from the pack were rendered in order with all available render engine settings. In particular, each of the transitions was rendered with engines such as “Mercury Playback Engine GPU Acceleration (CUDA)”, “Mercury Playback Engine GPU Acceleration (OpenCL)”, “Mercury Playback Engine Software Only”. Moreover, this was done at least 4 times at different stages, such as the development stage, the stage of selecting sounds, the stage of selecting images for previews, the stage of final rendering for previews in the extension and the site. Considering the volume of the pack, it took a huge amount of time, but we are sure that it works and passed all sorts of checks of our quality control.
- There are no restrictions due to the unique possibilities of automatic adaptation of presets to the settings of the sequence. This is really real. Thanks to our cleverly developed preset structure, a unique way of storing presets and the exclusive functionality of our AinTransitions extension for Premiere Pro, we were able to develop a solution that has no restrictions on project settings or sequence settings. In particular, our extension converts the originally developed preset to the settings of your active sequence. It adjusts to any resolution, frame rate, pixel aspect ratio and fields property. In addition, all this is compatible with changing the transition speed, which is done in one click in the extension. All this in scope has no analogues in the world!
As you can understand from the characteristics above, we have technically tried to reduce the occurrence of problems to zero. However, situations may still arise that are not associated with some technical problems. Let’s look at such cases and how to act in these cases to fix problems.
- In the process, you could change the settings of the sequence. In this case, the transition may stop working or work incorrectly if you added a transition to the timeline with certain sequence settings, for which the transition preset was adapted, and then changed these settings, thereby causing possible incompatibility.
Solution: Delete the transition preset from the timeline and add it again using the AinTransitions PPro extension. This will adjust the transition to match your updated sequence settings. - You might accidentally delete one of the system files that are part of the transition structure. This can cause either a complete removal of the transition from the timeline, or the transition will remain but stop working.
Solution: Delete the transition preset from the timeline and add it again using the AinTransitions PPro extension. This will add the necessary system files to the project if they are missing. - The visual appearance of the transition is different from the preview. This can be the case when you added a transition that uses GPU accelerated effects, and in the settings of your project, the render engine “Mercury Playback Engine Software Only” is specified. With this setting, Premiere Pro or Media Encoder will render using the CPU. Therefore, effects that require GPU will look different.
Solution: Change render engine settings to “Mercury Playback Engine GPU Acceleration (CUDA)” or “Mercury Playback Engine GPU Acceleration (OpenCL)” or “Mercury Playback Engine GPU Acceleration (Metal)” depending on your graphics card. - The transition looks broken on video footage. This situation can occur for transitions marked as sequence base when you use such transitions on video footage. Due to the specifics of Premiere Pro work, this starts the calculation of the effect not on a specific part of the video under the transition, but from the beginning of the video. Accordingly, the transition cannot work correctly in this case. You can read more detailed information on this in the documentation.
Solution: Trim the video clips below the transition using the “Razor” tool and then make each of the two clips into a Nest. On the documentation page, this situation is described in more detail and contains a video tutorial.