Yes it's a coding problem on Adobe's side ... many reports of the issue and yet NO fixes from Adobe.  See here.  My solution to to stop CC from loading. ... View more

Yes, see my post here.   It's a software engineering problem and quality assurance problem.  I expected more from a company that is making 4+ Billion in record revenue for Q3. ... View more

I guess we disagree Neil ... with current hardware 32c/64t CPUs, DDR5, M.2's, GPUs with 82 TFLOPS at FP16/FP32 is some serious computing performance ... where working with 5030 4000 x 3000 res files would barely register as "activity".  My PCs can process 75GB/sec thruput (not theoretical) data no problem.   When I'm editing there is hardly any CPU or GPU activity.  I would expect Pr to have all my cores working to prerender whatever format it needs to display an image correctly in a sequence, but I get nothing until I move my playhead to a location then I get ONE CPU pegged at 100%.   CUDA seems to be only used on exports or render outs not during editing nor proxy generation ... makes no sense to me?  Editing is the #1 operation for me ... I assume most either send out final to a render farm or their own render servers (I use my own in house) so it's really not that big a deal ... it's the editing that's the problem. Even with photoshop, exporting a simple 4K image to PNG for some bizarre reason takes 10-20 seconds?  Something that takes <1 second in Windows Paint/Photo app?     Sorry, but Adobe have some serious performance issues that they can't seem to or don't think are important to solve?   Software is not physical, tools are locked into the physical realm, can't really compare.   Like I mentioned to Warren below, I think the issue is the use of abstraction layers in coding trying to maintain a single code path for both iOS and Windows.  This is the LCD approach to software engineering across platforms, cheaper development costs at the cost of less utilized and highly specific accelerated hardware instructions.   But again, if editing in Pr is going to be such a horrible performance issue, then the golden rule for software development is to provide the user with a "progress indicator" to shows users that it is working on something even if very slowly.  Right now, there is NO visual queue (unless you're like me and monitor activity via task manager or some other tools) in Pr to indicate it's "thinking".  That's just a bad UI.   I honestly don't understand why some of you defined the poor performance of Pr?  You know it's poor because you and I have work around after work around to try to improve it.    I was taught to use the right tool for the job also, Pr isn't that tool. ... View more

That's interesting, but not sure what it has to do with Adobe's performance issues post 2017?  Having to keep a 2017 version operational on one of my PC's shouldn't be a "solution" to problem.  Adobe still can't get the basic Meta data information correct for many sources ... that's really basic programming.  Again, it's as if they're all Mac/iOS developers using XCode and no one is proficient with Windows OS programming using Visual Studio.  The performance problems with Pr 2022 feels like an abstraction layer rather than fully utilized hardware level accelerated operations which I know C++ is more than capable of working with.   Adobe have the financial resources for two development paths (Windows/iOS), but given their current announcement regarding running on iPad it sounds more and more like abstraction layers where the code has no direct path to low level hardware to utilize it's potential.  The advantage to code abstraction is having a single code path, the disadvantage is performance as the abstraction layer has to operate at LCD (lowest common denominator) in order to maintain cross platform compatibility ... in other words don't utilize very specialized instruction sets/drivers/hardware. ... View more

Again, I'll disagree.  I've got legacy Pr 2017 version running and these image files (5030 image file count not pixels, jpg at resolution 4000 x 3000 at 2382KB per file) ... in fact, that's what I do, load Pr 2017 if there is nothing in Pr 2022 I need for the project.  Pr 2017 has no performance issues with processing these files.   If Adobe continue with their performance problems and/or just ignore users, I don't see much of a future here?  I know I'm not alone based in the feedback I've received from many many users.     One major software engineering "best practices" is to provide a user with long running process feedback ... what I mean by that, is if a process is going to take more than 2-8 secs it needs to have a "progress" UI indicator ... no such indicator exists in Pr when working a sequence.  Pr leaves the user guessing on what's going on, this is NOT GOOD and every software engineer I've worked with over the past 35 years knows that's a bad interface. Here is an old article going back to 1990's discussing UI response time, it's actually gone down to 2-8 seconds max before a progress feedback is required.   If Adobe can't figure out their performance problems, then they should at a bare minimum provide UI feedback.     ... View more

