What's a REAL fix for Adobe's Products?

[jefferyb341318]

Seriously, this is insane.

I cannot render a 5 second long video on Premiere Pro OR Media Encoder. Rendering gets stuck just past 50 percent and DOES NOT move. Oh, and that's not all.

Premiere Pro 2019 comes with some new features we didn't have last year:

1.) Uses 100% CPU at idle, just by having the program running, not even doing anything. This is a neat feature.

2.) Cannot render a 1080p timeline, that's 5 seconds long, on 1/4. Freezes or flat out doesn't render at all. Great new feature this year.

3.) Media Encoder comes with a new feature of not actually doing anything. It doesn't create files Queued from Premiere Pro. Neat feature.

These are the problems I'm having with this stuff.

I will never "Update" again, but I'm going to try downgrading to 2018 versions of everything to see if that works.

In the meantime, does Premiere Pro 2019 actually do anything?

If so, what are some fixes.

I have an i7 6 cores processor that runs at around 3Gh clock speed... and graphics card is Nvidia GeForce GTX 1060 with 8GB VRAM.

My programs run on a Solid State Drive. I have no storage issues. I've cleared cache on all fronts, multiple times, to no avail whatsoever.

So, this is not a hardware problem. This is an Adobe problem.

What's the solution? What are possible solutions? Do any solutions exist?

[R Neil Haugen]

Wes is a good person to have helping on this, BTW.

long-GOP ... long group-of-pictures.

It's a format for reducing storage needs for video files. It works by looking at complete frames, and seeing what pixels change between complete frames. Then it only writes say one complete frame (called an i-frame) every 9 to 15, 30, or with some drones, up to 120 frames apart. In between, it writes data-sets for each "frame" of the pixels that have changed since the last i-frame. These are "p-frames" ... for previous I suppose.

And ... it can store pixel sets of the data that have changed since the last i-frame, ... AND ... WILL change before the next i-frame, called "b-frames" for bi-directional.

Specialized chips in the cameras can rip this out very fast and it stores in a much smaller space than actually storing complete but compressed frames. Which is what an "intraframe" codec like say ProRes, DNxHD/R, or Cineform do.

But in editing, the computer has to fly between storage, CPU, and RAM to create the picture images for each frame with a ton of build/store/recall/rebuild work. It's darn hard for editing work.

Neil

[Ann Bens]

Set editing mode to Custom to be able to select preview codec.

[jefferyb341318]

Thank you for the information on how to access that preview codec.

However, when I sent the project directly to an Adobe Employee, this person discovered I had encountered a bug.

So, one of the effects I used was the lightning effect, but the way I used it possibly caused Premiere Pro to bug and just eat a bunch of CPU for no reason.

The Adobe Employee notified me that he has forwarded this bug I encountered to people who can address it. This wasn't supposed to happen in Premiere Pro, but it did anyway.

Program bugged and the culprit, according to the Adobe Employee, is most likely the way I used the lightning effect. Of course, the program is supposed to handle that easily, but it didn't, for whatever reason.

I was instructed to use After Effects for both lightning and turbulent displace (two effects I used in this small project), just to be safe and not reproduce the bug in Premiere Pro.

[Wes Howell · Accepted solution]

Jeffery has sent the project over.

On the small section that fails to render, I have isolated a rendering bug related to a couple older AE filters that are supported in Premiere Pro.

I am investigating this issue internally and have logged a bug.

In the meantime, the workaround would be to use AE for this particular section as those filters are native to AE (lightning and turbulent displace) and it should work great.  I did do some testing in AE to confirm this.

Wes

[jefferyb341318]

WOW!

We said the same thing in the same minute.

That's pretty funny. haha

But yeah... it's a bug. So, I have to use After Effects when I'm doing turbulent displace and/or lightning.

[ElDesconocido]

Replying to the render problem, try to clear the media cache.