Photos wont import from my 5s into Aperture since 2015 & photo stream has stopped

Since new year none of my photos on my 5s are showing in Aperture to import. Everything from previous years is visible in Aperture to import but it shows nothing from 2015???
The photo stream in Aperture has also stopped on the 1st Jan 2015??
If I plug in my ipad it will show the photo that has been taken in 2015 and I can import it no worries which makes me think its my phone???

in my case it turned out to be a corrupt thumbnail cache on the iPhone. The more I tried to use pictures in other apps the more it became obvious that something bigger was wrong, not just with apeture. For example I couldn't select a photo from my phone to upload to facebook either, it just did nothing when I clicked on them. Some research revelaed that with the freeware "iExplorer" that lets you browse the phone as files on a disk you can delete the cache files and databases and force the phone to rebuild them. Upon rebuilding them everything is back and I just imported eveything into Aperture without difficulty. After running iExplorer I navigated into the media folder, and the photo data folder. I deleted the "com.apple.photos/caches_metadada.plist" and also the "Photos.sqlite" and "PhotosAux.sqlite" files then shutdown and restarted the phone. The first time I accessed the photos after the restart it said I had no photos, but a little while later it rebuilt the lists and all is well. That info I got off some site on the internet and I believe that it's been posted here on apples discussions site too, but it never hurts to have more than one copy I have no idea how they got corrupted in the first place, nothing like this has ever happened before.

