Skip to main content
Participant
April 8, 2021
Open for Voting

P: Bring back "Shake Reduction" filter - Removed in Photoshop v.23.3.0

  • April 8, 2021
  • 188 replies
  • 76167 views

Änderungen am Programm ohne die User zu fragen - "Verwacklung reduzieren" in PS v.23.3.0 entfallen?

 

Mittlerweile ist man es als User gewohnt, dass Adobe Änderungen an Photoshop und Co. vornimmt.

Erst der "Fehler" seit Anfang Februar, dass die Ebenen bei der Nutzung von Color Lookup´s schwarz sind und somit nicht nutzbar (das Problem habe ich nach zwei Monaten endlich selbst gelöst) und nun fehlt schlicht und einfach wieder ein Scharfzeichnungsfilter, den viele wahrscheinlich nicht häufg nutzen, ich jedoch als finales Schärfen, diesen "Verwacklung reduzieren" mit Vorliebe eingesetzt habe.

 

Heute am Rechner, Bilder vom Ostersonntagmorgen mit Monduntergang, sitze hier, bearbeite und ... bin überrascht, dass ich meinen Filter nicht mehr finde.

 

Falls dieser doch noch irgendwo sein sollte, mal wieder irgendwo ganz hinten drin versteckt, bin ich dankbar für jeden Tipp.

 

Liebe Grüße und ein schönes Osterfest...
Gordon

This topic has been closed for replies.

188 replies

Known Participant
July 5, 2022

Developers are routinely removing useful tools and removing tools that function perfectly. Millenial programmers, out of touch with users needs, nothing new.

Inspiring
June 17, 2022
You obviously haven't been reading this thread
e.reed.rogers
Inspiring
June 17, 2022

@lesterk25013207I'm using  23.3.2 and it's still working. I don't let Adobe auto update anything so I think I'll stick with this until something comes along which warrants an update. RE Adobe disabling that filter: It seems very likely it IS the case that Adobe pushed out some code to disable this specific plugin because I have (VERY) old 8bf(s) that still work just fine. If that were to be confirmed it's just another (solid) reason to migrate.Why would anyone want to use a product from a company that does that?

Inspiring
June 17, 2022
As someone else posted, next time copy the Shake Reduction.8bf file and after each update that knocks it out, just reinstall it. Until Adobe can rectify this we will need to play the game. There have been a lot of complaints about Adobe for years but the truth of the matter is nothing else comes close. Photoshop is an incredibly complex software program and they are working constantly to debug and improve it, not to mention new tools and improvements come regularly. For me it is an awesome entity
lesterk25013207
Participating Frequently
June 17, 2022

Hi @franciss43197070 

Looks like your Shake Reduction.8bf solution was only a temporary joy for me.

After the latest update 23.4.1, when I click on Shake Reduction, I get this error message:

"Could not complete the Shake Reduction command because of disk error".

I tried increasing the scratch disk to no avail. I also tried to delete the Shake Reduction.8bf

and restart the software then shut it down and recopy the 8bf file into the folder and I still

get the same error. It looks like Adobe probably jammed the work around somehow.

Thanks.

 

 

 

TheDigitalDog
Inspiring
June 10, 2022

It's time to start demanding that Adobe create an API for both Filters and Adjustments so that 3rd party devs can start doing all the work that Adobe is uninterested or unwilling to do.

 

Start here:

https://developer.adobe.com/photoshop/uxp/guides/

https://developer.adobe.com/photoshop/photoshop-api-docs/

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Participating Frequently
June 10, 2022
The CEO of Adobe was interviewed on CNBC (Jim Cramer) last night and not
once did he mention photography. He did mention "creators" and "design" a
lot as this is their future. Adobe has moved on.
Earth Oliver
Legend
June 10, 2022

Folks, none of this is at all surprising. Adobe long ago abandoned doing any work on Filters, even though they're how so many of us fell in love with Ps in the first place. The vast majority of filters haven't been touched since the 90s and almost no new filters (Neural, i know) have been introduced since that time either. From my perspective, Filters (and Adj Layers) should be under constant development with updates, improvements and additions. That they're not just goes to show how out of touch Adobe is these days.
It's time to start demanding that Adobe create an API for both Filters and Adjustments so that 3rd party devs can start doing all the work that Adobe is uninterested or unwilling to do.

Known Participant
June 10, 2022

I reiterate, that a tiny operation like Topaz labs have managed to get their shake reduction app (Sharpen AI) working on M1 Macs. No it is not quite as slick as the PS filter was but it gives very good results. If a minnow like Topaz can make it work, why can't the behemoth that is Adobe do it. I can only assume it is lack of will and a loss of interest in pure photography, where they now prefer to be messing about with design and video. 

Participating Frequently
June 10, 2022

Thank you @franciss43197070 !!! LOL, yours is the TRUE solution to the problem for this missing filter; it is comical that the "solution" is so simple.  The FACT that this works is proof that there is nothing wrong with the filter at all. 

 

I know a lot of you are putting 100% of the blame for this on Adobe for not being able to get this filter to work on M1 Macs.  But I'm not convinced they are fully to blame.  This is PURE SPECULATION, but now more than ever I think Apple played a role in Adobe removing the Shake Reduction filter.  The existance of a very simple to use, quick, and effective feature that works perfectly fine on everything ecept an M1 Mac is as much or more of a knock on Apple as it is Adobe.  It just seems odd to me that Adobe would remove a perfectly functional feature on it's own just because it doesn't work on a very small percentage of user machines.  If M1 Macs were the lion's share of end user machines, then I would understand, but that obviously isn't the case.

 

Thank you again @franciss43197070.  Let's hope Adobe doesn't intentionally break this work around in an upcoming release.