We'll just have to disagree on this one ... upto about 2017 Pr had no problems working with some of the CODEC commonly used ... the conversion to x64 seems to be the root cause.  Anyway, I've circled this wagon long enough and it's painfully obvious nothing is going to change on the Adobe side. ... View more

What bothers me the most is that Adobe's revenue is doing extremely well 4.3Billion increase from last year so I KNOW they have the financial resources to get additional developers to work on this and fix this along with many other issues from HDR to performance ... converting to ProRes and/or using Proxies shouldn't be my only option.  Adobe management seem more obcessed with personal gain than reinvesting in the company. ... View more

Every performance solution for Adobe seems to be "convert to ProRes" which I already know about ... the issue there is time and space ... time to convert and the increase (considerable) in storage space used.  Other editing platforms don't seem to have any such requirement and work extremely well all native formats/codecs ... no one at Adobe seems competent enough to explain why they can't? ... View more

I've been down the Apple path ... biggest problem is that Apple don't keep up with CPU/GPU hardware improvements so while everyone else is improving the deliverable times I was stuck with whenever Apple decide they wanted to update their desktop hardware (which is rare).  I really like FCP, but if it wasn't for Apple complete lack of improving their desktop hardware in a timely manner, I'd probably still be using FCP.   But agree, the fact Adobe can't (still can't) get something as simple as correct creation dates on source assets is beyond incomprehensible??  Programmering 101 ... and that's coming from a 35 year experienced software engineer.  I'm just baffle by this ... how could this not be a priority after so many years? ... View more

It's definitely a bug ... but it's because you have ..   ...Using hardware accel...  By @movingimage   If you switch over to software rendering then that option will stick.  The issues seems to be Adobe understanding the various GPUs (and drivers) and what they can and can't do ... anyway, side point, Adobe should simply NOT show the option if the GPU hardware isn't able to support the Max Render Quality option ... allowing users to check this option but ignoring the user input because of hardware acceleration is just going to trigger confusion and more support questions.   I'm not sure what Hardware actually support Max Render Quality but I'm guessing something very expensive and exotic as you definitely do NOT want to be rendering as software as that will take forever and a day pending project and encoder.   Rob. ... View more

You mean more nuts than I already am? 🙂  ... yeah, I was doing everything correctly for HDR, just YouTube wasn't. ... View more

This is a fairly old post and video ... much has changed in 3 years.    Methods to improved performance: 1.  Use Proxies (at medium or low resolution option) ... this is really easy to do now but not ideal especially for color grading and/or HDR. 2.  Convert to Apple ProRes before working with any files in a sequence. 3.  Never link in Ae projects directly, render them out first and use rendered output in sequence. 4.  If possible (the FX/features your using support it) set project to GPU hardware acceleration. 5.  If software rendering (as many CPU cores as you can and as fast as you can, AMD seems to shine here)   Methods that made little or no difference to performance: 1.  Memory settings (Performance or Memory) neither makes any difference 2.  Adding more than 64GB RAM makes no difference regardless of file or image sizes 3.  Very expensive GPUs makes little or no difference.  My nVidia 1060 vs. 3090Ti perform the same when GPU acceleration is enabled. 4.  Expensive and very fast M.2 drives with 7GB/sec xfer speeds doesn't seem help at all, about 200-300MB/sec is the cut off, anything above that isn't realized in terms of performance. 5.  Using a RAM drive, actually slowed performance down just a little ... I had a system with 256GB RAM and tried out a 64GB RAM drive and put my footage on that RAM drive and it made absolutely no difference to workflow performance nor exports.   Obviously Adobe forces compromises in order to get better performance: 1.  Apple ProRes convesion is a long extra step and produces large files sizes taking up disk space. 2.  Proxies just aren't good enough do any HDR and/or color grading work ... use proxies for rapid editing (cuts/delete/inserts etc.) only. 3.  Not being able to directly link in Ae projects without a major performance hit means extra steps to render out and round trips between the two apps Pr and Ae.   Pr 2022 is full of bugs (more so than any version I've used in the past), especially around HDR and Exports.   Rob. ... View more

