Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: Robert-Peter Westphal on November 29, 2016, 04:51:09 am
-
Hello,
my lightroom and PS CC / ACR are at the latest version available. When I do a right click in Lr and chose edit in PS CC 2017, PS ist started, but the picture is not opened in PS. Some time later I see the picture in LR with the -edited- extension in the name and tif format ( prior it was raw), but exactly the same as the raw.
Photoshop just shows a black working space - nothing more.
Does anyone else have the same problem, or weird behavior of Lr and PS. Now I really consider to check Affinity photo - I can't stand the many problems with Adobe apps anymore !!!
Br Robert
-
I sympathise, but I don't think such problems are unique to Adobe. Almost every complex program I use goes inexplicably wrong from time to time, and I tend to apply a fairly mindless checklist, in the order of time and inconvenience of each step:
- Restart the program.
- Reboot.
- For Adobe CC: try logging out of CC in the CC app, and logging back in again.
- For Windows, if there's been a recent upgrade of Windows or video driver, try a System Restore (or roll back the driver upgrade). I'm not sure of any Mac equivalents.
- Remove and reinstall the program(s).
- Delete any program preference files. I put that last as it's tedious and frustrating having to reset all preferences.
If these do not work, I start more analytic fault-finding.
I've come to the view "ours not to reason why...", but just run the checklist. Sometimes there's no obvious analytical path that would lead one to a deduction of a particular cause for a program malfunction.
For example, some years ago, on a Dell PC of mine, a faulty video driver caused Epson printer software to blue-screen the machine on a print preview. Huh, how could that happen? And why only when Epson software is running? And why didn't the blue-screen happen in the video driver code? There was no indication in any system dump that the video driver was involved, but replacing the video driver fixed it, and I replicated that by accident later after a complete system rebuild.
-
Not every one has the time, skill and patience to do all this, nor should we need to. These programs are supposed to work properly in all of their supported operating environments. I think the top-level question is whether the O/P's problem is systematic/shared amongst many users, or unique to him (i.e. an Adobe problem or a user problem). The steps you are proposing would deal with purging possibly corrupted factors in his own computing set-up, but would not necessarily address this issue of whether this is an Adobe problem or a user problem. In light of recent experience this always remains a valid first-level of concern until it is dispelled. We would get to know that from the feedback of numerous users of the up-dated combo.
-
Not every one has the time, skill and patience to do all this, nor should we need to. These programs are supposed to work properly in all of their supported operating environments. I think the top-level question is whether the O/P's problem is systematic/shared amongst many users, or unique to him (i.e. an Adobe problem or a user problem). The steps you are proposing would deal with purging possibly corrupted factors in his own computing set-up, but would not necessarily address this issue of whether this is an Adobe problem or a user problem. In light of recent experience this always remains a valid first-level of concern until it is dispelled. We would get to know that from the feedback of numerous users of the up-dated combo.
I agree that one can first try to find out if it's a generic problem, but sometimes it can take a while for a generic problem to surface on forums like this.
My personal preference: a quick Google to see if it's a known problem, then I would normally run down some of that check list I gave, as IMHO it doesn't take much time, effort or expertise.
I entirely agree that programs should just work.
In the real world, as a former software developer I know bug-free programs don't exist, and even extensive testing doesn't eliminate bugs, it merely reduces the number. Software is just too complex. There are various methodologies for creating "fault-free code", which doesn't prevent all bugs but eliminates some classes of bugs. Furthermore, for software developers much of the system is not under their control. Bugs often surface as a result of interactions between one's own code and third-party code (the operating system, libraries or whatever). Such bugs can't be designed out, and the number of combinations to test is near infinite.
The best one can hope is that in good software, bugs are uncommon. For that reason, I tend to assume that problems with one's own computer (including user error) are often a likely cause of mishaps.
-
.............then I would normally run down some of that check list I gave, as IMHO it doesn't take much time, effort or expertise.
..............
Like everything, "it depends" and will vary from user to user. But the rest of what you say - agreed.
-
I can't begin to count the number of times I've experienced the same thing! The only solution for me has been to quit and restart Photoshop. I've also noticed another odd thing: the file will import to PS, but it shows up as a pinhole sized image only a few pixels in size. I hit Command 0 and it enlarges just fine. But still, kinda weird....
Merrill
-
Hello,
my lightroom and PS CC / ACR are at the latest version available. When I do a right click in Lr and chose edit in PS CC 2017, PS ist started, but the picture is not opened in PS. Some time later I see the picture in LR with the -edited- extension in the name and tif format ( prior it was raw), but exactly the same as the raw.
Photoshop just shows a black working space - nothing more.
Does anyone else have the same problem, or weird behavior of Lr and PS. Now I really consider to check Affinity photo - I can't stand the many problems with Adobe apps anymore !!!
Br Robert
Robert is this on Mac or Windows?
I just installed the stuff on my new windows 10 laptop, but it just works. No such isues.
-
Hello,
many thanks to you for all your interestig answers !
Today I switched from PC / Windows 10 to Mac and the problem doesn't exist anymore. It seems to be that this was a Windows problem.
BR Robert