• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

Re: Premiere Pro and Multicore Support

New Here ,
May 05, 2020 May 05, 2020

Copy link to clipboard

Copied

You are a big company, you can solve it - so solve it.
To use the excuse that it is difficult to solve is just silly and provocative.
You need to prioritize this issue.
There are thousands of users with powerful multi-core CPUs with lots of power that are not utilized by Adobe's programs.
You will get incredibly positive response from users if you focus on speed and core utilization over new features in next updates - especially with the new CPUs currently being released.
Right now, it is becoming more and more annoying to have more and more powerful computers - which are well utilized by other software - while Adobe's programs only exploit a fraction of PC potential.

Views

41.8K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 05, 2020 May 05, 2020

Copy link to clipboard

Copied

LATEST

Yea, we all want more and want it now. There's a common comment included in your post that doesn't hang with reality though.

 

focus on speed and core utilization over new features in next updates

 

Let's see ... how many new features were there all through the 2019 cycle? That would be ... um ...the HueSat curves in Lumetri, some tweaks to the Essential Graphics operations ... um ... ProRes on PCs, and the Display Color Management switch.

 

Well, how about 2020 so far? ... AutoReframe ... oh, and HDR 10 metadata export options.

 

Not a long list, is it?

 

They intentionally slowed working on new features two cycles ago, when Patrick Palmer took over the video apps. His main effort has been working on bugs including ones that went back a generation of code or two, performance, and stability. The numbers for the majority of the user base are way up on those, which is the good news. The bad news is that many of the bugs and performance issues plaguing various small subsets of users are things they cannot replicate in-house. What you cannot see, you cannot fix.

 

Which is why they created their public beta program out of the CC app, to get more users into the development cycle on a wider range of gear/media/workflows than their engineering staff and "internal" beta people provided.

 

And as they are getting bugs out and stability up, they are working more on getting performance up. Including in the public beta, they have hardware encoding for H.264 using both Nvidia and AMD GPUs being tested among other performance items.

 

And the place to communicate directly to the development team is their UserVoice system. This forum is primarily user to user, with product support staff like Kevin Monahan who started this post doing supervision. The UserVoice site is the direct link to the developers. I've talked with one of the engineers tasked with reading every post, and he wants both more posts by users with problems and especially more detail in those posts.

 

Also ... every post on the UV system is collated and goes up to the upper managers who determine priorities and budgets. Those folk work, live, eat, and sleep Metrics. The UV system is the best way we users can give them the metrics we want them to see.

 

So ... feel encouraged to go search the UserVoice system for core-count posts, and upvote any you see. If you don't find a good one, make a new one, come back here and post the link, and I and others will happily go over an upvote it.

 

Neil

 

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines