Skip to main content
U
UNHAPPY_ADOBE_USER10969523
Known Participant
March 20, 2019
Question

Premiere Pro Ingest encodes taking too long

  • March 20, 2019
  • 1 reply
  • 1423 views

For the purposes of creating proxies, I am trying to ingest Pro Res 422 HQ footage recorded on a BlackMagic URSA Mini Pro 4.6k, however it's taking 23 hours to ingest an 8 minute interview.

I have followed all of the ingest steps correctly.

Here's one of the many videos I looked at in addition to your step by step guide: https://youtu.be/fq4hYAYYFQ8

I have tried multiple presets as well as creating new ones yet all yield the same result: 23 hours to ingest an 8 minute interview.

Computer specs:

Model Name: iMac

Model Identifier: iMac17,1

Processor Name: Intel Core i7

Processor Speed: 4 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 8 MB

Memory: 32 GB

O/S 10.13.6

Now that we've established my hardware is not the issue, please explain how I get your software that I pay for every month to work properly.

Thank you.

This topic has been closed for replies.

1 reply

Kevin-Monahan
Community Manager
Kevin-MonahanCommunity Manager
Community Manager
March 20, 2019

Hi UNHAPPY_ADOBE_USER,

Wow, sorry to hear about your negative experience.

  • I am trying to ingest Pro Res 422 HQ footage recorded on a BlackMagic URSA Mini Pro 4.6k, however it's taking 23 hours to ingest an 8 minute interview.
  • I have followed all of the ingest steps correctly.
  • I have tried multiple presets as well as creating new ones yet all yield the same result: 23 hours to ingest an 8 minute interview.

Let's see what you are trying to accomplish:

  • Transcoding 4K footage from one format to another.
    • Are you scaling this footage from 4K to another frame size that is less than 4K or are you not resizing the footage?
    • If you are resizing the footage, that means you are scaling it down. Scaling in either direction is a GPU accelerated process.
      • Is GPU acceleration enabled in File > Project Settings?
      • With encode times like that, I suspect it is not set for GPU acceleration.
      • It should be. Please check that first.
      • You need to have GPU acceleration for any transcoding process for best results.
    • Avoid using H.264 presets. Try ProRes Proxy or LT.
  • Computer specs:
    • Model Name: iMac
    • Model Identifier: iMac17,1
    • Processor Name: Intel Core i7
    • Processor Speed: 4 GHz
    • Number of Processors: 1
    • Total Number of Cores: 4
    • L2 Cache (per Core): 256 KB
    • L3 Cache: 8 MB
    • Memory: 32 GBO/S 10.13.6
  • Now that we've established my hardware is not the issue....
  • Most of the specs are pretty good, but your hardware (your GPU specifically) actually might have something to do with slower encoding times:
    • You have an iMac 17,1, which I believe has only 2 GB VRAM, does it not?
      • The recommended amount of VRAM for 4K workflows is 4GB VRAM.
      • You are 2 GB short of the recommended amount of VRAM for 4K workflows.
      • If you have less than 4GB VRAM in a 4K workflow, and need to scale footage, you need to adjust your expectations for the duration of the media processing times when attempting the transcoding process.
      • Sorry, I don't believe you can update your iMac's GPU to improve this situation.
      • All you can do to reduce the duration of encoding time with your iMac is to ensure that GPU acceleration is enabled.

Please check these things and return with any questions.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
U
UNHAPPY_ADOBE_USER10969523Author
Known Participant
March 20, 2019

Why is it Adobe always tries to blame user hardware instead of admitting their software is faulty?

My hardware has enough VRAM:

Chipset Model: AMD Radeon R9 M395X

   Type: GPU

   Bus: PCIe

   PCIe Lane Width: x16

   VRAM (Dynamic, Max): 4096 MB


    I tried multiple presets, including Pro Res Proxy and LT. Same results. You know what almost works? OLD versions of the program. GPU Acceleration was already turned on.

Turns out, Adobe programmers updated their software so much, now it doesn't work. I re-installed Premiere and Media Encoder 2017. This combo ingested the 8 minute clip in 20 minutes.

2019 Premiere links the proxies created in Premiere 2017. However, the playback of the proxies (with monitor resolution set to ¼) starts to skip after a few seconds. If I stop and start the playback, it plays correctly for about 5-10 seconds then starts to skip again.

So it turns out, Yes, indeed, Adobe programmers failed to do their job. Do you have a solution for the bugs in your software that doesn't involve blaming user hardware?

Kevin-Monahan
Community Manager
Kevin-MonahanCommunity Manager
Community Manager
March 20, 2019

Hi,

Why is it Adobe always tries to blame user hardware instead of admitting their software is faulty?

In my case, I'm from Cupertino, CA. I love Macs and I've edited for years. My Mac here at work is nothing special, but it is transcoding without issue with version 13.0.1. No one else I can find with the same situation that you're in.

So, I'm not blaming you for anything. Only comparing my experience, and other users' experience with yours. Nothing personal.

I think something is up with your Mac, or your installation of Premiere Pro if you do, indeed, have GPU acceleration available. FYI, the info I looked up online for the 17,1 did not include a 4GB VRAM GPU. I was wrong. Glad you have one!

I re-installed Premiere and Media Encoder 2017. This combo ingested the 8 minute clip in 20 minutes.

Glad to hear it. This seems to indicate something about your installation of Premiere Pro, I think.

2019 Premiere links the proxies created in Premiere 2017. However, the playback of the proxies (with monitor resolution set to ¼) starts to skip after a few seconds. If I stop and start the playback, it plays correctly for about 5-10 seconds then starts to skip again.

Have you tried deleting media cache?

Have you tried resetting Adobe Folder permissions?

Still no go? Another thing that can cause issues that have little or no explanation is if you updated your project from one major version to the next (which sounds like the case). This can actually cause unexpected behavior, including project corruption, so that could be at the heart of the issue, as well. Project back up files can be your saving grace in that case.

You can test by creating a brand new project and seeing how those files transcode with the same footage as in your project. If they transcode normally, your project might be corrupt.

So it turns out, Yes, indeed, Adobe programmers failed to do there job. Do you have a solution for the bugs in your software that doesn't involve blaming user hardware?

If you have complaints about the software quality, you need to put those in front of the product team here. We are on the support team here in forums.

Hope we can assist you with your current problem.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices