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.
Similar Messages
-
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.comThe 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. -
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/
-
SSRS indicator image display problem!!
Hello ALL;
I am having problem with displaying indicator image in DEV report manager. but same rdl works in QA environment. Both server has SP1 installed. Any Idea? Appreciate for your help. Thanks,Hi Techchi,
Based on the limited information, I cannot figure it out for this issue. As per my understanding, I think this issue can be caused by the browser that run the report manager. If you use IE explorer to render the report, I suggest that you can try to run
it in compatibility mode. If you are using another browser, I recommend that you should use IE explorer to render the report to check the issue again.
If this issue still exists, in order to solve the problem more efficiently, I need to clarify some information.
Are all reports with indicator image cannot render well in DEV report manager? Or just this one report?
What is the phenomenon about the indicator image display problem? Could you please post a screenshot about this?
It is benefit for us to do further analysis. Thank you for your understanding.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
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 -
Image orientation upon importing?
HI, I am using Photoshop elements 8. I was wondering if anybody knows of an option which controls image orientation during photo import? My situation; I have a large catalogue of photos and I have a canon 40d which I use for my serious photo work and I use an Olympus 6000 tough for play. Just recently when I went to upload my images off of the Olympus point and shoot all of my portrait image when imported are laying on their side or are presented in a landscape style. Now I have to go through manually rotate each image or select groups of images which is very time consuming. I don’t know what happen, elements use to rotate the images to their correct orientation during import. Does anybody know how to solve this?
Thanks,
jtThe photo you posted has the Orientation field in the EXIF metadata set to Horizontal (landscape):
Image Width : 3648
Image Height : 2736
Make : OLYMPUS IMAGING CORP.
Camera Model Name : uT6000,ST6000
Orientation : Horizontal (normal)
So that's why PSE isn't rotating it. Perhaps there's a setting in your camera you need to enable to have it record the Orientation properly, or perhaps the orientation sensor broke?
I used Exiftool to examine the EXIF metadata in the photo -- it is the most reliable way of examining all the photo metadata without the "helpful" interpretation and filtering that most programs (like PSE) provide. -
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?
ThanksI 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.
-
I held a facetime chat with a friend and was completely unable to cause both phones to properly display horizontal oriented images. Each person saw the other horizontal image as a belt-line horizontal you would see on a vertically oriented iPhone.
With both vertical-no problem.
The ads clearly show several examples of both ends of the conversation captured in horizontal orientation, but nothing we could do would convince the phones to behave this way.
Any clues?Found it!
After searching the iPhone docs several times with no success, an article on the internet pointed to the easy Image Orientation Lock/Unlock control.
For others with this "issue", it's found by double clicking the Home button on the iPhone, then flicking the line of apps to the right. Most/many of us are familiar with flicking this to the left to search back in our app usage, but when you flick to the right, there's a set of iconic controls, including the circle around a lock symbol.
All well now. Thanques to all. -
Camera image orientation on iOS
Hi,
Taking a picture using CamerUI on iOS (and on Android) may bring the image oriented in the wrong angle.
Reading the Exif on Android is fine and allows reorientation to the correct position, however this is not working on iOS.
Since I assume taking a picture using the camera is a core feature for many applications, I’d appreciate if someone who managed to solve it can post a solution here?
Thanks!I think this is it:
// ExifReader.as
// Reads and obtains JPG EXIF data.
// Project site: http://devstage.blogspot.com/2011/02/extract-jpg-exif-metadata-in.html
// SAMPLE USAGE:
// var reader:ExifReader = new ExifReader();
// reader.addEventListener(Event.COMPLETE, function (e:Event):void{
// trace(reader.getKeys());
// trace(reader.getValue("DateTime"));
// trace(reader.getThumbnailBitmapData().width +'x' + reader.getThumbnailBitmapData().height);
// reader.load(new URLRequest('myimage.jpg'), true);
package
import flash.display.Bitmap;
import flash.display.BitmapData;
import flash.display.Loader;
import flash.display.LoaderInfo;
import flash.events.Event;
import flash.events.EventDispatcher;
import flash.events.ProgressEvent;
import flash.net.URLRequest;
import flash.net.URLStream;
import flash.utils.ByteArray;
public class ExifReader extends EventDispatcher
private var m_loadThumbnail:Boolean = false;
private var m_urlStream:URLStream = null;
private var m_data:ByteArray = new ByteArray();
private var m_exif:Object = new Object;
private var m_exifKeys:Array = new Array();
private var m_intel:Boolean=true;
private var m_loc:uint=0;
private var m_thumbnailData:ByteArray = null;
private var m_thumbnailBitmapData:BitmapData=null;
private var DATASIZES:Object = new Object;
private var TAGS:Object = new Object;
public function load(urlReq:URLRequest, loadThumbnail:Boolean = false):void{
m_loadThumbnail = loadThumbnail;
m_urlStream = new URLStream();
m_urlStream.addEventListener( ProgressEvent.PROGRESS, dataHandler);
m_urlStream.load(urlReq);
public function getKeys():Array{
return m_exifKeys;
public function hasKey(key:String):Boolean{
return m_exif[key] != undefined;
public function getValue(key:String):Object{
if(m_exif[key] == undefined) return null;
return m_exif[key];
public function getThumbnailBitmapData():BitmapData{
return m_thumbnailBitmapData;
public function ExifReader(){
DATASIZES[1] = 1;
DATASIZES[2] = 1;
DATASIZES[3] = 2;
DATASIZES[4] = 4;
DATASIZES[5] = 8;
DATASIZES[6] = 1;
DATASIZES[7] = 1;
DATASIZES[8] = 2;
DATASIZES[9] = 4;
DATASIZES[10] = 8;
DATASIZES[11] = 4;
DATASIZES[12] = 8;
TAGS[0x010e] = 'ImageDescription';
TAGS[0x010f] = 'Make';
TAGS[0X0110] = 'Model';
TAGS[0x0112] = 'Orientation';
TAGS[0x011a] = 'XResolution';
TAGS[0x011b] = 'YResolution';
TAGS[0x0128] = 'ResolutionUnit';
TAGS[0x0131] = 'Software';
TAGS[0x0132] = 'DateTime';
TAGS[0x013e] = 'WhitePoint';
TAGS[0x013f] = 'PrimaryChromaticities';
TAGS[0x0221] = 'YCbCrCoefficients';
TAGS[0x0213] = 'YCbCrPositioning';
TAGS[0x0214] = 'ReferenceBlackWhite';
TAGS[0x8298] = 'Copyright';
TAGS[0x829a] = 'ExposureTime';
TAGS[0x829d] = 'FNumber';
TAGS[0x8822] = 'ExposureProgram';
TAGS[0x8827] = 'IsoSpeedRatings';
TAGS[0x9000] = 'ExifVersion';
TAGS[0x9003] = 'DateTimeOriginal';
TAGS[0x9004] = 'DateTimeDigitized';
TAGS[0x9101] = 'ComponentsConfiguration';
TAGS[0x9102] = 'CompressedBitsPerPixel';
TAGS[0x9201] = 'ShutterSpeedValue';
TAGS[0x9202] = 'ApertureValue';
TAGS[0x9203] = 'BrightnessValue';
TAGS[0x9204] = 'ExposureBiasValue';
TAGS[0x9205] = 'MaxApertureValue';
TAGS[0x9206] = 'SubjectDistance';
TAGS[0x9207] = 'MeteringMode';
TAGS[0x9208] = 'LightSource';
TAGS[0x9209] = 'Flash';
TAGS[0x920a] = 'FocalLength';
TAGS[0x927c] = 'MakerNote';
TAGS[0x9286] = 'UserComment';
TAGS[0x9290] = 'SubsecTime';
TAGS[0x9291] = 'SubsecTimeOriginal';
TAGS[0x9292] = 'SubsecTimeDigitized';
TAGS[0xa000] = 'FlashPixVersion';
TAGS[0xa001] = 'ColorSpace';
TAGS[0xa002] = 'ExifImageWidth';
TAGS[0xa003] = 'ExifImageHeight';
TAGS[0xa004] = 'RelatedSoundFile';
TAGS[0xa005] = 'ExifInteroperabilityOffset';
TAGS[0xa20e] = 'FocalPlaneXResolution';
TAGS[0xa20f] = 'FocalPlaneYResolution';
TAGS[0xa210] = 'FocalPlaneResolutionUnit';
TAGS[0xa215] = 'ExposureIndex';
TAGS[0xa217] = 'SensingMethod';
TAGS[0xa300] = 'FileSource';
TAGS[0xa301] = 'SceneType';
TAGS[0xa302] = 'CFAPattern';
//... add more if you like.
//See http://park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
private function dataHandler(e:ProgressEvent):void{
//EXIF data in top 64kb of data
if(m_urlStream.bytesAvailable >= 64*1024){
m_urlStream.readBytes(m_data, 0, m_urlStream.bytesAvailable);
m_urlStream.close();
processData();
private function processData():void{
var iter:int=0;
//confirm JPG type
if(!(m_data.readUnsignedByte()==0xff && m_data.readUnsignedByte()==0xd8))
return stop();
//Locate APP1 MARKER
var ff:uint=0;
var marker:uint=0;
for(iter=0;iter<5;++iter){ //cap iterations
ff = m_data.readUnsignedByte();
marker = m_data.readUnsignedByte();
var size:uint = (m_data.readUnsignedByte()<<8) + m_data.readUnsignedByte();
if(marker == 0x00e1) break;
else{
for(var x:int=0;x<size-2;++x) m_data.readUnsignedByte();
//Confirm APP1 MARKER
if(!(ff == 0x00ff && marker==0x00e1)) return stop();
//Confirm EXIF header
var i:uint;
var exifHeader:Array = [0x45,0x78,0x69,0x66,0x0,0x0];
for(i=0; i<6;i++) {if(exifHeader[i] != m_data.readByte()) return stop();}
//Read past TIFF header
m_intel = (m_data.readByte()!=0x4d);
m_data.readByte(); //redundant
for(i=0; i<6;i++) {m_data.readByte();} //read rest of TIFF header
//Read IFD data
m_loc = 8;
readIFD(0);
//Read thumbnail
if(m_thumbnailData){
var loader:Loader = new Loader();
loader.contentLoaderInfo.addEventListener(Event.COMPLETE, thumbnailLoaded);
loader.loadBytes(m_thumbnailData);
else stop();
//EXIF data is composed of 'IFD' fields. You have IFD0, which is the main picture data.
//IFD1 contains thumbnail data. There are also sub-IFDs inside IFDs, notably inside IFD0.
//The sub-IFDs will contain a lot of additional EXIF metadata.
//readIFD(int) will help read all of these such fields.
private function readIFD(ifd:int):void{
var iter:int=0;
var jumps:Array = new Array();
var subexifJump:uint=0;
var thumbnailAddress:uint=0;
var thumbnailSize:int=0;
// Read number of entries
var numEntries:uint;
if(m_intel) numEntries = m_data.readUnsignedByte() + (m_data.readUnsignedByte()<<8);
else numEntries = (m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte());
if(numEntries>100) numEntries=100; //cap entries
m_loc+=2;
for(iter=0; iter<numEntries;++iter){
//Read tag
var tag:uint;
if(m_intel) tag = (m_data.readUnsignedByte()) + (m_data.readUnsignedByte()<<8);
else tag = (m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte());
//read type
var type:uint;
if(m_intel) type = (m_data.readUnsignedByte()+(m_data.readUnsignedByte()<<8));
else type = (m_data.readUnsignedByte()<<8)+(m_data.readUnsignedByte()<<0);
//Read # of components
var comp:uint;
if(m_intel) comp = (m_data.readUnsignedByte()+(m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<24));
else comp = (m_data.readUnsignedByte()<<24)+(m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<0);
//Read data
var data:uint;
if(m_intel) data= m_data.readUnsignedByte()+(m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<24);
else data = (m_data.readUnsignedByte()<<24)+(m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<0);
m_loc+=12;
if(tag==0x0201) thumbnailAddress = data; //thumbnail address
if(tag==0x0202) thumbnailSize = data; //thumbnail size (in bytes)
if(TAGS[tag] != undefined){
//Determine data size
if(DATASIZES[type] * comp <= 4){
//data is contained within field
m_exif[TAGS[tag]] = data;
m_exifKeys.push(TAGS[tag]);
else{
//data is at an offset
var jumpT:Object = new Object();
jumpT.name = TAGS[tag];
jumpT.address=data;
jumpT.components = comp;
jumpT.type = type;
jumps.push(jumpT);
if(tag==0x8769){ // subexif tag
subexifJump = data;
var nextIFD:uint;
if(m_intel) {
nextIFD= m_data.readUnsignedByte()+(m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<24);
else {
nextIFD = (m_data.readUnsignedByte()<<24)+(m_data.readUnsignedByte()<<16) + (m_data.readUnsignedByte()<<8) + (m_data.readUnsignedByte()<<0);
m_loc+=4;
//commenting this out, as suggested in the comments.
//if(ifd==0) jumps = new Array();
for each(var jumpTarget:Object in jumps){
var jumpData:Object = null;
for(;m_loc<jumpTarget.address;++m_loc)m_data.readByte();
if(jumpTarget.type==5){
//unsigned rational
var numerator:uint = m_data.readInt();
var denominator:uint = m_data.readUnsignedInt();
m_loc+=8;
jumpData = numerator / denominator;
if(jumpTarget.type==2){
//string
var field:String='';
for(var compGather:int=0;compGather<jumpTarget.components;++compGather){
field += String.fromCharCode(m_data.readByte());
++m_loc;
if(jumpTarget.name=='DateTime' ||
jumpTarget.name=='DateTimeOriginal' ||
jumpTarget.name=='DateTimeDigitized'){
var array:Array = field.split(/[: ]/);
if(parseInt(array[0]) > 1990){
jumpData = new Date(parseInt(array[0]), parseInt(array[1])-1,
parseInt(array[2]), parseInt(array[3]),
parseInt(array[4]), parseInt(array[5]));
else jumpData = field;
m_exif[jumpTarget.name] = jumpData;
m_exifKeys.push(jumpTarget.name);
if(ifd==0 && subexifJump){
//jump to subexif area to obtain meta information
for(;m_loc<data;++m_loc) m_data.readByte();
readIFD(ifd);
if(ifd==1 && thumbnailAddress && m_loadThumbnail){
//jump to obtain thumbnail
for(;m_loc<thumbnailAddress;++m_loc) m_data.readByte();
m_thumbnailData = new ByteArray();
m_data.readBytes(m_thumbnailData, 0, thumbnailSize);
return;
// End-of-IFD
// read the next IFD
if(nextIFD){
for(;m_loc<nextIFD;++m_loc) m_data.readUnsignedByte();
if(ifd==0 && nextIFD)
readIFD(1);
private function thumbnailLoaded(e:Event):void{
m_thumbnailData.clear();
var loader:LoaderInfo = e.target as LoaderInfo;
var bitmap:Bitmap = loader.content as Bitmap;
if(bitmap != null){
m_thumbnailBitmapData = bitmap.bitmapData;
stop();
// Releases m_data and dispatches COMPLETE signal.
private function stop():void{
m_data=null;
dispatchEvent(new Event(Event.COMPLETE));
return; -
OCR in Java to set image orientation.
I want to set the orientation of an image after scanning. I thought the only way to do this is to use some type of OCR (Optical Character Recognition). I was curious if there are any small packages out there to do this (or another way to set image orientation. All the ones I have found are giant all-in-one imaging solutions.
ThanksI think that you need OCR package at javaocr.com
-
[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) -
Photoshop Elements 10 Slideshow Image Orientation
Hi,
I wonder if anyone can help me please? My OS is WIndows 7 Premium and I am using Photoshop Elements and Premier 10.
I have created a slideshow in Photoshop Elements and saved this to DVD (PAL as I am in the UK). All images are the correct orientation and display correctly when on my PC. However, once saved on DVD and played through my DVD player to the TV there are a number of images being displayed in the incorrect orientation.
Does anyone know how to correct this please?
Thanks.Hi everyone,
I agree with suspicion that Premiere Elements is probably making the mistake of displaying the photos incorrectly. However, I suspect that avoiding the problem by actions in the Organizer may be the most practical alternative.
Ken, can you help with some details ?
1 - I am not at a computer where I can verify this statement -- but I think that in earlier versions of the Organizer, there is an Organizer Preference which controls how the photo is rotated (by orientation indicator only) or by actually rotating the photo. And by orientation indicator only is the default. Does that Preference still exist in version 10 ? If yes, then I think rotating multiple photos at the same time within the Organizer would probably be a circumvention of the problem that shows on the photo orientation on the DVD.
2 -- My expereince and what I have seen reported on these forums is that the Elements Organizer does recognize an Orientation indicator which has been set in a photo file by the camera. So portrait mode photos which come from the camera with this Orientation indicator usually (maybe always) display correctly within the organizer.
Therefore since this thread says "All images are the correct orientation and display correctly when on my PC", I suspect that the person originating this thread did not make any orientation correction.
3-- The type of approach that I believe some people have successfully used, is to first set the Organizer preference to actually rotate the photo file: then do
-- one rotate if necessary to have the photo display correctly in the Organizer
-- if the portrait photo initially looked OK in the Organizer, then 2 rotates would be done : first would set the photo on its side (temporarily) and then the second rotate would be back in the other direction. These actions can be done for multiple selected photos.
4-- OR as an alternative to 3 (above), if the slide show has already been constructed within the Organizer Slide Show Editor, then there are methods to initiate an edit of a specific photo file which transfers to the PSE editor and can take the action of changing orientation in the PSE editor.,
FYi - Mt Ventoux,
Don't be discouraged by all the details I am discussing while we explore the best solution for you. -
IPhoto causes portrait format images to sort incorrectly in iOS
After importing photos into an Event in iPhoto, then on quitting iPhoto, the portrait format photos within that Event have their modification date/time changed from the creation date/time (which is what it should be) to the date/time that the photo was imported into iPhoto. This causes the Photos App under iOS 6.0.1 and above to sort the photos within that Event so that all the landscape format images are displayed ahead of all the portrait format images. This is because the iOS Photos App incorrectly sorts on modification date/time rather than creation date/time.
Steps to Reproduce: Take a number of photos with a camera that records orientation information in the EXIF data (e.g. Nikon DSLR or similar). Ensure there is a mixed assortment of both landscape and portrait format photos. Import those photos into an Event in iPhoto (with Sort by Date selected). You will see in iPhoto that the images are sorted correctly in chronological order. Examine the Info (CMD-I) on both types of image, and you will see that modification date/time is the same as creation date/time for every image (as it should be). Now quit iPhoto, and relaunch it. In iPhoto, look again at photo Info (CMD-I) of photos in that Event, and you will see that all of the portrait format images have now had their modification date/time changed to the date/time of import into the iPhoto library. Using iTunes, sync that Event with an iOS device (e.g. iPad). On the iOS device, look at the Event in the Photos App, and you will see it is sorted incorrectly, with all the landscape images first, followed by all the portrait images.Sigh. I know I'm being troll bait, and I really don't believe you can be so obtuse, but I'll have one last stab, just in case you're genuine.
Point 1. Nothing on your Mac needs iPhoto. Every application on your Mac can deal with photos as files, without intervention or advice from iPhoto. Even the Finder gets it right, orienting the images correctly from EXIF information. Even Quicklook gets it right. You can remove iPhoto from your Mac and everything will continue to display images correctly. There is no need for iPhoto to change mod date in the EXIF data on a photograph inside the iPhoto library, simply because the camera was oriented vertically instead of horizontally when the picture was taken. It helps no-one and the only thing affected, adversely, is the Photos App on iOS.
Point 2. If it were really the warped intention of iPhoto developers that vertically oriented photos should be considered to have been modified when they were imported into the iPhoto library, then iPhoto should treat them the same as it treats other photos modified in iPhoto. It should put a copy of the original file, as modified, into the Modified section of its library, and it should leave the original in the Originals section. And it should offer a 'Revert to Original' option. It does not do that for these vertical images. There is no copy in the Modified part of the library. And 'Revert to Original' is greyed out, unobtainable.
Point 3. It is only in the past 5 or 6 months that iPhoto began clobbering the modification date of vertical images. For the previous 9 years that I've been using iPhoto and the 18,000 images in my iPhoto library, everything had been fine. Only the vertically oriented photos imported into iPhoto since version 9.3.2 have had their mod date trashed. This is a pernicious and no doubt unintentional bug, that fortunately impacts nothing else on the Mac (and assists nothing else either). It does affect the Photos App on iOS. It might affect the iPhoto App on iOS too. I don't know, as I don't have it.
Point 4. The iOS Photos App is also incorrect in sorting on mod date instead of creation date. This began with iOS 6.0.1. I have also submitted a bug report to Apple on that issue. -
Image Orientation Reset Accessing External HDD Images
I'm using Lightroom 2.1 on Windows XP. Ever since the later LR 1.x versions, I've been running into this problem.
I initially edit my images on my internal HDD, then I move them to my external once I'm done with them. The problem occurs when I go to the images (now on the external) in LR and all the vertical/portrait images (thumbs) revert to the horizontal/landscape orientation. When in LR and I go to the folder where they reside, the thumbs initially show in their proper rotated (vert/portrait) orientation, but then they automatically get turned back around to the incorrect initial/landscape orientation. When dealing with 10's of thousands of images, this grows VERY frustrating.
Is this a common bug?
Thank you.
SethWhen I move the files to the external, I copy the folder in Explorer and paste it into the appropriate folder on the external. Yes, I then use 'locate missing folder' in LR. So therefore all the metadata and settings stay associated with the files. The files are mostly DNG, along with some JPEG and TIF.
Strangely enough, the rotation setting is the only one that gets reverted to the original setting. I make other changes to the files as well (saturation, clarity, tone, vignette, etc), and all of those hold their changed value correctly (as well as caption/title/location and other metadata). And since all these develop settings (incl rotation as I am led to believe) are saved in the LR '.lrcat' file (I DO NOT use .xmp sidecar files), it strikes me as very strange that only the rotation is reset.
The only files where the rotation is not reset are the TIF files that I have created by opening a DNG in PS to make other corrections. The reason being that the rotation setting is saved in the TIF file, not in the .lrcat settings file.
The reason I don't auto-rotate in the 5D is b/c I'd rather have to turn the camera, but see the files full screen on the camera. Would rather not change this if possible... hoping I can discover the issue in LR first. Otherwise maybe I'll have to give in, but not just ready yet... -
Safari gets stuck on loading indicator/image placeholder when trying to load "some" images
Ok, so Safari and Firefox for Mac both have this problem.
When I go to some websites, I get an endless loading icon (place holder) and nothing appears.
However on Windows/Internet Explorer (using parralels) the page loads fine.
This happens on Ram Trucks http://www.ramtrucks.com/en/2012/ram_1500/
and also on Yelp http://www.yelp.com/biz_photos/5DJS-EaAN51xbEwqW7Jk6Q?select=YosUpE8E0BgZSEYbWze IKg
Since it happens on Both Safari and Firefox for Mac, Im thinking something is wrong with my MAC Operating System.
Here is what I see when I go to those sites.
YELP = i49.tinypic.com/153pslv.jpg RAM TRUCKS = i46.tinypic.com/2q3cd9t.png
Those are just two examples of sites, but it happens to other sites.. and its not all images.. it seems like its just those websites that have special/custom loading indicators when you click on photos. I think its some special HTML or scripting that the sites use to bring up the images thats causing the problem. Since its only those sites that have an animated gif as a waiting/loading indicator for the image your trying to view.
Anyone have any ideas? This was working fine, but my hard drive crashed and I had to reinstall OSX. Thats when i started experiencing this. I have already done all the MAC updates.I already tried taking them off the SD card directly from the Mac card reader, it detects it in image capture and in iphoto, but the same thing happens, just a loading screen as pictured above.
Maybe you are looking for
-
I am trying to import cr2files from the camera into lightroom 5 and keep getting an error message saying Lightroom can not read the files and therefore will not import them. Has anyone had a similar problem-.thanks
-
T60 14" SCREEN HAS DEVELOPED A FADED BAR AT THE BOTTOM OF THE SCREEN.
Hello all, I have a T60 14" which has developed a constant faded bar at the bottom. the bar is about 10cm in height and makes the screen look like it has two contrast settings. Upper screen is normal and lower faded area looks in high contrast. The
-
Is there any way to crop part of a screen shot and paste into Pages?
Instead of importing an entire photo into Pages, I am trying to: -take a screen shot of iPad documentation - open in photo roll and crop a section out of it - paste into Pages Is there an App that might crop and paste into Pages? Thanks for any help.
-
Itunes 7 saga and getting back to 6.0.5 (uninstalling version 7)
Hi, so I've got my ipod functioning again having reset a million times, but daren't plug it into my mac running itunes v7 for fear it will screw it up again!!! Anyone have any ideas how to get back to v6.0.5 in Tiger? I'll have to do that so I can pl
-
HHi all, I need to know where the reason code field can be found while creating an iexpense report in Oracle. Allso if there is any lookup involved and where that lookup can be found . Many thanks in advance