Summer fun with your Saharan Water Dog! -Noel ... View more

I respect your choice to use JPEG instead of raw format, though I wonder whether you would benefit from switching to a raw workflow if you really are using the more advanced features of Camera Raw when opening files. One thing I've found over time is that my old raw files, should I need or want to use one, can be turned into better results today by modern raw converters than by the converters of the time.  There is definitely more information in the raw files than what's provided by the camera in its JPEGs (a great example is if there's near overexposure).  There's no evidence that conversion algorithms have reached their limits either, so the trend will likely continue. Yes, the storage burden is greater to keep raw files, but disk space is less costly today than ever before. Canon out-of-camera JPEG color can be very pleasing; I've personally always liked their renditions.  For that reason I set things up so that my raw files open by default with nearly identical colors to the Canon look. Lastly, JPEG compression introduces sometimes pretty bad artifacts, especially if there's a lot of detail.  Just try sharpening an image aggressively and you can see them clearly. I guess my point boils down to this:  Have you re-evaluated lately why you want to use JPEGs? Maybe you can solve this problem by switching to a workflow that delivers higher quality AND better repeatability.  A way to convince yourself you're on the best path for your needs is to set your camera to record both formats (I presume that's still possible with the latest models), then open a few of your own images both ways. -Noel ... View more

For those of you still experiencing slow operation, can you please post a screen grab of your Performance preferences?  Perhaps upon review more suggestions can become apparent... -Noel ... View more

Color-management is a complex subject that defies a simple answer or "set it and forget it" operation.  Dave has done a very good job above with an overview. The subject, with some effort, is navigable and learning what everything means and how it works can benefit you from now on.  However, there is much misinformation.  The thing to keep in mind is that every setting is there for a reason, and you're expected to set them all so that when you're working, Photoshop is helping you as best it can to keep things straight. My first questions to you, integrationi41501282​​, are: What color-profile describes the colors of your document (i.e., what is your working space)?  And why have you chosen this working space? If you don't quite know how to answer, can you please describe how you get to where you're editing an image (e.g., do you open a raw file, File > New and draw shapes, or what)?  We can work into it step by step. -Noel ... View more

One additional tip: To copy a block of steps first select the steps, then choose Duplicate from the fly-out menu, then drag to your desired position. Actions editing is somewhat 1980s-esque, but it can be done. -Noel ... View more

The formats of the images you use as input don't influence how big your saved .psb file will be.  The .psb file can be compressed, depending on your compression preference, but it's not lossy compression like .jpg and will be much larger. Also, the way you've organized your document will also influence it's size.  For example, if you have complicated layer masks on a whole lot of layers, they take room in the file too. Other things can also affect size...  For example you might have image data beyond the edges of your canvas. You have some responsibility for optimizing your document, or as you have seen it can get out of hand.  A number of experts here who have practical experience have already given you some good advice. Finally, if you really need monstrous images, and that's the way you want to work what's the problem getting a powerful computer with lots of resources (e.g. 64 or more GB of RAM and TB of free disk space)?  If you need it you need it. -Noel ... View more

