
D Fosse
Community Expert
D Fosse
Community Expert
Activity
6 hours ago
@Michael26531295kdax
That wasn't what anyone said - it was just mentioned in passing as a possible cause (hacker-modified code). Which isn't entirely unreasonable, given the extremely high volume of pirated copies being offered on the internet, to unsuspecting buyers.
But the general consensus is that this is most likely the GPU driver. If not that, then possibly an overheating/malfunctioning hardware component.
The bottom line is in any case that a modern application cannot cause a BSOD. That's prevented by sandboxes and insulating layers. What the application can do, is trigger a BSOD by making specific calls that expose latent problems.
... View more
7 hours ago
Agree with Axel. The only logical conclusion is that Lightroom is the real problem.
... View more
9 hours ago
First of all, I would reset SFW preferences, not Photoshop preferences (you need to google that; I can't recall which keys to press as you launch. But either way you can rename/move the SFW settings folder in your user account, which does the same thing).
Secondly - the preferences are much more than your own user settings. It's the sum total of the application configuration, including lots of hidden parameters that are dependent on other settings. It's complex, and that's why corrupt preferences can cause weird and unpredictable behavior.
... View more
9 hours ago
1 Upvote
A preset will not work the same way on an RGB file and a raw file.
That has nothing to do with the applications, but is a result of how the data are encoded in the file. Any numerical adjustment is relative to the color space - the three primaries and the tone response curve.
A raw file is linear (gamma 1.0) with ProPhoto primaries - at least it is by the time the presets are applied (out of the camera it's grayscale).
Once opened into Photoshop, the tone curve is not linear, but can be gamma 2.2, 1.8, or the rather idiosyncratic sRGB curve. The primaries are not necessarily the same either, they can be sRGB, Adobe RGB or DCI-P3. All of this affects what a certain adjustment will do.
Just as a very simple illustration, setting the black point at 1 or 2 in a ProPhoto file will usually result in significant and noticeable black clipping. Doing the same in an Adobe RGB file will probably not be very visible at all.
And, since this seems to be an extremely common misunderstanding: you do not need to match color settings or profiles between Lightroom and Photoshop. The whole point of color management is that color spaces do not need to match. Preserving color from one to the other is what color management does. Any profile you set in Lightroom will be correctly treated and correctly interpreted in Photoshop.
... View more
18 hours ago
@patricktheart
If you lose your preferences in minor dot updates, something's wrong, like not having full administrator privileges in your user account.
With a major whole-number version update, preferences do not carry over, they never have. There is an option to migrate preferences, but I don't recommend it because of the high risk of accumulated errors carrying over as well.
As for actions, brushes, anything that can be saved out - save out and keep it in a safe place. Then it can always be easily reloaded.
... View more
18 hours ago
2 Upvotes
Let's get some realism into this. Have you scrolled down to check all the other resource hog processes running? This is just a random screenshot from a cold started machine, no applications running. And no, I have no idea what all this is:
And if you take a closer look, these CC processes aren't actually doing anything. They're just sitting there.
A few hundred MB of memory is totally insignificant. Once you open some image files to do actual work, you'll be needing orders of magnitude more memory than you have installed in total, so Photoshop uses its scratch disk to handle all the data. However much you have installed, there's not enough RAM to handle that. That's not Photoshop, that's the reality of editing raster based pixel images.
If you have performance problems, this is not the reason.
... View more
‎Feb 24, 2025
11:49 AM
Do not attempt to install on a non-system drive! It's the wrong way to go about it.
You only save around 2-3GB, which is absolutely negligible in this context. It's a drop in the ocean. You can free up 10-50 times that by doing a thorough cleanup on your system drive!
In any case, a large part of the installation will still end up in your user account on the system drive.
Start by running disk cleanup in Windows. That can be surprisingly effective.
If you're using Bridge, purge the cache. Empty the recycle bin. Take a look around your user account. All of your applications dump things here that you probably don't need, a lot of it won't be removed again even if you uninstall the application.
Hibernation can be disabled, that alone can give you 10 GB or so.
There's an excellent free utility called WinDirStat that shows you exactly what fills up your drive and where it is.
And all this is just to get Photoshop installed. To actually get some work done, you need about 100-250 GB for the scratch disk. You can get away with less, say 50, if you work with small files, don't have more than one open at a time, and reduce history states to 2-3.
... View more
‎Feb 24, 2025
11:19 AM
1 Upvote
@QINGCHARLES
To repeat what I wrote above:
Photography is, or can be, art, and as such you can do whatever you want, with whatever tools you find applicable. But to put your name on it, it has to be your own work. The level of manipulation is irrelevant, as long as it's your manipulation.
Photoshop has never been an ethical problem. You had to do the work to get what you want. With AI, an outside agent is doing work that you claim as your own. That's unethical. To me, this is a crystal clear line in the sand and I have no problem seeing where it goes.
Again quoting myself, I don't have a problem with AI as long as it's clearly stated and upfront.
... View more
‎Feb 24, 2025
07:28 AM
I can't reproduce it. The tonal values of the image are preserved, so you won't necessarily get 128 - but you should get neutral gray R=G=B on the clicked point. I get that here.
This isn't something I normally use, so I may be missing something.
... View more
‎Feb 24, 2025
06:33 AM
Excellently put, @Kevin Stohlmeyer
However:
digital cameras themselves manipulate and deceive by interpreting what they are capturing with presets.
Analog cameras and darkrooms did that too. That's not the breakpoint here. The great divide is passing AI-generated material off as your own creation. That's deception and fraud, by definition. You didn't do it.
@QINGCHARLES Arguing that "it's just a little bit" is a false and invalid argument. If it was that little, you wouldn't need to use AI.
Photography is, or can be, art, and as such you can do whatever you want, with whatever tools you find applicable. But to put your name on it, it has to be your own work. The level of manipulation is irrelevant, as long as it's your manipulation.
I don't have a problem with AI as long as it's clearly stated and upfront. It'll be dull and boring, because AI can never invent, only imitate and copy, but it'll be ethical. It's the desire to deceive that gets me every time.
... View more
‎Feb 24, 2025
04:57 AM
1 Upvote
As with everything else, it's the lifetime of the product, not the lifetime of the user.
Fifteen years is a pretty good return on investment. If you buy a computer, do you expect that to be fully functional and up to date for fifteen years? Of course not. If it broke down after, say, ten years, you wouldn't sue the company that made it, would you?
There's a kind of mental trap here that many fall into. Since it's not a physical thing, it's expected to "last forever". But it doesn't, because it gets outdated and obsolete. The rest of the world has moved on.
... View more
‎Feb 23, 2025
10:32 PM
It has always been a golden rule of computing to never use period in the filename. It's just one of those things you don't do. Make it a habit to use underscore instead.
A period signals that what comes after is the file extension.
Often you can get away with it because Windows is smart enough to count backwards, stopping at the last period. But if, say, you have set Windows to hide file extensions, as many do, things go wrong. Just don't do it.
... View more
‎Feb 23, 2025
12:39 PM
1 Upvote
Not sure what the problem is - you have an active button to save a new set of shortcuts. That's the one you need.
You can also save shortcuts as part of a whole workspace, that can sometimes be even more convenient.
If you choose a shortcut that is already taken, you'll get an option to override and replace the old shortcut. Just hit enter.
... View more
‎Feb 23, 2025
10:57 AM
@korkmaz_8987
You should always have file extensions visible. You apparently had them hidden, and that's when it's easy to get double extensions like in your case. Keep that box unchecked.
The problem elsewhere in this thread is corrupt files, regardless of extension.
... View more
‎Feb 23, 2025
09:20 AM
1 Upvote
See the troubleshooting guide below, in particular this section:
6. Check and delete the TempDisableGPU3 or TempDisableGPU2 files
Using the same methods that you used to find the Logs folder, find the CameraRaw or GPU folder.
On Windows, the location is: %APPDATA%\Adobe\CameraRaw\GPU
On Mac, the location is: ~/Library/Application Support/Adobe/CameraRaw/GPU
If an unhandled, fatal error occurs during GPU initialization, Camera Raw or Lightroom leaves behind a TempDisableGPU3 file (or TempDisableGPU2 in some cases). In the GPU folder, find the subfolder for the application you are using and check for these files.
https://helpx.adobe.com/camera-raw/kb/acr-gpu-faq.html?x-product=Helpx%2F1.0.0&x-product-location=Search%3AForums%3Alink%2F3.6.6
The point is that this file is supposed to stop ACR from launching if there's a system error - but if the error no longer exists, deleting this file lets ACR initiate again.
... View more
‎Feb 23, 2025
07:21 AM
First of all, are you saving directly to an external drive? If you are, save to local disk and copy the saved file over.
https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html
Other than that, "If I merge all layers then save PSD it will save in a fraction of a second" points to a problem with layer compositing. Try to uncheck these:
... View more
‎Feb 23, 2025
01:45 AM
@am3104photo
Thanks for reporting back, that's very interesting and very useful to know.
From time to time we see these reports of memory leaks, both on Mac and Windows, and it's always a mystery because most of us can't reproduce it. But this suggests it could be either a corrupt install or corrupt preferences (or both).
Going forward, a completely fresh install with fresh preferences will be my first suggestion.
We do know that migrating preferences is pretty common. I've always warned against that, because the risk of accumulated errors carrying over is high, and with new application code it may suddenly bring out latent issues.
I wrote above that this excessive memory reported is virtual memory including the Photoshop scratch disk. That turns out to be not correct, the scratch disk is not included here. It is virtual memory, but actually the system pagefile. When that fills up, the whole system chokes.
... View more
‎Feb 22, 2025
03:27 PM
Do you suggest using a Monitor Calibration Hardware tool such as "Datacolor Spyder X Pro?"
By @JGiunta
That is always recommended - but for the purposes of this discussion, it needs to be clear that it doesn't affect the file itself in any way. It just lets your monitor reproduce it correctly, so that you can properly see what you're doing, instead of having to guess.
As for your original question, as the others have pointed out - a "CMYK checker" is pointless if they don't specify which CMYK profile to use. And no, there shouldn't be general desaturation, only those colors that are out of gamut in the specific target CMYK profile.
I'd go elsewhere. There is no indication that Printify has a properly color managed process - or even that they know what they're doing.
... View more
‎Feb 22, 2025
03:12 PM
2 Upvotes
If you reset preferences on quit, the home screen will come right back. Resetting preferences returns the application to factory state, and that means home screen active.
Try this: Uncheck "auto show home screen", then open an image, close it out again, and then shut down Photoshop with just the regular workspace but no image.Then it should stick.
... View more
‎Feb 22, 2025
01:31 PM
It's not about the "same" zoom ratio. It's about 100% specifically.
100% means that one image pixel is represented by exactly one physical screen pixel. There is no screen resampling, so screen resampling algorithms are not in the equation. You see every image pixel, as it is in the file.
... View more
‎Feb 22, 2025
01:21 PM
1 Upvote
I don't think this is difficult at all. If you don't want your images tagged as AI, then don't use AI.
... View more
‎Feb 22, 2025
11:31 AM
I don't understand this. If you're using Generative Fill, you're using AI. You can't pretend you're not, and you can't try to pass it off as something it isn't. That's not ethical.
If you're using the Remove Tool, you can turn off AI.
... View more
‎Feb 22, 2025
10:08 AM
This is something I have never, ever heard of before.
It does sound like something is interfering with either the monitor profile, or the calibration tables. The latter sounds more likely. In a Mac, there is a series of presets that could easily interfere with any calibration tables made by a calibrator.
... View more
‎Feb 22, 2025
10:03 AM
1 Upvote
For my part, I would like a toggle in Photoshop to prevent all use of Generative AI so we can avoid this situation for images where we need to show that it is entirely our own work.
By @jane-e
Yeah, that's what all of this boils down to. If they could just do that, this whole discussion would be moot.
If you use AI, own it.
If you don't want to use AI, just turn it off entirely (that's what I'd do).
... View more
‎Feb 22, 2025
06:33 AM
1 Upvote
@SK321
It's very easy to avoid the tools in Photoshop that use generative AI. That is entirely under your own control. Both the Remove tool and Content-aware fill can be set to not use AI.
If it's just a speck of dust, why would you need AI to remove that? We have removed dust without any problems long before AI.
What surprises me nowadays is how AI is considered necessary for even the most trivial tasks.
... View more
‎Feb 21, 2025
02:28 PM
Picks correctly from the pasteboard here too.
... View more
‎Feb 20, 2025
11:26 PM
OK, got it. Does seem like a bug. Not at my workstation right now, but I'll try later and see what happens.
... View more
‎Feb 20, 2025
02:29 PM
Not sure I understand the problem - according to the Layers panel, the light color is the top layer in the lower screenshot? Your color picker is set to "sample all layers", so that checks out too.
There may be something wrong here, but your screenshots seem perfectly fine?
... View more
‎Feb 20, 2025
01:42 PM
Up left in the options bar at the top. It's half hidden under the tooltip in your screenshot.
... View more
‎Feb 20, 2025
01:39 PM
Actually, your system info does not list AVX/AVX2 support. It should be right up there at the beginning, under system architecture.
Obviously, an M2 will have AVX2 support. Apparently you're running under Rosetta emulation, could that be the reason? Current versions will run natively in Apple silicon.
... View more