Thanks for the vote of confidence and appreciate the help ... I'll keep trying, but right now, it's just not working for me and I've confirmed my asset sources are in HDR.   My next step is to try and create (from scratch) some HDR output from Ae and see if that works.   I've also confirmed that dumping my native HDR footage to YouTube does get flagged as HDR so whatever "it" is, it seems to be specific to Adobe Pr.   I found a few videos on HDR workflow for Ae, and I'll try those.   Cheers, Rob. ... View more

I can't imagine why anyone using Pr would want those checkboxes?  Why does someone want to be locked out of changing those settings?  Can you give some context?   Default values are initially assign/set when the export screen is loaded or when the format is changed, that's how 99.9% of UI's work with just about any application.  I've never ever seen a UI that wants to "lockout" changes to settings, kinda defeats the purpose of having the settings, no?   Maybe in edit, to lock layers/tracks, but export settings?   Anyway, still no HDR output regardless of what settings I use.  Is there a way to reset my Pr preferences and put Pr back in a default state?  In the past (several years ago), I've had problems with Pr where it didn't have appropriate rights to write to directory/folder locations outside the MS best practices for file/data locations.  But I thought that was solved in more recent versions?   I sorta feels like the Pr development team are primarily OSX platform developers and not really wanting to get involved in the Windows side of things.   Anyway, I'm about to uninstall Pr completely and reset my entire Adobe set of applications and then reinstall my plugins, etc. etc. in the hope this will fix HDR, but I have my doubts.   I think you missed my point about GPU settings ... if GPU settings can be set "per project" then they should NOT be available in global Preference as a setting.   Rob   ... View more

Hi Neil,   I've gone thru both of those articles/posts with a fine tooth comb, they are great articles.  BUT, the problem I'm running into is that Pr2022 seems to at random disable options when I select  from a dropdown in the Export screen ... as in my video where I showed you where settings aren't being saved by Pr2022.  It's like a very bad UI designer got a hold of the new export screen and made a complete confusing mess of it.  For example what is the purpose behind have a checkbox next to the dropdown option??  Checking the box just seems to disable the dropdown??  If it's not checked does that mean the setting is NOT going to be used ... why on earth would I want it to disable the HDR Gaphics White (Nits) setting dropdown box so I can't select from it? When I change from Quicktime to HEVC H.265 my options have changed but once again I've faced with the settings that when adjusted will change my other settings: I have no idea if those settings I've selected from the dropdown are actually going to be use since I haven't checked those checkboxes next to them??   Another example of more HDR bugs is under Edit | Preferences ... the "Display Color Management (requires GPU acceleration)" is disabled (not able to check or uncheck it) if the "Project" settings File | Project Settings | Ingest Settings | General tab under Renderer is set to "Mercury Playback Engine Software only" ... this is supposed to be a project setting and NOT a globa Preferences setting.  Adobe seems to mix and match setting context "Global" settings vs. "Project" settings which just adds to the confusion and frustration.   Trust me, I've been futzing more than just a bit ... this is insane try to get HDR to output correctly from Pr 2022.  I appreciate your responses and links, but not getting anywhere with HDR.   Rob. ... View more

I'll try that and see what happens, but so far nothing it registering as HDR with YouTube.  Tried all kinds of export options along with "included HDR10 metadata".  The Adobe documentation I found on export settings is vague but I think I must have tried well over 30 combinations of settings (both hardware and software rendering).   Color Primaries (for my monitor) and settings in Pr are DCI-3 which is same as P3D65.   Nothing seems to be coming out as HDR or being registered as HDR by YouTube when I use Pr ... native uploads seem to register as HDR (i.e. not going thru Pr).   Very frustrated here.   Rob. ... View more

