1:1 Previews in Loupe

Facts - MacPro with 16gb ram and latest OS X. When i import images 1:1 previews are generated. My preferences file says to never get rid of 1:1's and I have a 90gb cache file. Using 2 - 24" monitors.
Question:
Grid view in one display and the other shows loupe view. When click on loupe view on second monitor to go to 1:1 it can take 15 seconds (D800 files) for the 1:1 loupe view to show. What is weird is that if I go to an image in grid (second monitor off) and go to the menus and build a 1:1 preview then when I open loupe on the second miniotr and go to 1:1 it is immediate with no waiting.
Would appreciate any thoughts. Thanks
Dan
Added later
Have instructed LR to build 1:1 previews on a group of files. After doing this the 1:1 loupe view is immediate. For those images that were not yet rendered took time to show 1:1 in loupe.
I rerally do not understand how this is happening since 1:1s were rendered at import. Evbidently the import 1:1s have been removed - but why?

THank you vry much that is exactly what I did. Apply bulk resets after import. Will need to change workflow nd wil fix this problem very easily.
AGain thank you
DAn

Similar Messages

Very low resolution previews using loupe in import dialog

Hi,
I had connected Canon 6D via usb to import photos to Lr. However in import dialog using loupe view I get very low resolution previews even if I zoom all way up. It doesn't make any changes in preview resolution, it's like 200x300 pixels at most. I shoot both raw and jpeg and it is the same. Tried full card format. Doesn't help. I can zoom normaly in camera screen. Is it related to the fact that I connected camera directly via usb instead of using card reader? I use latest Lr (5.6) and latest camera firmware (1.1.4).

A raw file usually has two previews embedded in it, a tiny thumbnail preview and a larger zoomable preview. It sounds like LR is only able to retrieve the tiny thumbnail preview even though you are able to zoom in on previews in the camera. Unless the camera, itself, is actually decoding the raw file to produce the zoomable preview and none is in the raw file for LR to see.
You can use the following website to investigate what previews are available in a raw file: http://regex.info/exif.cgi You want to click the Browse button next to Local Image File and navigate to a raw file and click Ok, then click the View Image From File button, then wait for the raw file to be uploaded, after which information about the raw file will be shown including the sizes of the previews and raw image.
As to your question about whether using a card reader might help, try it and see. There could be a system driver getting in the way when the camera, itself, is plugged in.

Problem with Bridge CS6 and zooming to 100%

When I click on a file to zoom to 100% it zooms to 800%. I had the same problem in CS5 and fixed it by deleting the com.adobe.bridge.plist, but this does not work with CS6 and I don't even find the plist. I have a Mac with OS X 10.8.2. I found two plists, com.adobe.CSXS.3 and com.adobe.CSXS2Preferences but it didn't fix the problem deleting them.
I use the zoom function alot and would be very grateful if someone could help me. I do not like the preview workspace with the little 100% window, I prefer zooming to 100% by clicking on the file.

It does not work on a Mac, and they have only one set og +/-, at least my Macbook Pro has.
That is a bit strange, it always has worked for that way on both my Mac Pro and my MacBook.
I can use the scroll wheel on my mouse to enlarge the 100 % preview from loupe in preview window to 200, 400 and 800% but also the + and - keys from both my qwerty key board and the number pad of my extended keyboard for the same result.
Hitting tab for full screen preview I don't even have to click, both aforementioned + and - keys set to 100%, 200, 400 and 800% as well my scroll wheel.
All those methods work on both MacPro and MacBook.

Image file access dates changing in mass (Windows).

In review of the access date properties for image files within a directory being accessed by Bridge within the Favorites area, they are all changing to the current time and date, even if the image is not viewed within Bridge. Why are the access dates of image files being changed even though they are not viewed? This makes it hard to determine whether an image can be archived or deleted based on last access if Bridge is always changing the access date every day. Thanks for any insight you can give on this!

