Photoshop CC problem(s)

On Fri, 15 Jan 2021 17:21:01 -0800, Savageduck
wrote:

On Jan 15, 2021, Eric Stevens wrote
(in ):

On Tue, 12 Jan 2021 12:44:40 -0600, Bill
wrote:

Go into task manager, and check for 100% (or close) CPU, memory, or disk
read/write usage. The problem will be that it might take forever just to get
into task manager, but it’s helpful, so wait. If it’s Adobe tying
everything up, then take nospam’s advice, and reinstall everything. If
something else is responsible, let us know what it is. I have had very
similar problems from Malwarybytes, Foxit Reader, and one or two others. If
it something else, then you have to kill those programs, or uninstall them,
and then talk to their customer support. My problems tended to come after
updates to programs, and reinstalling them will not fix that.

I wish I had two Task Managers so I could watch both Processes and
Performance at the same time. In the absence of a second, I spend most
time watching Performance. With TBMT enabled only one core (out of 12)
is actively engaged and that is at 100%. With TBMT disabled loading an
image has an effect on the loading of all cores but not excessively.

But that is only part of the problem. Why does PS insist on starting
raw files in ACR, even when I have all the options switched off?

PS cannot open RAW files on its own. PS is assisted in that task by ACR, or ACR buried in LRc.

That's right to a point, but it has never previously offered me
LR-like panel of editing sliders. I have had to call them up from the
filter menu.

Why does it then run so slowly?

If you are somehow trying to force feed NEF files to PS without first having them digested by ACR or LR, PS will choke.

No, it's not choking. It's never choked. PS has opened NEF files as
easily as it opens any other.

Why are the sliders not working?

I think you are experiencing pilot error.

Nope. They won't move. I can't enter numbers, and if I wait for a
sufficiently long time the ACR window will shut down leaving the image
open in PS.

What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing engine.

Yes, I know that. In fact the great body of the ACR software is used
by both LR and PS. They are not separate installations. But LR opens
images almost instantaneously but ACR in PS does not, not even when
working normally. In PS there is something between ACR and the user.

PS has been unusable since before Christmas.

I believe it is your PS that has been unusable for you. I sugest that you try to work your NEF files via round trip from LR to PS and back. Then tell us whether or not PS is still not working for you.

Of course it's my PS that's been unusable for me. Why else should I be
raising the problem? I've already told you that there is no problem
opening raw files in LR, the same raw files that PS has difficulty
with.
--

Regards,

Eric Stevens

In article , Eric Stevens
wrote:

PS cannot open RAW files on its own. PS is assisted in that task by ACR, or
ACR buried in LRc.

That's right to a point, but it has never previously offered me
LR-like panel of editing sliders. I have had to call them up from the
filter menu.

add that to the ever growing list of problems you need to fix.

Why does it then run so slowly?

If you are somehow trying to force feed NEF files to PS without first having
them digested by ACR or LR, PS will choke.

No, it's not choking. It's never choked. PS has opened NEF files as
easily as it opens any other.

except for the 2 hour delay.

Why are the sliders not working?

I think you are experiencing pilot error.

Nope. They won't move. I can't enter numbers, and if I wait for a
sufficiently long time the ACR window will shut down leaving the image
open in PS.

another symptom.

What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing
engine.

Yes, I know that. In fact the great body of the ACR software is used
by both LR and PS.

it isn't.

They are not separate installations.

they can be.

But LR opens
images almost instantaneously but ACR in PS does not, not even when
working normally. In PS there is something between ACR and the user.

you mean chair.

PS has been unusable since before Christmas.

I believe it is your PS that has been unusable for you. I sugest that you
try to work your NEF files via round trip from LR to PS and back. Then tell
us whether or not PS is still not working for you.

Of course it's my PS that's been unusable for me. Why else should I be
raising the problem? I've already told you that there is no problem
opening raw files in LR, the same raw files that PS has difficulty
with.

