After the last update, Photoshop started blinking blinking like a
stroboscope whenever I opened an image file.

I rebooted the PC, uninstalled and reinstalled Photoshop, but it would
continue flashing like a stroboscope.

Finally, I found this in the Adobe forums:
https://community.adobe.com/t5/photoshop-ecosystem-bugs/after-photoshop-latest-update-screen-starts-blinking/idi-p/13673834?profile.language=de

All I can say, my goodness, why can't Adobe deliver a product which does
not blink or require users to "deactivate native canvas" in the
settings. Don't they have a quality control?
--
Alfred Molon

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

On 24/03/2023 9:25 am, Alfred Molon wrote:
> After the last update, Photoshop started blinking blinking like a
> stroboscope whenever I opened an image file.
>
> I rebooted the PC, uninstalled and reinstalled Photoshop, but it would
> continue flashing like a stroboscope.
>
> Finally, I found this in the Adobe forums:
> https://community.adobe.com/t5/photoshop-ecosystem-bugs/after-photoshop-latest-update-screen-starts-blinking/idi-p/13673834?profile.language=de
>
> All I can say, my goodness, why can't Adobe deliver a product which does
> not blink or require users to "deactivate native canvas" in the
> settings. Don't they have a quality control?

Instead of finding this workaround maybe they could have put the effort
into fixing the problem and issuing another update...

geoff

On Thursday, 23 March 2023 at 20:41:01 UTC, geoff wrote:
> On 24/03/2023 9:25 am, Alfred Molon wrote:
> > After the last update, Photoshop started blinking blinking like a
> > stroboscope whenever I opened an image file.
> >
> > I rebooted the PC, uninstalled and reinstalled Photoshop, but it would
> > continue flashing like a stroboscope.
> >
> > Finally, I found this in the Adobe forums:
> > https://community.adobe.com/t5/photoshop-ecosystem-bugs/after-photoshop-latest-update-screen-starts-blinking/idi-p/13673834?profile.language=de
> >
> > All I can say, my goodness, why can't Adobe deliver a product which does
> > not blink or require users to "deactivate native canvas" in the
> > settings. Don't they have a quality control?
> Instead of finding this workaround maybe they could have put the effort
> into fixing the problem and issuing another update...
>
> geoff
It could be people that have particular versions of windows or graphic cards so not all users are affected.
Modern siftware is quite complex and differnt drivers etc can have an effect.

I wonder if any Apple users have been affected.

In article <35036a10-f09b-4e81-8893-aa91d891c61fn@googlegroups.com>,
Whisky-dave <whisky.dave@gmail.com> wrote:

> > > All I can say, my goodness, why can't Adobe deliver a product which does
> > > not blink or require users to "deactivate native canvas" in the
> > > settings. Don't they have a quality control?
>
> > Instead of finding this workaround maybe they could have put the effort
> > into fixing the problem and issuing another update...
> >
> It could be people that have particular versions of windows or graphic cards
> so not all users are affected.
> Modern siftware is quite complex and differnt drivers etc can have an effect.

that's almost always why.

photoshop pushes hardware to its limits and sometimes problems appear
with some configurations.

adobe can't fix problems with products they don't make. all they can do
is release a workaround and hope that the actual problem is eventually
fixed.

> I wonder if any Apple users have been affected.

probably not.

Am 24.03.2023 um 13:54 schrieb Whisky-dave:

> It could be people that have particular versions of windows or graphic cards so not all users are affected.
> Modern siftware is quite complex and differnt drivers etc can have an effect.
>
> I wonder if any Apple users have been affected.

Well, I've never had an image processing application doing this kind of
blinking nonsense.

BTW, also Adobe Bridge malfunctions. After I let it index a folder with
RAW files, after the indexing is completed it continues running in the
background consuming 20-25% CPU. It does so, even after I closed Bridge.
The only way to stop it is to kill the process in the task manager.
--
Alfred Molon

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

Am 25.03.2023 um 11:08 schrieb Alfred Molon:

> BTW, also Adobe Bridge malfunctions. After I let it index a folder with
> RAW files, after the indexing is completed it continues running in the
> background consuming 20-25% CPU. It does so, even after I closed Bridge.
> The only way to stop it is to kill the process in the task manager.

I posted this problem here:
https://community.adobe.com/t5/bridge-discussions/adobe-bridge-permanent-cpu-usage/td-p/13677906

then found this other thread where somebody is reporting the same problem:
https://community.adobe.com/t5/bridge-discussions/adobe-bridge-13-0-3-still-very-broken-regarding-performance/td-p/13672843

One poster is writing that he reverted to Bridge CC 2018 "because its
literally 100x faster and smoother then this".
--
Alfred Molon

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