Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Jeff Schewe
LEGEND
Jeff Schewe
LEGEND
Activity
‎Apr 11, 2012
02:59 PM
msp-iggy wrote: others on other forums -- tell of having to 'select' camera from lists... ACR is reading the camera info from the image metadata and prefiltering the DNG Profile list for only those profiles relevant to your camera.
... View more
‎Apr 02, 2012
04:28 PM
Rob Cole wrote: ...and you don't use the other features of Lr4, then by all means, wait and hope for Lr5... Actually, the odds of a new PV 20xx are actually much greator than Fill Light returning. Not saying there will be a new PV in LR5, but the odds of Fill Light returning to be mixed in and blended with PV2012 are nil. The whole purpose of the Process Versions are to maintain user's ability to keep their images in previous versions. To take advantage of the image processing progress (and PV 2012 is progress) Adobe had to draw a line in the sand, which resulted in creating an all new set of Basic panel controls. Some people have kicked and screamed initially at the changes, only to find that for the vast majority of images, PV2012 is a bif win. For those images where the old Fill Light haloing and artifacts actually "helped" images, you still have the option of using PV2010. That's why the PV concept was created...
... View more
‎Apr 01, 2012
06:20 PM
christianbobak wrote: Also, what is "PV2010" and "PV2012." I don't know what those are. PV2010 is the control set from LR3, PV2012 is the updated and imporived control set. If you really don't want to get the benefit of PV 2012, you can keep using PV2010. Course, it's your loss as the new controls are much improved (if you spend the time to learn them).
... View more
‎Mar 25, 2012
03:06 PM
Cornelia-I wrote: ....schadenfreude about their fate at the hand of an insidious bug, which is entirely Adobe's inexcusable fault. Had to look that one up...to be honest, I take no joy because of the upgrade bug with LR3 > LR4 catalog upgrades with regards to the point curve edits being "lost". Perhaps I should not have used the word "delicious" to describe the irony–but it is indeed ironic. And I agree that it's an "insidious bug"...and Adobe has worked hard to determine how it happened and how to fix it and are distressed that it happened in the first place. But regarding the philosophy of zeroing out the image and making an image look worse before you end up making it better is, I think wrong headed. It complicates the process and in the case of a "linear curve" puts too much emphasis on the point curve editor and not enough emphasis on properly using the Basic tone mapping controls. And now with PV 2012, this approach acts to diminish the importance of the new image adaptive adjustments. I think starting with an image that has been normalized so it's appearance is not intentionally bad is a better approach. It allows a user to better evaluate what adjustments the image needs rather than starting from some arbitrary artificially poorer starting point. PV 2012 is the result of a lot of research and engineering…seems a shame to ignore that.
... View more
‎Mar 25, 2012
01:12 PM
Cornelia-I wrote: Is it necessary to put a demeaning label to Michael Frye? Minority approach it may be, but it receives some attention among Craft&Vision. Hey, Michael may be a real nice guy...he's a pretty good photographer, but I'm not sure how skilled he is at raw processing...can't really tell since he didn't actually finish the images. Did you actually watch the linked video? I did...his first image where he talked about reducing the Contrast to 0 and putting the curve to linear just ended with no additional image adjustments...I didn't see the point of using that image if he wasn't going to finish the editing on the image to make his case. The second image he reduced Brightness to zero and and then set the curves to essentially redo what he undid with Brightness and Contrast. Again, I didn't see that image as arriving at an optimal result that was based on starting at zero and ending up with an improved result. I didn't see that video as a compelling case for starting at "zeroed" settings...and zeroing the settings before readjusting everything is a minority position. Now with the image adaptive adjustments in PV 2012 Basic, I think trying to do all tone mapping using the point curve is wrong...it defeats the purpose of the image adaptive adjustments. But hey, if somebody want to go down that hole, it's still possible...just not optmal.
... View more
‎Mar 24, 2012
10:23 PM
Mark Alan Thomas wrote: Adobe should just provide a flat preset and/or profile so this stops being an issue. Sheesh. Why? The OP has drunk the Cool-Aid of a little known "instructor" who advocated a rather minority approach; the "Curves First" approach which with PV 2012 is pretty much out the window. As it stands, you can pretty much do whatever you want to do with PV 2012...you just have to learn how to use the controls. It's all about tone mapping...what you start with really doesn't have an impact on what you end up with. With the new image adaptive controls in PV 2012, doing the tone mapping with a point curve edit is, well, ignoring the considerable effort the engineers went to to improve PV 2012. If you want to go down that rabbit hole, there's a way…with a bit of effort. If you want to take advantage of the PV 2012 image adaptive adjustments, no, you'll need to figure out a way to regress your approach to some sort of "linear" or "neutral" starting point. To be honest, I could care less about how the image starts out, what I care about is how the images ends up. Also note that this OP hasn't, it seems actually updated to LR4...he's waiting till LR4 is usable for him. Whenever that might happen... And yes, there was a posted issue regarding upgrading a LR3 catalog that extensively used the LR3 point curve editor... (does anybody else see the delicious irony here :~) With regards to actually changing the way LR4's curves editor behaves, sorry, that ship has sailed...it ain't gonna change. There was a better potential for changing with the beta, but now that it's shipping, it's a foregone conclusion. So the OP is only trying to cause agitation because the functionality ani't gonna change and the OP knows it. These are not the droids you where looking for...
... View more
‎Mar 24, 2012
07:48 PM
TK2142 wrote: I'll try to edit my camera profiles with the DNG profile editor once LR4 has developed to a point when it becomes usable. Hopefully, this will work as desired. However, I still think that no one should be required to jump through such hoops only to get a neutral develop setting. Setting sliders to "0", where "0" means zero, should be all that is required. We've already covered this at length in the now gone LR4 beta forum...the old "neutral" wasn't really neutral and the old "linear" wasn't really linear...there are always baseline adjustments to a raw file. A truely linear (meaning zero tone mapping) isn't really useful since it's so dark. If you want a replication of PV 2010's linear curve, you can roll your own using the DNG Profile Editor, yes, that works. So, it'll be interesting to hear what Michael has to say about LR4 and PV 2012. You be sure to ping us when he redoes his video, huh? :~)
... View more
‎Mar 17, 2012
07:52 PM
Blind Monk wrote: I just completed an intense seesion of keywording, metadata entry, and cataloging of MOV files in LR4. This is an entirely different issue and would be better served by it's own thread...better not to contaminate a thread with OT posts.
... View more
‎Mar 13, 2012
09:51 PM
So, based on your screen shots, I would expect the Develop module to be slow showing images zoomed in since the Develop previews are ripped not from the LR previews but directly from the raw file. Again it would be useful to know whether or not you've applied and noise reduction. Just understand the Library and Loupe views are using the previews rendered by LR when you import. When you go to Develop, LR must (by nature) re-render the whole raw file to present a color accurate rendering which will include any noise reduction you've applied. It's not at all surprising that moving image by image in Develop in the film strip is slow unless you've visited that image before. Again, all of these reports of "slowness" are separate and distinct. You may not realize how LR works, but there is a standard practice that would be useful to follow. Wait till LR is done rendering standard previews, then use Loupe view to view the images, if you want 1:1 (100% previews) that's gonna take time to generate. No free lunch...getting pixel level info takes time.
... View more
‎Mar 13, 2012
09:40 PM
mizzified wrote: in develope mode... as i start to edit an image (dual monitors on) the more i edit the more it lags to the point on complete 5 second frustration.... sliders wait seconds to move then jump.... everything just starts to lag dramatically to the point of total frustration. Of course unselecting details section helps.... as does turning off the dual monitor view.... slightly, but, i'm really hoping this isn't they way I'm expected to use the software. There are reports that something about dual display is really, really slow....it would be useful to know if this is a facot. Can you go to single display and do the same steps and see if you are getting the same response?
... View more
‎Mar 13, 2012
09:12 PM
stationarymotionOKC wrote: Upon launching LR, sometimes it won't ever show that there are images across 9 hard drives in the catalog. All of the date folders are greyed out. If I close LR4 and re-open it, generally within 3-6 minutes, it will show the image counts in each folder. When in Develop mode, I have the same complaint as so many others, you move the clarity slider from 0 to 18 and it's a 30-60 second turnaround. When clicking on a preset I have created, sometimes you don't ever get the image updated with the new settings. When you imported the 9 drives of images...did you actually try to use the previews or did you simply upgrade a LR3 catalog? Big difference...when you import images either from a CF car or a previous catalog, LR has to "know the images" meaning it needs to have loaded and previewed all the image you may look at. Initially after an import, particularly before the previews are done rendering, it takes a while for LR to absorb the image data and organize the previews. That's why sometimes it shows a grayed out drive/folder name and sometimes shows the three dots next to an image preview and sometimes shows the preview as a grey square...that's normal for new use of an import or catalog. This tends to go away over time (once LR works in the background to fully enter in the database records and makes previews). This has nothing to do with potential slowdowns when in Develop. Unless you explicitly tell LR to make previews, it doesn't do it as a foreground function, it does it as a background operation. Which means anything you may do in the foreground will impact (negatively) the background operations. With regards to the Develop slowdown (and entirely different animal) again I would ask whether or not noise reduction has been applied/turned on. That is a cpu hog when dealing with any images whose noise reduction is other than zero. For the engineers to understand what's happening, the reports of slowdowns need to be less emotional (ranting) and more informational. That's the only way to try to isolate what's going on for some but not impacting others.
... View more
‎Mar 13, 2012
08:42 PM
nph2go wrote: i see the incredibly slow response in LIBRARY module, all i am doing is - working in a folder with ~200 images, using the filmstrip view and scrolling between images using the arrow key as i scored the images (1-5). Are these images that have already had previews made? Are you looking at the images in Loupe View? (as apposed to the thumbnails inside of Library) Once you've got the images imported, have you given LR enough time to render the previews? I wouldn't expect major slow downs when viewing Fit Image size in Loupe unless you haven't gotten the standard previews rendered...if you are viewing at 1:1 and you haven't made 1:1 previews, I would expect that to also be slow'ish. This is an entirely different animal than having slow response time to adjustments made in Develop. That's why it's super critical to know exactly where the slow downs are and what people are doing when they see a slow response. I would expect moving between Fit Image zoom views to be pretty fast (no lag) after you've made the standard previews after an import. If you are importing and immediately trying to Loupe the images, yes I would expect slow downs.
... View more
‎Mar 13, 2012
08:21 PM
1 Upvote
stationarymotionOKC wrote: Something has to give somewhere, using the full upgrade to LR4 and working with 5DmII & 7D images and it's unuseably slow. Reimporting images is too much of a task also having a current library of over 300k images. I am going to need an energy drink for the night ahead of me. Sorry you are having problems...a couple of things to try assuming your speed hit is in Develop (it's useful to spell out EXACTLY where LR is being slow). If you are using noise reduction in PV 2012, try turning off the apply switch in the detail panel. New in LR 4 is the attempt to try to render the noise reduction at any screen view. This take cpu clicks...if you turn off the noise reduction while doing other work, it'll speed up the responsiveness of other adjustments. Other things that are known to tend to slow things down are lens correction and tons of local correction. Again it would be far more useful to know EXACTLY where your slow downs are coming from...I'll also say that due to the adaptive image nature of PV 2012, a lot more cpu cycles are being used. Not for nothing, but if you are running a lot of other apps in the background that are stealing cpu cycles, that will also add to the speed hit. I have issues when running LR and photoshop at the same time but LR by itself seems to be fine...YMMV. You all really need to be explicit in your reports of slowdowns and what your OS & processors are, ram and other things running.
... View more
‎Mar 09, 2012
12:19 AM
JayS In CT wrote: My initial point was not just the PV2010 to PV2012 discussion, but just one in general about keeping an interface stable to minimize disruption when moving to a new version. But if the underlying algorithms have changed, how do you expect Adobe to deal with that? Ignore the potential improvements or let them lay fallow in the field? If you wish to embrace change, it requires, well, change ya know? Otherwise PV 2010 is still there (if you need it–the odds are it will stay as long as you may need it). The ACR/Lr engineers should be congratulated for keeping that option in place...while still advancing the art.
... View more
‎Mar 08, 2012
09:03 PM
JayS In CT wrote: I'm also not suggesting abandoning change, but I am suggesting that at some point there needs to be a level of certainty going forward, or a straight forward conversion from point A to point B. That's where your expectation are a bit unrealistic...while PV 2003 to 2010 was relatively mild in tonality, the fundamental changes in PV 2012 made the matching of PV 2010 to PV 2012 is impossible. The underlying algorithms are fundamentally different so no exact match can be made. That's the reality...the engineers tried real hard to do a 1:1 mapping of tones but the adjustments are simply too different. So, if you have images whose PV 2010 settings are "optimal" keep them...don't update the conversion. For new images you'll get the PV 2012 as default. Learn how to use the new controls and see whether or not there's substantial improvement (for me, there is, YMMV). But the bottom line is, expect change as processing becomes better. You can't stand in the middle of a river and not epect the river not to run by you...adapt, adopt and move on...use PV 2012 where it's a good thing, don't when you have already committed to a rendering (unless you want to play). As to bringing back the old Fill Light (and its many problems) ain't gonna happen...move on, these are not the droids you were searching for...
... View more
‎Mar 08, 2012
06:44 PM
JayS In CT wrote: I think the bigger issue here and in some of the other improvements is that at some point we need to lock down the basic workflow from version to version in LR. Not gonna happen and I'm sure glad that the engineers continue to advance image quality...PV 2003 to PV 2010 had a major impact. No, it didn't have a huge impact of tone and color (it did have some impact). Now with PV 2012, they have made great strides on the tone mapping capability of the adjustments. Do you really want to not take advantage of tis? Simple, keep using PV 2010 and use your old workflow. There's a reason the engineers have committed to maintaining the rendering people have applied to their images. If you want to take advantage of the new adjustments, you'll simply have to come to terms they work differently...they couldn't keep the old adjustments while updating the fundamental processing. Look, we're at an interesting age in photography where over time, the processing of raw images is improving. In the old days, your negs were fixed. Now with raw we can go back and take advantage of the progress of new processing making our original raws better over time. And yes, with change comes, well, change. I really hope the LR/ACR engineers don't slow down…and I know they still have some tricks up their sleeves, so expect more changes in the future.
... View more
‎Mar 07, 2012
10:20 AM
KateMann wrote: ...at this point I am assuming that the edits that I just performed in Lightroom are now rendered in the photoshop file that I'm looking at, which is still a dng. Am I correct or not? I edit the file in Photoshop and save it as a psd. It pops up in Lightroom. I assume that the psd now has the cumulative work that I have done in both programs. Am I correct still or not? If you've used PV 2012 in LR4 you need to download and install Camera Raw 6.7 RC1 in order to render the settings into Photoshop CS5/5.5. Then yes, you'll be getting the proper rendering from LR4.
... View more
‎Mar 06, 2012
11:29 AM
Just to be clear, you do have internet access on the machine you are using, right? Reverse geotagging uses Google Maps engine to look up the locations based on the GPS coordinates... Otherwise, not sure why it's not working for some people. Works here (Mac 10.7.3/10.6.8)
... View more
‎Feb 26, 2012
05:11 PM
Purge the cache for the folder involved...in Bridge navigate to the folder and from Tools, Cache, select Purge for that folder...
... View more
‎Feb 18, 2012
08:41 PM
1 Upvote
Papa Ben wrote: But I've had too much experience with databases to trust them with all that hard work. That's not even a remote possibility. Which is why you can set your catalog preferences to verify and optimize and backup each time you quit Lightroom. There's nothing fundamentally wrong with using a database to store your image edits...as long as you have them all backed up–which is easy to do with LR. Under the Lightroom menu, select Catalog Preferences...and in the General select the option that makes you feel better. I have it set to daily but if I haven't done a lot of work when I quit, I dismiss the back up via ad dialog. You really need to get your head around the concept of "parametric" image editing where you don't edit the original pixels but you edit the settings parametrically and store those setting in a database. You edit parameters of the image not the image itself–far more efficient than trying to constantly edit and re-edit your originals...
... View more
‎Jan 11, 2012
08:43 PM
The place you should be posting to is the Lightroom 4 Beta Forum...
... View more
‎Dec 30, 2011
09:43 PM
Thomas Geist wrote: Lastly again Capture One is also a good example for exhaustive brush capabilities. Really, you sure? I find C1's brush to be primitive compared to LR...
... View more
‎Nov 24, 2011
09:27 PM
Bob the Sign Guy wrote: This scheme of forcing loyal, registered users into a monthly subscription pricing thing is exactly the type of thing only a greedy, bean-counting "suit" could propose. The whole idea is generating a greater amount of positive cash flow for Adobe at the much greater expensive of registered users. It would be useful if you understood the Adobe Creative Cloud option...it's an additional option, not a forced initiative. You can choose to keep perpetual licensing of suites or point products OR choose a subscription model. There is no indication that anybody will be FORCED to do a subscription only option... The only forced aspect is the 1 version back policy change.
... View more
‎Nov 03, 2011
02:07 PM
We might be able to help...I'll send you an email.
... View more
‎Oct 29, 2011
09:38 PM
yhhdzy wrote: How could I open the temp file? You can't...if you didn't have a restore point or a saved copy, that PSD is toast...you might as well start working on a redo (and make backups as you work).
... View more
‎Oct 27, 2011
05:00 PM
trshaner wrote: But an accurate histogram display using the file's or target destination's color profile would be very helpful (and desireable). This will allow detecting clipping that may result in the exported image. That's an entirely different issue (and discussion)... Also note that even in the case of JPEG/TIFF images, the adjustments are carried out in the ACR/LR processing pipeline which is; linear ProPhoto RGB colors in 16 bit. So again ACR/LR is dealing with linear applied adjustments not adjustments to gamma encoded images.
... View more
‎Oct 27, 2011
01:44 PM
Cristiano_Palazzini wrote: Well, Exposure, Black and Brightness do not really works the same way that the Levels in Photoshop. The impact on the image is different....I am not able to tell you exactly how but, try it yourself. The imact on the image is bound to be different because ACR/LR is designed primarily as a raw processing engine and has to deal with linear encoded raw captures. The Levels command in Photoshop works on gamma encoded images, so it's really and apples/oranges difference. You would be better off consentraiting on developing a better understanding of LR's toolset and not try to force fit an understanding of a tool from Photoshop. What you do in Levels in Photoshop will always be different, not better or worse, just different. Everything you can do in levels (except deal with individual channes) can be done in LR, just done a slightly different way.
... View more
‎Oct 06, 2011
10:15 AM
Greg Tan wrote: I just had the same issue as I changed my camera from 450D to 60D and was told that the plug in(CS 5) did not support. Appreciate any advice how to reinstall / update the plug in ? Note, you've added a message to a thread whose last post Dec 2010... The way to update Camera Raw is to go to the Camera Raw Product Page or to simply Check for Updates in Photoshop CS5. Where to look for the update command differs based on your OS.
... View more
‎Aug 10, 2011
02:42 PM
Keith_Reeder wrote: Not according to Jeff in the post above yours, Noel... Actually I was wrong...I forget that ACR 2.4 in Photoshop CS -CAN- open DNGs created with the current DNG Converter if (and only if) click on the Change Preferences button in Converter and set the Compatibility settings to Camera Raw 2.4 and later. There will be some limitations due to changes in the DNG spec but at least a uers can open the DNG in Photoshop CS in ACR 2.4–which BTW is ancient and way behind the times.
... View more
‎Aug 08, 2011
10:33 AM
catsnjammer wrote: i have the original photoshop cs version 8... Sorry, Photoshop CS can not open any recent raws whether or not you convert to DNG. Your version is simply too old. Unfortunately, you're also outside the window of upgrading to CS5 (Adobe will only allow upgrades from 3 versions back).
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices