..with Canon EOS ids mrkll

I don't see my question posted so i guess i didn't upload correctly but here was my q of earlier this morn...
I've been trying to import raw (and larger jpeg)files and I get the message "out of memory (RAM)" even though i have 4.5 gigs of ram. People say its because there is about a 37mg limit on PS 6. Raw files are not that large anyway. Is there
a limit size on Aperture?
Also, just as important, after i figure out the ram issue, i am looking for a photo management program that automatically
makes thumbsize jpegs (or jpeg pages) as I generate hundreds of shots in a shoot and this would save me hours if not days!
Anybdy know of any such program? Thanks....jb

Agreed that you should not be having trouble with file size. I import much larger files that came out of my 1ds Mark II without difficulty.
On a related note . . . I had posted prior to the 1.1 update complaining about poor RAW conversions using Aperture in comparison to the CS2 Raw conversions.
At first glance my conversions now look much, much better with 1.1. Is anyone else having similar success, or is it just wishful thinking on my part? Also, I got a lot of utility out of the lens correction feature in CS2 Raw to correct red/green or blue/yellow vignetting of sharp object against bright backgrounds. Is there a similar function in Aperture that I'm missing?

Similar Messages

  • I have Photoshop Elements 9. I downloaded the plug in 6.0 and it works on the RAW files from Canon EOS 60D, but not with Canon EOS 70D. I cannot download higher versions of plug in, because I have Windows Vista and it is not supported.

    I have Photoshop Elements 9. I downloaded the plug in 6.0 and it works on the RAW files from Canon EOS 60D, but not with Canon EOS 70D. I cannot download higher versions of plug in, because I have Windows Vista and it is not supported.

    You could try using the DNG converter 8.7 on Windows vista:
    <Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.7>
    <Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.7>
    You then need to watch this video to get hang of it:
    <Camera Raw: How to use Adobe DNG Converter - YouTube>
    Hope this helps.

  • I can't use my iPad2 with CANON EOS 350D

    I can't use my iPad2 with CANON EOS 350D

    Hi! You seem to be good at this. today I purchased the Camera Connection Kit but it doesn't work with my old Canon EOS 350d. I've switched to 'PTP' but it doesn't work. When I go in to "pictures" and "Camera" I can't see any pictures. Do you have any idea why? Can it have somehing to do with that I don't have the newest IOS 5? ( I have iPad 2nd gen). Don't know if you need to know anything more, but I would really appreciate if you could try to help me!

  • Is canon EF 24-85mm F3.5-4.5 lens is compatible with canon eos 6D ?

    Is canon EF 24-85mm F3.5-4.5 lens is compatible with canon eos 6D ? is it work fully automatic ?

    pjmacd wrote:
    Yes, that lens will work normally on the EOS 6D with all automatic functions intact. Any Canon lens labeled as "EF" will work on the 6D, but lenses labeled "EF-S" will have strong vignetting (darkening in the corners of the shot).
    Actually... "EF-S" lenses will not even mount.  There's a lip on full-frame bodies designed to prevent EF-S lenses from being attached.  It's not just a question of heavy vignetting and severely degraded image quality at the edges of the frame -- there's a risk of the reflex mirror hitting the rear-most element on an EF-S lens (remember... full frame cameras require physically larger reflex mirrors).  
    Any "EF" lens can be used.  Any "EF-S" lens must not be used (and will not fit).  Also, there are a few special purpose lenses such as the MP-E and TS-E lenses which will work with the 6D as well.
    Tim Campbell
    5D II, 5D III, 60Da

  • Is canon EF 24-85mm F3.5-4.5 lens compatible with canon eos 6D ? is it work fully automatic ?

      Is canon EF 24-85mm F3.5-4.5 lens  compatible with canon eos 6D ? is it work fully automatic ?

    6D requires lenses with an EF mount. You list your lens as an EF (the mount style) 24-85 zoom so yes it will work but it may not provide nice crisp images on such a modern high mpixel camera. The newer bodies show the weaknesses of older consumer grade lenses.
    "A skill is developed through constant practice with a passion to improve, not bought."

  • I can't update my Photoshop CS3 in order to open pictures made with Canon Eos 60 D

    I can't update my Photoshop CS3 in order to open pictures made with Canon Eos 60 D

    It's not terrible even if you jump a few versions; the Adobe folks don't want change a good thing, so much of what one expects is still where you expect to find it from version to version.  A person who upgrades from Photoshop CS3 to CS6 will find the new Tabbed View, introduced first in CS4, and probably won't like it (at first), but it actually can grow on you.
    With CS6 they've introduced this new "shape layer" abstraction of what was once a fill layer with a vector mask.  Beyond that, I suppose there must be 3D changes, though I haven't the experience to tell since Photoshop CS6 is the first version I've moved up to Extended with.  I admit, the 3D stuff is fun to play with.
    Just to give you an idea of what I've been doing with Photoshop just this evening...  My collaborator and I have been photographing carbon stars - red giant stars whose atmosphere contains more carbon than oxygen, and which are strikingly red.  In this image the carbon star, SAO49477 is the red member of the close double just up-right of center.  The red stuff between the stars is glowing hydrogen gas, singly ionized by starlight to emit a deep red color.  Someday it will coalesce and make more stars.
    -Noel

  • Tethering with Canon EOS 450D

    Hello!
    Is tethering with Canon EOS 450D even after the digital camera raw compatibility 2.6 still not possible?
    Regards,
    Vlad

    Tethering with Canon EOS 50D also not Possible.
    Mac OS X 10.6.1
    Aperture 2.1.4

  • Raw file rendering problems with Canon EOS 5D in Aperture 3

    Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
    With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
    A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
    I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
    I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
    Has anyone experienced similar problems?

    I'm having the same problem.
    iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2.  Workflow is importing through Canon's DPP and then using referenced images in Aperture.  The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
    There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
    but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
    I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
    I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps.  I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end?

  • After loading Lion I cannot open some pictures. I get Unsupported Image Format. It tells me picture was taken with Canon EOS Rebel with unknown lens

    After loading Lion I cannot open open some pictures in Aperture. I get Unsupported Image Format, all files even the ones I can open are .JPG. Also it tells me picture was made using Canon EOS Rebel with unknown lens.

    You mention that 'most' of your files are DNG. Try
    running the effected files through Adobe DNG
    converter again and then import your reprocessed
    files to Aperture and see if the problem persists.
    I had a problem with a batch of D2x files converted
    to DNG which had been metadata tagged by
    PhotoMechanic (the evil app).
    B.T.W. You mention that you had been using Bridge.
    Are you getting any of the embedded XMP metadata
    coming into Aperture during the import process?
    Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
    I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
    Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

  • Problems with Canon EOS Utility & Canon 5D Mark II

    Canon EOS utility cannot see my 5D Mark II connected via USB.
    I've installed the latest 5D firmware (1.2.4), latest EOS Utility (2.7.2) and i'm running Snow Leopard 1.6.2.
    When I open EOS utility it cannot recognize the camera, neither with Snow leopard default photo import application.
    How can i solve it? Already tested the usb cable and all the option under camera menus...

    Yes, just started using this and noticed pretty soon afterwards. Seems to happen when I start clicking around or doing anything that uses the processor more than just surfing the web, but that's just anecdotal. I immediately stopped and started using MPEG Streamclip, but I really want the timecode.
    Most recently, I had Log and Transfer open, transcoding some 7D footage, and a few of the clips didn't come in—they were left with the red stop-sign symbol/exclamation point. When I clicked to "retry," it stopped importing the current clip and started on the clip I retried. I clicked "retry" on another unimported clip, and again, the clip import stopped and the new clip began processing. I let it go through and, after the checking the footage, I discovered it had been incorrectly named the first clip's filename! Needless to say, I hand-checked every file to make sure it was the right duration (a few weren't), deleted the files from the Capture Scratch folder, and reimported—making sure I didn't touch the computer.
    I hope they fix this bug, whatever it is.
    BTW, I've experienced it on two separate Mac Pros.

  • Mac will not work with Canon EOS cameras

    My imac OS X 10.6 is not working well with my Canon EOS 5d Mark II camera on the tethered mode. The camera works well with other Mac computers, and I have spent hours with Canon tech help. It now seems that the issue may be with the computer. The EOS Utility is working, everything has been updated, all Canon checkpoints look good, but when I use the camera, the image does not transfer. And then everything gets locked into a loop and I have to crash the camera and force quit the program. Is there something in the computer that may be blocking the transfers? any ideas where to look? Canon has done everything on the camera side, but I don't know where to begin with the computer.

    OH, ok. So the issue is with transferring the image from the camera to the computer. Since you said you have done everything possible with canon, the camera's firmware is completely up to date, you have the correct software installed. Since you say no cameras work with this computer I am inclined to say the problem is from the computer, which is why the problem exists. I'd do an apple hardware test and see if anything turns up. Clean install of the canon software would also be a good idea.

  • Aperture and RAW support with Canon EOS 60D

    Got my new Canon EOS 60D yesterday. But Aperture does not support the new RAW photos from the EOS 60D yet.
    Anyone with the same problem?
    When is Apple updating the RAW support for the 60D in Aperture?

    Well, DNGs don't actually contain all the data of the original raw file, so that could be an issue.
    As an example, the focus point functionality of Aperture 3.0 doesn't work with files converted to DNG, as the camera-specific information has been stripped from the file by Adobe. I don't know whether the DNG format can actually hold that info or not, but as of today it doesn't.
    Apple historically has tended to support the new SLR cameras from Canon and Nikon, so I wouldn't be surprised if support came along shortly. That said, buying a camera the day it's available and expecting immediate support for its raw format is not all that reasonable. The vendors providing raw support don't necessarily have access to pre-release versions of the cameras (in general), so there's going to be some time necessary to develop and QA the support for the new format.

  • Problem with Canon EOS 5D MK II & LR 2.2

    Good day! I love LR. I've used it very successfully wih my Nikon D-80. I've recently purchased a Canon EOS 5D MK II & upgraded to LR 2.2. I've got an issue with importing RAW images. None of the 3 RAW sizes are recognized by LR. When I go to import the images from device, the RAW picture files are displayed as gray blocks with no picture detail. Check marks are still there and I can go through the motions of importing, but there is always an error message that the files are unrecognizable. I would hate to start shooting in JPEG again. Does anyone have any advise that may help?
    Thanks ahead
    Rich

    Try using a dedicated card reader instead of importing directly from the camera.

  • Does Photoshop work better with Canon EOS 7D or Nikon D7000?

    18.0 megapixels - Canon EOS 7D
    16.2 megapixels - Nikon D7000
    Also, I keep reading the best digital image format to work with in Photoshop CS5.5 is RAW.
    Is this right?
    Thank you.

    You should know that the sensors are made or at least created by the same company it is a question of specification by the manufacturer that determines which sensor and advance standard the sensor is made.
    That being the case Canon has traditional jump the gun to select the more advanced technology rather than wait for that technology to be 100% perfected as in a full frame 35mm format sensor.
    Also they have consistently favored larger pixel count over quality of the pixel itself and use software (the firmware) to smooth the result giving it that slightly soft quality.
    They do this with their lenses as well in particular to their Shift Tilt lenses which had to be updated since Nikon waited and were very successful with that update as well.
    It is not that the cameras as not popular or good but if they wait they might be able to give their customers the better product.
    Like the sensors the Shift Tilt lenses seem to be made by the same company but with different specification and perhaps different glass.
    The two cameras you are speaking of are not their high end cameras but like all the products both companies make they are good depending on what you need.
    And counting pixels is kind of ridiculous these days as the New 1DX has a lower pixel count then its predecessors because they found that making larger pixels enable them to control the noise better as Nikon discovered.
    I still use the D3 and my client in Paris often enlarges the images to over a meter in hieght with amazing detail and it could easily be resampled much larger.
    And you are talking about 12.1 megapixels to start with so the game of pixel has some meaning but not much.
    When they perfect the noise control for smaller pixels then the technology for a larger pixel count will have some weight right now that is not the case although from what the they claim about the 1Dx might prove to be an indication that they hav made some strides in this direction it reamins to be seen if Canon has jump the gun again which I suspect they have done.
    Doing things in a rush is often the slower way to a goal.
    Let see if Canon jump the gun again. I would think Nikon woud have been on it if they thought the tehnology was finished they get the sensors from the same place.
    So far all I have seen is that the body looks good?

  • Problems with Canon EOS MOVIE Plugin-E1 for Final Cut Pro

    After about two weeks of using the Canon EOS MOVIE Plugin-E1 for Final Cut Pro, I've found some clips are cut short when they are transcoded to Prores and appear in the browser. Has anyone else had this happen?

    Yes, just started using this and noticed pretty soon afterwards. Seems to happen when I start clicking around or doing anything that uses the processor more than just surfing the web, but that's just anecdotal. I immediately stopped and started using MPEG Streamclip, but I really want the timecode.
    Most recently, I had Log and Transfer open, transcoding some 7D footage, and a few of the clips didn't come in—they were left with the red stop-sign symbol/exclamation point. When I clicked to "retry," it stopped importing the current clip and started on the clip I retried. I clicked "retry" on another unimported clip, and again, the clip import stopped and the new clip began processing. I let it go through and, after the checking the footage, I discovered it had been incorrectly named the first clip's filename! Needless to say, I hand-checked every file to make sure it was the right duration (a few weren't), deleted the files from the Capture Scratch folder, and reimported—making sure I didn't touch the computer.
    I hope they fix this bug, whatever it is.
    BTW, I've experienced it on two separate Mac Pros.

Maybe you are looking for