Problem still there in version 5.3. ... View more

The simple solution is to uninstall the Extension Manager, download the full package (Adobe CS6 Extension Manager version 6.0.8) and to re-install. ... View more

Same problem here. Downloading the update separately and installing also failed. I don't think that I will reinstall the full PS CS6 package, as suggested in the mentioned article, just to fix this. The updater itself is buggy, IMHO. ... View more

Phillip Jones wrote: Back having to sign everytime you shut off browser. Same here. Checking the "Remember me" option has no effect (Windows 7, Firefox) Things are slowly getting worse... ... View more

Hi, I could eventually update to 13.0.1.3 after re-applying the 13.0.1.2 update package instead of re-installing the original version. Regards. ... View more

Samoreen wrote: Same problem here : Adobe Photoshop 13.0.1.3 Installation failed. Error Code: U44M1P7 Re-installing didn't help. By the way, the Adobe FTP server doesn't seem to have the latest CS6 version. So I'm stuck. ... View more

Hi, Same problem here : Adobe Photoshop 13.0.1.3 Installation failed. Error Code: U44M1P7 ... View more

Samoreen wrote: I have direct access. Well, sometimes . I spoke a little bit too fast. Now, it's just random. Sometimes I open the browser, click on the forum link and have direct access, sometimes I have to click again on the sign in button. ... View more

Problem solved for me. Today, I had to sign in again, and I checked the "keep me logged in" option. Now when I return to the forum, even after exiting the browser, I have direct access. ... View more

dj_paige wrote: Ranielse is correct You need PHotoshop or Photoshop Elements Or Corel Paintshop Pro X5/X6 or onOne Perfect Suite 7.5 / 8. ... View more

Noel, Noel Carboni wrote: TDD...  LOL.  Sorry, call me old school, but just because undisciplined, haphazard development has an acronym and a Wikipedia page doesn't make it good.  I'm not against good testing, and I certainly believe developers should have a say in what gets developed, but there is no substitute for good top-down design. I have been teaching TDD for years, along with object-oriented development. I'm not aware of any developer among my students who had given these technologies a try and who wanted to go back to old procedural development and old testing methods unless the project manager wanted him to do so for non technical reasons. My feeling is that those "bricks" are more like a small pile of "stones" of all different shapes, sizes, and colors, and while you can certainly envision creating a stone wall, without mixing up a BUNCH of mortar the pile of stones begins to lose its integrity. If you have read the above mentioned thread, you have understood that these building bricks are actually a collection of PS plugins and a host application. Plugins have to comply with a common architecture but they don't have to be run in PS as a host. Topaz Labs photoFXLab, as an example, is a host for any PS plugin, those from Topaz and those from any other company. I guess that onOne can easily add this feature in their Perfect Suite. Google/Nik would be well advised to provide such a host anyway. So consistency would be there anyway : there is no reason for plugins to be less consistent with each other in a host than in PS. And I remind you that Photoshop itself is created from a number of packages that were purchased and integrated, which led to the situation we're in now where not everything works quite consistently. This should not be a problem if the design of the hosting software is thought out with integration and testing in mind. I don't want to come off sounding like I'm arguing against progress.  But what I AM doing is trying to bring a bit of realism into the argument that something can replace Photoshop in short order. Make no mistake : I'm sure that "something can replace Photoshop in short order"... for photographers. I'm pretty sure this will happen within one year or two if third-party companies understand the big opportunity that Adobe is offering them and if Adobe don't decide to release a PS Photographer Edition rather quickly. ... View more

Noel, Noel Carboni wrote: Thing is, an application the size of Photoshop cannot be just "written from the ground up" in months, or possibly even in a few years - even if you just wanted to make it a Photoshop workalike. Globally correct statement. But if you look at the product from a photographer's point of view, things are very different. As explained by Nevada Shooter, innovation is here and new ways of doing things are appearing. Look at this thread. This (wrong) move by Adobe just made clear to many photographers that they might no longer need PS within a few years. Almost every brick necessary for building a new and comprehensive approach of photo editing is already available and the missing modules could be made available very quickly. You are right that nobody is able to produce a PS clone. But do we need this? Would it be a good thing? That's the problem with products that have no competitors. We are convinced that we couldn't do without them... until we realize that there are other (possibly better) ways of doing things. Also, they should have considered much earlier re-writing the product using more modern development technology. The product's architecture is old and obviously, they are unable to switch to something more flexible that could support more effective development methods. As an example, it is obvious for any developer that regression testing in PS and LR is not done or is done the wrong way. Otherwise, we wouldn't have to live with these years lasting bugs that will never be fixed. There are development methods (TDD for example) allowing to strongly limit regression. But this implies using an adapted software design and modern development tools. Adobe's decision forced many of us to re-consider what we have regarded for years as "the holy truth" about PS. Their mistake. Now people are aware that the "truth might be elsewhere". So their decision is not only a wrong decision about their pricing and licensing policy. It's also a bad estimation of what their product actually was and now is and of what a good part of their customers needs. ... View more

My apologies for the inadequate post. ... View more

MVP? Mylenium wrote: Subscriptions are subscriptions - you pay what you use. When you don't pay, the program stops working. The question was about CS6 standard not about CC. Mylenium wrote: And no, you cannot buy older versions from Adobe. You could try finding one on eBay or wherever, but there's always the risk of being scammed... And yes, we can still purchase from Adobe a perpetual license for PS CS6. At least until mid-june. Please don't add misinformation to an already confusing situation. Especially as an MVP. ... View more

Dragoro21 wrote: How bout you complainers go offer your bosses to work for free. I mean, its the right thing to do, right? How about your boss lowering your salary and preventing you from working for another company? ... View more

Samoreen wrote: So if Ctrl-Z doesn't work when editing an image in Lightroom there are only 2 possibilities : - There's a bug in Lightroom - Some keyboard utility (keyboard remapper) installed by the user is capturing the keystroke and doing something wrong that is fooling LR. By the way, I suggest that everyone having this problem looks at C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.4\Resources\en\TranslatedStrings.txt (if the file exists) in order to check whether the Ctrl-Z key has been re-assigned. Non english speaking users should look at the file corresponding to their language. Normally you should find this line in any TranslatedStrings.txt file (except for the english language - see below) "$$$/Application/Menu/Edit/Undo/Key=Cmd+z" If the file doesn't exist on your system (which will normally be the case for those using the english language because in that case everything is hard-coded), create the file, add the above line, restart LR and see whether this fixes the problem. ... View more

Hi, Just to make things clear : Ctrl-Z is not an overall operating system function. It is an admitted rule that when a user hit Ctrl-Z in an application, the program should undo the last action. Whether the application actually does something when Ctrl-Z (or Alt-Bsp) is hit is a decision of the developer. The only exception is when the application uses some interface element provided by the operating system (e.g. an edit field) and when the Undo feature is built-in. An Undo operation cannot be implemented without having a deep knowledge of the application internals. So only the application developer can code it. There's no idea of a system global Undo function triggered by Ctrl-Z that would work with any application. So if Ctrl-Z doesn't work when editing an image in Lightroom there are only 2 possibilities : - There's a bug in Lightroom - Some keyboard utility (keyboard remapper) installed by the user is capturing the keystroke and doing something wrong that is fooling LR. ... View more

Mollysnoot wrote: ?  I posted my message three days before you posted yours!  M Oooops! Sorry for the mistake. ... View more

Please see the message that I just posted a few minutes ago, just before you posted this one. ... View more

Hi, ymc226 wrote: Thanks Samoreen. I am definitely not going to upgrade to LR4 as I am running Lion as well.  I do have a question which I don't know if you have an answer but would value your opinion. Just installed the complete NIK collection last week and updated then (prior to yesterday's update in reponse to the big LR4 bug). Would updating these most recent versions of the NIK plug ins do any good or harm if I still use LR3 only? Sorry for the late answer but I'm abroad and it was time to sleep a little. There is no problem with installing the latest version of the Nik plugins and using them with LR 3.6. Actually, this is what I'm doing. These updates are here to fix (among other things) a problem that made impossible to update the metadata in the TIFF files generated after invoking the plugins from LR. The bug was first fixed in Color Efex and then they fixed it in the other plugins. ... View more

