Lightroom permanent crash - no images displayed whatsoever

Hi all,
I use the 64-bit Lightroom 2.0 on a Vista Business machine. Today, I was importing some images and since the import finished I cannot get any images in my library to display. There are simply blank panels where images should be (in all modules, in import screen, everywhere). The panels display all the relevant icons, tags and stuff, but there is absolutely no image displayed.
I have tried the following:
- repair reinstall
- uninstall + reinstall
- delete settings file
- create new catalog
- optimize catalog
None of the above changes anything. The only thing I have not tried is rebooting after uninstalling and then reinstalling Lightroom.
I have not found any relevant information to this particulary nasty problem, not on Google and here on these forums. Can anybody help me restore the functionality of Lightroom? Has anybody ever even encountered this problem?
Thanks!

As indicated in post #3, I already tried that. The previews are reconstructed (I can even observe the panels changing as previews are built) and the previews folder does contain valid files (the files contain image data that can be opened with an image browser).
I have now also tried:
- running in Admin mode
- upgrading to 2.3RC
- uninstalling and reinstalling
- uninstalling and killing all relevant entries in the Registry and then reinstalling
- using a catalog made on 1.2 and converting it to 2.x
Nothing works.
UPDATE: OK NOW I GOT IT! It was the color profile! I used the Vista Color Management thing, killed all profiles and used some default sRGB profile and restarted Lightroom. It started working right away. Apparently my custom profiles made with a Spyder were somehow erased and lost. A big thanks goes to Kenneth Daves and all you guys for helping me out.
I had it at the back of my mind to try the profiles too. Since no reinstall helped I did foresee the possibility that something else on the system went bust. I couldn't do a System Restore (too many re-installs, used up all my restore points), so I was going to try first the color management thing and then some installing in safe mode (to perhaps kill any locks on DLL files that might be faulty). I would have also tried installing v1.2, but it would probably behave in the same manner.
Thanks again guys!

