Image Orientation/Rotation Problem in Lightroom 3.2 Final

This is a continuation of my previous post regarding this same problem in 3.2RC. It's still happening in the Final version of Lightroom 3.2.
THE PROBLEM
Image orientation is not working properly in Lightroom 3.2. This affects newly imported images and images that were already in my Lightroom database -  and which have been in the database since Version 1.
Here's a screen capture showing the strange displays I'm seeing in  Lightroom's grid mode:
Notice the odd angle of the image. When I use the Rotate Photo Left tool, the display looks like this sometimes. After a second or so, it will snap to either a vertical or horizontal orientation by itself but rarely gives me the 90-degree rotation this tool should give. The image may flip 90-degrees or 180-degrees, there's no way to tell.
When I view the image in Loupe view or on my second monitor, the orientation shown in Grid view does not match that displayed in Loupe Vew. For this particular image, Grid view currently shows it as correctly orientated as a horizontal while Loupe view shows it rotated 90-degrees to the right. Shouldn't they match?
BACKGROUND
I never had a problem with image orientation in any preveious version of Lightroom prior to Lightroom 3.2RC and 3.2 Final. So, it seems to be a bug in 3.2. I'm still using the same computer and video card I used with previous versions. My operating system is Windows 7 Home Premium. Both Windows and Lightroom are 64-bit.
HELP!
Is anyone else having this problem? How can I solve it?
Alan
PhtooCitizen.com

The size of the catalogue is almost certainly not at play here.
FWIW, I recall seeing something like this once a long time ago on a Mac, possibly with Lr 3 beta, or Lr 2.x.  It went away with a restart. It almost looks like a threading issue, where a thread is suspended or preempted and then is lost or disconnected from the main UI thread.
I recall you can just rotate the image again and it will right itself.
Adobe fist-line support seem to want to use the number of images in the catalogue as some sort of catch-all.  The problem with this is that most of us can demonstrate that there is little correspondence with the number of image IDs in the database and many reported UI artefacts.
I'd keep raising this with them, and suggesting that the size of the catalogue is probably not at play here. As a tactic, you can ask what the maximum size of a catalogue should be, and if it is raw images or the number of changes to the images and virtual copies that is the problem, and if this can be verified by second- or third-line support.

Similar Messages

  • Contact Sheet image rotation problem

    When using the Contact Sheet f
    unction of CS4, some of the images are rotated 180
    degrees on the sheet.  Some of them are right side up and some are rotate
    d.  Changing the "rotate for best fit" checkbox has no
    affect.
    Has anyone else had
    this problem??
    Thanks.
    Jim

    Hi captianbob,
    Make sure that you have not selecte primary only (look in the edit menu, can be toggle with the S key)
    You can promote or demote images in the stack, see the Stacks menu.
    You can always create an album or smart album and use that to play you slideshow.
    Just an advice, if you have multible questions you should make seperate posts.
    Best regards - Per.

  • Rotation problem after editing in Photoshop

    I'm using Lightroom 1.3 and Photoshop CS3 with all the current updates. This problem was the same in LR1 and PS CS2.
    I have a mix of orientations in the JPEGs in my library - portrait and landscape. When the photos are imported into LR they appear correct. If I select a bunch of them, open them in PS (using Edit in Photoshop > Edit Originals), run a noise filter, save them, and then go back to LR, the previews for the portrait images are rotated so that all the previews show as landscape.
    The portrait images display correctly (except for the fact that they have been rotated) in the Library module - both grid and loupe view). In the Develop module, the image aspect is displayed portrait but the image is as a distorted landscape - the image is rotated and then distorted to fill the portrait oriented space. In the Print module, that same distorted image is fills the portrait oriented page. To be clear, instead of a portrait image appearing in the correct orientation on a portrait page preview, the image is rotated 90 degrees and then stretched to fill the page.
    There is a badge on the preview indicating that the metadata is out of sync with the file.
    If I rotate the image in LR, the badge goes away and the image appears portrait and undistorted in the Library module's grid and loupe views. The Develop module show the portrait image in the correct rotation, but has been stretched to a landscape aspect. The Print module shows that distorted image rotated to fit the portrait page.
    The only way to correct this is to "Read Metadata from file". This resets all the orientation information so that it displays correctly in LR, but all the tags and IPTC information gets erased.
    This is most of the reason why I was writing all the metadata into to files until now. I would write the metadata before editing in PS, do my PS edits, and then back in LR I'd "Read the Metadata" from the files to set everything correctly in LR. But of course now that I'm working with Leopard I get screwed if I do this because my files will crash the Finder.
    To top it all off, I've run into the "...cannot be saved because the file is in use" problem with some files I opened last night.
    Clearly none of these issues are being addressed in Adobe or Apple's updates. Is there a reasonable workaround that will let me:
    1. set metadata and tags and know that they won't either get lost or cause problems
    2. have image orientation respected and displayed correctly
    3. not crash any of the three critical applications on this computer - Lightroom, Photoshop, and Finder.

    I really appreciate your explaining this Jao.
    I'm going to explain how I got into this situation, in the hopes that it may prove useful to someone (I'm looking at you, Adobe) who wants to understand how the app is being used in the real world.
    So as not to break up the narrative, let me just say that I'd be happy (ecstatic, actually) if I could use Lightroom for my entire workflow, but the noise reduction filter in LR is just nowhere near as good as NoiseNinja. (A problem shared by LR, PS, and Aperture.) If I could run NN from inside LR, that would rock.
    Oh, and I shoot JPEG because I shoot live events where the lighting is usually crap and I need to be ready at any moment for something interesting to happen. Shooting RAW would be nice, but it's too slow and takes up way too much space.
    So here's what I do, (hopefully edited to make the reading non-tedious)
    1. import all photos from source (usually memory cards)
    The photos go onto a drive reserved for photos. I shoot events, so everything is organised by date-event. On import I set filenames (date - event name - time stamp.jpg) and keywords.
    2. cull
    They get marked "1" (irretrievably useless, to be deleted), "2" (keep just in case), "3" (decent shots), "4" (photos that I want to show to other people), or "5" (this is one of my best this year). Delete the "1"s.
    3. select 20-30 "picks"
    I create a folder within the event folder called "Picks" for these photos. Then I duplicate that folder as "Originals"
    In doing it this way I can protect myself if I need/want to change my cataloguing application. I'm on my fourth one at this point (Lightroom) and while I am generally finding that LR is meeting my needs more than anything else I've tried, I've been burned in the past (how many of us have regretted letting Aperture put all our photos into an incomprehensible database/folder hell?)
    The Picks/Originals structure makes sure that the originals never get touched (because it doesn't show up in LR) and I can quickly find the Picks.
    I -was- writing the metadata to the files so the ratings, keywords, and IPTC info was where it should be - attached to the photo. I've stopped doing this for the time being until this whole Finder-craching debacle is corrected.
    So why am I not using LR's built "Edit - Copy"/stacking function, which more or less duplicates my process?
    Well part of it was my own dumbness - Aperture made the edited copy/variation a Photoshop file, which ballooned my collections with staggering speed. I'm not sure if LR used to do the same thing, or I just made the assumption. My mistake.
    The other part of the problem is just the simplicity of having an Originals folder that is effectively ignored. Using LR will mix the "-edited" files in with originals, which is not as efficient or elegant a solution, but I'll give it a whirl.
    Thanks for your suggestion. If giving up my Picks/Original process solves the rotation problem then perhaps it's a fair trade.
    Still, it seems that the right hand is somehow oblivious to what the left hand is doing in the whole PS/LR thing, and that it ought not work that way.

  • Rotate problem

    I am shooting tethered direct into L3. I need to rotate my images to portrait and when I move to the previous image the image I have just rotated goes back to its original orientation. Go back to it and re-rotate it and then everything stays as it should. Very frustrating and hardly helping workflow. Anyone else experienced this?
    Canon 5d Mk 1, OSX 10.5.8

    I want the image to fill the screen on my camera - you loose half the image when auto rotate is on.
    My camera (Nikon D80) have an option to tag images as rotated and another option to display it rotated in screen. I leave the first option on for Lightroom and other software to display it correctly, and the second option off to use the camera's LCD real estate more efficiently.
    Check your camera's custom settings — Canons might have that second option too. That will solve both your problems.
    Well it's not really relevant to the problem but ...
    Yes, but sometimes it's good to look into the root of the problem. This could lead you to a more efficient solution.

  • Auto Rotate problems when shooting tethered overhead

    I am shooting with a Canon 5d mark 2.  When I shoot product into the auto rotate works properly and the image appears rotated properly. Although when I shoot overhead or down on product it seems to get confused. If I rotate the camera twords the horizon and fire it figures out which way it should be the I can reframe my overhead shot.  But if the camera is moved at all it will show up rotated the wrong way and I have to slightly move the camera away from its directly overhead framing again so it can figure out wich way it should be rotating. I have tried all three rotate modes with the camera with similar inconsitant results. What is the best setting on the camera to get consistant results. Or ii I turn auto rotate off is there a way to tell lightrroom to rotate it properly on import like it does for all other settings like white balance.

    This isn't a function of tethering, I wouldn't think. Many cameras have a sensor that determines the orientation of images so auto-rotate works. The problem is that these sensors generally only work along one axis, using the force of gravity to tell them where down is. When you orient the camera such that the lens is pointing down most sensors no longer are able to determine whether you are in portrait or landscape, because there is no down -- it ends up being somewhat random.
    I've seen this on many different cameras, and all without tethering. It has to do when the sensor is read when composing the short.
    Your best bet is to set the camera to ignore the sensor when taking pics like this, and rotate the image by hand that are need to be in portrait. If there is no rotation in the image metadata, Lr will not rotate it. It will have to be done by hand. It won't be that hard to select a number of images and bulk rotate them.

  • Image Orientation in Blog and Blog Summary

    Inserted a picture into a blog entry and rotated it 90 deg.
    In the blog summary, on the summaries page, the image reverts to its original orientation.
    Can't see a way to change the image orientation on the summary page, which would be undesirable anyway - don't want to have to edit two pages for every entry.
    Has anyone experienced this problem?
    Are there any solutions?
    Thanks

    I played around with the orientation manually, and found that if I change the orientation, the image would be correctly "orientated' in the lower part of the split viewer, but the actual image would be off by 90 degrees. I then reoriented the image back (sideways view in the bottom file-strip) and the large image would display correctly again, and, the bottom image corrected itself to the normal orientation. So, by changing each sideways image 90 degrees once and then back again, seems to "fix' the issue. Still not sure how I applied this feature.

  • [solved] Image orientation issue

    Hello,
    I have a problem with image orientation.
    I am using Arch64 and KDE 4.4.5 from Arch.
    When I look at my pictures in digikam (1.3.0) or gwenview, portrait pictures are displayed fine. If I send them with thunderbird, portrait images are displayed with landscape orientation.
    The only workaround I found is to rotate twice the image with digikam (once on the right and once on the left to set it back to previous orientation).
    I have noticed that EXIF information change...does anyone have the same issue and knows what is the cause of it ?
    before, orientation is "droit, haut" = "right, top"
    after, orientation is "haut, gauche" = "top, left" and width and heigth size is set...
    regards
    Last edited by supercow (2010-07-08 17:20:11)

    Digital cameras create images that aren't rotated as such -- as plain images they're always in landscape format. If your camera has an orientation sensor, it will merely hint at the intended orientation by setting the exif orientation value in the jpeg file (instead of really rotating the image and creating a jpeg with a portrait format).
    Not all programs interpret all exif data. Programs that don't interpret the exif orientation (as thunderbird seems to do it) will display the image as it is (always in landscape), while others (like digikam) use the exif data to decide on how to rotate the image for display. So digikam is just smart enough to show the image in it's "logical" portrait format while it's "physically" remains in landscape format.
    To make a real portrait jpeg, you have to really rotate it and adjust the exif orientation accordingly, which is what effectively happens if you use digikam in the way you describe it. So that's not a workaround, but required to make sure that all programs display the images in the desired format, and not just those that are smart enough to honor the exif orientation.
    See the jpegexiforient and jpegautotran programs for an explanation and an alternative way to rotate images based on their exif orientation value.
    Last edited by hbekel (2010-07-07 21:55:00)

  • Unable to stop images from auto toning in lightroom 4

    lightroom automatically auto tones images after importing them even when told not to do so in the preferences.
    Edit> preferences> presets
    I have made sure everything is unchecked.
    I previously asked this question but got no solution so i'm trying again to ask.
    here is link original: http://forums.adobe.com/message/4320121
    to sum up my problem. when I synchronize a folder it imports the images, which then starts auto toning the thumbnails and if i click on image its looks awful. so its not just the thumbnails its the image also
    this is really frustrating for me because I shoot in HDR, meaning I bracket my shots  from -3 to +3, 1 stop for each image. so what i expect is each each to go from dark to light but instead lightroom tones them automatically making each image near identical.
    its like lightroom thinks theres a problem and tries to balance each picture so instead of going from dark to light now all 5 bracketed shots look near identical because it has toned them.
    i dont know why it does this.
    i have uninstalled light room.
    deleted every folder, cache in my app data and anything related to adobe lightroom. rebooted.
    reinstalled.
    Edit> preferences> presets
    I have made sure everything is unchecked.
    then i import a folder and again it starts auto toning them.
    my work around is to select all images> right click develop settings>reset
    and now they look normal.
    so i have to do this each time, basically adding another step.
    the frustration grows because I suffer from ADD and some times I forget to reset the images after an import. grrr
    anotyher huge problem is I export images.
    when ever I have finalized the image and deem its ready for the internets I export it to a subfolder as a jpeg at 100% size and quality.
    then I synchronize the folder and it imports those new jpeg pictures
    and guess what it does, it auto tones them,
    argghhhh
    this is driving me nuts.
    all i want it lightroom to NOT auto tone anything after an import.
    i want my pictures and thumbnails to look exactly how they look.
    to be specific. after I import i can see all my thumbnails, they looks fine. i can see my bracket shots from dark to light as they should but a few seconds later i start to notice lightroom is auto toning each thumbnail one by one. its not instant it takes a a sec or so to do each thumbnail.
    I wish to prevent that...how?
    Can anyone please help me
    on my last post I tried everything everyone suggested but for some reason thread is locked and i could not reply anymore even though it states NOT answered.

    If you haven’t already, I’d delete your LR4 preferences file, in case it is corrupt.  On my 32-bit windows system, the LR4 preferences file is in the following folder:
       C:\Users\yourusername\AppData\Roaming\Adobe\Lightroom\Preferences
    and is called:
      Lightroom 4 Preferences.agprefs
    Exit LR4, and delete this file, then restart LR4, and try importing a new, never-been-seen image file.

  • Character rotation problem in tiled map

    Hi I am trying to rotate the character in a tiled map. Its is successful but theres problem with moving diagonally. When i pressed for example up and right keypressed, when its moving it will rotate as i wanted but when i released the buttons, it either rotate to the up or right. I want the image to rotate diagonally and stay as it is when i released the buttons.
    Here are my source code...I noe its very long but really need someone help...There are 3 java files. (Sorry for dis long and ridiculous codes...)
    1) Game.java
    import javax.swing.*;
    import java.awt.*;
    import java.awt.image.BufferStrategy;
    import java.awt.event.WindowAdapter;
    import java.awt.event.WindowEvent;
    import java.awt.event.KeyEvent;
    import java.awt.event.KeyListener;
    public class Game extends Canvas implements KeyListener
         private BufferStrategy strategy;
         private GameMap map=new GameMap();
         private Player player;
         private boolean left,right,up,down;
         Image ship = Toolkit.getDefaultToolkit().getImage("res/up1.PNG");
         public Game()
              Frame frame = new Frame("Pirate Game");
              frame.setLayout(null);
              setBounds(0,30,480,510);
              frame.add(this);
              frame.setSize(480,510);
              frame.setResizable(false);
              // exit the game
              frame.addWindowListener(new WindowAdapter() {
                   public void windowClosing(WindowEvent e) {
                        System.exit(0);
              frame.addKeyListener(this);
              addKeyListener(this);
              frame.setVisible(true);
              createBufferStrategy(2);
              strategy = getBufferStrategy();
              player = new Player(ship, map, 1.5f, 1.5f);
              // start the game loop
              gameLoop();
    public void gameLoop()
              boolean gameRunning = true;
              long last = System.nanoTime();     
              // keep looking while the game is running
              while (gameRunning)
                   Graphics2D g = (Graphics2D) strategy.getDrawGraphics();
                   // clear the screen
                   g.setColor(Color.black);
                   g.fillRect(0,0,480,480);
                   // render our game objects
                   g.translate(0,0); //placing the map to desired location on the frame
                  map.paint(g);
                   player.paint(g);
                   // flip the buffer so we can see the rendering
                   g.dispose();
                   strategy.show();
                   // pause a bit so that we don't choke the system
                   try { Thread.sleep(4); } catch (Exception e) {};
                   long delta = (System.nanoTime() - last) / 1000000;
                   last = System.nanoTime();
                   for (int i=0;i<delta / 5;i++)
                        logic(5);
                   if ((delta % 5) != 0)
                        logic(delta % 5);
         public void logic(long delta) {
              // check the keyboard and record which way the player
              // is trying to move this loop
              float dx = 0;
              float dy = 0;
              if (left)
                   dx -= 1;
              if (right)
                   dx += 1;
              if (up)
                   dy -= 1;
              if (down)
                   dy += 1;
              // if the player needs to move attempt to move the entity
              // based on the keys multiplied by the amount of time thats
              // passed
              if ((dx != 0) | (dy != 0))
                   player.move(dx * delta * 0.0015f,dy * delta * 0.0015f);
         public void keyTyped(KeyEvent e) {}
         public void keyPressed(KeyEvent e)
              if (e.getKeyCode() == KeyEvent.VK_LEFT)
                   left = true;
              if (e.getKeyCode() == KeyEvent.VK_RIGHT)
                   right = true;
              if (e.getKeyCode() == KeyEvent.VK_DOWN)
                   down = true;
              if (e.getKeyCode() == KeyEvent.VK_UP)
                   up = true;
         public void keyReleased(KeyEvent e)
              if (e.getKeyCode() == KeyEvent.VK_LEFT)
                   left = false;
              if (e.getKeyCode() == KeyEvent.VK_RIGHT)
                   right = false;
              if (e.getKeyCode() == KeyEvent.VK_DOWN)
                   down = false;
              if (e.getKeyCode() == KeyEvent.VK_UP)
                   up = false;
         public static void main(String args[])
          new Game();
    2) GameMap.java
    import javax.swing.*;
    import java.awt.*;
    import java.util.*;
    public class GameMap
         int width = 15;
        int height =15;
        static final int TILE_SIZE = 32;
             int[][]  A  =  {{1,1,1,1,1,1,1,1,1,1,1,1,1,1,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,3,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,2,2,2,2,2,2,2,2,2,2,2,2,2,1},
                                 {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1},
        Image sea = Toolkit.getDefaultToolkit().getImage("res/sea.PNG");
        Image rock = Toolkit.getDefaultToolkit().getImage("res/rock.PNG");
         public void paint(Graphics g)
            for(int across = 0; across < width ; across++)
                for(int vert = 0; vert < height ; vert++)
                    if (A[across][vert] == 1)
                    g.drawImage(rock,across*TILE_SIZE,vert*TILE_SIZE,null);
                         else
                         g.drawImage(sea,across*TILE_SIZE,vert*TILE_SIZE,null);
        public boolean blocked(float x, float y)
              return A[(int) x][(int) y] == 1;
    3) Player.java
    import java.awt.Graphics2D;
    import java.awt.Image;
    public class Player {
         private float x;
         private float y;
         private Image image;
         private GameMap map;
         private float ang;
         private float size=0.3f;
         public Player(Image image, GameMap map, float x, float y)
              this.image = image;
              this.map = map;
              this.x = x;
              this.y = y;
         public boolean move(float dx, float dy)
              // new position
              float nx = x + dx;
              float ny = y + dy;
              //check collision
              if (validLocation(nx, ny)) {
                   x = nx;
                   y = ny;
                   // and calculate the angle we're facing based on our last move
                   ang = (float) (Math.atan2(dy, dx) + (Math.PI / 2));
                   return true;
              // if it wasn't a valid move don't do anything apart from tell the caller
              return false;
         public boolean validLocation(float nx, float ny)
              if (map.blocked(nx - size, ny - size))
                   return false;
              if (map.blocked(nx + size, ny - size))
                   return false;
              if (map.blocked(nx - size, ny + size))
                   return false;
              if (map.blocked(nx + size, ny + size))
                   return false;
              return true;
         public void paint(Graphics2D g) {
              int xp = (int) (map.TILE_SIZE * x);
              int yp = (int) (map.TILE_SIZE * y);
              // rotate the sprite based on the current angle and then
              // draw it
              g.rotate(ang, xp, yp);
              g.drawImage(image, (int) (xp - 16), (int) (yp - 16), null);
              g.rotate(-ang, xp, yp);
    }

    rotate() should always be accompanied with appropriate translate().
    See:
    http://java.sun.com/docs/books/tutorial/2d/TOC.html
    http://www.adtmag.com/java/articleold.aspx?id=1241
    http://www.apl.jhu.edu/~hall/java/Java2D-Tutorial.html
    And, never mix AWT components with Swing ones.
    Use JPanel instead of Canvas.
    Use also standard drawing/painting technique shown above URSs.

  • Exposure problem with Lightroom 4 CS5 and Raw 6.7

    Hi all
    I have recently upgraded from Lightroom 3.6 to the new Lightroom 4 and am genrally pretty happy with it, I tend to use it along with photoshop CS5 extended and also imagenomic Portraiture, but I have found an annoying little problem in doing this and something that I never suffered with when using Lightroom 3.6 and it is this...
    when I take an image from Lightroom 4 and click Edit image in Photoshop CS5 and then use Imageonmic to soften skin etc all seems to work well I then carry out any touching up within Photoshop and once finished save it back to lightroom for any final tweaks etc which is fine and all works smoothly, except once I have saved it back to Lightroom the exposure has been pushed up about 3-4 stops at least , meaning I then have to pull it down again and this can sometimes result in extra editing I could do with out. now I know its not the end of the world and is probably just a bug that I'm hoping will be sorted within Lightroom 4 but I just wondered if anyone else has had a similar problem, is it a bug or am I doing something wrong? (although I'm doing the same with Lighroom 4 as i used to do with LIghtroom 3.6 and that worked fine)
    Oh one more thing I should mention to get lightroom 4 and CS5 to work properly together I had to go into the Adobe Labs site and download the Camera RAW 6.7 software for CS5 so it could also be a bug here i guess.

    There have been several posts over on the Lightroom forum, and other non-Adobe forums also, about this issue: it seems that there's a bug in ACR 6.7RC which causes the image to be over-expose, compared with the setting applied using PV2012 in LR. I guess this is the kind of thing a Release Candidate is supposed to flag up! I was all set to upgrade my own ACR to ensure that PS would recognise my LR4 edits (I normally avoid RC versions and wait for the final), but all the reports of this problem have stopped me from doing so.
    In the meantime, best option so far as I'm aware is to process the image in LR (you get the option when you choose to edit in PS), meaning that it does all the rendering before passing it over to PS (otherwise, ACR handles the conversion of the raw file into TIFF). This does however mean that smart-objects and so on are temporarily out of the equation.
    I'm sure this will all be resolved pretty soon.
    Edit: in fact, one of the posts I mentioned is about ten posts down in this very forum: http://forums.adobe.com/thread/974963?tstart=0
    M

  • Image Capture + Rotate per EXIF + iPhoto = Bad

    My image intake workflow starts by importing with Graphic Converter, then renaming withi 'A Better Finder Rename' (rename images to a "datedescriptionimage#"), then review and major edits in GC then import into iPhoto.
    A recent release bug in GC, however, forced me to use OS X Image Capture. That's bad news with EXIF auto-rotate and iPhoto.
    Image Capture has had a bug for several years -- with my Canon camera it duplicates the EXIF orientation tag when it auto-rotates on import. This confuses iPhoto 5.04 -- iPhoto re-rotates portrait images a second time (interestingly the thumb nail is upright) and so the image ends up rotated 180 degrees. I was sure this bug must have been fixed in Tiger. Wrong.
    The malrotation is bad enough, but if one includes these double-tagged images in a batch that's mailed, Mail.App hangs until it finally times out with an AppleEvent error. It takes about 15 minutes to time out, during which time one watches the spinning pizza of death.
    I fixed my Image Capture mangled images using a Graphic Converter feature that was added a while back on my request. This feature fixes corrupt orientating tags and resets them to the current orientation (so first get the image oriented correctly, then run this).
    First I told iPhoto to restore all image to original. Then I did something quite risky (I have backups), I quite iPhoto, deleted the Library root .jpg cache files, then used GC to navigate the images I'd imported in their iPhoto directories. I located all the mangled images, reoriented them, and ran the EXIF repair utility. I then fired up iPhoto. (I tried removing the thumbnails, but iPhoto doesn't regenerate these as one would expect, instead it hangs and eventually shows blank images -- I think this is a cause of the broken thumbnails bug -- iPhoto should just regenerate them.) In cases where the thumbnails were mal-oriented I forced a thumbnail rebuild by editing the image then restoring to Original.
    After this fix I was able to mail the images without any trouble.
    iPhoto is in such bad shape I wonder if Apple shouldn't do rewrite from the ground up -- maybe an app that would only run in Tiger.

    Yes, I understand that (technical) distinction, but Image Capture has worked fine for me with earlier Canon cameras. If this was just support for iPhoto and Aperture it should be labeled as such, but the actual documentation for the 10.5.4 updates says "Includes additional RAW image support for several cameras" and the document describing Raw support says "Mac OS X Leopard provides system-level support for digital camera RAW formats from the following cameras.
    Products Affected
    Mac OS X 10.5
    Supported by Mac OS X 10.5.4 or later
    Canon EOS Digital Rebel XSi / Kiss Digital x2 / EOS 450D"
    The key language here is "system level support" - which I had assumed included importing the raw images. Image capture recognizes the XSi and moves the jpegs just fine - it's not clear to me why raw files would be any different.
    Anyway, as others in this thread have mentioned, just using a SDHC card reader works fine - and is faster. You just have to remove the card for the transfer.

  • Problems with Lightroom 5.2 and Olympus EM-1 RAW files?

    There have been reports on DPREVIEW of color problems using Lightroom 5.2 with RAW files from the Olympus OM-D EM-1 camera.  This causes  difficulty creating camera profiles, and creates a red shift in Images.  JPG images are unaffected.
    Anyone else seeing this?
    When may we look forward to LR 5.3, hopefully with a fix?
    Thanks............... Jack Winberg

    The read me file from Adobe indicate that LR 5.2 has "preliminary" support for the Olympus EM-1 raw files.
    I would make sure you keep your original raw files so they can be converted when the support is finalized. i.e. I would not convert to dng on import if that is your normal workflow.

  • Can you lock the background image orientation?

    Hello all
    Is there a way to lock the image orientation? When I turn the iPad, I want the apps to rotate, but I want the background image to stay portrait.
    If not, is there someplace i can suggest the feature?
    Thanks!

    No. It will orient along with your view. You can post feedback here: http://www.apple.com/feedback/

  • Indicated Image Orientation is Incorrect

    Hi all:
    Aperture 2.1.1 has begun to incorrectly tag images in the portrait orientation as “Landscape,” even though the images were correctly oriented as portrait during import and when viewing them in the Browser or Full screen mode. Doesn’t matter which camera (Nikon D80, Canon Powershot SD600 or Panasonic DMC-TZ1) I import from.
    Additionally, when viewing the incorrectly tagged images in the Finder window, set to column view, portrait-oriented images correctly oriented in Aperture are incorrectly oriented as landscape in the Finder window. They also open as landscape-oriented images in Preview. If I correctly rotate the image in Preview, then save the file, the Finder correctly displays the image, but the thumbnail in Aperture becomes corrupted: The image orientation in the Browser window remains as portrait, but the image preview has rotated 90 degrees.
    Can’t tell if this occurred since upgrading to Aperture 2.1.1 or Mac OS 10.5.5. Any ideas?

    Thanks for the tip. I did exactly what you suggested and ended up with over 2000 extra versions (sometimes up to six) of my files, some with strangely cropped previews, and files long since deleted. All these extra versions did not include any metadata I added (i.e., keywords, description, byline, city, state, etc.). In some cases the file name reverted back to the original one assigned by the camera(s).
    Meanwhile, rebuilding the database did not solve the incorrect orientation tag issue. All my images are referenced masters. No masters in my database are stored in the Aperture library.
    Thanks for any advice out there.

  • CameraRoll & CameraUI image orientation

    Hi,
    I am trying to read the Orientation tag in EXIF image data grabbed with CameraRoll or CameraRollUI using AIR 3.6 on iOS 6.1
    To achieve this, I use this library coded by Christian Cantrell :
    http://blogs.adobe.com/cantrell/archives/2011/10/parsing-exif-data-from-images-on-mobile-d evices.html
    Unfortunantly, it raises an error when I try to parse the Byterray containing the EXIF data :
    var exifInfo:ExifInfo = new ExifInfo( eb );
    TypeError: Error #1034: Type Coercion failed: cannot convert "<tags level="0th IFD TIFF Tags">
      <tag tag_name="Image width" field_name="ImageWidth" id="0x0100" compressed="J">
        <uncompressed chunky="M" planar="M" ycc="M" />
      ... INSERT BIG CHUNK OF XML HERE ...
    </tags>" to XML.
              at jp.shichiseki.exif::ExifInfo/readIFDs()[/Users/***/Google Drive/AS3/libs/jp/shichiseki/exif/ExifInfo.as:100]
              at jp.shichiseki.exif::ExifInfo()[/Users/***/Google Drive/AS3/libs/jp/shichiseki/exif/ExifInfo.as:63]
    It seems that Air can't cast the data into XML, but it's kind of crazy because I am able to see all the data in the error text (I purposedly truncated it here for not flooding this post) and it's XML valid. I had a look into the ExifInfo class, but it's hard to see where the error comes from.
    I really need to get access to these data, since it's the only way to determine image orientation in iOS. Or is there any native extention thaht I could use to achieve this ?
    Any advice will be welcome as I am stuck on a project for a client because of this.
    Thank you all !

    Hello Frog,
    a very (very) dirty solution could be :
    - use a try...catch...finally block to prevent the error raising
    - in the catch block, parse the error message to get your orientation value (String method, regexp...)
    [code]
    var myExifData:XML;
    try {
         // try to get the exif data
         var exifInfo:ExifInfo = new ExifInfo( eb );
    } catch(err:Error) {
         // fails, but maybe I can get the exif info in the error message...
         myExifData = parseExifError(err.message); // parse the error message to get your orientation info...
    } finally {
        do what I have to do with my image : rotate, scale....
    [/code]
    BTW, PhoneGap is perfectly able to get orientation of an image from the camera roll. So there IS a solution somewhere.
    Maybe you could try to make a native extension ? It's not so hard for little things like that...
    My 2 cents
    Nicolas

Maybe you are looking for