Skip to main content
Inspiring
May 27, 2012
Not Prioritized

P: Please support PixelBender in CS6/CC

  • May 27, 2012
  • 211 replies
  • 4630 views

Why pn earth would Adobe drop this hugely successful and uniqe set of plug-ins/filters! I know a lot of people are very unhappy about this. I really hope Adobe changes its mind and comes out with an upgrade/patch to fix this problem.

211 replies

Inspiring
June 10, 2012
Products and features get end of life'd / discontinued all the time.
We don't like the situation much, either - but we really don't have much influence in this case.

PixelBender is not related to the script engine and not likely to be ported in such a way.
Inspiring
June 10, 2012
Some of them left the company, and most are busy on other teams now. It's not that simple.
Inspiring
June 10, 2012
The other team wrote it, and a Photoshop engineer spent much of the product cycle getting it to work correctly. The PixelBender team was part of the core technologies group within Adobe.
D Cam
Participating Frequently
June 10, 2012
Thanks for this Chris. It's nice to finally hear a voice on this. Seems as though it might be worthwhile to investigate what it would take for Adobe to recruit their own pixel-bender team, maybe acquire some from the old team, and if possible, the lead. The route pixel bender is using is the future in this area of design. I wouldn't dismiss it over such a setback.
creskdesign
Participating Frequently
June 10, 2012
It would became quite a hilarious situation if we did the same to our clients.

Anyway, please allow me to think out loud. Do you think the PB plug-in could be ported to the Script Engine in some kind of way? We all know there are lots of developers capable of doing this.
Known Participant
June 10, 2012
Chris,

"another organization"? What organization are you talking about?
Who wrote the Oilpaint filter for CS6? That "other team" or the Photoshop team?
Anyway, if Pixel Bender comes back any time, it should get the new UI that the blur gallery uses.
Inspiring
June 10, 2012
The Photoshop team did not write PixelBender, and does not have the specialized knowledge to maintain the code in PixelBender. PixelBender was written by another team, in another organization - and that team is gone.

Again, the Photoshop team can't do much about this. We wanted PixelBender, we spent a lot of time helping them get their plugin up shippable standards - but now the team that wrote it is gone, due to decisions outside of the Photoshop team's control.
Inspiring
June 10, 2012
That's your explanation?! Maybe I'm not understanding what "Photoshop Family" actually is. Are you Adobe employees? Who is it within the Adobe empire that does have control over software development?
creskdesign
Participating Frequently
June 10, 2012
Sorry, but this is too easy. The Photoshop team could do everything about this. What if they decided to back out? Would that be the end of Photoshop too?
Inspiring
June 10, 2012
Sorry, but there really isn't much that the Photoshop team can do about this.