Is there a way to turn off the caching of thumbs or metadata or whatever is causing the Access date to change when searching or reviewing images within a directory using Bridge?
As said, no experience with network environment. But Bridge is a browser and when you want to view things it needs to cache the file and data first.
Having said that, in normal usage (stand alone) it stores and saves this data in the cache folder and once it has done so it will not need to recache until you have made changes to the file. Check Bridge prefs / Cache/ Location to see where the data is stored when you are using this machine.
By default on a stand alone Mac (windows seems to have a similar cache file) it should be in the User Library/ caches/ Adobe/ Bridge CSxx and inhere is a plug in and a folder called Cache, containing several folders.
For Bridge CC there are 4 folders, 256 (the cache files of the thumbs) 1024 (containing HQ preview cache files) data (what it says) and full (containing the 100% previews in cache)
All files that have been fully cached (pointing to a folder the content window should show already good thumbs and the activity bar bottom left in Bridge window should not show any activity, only the number of items showing and items hidden) don't need to recache for that machine again unless you changed something to the file or added metadata.
So once cached there should be no reason for Bridge to 'access' the file again unless access means looking for the file to check if the saved data still applies to the corresponding file on your machine, but then al files should show about the same access time because this is a very fast process on a fast machine.
You can't deselect cache because as said Bridge is a browser showing the content of your files, and to show this it has to generate a thumb and if needed a preview. But as also said, once cached it normally should not start recaching until changes are applied.
You have several ways to set the quality of the cache:
There are two checker board icons top right that give you the option to set for cache. By default it is set to 'Always HQ' to have both good thumbs and a good preview when pointing to a file.
Then you also have to option to generate 100 % previews which provides you with almost instant 100 % previews for loupe in preview panel or full screen view and click. Logically this needs more time and generates a lot of big cache files, all depending on the files you start with and the size of your monitor.
Finally you have the option to use embedded previews only. This is a very quick method but provides low quality thumbs (black border around it) and when clicking on a thumb it first needs to generate a HQ preview that then will take time.
In Bridge prefs advanced there is the option to create also monitor sized previews which should provide you with good quality full screen when using space bar in Bridge to preview in full screen.
This setting also creates a bit larger cache files in the 1024 folder depending on the size of your monitor (logical).
And if you want to apply a search using the find command you also have to include non indexed files to search in all folders, including the not before cached files.
Like first time cache this first indexing takes some extra time but should only need to be done once and then be persistent until you add new files or folders that have not been cached or indexed before.
Until so far the theory for a stand alone. If you have the files stored in a Network and other stations have access and have different cache settings or monitor size settings there might be some other things going on, or someone else has changed the file on their station and then when you select that folder Bridge needs to recache the changes.
Hopefully this makes some sense for you?

ACR6 Sharpening/NR visibility at less than 100% zoom