Similar Messages

  • I can't import from my iPhone into Aperture anymore

    Since upgrading last night to 10.10.3 and running the new Photos app, I'm unable to import from my iPhone into Aperture. My iPhone does not show up in the Import pane. Anybody else seeing this? or am I missing something?

    I agree that Apple screwed Aperture users. I don't understand why. Over the last few years, Apple has dumbed down some applications which makes those apps much less useful. Then they slowly start adding some functions back in for a couple of years then nothing. Look at Pages. It still is missing features that the old pages had.
    Apple should have simply given Aperture to everybody and maybe implemented a Simple User function for those people that don't need professional features. Here was an app ready to go and what does Apple do? Get rid of Aperture to come up with a "toy" replacement, as somebody on these discussion boards mentioned. I'm very disappointed in Apple and the direction that some of these apps are taking. I used to enthusiastically push Apple products to everybody but now I mind my own business. It's a sad state of affairs. The whole quality has gone down. All this reminds me of Apple before Steve Jobs took over. Somebody needs to crack the whip over there and focus on quality and useful apps AND listen to the users.

  • Not all images from iPhoto came into Aperture

    I ran an import from iPhoto and I think I am not seeing photos in some albums.
    Is it possible this is due to my hiding the Album in iPhoto and if so can someone tell me if there is a good or a global way to unhide all Albums?
    Also, can someone tell me if it is possible that I need to unhide all photos as well?
    Are there other things I should make sure to do so that everything I can get to Aperture gets to Aperture?
    Looking forward to working in this software but I have to get clear of iPhoto first.
    Thanks.

    I've been importing referrenced images into Aperture since it was launched. I am also irritated when I set the sort order to Date and as soon as the import starts it changes to Manual.
    Are you saying that I have to go back to my hundreds of albums and set each one to be sorted by Date in order for a new import into a new album to be imported already sorted by Date?
                                            Additional trivial complaints follow:
    I never import from the camera or the SD card. I move my images onto an external HD where they are arranged by date. The files and the folders are set to sort by date on my HD. Why not follow that protocol when importing?
    It was bad enough when v 2.0 came out and decided during the update and "conversion" that my method of sorting and displaying my images which were Year = Project, Month = Folder, Day = folder was incorrect.. Everything was sorted by date because the names of the Project - Folder - folder were all labeled by date : year - month - day. Everything was messed up when Aperture decided I was using the wrong order of storage. So Aperture, without asking, changed the way my images were stored and sorted. It took me weeks to convert them so they would sort & display the way I wanted.

  • Problems importing iPhoto 06 files into Aperture 2.1

    I have iphoto 06 on a 2006 Mac Book Pro with OS X 10.4.11. I've upgraded RAM to 2Gb and have recently installed Aperture 2.0 with the upgrade to Aperture 2.1.
    I'm trying to drag individual RAW (12Mb) files from iPhoto 06 into Aperture 2.1 via the File > show iPhoto Browser command. Unfortunately, Aperture just seems to hang at this stage. The program appears to be importing (little wheels spinning etc) however, nothing happens. I usually loose patience at the 20-min stage and force quit. I figure even with 2Gb of RAM it should not take +20-min to transfer one 12Mb file. Please note i've tried dragging the files in as both Masters and Referenced Masters and it makes no difference Aperture still seems to hang.
    Any advice?
    Thx,

    Aperture, actually OS X, goes by camera make and model not by file. The reason being that RAW files from the same manufacturer with the same file extension but from different camera models can and often do have different formats.
    So it's not possible to talk about adding a certain manufactures file or extension you need to specify the camera make and model. Then you can see what version of Aperture and Camera RAW bundle you need to accomplish that.
    See http://www.apple.com/aperture/specs/raw.html for the list of RAW cameras currently supported. The only Kodak that shows up is the DCS Pro/SLR n which was supported starting back with Aperture 2 in Tiger or Leopard.
    regards
    Message was edited by: Frank Caggiano

  • Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

    Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in Oracle and  yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

    Thanks for your advise.
    However, I missed to mention that we have two set of users  One is for Finished Goods and another for Spares.
    Only Spares users need to be prevented from creating Direct/Manual Sales Orders in Oracle.
    As you suggested, if this will be done at Form level, that may Disallow FG users also to create Manula Sales Orders which should not be the case.
    Further, I tried to test one scenario through Processing Constraints but it did not work.
    Application
    OM
    Validation Type
    Entity
    Temp
    Short Name
    TBL
    Validation Semantics
    Created By
    Equal To
    User(Myself)
    Processing Cosntraint
    Application
    OM
    Entity
    Order Header
    Constraint
    Operation
    User Action
    Create
    Not Allowed
    Conditions
    Group
    Scope
    Validation Entity
    Record Set
    Validation Template
    101
    Any
    Order Header
    Order
    Above Created
    Please advise.

  • Error While Importing from EIF file into AW

    Hi All,
    I am facing the following error while importing from EIF file into AW using AWM as well as from sql prompt.
    java.sql.SQLException: ORA-36786: (IOSEC04) File POCAW/abc.eif does not exist or cannot be accessed.
    ORA-06512: at "SYS.DBMS_AW", line 42
    ORA-06512: at line 1
    at oracle.olap.awm.eif.eifimport.ImportDialogActionThread.doExportOrImport(ImportDialogActionThread.java:172)
    at oracle.olap.awm.eif.EifDialogActionThread.doAction(EifDialogActionThread.java:58)
    at oracle.olap.awm.ui.dialog.ThreadedDialogActionThread.run(ThreadedDialogActionThread.java:49)
    i have already created the directory pocaw.
    i have done the following steps :
    CREATE OR REPLACE DIRECTORY POCAW as 'D:\Olap_POC\export';
    GRANT all ON DIRECTORY POCAW to PUBLIC;
    execute dbms_aw.execute ('aw create ''POC_AW''');
    execute dbms_aw.execute('cda pocaw');
    execute dbms_aw.execute('dtb attach POC_AW rw');
    execute dbms_aw.execute('import all from eif file ''/abc.eif'' dfns update ');
    any idea or thought would be appreciable.
    thanks n advance
    anwar

    execute dbms_aw.execute('import all from eif file''/abc.eif'' dfns update ');
    Maybe one of the following file names could help
    (have never tried it):
    ''abc.eif''
    ''POC_AW\abc.eif''Yes,
    you don't need the slash. CDA is like setting a default directory.

  • Wrong photo will import from iPhoto window

    During the normal course of editing, all of the photos that were in the movie were overprinted with a random movie clip still. The thumbnails in the project window still show the intended photo, but only the new clip still will show during playback. By right-clicking the photo and doing "Show in Finder", the correct .jpg file is referenced. When I try to drag the correct photo back in from the photo media window, a photo will be brought in, but it will be one that appears a few spots away in the list from the intended one. The thumbnail remains the correct photo. I believe something has become corrupted in my iMovie project that will not show the correct photo, even though the program is internally pointing to the correct photo. Very frustrating, as I have lost many days of careful editing. Made a copy of the project and have tried many things, to no avail.
    Anyone have an idea? Is there a parameter file or something that I can delete that will reset things? Thanks very much.

    The distortion/blurriness may arise due to the size of the photo being imported from iPhoto.
    iMovie HD 6 appears to have problems handling very large photos - these should be resized (not cropped) in iPhoto before being imported to iMovie HD. The process is described in this post by Karl Petersen on 14/04/2007:
    http://discussions.apple.com/message.jspa?messageID=4389924#4389924
    Karl describes the process very thoroughly (as always) in Point 3 of his post.
    Doing as Karl suggests may not, of course, help in your particular case but it's certainly worth a try.
    John

  • Video clips imported from an iPhone into iMovie ver 6 are rotated 90 degrees; how can I fix this or avoid it?

    Video clips imported from an iPhone into iMovie ver 6 are rotated 90 degrees; how can I fix this or avoid it?

    iMovie works best with uncompressed audio. If your track is MP3 or AAC, you may get better results by converting your track to the AIFF format and then using that in iMovie.
    You can do this in iTunes. Go to iTunes/Preferences and click the General button. On the General page, click the Import Settings button. Choose IMPORT USING: AIFF ENCODER.
    (note: remember what you changed it from so you can change it back later, before you import another CD)
    Now, in iTunes, select your track. Then click FILE/CREATE NEW VERSION/AIFF VERSION.

  • I had a library of 500 songs,some purchased some imported from cd's i have since lost in a fire. I only have purchaed music in library. Does that mean I have to purchase music match to include any other music?

    I had a library of about 500 songs, some purchased and some imported from cd's I have since lost in a fire. Only the purchased ones now appear in my itunes library. Does that mean iI have to subscribe to music match in order to have all of my music in my itunes library? I still have most of the songs on my iphone. I use a pc.

    " When I did this, my library showed all the music I have "purchased" from itunes but did not have the music that I downloaded a long time ago through itunes from my old CDs."
    Correct.
    " How can I get that music to show up in my library now on my new computer?  "
    Copy it from your old computer or your backup copy of your old computer.
    The sync is one way - computer to ipod.

  • Apple photo streams has stopped working

    My photo stream has stopped working all of a sudden.  It has been working and I can't figure out how to get it back.  Any suggestion from anyone????

    Uninstall and then reinstall the iCloud control panel on your computer.

  • HT4890 How come I keep getting this message when I turn on my computer: 'photo stream has stopped working.' my pictures aren't saving on the cloud!

    How come I keep getting this message when I turn on my computer: 'photo stream has stopped working.' My pictures aren't being saved from my iphone to my computer.  I have wifi enabled on my iphone.  Thanks for your help.

    Firefox 2.0.0.20 is the last ever version of Firefox for Win98 / SE / ME.
    You can get it from here, but you are better off using K-Meleon (derived from Firefox) or Opera instead an old version of Firefox:
    [ftp://ftp.mozilla.org/pub/firefox/releases/2.0.0.20/win32/en-US/]
    You can try KernelEx to get Firefox 3+ to work, but it would be very slow with an old PC of less than 750Mhz. 3.5 and later supposedly doesn't work.
    http://sourceforge.net/projects/kernelex/

  • I am trying to import my photos from iphoto 11   into Aperture v3.0

    I am trying to import my photos from iphoto 11 v9.4.3  into Aperture v3.0. When I select import I get a message saying Aperture cannot import libraries from version earlier that iphoto 7.1.5 and tells me to upgrade to a lter version of iphoto. Advice ?

    I am on MAC OS X Version 10.8.5
    Is Aperture 3.0 still correct or have you upgraded to Aperture 3.4.5? Only Aperture 3.4.5 can import iPhoto 9.4.3 libraries.
    As I said above, you can download the updater for Aperture here:
    Use this link:  Aperture 3.4.5

  • Import keywords and ratings into Aperture from adobe apps?

    Hi,
    I'm currently using adobe bridge/ps2/pse etc as my main apps. I use keywords and ratings extensively.
    When I import my photos into aperture, will I also be able to keep my current ratings/keyword tagging?
    Thanks.

    I also used Bridge/ACR to rate and add keywords to RAWS (Canon) and also used Adobe DNG converter to make DNG files from these.
    No ratings or keywords have imported for any RAWs and DNGs. And, for some DNG files (which I can see in Bridge and iViewMedia), they cannot be displayed in Aperture. It's very strange since I've used the same workflow to create the DNG files over the past year. Some can be imported/viewed, some cannot be viewed. All originally from the same camera/RAW file. I've read in this forum that Aperture cannot read things like keywords from sidecar files.
    I am hopeful that Apple will make DNG sidecar file import a big priority.
    - Pierre

  • 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?

  • My photos won't import from my camera into iPhoto

    Just recently my photos are not able to upload from my Canon camera into iPhoto, but it was working before.
    When I plug the USB camera into my Mac the device shows up on the sidebar column in iphoto, it will say "Loading Photos" with the little circular waiting symbol and then it will just go to a blank grey screen.
    If I try to click on any of the options under "File" or "Edit" they are all greyed out.
    I'm not sure what the problem is since the camera is clearly connecting and being ready by iphoto and starting the import, but then it just stops. There are definitely pictures on the camera to import because I can view them on the camera.
    Has anyone else had this problem or know how they might be able to help? Everything seems to be working except for the last step.

    Can you access the imges on the card with Image Capture (in your Applications Folder) ?
    I would try reformat the card with your camera.
    Regards
    TD

Maybe you are looking for