Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Spooky Slow Export Time in PP – Any Thoughts???

  • Spooky Slow Export Time in PP – Any Thoughts???

    Posted by Scott Miller on March 25, 2014 at 4:53 pm

    I’m running Production Premium CS6 package editing PP on Windows 7, AMD Phenom IIx6, 64-bit, 16 GB RAM, with an NVIDIA GeForce GTX 560 adapter. (I know, my adapter is no longer supported. A real editing card is on the shopping list!)

    Here’s the issue: Editing a long clip for our local church with their new video system. They, thankfully, added another camera angle with a standard camcorder. This was the only footage recorded for the first ½ hour of the presentation due to the fact that the operator forgot to push his/her new button. Consequently, this is the only footage that can be utilized during that time frame. These segments were quite grainy and treated quickly and lightly with Video Toaster, totaling two cuts at 6 and 8 minutes apiece. 5 more cuts, ranging from 12 to 28 seconds fall later in the piece. These were all rendered separately and as the last renders of the process.

    This footage was imported at 1080p/MP4. Footage from the church system was recorded and imported in 720p/mp4. There is an additional clip from an existent video of 16 minutes, imported in an mov. format. Intro and out are mov. at 15 seconds with an additional 7 second of avi cut into the intro. All, with the exception of the MOV video, are laid over an audio track in a pkf format.

    Effects are limited to the Video Toaster clips mentioned and Brightness & Contrast on all except the 16 minute MOV video. Overall duration is 1;20;15. All unused clips and files were discarded and I’m exporting to the Vimeo 720, 29.97 preset in Premiere. The first export estimated at 32 hours and an immediate 2nd calculated the export at 52. After a check and double-check, I looked to Media Encoder where I saw an estimated 17 hour export before I declined this option. Here I cleared the Media Cache and checked export once again, estimated at 24 hours and accepted this option. That was 37 hours ago and the encoding sequence is currently at 68% with an estimated 15;29;53 left…

    What I find distressing is that an export usually runs CPU’s at 90% or above and they are currently running between 17-33% at +/- 5 GB RAM. This will ramp up on occasion to normal levels and I’ll see the encode progress, sometimes rapidly, sometimes in spurts.

    My thoughts are that I’ve overlooked something sophomoric and/or obvious. Similar pieces in length of this mix-and-match type have exported in much, much less time. Did I drop the ball by clearing the Cache? Is it Video Toaster… Or, could it be an unknown codec from the new camera system, to which I don’t have a clue???

    Thanks for any and all advice ahead of time!
    ~RS

    Al Bergstein replied 12 years, 1 month ago 3 Members · 3 Replies
  • 3 Replies
  • Tim Kolb

    March 25, 2014 at 7:28 pm

    Your situation is pretty complicated and vague to really troubleshoot unless you can identify the specific codecs on the timeline you’re trying to export.

    Your CUDA card will only have a significant effect on a GPU-assisted effect, not on decode or encode.

    I would say if your CPU cores look under utilized, that your system is waiting for data…is the drive all this is on full? Is it a small, external drive?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Scott Miller

    March 26, 2014 at 2:08 am

    Thanks for the response, Tim.

    Yes, I haven’t a clue what the cameras were, let alone what the codecs may be. AVCHD “something”??? This one was a favor and next time I’ll certainly find out what I’m working with but not even sure the editor who gave it to me knows.

    Thanks for the CUDA info. I understand.

    CPU is what confuses me. This drive has 1/2TB waiting open. One thing brought to my attention is that I’m playing only on this one drive. I don’t have a second internal drive. I’m bringing my files in from the USB3 HD to a file on desktop to increase speed and keep all data allocated in one easy to find place. Problem is that I’m writing back to that same file folder on the desktop, I.e.; through the C: drive.

    Right now, as the piece is finally done and looks good, I’ve cleaned the drive, defragged it and I’m going to bring the whole file back in and attempt an export back to the USB3 HD. This so that the CPU is not reading from and writing to the same place. I’ll change to only a VBR 1-pass without using the Previews option. Then we’ll get to see what happens here.

    One thing I found really weird is that when I went to pull file off desktop and take it to the external HD all files were already copied to this drive. All in a folder exactly like the one on the desktop, subfolders and all. I never created this on the external drive, it just appeared. It seems that PP was writing to both the C: and E: drives, yet the final export only went to it’s allocated destination. I went through PP and double checked paths, to no avail. Perhaps there is a “switch” somewhere in Windows creating this? If PP was looking to both drives while it encoded? … No… I don’t know. Really weird.

    Does this make sense and am I on the right path?

    Thanks,
    ~RS

  • Al Bergstein

    March 26, 2014 at 4:00 pm

    You really need to move the video processing off the C drive. It’s likely contending with the OS. There are numerous posts about how to properly setup your system for Pr. Putting everything on one drive is not recommended, except for simplest of video editing, and even then, you should have all your footage off on a esata, USB3 or firewire drive at the miminum. I routinely run into lengthened rendering/export times when I add effects, even blurring or sharpening. So you are doing everything you can to make the times long. Go buy a USB 3.0 external drive (a fast one if possible, i.e. get an external dock and buy a fast hard drive, it shouldn’t be much more than buying a slow drive, move all your footage onto it, and then try this again.

    Al

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy