Color changes in photos after exporting from aperture and viewed on another computer

Help! I import raw images, I'm Proofing with sRGB IEC61966-2.1 and my colorsync profile in my export settings are also set with sRGB IEC61966-2.1. When i export to my computer the pictures look exactly as they should be, but when i email them and see them on other computers the colors are not at all what i be;ieved to have been exported! Im a newbie to the digital world...

What is your Mac's display color setting?

Similar Messages

Can a photo be exported from aperture in CMYK profile

Can a photo be exported from aperture in CMYK profileas TIFF jpeg PSD etc .?

Yes, in the export dialogue panel pick a TIFF or PSD setting, and then set the colorsync profile selector to a cmyk-profile,
You need to have installed cmyk-profiles, however;
most of my colorsync profiles were installed by photoshop.
You will find the cmyk-profiles in the system library:
/Library/ColorSync/Profiles/
Regards
Léonie

Unlogged Missing Photos After Import From Aperture

Hi!
I have just made the switch from Aperture to Lightroom, and have use the 1.1 version of the Aperture import plugin.
In my Aperture Library I have, according to the Library -> Photos: 11105 Photos, however after importing to Lightroom, I have only 10967 photos. I have checked the import log, and there were 4 items which failed to import - 3 were .mpo files (panoramas from an xPeria) and 1 was a .gif file. This leaves a deficit of 133 photos that I can't account for.
Is there any way to compare the aperture library to the lightroom library to see what is missing?

*WARNING* Once agin, this is a VERY long post! And this contains not only SQL, but heaps of command line fun!
TLDR Summary: Aperture is storing duplicates on disk (and referencing them in the DB) but hiding them in the GUI. Exactly how it does this, I'm not sure yet. And how to clean it up, I'm not sure either. But if you would like to know how I proved it, read on!
An update on handling metadata exported from Aperture. Once you have a file, if you try to view it in the terminal, perhaps like this:
$ less ApertureMetadataExtendedExport.txt
"ApertureMetadataExtendedExport.txt" may be a binary file. See it anyway?
you will get that error. Turns out I was wrong, it's not (only?) due to the size of the file / line length; it's actually the file type Aperture creates:
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: Little-endian UTF-16 Unicode text, with very long lines
The key bit being "Little-endian UTF-16", that is what is causing the shell to think it's binary. The little endian is not surprising, after all it's an X86_64 platform. The UTF-16 though is not able to be handled by the shell. So it has to be converted. There are command line utils, but Text Wrangler does the job nicely.
After conversion (to Unicode UTF-8):
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: ASCII text, with very long lines
and
$ less ApertureMetadataExtendedExport.txt
Version Name    Title   Urgency Categories      Suppl. Categories       Keywords        Instructions    Date Created    Contact Creator Contact Job Title       City    State/Province Country Job Identifier Headline        Provider        Source Copyright Notice        Caption Caption Writer Rating IPTC Subject Code       Usage Terms     Intellectual Genre      IPTC Scene      Location        ISO Country Code        Contact Address Contact City    Contact State/Providence        Contact Postal Code     Contact Country Contact Phone   Contact Email   Contact Website Label   Latitude        Longitude       Altitude        AltitudeRef
So, there you have it! That's what you have access to when exporting the metadata. Helpful? Well, at first glance I didn't think so - as the "Version Name" field is just "IMG_2104", no extension, no path etc. So if we have multiple images called "IMG_2104" we can't tell them apart (unless you have a few other fields to look at - and even then just comparing to the File System entries wouldn't be possible). But! In my last post, I mentioned that the Aperture SQLite DB (Library.apdb, the RKMasters table in particular) contained 11130 entries, and if you looked at the Schema, you would have noticed that there was a column called "originalVersionName" which should match! So, in theory, I can now create a small script to compare metadata with database and find my missing 25 files!
First of all, I need to add that, when exporting metadata in Aperture, you need to select all the photos! ... and it will take some time! In my case TextWrangler managed to handle the 11108 line file without any problems. And even better, after converting, I was able to view the file with less. This is a BIG step on my last attempt.
At this point it is worth pointing out that the file is tab-delimited (csv would be easier, of course) but we should be able to work with it anyway.
To extract the version name (first column) we can use awk:
$ cat ApertureMetadataExtendedExport.txt | awk -F'\t' '{print $1}' > ApertureMetadataVersionNames.txt
and we can compare the line counts of both input and output to ensure we got everything:
$ wc -l ApertureMetadataExtendedExport.txt
   11106 ApertureMetadataExtendedExport.txt
$ wc -l ApertureMetadataVersionNames.txt
   11106 ApertureMetadataVersionNames.txt
So far, so good! You might have noticed that the line count is 11106, not 11105, the input file has the header as I printed earlier. So we need to remove the first line. I just use vi for that.
Lastly, the file needs to be sorted, so we can ensure we are looking in the same order when comparing the metadata version names with the DB version names.
$ cat ApertureMetadataVersionNames.txt | sort > ApertureMetadataVersionNamesSorted.txt
To get the Version Names from the DB, fire up sqlite3:
$ sqlite3 Library.apdb
sqlite> .output ApertureDBMasterVersionNames.txt
sqlite> select originalVersionName from RKMaster;
sqlite> .exit
Checking the line count in the DB Output:
$ wc -l ApertureDBMasterVersionNames.txt
   11130 ApertureDBMasterVersionNames.txt
Brilliant! 11130 lines as expected. Then sort as we did before:
$ cat ApertureDBMasterVersionNames.txt | sort > ApertureDBMasterVersionNamesSorted.txt
So, now, in theory, running a diff on both files, should reveal the 25 missing files.... I must admit, I'm rather excited at this point!
$ diff ApertureDBMasterVersionNamesSorted.txt ApertureMetadataVersionNamesSorted.txt
IT WORKED! The output is a list of changes you need to make to the second input file to make it look the same as the first. Essentially, this will (in my case) show the Version Names that are missing in Aperture that are present on the File System.
So, a line like this:
1280,1281d1279
< IMG_0144
< IMG_0144
basically just means, that there are IMG_0144 appears twice more in the DB than in the Metadata. Note: this is specific for the way I ordered the input files to diff; although you will get the same basic output if you reversed the input files to diff, the interpretation is obviously reversed) as shown here: (note in the first output, we have 'd' for deleted, and in the second output it's 'a' for added)
1279a1280,1281
> IMG_0144
> IMG_0144
In anycase, looking through my output and counting, I indeed have 25 images to investigate. The problem here is we just have a version name, fortunately in my output, most are unique with just a couple of duplicates. This leads me to believe that my "missing" files are actually Aperture handling duplicates (though why it's hiding them I'm not sure). I could, in my DB dump look at the path etc as well and that might help, but as it's just 25 cases, I will instead get a FS dump, and grep for the version name. This will give me all the files on the FS that match. I can then look at each and see what's happening.
Dumping a list of master files from the FS: (execute from within the Masters directory of your Aperture library)
$ find . -type f > ApertureFSMasters.txt
This will be a list including path (relative to Master) which is exactly what we want. Then grep for each version name. For example:
$ grep IMG_0144 ApertureFSMasters.txt
./2014/04/11/20140411-222634/IMG_0144.JPG
./2014/04/23/20140423-070845/IMG_0144 (1).jpg
./2014/04/23/20140423-070845/IMG_0144.jpg
./2014/06/28/20140628-215220/IMG_0144.JPG
Here is a solid bit of information! On the FS i have 4 files called IMG_0144, yet if I look in the GUI (or metadata dump) I only have 2.
$ grep IMG_0144 ApertureMetadataVersionNamesSorted.txt
IMG_0144
IMG_0144
So, there is two files already!
The path preceding the image in the FS dump, is the date of import. So I can see that two were imported at the same time, and two separately. The two that show up in the GUI have import sessions of 2014-06-28 @ 09:52:20 PM and 2014-04-11 @ 10:26:34 PM. That means that the first and last are the two files that show in the GUI, the middle two do not.... Why are they not in the GUI (yet are in the DB) and why do they have the exact same import date/time? I have no answer to that yet!
I used open <filename> from the terminal prompt to view each file, and 3 out of my 4 are identical, and the fourth different.
So, lastly, with a little command line fu, we can make a useful script to tell us what we want to know:
#! /bin/bash
grep $1 ApertureFSMasters.txt | sed 's|\.|Masters|' | awk '{print "<full path to Aperture Library folder>"$0}' | \
while read line; do
openssl sha1 "$line"
done
replace the <full path to Aperture Library folder> with the full path to you Aperture Library Folder, perhaps /volumes/some_disk_name/some_username/Pictures/.... etc. Then chmod 755 the script, and execute ./<scriptname> <version name> so something like
$ ./calculateSHA.sh IMG_0144
What we're doing here is taking in the version name we want to find (for example IMG_0144), and we are looking for it in the FS dump list. Remember that file contains image files relative to the Aperture Library Master path, which look something like "./YYYY/MM/DD/YYYYMMDD-HHMMSS/<FILENAME>" - we use sed to replace the "./" part with "Masters". Then we pipe it to awk, and insert the full path to aperture before the file name, the end result is a line which contains the absolute path to an image. There are several other ways to solve this, such as generating the FS dump from the root dir. You could also combine the awk into the sed (or the sed into the awk).. but this works. Each line is then passed, one at a time, to the openssl program to calculate the sha-1 checksum for that image. If a SHA-1 matches, then those files are identical (yes, there is a small chance of a collision in SHA-1, but it's unlikely!).
So, at the end of all this, you can see exactly whats going on. And in my case, Aperture is storing duplicates on disk, and not showing them in the GUI. To be honest, I don't actually know how to clean this up now! So if anyone has any ideas. Please let me know I can't just delete the files on disk, as they are referenced in the DB. I guess it doesn't make too much difference, but my personality requires me to clean this up (at the very least to provide closure on this thread).
The final point to make here is that, since Lightroom also has 11126 images (11130 less 4 non-compatible files). Then it has taken all the duplicates in the import.
Well, that was a fun journey, and I learned a lot about Aperture in the process. And yes, I know this is a Lightroom forum and maybe this info would be better on the Aperture forum, I will probably update it there too. But there is some tie back to the Lightroom importer to let people know whats happening internally. (I guess I should update my earlier post, where I assumed the Lightroom Aperture import plugin was using the FS only, it *could* be using the DB as well (and probably is, so it can get more metadata))
UPDATE: I jumped the gun a bit here, and based my conclusion on limited data. I have finished calculating the SHA-1 for all my missing versions. As well as comparing the counts in the GUI, to the counts in the FS. For the most part, where the GUI count is lower than the FS count, there is a clear duplicate (two files with the same SHA-1). However I have a few cases, where the FS count is higher, and all the images on disk have different SHA-1's! Picking one at random from my list; I have 3 images in the GUI called IMG_0843. On disk I have 4 files all with different SHA-1's. Viewing the actual images, 2 look the same, and the other 2 are different. So that matches 3 "unique" images.
Using Preview to inspect the exif data for the images which look the same:
image 1:
Pixel X Dimension: 1 536
Pixel Y Dimension: 2 048
image 2:
Pixel X Dimension: 3 264
Pixel Y Dimension: 2 448
(image 2 also has an extra Regions dictionary in the exit)
So! These two images are not identical (we knew that from the SHA-1), but they are similar (content is the same - resolution is the same) yet Aperture is treating these as duplicates it seems.. that's not good! does this mean that if I resize an image for the web, and keep both, that Aperture won't show me both? (at least it keeps both on disk though, I guess...)
The resolution of image 1, is suspiciously like the resolutions that were uploaded to (the original version of) iCloud Photos on the iPhone (one of the reasons I never used it). And indeed, the photo I chose at random here, is one that I have in an iCloud stored album (I have created a screensaver synced to iCloud, to use on my various Mac's and AppleTVs). Examining the data for the cloud version of the image, shows the resolution to be 1536x2048. The screensaver contains 22 images - I theorised earlier that these might be the missing images, perhaps I was right after all? Yet another avenue to explore.
Ok. I dumped the screensaver metadata, converted it to UTF-8, grabbed the version names, and sorted them (just like before). Then compared them to the output of the diff command. Yep! the 22 screensaver images match to 22 / 25 missing images. The other 3, appear to be exact duplicates (same SHA-1) of images already in the library. That almost solves it! So then, can I conclude that Lightroom has imported my iCloud Screensaver as normal photos of lower res? In which case, it would likely do it for any shared photo source in Aperture, and perhaps it would be wise to turn that feature off before importing to Lightroom?

Adobe RGB changed to sRGB after export in Aperture 2.1.1 Why?

I have tried taken pictures with color profile Adobe RGB, but all images exported via Aperture 2.1.1 shows up as sRGB in the EXIF. Does Aperture convert the color profile somewhere?

When exporting, you get to choose your color profile. The export pre-set you chose uses sRGB. So, after choosing your export preset, click on the preset drop-down menu again and go all the way down to "Edit". This will allow you to change the profile to Adobe RGB from sRGB. That setting now will always be used for that pre-set. If needed, you can create other pre-sets by clicking the plus symbol in the bottom left corner of that edit dialog box.

Since the recent upgrade all my photos have gone from Aperture and i cannot open any backed up Aperture files please help.

Since the recent upgrade i have lost my Aperture libaray and cannot open the old one message reads you cannot use this version of the application Aperture original with this version of OS X you have Aperture original 3.2.4.
How do i get my photos back please.

Aperture 3.2.4 will not work on Mavericks.
You can do as I did, either do a web search for Aperture updates to your current version of Aperture to update to Aperture 3.4.5 OR just simply upgrade to latest version of Aperure 3.5 ( from the Mac App Store) that is fully 64 bit compliant for OS X Mavericks. As long as you have registered your previous version of Aperture, the new 64 bit version will be a free upgrade.
Be advised that if you just upgrade to the latest version of Aperture, it will update your Photos Library, as well.
When this happens, your old version of Aperture on older versions of OS X will no longer work with the new, updated Photos Library.
If you still want to be able to access your Photos Library with an older version of Aperture and older OS X version, you need to make a copy of your current Photos library.
Make a copy of your current Photos Library and put it into a folder called something like old Photos Library so you still have an older version you can still access if you need to.

Indesign CS4 button flashes after exported to PDF and viewed in Acrobat Reader/Professional X

Hey everyone,
Greetings!
I've encountered this odd problem when preparing my portfolio.
I've created some 40 buttons in InDesign CS4 (all according to the official tutorial) to Show/Hide Fields (specificly images), and navigate through the pages.
The buttons all have their own Normal and Rollover states, but no Click states.
After exporting the file to PDF, I tested the buttons in Acrobat Reader 9 and Acrobat Pro 9, and both the actions and the states worked fine.
BUT that's not the case with Acrobat Reader X or Acrobat Pro X.
The actions are still there, showing the images and navigating, but the states are not!
The buttons' rollover states just flashes when the mouse hover above them, and even in Normal state, they kept *blinking* randomly.
Frustrated for a week.
PS. I suspected and used a Indesign file with only one simple button to rule out the following:
1. Overlapping buttons
2. Slow processing due to large image size
3. Mishandling of transparency
At this moment I'm pretty sure it's an Acrobat thing...Help!

Thanks Dave! I was in the middle of writing this when your post came in:
Not sure if this will help anyone, but I changed the button fill color to white and it seemed to fix the flicker. I exported each state from indesign as a PDF and recreated the button from scratch. This still had the flicker. I'm guessing something strange is happening with the transparancy of the states.
Glad to hear it's fixed!

How do I export from Aperture to iPhoto?

Ok, I am very new at all of this, and find it quite confusing.
I took several hundred raw photos and imported them into Aperture. I believe they are all in a 'project', the yellow box looking icon? Then, I created numerous folders inside this project, in which I carefully sorted all my photos by subject - about 18 folders. Then, I worked with each folder, fine tuning each image, and adding exif metadata, and rating each image. So far so good.
Now, I want to bring all this images (as full size jpegs) into iPhoto.. this is where I am getting bogged down. There is an export function in Aperture, and an import function in iPhoto: which do I use?
I have been experimenting with various scenarios, but nothing seems to be working the way I want.. specifically, to have all my images in iPhoto - IN THE SAME STRUCTURE as I have in Aperture. When I did manage to bring them into iPhoto, they all came over in one big massive event, leaving all my sorting and ratings behind. This can't be right.. I don't want to resort them all again, moving them into the appropriate folders. And I don't want to have to re-enter the exif metadata and ratings again.
Can someone please help me with this?

Export from Aperture and then import to iPhoto.
Alternatively, you can share your Previews with iPhoto but that gets only the Preview.
FWIW: your workflow makes no sense. It's like writing your novel in TextEdit then opening it in Word to Spell Check and then copying it back to TextEdit. Why not just write your novel in Word? Aperture is not an editor. It's a complete replacement for iPhoto. It will do everything that iPhoto does, and then more. Or if you want to stick with iPhoto, get an editor and use it as an external editor in that.
Regards
TD

PDFs dull in Acrobat after exporting from Indesign - again

Hi folks,
I am aware of a previous post which discussed this issue which was apparently resolved, but it appears to have reared its ugly head again. The problem - since updrading to Mavericks and the Creative Cloud, pdfs in Acrobat are very dull after export from Indesign and it is not a transparency blend or Indesign issue. I understand Adobe blamed Apple for not updating their colour management software and the reply from Adobe was:
"We have found the root cause of this issue and are in process of providing a fix. Once this is done, we will test it to make sure that it works as expected and will release an update patch for all our users."
I am running the latest version or everything but it appears to still be a problem. I have also uninstalled Acobat XI and tried earlier versions without success. I have a print job to send off tomorrow and I am very nervous about how this will print.

Sorry about that, I apparently forgot to attach the file; have done so now.
The method I'm using for creating outlines is simply to use the "Create Outlines" command under the Type menu within InDesign. Then I create my PDF files by using the Export command under the File menu and choosing the PDF/X1a option. 99% of the time I get perfect results, it's only when I try to make outline type that I encounter this problem. You'll clearly see the artifacts in question in the example attached.
I don't know whether or not the press would have printed these artifacts, as you suggest, since no printer has been willing to execute a file that shows any anomaly in the proof process. I can't say that I blame them.
Hopefully you will see what I'm talking about and can recommend a solution, though I like your idea of simply giving them a properly executed file and then telling them to get a life. It hasn't worked so far, as I unfortunately deal with a lot of Neanderthals around here, but I suppose it's worth putting forth again the next time this issue arises. It will.
By the way, no print house of my choosing is this far behind the curve, if at all. These cavemen are always printers who have long-standing relationships with my clients, and for whatever reason (generally lowest cost I'm sure), the clients think they hung the moon. We, of course, no otherwise, but it does it profit a designer to tell his client he or she is crazy for using a printer who is a decade behind the technology curve.
We cowboy up and seek solutions, eh?

Export from Aperture to edit in Windows Live Photo Gallery

Hi.
I'm hoping to work collaboratively with a colleague, in a scenario where I take & edit photos, then pass them over for a possible final touch up before being forwarded to clients.
I use Mac OSX 10.6 and Aperture. He uses Windows Vista and Windows Live Photo Gallery.
The problem we've come up against is this: he is unable to edit the image I've exported from Aperture. I'm exporting as .JPG, and he's able to read them ok - i.e. load it into Windows Live Photo Gallery, but not alter the image.
Does anyone have a similar workflow, exporting from Aperture, then editing in Windows Live Photo Gallery?
Thanks in advance,
PB

Hi Frank.
Thanks for the response.
Agreed, the pertinent question is why can't my colleague edit the JPG exported by Aperture. It's probably also worth pointing out, the same problem occurs with JPGs exported from iPhoto.
The Windows software usually plays nicely with JPGs by all acounts, just not the ones I send - which I do via eMail or my public space on Mobile Me incidently.
So, another key question is: all settings being equal (color profile, quality, etc.) are the JPGs as produced by iPhoto and Aperture indistinguishable from those produced by other apps on other platforms - i.e. does the use of JPG enforce a common standard?
If that is the case, I suspect ours might be a permissions issue.
According to the Microsoft support page on editing in Windows Live Photo Gallery, the inability to edit a picture is commonly caused by unsupported file type, or read-only attribute set on the file.
Unfortunately, he and I are not in the same place, and he's not particularly au-fait with this type of problem solving. Hence, before involving him, I'd like to know:
1. it's possible (i.e. someone else does it), and,
2. what's involved (at my end and/or his).
Thanks again,
PB

Photos in FCE; export from Aperture in target size?

hi all.
I'm planning to place photos from Aperture into my FCE project, with the photos fading from one to the next. they won't be full screen, less than half. to get the best final quality, do I need to sharpen and export from Aperture so that the photos are placed within the FCE project at 100% without scaling?
cheers,
Gregory

Hi Frank.
Thanks for the response.
Agreed, the pertinent question is why can't my colleague edit the JPG exported by Aperture. It's probably also worth pointing out, the same problem occurs with JPGs exported from iPhoto.
The Windows software usually plays nicely with JPGs by all acounts, just not the ones I send - which I do via eMail or my public space on Mobile Me incidently.
So, another key question is: all settings being equal (color profile, quality, etc.) are the JPGs as produced by iPhoto and Aperture indistinguishable from those produced by other apps on other platforms - i.e. does the use of JPG enforce a common standard?
If that is the case, I suspect ours might be a permissions issue.
According to the Microsoft support page on editing in Windows Live Photo Gallery, the inability to edit a picture is commonly caused by unsupported file type, or read-only attribute set on the file.
Unfortunately, he and I are not in the same place, and he's not particularly au-fait with this type of problem solving. Hence, before involving him, I'd like to know:
1. it's possible (i.e. someone else does it), and,
2. what's involved (at my end and/or his).
Thanks again,
PB

HT204655 How to have a unified Photos Library after migrated from iPhoto and Aperture?

The "HT204655: Get started with Photos for OS X" do not help. If you have previously used iPhoto and Aperture, when you "migrate" the iPhoto, then follow the steps to "migrate" the Aperture library, you end up with 5 files in your Pictures folder: Photos Library (from iPhoto), Photos Library 2(from Aperture), iPhoto Library (Not sure if can be deleted or not - of course no), Aperture Library (for some reason blank), Aperture Library 2 (Created by Photos?).
So, looks like a mess and no easy way to make a clean migration.
I've a hope that exists a solution to have a single Photos Library with the merged iPhoto and Aperture contents, like a real migration.
If I export everything (From iPhoto and Aperture) then import in the Photos in a single Library should work, but will lose all the organization, faces, etc...

You could merge libraries with iPhoto Library Manager, but I never tried this for merging Aperture 3 libraries with iPhoto 8.
Are you planning to keep all your photos in iCloud? Then consider to merge them in iCloud, but it will take a long time.
Are you using iCloud Photo Library (Beta) and have enough iCloud storage for the merged library?
Wait, till your current Photos Library has been completely uploaded to iCloud.
Then quit Photos, and launch it again, while holding down the alt/options key. Select the old iPhoto lIbrary.
When the upgrade of the old library has been finished, make this library the System Photos library (in the Photos Preferences > General).
Enable again iCloud Photo Library (Beta) in the Photos > iCloud preferences.
Now Photos will upload the new library to iCloud as well and create a merged library in iCloud. After this merged library synced with your Mac, you will have a merged Photos library.

How do I make space on iTunes for photos after exporting photos from iPhoto on ipad.

How do I make space on iTunes for photos after exporting photos from iPhoto on iPad?

How do I make space on iTunes for photos after exporting them to my PC from iPhoto on my iPad? I received an error message saying I had no more space available to export.

Some Photos are blank after conversion from Aperture

Library contains 45K photos .. migrated from Aperture. For some reason a large number of the photos have meta data but are blank. Where have they gone?

Partial CLUE ..
Two photos .. appear to be dupes .. but the case of the file NAME is different. The UPPERCASE JPG is blank .. the lowercase .jpg is not.
Ok -- Apple Engineers .. here's a start .. go fix.

Sharpness APERTURE vs iPHOTO~file exported from Aperture worse than iPhoto

HEY.
i'm recently using Aperture for my Photo Editing work.I found that everything Good and Perfect after fine tune and preview in the Window of Aperture...while Export it to the Jpeg (originaly image import from jpeg file) I found it's a bit loose from what i see in the Window Aperture...means,Loose the Sharpness...whole image getting un-sharp or s'ld i say added gausion blur of feel??
Once i import it(the one exported from Aperture) into iPhoto and Export it (even down size to 800 of diamention) it became Sharp and nice colour tone while compare with the one which Export from Aperture!!!!
Why?
In the Export setting of Aperture i do set the Quality to max 12 and 300dpi even...
Need your hand...thanks!!

WARNING! The sharpness problem is occurring in iPhoto modifications as well! I'm running Tiger and Leopard at the same time on 2 different computers - SAME EXACT SHARPNESS problems. The problem is NOT the OS - it's in the APPLE Photo Aps!

Cant edit photos after exporting

Hello all. Relatively new to Lightroom here so Im not sure if this is a dumb question or not.
I imported about 220 photos and worked on just about 20 to 25 of them. I then selected those 25 from my collection and exported them to a folder on my PC so I could then import them into Picasa.
After doing that, I returned to Lightroom to edit more from that collection but could no longer do so. I couldnt make any changes to the ones I previously worked on, but more importantly, I couldnt make any changes to any of the ones I hadnt even touched yet. When you export photos from a folder, does Lightroom automatically prohibit you from changing anything else? It seems the only way I can bypass this problem is just to delete the folder and re-import the photos from my camera again, creating a new folder.
Am I missing something? How can I go back and edit photos after exporting? Can it be done?
Thanks!

Hi Judy
On the bottom left of the left tool bar there are two buttons. Import and Export. I exported my photos using the Export button. When you do that, the screen that comes up prompts you to set up an export location on your C drive. So I exported the photos to a folder I set up.
I did not set up a catalogue or export any catalogue.
I seriously doubt that Picasa had any effect on the folders in Lightroom. The two software application are totally separate. You dont directly transfer photos from LR to Picasa. You need to export from LR first to a location on your PC then Import from that file on your PC into LR. So I dont see how Picasa could effect the photos that are in LR.

Color changes in photos after exporting from aperture and viewed on another computer

Similar Messages

Maybe you are looking for