Also bear in mind that, presuming you have a few spare GB of disk space, you can have both the older and newer Photoshop available to test with simultaneously (well, maybe interchangeably would be a better word). Also, make sure you are aware (you've probably already checked) of the latest version of the display driver available from HP for your machine.  With laptops one generally can't get drivers direct from AMD/ATI. -Noel ... View more

Layer > New Adjustment Layer > Curves (which will be the layer with the mask as well). -Noel ... View more

I have to agree with JJMack that it sounds like you have hardware issues, though another possibility is a display driver bug or even a corrupted install.  Does your system's event log show any problems? -Noel ... View more

Check all your Photoshop performance settings, especially your RAM limit and scratch disk choices.  They likely were set at defaults when 2019 went in. Also, 16 GB total RAM isn't much in the grand scheme when working with documents of that size. -Noel ... View more

Hey Dag, I had an idea that's a bit out there...  Here's my sniffer-out.txt file.  Does it differ from yours in any important ways? Number of Launches: 331 stdout: # Photoshop Version: 20180920.r.24 2018/09/20: 1193433 Tester="Photoshop" snifferStart="2018-10-28_00:35:54" AIFCoreInitialized=1 # 00000_2018/10/28_00:35:54.313(+00.000)[f10] BEGIN DoRunAIFOGLInitialize AIFOGLInitialized=1 # 00001_2018/10/28_00:35:54.313(+00.000)[f10] END DoRunAIFOGLInitialize, duration=8.88295e-06 # 00002_2018/10/28_00:35:54.313(+00.000)[f10] BEGIN DoRunAnyGLGPU OGLContextCreated=1 # 00003_2018/10/28_00:35:54.881(+00.568)[f10] END DoRunAnyGLGPU, duration=0.568035 # 00004_2018/10/28_00:35:54.881(+00.000)[f10] BEGIN DoRunEnumerateGLGPUs # 00005_2018/10/28_00:35:54.933(+00.052)[f10]  wmiNumDevices=1 # 00006_2018/10/28_00:35:54.934(+00.000)[f10]  adapter[0]{ VendorID=4318 DeviceId=7216 SubSysId=296947934 Revision=161 DedicatedVideoMemory=5160439808 DedicatedSystemMemory=0 SharedSystemMemory=25768527872 Description=NVIDIA Quadro P2000} # 00007_2018/10/28_00:35:54.934(+00.000)[f10]  output[0]{ DesktopCoordinates={ L=0 T=0 R=2560 B=1600 W=2560 H=1600 } AttachedToDesktop=1 Rotation=1 Monitor=0000000000010001 DeviceName=\\\\.\\DISPLAY1 # 00008_2018/10/28_00:35:54.934(+00.000)[f10]  output[1]{ DesktopCoordinates={ L=-1200 T=0 R=0 B=1600 W=1200 H=1600 } AttachedToDesktop=1 Rotation=2 Monitor=0000000000010003 DeviceName=\\\\.\\DISPLAY2 # 00009_2018/10/28_00:35:54.934(+00.000)[f10]  output[2]{ DesktopCoordinates={ L=2560 T=0 R=3760 B=1600 W=1200 H=1600 } AttachedToDesktop=1 Rotation=2 Monitor=0000000000010005 DeviceName=\\\\.\\DISPLAY3 # 00010_2018/10/28_00:35:54.934(+00.000)[f10]  adapter[0] displays: 3 # 00011_2018/10/28_00:35:54.934(+00.000)[f10]  adapter[1]{ VendorID=5140 DeviceId=140 SubSysId=0 Revision=0 DedicatedVideoMemory=0 DedicatedSystemMemory=0 SharedSystemMemory=268435456 Description=Microsoft Basic Render Driver} # 00012_2018/10/28_00:35:54.934(+00.000)[f10]  dxgiNumDevices=1 # 00013_2018/10/28_00:35:54.934(+00.000)[f10]  aifNumDevices=1 # 00014_2018/10/28_00:35:54.934(+00.000)[f10]  aifDeviceIndex=0 # 00015_2018/10/28_00:35:54.935(+00.000)[f10]  creating ContextOffscreen for { DeviceName=\\\\.\\DISPLAY1 DeviceString=NVIDIA Quadro P2000 DisplayID=7216} # 00016_2018/10/28_00:35:54.939(+00.005)[f10]  aifDevice[0]={ DeviceName=\\\\.\\DISPLAY1 DeviceString=NVIDIA Quadro P2000 DisplayID=7216} # 00017_2018/10/28_00:35:54.939(+00.000)[f10]  aifNumContexts=1 NumGLGPUs=1 # 00018_2018/10/28_00:35:54.940(+00.000)[f10] END DoRunEnumerateGLGPUs, duration=0.0580164 glgpu[0].GLVersion="4.1" # 00019_2018/10/28_00:35:54.940(+00.000)[f10] fAdapterDesc.VendorId=4318 # 00020_2018/10/28_00:35:54.940(+00.000)[f10] Looks like a discrete GPU glgpu[0].IsIntegratedGLGPU=0 # 00021_2018/10/28_00:35:54.954(+00.014)[f10] DXGI RAM=5160439808=4921MB # 00022_2018/10/28_00:35:54.954(+00.000)[f10] wmiVRAM=5120 dxgiVRAM=4921 glgpu[0].GLMemoryMB=5120 glgpu[0].GLName="NVIDIA Quadro P2000" glgpu[0].GLVendor="NVIDIA Corporation" glgpu[0].GLVendorID=4318 glgpu[0].GLDriverVersion="24.21.14.1181" glgpu[0].GLRectTextureSize=32768 glgpu[0].GLRenderer="Quadro P2000/PCIe/SSE2" glgpu[0].GLRendererID=7216 glgpu[0].HasGLNPOTSupport=1 glgpu[0].GLDriver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um" glgpu[0].GLDriverDate="20181016000000.000000-000" glgpu[0].CanCompileProgramGLSL=1 glgpu[0].GLFrameBufferOK=1 gputag.GL_SHADING_LANGUAGE_VERSION=35724 glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.60 NVIDIA" gputag.GL_FRAGMENT_PROGRAM_ARB=34820 gputag.GL_MAX_PROGRAM_INSTRUCTIONS_ARB=34977 glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[65536] gputag.GL_MAX_TEXTURE_UNITS=34018 glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4] gputag.GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS=35661 glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192] gputag.GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS=35660 glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32] gputag.GL_MAX_TEXTURE_IMAGE_UNITS=34930 glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32] gputag.GL_MAX_DRAW_BUFFERS=34852 glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8] gputag.GL_MAX_VERTEX_UNIFORM_COMPONENTS=35658 glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096] gputag.GL_MAX_FRAGMENT_UNIFORM_COMPONENTS=35657 glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[4096] gputag.GL_MAX_VARYING_FLOATS=35659 glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124] gputag.GL_MAX_VERTEX_ATTRIBS=34921 glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16] gputag.AIF::OGL::GL_ARB_VERTEX_PROGRAM=69 glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1 gputag.AIF::OGL::GL_ARB_FRAGMENT_PROGRAM=27 glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1 gputag.AIF::OGL::GL_ARB_VERTEX_SHADER=70 glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1 gputag.AIF::OGL::GL_ARB_FRAGMENT_SHADER=28 glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1 gputag.AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT=81 glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1 gputag.AIF::OGL::GL_ARB_TEXTURE_RECTANGLE=58 glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1 gputag.AIF::OGL::GL_ARB_TEXTURE_FLOAT=53 glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1 gputag.AIF::OGL::GL_ARB_OCCLUSION_QUERY=37 glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1 gputag.AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT=68 glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1 gputag.AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD=47 glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1 # 00023_2018/10/28_00:35:54.963(+00.009)[f10] BEGIN DoRunAIFOCLInitialize # 00024_2018/10/28_00:35:55.006(+00.043)[f10]  DoRunAIFOCLInitialize: AIF::OCL::Library::initialize(); # 00025_2018/10/28_00:35:55.007(+00.001)[f10] END DoRunAIFOCLInitialize, duration=0.0437542 # 00026_2018/10/28_00:35:55.007(+00.000)[f10] BEGIN DoRunEnumerateCLGPUs NumCLGPUs=1 # 00027_2018/10/28_00:35:55.007(+00.000)[f10] END DoRunEnumerateCLGPUs, duration=2.30977e-05 clgpu[0].CLPlatformVersion="1.2" clgpu[0].CLDeviceVersion="1.2 CUDA" clgpu[0].IsIntegratedCLGPU=0 clgpu[0].CLMemoryMB=5120 clgpu[0].CLName="Quadro P2000" clgpu[0].CLVendor="NVIDIA Corporation" clgpu[0].CLVendorID=4318 clgpu[0].CLDriverVersion="411.81" clgpu[0].CUDASupported=1 clgpu[0].CUDAVersion="10.0.181" # 00028_2018/10/28_00:35:55.007(+00.000)[f10] BEGIN GPUSnifferTester::DoRunCLBandwidth # 00029_2018/10/28_00:35:55.007(+00.000)[f10]  BEGIN GPUImplHardware::DoGetCLBandwidth # 00030_2018/10/28_00:35:55.007(+00.000)[f10]   GPUImplHardware::DoGetCLBandwidth: AIF::OCL::Context context(properties, *iDev); # 00031_2018/10/28_00:35:55.343(+00.336)[f10]   GPUImplHardware::DoGetCLBandwidth: AIF::OCL::CommandQueue cq(context, *iDev, false, true); # 00032_2018/10/28_00:35:55.343(+00.000)[f10]   BEGIN GPUImplHardware::checkBandwidthCL # 00033_2018/10/28_00:35:55.343(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: clCreateBuffer d_idata nbytes=16777216 # 00034_2018/10/28_00:35:55.343(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: clCreateBuffer d_odata nbytes=16777216 # 00035_2018/10/28_00:35:55.343(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: clFinish # 00036_2018/10/28_00:35:55.343(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: copy 100 iterations # 00037_2018/10/28_00:35:55.343(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 0 of 100, totalSeconds=0 # 00038_2018/10/28_00:35:55.352(+00.009)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287843 # 00039_2018/10/28_00:35:55.352(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287843 # 00040_2018/10/28_00:35:55.352(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.00287843, BW=1.16572e+11, maxBW=1.16572e+11 # 00041_2018/10/28_00:35:55.352(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 10 of 100, totalSeconds=0.00287843 # 00042_2018/10/28_00:35:55.355(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287027 # 00043_2018/10/28_00:35:55.355(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287027 # 00044_2018/10/28_00:35:55.355(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0057487, BW=1.16903e+11, maxBW=1.16903e+11 # 00045_2018/10/28_00:35:55.355(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 20 of 100, totalSeconds=0.0057487 # 00046_2018/10/28_00:35:55.359(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287946 # 00047_2018/10/28_00:35:55.359(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287946 # 00048_2018/10/28_00:35:55.359(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.00862816, BW=1.1653e+11, maxBW=1.16903e+11 # 00049_2018/10/28_00:35:55.359(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 30 of 100, totalSeconds=0.00862816 # 00050_2018/10/28_00:35:55.362(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00286925 # 00051_2018/10/28_00:35:55.362(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00286925 # 00052_2018/10/28_00:35:55.362(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0114974, BW=1.16945e+11, maxBW=1.16945e+11 # 00053_2018/10/28_00:35:55.362(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 40 of 100, totalSeconds=0.0114974 # 00054_2018/10/28_00:35:55.366(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.0028785 # 00055_2018/10/28_00:35:55.366(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.0028785 # 00056_2018/10/28_00:35:55.366(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0143759, BW=1.16569e+11, maxBW=1.16945e+11 # 00057_2018/10/28_00:35:55.366(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 50 of 100, totalSeconds=0.0143759 # 00058_2018/10/28_00:35:55.369(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287437 # 00059_2018/10/28_00:35:55.369(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287437 # 00060_2018/10/28_00:35:55.369(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0172503, BW=1.16737e+11, maxBW=1.16945e+11 # 00061_2018/10/28_00:35:55.369(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 60 of 100, totalSeconds=0.0172503 # 00062_2018/10/28_00:35:55.372(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00286925 # 00063_2018/10/28_00:35:55.372(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00286925 # 00064_2018/10/28_00:35:55.372(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0201195, BW=1.16945e+11, maxBW=1.16945e+11 # 00065_2018/10/28_00:35:55.372(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 70 of 100, totalSeconds=0.0201195 # 00066_2018/10/28_00:35:55.376(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287949 # 00067_2018/10/28_00:35:55.376(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287949 # 00068_2018/10/28_00:35:55.376(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.022999, BW=1.16529e+11, maxBW=1.16945e+11 # 00069_2018/10/28_00:35:55.376(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 80 of 100, totalSeconds=0.022999 # 00070_2018/10/28_00:35:55.379(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00286928 # 00071_2018/10/28_00:35:55.379(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00286928 # 00072_2018/10/28_00:35:55.379(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0258683, BW=1.16944e+11, maxBW=1.16945e+11 # 00073_2018/10/28_00:35:55.379(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: 90 of 100, totalSeconds=0.0258683 # 00074_2018/10/28_00:35:55.382(+00.003)[f10]    GPUImplHardware::timeBandwidthCL: totalSeconds=0.00287539 # 00075_2018/10/28_00:35:55.382(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: seconds=0.00287539 # 00076_2018/10/28_00:35:55.383(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: totalSeconds=0.0287437, BW=1.16695e+11, maxBW=1.16945e+11 # 00077_2018/10/28_00:35:55.383(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: clFinish # 00078_2018/10/28_00:35:55.383(+00.000)[f10]    GPUImplHardware::checkBandwidthCL: releasing # 00079_2018/10/28_00:35:55.384(+00.002)[f10]    GPUImplHardware::checkBandwidthCL: result=1.16945e+11 # 00080_2018/10/28_00:35:55.385(+00.000)[f10]   END GPUImplHardware::checkBandwidthCL, duration=0.0413094 # 00081_2018/10/28_00:35:55.385(+00.000)[f10]   bytesPerSecond=1.16945e+11 # 00082_2018/10/28_00:35:55.385(+00.000)[f10]   GPUImplHardware::DoGetCLBandwidth: result=1.16945e+11 # 00083_2018/10/28_00:35:55.385(+00.000)[f10]  END GPUImplHardware::DoGetCLBandwidth, duration=0.377736 clgpu[0].CLBandwidth=1.16945e+11 # 00084_2018/10/28_00:35:55.385(+00.000)[f10] END GPUSnifferTester::DoRunCLBandwidth, duration=0.377807 # 00085_2018/10/28_00:35:55.385(+00.000)[f10] BEGIN GPUImplHardware::DoGetCLCompute # 00086_2018/10/28_00:35:55.385(+00.000)[f10]  GPUImplHardware::DoGetCLCompute: AIF::OCL::Context context(properties, *iDev); # 00087_2018/10/28_00:35:55.723(+00.338)[f10]  GPUImplHardware::DoGetCLCompute: AIF::OCL::CommandQueue cq(context, *iDev, false, true); # 00088_2018/10/28_00:35:55.723(+00.000)[f10]  BEGIN GPUImplHardware::MeasureCLCompute # 00089_2018/10/28_00:35:55.771(+00.048)[f10]   GPUImplHardware::MeasureCLCompute: clFinish # 00090_2018/10/28_00:35:55.772(+00.000)[f10]   GPUImplHardware::MeasureCLCompute: result=0.00846848 # 00091_2018/10/28_00:35:55.772(+00.000)[f10]  END GPUImplHardware::MeasureCLCompute, duration=0.0488671 # 00092_2018/10/28_00:35:55.772(+00.000)[f10]  timeForKernelExecution=944.68 # 00093_2018/10/28_00:35:55.772(+00.000)[f10]  GPUImplHardware::DoGetCLCompute: result=944.68 # 00094_2018/10/28_00:35:55.772(+00.000)[f10] END GPUImplHardware::DoGetCLCompute, duration=0.387433 clgpu[0].CLCompute=944.68 NumNativeGPUs=0 snifferEnd="2018-10-28_00:35:56" stderr: ... View more

Hm, I never see that screen.  Here are my prefs; you can look to see what I do differently. Sorry for the ordering; it's the way the forum added the files. -Noel ... View more

By the way, I did a little more research on the ProPhoto RGB profile.  According to this page, there's actually a linear section of the tone curves very close to black: ProPhoto RGB color space - Wikipedia The cutoff for the linear section is 1/512, or 0.001953125.  The designers clearly envisioned it being used with high bit depth data. No particular reason for mentioning this, though it's food for thought...  If a particular color-management implementation forgets to account for that section (or approximates it) it would introduce inaccuracies near black... -Noel ... View more

You might want to consider watching for a patch to be released by Adobe before giving it another shot.  Adobe does update their software from time to time to fix bugs. Also note that you can easily have Photoshop CC 2018 and 2019 installed at the same time.  Just instruct Creative Cloud not to uninstall the prior version to maintain the use of it.  The Creative Cloud application can maintain both versions for you.  You just have to make some different selections in pull-down menus. -Noel ... View more

Hi, yeah, thanks, I've tried a bunch of different monitor profiles.  The error seems to follow the image profile.  And as we've learned here, changes nature occasionally depending on other as of yet unknown factors.  It's really encouraging that on some of your systems it's working AOK. A workaround is clear - if the on-screen color accuracy with ProPhoto RGB is of high importance, use Basic GPU mode. Otherwise, with virtually every other profile the GPU Normal and Advanced modes (i.e., color-management by Adobe GPU software) are fine.  I personally don't use the ProPhoto RGB profile much, though I have occasionally set it as the conversion target for Camera Raw, then done software conversions once the image is opened into Photoshop and processed a bit.  This can be helpful if subject material with brilliant bright reds (e.g., Christmas flowers) are photographed. -Noel ... View more

The various settings for UI Font Size have traditionally been not very different.  However, I'm not sure this is the setting that is intended to give you the results you want. What do you see in the rest of your preferences panel on your Mac?  I ask because the newest versions of Photoshop are supposed to be able to scale the UI overall to match the resolution of your display, and that capability is influenced by the UI Scaling setting. What do you have for UI Scaling? -Noel ... View more

All modern Photoshop versions (not sure how many years back that feature goes) autosave backup copies for you in case Photoshop crashes.  Did that not help you recover the lost file? -Noel ... View more

Further experimentation reveals the results are changed by the choice of color engine one makes in the Edit > Color Settings...   If for example I choose the Microsoft ICM color engine instead of Adobe (ACE), I see a noticeable shift in the color inaccuracy and brightness of the dark parts (they're brighter with the Microsoft ICM).  I don't see a difference by tweaking the 3 checkboxes, but I haven't done an exhaustive test. Here's what I've got for color settings: Note that closing and restarting Photoshop is required to see the change take effect. -Noel ... View more

https://forums.adobe.com/people/rob+day  wrote I get similar capture artifacts no matter what the profile assignment is, but they never show in the file that's being captured, either in appearance or the numbers. I'm not doubting that it's a problem, I just can't reproduce it. Curiouser and curioser...  Yes - I also see that with any profiles that don't match my reference sRGB monitor profile only when CPU-based color-management is being done, not when GPU-based color-management is being done.  This is a surprise to me; I've always assumed the grayscale was pure, because without so much extra saturation the errors are not perceptible. Each of these are gray gradient fill layers expressed in the listed profiles, displayed on my monitor, screen grabbed, and saturation of the screen grab increased to +100 twice. This forum botches up image attachments, but note the major color inaccuracy in 1 of the 4 images in the first set, and tiny pixel-width lines in 3 of the 4 images in the second set. As displayed in Photoshop CC 2019 with GPU color management: As displayed in Photoshop CC 2019 with CPU color management: -Noel ... View more

At this point I'm convinced there's something special about the ProPhoto profile itself. A (small) new piece of info.  I had thought that my own software was rendering the grayscale completely as gray, but lo and behold (and this is something I see in @rob day's post above as well) with extreme saturation there are tiny color errors in single pixels right at the transitions between adjacent levels (in the 8 bit screen grab world).  That probably made no sense.  This hyper saturation-enhanced comparison may help (Photoshop display on top, what I *thought* was a correct rendition on the bottom, but look closely): Those tiny lines show up in @rob day's screen grabs above if you push the saturation way up. Dag, please do a screen grab of the gray gradient as displayed on your system, hyper-saturate it, and post it here. I  wonder if these color inconsistencies are just a matter of magnitude, always there (because of something about the ProPhoto profile) but being (mostly) covered up by roundoff error in some cases and not in others. -Noel ... View more

Hi Trevor, You're too kind.  I'm just here getting a feel for what's up with Photoshop lately in the world, and to help out however I can. -Noel ... View more

Ah well, the file is identical to what I have. I'm out of ideas for the moment, except perhaps that the disappearance of the bug has to do with planetary alignment... -Noel ... View more

Hey Dag, if you're still seeing your ProPhoto documents without the cyan banding, could you please share your copy of the ProPhoto.icm file?  I want to see if there could possibly be a difference. -Noel ... View more

Often there are settings you can throw to re-enable old functionality, yes. Sometimes you have to get a bit geeky and edit PSUserConfig.txt to get to some of them. -Noel ... View more

Sorry, I miscounted before I guess.  Just 23... -Noel ... View more

The "new world" of rapid software releases and fast networking to download big files quickly to fix problems is why Adobe doesn't actually replace your older version when they make a version release.  Before uninstalling (which, by the way you didn't need to do; Creative Cloud allows you to retain and use both new and old versions), did you try making the configuration change to re-enable the Legacy Compositing process (in the Performance preference panel)? I did some counting, I never remove old versions (plenty of spare disk space), and between 32 and 64 bit editions, I actually have 25 different Photoshop versions installed. May I recommend, in the future, if you're going to download and install a new version that you consider keeping the older version installed. Meanwhile, I'm sure Adobe is working hard to create a 20.0.1 release that will fix the big problems.  -Noel ... View more

Yeah, I think that weird blotchy color thing was me opening an intermediate file I had created in a different folder on the way to making that proper grayscale PNG.  Sorry for muddying the water with that. The cyan banding problem with previews of images expressed in the ProPhoto RGB color space is still a real issue, however. -Noel ... View more

I tested above in 2019, but I've seen the ProPhoto cyan cast issue before in 2018 and earlier versions, going all the way back.  Apparently it's appearance is dependent on something we've yet to nail down. The second issue, which I just uncovered above, may be my fault.  I re-opened the PNG file I posted above and I haven't been able to reproduce bringing out any weird colors with any number of Saturation steps.  I may have opened a different test file from my History to get the effect with the neat patterns. Here are reproductions of the ProPhoto cyan cast problem, with settings like yours... Photoshop CC 2018 "girl in drug cloud splash screen edition": Photoshop CC 2019 "cloud headed dude splash screen edition": As you can see, even with the same settings you're using (e.g., no 30 bit in my case) the color banding remains. The samples all show equal R, G, and B values, whether or not point samples or averaged samples are made.  It must be purely a monitor display issue. The cyan banding issue doesn't show up in the Navigator display, by the way.  I believe Photoshop must always use CPU color-management for that. -Noel ... View more