Ann, It's not a low memory warning?  Please read the error message.  Anyway, changing back to performance and I get the same results ... the "Maximum Render Quality" still does NOT save for the sequence settings ... I made a video here demonstrating the Pr bug:   https://youtu.be/zS1a-48Qt14   Rob. ... View more

It looks like HDR just isn't work in Adobe Pr 2022.  I captured some nVidia HDR footage and confirmed  Color Space: Rec. 2100 PQ Color Space Override: Off Input LUT: None Video Codec Type: HEVC 10 bit 4:2:0   Monitor set to HDR10   Sequence set but Pr refuses to "save" the "Maximum Render Quality" ... gives me a warning:   Even though Optimize Rendering Preference is already set to "memory".   There is definitely a bug in HDR for Pr 2022.   To further put the nail in the coffin that this is an Adobe bug, I uploaded the native 2100 PQ HDR directly to YouTube (not via Pr).  After the YouTube processing was complete, I view the footage on my HDR monitor and it works as expected, true HDR.   Rob. ... View more

Hi Neil,   Yes, that was set to HLG 2100 per screenshot.   Rob.   ... View more

Thanks Ann, but I've already go thru that article ... I'm fully HDR workflow and still not working correctly in Pr 2022.  Please see my attached screenshots from my post of all the settings from OS to monitor to Pr.   Cheers, Rob. ... View more

Sorry, your response isn't making much sense to me?  Did my screenshots not come thru?  There is no HLG or PQ option for sequence settings.  Please review my attached screen shots of EVERYTHING from OS to Adobe ... fully HDR pipeline including HDR10 monitor.   Cheers, Rob.   ... View more

Hi Neil,   Yes, working with iPhone 13 HLG 2100:   When I check "Maximum Render Quality" and hit OK, then return back to check the Sequence Settings, "Maximum Render Quality" is unchecked??  Pr 2022 doesn't appear to be saving the setting.   My monitor is in HDR mode (Samsung Odyessy G9 which supports HDR10).   So no go for HDR HLG 2100 with my setup.  Looked at your link but sadly didn't help.   I can set it to R709 but I need to do a full HDR output and it doesn't seem to be working in Pr 2022.   Rob. ... View more

Hi Neil,   Yes, OSX and Windows are different and I'd be VERY surprised if Adobe don't have provisions in code for both OS types ... I mean they're operating CUDA support and other OS/Platform specific features so I'm certain Adobe must have conditional compiles for those items that are OS and hardware specific.   As far as Windows OS going back decades, getting file information is very simple, here is the file information from .NET.  On the C++ side, if Adobe are trying to maintain the same code path (which might explain why they run into so many performance issues if they avoid using Windows platform specific features/acceleration because they don't work on OSX) for all platforms OSX, Linux, Windows, then they'll need to use #ifdef to conditional compile and the stat.h for Linux/OSX and unistd.h for Windows and I believe their are additional C++ 20 libraries that can work on multiple OS types ... Adobe developers can find more information here.  This is an easy to solve problem that doesn't require much coding work and certainly doesn't generate any breaking changes.   My 2 cents.   Cheers, Rob.     ... View more

Hi Neil,   Yes, Render Selection just plays back the currently selected clip, it doesn't render it.   The ONLY work around is to enable WAB (Work Area Bar), adjust those start/end points to cover the area I want rendered, then select "Render Entire Work Area".  There is NO ability to create a short cut for "Render Entire Work Area" (same problem as Render In Out).   FYI, when WAB is enabled the Render In Out is not longer an option.   Rob. ... View more

I can't see or make a short ct for Render In to Out ... this is in Pr 2022?   Is this problem going to be fixed ... ever?  5 years later?   Rob ... View more