Luminous Landscape Forum
Raw & Post Processing, Printing => Digital Image Processing => Topic started by: Rajan Parrikar on June 18, 2014, 03:24:30 pm
-
Why does the 'new' Photoshop CC not overwrite the existing copy? I just downloaded it and it sets up as a separate "Photoshop CC (2014)." I had to copy over the Preferences from my existing Photoshop CC copy. I don't understand why we should have multiple copies on our desktop.
Oh, and now I see that the Plugins/Extensions have not been ported over. Bloody pain. Or have I missed something?
-
This really isn't new behavior. If you went from CS6 to CC, you'd have the same condition.
-
This really isn't new behavior. If you went from CS6 to CC, you'd have the same condition.
I thought the behaviour would change now that we have the Cloud.
-
I thought the behaviour would change now that we have the Cloud.
I don't think it should. It's a delivery system. Would you want CC (2014) over-riding CC which you have to think of as the previous version, just like CS6/CC? There should be an uninstaller for CC once you're sure you're done with it. You may want to run both for awhile. CC 2014 should update itself from the cloud, presumably until CC 2015.
-
Of note, is that this new update breaks all or most existing extensions. The new version only works with HTML5 extensions, so my custom panels that I've been fine tuning for years, GuideGuide, a guide utility that I use every day, the Coolorus color picker that I use extensively, and other existing third party panels/extensions are now toast until they are rewritten.
I know that sometimes painful choices need to be made for the sake of advancing options in the future, but Adobe seems to have made another PR blunder in burying the lede on this front. Letting everybody know that this is an entirely different animal than the previous CC updates would have been a wise move. I'm happy that I can revert to using my previous version of CC, but don't think that this was handled very smoothly.
-
Why does the 'new' Photoshop CC not overwrite the existing copy? I just downloaded it and it sets up as a separate "Photoshop CC (2014)." I had to copy over the Preferences from my existing Photoshop CC copy. I don't understand why we should have multiple copies on our desktop.
Oh, and now I see that the Plugins/Extensions have not been ported over. Bloody pain. Or have I missed something?
I only have one thing to say (well maybe two). The first is GOOD GRIEF. The second is, what? I hope Jeff or Eric or someone will help us understand what's up with two versions of PS CC eating up valuable SSD space.
Rand
-
I only have one thing to say (well maybe two). The first is GOOD GRIEF. The second is, what? I hope Jeff or Eric or someone will help us understand what's up with two versions of PS CC eating up valuable SSD space.
Rand
It's always been like that. When a new version of ps came out ad you upgraded, you got both versions on your drives. Nothings changed from that aspect.
-
I only have one thing to say (well maybe two). The first is GOOD GRIEF. The second is, what? I hope Jeff or Eric or someone will help us understand what's up with two versions of PS CC eating up valuable SSD space.
What's not to understand? Is CS6 deleted or over-written when you install CC? Or CS5? No. CC and CC (2014) are completely different versions, just as CS4 and CS5 were and the installers for CC (2014) is doing exactly what all the other installers did. If you install CC (2014) and want CC as well, you've got it. If you want to remove it, there's a very good uninstaller. Gone. Again. CC and CC (2014) are to be thought of as CS4 and CS5; completely different versions.
-
It's always been like that. When a new version of ps came out ad you upgraded, you got both versions on your drives. Nothings changed from that aspect.
Now I am confused. Wasn't it one of the selling points of the CC concept that it updates itself more frequently and faster than stand-alone versions? In other words, if CC is always the latest and most up-to-date version, what is the point if having now two CC versions? Isn't it also the reason that the name (CC) did not have any version number attached to it (in contrast to CS6 for instance)?
-
Wasn't it one of the selling points of the CC concept that it updates itself more frequently and faster than stand-alone versions?
It does and it will. CC 2014 will get updates and new features, presumably until Adobe wants to brand a new version which is what they just did, hence Photoshop CC 2014. We can't have Photoshop CC naming go on forever.
There is no point in having two versions of CC and CC 2014 any more than having CS5 and CS6. Some people do that. Some want to work with the older version for awhile or make sure they can do production on the newer version, moving cautiously. If you update CC 2014 and want more room and don't need CC, uninstall it.
-
What's not to understand? Is CS6 deleted or over-written when you install CC? Or CS5? No. CC and CC (2014) are completely different versions, just as CS4 and CS5 were and the installers for CC (2014) is doing exactly what all the other installers did. If you install CC (2014) and want CC as well, you've got it. If you want to remove it, there's a very good uninstaller. Gone. Again. CC and CC (2014) are to be thought of as CS4 and CS5; completely different versions.
No, you're right of course. But I had a vision of the cloud versions being seamless and "continuous" - if that makes sense - with incremental updates/upgrades as it went along. At least that's what their advertising seemed to say. Not a big deal. I'll just nuke CC 6 off the drive.
Rand
-
... Adobe wants to brand a new version which is what they just did, hence Photoshop CC 2014...
Ok, so if CC 2014 is a new version, what exactly is new or different from CC? There should be something rather substantial to justify a new version, i.e., X.0, rather than incremental improvements that are more suitable for 0.xx updates.
-
Slobodan, I think you are trying to apply an unreasonable standard to Adobe's actions, by holding them to what they said they were going to do. ;-)
IMO, this appears to be largely, or at least somewhat driven by Adobe's desire to kill off Flash within the API. That's why the panels I mentioned, including those made with the now dead Adobe Configurator, no longer work. I'm sure that they didn't want to send off any alarms by mentioning another strike against Flash, and they would prefer to deal with some grumbling than mention that in any of their more prominent public statements. The last thing they want to do is to throw any red meat to the Flash haters. Unfortunately, this will only lead to further Balkanization of the Photoshop platform, instead of the previously stated goal of having more people running the latest and greatest version. As far as I can tell, none of the third party palette/panels works in the new version, and developers are madly scrambling to write new versions. At least those that are still willing to stay on the treadmill.
Regarding the new improvements, there certainly are some. None that would seem to justify an entirely different version, though, IMO, other than the reason I stated above.
-
Ok, so if CC 2014 is a new version, what exactly is new or different from CC? There should be something rather substantial to justify a new version, i.e., X.0, rather than incremental improvements that are more suitable for 0.xx updates.
Check the feature list, there's new stuff BUT because this is a subscription, with new features coming all the time, you can't think of this as the old school "we get a new name so now we need a slew of new features". Let's hope in aggregate, you are happy over X number of months and years subscribing that you are getting newer features you can use. New naming in a subscription doesn't appear to mean the same thing as a new version when the license was perpetual. And this is all new territory.
-
... because this is a subscription, with new features coming all the time, you can't think of this as the old school "we get a new name so now we need a slew of new features"....
So, because this is a subscription, the new school is "we get a new name so now we DON'T need a slew of new features??
Sorry, couldn't resist ;)
-
So, because this is a subscription, the new school is "we get a new name so now we DON'T need a slew of new features??
Number of new options over X number of (fill in time span) is different now. Simple as that. You don't get them all at once.
-
Interesting . . . in looking at the "program size" on my Win 7 machine, CC 2014 is almost a gig smaller. 1.99 gigs for PS CC (2014), 2.85 gigs for PS CC.
Rand
-
I'm wondering if I have a flaw in how the new code is released. I have the PS+LR $10/month combo deal for CC. I also have CS6 Studio of some extension type. I was presented with the CC download application with all of my CS6 files PLUS a full suite of CC files that extends beyond the LR+PS subscription I purchased.
It successfully downloaded the After Effects 2014 file for CC with a check mark verification. The rest of the 2014 versions downloaded, installed, but reported as failed. On closer review it says they did DL/install and looking in my program file I see all of the apps available to me. I clicked one and it wants me to verify my email....which I will....but I don't understand why these files were presented to me and why I was able to download them yet show a 'fail' within the adobe CC utility.
-
Now I am confused. Wasn't it one of the selling points of the CC concept that it updates itself more frequently and faster than stand-alone versions? In other words, if CC is always the latest and most up-to-date version, what is the point if having now two CC versions? Isn't it also the reason that the name (CC) did not have any version number attached to it (in contrast to CS6 for instance)?
Mine subscription did update throughout the year automatically. Personally, when a major new revision is released, I like the ability to have both active. Do you see this as bad...and if so, why?
-
Our friend Jeff did explain to us in minute details when CC was announced and CSx discountinued that Adobe had some technical limitations preventing the continuation of the perpetual licensing model in parallel with the new subscription one (I won't use the word cloud as it has little to do with the commonly accepted definition of cloud).
He explained that this was related to the way the code was built, in particular that CC would be managed only through incremental builts that were not compatible with the maintenance of 2 streams of code.
Now, what do we see? That CC is being upgraded in 2 ways:
- The incremental builds with point additions every few months (I personnally don't really bother looking at those upgrades, just no time for that and not enough encounter with material explaining the new features, not enough discussion in forums... I wonder how many % of users actually invest time in learning these new point upgrade features),
- Major builds at a frequency that seems similar to that of former CSx->CS(x+1) releases frequency.
With the existence of these major builds (CC 2014), I don't understand anymore the initial technical rationale explaining why CS7 could not have been released with a perpetual license in parallel with the new subscription model.
Besides, the confirmed availability of the CC+LR package at 9,99 a month without any condition of previous Adobe products ownership is simply a slap in the face of people like myself who have invested in Adobe's products for many years under the assumption that this would help acquire future products at a favorable pricing. Yes, it remains cheaper than the previous perpetual license deal, but the recognition of my past support to their business is gone.
The message is clear, Adobe doesn't value the investement we make in their products. Or, put in the other way, since they have made us prisonner of an eternal subscription model, they don't need to incentive us any longer to stay on board. We are stuck. In case anybody would still have had doubts about the way they look at us, this should be clear now.
Cheers,
Bernard
-
With the existence of these major builds (CC 2014), I don't understand anymore the initial technical rationale explaining why CS7 could not have been released with a perpetual license in parallel with the new subscription model.
Was there ever a technical rationale explaining why CS7 could not have been released with a perpetual license?
-
Was there ever a technical rationale explaining why CS7 could not have been released with a perpetual license?
According to Jeff, yes.
This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.
Cheers,
Bernard
-
…to please some MBA fed board members…
Fiduciary duties to shareholders.
-
I could see a big reduction in support issues by having everyone on the same revision of software. The CC model basically guarantees this by continually upgrading each CC out there to the latest greatest. With perpetual models, there were many different releases of PS active at once, providing much more stress on support.
I run a product that has many different versions active and trying to provide support for all these different versions taxes out our customer support group.
According to Jeff, yes.
This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.
Cheers,
Bernard
-
I could see a big reduction in support issues by having everyone on the same revision of software.
Except this is the opposite of what they just did with this new release. Now we have vanilla Photoshop CC and Photoshop CC 2014. For me to use the new features rolled out today, I will be running 2014. For my day to day workflow, though, I will have to revert to the previous CC, so that I can use the custom panels I built, and the third party extensions that no longer work with the newest API that is no longer compatible with Flash extensions or Configurator panels. As best I can tell, none of the third party extension vendors were ready at launch.
-
I'm not seeing the option to upgrade to Ps 2014. The only (2014) app I see is InCopy CC (2014), which I'm not using. I'm on Win 7 x64. Is anyone else not seeing the upgrade in Adobe CC updater app?
Jim
-
Yeh, I don't know why they did that...maybe they knew some people like you would need access to the previous version...but I know one of the goals of moving to the CC model was to get everyone onto the same releases to reduce support costs. Remember Adobe has a huge number of applications, not just PS and supporting all the different versions out there must be a nightmare.
Except this is the opposite of what they just did with this new release. Now we have vanilla Photoshop CC and Photoshop CC 2014. For me to use the new features rolled out today, I will be running 2014. For my day to day workflow, though, I will have to revert to the previous CC, so that I can use the custom panels I built, and the third party extensions that no longer work with the newest API that is no longer compatible with Flash extensions or Configurator panels. As best I can tell, none of the third party extension vendors were ready at launch.
-
I hope Jeff or Eric or someone will help us understand what's up with two versions of PS CC eating up valuable SSD space.
So far, all of the previous versions of Photoshop CC were "updates" that patched the core application to add new code. Photoshop CC (2014) is an "upgrade" that needs to have the entire new application downloaded because the new features and functions were beyond the scope of a code patch...note the (2014) meaning this is the first major upgrade...additional "updates" will patch the current new code.
In the future (prolly 2015) there will be another "upgrade" which will again require downloading and installing the whole app.
-
This was his main argument to sell the proposal that Adobe was not just a greedy monopolistic corporation looking for a way to extract even more cash from its faithful customer base to please some MBA fed board members expecting even more return on their investement.
Yeah, ya know...I'm not going down that road again...everything I said was true then (as it is now). What you want to make of it is your own business...
Note, the upgrade to Photoshop CC (2014) is free to subscribers...so, I really don't understand how you can spin that into a greedy Adobe argument.
-
Yeah, ya know...I'm not going down that road again...everything I said was true then (as it is now). What you want to make of it is your own business...
Note, the upgrade to Photoshop CC (2014) is free to subscribers...so, I really don't understand how you can spin that into a greedy Adobe argument.
Jeff,
Free to subscribers is an interesting way to put it. ;)
But you are correct that CC 2014 doesn't add, or substract, anything to/from the original greediness I believed motivated the move to a subscription only model.
Cheers,
Bernard
-
Free to subscribers is an interesting way to put it. ;)
So...Photoshop CC (2014) did not cost CC subscribers any additional fee for upgrading...so, it was a free (no cost included) upgrade. So, I'm wrong that I called it a free upgrade?
If you are spoiling for a fight, I decline...as I said, I'm not going down that road again. A whole lot of people reacted irrationally to the changes Adobe enforced. That's on them (and you). I gave up caring about what they (you) think...
If you want facts and/or knowledge, I'll give it–if you want to rant and rage, screw you...and yes, the Photoshop CC (2014) full app upgrade actually enforces my statement that dual code bases resulted in Adobe dropping CS7...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.
-
The way I see it Adobe was very prudent. As the new version didn't hold full compatibility to previous extensions (the cost of moving forward and making some improvements) they had the decency of launching it as a separate version, so we can have both at the same time until plug-ins and extensions are updated. That is a good thing. Yeah, "cc 2014" is kind of lame when you think about the concept they advertised of "the definitive and ever-changing Photoshop", but I think it was necessary for our own good.
-
Jeff, other than the new features I have read about, were there significant changes to the code base, aside from dropping Flash support from within the API itself? I'm just curious.
-
Jeff, other than the new features I have read about, were there significant changes to the code base, aside from dropping Flash support from within the API itself? I'm just curious.
Well, I can't say other than to say that the totality of the changes required a new app installation vs a code update via a patcher...and yes, rather than overwriting the older CC code it installed a new app partially due to backwards compatibility. It allows one to have both versions and decide on their own, which version to use.
-
Interesting. I was assuming that it was more about looking ahead, rather than anything that was needed for the new features just released.
-
Hi,
One thing that I noticed is that there is no longer a 32 bit version for CC (2014) so if you have any special plugin that works only on 32 bits, then you might want to keep the old CC version for some time (I can't think of other reason unless you're still using a 32 bit OS)
Regards,
-
Hey hey a new Photoshop. I am well excited. But then I used to get excited about a new enlarger in the old days. This feels a bit like that but it's free.
-
How can one establish which plugins will simply work by copy & paste from PSCC Plugins folder to PSCC(2014) Plugins folder? And which will fail or cause problems?
We could do with something comparable to what roaringapps.com does for OSX upgrades, listing what will work and what won't, but maybe that's not feasible
For starters, anyone know if PKS2 will work if I copy & paste the PG Toolbox Plugin Module folder into the new version's Plugins folder?
Jim
-
So, we’ve spent some time in this thread trying to deconstruct and understand Adobe’s latest software updates.
Would it not help everyone if Adobe were just clearer on this from the outset ? Wouldn't it be better just tell us what they are doing instead of leaving it for us to figure out ?
This thread has helped me understand some of what is going on with these software updates but I still don't understand why I am being offered another version of Lightroom (see this thread New Photoshop CC and Lightroom ??? (http://www.luminous-landscape.com/forum/index.php?topic=90922.0). Clicking on the link “What’s new” in the Creative Cloud window takes me to a web page talking about Lightroom June 2013. Thus, my confusion. It could mean that I will get Lightroom 5.5 but that the software update panel is giving me misleading information ? Or it could mean I get a new version of Lightroom ? Would be good to know.
(sound of distant gunfire – see New Photoshop CC and Lightroom ??? (http://www.luminous-landscape.com/forum/index.php?topic=90922.0))
-
For starters, anyone know if PKS2 will work if I copy & paste the PG Toolbox Plugin Module folder into the new version's Plugins folder?
Assuming the latest versions, that worked just fine for me under Mac OS X.
-
Hey hey a new Photoshop. I am well excited. But then I used to get excited about a new enlarger in the old days. This feels a bit like that but it's free.
Yep, free, of course if you forget that you have already paid for it through your monthly subscription fee. ;)
Cheers,
Bernard
-
Yep, free, of course if you forget that you have already paid for it through your monthly subscription fee. ;)
Is the glass half empty?
It is free for the new features. Old version without new features or new software with new features has a cost. There was always a cost too.
-
Jeff,
hence the new CC (2014) code base
The light is dawning... thanks. This the also accounts for the significant difference in program size, as I shared in an earlier post?
Rand
-
Adobe, I love the CC system, but this is retarded.
-
Adobe, I love the CC system, but this is retarded.
Agree... not exactly the clarion of clarity.
When I was fire chief for a fairly large agency, and I had a need to write a memo to "all hands," I'd take my draft and give it to the most junior person on the deparment. If they could read it and understand what I was "trying to say" I knew that I was "good." If they couldn't, I went back to the drawing board.
Adobe makes fabulous software. Clear communications/explanations ... not so much. ;D
Rand
-
Adobe is quite obviously run by tech geeks, for tech geeks. In contrast to Apple run by tech geeks but with the added buffer of a human interaction department to make sure things like this never make it out.
While *I* can look at this and see what's going on, you can bet your ass the VAST majority of users will be confused and CERTAINLY not know what to do for the best setup afterwards.
What this was telling me was the bottom 'Lightroom 5' was my current 5.4 version. Notice they don't even have the good sense to include the version numbers anywhere. Which wouldn't be a problem if they didn't do stupid stuff like we now see.
The top 'Lightroom 5' is the update, version 5.5. Up to this point I have never seen multiple instances, it simply says Update Pending for whatever is there. Again, no good sense here.
Then we have the genius of the Adobe team reverting BACK to version numbers when they said they were done (cc). Now instead of 'Photoshop CC' getting an update like has been done till now, we have the 2014 designations for most of the applications. First, STUPID versioning. What will the updates be called, 2014.1? Second, it's certainly not clear to the average user that this is an ALL NEW installation. You can bet most users will now have redundant, old versions hogging drive space. Hell I have seen photographers with 4 old versions still installed because they had no clue they were still there. Same with Lightroom.
CC was supposed to handle all this a LOT better. It boils down to shitty design by the Adobe staff. They need to REALLY look at how other companies handle things, like Apple or even Steam.
-
I'm not seeing the option to upgrade to Ps 2014. The only (2014) app I see is InCopy CC (2014)...
Logged out. Quit Adobe CC helper app. Started it again. Logged back in.
Fixed.
Jim
-
Assuming the latest versions, that worked just fine for me under Mac OS X.
Thanks Andrew. I'm on v2.0.7 of PKS2, so I'll give it a try :)
On the subject of Plugins, I notice that in PSCC I still have some that show up in the Finder with old-style ImageReady plugin icons, while others have a modern-style blue lego-brick icon. Is the icon any indication of the usability/ obsolescence of the plugin?
Jim
-
On the subject of Plugins, I notice that in PSCC I still have some that show up in the Finder with old-style ImageReady plugin icons, while others have a modern-style blue lego-brick icon. Is the icon any indication of the usability/ obsolescence of the plugin?
Not that I'm aware of.
And if anyone out there is using PK products on CC 2014 under Windows 8, love to know if that's working OK for you.
-
Great, and it broke the Edit In process. Now it launches the new PS CC 2014...but no image. Thanks Adobe, now I get to debug your shit...again. Win 7
-
Great, and it broke the Edit In process. Now it launches the new PS CC 2014...but no image. Thanks Adobe, now I get to debug your shit...again. Win 7
The order you install LR and PS has been a long standing issue. Install PS then LR, the Edit In 'link' should fix itself.
-
#1, I did the Update all in CC. That's not the issue. #2 the link works fine, as I said. PS launches. It just doesn't create the TIF anymore and open it. Now looking in the Adobe forums it's FILLED with people with major issues with 5.5. I do NOT suggest anyone update yet.
-
I'm going to try uninstalling LR and installing fresh.
-
No change...
I tried setting photoshop.exe as the 'External Application'. Same results. It's like LR is not producing the TIF file for editing. Tried all the settings, PSD, compression, bit depth - nothing. I'll try on another machine.
-
Works fine on my studio Win8 system, same process.
-
OK narrowing it down...works fine on a TIF file, not on a DNG. I'll do a new import and see if it works on a RAW...
...nope. So it has to do with ACR maybe?
-
ACR reads current, 8.5.
I'll try uninstalling PS, deleting every folder and starting fresh.
-
That did it. had to uninstall then COMPLETELY wipe all folders regarding PS and ACR. There were many spread out.
-
And then there's this (if you Windows folks find you can't use Develop module or can't launch):
https://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html
-
Assuming the latest versions, that worked just fine for me under Mac OS X.
Unfortunately that did not work for me on a Win 7 64-bit computer. PKS 2.07 one of the very few plug-ins I couldn't just copy and paste into CC 2014. What have other people experienced?
Regards,
David
-
Unfortunately that did not work for me on a Win 7 64-bit computer.
In what way? Any info will help fix the issue.
-
If you want facts and/or knowledge, I'll give it–if you want to rant and rage, screw you...and yes, the Photoshop CC (2014) full app upgrade actually enforces my statement that dual code bases resulted in Adobe dropping CS7...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.
For all software engineers on this forum, this statement from that same guy (??) whose inferiority complex pushes him to insult other members (e.g. "screw you" in the quote above), is simply insulting to their knowledge and their day jobs.
Branch management, version control, installation scripts, licensing demons, etc.. There are absolutely no technical reasons behind Adobe's decision. It was a business decision. Is it the right business decision for their shareholders? Future will tell. So far, what we have seen:
. Fewer key features introduced in comparable timeframes
. Emergence of lot of alternative software
. Move from PC to tablet continuing at a rapid pace
. Pirating is still going strong, particularly OUS
Oh well, that ship has sailed...
-
Oh well, that ship has sailed...
Yep...so, still beating the dead horse? That horse is dead (and you are still wrong about the "technical issues" relating to major code branches of super large cross platform applications but it's clear nothing I say will make a dent in your armor).
Sorry, I chose not to engage in this worthless discussion...from now on, you are talking to yourself.
-
In what way? Any info will help fix the issue.
Apologies for not being more informative. I have a Win 7 64-bit computer. I reinstalled PKS 2.0.7 after Ps CC2014 had been installed. But PKS did not show up in as selections in the File > Automate menu.
For that reason plus the fact that some panels I use did not work in CC2014, I have uninstalled CC2014 for the time being.
Best regards,
David
-
I reinstalled PKS 2.0.7 after Ps CC2014 had been installed. But PKS did not show up in as selections in the File > Automate menu.
The only time I've heard that happening is if there's a 32 bit plug-in installed for 64-bit Photoshop or vise versa. I'd download the latest installer and try again. You can also go into the PS help menu, select System Info and you'll see a report that includes what plug-in's loaded, which didn't.
-
I have the same problem - no PKS in Photoshop CC 2014. I tried downloading the latest installer and reinstalling and this did not solve the problem.
-
I have the same problem - no PKS in Photoshop CC 2014. I tried downloading the latest installer and reinstalling and this did not solve the problem.
Again,run the system info from Photoshop's Help menu, that would give us a clue what's going on.
Everything on Mac works as it should thus far. So maybe it's the installer? If you see it not loading in the report, that tells us one thing.
-
Again,run the system info from Photoshop's Help menu, that would give us a clue what's going on.
Everything on Mac works as it should thus far. So maybe it's the installer? If you see it not loading in the report, that tells us one thing.
I did. It's not listed as a loaded plug-in in help->system info, nor is it listed in help->about plug-in. It was listed in both places the previous version (Photoshop CC x64). I downloaded the installer today so I'm using the latest version of the installer but, for some reason, it is not getting installed correctly. If it help I'm running Windows 8.1 x64 Update I.
-
I did. It's not listed as a loaded plug-in in help->system info, nor is it listed in help->about plug-in. It was listed in both places the previous version (Photoshop CC x64). I downloaded the installer today so I'm using the latest version of the installer but, for some reason, it is not getting installed correctly. If it help I'm running Windows 8.1 x64 Update I.
Send me an email, I'll send you a zip to install manually.
-
Actually this may help other Win users. Here's a zip of PhotoKit Sharpener II that isn't an installer. Unzip, place directly into the Plug-In folder. Does it work? If so, we need to look into the installer itself. You can find the zip at:
http://www.digitaldog.net/files/PKSII_Win_toolbox plug-in module.zip
Make sure you also don't have any PG plug-ins in the CC 2014 directory.
-
Actually this may help other Win users. Here's a zip of PhotoKit Sharpener II that isn't an installer. Unzip, place directly into the Plug-In folder. Does it work? If so, we need to look into the installer itself. You can find the zip at:
http://www.digitaldog.net/files/PKSII_Win_toolbox plug-in module.zip
Make sure you also don't have any PG plug-ins in the CC 2014 directory.
We're making progress. I downloaded the zip file, unzipped it, deleted the PG plug-ins that were in the CC 2014 directory (presumable from the install attempt earlier today) and placed the newly downloaded files directly into the Plug-in folder. The plug-ins now show up in help->system info, help->about plug-in, and as a selection option in file->automate. Unfortunately, attempting to run any of the PG plug-ins from file->automate crashes Photoshop with the following generic error message "Adobe Photoshop CC 2014 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
-
Windows will close the program and notify you if a solution is available."
Yup, seems two issues. One is the installer which the zip process bypasses but then the bug you report which our engineer is looking into.
-
PKS2 installer works with CC 2014 on Windows 7/64.
-
...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.
I do understand this (I'm in the software business), and I'm also in agreement with an earlier poster that it is actually good that Adobe allowed for both CC and CC 2014 to coexist. But here's where I think Adobe should go one step further: As the OP pointed out, it is a REAL PAIN to have to re-create all your personal preferences each time a new code base for PS comes out. I for one would like to see some effort from Adobe to carry forward all possible user preferences into the new version. MANY software vendors do this as a matter of course with new installs over an existing application, and it would certainly make our life easier.
Dave
-
Adobe, I love the CC system, but this is retarded.
It is not absolutely clear. For example, what's the difference between "Install" and "Try" ? This appears on my CC installer app. I'm a full CC subscriber, so why the "try" ?
Besides, Yoda said "There is no try" :)
-
Has anyone found a fix for the interface bug in Photoshop CC 2014?
There are four choices of UI font size - Tiny, Small, Medium and Large - but it stays on Tiny even if one of the others is selected.
-
There are four choices of UI font size - Tiny, Small, Medium and Large - but it stays on Tiny even if one of the others is selected.
Quit and restart?
-
Quit and restart?
Restarting makes no difference - it's still stuck on 'Tiny' and the menus are all unreadable for me (font is far too small).
This is a bug in the UI. The 'UI Font Size' selector (in Edit>Preferences>Interface) worked fine in all previous versions of CC, but it doesn't work at all in CC 2014.
-
Works on this end after restarting. But to be clear, what changes is the font size in the Option's bar using Text Tool.
-
...If you understood software development, you would understand this.
I think that this is a weak argument. Are you a world authority on software development? If I could find some credited software developer that disagreed with you, would you change your mind?
-h
-
Works on this end after restarting. But to be clear, what changes is the font size in the Option's bar using Text Tool.
I don't mean the Text Tool, I mean the size of the font used for the user interface itself - e.g. the menus (File, Edit, Image, Layer, etc.). In Edit>Preferences>Interface, there's a dropdown in the Text section called 'UI Font Size' which has 4 options. Changing this selection does nothing to the menus font - it stays really small regardless.
Perhaps 'UI Font Size' isn't supposed to change the size of the menu font - but in that case why is CC so much bigger than CC 2014. Here's a screenshot for comparison - the real thing is a lot smaller than it looks here and I can't read the menus in CC 2014 without a huge effort.
http://www.luminous-landscape.com/forum/index.php?action=dlattach;topic=90916.0;attach=104788;image
-
I don't mean the Text Tool, I mean the size of the font used for the user interface itself - e.g. the menus (File, Edit, Image, Layer, etc.). In Edit>Preferences>Interface, there's a dropdown in the Text section called 'UI Font Size' which has 4 options. Changing this selection does nothing to the menus font - it stays really small regardless.
On this end, Mac OS, none of the settings alters that UI size. I'm not sure it's supposed to. It does change the UI on the Options Bar for type.
The UI itself DID change between CC and CC2014. That's what I think you're noticing.
-
....The UI itself DID change between CC and CC2014. That's what I think you're noticing.
Yes, I think you're right. Why they had to change it is beyond me.
CC 2014 is useless as far as I'm concerned - I just can't read the menus or the panels.
Others are having the same problem. Someone here suggests using a lower monitor resolution but that's just crazy - https://forums.adobe.com/thread/1373107.
-
I've been using PSCC and LR5 on my subscription with no problem. I upgraded to the latest stuff in PSCC and also LR5.5, running with no problems. Today I downloaded and installed PS CC2014. After opening it I got a message to sign in and then received a message saying PSCC2014 was registered to me and I could enjoy it, or something like that. I was able to plug my plugins (NIK/Google, Focus Magic and Topaz) into the PlugIns folder, and used my filters OK. Two problems, however:
1) I set the prefs for Large Text, as have several above me in this thread, and ran into the same problem after closing and re-opening PS CC2014; the text is much smaller and on my NEC3090, I can't read it from where I sit. That was not so with plain vanilla PS CC.
2) Also, on reopening PS CC2014 it said I was using the trial version. I redid the registration and sign-in, and it again told me it was OK and to enjoy PS CC2014. However, on closing and reopening again, the same process was required. It feels like GroundHog Day. Any thoughts? (My subscription is paid up--it is deducted automatically.)
-
2) Also, on reopening PS CC2014 it said I was using the trial version. I redid the registration and sign-in, and it again told me it was OK and to enjoy PS CC2014. However, on closing and reopening again, the same process was required. It feels like GroundHog Day. Any thoughts? (My subscription is paid up--it is deducted automatically.)
I've had this problem before. I'm on Win 7. I fixed it by logging out of the CC helper app, quitting all CC apps (including the hidden ones like AdobeARM.exe), navigating to %LocalAppData%>Adobe> and renaming 'OOBE' to 'OOBE old'. You can find where %LocalAppData% by entering it in the search box that you get when you click on the Pearl.
Then I started the CC helper, signed in, and was off to the races.
If you're at all confused by any of the above, you might want Adobe support to talk you through it.
Jim
-
If you're at all confused by any of the above, you might want Adobe support to talk you through it.
Jim
Thanks, Jim. I went onto the Adobe website and had a "chat" with a tech, who had me sign out on the Adobe App manager and then sign in again. When I reopened PS CC 2014, everything worked the way it was supposed to.
-
1) ....the text is much smaller and on my NEC3090, I can't read it from where I sit.
Did you ask the online tech about this when you spoke to him?
-
Thanks, Jim. I went onto the Adobe website and had a "chat" with a tech, who had me sign out on the Adobe App manager and then sign in again. When I reopened PS CC 2014, everything worked the way it was supposed to.
Good for you. Now I'm having a problem with Ps CC 2014. About one-third of the time, when I quit it, it appears to quit, but the process Photoshop.exe continues to run. That means I can't start Ps again until I open the Windows Task Mangler and kill the process. Works that way whether I start Ps or Lr does...
Jim
-
I could see a big reduction in support issues by having everyone on the same revision of software. The CC model basically guarantees this by continually upgrading each CC out there to the latest greatest. With perpetual models, there were many different releases of PS active at once, providing much more stress on support.
I run a product that has many different versions active and trying to provide support for all these different versions taxes out our customer support group.
I have never seen a product with so many installation and operational problems as PS CC. This is compounded by the fact the Adobe Support is often unable to diagnose and fix those problems. Software for masochists! High time to acknowledge the whole CC fiasco and save the day with a Classic PS7.
-
Did you ask the online tech about this when you spoke to him?
(concerning the menu font size)
No. The chat was in text rather than by phone, and I was just so happy to get the installation/registration problem cleared up that I neglected to ask about the other problem.