Missing photos after import - Canon EOS Digital Rebel

Hi,
After two calls to Apple Support I have solved this issue for this digital roll of 12 raw format images. Here are details for whoever might be interested.
For some reason, iPhoto 6.0.6 was unable to import all of the images from a Canon EOS Digital Rebel camera. 7 out of 12 downloaded fine, however iPhoto seemed to stall at 5 remaining.
Further efforts to rebuild photo library did not help, and the images were never transferred from the camera to the iPhoto 6.0.6 on MacBook Pro Intel (not in original folder).
Then I tried to import the images to the iPhoto 6.0.6 on MacBook Pro Intel via a different user. Then I deleted the first 7 images from the memory card, and tried to import with iPhoto and with ImageCapture. None of these worked.
Then a new memory card with 4 test images (2 large, 2 raw) did import to iPhoto ok.
Then I used Canon File Viewer Utility to drag the 5 images from the first memory card to the desktop. And then I reformatted that memory card.
Before deleting or reformatting the memory card I was also able to import the 12 images to a 12in PowerBookG4 with iPhoto5 version 5.0.4 ok.
From now on however I will be counting the images from card to iPhoto.
MacBook Pro   Mac OS X (10.4.9)  

this is answered per calls to Apple Support

Similar Messages

  • Support for tethered shooting for Canon EOS Digital Rebel T1i

    I just read online that Apple Aperture 3.1.2 won't tether to my Canon EOS Digital Rebel T1i under OS X 10.6.7.  Is this true?  If so, is there a workaround or some software I can install?
    Thanks,
    Joe

    BTW - in case anyone is wondering, I've tested this... Canon T1i does work with tethering. (this camera is natively supported by Aperture for purposes of tethering)
    For any cases where there is a camera which is not supported directly, there is also a work-around which should work for almost any camera.
    Go to the Aperture plug-ins page:  http://www.apple.com/aperture/resources/plugins.html
    Look for a plug-in called "Aperture Hot Folders" (direct link is here:  http://www.apple.com/downloads/macosx/automator/aperturehotfolder.html?cmp )
    The plug-in monitors a folder (of your choosing).  Any image which shows up in that folder will automatically be imported into an Aperture project (it's on-the-fly).  Essentially you'd use the Canon EOS Utility to do the tethering, which requires that you pick a target folder where it'll save all pictures you shoot during the tethered session.  You then tell Aperture Hot Folders to monitor that same folder and import any images found into an Aperture project. It gives you the ability to create tethering support for any camera that can do "tethering" even if Aperture doesn't directly support the specific camera (by using the manufacturer's own tethering utility.)

  • Canon - EOS Digital Rebel T1i

    Hi! I want to buy Canon - EOS Digital Rebel T1i 15.1-Megapixel Digital SLR Camera - Black, and on bestbuy website says: "digital camera that features an 18-55mm image stabilized zoom lens" But when I come to store, I saw this camera and this kit lens without IS. How it can be?? is it different products, in local store and in online store?? Thank You. 

    _Hungry wrote:
    I don't know what the lens was there, but "Stabilizer" or something like this isn't on it , and the bestbuy worker said that this kit camera doesn't have IS. 
    Ask to see an unopened box that includes the kit.  If it claims that the lens has IS, purchase the unit and open the box in the parking lot to verify that it is an IS lens.  Hard for them to argue that you pulled a swap if you come immediately back from the parking lot.  (The longer you wait to open, verify, and return, the harder it is to return an "inconsistent" unit.)
    *disclaimer* I am not now, nor have I ever been, an employee of Best Buy, Geek Squad, nor of any of their affiliate, parent, or subsidiary companies.

  • HT4757 installer for canon eos digital rebel xt for mac 7.10.5

    I need to know why my camera isnt downloading my photos anymore. I couldn's find my installer, and it should be on my compter. Is there an online download for this camera with this latest system?

    BTW - in case anyone is wondering, I've tested this... Canon T1i does work with tethering. (this camera is natively supported by Aperture for purposes of tethering)
    For any cases where there is a camera which is not supported directly, there is also a work-around which should work for almost any camera.
    Go to the Aperture plug-ins page:  http://www.apple.com/aperture/resources/plugins.html
    Look for a plug-in called "Aperture Hot Folders" (direct link is here:  http://www.apple.com/downloads/macosx/automator/aperturehotfolder.html?cmp )
    The plug-in monitors a folder (of your choosing).  Any image which shows up in that folder will automatically be imported into an Aperture project (it's on-the-fly).  Essentially you'd use the Canon EOS Utility to do the tethering, which requires that you pick a target folder where it'll save all pictures you shoot during the tethered session.  You then tell Aperture Hot Folders to monitor that same folder and import any images found into an Aperture project. It gives you the ability to create tethering support for any camera that can do "tethering" even if Aperture doesn't directly support the specific camera (by using the manufacturer's own tethering utility.)

  • Nikon D40 or canon eos digital rebel xt

    I'm looking to make the transition from p and s cameras to an SLR. I have my eye on these two cameras. I'd be using them mostly for scenic shots and sports photography. I don't really have a budget (I don't mind spending more for the canon), my concern lies with the practicality of using each at my level. If I get the canon will there be too many options for me to grasp? Alternately, if I get the D40 will I quickly outgrow it and have to spend more for a new camera anyways?
    I also had a question about shooting raw jpegs. I'm fairly fluent in Photoshop cs3 in terms of design and compositing elements. Can CS3 edit raw jpegs or will I have to purchase a program like Aperture? Thanks.
    Message was edited by: Paperwayte

    Are you buying these "used" and at a substantial discount from suggested retail? Both are old and have been replaced by cameras in the same price range with substantially better specs.
    The Canon EOS Rebel XS and the Nikon D3000 compare with nearly identical specs. Both have 10 Megapixel sensors. Sensors are nearly the same size. Both come as a 'kit' with an 18-55mm image-stabilized lens, and both have similar street prices (you should have no trouble finding them for about $470 -- both Amazon and BH Photo sell them at that price.)
    When I look for the Rebel XT or D40 they're hard to find and the places that claim to have them want more money for them than the substantially improved cameras that took their places in the respective model lines.
    10 megapixel crop frame sensors do a very respectable job. Unfortunately those start 18-55mm zoom lenses are "good" but not "great". With higher quality lenses these cameras will take much better pictures. Unfortunately high quality lenses cost as much or more than the whole starter camera outfit -- so that's probably something to grow into.
    I don't know the Nikon lens line-up as well as I know the Canon (I'm a Canon guy but I'm not particularly biased.... basically in the competitive landscape of DSLRs it seems to be a slug out between only Canon and Nikon. There are lots of others but I think they trail behind.
    Though you can get models with 12, 15, 20, megapixel I think 10 is really very substantial. At this point the lens quality becomes a major factor in how good the photos will look as many lenses don't deliver enough definition for higher resolution sensors to show off their best work. This is the case with the 'starter' lenses that come with these cameras. They are "o.k." and will take decent pictures (far better than you'd ever get with a compact camera), but when you take a tool like Aperture and put the image in full-size mode (so every pixel on the screen represents a pixel from the camera) you'll see that the images aren't so crisp. At that point it's more about acquiring better lenses than it is about acquiring a better camera.
    On the Canon side, the EF-S lens series are designed specifically to work with the crop-frame sensor cameras. The EF (without the "-S") are designed to work with the full-frame sensor cameras but will also work perfectly with the crop-frame (EF works with any Canon EOS -- Rebel or not). The reverse is not true (EF-S lenses will NOT work with Canon's full-frame sensor models). If you plan to upgrade but keep your lens inventory then keep that in mind when making purchase decisions. On the other hand, EF-S lenses are usually more affordable -- so if the price of EF lenses isn't practical for your budget (especially the EF lenses that come with "L" series optics -- astonishingly gorgeous optical quality but VERY spendy price tags.) you might just stick with the EF-S lenses anyway.
    Similarly, the Nikon's come in crop-frame sensor versions (e.g. the D3000) or full-frame sensor versions (e.g. the D3). Full-frame is MUCH better, but also much more expensive. You'd have to ask a Nikon guy how their lens line-up works. I'm assuming they have similar nuances, but I'm afraid I can't be much help there since I have no experience with them.
    As for Aperture vs. Photoshop... they're very different beasts. Photoshop does wholesale image manipulation. Aperture does better photographic quality adjustment and also manages all your photos but doesn't do wholesale image manipulation (e.g. you couldn't cut a person out of one photo and stick them in another using Aperture. But you can touch-up images in Aperture... e.g. remove a minor object using the clone tool, touch up blemishes, etc.). I have both Aperture and Photoshop CS4 -- not sure how Adobe is for providing RAW updates for CS3 since it's no longer the 'current' version.

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

  • I am having trouble importing jpegs shot on my Canon EOS Digital Rebel XTi

    I have about 1000 jpegs that i need to import into FCP. A few specs to start off with. I am working on FCP 7.0 and a brand new MacBook Pro. I have had this camera for about 4 years and have not had a problem importing the jpegs into my old laptop and old FCP program.
    When i try to import the jpegs, the 2 portrait jpegs will import fine, but the 350 landscape jpegs will not. I keep getting the "file unknown" error. The dimensions are exactly the same, just reversed. it is RGB. i am able to open the file in preview and resave and then it will import fine. But, i have 1000 photos and don't want to have to do that for all of them. Plus, i will be taking several thousands more and won't have time to do that to each and every photo.
    How to i solve this problem so I can simply import the landscape jpegs as i have always done?
    Thanks in advance for all of the help.

    Will I have to do that for every picture? I am able to open them in Preview and resave them and they work fine. Is there a camera setting that I need to use to dictate how the pix are imported?
    Thanks for your help!

  • Missing photos after importing from iPhoto

    I have a big iPhoto library that span from 2002 until today.
    Launching Photo for the first time started the import of the default iPhoto library, when finished the problem is not everything has been imported.
    I have not done photo by photo check, but for instance all 2014 photos are missing and since I see less photo in previous years and in 2015 also photos from other years are missing.
    I can't reimport the iPhoto library (I have not been able to find how), so my question is how can I import the whole iPhoto library to Photos?

    First off that is a bad practice - never have any computer program delete things - import photos and keep them - after at least one successful backup cycle has taken place and you are sure your photos are safely on the Mac and backed up then use the camera's format command to erase and reformat the card
    You can try to backup your iPhoto library and hold down the option and command keys while launching iPhoto - repair permissions and rebuild the database form the resulting first aid window - that may recover your photos - if it does not then photo recover software like media recover is the next step
    LN

  • Missing photos after Import

    Ok here is the deal, I have had problems iporting photos into my iphoto library lately. I imported a rill via the import command and then I got a munch of the ! mark things one for every picture. So then I went into the iphoto library and found that the folder that keeps the rolls was read only ( I sure didnt put it that way) anyways I changed it to read and write, I imported again and now have all the thumbs but when I view them individually I get the ! thing again, plus it keeps telling me to rebuild my thumnail cache, which I don't remember ever having to do before. Any help is appreciated.
    Thanks,
    Zach_

    Zach:
    Welcome to the Apple Discussions. Try the following: download and run BatChmod on the iPhoto Library folder with the settings shown here, putting your administartive name in the owner and group sections. You can either type in the path to the folder or just drag the folder into that field. See if that will make any difference.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • How can I get my computer to recognize the canon eos digital rebel

    I have not used this camera for more than 2 years.  I now have a laptop with windows 7.  This computer will not recognize this camera when I plug it in to usb to download pictures.  I have tried everything except what is going to work.

    Do you happen to have the original discs?  Or, was EOS utility previously installed on that computer?  If not, you need to do a bit of shinanigans to get around Canon's protection (which I still don't understand, either you own a Canon, or the software is no use to you).  It's not hard, but you have to rewrite a registry file to make the software think it was previously loaded on your computer.
    Go here (providing you're in the US) to download EOS utility:
    http://www.usa.canon.com/cusa/support/consumer
    It's an "updater".  So again, you need to have had a previous version on your computer or it won't install.   Once it installs all you do is plug in your camera and turn it on and a window pops up offering a couple different options like File Transfer or Tethered Shooting.

  • Tethering and the Canon EOS Digital Rebel

    Aperture site says its supported but all I get when connected is the HUD will the button in ready mode but when you click capture or take a picture with the camera, nothing. I have connected by PTP and it will not see the camera. I have removed the card and taken pictures with the camera and still nothing.
    Is there something I have missed?

    canon changed the tether protocols...over a year ago....all canons from the last year cannot be used tethered in aperture....please do us all a favor and contact apple support and put in a request to finally have this fixed...the more write in, the better our chances are....
    this is the 3rd thread on the first page of the forum on the same subject....apple please listen...

  • Hi cannot import RAW photos from my canon eos 5d mark 3 to iphoto 9.6 with iOS  X Yosemite. Fotos are black. Did you have a solution for that?

    hi cannot import RAW photos from my canon eos 5d mark 3 to iphoto 9.6 with iOS  X Yosemite. Fotos are black. Did you have a solution for that?

    Thanks. Once ImageCapture had accessed the photos, THEN iPhoto began to pick up the data, so I was ultimately able to do both. It only worked with the cable, though, not the card readers. Weird.
    And I really appreciate the ImageCapture tip. Any idea why it worked?

  • Lightroom 5 Darkens Photos after Importing Images Used with Different Camera [NOT SHOOTING IN RAW NOR B

    I seriously need help, my whole entire catalog of photos just got darkened for some reason after importing photos used with a different camera. What happened is that I imported photos taken with a different camera (Canon EOS 60D) and when I did that, it darkened all the rest of my photos (taken with Canon EOS Rebel T3). Why did this happen? This is making my photos insanely hard to edit.

    If you always want Camera Neutral picture style to be applied, then open one of your images that you have imported and have changed nothing else in Lightroom.  Set the camera profile to Camera Neutral and save new camera default settings.  Then whenever you import that setting will be applied to all of your images.
    If you don't always want that style, you could save a preset that applies the Camera Neutral picture style, and then you could choose to use that preset during the import process.
    It is simply a matter of determining your workflow and then setting things the way you want them to work.

  • Can't install Canon EOS Digital Solution disk

    Hi,
    Have got a problem installing 'EOS digital solution disk' which came with my Canon EOS 400D digital SLR camera. Here is a description of what happens:
    I click on 'CANON EOS Digital Installer' icon as instructed. First something called 'MasterInstaller' launches, and I select 'Europe' then 'UK' when prompted. The main menu appears again and I select 'Install', then 'Next' then 'Easy Install'.
    I 'Agree' the terms, then hit 'Next' in Starting Installation window.
    At this point, 'Installer' launches and a window appears with the text "Preparing to install ImageBrowser" (with a blue striped barber pole type line beneath) but nothing happens. The blue stripes do not 'move' as is normally the case when something is working. It just locks up, and usually the Mac beachball of death will spin. I've tried leaving it ages to sort itself out, but nothing changes.
    When I go into the 'Force Quit' option from the pull down menu in Finder, (as everything is stuck) the 'Installer' and 'MasterInstaller' are usually highlighted in red, I guess meaning they've either crashed or got lost. Sometimes the Finder joins in too (being highlighted in red).
    I'm not running any other applications, and I've tried doing a Custom Install, (instead of 'Easy') and choosing only 1 application at a time, and disconnected my external drive but to no avail.
    I tried emailing Canon, but they have just suggested I try loading it onto another Mac but I don't have one or access to one either.
    Some help would be appreciated.
    P.S. Gave disk to my partner to try on his PC and he said it loaded ok, so I assume it's not a faulty disk.

    So it still said Keys out of order ? That is a pretty serious error that Disk Utility rarely is able to repair. I would run it again and report to us exactly what is reported when you attempt a repair (not verify) please.
    Hi Dale,
    Well, the plot thickens....
    I kept running the DU repair (about 5 or 6 times), and interestingly enough kept getting EXACTLY the same message:
    Checking HFS Plus volume
    Checking Extents Overflow file
    Checking Catalog file
    Keys out of order
    Rebuilding Catalog B-tree
    Repair completed
    No details or other messages about what the specific problem was. (Is there a way to find out?)
    Well, I took another look on the link you posted and ran an 'fsck'. (I still have no idea what that means but it sounded as if it may throw up some info.) Indeed it did and here's what appeared after I typed '/sbin/fsck -fy':
    ** /dev/rdiskOs9
    ** Root file system
    ** Checking HFS Plus volume
    ** Checking Extents Overflow file
    ** Checking Catalog file
    diskOs9: 0x8 (UNDEFINED)
    Keys out of order
    (4, 1886)
    ** Rebuilding Catalog B-tree
    diskOs9: 0x8 (UNDEFINED)
    ** The volume Mac Hard Disk could not be repaired.
    sh-2.05a#
    (Hopefully there aren't any typos, I just typed this in myself, having written down the info on paper.)
    Obviously the DU knows there's a problem, but simply thinks it's fixing it every time I run a repair. A bit like Groundhog Day I guess....
    Now what??
    Cath

  • I cannot upload photos from my Canon EOS

    I cannot upload photos from my Canon EOS.  Are there any downloads or softwares that might help.?

    iPhoto should Import. What are you trying to use? How are you doing it?

Maybe you are looking for