I am seeing that ACR in CS5 now shows sharpening and noise reduction at less than 100% zoom. Thanks for that Adobe (even though we know it's not "accurate" in the strictest sense).
Now that we have that I am curious about the interpolation method used by ACR for screen display/zoom. Is it the old PS way (the one where 25% and 50% were considered to be "better" at judging sharpness), the newer interpolation that started with PS CS4, or something entirely different?
Also, this is more of a Bridge question but I have seen at least once so far where Bridge showed me sharpening applied in ACR6 in the Bridge preview but it seems a little quirky in that it doesn't always show. Once it showed me NR but not sharpening. Is this perhaps a little buggy still or is there a special combination of the Bridge preview preferences that are needed to make it work? I have tried various combinations of the "monitor-sized previews", "100% previews", etc. and have tried to be diligent about purging the Bridge cache between changes but I can't seem to get it to display sharpening consistently in the normal preview (the loupe and full-screen at 100% or greater DO show sharpening and NR).
Thanks.

Someone needs to get busy and get OpenGL/OpenCL working in Camera Raw to accelerate resampling.
-Noel

When I am finished editing and I click on library from develop, LIghtroom will no longer save my sharpening edit. How do I fix this?

When I am done editing a photo and want to export it, I click on library from
develop, and Lightroom will no longer save the setting I used in detail for sharpening.This
has never been a problem before; How do I fix this?

Are you setting the sharpening at 100% zoom (1:1)? Only when zoomed in is the sharpening applied to the Develop display. Also, LR may not be redrawing the Library preview image file. To force the creation of a new preview, select loupe view (E) and zoom to 1:1 and then out to fit.

Performance tip

Hi,
For what it's worth...
I just discovered something that affects performance massively in the develoment module. Provided you are using a dual screen configuration, if you start to develop an image and forget to switch the second screen to grid mode, LR will constantly update both the image in the development module and the preview in loupe mode.This slows down LR dramatically.
This might happen more often than one could think. Most of the time, we are reviewing our images in grid mode while the second screen is in loupe mode. If we switch to the Develop module in this situation, the second screen remains in loupe mode.

Yes, it's a useful reminder of something users have identified on previous occasions dating back to when the second screen feature was introduced. It's also worth noting that some pretty horrendous performance issues were as a result of Lr updating the second screen. Most of these have been addressed, but some are still lurking around. Sadly, and as Dan Tull mentioned a few days back when asking for feedback on filmstrip performance, the trade off between fixing the problem and breaking something else is too big a risk to take in a dot update.

Preview Panel Appears Brighter than Loupe View In Develop Module

Settings and Hardware:
- Macintosh 15" Power Book G4
- Lightroom Version 2.1
- Attached Apple Cinema Display
- Mac OSX 10.4.11
When viewing Lightroom on the PowerBook monitor all is well and the Preview Pane shows the same brightness value. Yet when the Lightroom interface is brought over to the Cinema Display the Preview pane in the Develop Module is significantly brighter than the main image in the Loupe View.
Any help with getting the value of the Preview Pane to the same brightness value of the Loupe view would be of help. Or if there is a simple explanation as to why this happens, that would also be appreciated.
Cheers,
Jarrod.

Monitors should be calibrated at around 120 cd/m2. This is usualy around 2/3 brightness for Cinema displays and around 4 to 5 clicks back from maximum on a mac book Pro. If you don't, you'll think all your prints are far too dark.
>being a different luminance than the loupe view image on the same monitor
huh? I thought you were comparing between monitors?
Lightroom might not realize that you moved the entire interface to a different monitor and use the wrong profile or it forgets to use the different profile for the preview. This is very common even in managed apps. Lightroom does have a nice dual monitor interface now that uses the correct profiles for both monitors, but I don't think it likes the main window being dragged over.

Using the loupe causes preview to change

I pull up a raw in bridge (same thing happens in the preview slideshow btw) and all is good.. but if I use the loupe to magnify once I close the magnify loupe the image totally changes. I'm guessing it's some default but I need help learning how to stop it from happening. I've checked my default for the raw images and it is NOT what I get after closing the zoom.
Does anyone know what I am talking about?

Laryl,
If you really want a 100% or "1:1" sized preview of your camera's rendition of the RAW data instead of Camera Raw's rendition, then shoot in RAW+JPEG mode and put the loupe on the JPEGs.
It's impossible to see the embedded preview in the loupe because the loop shows a 100% view, and the embedded JPEG previews are not full-size images. I suppose we could disable the loupe if you are viewing an embedded preview, but I'm not sure that would really be helpful.
The reason that the preview is updated to the Camera Raw render after you use the loupe, even if you have the "Prefer Embedded" turned on is that once we have to generate the 100% preview to show it in the loop, we thought it was worse to have the appearance of the image in the loupe and preview mismatched.
For example, imagine you have a file with ACR settings which convert it to grayscale, but you are browsing the file in Bridge with Prefer Embedded turned on. When the previews are initially cached you see the embedded, color preview. Then you bring up the loupe. Now, since there is no 100% embedded preview available, we have to get a high-quality preview at 100% from camera raw--which is grayscale. It looks pretty stupid (at least in my opinion) to have a loupe with grayscale pixels over a color preview, so Bridge replaces the embedded preview in the cache with a high quality (grayscale in this case) preview. Now the loupe and preview match. When you are done with the loupe, you could purge cache for the item if you really want the embedded preview to show up again in Bridge.
The primary goal of Bridge's previews and thumbnails is to literally pre-view what the file looks like when you open it in Photoshop or Camera Raw. Since the Camera Raw dialog is not going to show you the embedded JPEG, by default Bridge doesn't either. The option to show embedded previews is primarily there to speed the editing process. You gain preview-caching speed at the expense of fidelity between the Bridge preview and Camera Raw.
The ACR defaults only change if you change them, so you are in control of what is going on shoot to shoot. If you want to "bake" the current default into the settings for a RAW file so the appearance doesn't change when you modify the defaults again do the following...
1. Open the files in the Camera Raw dialog.
2. Click the Select All button in the filmstrip.
3. Select "Export Settings to XMP" from the fly-out menu by the settings sliders.

LR4 The wrong file information in the preview loupe

I have not seen this mentioned in the forums but I keep getting a bug where the file information displayed in the preview window gets 'stuck'. The information sometimes hangs with that of a previous image. Ie it doesn't relate to the current image but a previous one I have viewed.
Any one else found this? It's a bit of an anoying bug!

Faces has identified the wrong person.
Actually iPhoto does not identify people - iPhoto suggests and you confirm or reject so you confirmed incorrectly (which happens to all of us)
How do I re-assign to the correct person?
double click on the photo to open it and click on "name" and type the correct name for the person
Mary and Jane are in a group picture and have been identified by iPhoto, not me.
In Mary's Faces album, Jane's picture is the thumbnail. In a way, the group picture is correct. I would rather have all of Mary's thumbnails show Mary.
The choice offered by iPhoto is accept or reject. Going into Edit for the pictures does not give the option to identify faces.
If you reject the person will remain un-named- and in the confirm names mode (starting with version 8.0.2) if you right click (control click) on the photo you can accept, reject or name
I am reluctant to reject because the group picture may not show up again.
You can always make a smart album with name is unnamed and find all photos with unnamed people (started in version 8.0.2)
LN

Full-screen (spacebar) preview quality testing

[For background story, please read http://forums.adobe.com/thread/1056763 but be warned, it's very l-o-n-g!]
In brief: some people have noted that Bridge full-screen (spacebar) previews (FSPs) don't accurately reflect the sharpness of a photograph. Sometimes this can be explained by individual configuration problems, but it's clear that this is a common issue amongst people using Bridge to assess/score photograph sharpness, without having to build/examine 100% previews for every image.
[It's worth noting that one common reason why FSPs aren't very sharp is because the Bridge advanced preference "Generate Monitor-Size Previews" hasn't been ticked, as this produces a higher resolution image cache. Another cause of very fuzzy previews is random and unexplained, but can usually be solved by restarting Bridge and/or clearing the cache for the selection.]
This discussion concerns the lack of sharpness seen only in FSPs. It can be described as "a subtle but significant loss of detail and sharpness, similar to a slightly out of focus photograph"; imagine a photo with a little bit of blur filter, or a Photoshop PSD at a non-standard zoom setting. This "softening" of the image is caused by Bridge asking the graphics processor to resize the image cache to fit the display. If you select the Bridge advanced preference "Use Software Rendering", you can improve a poor FSP slightly, at the expense of speed, by bypassing the graphics processor.
The test
Visit this web page and download the last image ("2362x3543 pixel, 4.5 Mb") to your computer.
Browse to this image in Bridge, and view it full-screen by pressing Spacebar. Take a screen capture, and save it as a TIFF or PSD.
Adjust your slideshow settings (Ctrl/Cmd-Shift-L), picking "Scaled to Fill", then click on "Play". Save the screen capture, as above.
You now have two screen captures: one FSP, and one cache JPEG reference shot. Examine them side by side at 100%, or layer them in Photoshop and use the hide layer button to flick between images. Pay particular attention to the two left-hand photos, the sharpness check text, and the converging lines.
Make a note of your computer's operating system, graphics processor and driver version, as well as your largest display's pixel dimensions.
Post this information below, together with high quality (10) JPEGs of both screen captures, labelled FSP and REF, and any observations, so we can all see.

OK, it usually takes me a while to let the penny drop, especially when it comes to maths...
I also am busy with the transition of my new Mac pro but with al this here are my results. I include several screenshots but due to upload limit of 2 MB per image in here I downsized the original screenshots a lot, but hopefully it will be clear.
For full screen screenshots I have the asked FSP and REF but also the 100% preview in Bridge with space bar and click. Don't know what your file size is but using EOS 1Dx with 18 MP CR2 files (converted to DNG) it does take me about 1,5 - 2 seconds for both loupe and FSP to build a 100 % preview, and I seem to recall this was not very different behavior on my previous (6 year old) Mac Pro.
You are right (of course... :-) ) regarding the difference between FSP and REF, when studying closely there is a significant detail difference between the FSP and the REF. However, only the 100 % preview matches the original jpeg. The FSP file is on closer look not so good with details but the REF file is only slightly better, both are not correct and therefor the 100 % is still needed.
Here is the FSP screenshot:
and here the REF screenshot:
also the 100 % preview in full screen screenshot:
and finally a composed file with details from original, 100 % REF and FSP:
As said before, at first sight I can't spot significant difference between all options and the full screen (as the preview panel HQ preview) let's me spot the vast majority of unsharpness issues, hence my multiple rounds of sorting and incases of doubt the 100 % option.
So while your theory is correct I'm afraid I (still) doubt the usefulness of this all. If neither the FSP and the REF (although the latter does show a bit better result) can match the results of the original but the 100 % does it well I don't see an easy solution for improvement.
I agree with the quality from the screenshots Curt provided, but Curt also uses the embedded thumbnail instead of HQ preview option. Depending on his needs and hard ware availability it would be nice to see new results with the HQ and monitor sized previews options enabled.
regards
Omke

Adobe Bridge CS6 keeps zooming into previews

Hi guys. I'm using Adobe Bridge CS6 to browse some media content, but each time I preview a video, it plays zoomed in about 20% or so. It does this for all video clips, all sizes, no matter how I try to reconfigure the layout, use OUTPUT mode, FILMSTRIP mode, ESSENTIALS etc, it still shows zoomed in.
I'm running Win7 64bit with a GTX570 with updated drivers.
Please help. Thanks.

You mean 200 % instead of 20 %??
Use the loupe on an image and check what the default zoom percentage is, it should show 100 % and if it is at 200 % you have to use your mouse scroll wheel to set it back to 100 % (it runs from 100 % to 200, 400 and 800 %).
If your video files exceed the preview window you have to enlarge this window or if the behavior keeps this way consider to reset the preferences of Bridge holding down control key while restarting Bridge and choose reset prefs.

With the following warning "ligheroom encountered an error when reading form its preview cache and n

with the following warning "ligheroom encountered an error when reading form its preview cache and needs to quit. lightroom will attempt to fix this problem the next time it lanuchse "
ligheroom progrem 5.4 64-bit is stopped
i can't use the Lightroom Progrem
and want to solve the problem As soon as possible

Delete preview cache - that should solve the problem.
It's the .lrdata folder in with your catalog, named something like "My Catalog Previews.lrdata".
Delete entire .lrdata folder, making sure you get the one in the same folder as the catalog you're opening. Do not delete anything else, and if you have something like "My Catalog Smart Previews.lrdata" - that's not it.
http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-41.html
When Lr comes up, consider initiating whole-catalog building of standard previews (Library -> Previews menu), lest you be "forever" greeted by temporarily gray thumbnails and "loupe loading" indicator in the future..

How can I select the photo to display in Loupe / edit in Develop?

Hi, I upgraded from Lightroom 3 to Lightroom 5.
(I'm now running Lightroom 5.4 on Windows 7 64bit)
I'm confused about the way LR handles photo selection.
In LR 3: No matter where I selected a photo - i.e. clicked on it (Loupe, Grid, Filmstrip), LR recognized this as the "current" photo and when I switched modes (Library <-> Develop), I was always working with this one photo.
This behavior seems to be gone in Lightroom 5.
* selecting a photo (left click) in Filmstrip only changes the selected photo when in Develop, nothing happens in Library (except that the preview changes in the Navigator)
* double clicking on a photo in Filmstrip has no effect either
* in Library mode the only way to select a photo to display in Loupe seems to be to click on it in the Grid view (plus the arrow keys to navigate)
* this means there are 2 independent "currently selected" photos
Why can't I use the Filmstrip to select the currently displayed photo e.g. in Loupe view?
Can this behavior be changed?
Having these 2 different independent "selections" is confusing. Is this a bug or an intended change of behavior?
I'm pretty sure this worked back in Lightroom 3.

OK, today I ran LR5 again and now everything is back to normal :-)
Looks like some weird glitch.
I'll write again if it comes back and/or I'll be able to reproduce it.

Grey thumbnail, grey loupe view-- no photograph displayed in library mode

When I import a new batch of photographs my library mode, both in grid and loupe view will not show my new photographs. And not that it just takes a bit of time to load-- the picture will not show, only gray. This has only happened in the last month or so. Previously everything worked well.
To get my pictures showing I have to go to develop mode and view them. The loading is taking considerably longer than it used to as well. I've been into my preference pane and can't see what to do. As per a tutorial I upped my "Camera Raw Cache Settings" to 50 GB. The problem hasn't coincided with this change however. I don't know what is going on but I am frustrated to have all photos load but not show up in Grid or Loupe mode.
Any ideas? I have over 7,000 photos in library. I've validated and checked library and it comes back okay.
Thanks for your help.
My computer is a newer 27" imac so I should have plenty of juice to run the program. Hard drive space isn't an issue as I have a 1TB.

Sounds like a corrupted preview cache. Let's test that theory. Close LR. Find your catalog on your hard drive, and rename the Previews.lrdata or move it to another location - you can delete it later when we know the new one's ok. Now restart LR, go to Grid view, select all and go to Library menu > Previews > Render Standard Previews. Hopefully that'll bring back your previews and if everything looks correct, you can then delete the previous one.

1:1 Previews in Loupe

Similar Messages

Maybe you are looking for