<p>I doubt it is memory or page fault related.  Encoding is more of a stream operation, you load a frame, process the frame, hold the frame until you finish a group of pictures and then encode the group of pictures.  It is not a memory intensive process unless you are doing fancy effects that require memory to process.  It is a potentially HDD stream intensive process as it has to stream the video sources off the HDD and then record the output back to the HDD, which could involve lots of seeks potentially to move between reading and writing.</p>

<p>The two things I would try would be to try CUDA acceleration first and see if you can offload the processing to your GPU.  If that doesn't get sufficient speed I would try making sure your system is defraged and if that doesn't give sufficient speed, I might try SSDs for processing to and from for better random access of assets.</p>

<p>It is also possible that it is simply harder to encode later parts of your video though.  Depending on the exact settings you are using, changes in the content of the video can make a significant impact on how difficult it is to encode the video, so it may not even be unexpected that the encoding time changes between the first minute and the rest of the video.</p>

CC BY-SA 3.0
2014-11-11T15:19:25.603Z
'CUDA acceleration first and see if you can offload the processing to your GPU' - Where do I check this?
I think I have GPU accelleration switched on but this was to render only and not export. Where can I check the settings? Thanks
Orange Juice Jones
CC BY-SA 3.0
2014-11-11T15:25:26.977Z
@user32056 - if you have CUDA rendering turned on, it is most likely using it for the encode as well.  I don't think they've split out the behavior yet, but I also am still on CS6 because I refuse to rent/be held hostage to Adobe.
AJ Henderson
CC BY-SA 3.0
2014-11-11T15:56:31.913Z
in one of premieres settings I can see option for Merury Playback Engine.. still the export is too slow.
Orange Juice Jones
CC BY-SA 3.0
2014-11-11T16:01:15.400Z
@user32056 - did any of the other steps help?  I include the CUDA thing in case people haven't turned it on yet or don't have CUDA support, but the other ideas may also help.
AJ Henderson
CC BY-SA 3.0
2014-11-10T16:38:48.347Z
2014-11-10T16:38:48.347Z
AJ Henderson
<p>I have a long sequence (canon dslr and titles) (1hour) and as a
test export 1 minute at h264 Blu-ray pre-defined setting (pal 1920x1080, upper
field, low quality). This takes approx 1 minute to export. I then export the
entire sequence but rather than the expected 60mins to export it takes 3 hrs.
I'm running a i7,6Gig ddr3 ram, NVIDIA GeForce GTX 470, windows 7 64bit.
Exporting directly from premiere cc. I've also noticed sometimes the hard drive
gets thrashed when opening another program, could this be memory / page faults occurring
?
The question is why is export time not linear? and how can I
improve export time?</p>

CC BY-SA 3.0
2014-11-12T06:31:46.473Z
I've found the same thing. Also opening the project can take ages, as premiere loads up the previews.
stib
<video><encoding>
Why doesn't the duration of a Premiere Pro encoding scale linearly?
Orange Juice Jones
# Why doesn't the duration of a Premiere Pro encoding scale linearly?

(Asked by: username_0 on 2014-11-10)

I have a long sequence (canon dslr and titles) (1hour) and as a
test export 1 minute at h264 Blu-ray pre-defined setting (pal 1920x1080, upper
field, low quality). This takes approx 1 minute to export. I then export the
entire sequence but rather than the expected 60mins to export it takes 3 hrs.
I'm running a i7,6Gig ddr3 ram, NVIDIA GeForce GTX 470, windows 7 64bit.
Exporting directly from premiere cc. I've also noticed sometimes the hard drive
gets thrashed when opening another program, could this be memory / page faults occurring
?
The question is why is export time not linear? and how can I
improve export time?

**Tags:** video, encoding

> **Comments:**
> **username_1**: I've found the same thing. Also opening the project can take ages, as premiere loads up the previews.  

---

## 1 answers

### Answer by username_2 on 2014-11-10. Score: 1

I doubt it is memory or page fault related. Encoding is more of a stream operation, you load a frame, process the frame, hold the frame until you finish a group of pictures and then encode the group of pictures. It is not a memory intensive process unless you are doing fancy effects that require memory to process. It is a potentially HDD stream intensive process as it has to stream the video sources off the HDD and then record the output back to the HDD, which could involve lots of seeks potentially to move between reading and writing.

The two things I would try would be to try CUDA acceleration first and see if you can offload the processing to your GPU. If that doesn't get sufficient speed I would try making sure your system is defraged and if that doesn't give sufficient speed, I might try SSDs for processing to and from for better random access of assets.

It is also possible that it is simply harder to encode later parts of your video though. Depending on the exact settings you are using, changes in the content of the video can make a significant impact on how difficult it is to encode the video, so it may not even be unexpected that the encoding time changes between the first minute and the rest of the video.

> **Comments:**
> **username_0**: 'CUDA acceleration first and see if you can offload the processing to your GPU' - Where do I check this? I think I have GPU accelleration switched on but this was to render only and not export. Where can I check the settings? Thanks  
> **username_2**: @user32056 - if you have CUDA rendering turned on, it is most likely using it for the encode as well.  I don't think they've split out the behavior yet, but I also am still on CS6 because I refuse to rent/be held hostage to Adobe.  
> **username_0**: in one of premieres settings I can see option for Merury Playback Engine.. still the export is too slow.  
> **username_2**: @user32056 - did any of the other steps help?  I include the CUDA thing in case people haven't turned it on yet or don't have CUDA support, but the other ideas may also help.  

---

