DPP4 slow to load images, previews are blurry

[woodsy]

When I load a raw photo it takes a long time for the throbber in the lower right corner to stop spinning and even then the preview is not as sharp as the jpegs I export. My computer is OK spec wise apart from the fact that I use the onboard Intel video card. Will adding an Nvidia video card to my computer help with performance and sharpness of the previews?

[jrhoffman75]

I think the reason is that the processor in that card isn’t a high speed unit. 

[6Dnewbie]

I'm having somewhat the opposite problem as the original poster.

When I first open up a raw file in DPP4, the picture on the screen looks great. Nice and sharp, etc..    But when the program has finished doing whatever it does to modify the picture (during which time the small wheel icon is spinning in lower right corner),  the picture ends up looking far worse than when I first opened it.  Significantly less sharp most noticably and often.  

This is happening with raw files taken on both my 6D and 5dmkIV.  

If I open the very same pictures from my 6D on DPP3, this does not happen.  The raw file looks as good, or better, once the program has finished "doing it's thing" when generating the picture ("generating high-quality image" I believe is what DPP3 says at the bottom while working on it versus spinning wheel on DPP4).  It is only when I open the raw files in DPP4 that they end up looking worse.  (DPP3 only applies to the pictures from the 6D, MarkIV won't work on it)

Anybody have any idea what the program is doing to make them look worse?  What settings is it applying and/or changing to cause this and can I turn them off/on/disable?

One example:  A picture that I took with my 6D, the waves created by the wake of a boat on a  lake with still water look great when viewed on DPP3.   When viewed in DPP4, the image ends up looking like someone took a paint brush with white paint on the tip and dabbed points of white on the tops of the wave crests with the frothing water glistening in the sun.  DPP3 looks as it should.

[RobertTheFat]

---

@6Dnewbie wrote:

I'm having somewhat the opposite problem as the original poster.

When I first open up a raw file in DPP4, the picture on the screen looks great. Nice and sharp, etc..    But when the program has finished doing whatever it does to modify the picture (during which time the small wheel icon is spinning in lower right corner),  the picture ends up looking far worse than when I first opened it.  Significantly less sharp most noticably and often.  

This is happening with raw files taken on both my 6D and 5dmkIV.  

If I open the very same pictures from my 6D on DPP3, this does not happen.  The raw file looks as good, or better, once the program has finished "doing it's thing" when generating the picture ("generating high-quality image" I believe is what DPP3 says at the bottom while working on it versus spinning wheel on DPP4).  It is only when I open the raw files in DPP4 that they end up looking worse.  (DPP3 only applies to the pictures from the 6D, MarkIV won't work on it)

Anybody have any idea what the program is doing to make them look worse?  What settings is it applying and/or changing to cause this and can I turn them off/on/disable?

One example:  A picture that I took with my 6D, the waves created by the wake of a boat on a  lake with still water look great when viewed on DPP3.   When viewed in DPP4, the image ends up looking like someone took a paint brush with white paint on the tip and dabbed points of white on the tops of the wave crests with the frothing water glistening in the sun.  DPP3 looks as it should.

---

Sounds as though you may have the highlight warning turned on, with the warning color set to white.

[6Dnewbie]

Checked, and highlight warning is off, and when I turned it on it was displaying in red.

I am guessing the white splotchiness on that particular picture is due to the terrible sharpness that shows up after the program chews on the picture.

Practically every picture I open looks good on the sharpness when first opened, but goes soft/loses detail after the spinning wheel is done doing it's thing.  

I am absolutely at a loss as to what is being applied to cause this.   The pictures look fine when opened, and they look fine in DPP3, even after the program does what it does to provide the "high quality image."   This is only happening in DPP4.   6D pictures, 5dmkIV, doesn't matter.

[jrhoffman75]

I’m guessing the initial view is the embedded JPEG.

I have not experienced what you are seeing.

Try switching DPP to Neutral Picture Style and check all tabs and switch off any check marks.

If that doesn’t help give Canon a call at 1-800-OK-CANON.

[Waddizzle]

---

@6Dnewbie wrote:

Checked, and highlight warning is off, and when I turned it on it was displaying in red.

I am guessing the white splotchiness on that particular picture is due to the terrible sharpness that shows up after the program chews on the picture.

Practically every picture I open looks good on the sharpness when first opened, but goes soft/loses detail after the spinning wheel is done doing it's thing.  

I am absolutely at a loss as to what is being applied to cause this.   The pictures look fine when opened, and they look fine in DPP3, even after the program does what it does to provide the "high quality image."   This is only happening in DPP4.   6D pictures, 5dmkIV, doesn't matter.

---

If you turned it on and it displayed as red, do you know what that means?  Your shot is over exposed.

[6Dnewbie]

I’m guessing the initial view is the embedded JPEG.

I have not experienced what you are seeing.

Try switching DPP to Neutral Picture Style and check all tabs and switch off any check marks.

If that doesn’t help give Canon a call at 1-800-OK-CANON. 

Thanks.   I'll  switch and check all the tabs.   

Good point on the embedded jpeg.

The perplexing thing is the raw files all look fine when viewed on DPP3.  

 I hope I can get this figured out as DPP3 will not read 5dmkiv files.

[6Dnewbie]

If you turned it on and it displayed as red, do you know what that means?  Your shot is over exposed

Yes, I know what the highlight display means.  

The picture I referenced as an example had no overexposed areas.   I used a different picture to see what color was used to display overexposed areas.   The one I used had a small blinking red area.

And again, the picture referenced in my first post, as well as many others, look just fine using DPP3.   Which leads me to the assumption that it is something being applied/turned on/adjusted/etc. specific to DPP4. 

I just downloaded it in mid August and haven't even adjusted any settings from default/as downloaded.    But as I have looked through the settings, I can't come up with any smoking guns.  However,  I don't know what I don't know regarding all aspects of this program.

[vaxofek413]

I feel your pain with DPP4. I still use it because I love how it handles Canon colors, but the performance has always been its Achilles' heel. You mentioned that the previews are blurry for quite a while before finally snapping into focus—that’s a classic symptom of the software struggling to process the RAW data in real-time. Even on high-end machines, it seems to crawl compared to something like Lightroom.

I’ve noticed a similar lag in my own workflow, especially when I’m pulling files off my storage server. I actually recently upgraded my networking setup with some new expansion modules to support a 32-Gigabit throughput, thinking that maybe the network bottleneck was the primary culprit for my slow load times. While the raw data moves across my local network at lightning speeds now, DPP4 still takes its sweet time rendering those previews. It really highlights that even with top-tier network devices and massive bandwidth, poorly optimized software can still bring a high-end system to a halt. It’s frustrating when your hardware is ready to fly, but the app is stuck in the mud.

Have you tried checking if hardware acceleration is enabled in the settings, or does that seem to make the stability worse on your particular rig?

[wq9nsc]

Depending upon the computer, using the "prioritize speed" option under preferences in DPP may reduce laggy behavior but in my experience it will have no significant speed impact with faster setups. 

I experimented some last year with my previous workstation and there was a slight but not really significant improvement in speed when selecting a RAW image or switching between the main and cropping tools tabs when set to speed priority.  DPP's note about this option is pretty cryptic stating that prioritizing speed may make noise more noticeable in some images but didn't state whether this drop in quality carries over to when the file is actually processed into a JPG file.  I tried both setups (exiting and restarting DPP each time so that the changed preference took effect) using some images from my 1DX III taken at 51,200 ISO and even highly magnified I could not see any difference in image quality and the file sizes were exactly the same.  So from my brief experiment, it would appear that the preference doesn't impact exported JPG quality so it might be worth trying for some setups to improve speed.

With my current workstation, a selected CR3 file takes under one second to go from the blurred large "wheel" indicator to the detailed small wheel indicator.  Switching from the main tool tab to the crop tab is well under 2 seconds for the same behavior and I can live with this although faster would always be better.  CR2 files are easier for computers to handle and those were lightning fast on both of my prior workstations.

I think diminishing returns will set it pretty quickly with DPP and hardware upgrades.  I monitored resource utilization while doing stuff with files on my current workstation and loading a RAW file or switching tabs on the tool palette never sends CPU utilization over 3%.  Batch processing CR3 files results in a less than one second spike never exceeding 13% CPU utilization but drops to mid single digits for over 90% of the 6 to 7 second per file processing time. The GPU utilization never moves from zero utilization in either editing or batch processing files.

I am using a HP Z8 G5 with twin 28 core Xeon CPUs and a pair of Nvidia Ada 4000 series workstation cards.  A less equipped PC is going to be slower BUT DPP never comes close to utilizing the available resources of this PC.  It would be interesting to see what CPU utilization looks like on other configurations; if it is going high then closing all other programs while working with DPP would probably help.

And even on a fast workstation, DPP's old memory leakage issue is very much present.  I have a total of 512 GB of memory (256 per CPU) and after a couple of hours DPP will increase usage to the 10 to 12 GB range from its usual 2 to 3 GB size and becomes sluggish even though only a fraction of available memory is in use.  So it is worthwhile to exit and restart DPP every couple of hours during long editing sessions (or as soon as you notice it becoming more sluggish).  I have been using DPP since 2005 and this memory leak has been a consistent issue for over two decades now 😞  For this same memory leak reason, if you are through editing once you start batch processing then exit the DPP program and let the batch run by itself.

Rodger