Only recently Lightroom started taking SOME advantage of graphic cards but still not enough. The gaming industry is a great example of how to use resources like high count and high speed RAM, high power GPU's or even multiple GPU's etc. Many popular programs are like that, but with apps like Lightroom, Photoshop, Premier and such, patches can go only so far.Īt some point, Adobe needed to sit down and redesign the whole program, but they did not nor tht they seem to be willing to do so. Lightroom became a patchwork of fix-ups instead of a flowing software. It is software issue and not hardware issue. LR product developers actively participate there but are rarely seen in this forum. I suggest you repost there, and be sure to include the first ten lines or so of Help > System Info. Regardless, Adobe wants all product feedback posted on the official feedback site: Lightroom Classic CC | Photoshop Family Customer Community. Product designers understandably hate throwing in a new manual knob each time a problem rears its head, but I think it's called for here. Given that there's always been some fraction of users for whom LR gets it wrong, it's clear that Adobe isn't able to implement a completely automatic rule, and in such situations, the traditional solution is to give the user a knob that controls how aggressive the export is at using the CPUs (that's what my plugin does).
I've worked on these sorts of problems in years gone by, and my most recent LR plugin faces the problem too.
Based on the reports in the forums, I think that generally works well, but there have been continual reports like yours where it fails. But in LR 6 (I think) Adobe changed LR to be more aggressive in using multiple CPUs. Originally and for many years, there were many complaints that LR didn't take full advantage of multiple CPUs, and people would fire up multiple concurrent exports manually or use a plugin to do that. Adobe has struggled from the beginning getting the right balance between export throughput and interactive response, across the wide range of users' machines, file formats (raw is particularly CPU intensive), workflows, and editing styles.
0 kommentar(er)