b_gossweiler wrote: Ever heard of LR 3.4.1? Ooops! I forgot this one. Sorry. ... View more

Brett N wrote: Thank you for the insight Samoreen. I'll post an update once we have more information from our engineers. Thanks. Now I can simply answer "yes" to 7thsojourn . ... View more

7thsojourn wrote: Great explanation. Thanks! Now, the question is: does Adobe know this?  🙂 I posted this in a thread in which an Adobe employee was participating. I also know that they have received at least one bug report from someone who has a tight relationship with the development team. Any skilled developer reading this error message should immediately understand what's going on. As I said above, there is no doubt about what is causing the error. Developers are using special debugging tools that are able to automatically detect such errors during program execution. So the problem is not how quickly this can be fixed : this is a matter of a few hours if not a few minutes. The questions are "when will they decide that it is a problem worth considering quickly?" and "how long will it take until the fix is published?". ... View more

Julie McLeod wrote: @Samoreen Thank you for your detailed and technical explanation.  Much appreciated.  Once the engineers identify the coding problem, I wonder how long it would take to get a fix pushed out? This is the problem with Adobe. Even for bugs that are easily spotted and fixed, it may takes a very long time until the fix is released. They are not used to release "x.0x" versions like Nik Software do, just to fix a specific bug. They never did this for LR. Chances are that we'll have to wait until they release version 4.1. For me, this is a major bug. If I can't safely invoke external programs or plugins, I'll stick with LR 3.6. ... View more

Hi, Quoting what I already explained in another thread: This error message is typical of a "dangling pointer" problem (in developer parlance). The "lower" function which converts a character string to lowercase, receives an argument that is a pointer (memory address) to the character string that should be converted. In that case, the pointer is invalid or null. This kind of bug may or may not cause a crash depending of the value (wrong address) contained in the pointer variable. This is just a matter of memory layout. So the bug affects everybody but in some cases it has no consequences. In other cases, it causes a crash that the system may (Windows) or may not (Mac) notify to the user. Typically, this kind of bug originates in "last moment changes" made to a piece of code that is not  re-tested afterwards (it was not present in the beta version). When you install another program like PS or PSE, you also install some services that were not there before. These modules are loaded when the system starts. So when you re-launch LR4, it is no longer loaded at the same memory address. This may (or may not) change the "dangling pointer" value. The value will always be invalid but in some cases this will do no harm. This kind of behavior is typical with such bugs. Loading another program first may (apparently) fix the problem. Installing another application may have the same effect... or not. This is just random and this is what is observed. The "PSE fix" works for some users and doesn't work for others. I guess you could obtain similar results when installing/uninstalling another application. Don't waste your time with these tests. The problem is a plain old classical pointer bug. The error message is unambiguous. It clearly explains what's happening and where. It should be easy for the developers at Adobe to spot this coding problem quickly. ... View more

Agnus1 wrote: In response to DdeGannes, I can assure you that if it is a Nik Software issue, they will fix it very quickly and are working on it. I highly doubt that it is though since none of my Topaz plug-ins work either now. Besides these plug-ins all worked in the beta version of LR4. Agreed. Given all the information collected since this issue first appeared, it is obvious that the problem is on Adobe's side. Either they changed the programming interface or they introduced the bug just before releasing the official version. ... View more

sarki64 wrote: The interested thing is that changes introduced by the installation of PSE only persist as long as you keep it on your machine. I tried uninstalling PSE and the error in LR is back again. This is consistent with what I explained. Installing PSE changes the way the memory is organized because some additional programs are loaded in memory upon startup. So LR is loaded at another address which may or may not have consequences on the way the bug manifests itself. This is just my opinion as a former developer. Maybe I'm wrong and maybe installing PSE or PS changes something else in the Common Files | Adobe folder (a missing file as you suggested) but I doubt. In that case, the problem would hit every user. ... View more