What's New in Photoshop CS17?

I hope they staighten out the version numbers while they are at it.  It is confusing to have CS6 which version 13.x that works with ACR 7.x and includes Bridge CS6 which is version 5.x.

Lets have everything the same -  CS17 version 17.x that works with ACR 17.x and Bridge CS17 version 17.x.  Would save lots of confusion.

You sure?

My understanding was that they were going to start over with two different letters and restart the numbering again, i.e., Adobe Photoshop SV (Subscription Version), SV2, SV3, etc.

-Noel

Click on the OP topic and it takes you to an Adobe webpage.

Firefox did exactly that going from dot (3.01, 3.03) releases to whole integers, breaking plug-ins that never checked for versions that far ahead.

So yeah, April Fool's Day

Curt Y wrote:

 

I hope they staighten out the version numbers while they are at it.

Seems to me that version numbering is becoming increasingly irrelevant given the incremental feature changes being progressively rolled out with the Cloud - all of which are CS6.

There are so many versions (Cloud and non-Cloud) of Photoshop CS6 and Dreamweaver CS6 that I've lost track.

Makes forum support very tricky - especially when people don't know, or care about, the difference between Photoshop 6 and CS6.

We now need to follow build numbers rather than versions and I don't see anyone salivating about what's coming in CS7 - that buzz in the air just before a new version arrives from Santa Adobe seems to be missing. It's more about version number fatigue and confusion in the community.

Nice April Fool although every online article I read today was presumed guilty until proven innocent.

Great one!

I also have heard that Adobe is going to bring back the CSI Version, last seen in the days of CS2:

Hunt

Curt,

Check your calendar.

Hunt

My comments still stand whether it is CS7 or CS17.  If they bump it to CS17 they can charge more as user has saved on upgrades for 10 versions.

Oh I do agree. Version numbering/naming has gotten quite confusing.

Throw in Photoshop Elements users, who hit here by mistake, and just state "Photoshop 11," when asking a question.

Similar confusion happened back at Premiere Elements 4.0, which matched up to Photoshop Elements 6.0. Adobe fixed that, by moving PrE up to PrE 7.0, along with PSE 7.0. Still, we see questions about PrE 5 and 6, which never existed.

Going way back, when Adobe took Premiere (no Elements, or Pro), from version 6.5 to Pr 7.0. Well, at the same time, they added the term "Pro," and also officially took what had just been released as Premiere 7.0, and Premiere Pro 7.0, and renamed it Premiere Pro 1.0. Other than boxes, and the printing on most of the paperwork, those three versions were all basically the same version of Premiere. Talk about confusing. [Even many later Premiere staff were unaware of that Premiere Pro 7.0, until we found photographs of the box and manual.]

At least the CS 6 versions of almost everything, help, but then we still see that the updates are 13.x.x, and some refer to PS CS 6 as PS 13. Maybe we DO need to just go to CS 17... ?

Hunt

PS - Loved the Content Aware Content feature. Now, if they would only add the "pretty" Filter.

Maybe we DO need to just go to CS 17... ?

True to form, Adobe won't be able to resist a CS17.1 Cloud-only update within a week or two (that'll remove all menus, introduce a Ribbon so we can find hard-to-locate deeply nested menu items and enhance productivity -- and go touchscreen only) unless your name is Frank and you qualify for 17.2 and anyone born on a full moon will get a special release 17.3.....

Then there's the 17.0.1 activation fix for perpetuals, who won't get the Ribbon until CS18...

Somehow, I think that you could be correct.

Hunt

No, thank you!

Lot's of fun, and I even used your article for a post to The Video Lounge, but added some Apple Final Cut Pro comments to it.

Also, as noticed, there WAS some legit discussion, that came from the post.

Hunt

I am using Photoshop Version 60.064 so version 17 will be going backwards

Just try this script....

alert(BridgeTalk.getTargets(null).join('\n'));