Similar Messages

  • Images in Photoshop and Lightroom not matching on external display

    On my external display the same image viewed in Photoshop and Lightroom is diplayed differently.
    My set up:
    Macbook pro running Mountain Lion (10.8.4), DVI connected NEC Spectraview 271. Photoshop CS4 and Lightroom 5. Both displays calibrated using Spectraview 5 software and an Eye one pro puck. Photoshop working space is Prophoto RGB and is set to preserve embedded profiles. I'm using Andrew Rodney's and Bill Atkinson's test images to try and figure this out.
    Behaviour:
    With the same image displayed in Lightroom and Photoshop on the Macbook screen they match perfectly. If I drag the Lightroom window across to the NEC it changes (as you would expect - richer colours & higher contrast). If I drag the Photoshop image across to the NEC it also changes but no longer matches the Lightroom image (cooler colours).
    So, I don't really know whether Photoshop or Lightroom is displaying correctly, and whether they or the OS are to blame. I had assumed it was Lightroom as the image is more pleasing but this obviously isn't necessarily the case. What is clear is that somewhere there is a difference between how Lightroom and Photoshop are converting the image numbers for monitor display on the NEC.
    Does anyone know how to find out what display profile Lightroom and Photoshop are using?
    Is it possible they are both using the same profile but one is not using the NEC hardware calibration? (Seems unlikely as I assume it would be impossible for the NEC to be using different internal look up tables at the same time)
    Could the OS be tripping up one and not the other in some way?
    Could the X-rite software (which I don't use but is installed) somehow be interfering?
    Anybody able to shed some light?
    Thanks for any help,
    Tom

    I'm having trouble with Lightroom 5 soft proofing with reds too.  To rid my propossed print of a gamut warning I must totally desaturate or change my paper profile to glossy (or both).  This is odd because my monitor is calibrated, I'm using the correct paper profiles etc and when I ignore the gamut warning my prints are looking good. This isn't helpful to you but at least your not alone....

  • Have trial version of lightroom images display in library and 'before' in developer, but can't display full image to develop.  Shows as a blue box with a white X on it.

    I have downloaded and installed Lightroom for a 30 day trial. Library works fine, but when I try to edit images in Develop, I can't see the full size image just a blue box with a white X on it.  If I switch on to Before & After mode, the image displays fine in the before, but still just blue box in the 'after'.  Can't find any answer to this anywhere!  Please help as my trial days are running out.

    Lightroom CC - blue box in develop module

  • Lightroom 2.1 will not display images.

    I use previous versions of Lightroom 1.3, 1.4, 2 Beta and they work fine. Now I upgraded to Lightroom 2.1 and Masters Collection CS4 and Lightroom 2.1 will not display images. All the images I import are just a shade of gray.
    When I adjust the parameters of the image the histogram is changing but the image is blank.
    I have a Vista machine.
    Thank you

    I have a Vista Home Premium, I am on Vista X86 and I just installed LR 1.4 and is working. Also LR2 Beta was working.
    So on the same Vista X86 machine LR 1.4 is working LR 2.1 is not displaying the images.
    This is the sysinfo:
    Lightroom version: 2.1 [512205]
    Operating system: Windows Vista Home Edition Service Pack 1 (Build 6001)
    Version: 6.0 [6001]
    Application architecture: x86
    System architecture: x86
    Physical processor count: 4
    Processor speed: 2.4 GHz
    Built-in memory: 3069.7 MB
    Real memory available to Lightroom: 716.8 MB
    Real memory used by Lightroom: 99.9 MB (13.9%)
    Virtual memory used by Lightroom: 75.2 MB
    Memory cache size: 65.9 MB
    Serial Number: 116040017170941123477699
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 2
    Library Path: C:\Users\Alex\Pictures\Lightroom\Lightroom 2 Catalog.lrcat

  • Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved.  It started with the last upgrade to 10.8

    Back up all data.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
    Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
    When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    resetpassword
    That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • Softproof in Lightroom and Photoshop on external display not matching

    Hi,
    When I soft proof an image in Lightroom (5) and in Photoshop (CS6) on my external display there is a noticeable difference between the two proofs.
    This is the case both with "simulate paper & ink" on and off (with matching settings in both applications) and with a variety of different profiles being used. On my laptop screen the proofs always match (between Photoshop and Lightroom).
    On the external display with soft proofing off there is an exact match between images in LR and PS. With soft proofing on saturated areas of images (particularly reds, greens and yellows) become noticeably less saturated and blocked up in LR as compared to PS. Subdued colours appear to match. It's almost like they are both using the same profile but Lightroom is squashing it into a smaller gamut. I'm fairly sure PS is correct and LR is the one with something going wrong.
    I'd like to sort it as I'd prefer to soft proof in Lightroom as that's where I print from. I've read up a lot on colour management and can't find a solution.
    Can anyone help?
    Thanks,
    Tom
    (I'm on a Macbook pro running 10.8.4 and the external display is an NEC Spectraview 271 (euro version of PA271W), the display is calibrated and profiled with Spectraview 5, with an i1 Display Pro. Working space in PS is Prophoto RGB and it's set to preserve embedded profiles. I've checked with various test images but mostly been using Bill Atkinon's printer test image. I set up the image in LR and PS to match on screen position and with the same colour (white) background, I can then flick back and forth and there should be no change but there is and it's very obvious.)

    I'm having trouble with Lightroom 5 soft proofing with reds too.  To rid my propossed print of a gamut warning I must totally desaturate or change my paper profile to glossy (or both).  This is odd because my monitor is calibrated, I'm using the correct paper profiles etc and when I ignore the gamut warning my prints are looking good. This isn't helpful to you but at least your not alone....

  • Lightroom 2 crashes need help.

    I just imported some 1DsMk3 files and after the import Lightroom 2 crashed. Now I started again and after a few seconds it crashes again. I tried different libaries but they are all crashing now.
    System:
    Windows Vista 64
    3,2Ghz Intel
    8GB Memory
    2*150 GB hardrives there lightroom is installed and two 500GB as scratch and image disk.
    Before that Lightroom 2 was working fine.
    Here is the error massage:
    Problem: APPCRASH
    programm name: lightroom.exe
    version:2.0.0.0
    time mark: 4874a113
    Error name modual:CameraRaw.dll
    Error modual version:2.0.0.0
    Error time stamp:4874a042
    Code:c0000005
    Offset:00000000002d6568
    extra info 1: 602d
    extra info 2:b048166afeca29e79e43de765bb90aae
    extra info 3:2a0b
    extra info 4:ef163ebfe639db77a5be8019b4f857b3
    Thanks a lot for the help.

    UPDATE:
    Photoshop CS3 and all other programs run as usal. I also tried to reinstall lightroom but did not help.

  • Image Display got rotten (really: the Indicator, not the Image!)

    I'd like to hear comments on the following VI, containing just a single Image Display Indicator, which, for some reason got corrupted during porting across LV versions and resizing. By divide and conquer I found that it was the origin of pretty odd problems that I was observing in a complex VI: absence of front panel updates, pull down menues not displayed, actions needing a double press of buttons, and so on.
    The VI is saved from LV2012 windows, also attached as saved for 8.5. Just opening it, on 2 installation of Labview, I turn labview into something responding oddily. (try to pull down a menu, e.g.). Linux LV seems not to suffer from it, maybe because it places a nonfunctional FP placeholder for this control, without trying to cope with its nonfunctionality.
    The question is perhaps, why LV doesn't detect the problem and behaves so weirdly with it -- bug?
    Enrico
    Attachments:
    BadImage.vi ‏34 KB
    BadImage85.vi ‏36 KB

    Yes, I was able to see this trouble as well. Checked in different versions (2010 and 2012 x86/x64). But was unable to re-create this VI from scratch. It seems to be that Vision Control was broken in customization attempt where cluster with buttons was rearranged from vertical to horizontal position (may be in combination with saving for previous LabVIEW version).
    Time to time I do the same (for example save VI with vision controls from v. 8.6 to 7.1) and I've got lot of situations when "downgraded" VI cannot be opened or caused just crash, or broken. Something is wrong.
    Quick and dirty analysis of the given "BadImage.vi" shows that the problem with refreshing is present. LabVIEW tries to refresh this control continuously.
    In Process Explorer we can see one thread with 100% CPU load (overall 20-25 percent, because I have 4 CPUs):
    In Call Stack we may see DrawImageControl function which is called from niviswnd.dll.
    Well, load this stuff into debugger, set breakpoint and see - this function called continuously:
    called somewhere from SetPIClusterPartSize from LabVIEW.
    I don't want to go deeper into call chain analysis (anyway makes no sense without source), but short walking in debugger shows that messages continuously fired:
    Check it with Spy:
    There are thousands WM_PAINT messages which continuously sent to the Window with this weird control. Looks like attempts for update, but due some internals errors this called again and again.
    The messages queue is full with WM_PAINT - therefore LabVIEW is "unresponsive" - context menus cannot be shown, dialogs cannot be closed, slow reaction, etc.
    Sorry for slightly off-topic above, but may be this will be helpful for NI's engineers for further investigation.
    Andrey.

  • Experiencing problem with image display in LR5

    I have an intermittent problem with images displaying and exporting in LR. It just began a couple of months ago and is totally random - will do it with RAW (CR2) or JPG. It displays this way in all modules - Library, Develop, Slideshow....The image displays fine in a non-Adobe image viewer (Faststone or Windows Viewer). I've reloaded LR5 and PSCC and is still persists. I know the image file is fine. It also has begun effecting older images that were showing up just fine a while ago. I just loaded about 200 images and maybe 3 or so have this viewing problem in LR & PS. Has anyone else experienced it and have a suggested fix? My graphics card has the latest drivers and shows no problems with other applications. Here is the same image - one a jpg export from Lighroom, the other a save as jpg from Faststone. HELP!

    This is almost always a hardware problem, causing corruption of the file. The difference you see between Lightroom and other software is that Lightroom is accessing the full RAW image, while the other software is trying to read the embedded JPG preview.
    To figure out exactly what hardware is the problem, you need to try different transmission paths and hardware ... different camera cards, different card readers or USB cables/USB ports, different hard disks, etc. Eventually you should be able to isolate the problem.

  • LabVIEW 8.2 Image Display bug

    Hi all,
    Description : Trying to create a constant by right
    clicking on an image display (controls palette > vision > image
    display) causes labview to crash.
    LV
    version : 8.20 only, didn’t exist in 8.0.1 and earlier !
    Same bugg happens:
    with image display (classic),
    when trying to create a constant from a
    local variable of these indicators,
    when trying to create a constant on the
    connector of a subVI for these indicators.
    Message Edité par TiTou le 10-23-2006 08:38 AM
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
    Attachments:
    bugg_image_display.png ‏234 KB

    Hello,
    Thank you for reporting this.  A CAR has been filed on the issue - for reference the CAR ID is 4308NMSQ.
    Best Regards,
    JLS
    Standard Response:
    This was reported to R&D (4308NMSQ CAR ID) for further investigation. Thanks for the feedback!
    Best,
    JLS
    Sixclear

  • Lightroom 4 crashes on import

    Windows 7, Home Edition, version 6.1 service pack 1
    Intel 7, with more than 400gb memory available
    I've now spent more than 32 hours trying to solve this problem, including two phone calls and three chat sessions with Adobe Help Desk.  The Help desk takes me through the same checklist of "fixes" as the previous calls and inquiries and has resulted only in wasting more hours of my time. 
    To date I have tried the following to fix this issue:
    - uninstall and reinstall with and without the LR 4.1 update
    - create a new administrator account on my machine and run LR off the new account instead
    - create a new catalogue for every import (which kind of defeates the purpose of having LR to begin with)
    - wipe out my old preferences file and allow LR to create a new one
    - completely wipe my hard drive and reinstall EVERYTHING all over again
    - rebuild my catalogues from scratch on a new, fresh install of lightroom
    - limit my cache size in LR preferences
    - limit my backups in LR preferences
    - change my 1:1 previews
    - attempt to import images from a Nikon 90, D3s and D800 only, each on a fresh LR install (in an effort to see if it was a particular camera model causing the issue)
    - attempted to only import directly from another hard drive, rather than an external or internal card reader
    Each time I have no more than a day of proper working conditions before the program hangs up and windows pops up a warning that the program has ceased to respond and must close.  Lightroom is rather useless if I can not import images.
    I'm out of solutions or fixes, and out of patience now too.  I'd really like to continue using Lightroom products because of how integral it is to my workflow.  At this point I'm ready to switch to a competitor if this issue can not be solved.

    Hi Dave lorde,
    Do you get an error dialog for Lightroom crashing?
    Also which version of Lightroom are you using? Have you tried with Lightroom 4.4 yet?
    You might also try downloading the Lightroom 5 beta that is available now on labs.adobe.com and see how it works on your system there.
    As for the current issues, my suggestions are as follows:
    0. Make sure you're up to date with LR 4.4 or LR5 beta
    1. Take a look through our performance optimization documents for Lightroom and see if any of these suggestions give you something to work with:
    Optimize LR performance
    http://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html
    Performance Hints
    http://helpx.adobe.com/lightroom/kb/performance-hints.html
    2. Try resetting Lightroom's preferences: http://helpx.adobe.com/lightroom/kb/recover-catalog-images-resetting-lightrooms.html#id_90 046
    3. Try Lightroom in a new administrator user to see if the hangs continue.
    Let us know how it goes,
    regards,
    Pete

  • Lightroom constantly crashes whenever I try to use develop, print, slideshow!

    This is driving me insane. I desperately want to use lightroom but outside of the library functions and the quick develop tools, I can't get into anything else. I can import images fine but when I try to click from the library mode to develop, sideshow or print, lightroom completely crashes and becomes a non-responding program. Whats even worse, is that windows explore (not the internet browswer, the actual platform) would also freeze after I ctrl-alt-deleted lightroom and I'd have to restart my entire system.
    I've installed lightroom twice thinking it was just a bad install and am running version 1.3.01, I think it is (I have the most recent update installed since I thought maybe that would cure it). I even installed another GB of ram into my PC thinking that would help but now even with 3 GB of ram in my system lightroom still crashes although explorer seems stable.
    Has anyone else had this problem, and if so had any luck fixing it? It's driving me insane!
    Thanks guys!~
    Joshua

    Wonder if any of following would help:
    http://blog.rrdphoto.com/2007/11/lightroom-13-freezing-with-nvidia.html
    http://www.adobeforums.com/webx?128@@.3c054997
    http://kb.adobe.com/selfservice/viewContent.do?externalId=333653&sliceId=2

  • PS CS5 Image Display Differs From Used ICC Profile In Win 7

    Hi,
    on my Windows 7 Ultimate x64 machine, I just calibrated my Dell SP2309W monitor using an i1DisplayPro and basICColor 5, creating a ICC v2 profile (I am aware of the problems under Windows with ICC v4 profiles).
    It created the ICC profile and applied it to be used by Windows. I double checked under COLOR MANAGEMENT that the new ICC profile is being used. Although I can see that the new ICC is being used (desktop appearance changes), there are a few issues I am experiencing:
    (1.) Windows Photo Viewer
    The thumbnails in Windpows Explorer look fine (they DO use the new ICC profile), when I double click a jpeg and open the image it DOES NOT use the new ICC profile. When I click the PLAY SLIDESHOW button (starting the slideshow) in the opened image in Windows Photo Viewer, the images DO use the new ICC profile.
    (2.) Internet Browsers
    All current internet browser (Firefox, IE, Safari and Chrome) DO use the new ICC profile and display the image correctly.
    (3.) Photoshop CS 5
    When I open the same image - that Windows Photo Viewer does not correctly displays (according to the new ICC profile) - in Photoshop CS5, I get the same image display that Windows Photo Viewer gives me (when not thumbnail or not in slideshow mode) - it appears to be the sRGB display.
    My color settings in PS CS5 are: North America General Purpose 2 > sRGB IEC 61966-2.1.
    When I go to View > Proof Setup > Monitor RGB I get the image display using the new ICC profile.
    Why does the image look different in PS than my calibrated monitor should output ?
    I was under the impression (please correct me if I am wrong), that the sole purpose for calibrating my monitor was to get a uniform display across (ICC aware) applications. Even when one applies different color spaces to a document in PS, I thought the output on my calibrated screen done by the graphic card should always be according to my calibration and the settings in the ICC profile being used.
    What Am I doing wrong or what am I misunderstanding ?
    Any help or input is appreciated !
    Thanks.
    - M

    Hello,
    A note on monitor calibration: calibrating your monitor will not guarentee that every application will display color correctly, it's more of a step along the pipeline, and for the preview part of a color workflow it's the last step.  Here's how color translation follows for an ICC workflow when previewing to a monitor:
    Image Color Numbers > Document Tag or Workspace Profile > Monitor Profile
    For non-color managed applications, if the original document is or isn't tagged with a color profile it will be translated directly to the monitor profile anyway.  This is the equivalent in Photoshop of selecting "Monitor" in soft proofing.  Selecting monitor in softproofing will bypass the tagged or workspace profile to translate colors directly through the monitor profile.
    For most automatic color managed applications (like Firefox), the image will be translated through the tagged profile and then sent through the monitor profile.  If the image is untagged or the profile is unrecognized, the colors get sent directly to the monitor profile.
    For Photoshop, a tagged document will have its profile respected and then sent to the monitor.  An untagged document will be assigned the workspace profile, which acts like a temporary document profile, and then gets sent to the monitor.  This is often why users will notice Photoshop behaves differently from other applications.  It's usually a case of the workspace coming into play.  By default the workspace profile is set to sRGB.  You can change this in Edit > Color Settings.
    The purpose of the workspace is originally for printing workflows, as a way of keeping consistant color translations when dealing with both tagged and untagged documents.  For web output workflows it can be useful for viewing everything through sRGB, which is typical of the average monitor output (not so with newer wide-gamut monitors, another source of confusion...) combined with the fact that originally most web browsers were not color managed.  Hence viewing everything through sRGB is pretty close to what most monitors see and what untagged/unmanaged docs will look like.
    Monitor calibration is useful only because it brings your monitor output to a "known state".  In traditional workflows the monitor was always a middle-man, a preview device which was useful for getting an idea of what the printed output would look like before you print it.  Since print colorspaces are often smaller than display spaces, it's feasible and useful to narrow down the monitor/display space and calibrate it to a known state, so that even if it doesn't totally match the print, you'll get used to its differences/limitations and they'll be consistent so long as the calibration is maintained.
    For web output, your final output is often another user's computer monitor, which can have any form of behavior (most standard monitors are pretty close to sRGB, or use sRGB as an operating system workspace (default monitor profile).  Wide gamuts behave differently, but I'm not sure if there's a particular ICC space that they closely match, or if different wide-gamuts are even that close to each other in their display color spaces.
    Hope this helps!

  • Image display control scrolling does not work properly when zoomed in

    I am using a ROI on an image in the image display control. When zooming into the image to fine-adjust the positioning of the ROI, the image scrolling does not work properly. As far as I understand, the image should scroll automatically when the ROI is leaving the visible area. However, the scrolling behaviour seems to depend on the origin of the Labview panel, not the origin of the image display control, which might require to move the ROI way out of the visible area before the scrolling takes place. In other words: the coordinate system of the image display control is shifted with respect to the true visible image area, depending on where you place it on the front panel. As a consequence, when clicking on a ROI which is in the visible area, but is outside of what Labview thinks is the visible area, it might immediately jump to the left border of the image, making the positioning of the ROI really difficult.
    Has anyone noticed this behaviour, and what would be a reliable solution to avoid this? 
    Dirk

    Hello,
    no, I am not talking about the tools palette. Just place an image control with some image in it on a new VI front panel. Then, use the rectangle from the tools and select a ROI in the image. If you zoom in (using the magnification glass), and then grab the ROI and move it around, the image scroll with the ROI. So far, so good. If you now place the image control elsewhere on the panel, or add new control above it, resize the panel, etc. , this scrolling when moving the ROI will not work correctly if the origin (0,0) of the panel is far away from the image control.
    I have attached a VI for simplicity (although there is hardly any code in it).
    If you make a ROI and try to move it down, you will notice that scrolling starts if you move the mouse out to about 10cms below the image (depens on your screen, of course). After that, if you click on the ROI, the scroll bars and ROI might jump up to the upper end of the image. Imagine how annoying this is if you try to finely adjust the ROI position. 
    I think it is a bug in the implementation of the image display control.
    Thanks,
    Dirk
    Attachments:
    scrolling.vi ‏818 KB

  • Hello apple guys, i can't open app store, reminders, contacts, mail(crash), maps, Image Capture, and other apps that comes with Mavericks OS, how i can solve this problem?

    hello apple guys, after installing OS X Mavericks, i can't open app store, reminders, contacts, mail(crash), maps, Image Capture, and other apps that comes with Mavericks OS, how i can solve this problem?

    So is this the way Apple works now? Not solving customers problems? I'm sure so many users have had this problem. I've had, and I reinstalled Mavericks 3 times. Works fine for some days and then several Apple Apps stop working. Is that a way to force us ti update to Yosemite? (I don't want to) and then pay to update some third party programs (i.e. Pro Tools). Also, there are so many 15" MacBooks Pro with graphic problems and of course the guys at the Apple Service Centers always say: "It's the logic board, you can have it replaced, but it's so expensive I would recommend a new Mac".  I really, really miss Steve Jobs!

Maybe you are looking for