Bridge CS3 Loupe tool in Lightroom

I would love to have the loupe tool present in Bridge CS3 in Lightroom in addition to the current zoom view. I found the Loupe in Bridge excellent for a quick check on the focus of certain part of the picture.
I also like very much the view type 3 in Bridge CS3 - this is the one with EXIF information + image size + workspace ,... on the side of the image.
I would like to have this view as an option to the grid view in LR.
Regards,
Luc

>You can adjust the percentage with the scroll wheel on your mouse.
Or with the + and - keys. (For those who don't have a scroll wheel, like me.)

Similar Messages

  • Loupe Tool in Lightroom Web Gallery

    I have created image galleries using the templates in LR3 for an artists website. She has asked me if it is possible to be able to zoom into the images to provide close up views. I am thinking a Loupe View tool would achieve this?
    Does anyone know if a loupe tool can be added to a LR web template so when published, users could use this tool to view close up detail of images in the web gallery?
    Any other suggestions greatly appreciated.

    In a HTML based page the fonts shown will always be dependent on the fonts installed on the end users computers. Whilst many LR galleries have the ability to select a font group that the respective end users machine may display by editing the page css style, I don't think the default html gallery that comes installed with LR has this.
    If you want to make the change yourself you will need to recode the exported gallery files yourself. In the index file a line such as
    body,td,th {      font-family: Verdana, Geneva, sans-serif; } should do it

  • Bridge CS3 Loupe Pixelation

    The loupe in Bridge can't focus on a close up at full res. It displays tiny pixels. I have 4GB RAM and thumbnails set @ 1000 MB in Prefs. Funny, I had no problem on a Mac with less RAM. Or is Leopard the problem? Help!

    >You can adjust the percentage with the scroll wheel on your mouse.
    Or with the + and - keys. (For those who don't have a scroll wheel, like me.)

  • Bridge CS3 Workspace Adobe Lightroom Web Gallery Creator

    A while back I was looking around for an easy way to create sharp looking image galleries with minimal work, and I came across a workspace plug in for Bridge Cs3. If I remember correctly, it was labeled Adobe Lightroom Web Gallery something or another. Anyway, I recently formatted my computer and reinstalled everything, but for the life of me I can find no trace of that handy workspace plug in. Does anyone know where I can find it? It had a bunch of customizable flash galleries as well as a customizable html gallery as well. Any help would be appreciated!

    Do you mean AMG( Adobe Media Gallery)? You could download from LAB.
    http://labs.adobe.com/wiki/index.php/Adobe_Media_Gallery

  • Problems with Bridge CS3 crash freeze and burn

    Hi,
    I am running Bridge CS3 version 2.1. 100 on a MacBook Pro 3
    Intel Core Duo
    2.4 GHz, 2GB ram
    I am having some serious Bridge issues. My problems have ranged from it just being very sluggish and slow to Bridge not applying a label to random crashes.
    So far today here are the issues:
    "Operation Cannot be completed, an unknown OS error has occurred"
    "EventHandler:2976"
    Will not apply a label when using the command key or from the tool bar menu
    Not responding when quitting from icon in the dock
    freezes when renaming a file
    unexpectedly quit while cropping an image in PS CS3
    Things I have tried to resolve this:
    shift-alt-command and reset all preferences and purged cache
    changing the thumbnails preferences to only process 50mb or smaller files
    create small thumbnails
    (as a former pc user) I have restarted multiple times...
    Things I have not tried:
    rebuilding OS
    uninstall reinstall
    throwing laptop in bathtub
    The files I am working on range in size from 4 mb up to 400 mb .psd files
    Any ideas?

    I can't use Bridge CS3 anymore. It freezes on my screen and the only way to close it is with task manager. Had problems with it the first time I loaded it...a full version of CS3, no upgrade. Spoke with 2 Adobe technicians who tried to help, but being a believer in Murphy's Laws I decided to bypass their suggestions which I had already tried.
    The best viewer alternatives to Bridge are:
    -Fast Stone Image Viewer is shareware and handles .psd files along with RAW, TIFF, JPG, etc. Go to their site an look for yourself. It was so good I sent them the suggested contribution. Adobe could learn a lot from them.
    -Use Adobe Lightroom as a viewer and to do preliminary editing before launching the file into CS3. Adobe got it right in Lightroom...how come not in bridge CS3?
    -Nikon View NX is good but doesn't show .psd files.
    Nikon's Capture NX is a reasonable alternative to CS3 if you get fed up with Adobe. Or go back to PS Elements!
    Finally, some lecturing Photoshop gurus have called Bridge "JUNK...you get what you pay for." Correct.
    Benefits of JUNK sofware is that you explore alternatives and can be surprised at what's available out there.
    Conclusion: Bridge CS3 is meant to be a "bridge" to many PS products, but for me it's a "bridge to nowhere." Make it simple, guys.

  • Bridge cs3 unresponsive

    Last week my Photoshop CS3 stopped working because "licensing for this product has stopped working". After talking to the guys of technical department that problem seems to be solved. Now I have a new issue: Bridge CS3 is unresponsive. I can't see my pictures through Bridge. The answer of the technical department: they can't help me since "my problem" is not related to Photoshop CS3 and is not an installation issue. They referred me to this forum. So, my question is, how do I get my Bridge CS3 back to work? The photos are still there since I can open them in Lightroom, so what is the problem?
    Thanks for any help,
    Not technical savvy at all....

    So, my question is, how do I get my Bridge CS3 back to work? The photos are
    still there since I can open them in Lightroom, so what is the problem?
    First of all the CS3 version for Bridge is pretty worse to put it mildly,
    you are 2 versions behind and both CS4 and CS5 version of Bridge are far
    better, more stable and faster.
    However if you don't want to upgrade it should be possible to get it back to
    work.
    First try the obvious route using the menu tools, cache, purge cache for
    folder and see if Bridge goes back to work again.
    If not restart Bridge holding down option key and choose reset preferences.
    Try again and maybe also try the purge cache using the tools menu.
    If no luck there is an other method but a little more effort needed for this
    so first try the above options.

  • Adobe Bridge CS3 - Favorites Disappear

    Every time I open Adobe Bridge CS3 I set up my favorites folder just the way I want them; but when I close the program down and reopen it, the favorites menu has been cleared.
    I tried saving my work space; But this was to no avail.
    The work space layout stayed in place but the favorites are still erase when I load the work space.
    Also, if it helps to diagnose the problem, when I try to open the preferences Adobe Bridge CS3 immediately crashes.
    I've tried deleting the cache folder & I've tried repairing Adobe with the install CD with no luck.
    Any help would be greatly appreciated.
    Stephen K.

    Stephen,
    Great when things work again; funny how you can try something and it does not work the first time; then magically it does - the joys of software!
    I often wonder what the preferences file in Bridge does for us, if we can clear it and not notice that we have lost any settings.
    I hardly use Bridge since I moved to Lightroom, except to check that Bridge sees what Lightroom does. But I must say that I like its Metadata panel.
    If neither Bridge nor Lightroom existed, I think that I could survive on Photoshop CS3 alone and manage files without either.

  • Bridge CS3 and Duotone: odd behavior

    Hello all.
    Are there any users of Bridge CS3 that work with duotone images?
    The new version of bridge displays the color mode correctly as Duotone, but now the color profile is still the profile of what it was when the image was in RGB mode (Adobe RGB, ProPhoto, etc).
    In Bridge CS2, the color profile of duotone images was always displayed as sRGB IEC1966-2.1. At least then it was constant across all my images.
    However in both Photoshop CS2 and CS3, duotone images show up as "untagged duotone" Color Profile what gives?
    Any ideas?
    Thanks.
    -Andrew

    Ramón,
    Thank you for your reply. The only times I have purged the cache has been through the Tools menu, as i've read from various people, including you, that the other option is "broken".
    Omke,
    In Grayscale color mode, Bridge shows the color profile that's embedded in the image. That comes from the Gray Working Profile selected in Photoshop's "color settings." The only way i know of to create a duotone is to start with a grayscale image. Even the "conditional mode change" function in File > Automate converts the image to grayscale as an intermediate step.
    Now, on to the original question, open to anybody who works with duotones in Bridge...
    a) Does anybody know why Bridge CS3 is treating the color profile of duotones differently than in CS2.
    b) is there any way to make it consistently show one profile? -- at this point i don't care muchly what profile it's displaying as long as it's the same for all my duotones.

  • Some Nikon D300 NEF files don't appear in Bridge CS3 (Mac)

    Hi all,
    I'm using a Nikon D300 and just upgraded to CS3 on my MAC in no small part because the D300 was not supported by CS2. I am running into a problem though.
    I always shoot in both JPEG and RAW modes. When I open Bridge I always see each JPEG version of a shot.
    However, only about 50% of the time can I see the NEF (RAW) version of the thumbnail. The rest of the time I only see a generic "RAW" thumbnail with no image. This sporadic NEF viewability carries over to the preview pane when I select such a NEF file.
    Furthermore, Camera Raw cannot open the NEF files that are not visible in Bridge. When I try opening them I get a message saying "Could not complete your request because Photoshop does not recognize this file type."
    I have tried purging the Cache (through Tools) as some indicated in other forums threads but this has not helped. I have also downloaded the ACR 4.4 plugin and installed it in the correct library location.
    Has anyone else experienced this (whether on a Nikon or other camera)? Any advice?
    Thanks

    I've finally solved the problem with having only some of my NikonD300 NEF files viewable in Bridge/readable by Photoshop! Jon Michael Riley had said he was having similar problems so I wanted to make sure he and anyone else has the info on what worked for me.
    The issue does not have anything to do with purging the thumbnail cache or installing the latest version of Camera RAW 4.4.1. While they were good suggestions (offered by Adobe's Technical support people also), they do not resolve this particular issue.
    I read that an earlier version of what Jon described as "Nikon's clunky software" had corruption issues when images were first transfered from the camera via Nikon PictureProject Transfer. It looks like the latest incarnation has the same issues. Nikon products can see the transfered images without a problem. HOWEVER, Adobe Bridge/Photoshop cannot rectify the corruption issue caused by transferring photos using Nikon's utility.
    So here's the solution: DO NOT use Nikon PictureProject Transfer! It is a piece of garbage! Instead, make ADOBE PHOTO DOWNLOADER the default tool to transfer images from the camera. To make it default do the following:
    Open Bridge, pull down the Bridge CS3 Preferences. Select the "General" preferences set. On this screen you will see "Behavior". The first clickable box reads "When a camera is connected launch Adobe Photo Downloader". Select this box to render this the default transfer tool.
    If you still have the pictures on your memory cards you can re-transfer them using Adobe Photo Downloader. All your NEF files should now be readable by Bridge/Photoshop. I've told Adobe Tech Support about this problem with Nikon's software. Hopefully they'll be able to check this as an option if others call in with similar problems.
    Unfortunately I have not figured out how to repair the corruption in the files I transfered earlier using Nikon's piece of garbage software. Since I don't have the images on memory cards anymore I can't just re-transfer them. Does anyone have any thoughts on how to do this? Will I ever be able to access my earlier NEF shots?
    Cheers,
    Greg
    Thanks to everyone for trying to help resolve these issues.

  • Bridge CS3 ver 2.1.0.100 most  buggy bridge ever

    With previous versions of bridge for CS3 I had occasional problems. The most vexing was that some Canon xti Camera raw files (CR2) and dng files could not have their file info changed via bridge. When I would right click on these files, the file menu that came up would lack the choice for modifying file information. It was impossible for these few files to use bridge CS3 to get to fields such as document title, author, author title, description, etc.
    If I opened the same exact files in the bridge for CS2, it was possible to modify file info for every one of them. The problem files when later opened in bridge CS3 would show the file info put into them with the CS2 bridge--the one that worked. It was still impossible however in bridge CS3 to modify the file info for these occasional files.
    I made the great mistake of upgrading to bridge CS3 2.1.0.100. Today I took more than 240 photos. It is not possible to modify the file info for any of them with lousy bridge 2.2.0.100.
    The new version also crashes much more often,simply disappearing without any error messages.
    In addition, at least some photos whose file info could be accessed via the older version of bridge CS3, no longer allow such access under the newest bridge version.
    The new bridge version is a massive step backward.
    Open challenge to Adobe--I will be happy to send you 200 plus problem files that only work properly with older versions of bridge. You could use them to fix bridge.
    Gateway computer with latest version of Windows xp,
    OS Name Microsoft Windows XP Professional
    Version 5.1.2600 Service Pack 2 Build 2600
    OS Manufacturer Microsoft Corporation
    System Name GATEWAYNEW
    System Manufacturer GATEWA
    System Model GM5076E
    System Type X86-based PC
    Processor x86 Family 15 Model 6 Stepping 2 GenuineIntel ~3199 Mhz
    Processor x86 Family 15 Model 6 Stepping 2 GenuineIntel ~3199 Mhz
    BIOS Version/Date Intel Corp. NT94510J.15A.0099.2005.1215.1455, 12/15/2005
    SMBIOS Version 2.3
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Locale United States
    Hardware Abstraction Layer Version = "5.1.2600.2765 (xpsp.050928-1517)"
    User Name GATEWAYNEW\Owner
    Time Zone US Mountain Standard Time
    Total Physical Memory 3,072.00 MB
    Available Physical Memory 1.96 GB
    Total Virtual Memory 2.00 GB
    Available Virtual Memory 1.95 GB
    Page File Space 4.84 GB
    Page File C:\pagefile.sys

    I have found CS3 less buggy that I expected.
    I have found "Bridge CS3" outstanding, but no doubt, some will experience problems.
    Experience is great teacher
    But I do keep CS2 on my machine for those times I cannot wait for whatever fix might be necessary.
    Do not worry.
    The problems many are having, whatever that may be, and it is somewhat varied, will most likely be worked out in CS4.
    I contribute many of these problems to be lack of control over the hardware that the software must function on. Windows vs. Mac ideologies rear their heads here. I use Windows and that is definitely my problem.
    Get used to it.
    CS4 whatever = CS3 whatever with most problems fixed.
    CS3 = CS2 with most CS2 problems worked out with some tool palette changes users have been asking for years, along with "some" real graphic ability improvement, along with some abilities that probably > 80% of us will never use. Better camera support in Camera RAW.
    Most all of this depends on how much money you have to devote to Photoshop, its upgrades , and the cost of the demands for appropriate hardware.
    Note:
    I was just using the "spelling checker". On this forum "Photoshop" is an unrecognized word. It wants to spell it:
    "Photo shop"
    or
    "Photos hop"
    Go figure.
    Just my 2 bit opinion which wouldn't buy you a cup of coffee or anything else.

  • Bridge CS3 not displaying .PNG thumbnails

    This behavior started about 2 months ago and I cannot figure what changed or what to do to get rid of the generic .PNG icons and get back to the image thumbnails. It's not isolated to Photoshop generated .PNG's. Any app I have that can save in the .PNG format will appear as a generic icon in Bridge CS3.
    .PNG's that were uploaded to our server prior to around mid-Feruary all have the proper thumbnails. Currently, replacing them or uploading the same file from before February produces the generic icon. Same thing in both in the main view and the Preview window.
    The only thing that has changed on my machine between now and February was an OS bump from  10.6.1 to 10.6.3.
    Every other format displays correct thumbnails. I've tried just about every suggestion dealing with missing thumbnails from the various "no thumbnail" posts in this forum...and still no luck. Does anyone have a suggestion or two...or three, that might help me clear this .PNG problem up? It's driving me bats trying to identify images.

    I've tried just about every suggestion dealing with missing thumbnails from
    the various "no thumbnail" posts in this forum...and still no luck.
    Could you specify on that, meaning also purge cache for selection. Using
    tool menu-cache, use the filter menu to select only PNG files for faster
    approach.
    And you may not like this but using a more then 3 year old app on a new
    (intel based and 64 bit OS system) might also not be the best route. CS5 is
    just out now and rebuild for 64 bit systems like Snow Leopard is.
    Also keep in mind CS6 will be your last option to upgrade according to the
    Adobe upgrade policy, after this you will need a new full license.

  • DNG Files Appearing as Icon not Thumbnail in Bridge CS3

    Hi
    If I save a Camera Raw manipulated image as a COMPRESSED (LOSSLESS) DNG file it appears back in CS3 Bridge as a DNG Icon and not as a thumbnail.
    Is there a reason for this and can I get the saved file to appear as a thumbnail.
    Many thanks

    Bridge 2.x, the one that comes with CS3, is easily the worst piece of software ever released by Adobe or any other major company, in my view.  It should have been fixed for free, but it wasn't.
    Cache management is extremely poor in Bridge CS3.  Purge the Cache for the offending folders through the Tools menu in Bridge.  DO NOT use the global purge command in Bridge preferences.
    Fortunately, Bridge 3.x in CS4 is much, much better.

  • Problem with changing Label in Bridge CS3 and CS6

    Hi there,
    I am having some problem with changing Label in Bridge CS3 and CS6 in windows.
    1. In Bridge CS3 (Windows XP), most of the time with most of the files, there is no problem. But I found that in some files, the Label does not get changed. I usually change Label by right clicking on the picture, then Label and select any Label. When I do so in those files, nothing happens. But when I rename the file by changing or adding just a single character, then it works. And if I again rename to original name, it still works. But without renaming the Label does not change. Again this does not happen with all pictures, but occationally with some. We usually receive pictures from different clients for editing purpose.
    2. In Bridge CS6 (Windows 7), if you create lot of Path using Pen tool in Photoshop for the purpose of removing background, you save the file, close, and change Label in Bridge, again open the file in Photoshop, you see no Path in the Path Pallette. So that means, changing Label works, but it removes the Path from the file. But if there is small amount of path, then no prboblem. But if there is lot of path, like you need to create for a necklace to remove background, then the problem arises.
    I am using Bridge for a purpose where it is very helpful so I really need to use Bridge, and Labeling feature is the most important to me, but after feaguring out this problem, I am really tensed as to whether or not I will find a solution to this. So any help, guidance will really be appreciated.
    Thanks very much in advance for any solution.
    Best regards

    I have re-checked the issue and I found that the problem is with JPG file.
    I wasn't even aware you could save a path to a jpeg file (always use PSD because of wanting to keep the Alpha Channel, jpeg only can contain 1 layer and no alpha channels and/or transparency).
    However I tried it on a file with a simple path and one with a complex path. It seems indeed you have found a bug. The simple path is no problem but the more complex path is indeed disappearing.
    It is not only label but also rate or adding IPTC in the description field. The moment metadata is saved to this jpeg file and reopened the earlier present work path of a more complex path is gone.
    Despite the fact that to my opinion a jpeg is not the most suitable file format for saving a work path this should not happen. If a work path is saved to a jpeg then it should be kept saved after just altering metadata in Bridge.
    It still is the same behavior in Bridge CC because that is what I use. Don't know when it started but it still needs to be repaired
    Here is the link for filing a problem or bug:
    http://feedback.photoshop.com/photoshop_family/

  • Bridge CS3 no longer renders RAW thumbnails

    Running PSE9 on OS 10.8.2 Mountain Lion.  Also running Bridge CS3 2.1.1.9 that I believe came bundled with PSE4 and which I have become fond of using as a tool for importing photos and other steps early in my workflow.  I shoot almost exclusively in RAW and sometimes in RAW/JPEG.  Recently, having made no change that I can remember, Bridge is no longer able to render thumbnails of the RAW files, instead showing just a thumbnail of a white sheet with the corner turned down; JPEG thumbnails render just fine.
    I would be extremely grateful for anyone that can help me get the RAW thumbnails working again.  I suspect some anciliary file outside of the main program package since Adobe is so fond of sprinking useful files all over the place if that rings any bells.
    I have tried to find a standalone Bridge CS3 installer on the web that I might use to re-write whatever is missing but I cannot find it.  It's an unusual request but if anyone would lend theirs to me I would also be grateful.
    Thank you in advance.

    Turns out my sister is more a packrat than me and she still had her original PSE6 disk, which was also bundled with Bridge CS3.  Uninstalled/deleted 9 and Bridge and removed every trace of them and prior versions I could find (e.g Library files) to a flash drive.  Installed 6 along with Bridge and all seems to be back to normal.
    Hopefully everything else still works right and I won't have to try-and-err putting Library files back one-by-one or something.  Once it feels like all is stable I'll be putting in my upgrades to PSE9.
    Thanks for your suggestions.

  • Bridge CS3 will not install

    My Bridge CS3 will not install on my new Intel duo core iMac.  It worked on my earlier iMac, but when PhotoshopCS3 was moved and installed on the new one, Bridge was nowhere to be seen.  I have repaired permisisons, reinstalled PS CS3, and looked for Internet advice.
    I would really like to continue to have the Bridge in the CS3. 
    Am I  going to have to rely on my new Lightroom Developer for its Camera RAW functions and for renaming my files?  I liked the Bridge RAW converter very much.  The old Bridge is still on my machine, but its renaming functions don't suit me at all,  and for some reason it is refusing to open my non-RAW files.

    I still advocate Repairing Permissions (with Apple's Disk Utility) before AND after any system update or upgrade, as well as before AND after installing any software that requires an installer that asks for your password.
    I have seen software installations go sour because the installer did not find everything as and where it should be.  I have also seen software installations go bad because the installer did not clean up after itself properly and did not leave everything as and where it should be.  This is just my own personal opinion and practice based on my own observations.
    Others may disagree and that's OK. I can only base my routines and my advice to others on my own experience and conclusion. I don't pretend to know why others believe otherwise.  Note that this suggestion begins with "I still advocate…", not "Apple recommends…".
    Repairing Permissions after the fact (i. e. not immediately before and after an install) may NOT help.  Try it anyway, though.
        ====       Additionally,  if your machine does not run 24/7 so that it runs the daily, weekly and monthly Cron Scripts in the middle of the night as intended by Apple, run Cocktail (shareware) as well.
    Cron Scripts are maintenance routines designed by Apple to run on a daily, weekly and monthly basis in the middle of the night.  If you don't run them, you WILL run into trouble, sooner rather than later.
    Here's an excerpt from the Apple tech doc http://docs.info.apple.com/article.html?artnum=107388  Mac OS X performs background maintenance tasks at certain times if the computer is not in sleep mode. If your computer is shut down or in sleep at the designated times, the maintenance does not occur. In that case, you may want or need to run these manually.
    Mac OS X periodically runs background tasks that, in part, remove system files that are no longer needed. This includes purging older information from log files or deleting certain temporary items. These tasks do not run if the computer is shut down or in sleep mode. If the tasks do not run, it is possible that certain log files (such as system.log) may become very large. Also, from:
    http://docs.info.apple.com/article.html?artnum=106978
    The disk activity generated by find is a normal part of file system maintenance, used for tasks such as removing invisible temporary files that are used by the system. It is scheduled to occur early in the morning at 03:15 everyday, 04:30 on Saturdays, and 05:30 on the first day of each month.
    NOTE: There have been comments to the effect that Apple "fixed" this in 10.4.2 and later versions of the OS, but I have not been able to verify this to my satisfaction.  The reference in the 10.4.2 release notes are far from explicit on this subject.    Other, more reliable reports indicate that this seems to have been fixed in the current version of Leopard.   
    In any event, Repairing Permissions and/or running the Cron Scripts cannot hurt.
    If you have DiskWarrior, run it regularly too.  It can't hurt either, and it often improves stability and performance.

Maybe you are looking for

  • Mac Mini worked at first with Haier 42" plasma - now won't.  Please Help!

    I'd be interested in any resolution here. Here's my story: I have a Mac Mini model MA723LL/A and a Haier P42LV6-T1 42" HDTV plasma with VGA and HDMI inputs. I first attempted to hook the Mac to the plasma TV using the DVI->VGA adapter that came with

  • Active Directory users not made member of Local Network group

    Hi all, I've just done a clean install from 10.6 Server to 10.8.4. The issue I seem to be having is a mismatch between what Groups in Server.app is reporting as members (who happen to be users or groups from our Active Directory domains) of a Local N

  • Recovery of administrator name

    I had moved and lost some of the documentation for my  IMac which included the administrator name.  I have the password.  Because of this I cannot update my system. Any suggestions on how to recover this?

  • Case of the Bouncing Icons?

    Here's an odd, if seemingly harmless, one: The other day when I tried to launch Quicken from the dock its icon just bounced away happily but the application wouldn't open. Just for fun, I tried to launch Safari and then I had two hopping icons but ne

  • OS X Mavericks 7.1 sound not working

    Hello Everyone, I have my Mac MINI late 2012 set up as TV computer. Since I upgraded to OSX Mavericks it would not deliver a 7.1 surround sound anymore. The Rear speakers won't play any sound at all. When configuring the MIDI device (HDMI) the sound