different app.

On Fri, 15 Jan 2021 17:21:01 -0800, Savageduck
wrote:

But that is only part of the problem. Why does PS insist on starting
raw files in ACR, even when I have all the options switched off?

PS cannot open RAW files on its own. PS is assisted in that task by ACR, or ACR buried in LRc.

Why does it then run so slowly?

If you are somehow trying to force feed NEF files to PS without first having them digested by ACR or LR, PS will choke.

Why are the sliders not working?

I think you are experiencing pilot error.

Do you really imagine that after all these years I do not know how to
use the editing sliders in ACR?

What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing engine.

PS has been unusable since before Christmas.

I believe it is your PS that has been unusable for you. I sugest that you try to work your NEF files via round trip from LR to PS and back. Then tell us whether or not PS is still not working for you.

I don't know how to make this more clear but PS exhibits the same
problems irrespective of whether I try to load images from PS, open
with, drag and drop, and Process In from LR.

At the moment I am pondering the multitude of warnings to the effect
that "ESENT 642 - Video.UI (11500,D,2)
{2147430D-0838-490D-93CB-91829C2C9DEF}: The database format feature
version 9080 (0x2378) could not be used due to the current database
format 1568.20.0, controlled by the parameter 0x410022D8 (8920 |
JET_efvAllowHigherPersistedFormat" and similar. I do know that my
problem is associated with a high error reporting load. Quite what, if
anything, this might have to do with Intel TBMT I do not know but the
two seemed to be tied together in some fashion.
--

Regards,

Eric Stevens

On Jan 16, 2021, Eric Stevens wrote
(in ):

On Fri, 15 Jan 2021 17:21:01 -0800, Savageduck
wrote:

But that is only part of the problem. Why does PS insist on starting
raw files in ACR, even when I have all the options switched off?

PS cannot open RAW files on its own. PS is assisted in that task by ACR, or ACR buried in LRc.

Why does it then run so slowly?

If you are somehow trying to force feed NEF files to PS without first having them digested by ACR or LR, PS will choke.

Why are the sliders not working?

I think you are experiencing pilot error.

Do you really imagine that after all these years I do not know how to
use the editing sliders in ACR?

What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing engine.

PS has been unusable since before Christmas.

I believe it is your PS that has been unusable for you. I sugest that you try to work your NEF files via round trip from LR to PS and back. Then tell us whether or not PS is still not working for you.

I don't know how to make this more clear but PS exhibits the same
problems irrespective of whether I try to load images from PS, open
with, drag and drop, and Process In from LR.

At the moment I am pondering the multitude of warnings to the effect
that "ESENT 642 - Video.UI (11500,D,2)
{2147430D-0838-490D-93CB-91829C2C9DEF}: The database format feature
version 9080 (0x2378) could not be used due to the current database
format 1568.20.0, controlled by the parameter 0x410022D8 (8920 |
JET_efvAllowHigherPersistedFormat" and similar. I do know that my
problem is associated with a high error reporting load. Quite what, if
anything, this might have to do with Intel TBMT I do not know but the
two seemed to be tied together in some fashion.

Whatever the particular (peculiar) PS issue that you are experiencing is, it is unique to your setup, and usage. It seems that none of us here have the same problem, nor are any of us able to replicate your problem.

As for you ever being able to process/edit an NEF, or any other RAW file with PS without the intervention of ACR, that is not possible.
Directly opening a RAW file is beyond the capability of PS. ACR is needed. Drop a RAW file into PS and it will open ACR, a PS plugin, and depending on what options you used you can return to ACR from the filters menu to refine the process.

At this point I can’t see what any of us could say, or do to explain, or fix your unique PS problem.

--
Regards,
Savageduck

In article ,
says...
I haven't ignored the possibility of hardware issues but have found
nothing yet that could point me to one. It's more like a software
issue in the swamp that is Wintel.

All Wintel machines I have here at home (in total five) work
fine, so I wouldn't call Wintel a swamp.
--
Alfred Molon

Olympus 4/3 and micro 4/3 cameras forum at
https://groups.io/g/myolympus
https://myolympus.org/ photo sharing site

In article
.com,
says...
What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing engine.

Not sure what you mean here. When I double-click on a RAW file,
it opens with ACR in PS. I never use LR.
--
Alfred Molon

Olympus 4/3 and micro 4/3 cameras forum at
https://groups.io/g/myolympus
https://myolympus.org/ photo sharing site

On Jan 16, 2021, Alfred Molon wrote
(in s.net):

In article
.com,
says...
What is the difference between loading an image in PS and ditto in LR?

PS does not run ACR natively, LR is built with ACR as its native processing engine.

Not sure what you mean here. When I double-click on a RAW file,
it opens with ACR in PS. I never use LR.

Exactly! Any RAW file directly opened using PS will be opened in ACR. PS is not capable of opening a RAW file without the intervention of ACR, a PS plugin.

PS first supported RAW file processing as of Photoshop 7.0 with ACR v1.0. Things have come a long way since then, and I doubt that Eric ever used any version earlier than PS7. Before that not too many folks were shooting RAW.

LRon the other hand was developed around ACR, with ACR as its editing engine. One might say that LR is Bridge and ACR on steroids.

--
Regards,
Savageduck

On 12/01/2021 07:48, Eric Stevens wrote:

As far as I can tell I have the same problem irrespective of whether I
am using PS 2020 or 2021.

Has anyone encountered or heard of a similar problem and if so what
was the cause/cure?

This gearhead masturbation topic generated 66 replies. That's an order
of magnitude more than it would generate on a dedicated Adobe forum.
Meanwhile eff all response all week on topics on the actual subject of,
duh, photography.

--
Melanie van Buren

On Jan 16, 2021, Melanie van Buren wrote
(in article ):

On 12/01/2021 07:48, Eric Stevens wrote:

As far as I can tell I have the same problem irrespective of whether I
am using PS 2020 or 2021.

Has anyone encountered or heard of a similar problem and if so what
was the cause/cure?

This gearhead masturbation topic generated 66 replies. That's an order
of magnitude more than it would generate on a dedicated Adobe forum.
Meanwhile eff all response all week on topics on the actual subject of,
duh, photography.

It is photography. Post processing is part of it, and this is rec photo
*digital*. Computers are pretty much required. If a poster can’t get his PC
to run Photoshop, his tool for processing, we try to help. It seems to be a
PC problem, not an Adobe problem, and some people here are knowledgeable in
that area - both Windows and Mac. It’s not like this subject is crowding
out any others. It’s a quiet little group here, and can be very helpful on
varied subjects.

On 16/01/2021 17:54, Bill W wrote:
On Jan 16, 2021, Melanie van Buren wrote
(in article ):

On 12/01/2021 07:48, Eric Stevens wrote:

As far as I can tell I have the same problem irrespective of whether I
am using PS 2020 or 2021.

Has anyone encountered or heard of a similar problem and if so what
was the cause/cure?

This gearhead masturbation topic generated 66 replies. That's an order
of magnitude more than it would generate on a dedicated Adobe forum.
Meanwhile eff all response all week on topics on the actual subject of,
duh, photography.

It is photography. Post processing is part of it, and this is rec photo
*digital*. Computers are pretty much required. If a poster can’t get his PC
to run Photoshop, his tool for processing, we try to help. It seems to be a
PC problem, not an Adobe problem, and some people here are knowledgeable in
that area - both Windows and Mac. It’s not like this subject is crowding
out any others. It’s a quiet little group here, and can be very helpful on
varied subjects.

You can rationalize anything away like that. Anyone stop to think the op
may be running warez?

https://community.adobe.com/t5/photo...ies&filter=all


--
Melanie van Buren