14.3.2 broken for PC no longer meeting system requirements. Suggestions?

[gr8bob]

I updated to Premiere Pro 14.3.1 -- it was broken for me.  Today updated to Premiere Pro 14.3.2, hoping my issue had been resolved. It's not.

I am dropping back to 14.3, which works fine for me.

Ditto the issues above for After Effects 14.7.1 (I have not tried to update to 14.7.2.)

Ditto for Media Encoder, latest updates.

My trouble with Premiere Pro 14.3.2:

No video display -- will not play video.  If I disable GPU acceleration, I get video display, but every operation is balky -- just saving a project sticks, gives "NOT RESPONDING", eventually saves.  It's not useable.

With Premiere Pro 14.3.2, as with 14.3.1, 16% of my i7 CPU is used by Premiere Pro when I am doing nothing.  If I close Premiere Pro, it leaves a back ground task open that still sucks up 16% of the CPU.  I have to kill the task from the task manager.

I am running fully up to date Windows 10.

Issue may relate to my video adapter.  My hardware is old, but Premiere Pro, After Effects and Media Encoder, latest updates, are only software products I use that do not work.

Other Adobe products newest updates, seem OK: Lightroom, Photoshop.

From After Effects, I get my GPU information:

Fast Draft: Available
Texture Memory: 404.00 MB
OpenGL
Vendor: ATI Technologies Inc.
Device: AMD Radeon HD 5700 Series
Version: 3.0.13399 Compatibility Profile Context 15.201.1151.1008
Total Memory: 1010.00 MB
Shader Model: 4.0 or later

[5uper_D]

Not surprised. With every update I hope it'll aleviate very simple issues but they always seem to get worse. 

[gr8bob]

I'm not a frequent user of this forum.  Is there some way to get Adobe's attention?

[Ann Bens]

If hardware is old it looks to me quite obvious you can run into issues. You graphics card is 11 years old.

Premiere is quite different from Photoshop.

Post full comp.specs

[gr8bob]

[gr8bob]

I also have a newer, maybe 5 years old, MS Surface Pro that I can try the update on, hopefully today.

[Ann Bens]

No wonder it does not work, take a look at the Adobe Premiere Pro CC System Requirements 

[gr8bob]

I note that I didn't meet requirements for 14.3, but it works fine on my old computer.

I tried 14.3.2 on my Surface Pro laptop, which is a few, maybe 5, years old.  It worked fine.  However my i5 Surface Pro with only 8GB RAM is pretty slow compared to my old i7 desktop with 16GB ram.

So now I am faced with, do I really want spend $1500 to get Premiere Pro/After Effects/Media Encoder to work on newest updates?

I can live on PP 14.3 for the time being while I consider the question.

[Kevin-Monahan]

Hi Bob,

Looks like you finally hit that "wall" of usability from this specific computer. You can only operate outside system requirements for so long before you hit a "tipping point" where your hardware is simply no longer effective for a particular version of any non-linear editing system. This happens all the time.

I am also operating outside system requirements from time to time with certain computers I have on hand. As time goes on, you can make workflow changes to limp along a little while longer. For example, perhaps your computer doesn't have enough power to have a H.264 4K workflow, but maybe it can still edit ProRes LT at 1080P? So, you have to do tests to see if you might work around your current performance and playback issue. If you are not operating with a second SSD for media, that is also a must have for those experiencing performance bottlenecks on underpowered systems.

So, yes, you have to ponder getting new hardware. Sorry about that. Honestly, though, I'd try my hand at transcoding or using proxies in a new workflow that might suit the hardware you have onhand there. If you need advice, do return with questions. As always, I hope to help you if I can.

Regards,
Kevin

[gr8bob]

I've only edited 1080p and less. Haven't touched 4K. There seems to be some CALL that hangs a process. Process still runs after I close PP -- have to kill it from task manager.

[Kevin-Monahan]

Try transcoding to ProRes LT. That should really help.

Kevin

[gr8bob]

I don't know what "transcoding to ProRes LT" means.  Is that some option in PP or do you mean create a different type of input for PP.  Regardless, I think you're off the mark.  PP semi-hangs as soon as I open it, before I import any video file into it; something starts running, seemingly in loop, that sucks up CPU utilization.

[Kevin-Monahan]

OK. Is this a new project or a legacy project you updated from a previous version? If the latter, test with a brand new project. See what happens.

Kevin

[gr8bob]

Legacy project worked fine on my Surface Pro laptop.

[gr8bob]

...... and I'd already tried to create new project, as well as clearing cache.

[RjL190365]

That will not be fixed any more, I'm afraid to tell you. Moving forward, the next MAJOR release of Creative Cloud will not even install at all on your system. Furthermore, attempting to update to that future version will completely uninstall and delete all instances of your current install (if such a version becomes permanently unavailable through the Creative Cloud app) with absolutely no warning whatsoever, and then, you will no longer be able to download and install a version of Creative Cloud and its programs that were compatible with your system any more since Adobe has now restricted version availability since May 2019.

Moreover, AMD had already ended all driver support completely for all Terascale GPUs, including your HD 5700 series, way back in 2015, shortly after the release of Windows 10. AMD issued only a single beta driver for these GPUs upon the original release of Windows 10 - and no more after that.

And with that Sandy Bridge i7, you're completely stuck between a rock and a hard place, with regards to a GPU upgrade: Any newer GPU will be heavily bottlenecked by your CPU, and your system's PCI-E 2.0 interface will only make matters worse. As a result, your CPU's performance level is in "no-man's land" because every single current-generation GPU either is severely overqualified for your CPU or completely lacks hardware encoding capability.

[gr8bob]

Sounds overly extreme given that my system works perfectly fine for 1080p video.  

[RjL190365]

There's where you misjudged things. Newer software is now requiring hardware capabilities that are completely lacking in your old hardware. As a matter of fact, almost all software companies are now becoming elitist, and absolutely refusing to support anything that's more than three years old.

In other words, it's not the performance. It's the standards support that matters here.

As a side note, you might be able to right things with a simple GPU update to a GTX 1650 Super, which costs around $160. Don't go above that unless you're planning to upgrade your system's entire CPU platform to something newer and more powerful within the next few months. And upgrade that RAM to 16 GB while you're at it. Premiere Pro now officially requires 8 GB or more free, unused available RAM just to run properly. EDIT: I now saw that you already have 16 GB of installed RAM. That's a start. But honestly, your GPU, in addition to being too old, also lacks a sufficient amount of VRAM to even function well, if at all, in any recent version of Premiere Pro. Premiere Pro, since the 2019 version, now officially requires 2 GB or more VRAM (4 GB or more VRAM recommended) just to work properly. Therefore, if you're going to continue to use that Sandy Bridge system for the foreseeable future, then just spend the $160 or so for the GeForce GTX 1650 Super GPU upgrade that I suggested, and get it over with.

[gr8bob]

I just updated to Premiere Pro 14.4, After Effects 17.1.4 and Media Encoder 14.4.  They work on my old computer!

[RjL190365]

Thank you for the update, gr8bob. As of 14.4, your old i7-2600K will run 14.4, but some features such as MPE GPU acceleration (if your GPU is too old or is lacking in the amount of SGRAM) will be disabled.

And when version 15 gets released, I would expect this to continue: Older hardware will run Premiere Pro 15.x, albeit with some features disabled. Expect a warning message to pop up during launch of 15.x when running on such older hardware.