Premiere Pro is a champ in terms of efficient organization of the render process, while other applications may be somewhat less efficient at that task. Here are some figures we measured on our computers:Īs you can see the spread of efficiency figures is quite significant. The efficiency depends on a video editing application quite a lot. We’ll compare the overall render/export speed of the video editing application to the speed at which Neat Video performs its’ task.įor example, if Neat Video’s speed is reported as 40 frames/second by Check Speed, while the video editing application exports/renders at a speed of 20 frames/second, then the efficiency of that application is 50%. To do this, we’ll render/export a simple project with Neat Video applied to one clip. Ok, with that in mind, let's check the efficiency of a video editing application. That’s when you may lose time unnecessarily. Any inefficiency of the application during any specific component of the render/export process will cause the overall speed to be reduced. Certain applications can organize the render/export process more efficiently than others, some codecs are faster than others, etc. The speed at which the application does each of these things influences the final export time. These include the input and output codecs used in the project, the application itself, effects and transitions and so on. However, the size of this difference should be questioned further because it offers clues about the efficiency of the video editing application.Īs we have discussed above, the overall render/export speed in a video editing application depends not only on Neat Video, but also on other components in the render pipeline. Resolve 15 rendering a simple project with Neat VideoĪs you can see, each video editing application renders/exports the test project at a speed that is somewhat lower than the speed of Neat Video alone. Premiere Pro rendering a simple project with Neat Video Neat Video itself without overhead of video editing application
In the table below you can see the speeds of two similar projects rendered and exported in Premiere Pro CC 2019 and in Resolve 15 when applying Neat Video to a 1080p clip as compared to the speed of Neat Video itself. To offer some real-life examples, we have done several direct tests with a timer. As you can imagine, if you add the time taken by all other steps, then the overall render time will be longer and correspondingly, the overall render speed will be lower than the speed of Neat Video alone. When you run the Check Speed test in the Neat Video plug-in (or use NeatBench as a standalone speed test) you’re only measuring the speed of Neat Video itself, without the other steps of the render pipeline. That means if you use Neat Video in a project, the overall render time is always longer than the time Neat Video itself takes to do its part of the work. The overall render time depends on what happens at each of these steps and the whole is always longer than the time taken by any one of those individual steps. At the very end, the output video file is written to a local hard drive or a network location.Īll these steps in the pipeline are organized and managed by the video editing application. Once all the desirable effects and transformations are applied to the video frames, the stream of those processed frames is compressed once again using a chosen output codec. Frames can be resized, color-corrected, denoised, the speed of the clip can be changed, different effects can be applied, transitions can be added and much more. At this stage, video frames can be modified in countless ways to achieve our creative goals. Then it’s time to do some processing, we like this part the most. Then, the application decompresses those frames using the corresponding input codec - which reads these frames for further processing. It starts with reading encoded video frames from a video file stored on a local hard drive or over the network. This is the queue of tasks that most video editing programs follow to go from original media to the output of the final file. Where does the time go when you render a video?įirst, let's have a look at a render pipeline of a video editing application.
To do that, we’ll describe a typical render pipeline first and then give you some tips on how to make it more efficient. In this article we try to offer some recommendations on how to make rendering faster and shorten the overall processing time. The bottom line is that we need to get to the results, faster. However, this is not always the case because increasing consumer expectations means the demand for new video content is also becoming higher every day.
As both hardware and software continue to improve very rapidly it may seem as though the life of the film creator is getting easier and easier.