Canon 500D raw corrupt after rendering in LR, preview oke and zoombrowser raw oke

My wife has a Canon 500D which is supported by Lightroom starting from versie 2.4. With a couple of photo's (raw) she has the problem that the rendering goes wrong. LR will import the photo (raw) and shows a preview perfectly (small version in the grid) but after the rendering has finished a part of the picture is gone. (a large white space is showing). It doesn't matter which rendering you choose (embedded/normal/1:1).
If you take the same raw file and open it with zoombrowser (free app from Canon) it's oke.

The JPEG preview is all right, but something's off with the RAW image. Can the Canon software work the RAW image into a TIFF? I trust this is on just a few images, as you mentioned. It may be they got slightly corrupted on Import- but best to test in other software before concluding the RAW is no good.

Similar Messages

Can't open Canon 500D raw file in PSE7

Since moving to a new laptop running Win7 Pro 64 bitI cannot open raw files created by my Canon 500D
camera. Is there something besides PSE7 that I need to install? I believe this worked under XP Pro SP3. Thanks

In the Editor click Help >About Plug-in >Camera Raw
Make sure you have version 5.4 or higher.
If that’s OK check your display resolution by going to Control Panel >Appearance
Sometimes the camera raw plug-in does not display fully (or properly) if the screen height is set to less than 800. This usually affects netbooks more than laptops.

Vista got corrupt after power failure. sfc reports error and Event log service is unable to start itself.

Hi,
After a sudden power failure, I guess vista file system is corrupt.   I am able to start vista in normal mode, but it seems there are errors like Event Log service unable to start itself, when I start IE, it closes automatically ,
Norton antivirus does not start itself. and so on.
After Bing search, I went to safe mode and executed sfc /scannow and it reported error as below.
"Windows resource protection found corrupt files but was unable to fix some of them"
Unfortunately I am unable to upload log file, so I am pasting CBS.log content here....   Please advice.
Some parts of logs are removed due to limit of 60000 characters.
Please advice.
Regards
2014-07-07 14:55:57, Info                  CBS    Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\cbscore.dll
2014-07-07 14:55:58, Info                  CSI
00000001@2014/7/7:09:25:58.062 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x7147854e @0x714563a1 @0x341392 @0x341ed4 @0x3417cb)
2014-07-07 14:55:58, Info                  CSI
00000002@2014/7/7:09:25:58.156 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x714ae7b6 @0x71490f93 @0x341392 @0x341ed4 @0x3417cb)
2014-07-07 14:55:58, Info                  CSI
00000003@2014/7/7:09:25:58.187 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x6e9c8a50 @0x73981a0d @0x73981794 @0x34360b @0x342be3 @0x3417cb)
2014-07-07 14:55:58, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
2014-07-07 14:55:58, Info                  CBS    NonStart: Windows is in Safe Mode.
2014-07-07 14:55:58, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL,
phase = 0, pdwDisposition = @0x2dfe70
2014-07-07 14:55:58, Info                  CBS    NonStart: Success, startup processing not required as expected.
2014-07-07 14:55:58, Info                  CSI    00000005 CSI Store 4780952 (0x0048f398) initialized
2014-07-07 14:56:03, Info                  CSI    00000006 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:56:03, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2014-07-07 14:56:10, Info                  CSI    00000008 Repair results created:
POQ 0 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\ca20037dc599cf01650000007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa070f7dc599cf01660000007806a403.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
    2: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\6aca137dc599cf01670000007806a403.program_files_common_files_d7a65bb2f0e854e7.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_d7a65bb2f0e854e7.cdf-ms"
    3: Move File: Source = [l:278{139}]"\SystemRoot\WinSxS\Temp\PendingRenames\2a8d187dc599cf01680000007806a403.program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms", Destination = [l:190{95}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms"
    4: Move File: Source = [l:286{143}]"\SystemRoot\WinSxS\Temp\PendingRenames\4ab11f7dc599cf01690000007806a403.program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms", Destination = [l:198{99}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms"
    5: Move File: Source = [l:292{146}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa12227dc599cf016a0000007806a403.program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms", Destination = [l:204{102}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms"
    6: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa28487dc599cf016b0000007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    7: Move File: Source = [l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\6aeb4c7dc599cf016c0000007806a403.$$_ehome_40103e2da1d
2014-07-07 14:56:10, Info                  CSI    121de.cdf-ms", Destination = [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_40103e2da1d121de.cdf-ms"
POQ 0 ends.
2014-07-07 14:56:10, Info                  CSI    00000009 [SR] Verify complete
2014-07-07 14:56:11, Info                  CSI    0000000a [SR] Verifying 100 (0x00000064) components
2014-07-07 14:56:11, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2014-07-07 14:56:19, Info                  CSI    0000000c Repair results created:
POQ 1 starts:
POQ 42 ends.
2014-07-07 14:58:29, Info                  CSI    000000b1 [SR] Verify complete
2014-07-07 14:58:30, Info                  CSI    000000b2 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:58:30, Info                  CSI    000000b3 [SR] Beginning Verify and Repair transaction
2014-07-07 14:58:38, Info                  CSI    000000b4 Repair results created:
POQ 43 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a5ad3d4c599cf01391100007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a5ad3d4c599cf013a1100007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    2: Move File: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\cadfdcd4c599cf013b1100007806a403.$$_help_windows_en-us_b594929e73669c5e.cdf-ms", Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_help_windows_en-us_b594929e73669c5e.cdf-ms"
    3: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\2a41dfd4c599cf013c1100007806a403.$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms"
    4: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\ea0ef7d4c599cf013d1100007806a403.$$_apppatch_1143992cbbbebcab.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_1143992cbbbebcab.cdf-ms"
    5: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\ea241dd5c599cf013e1100007806a403.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
    6: Create Directory: Directory = [l:48{24}]"\??\C:\Program Files\MSN", Attributes = 00000080
POQ 43 ends.
2014-07-07 14:58:38, Info                  CSI    000000b5 [SR] Verify complete
2014-07-07 14:58:38, Info                  CSI    000000b6 [SR] Verifying 100 (0x00000064) components
2014-07-07 14:58:38, Info                  CSI    000000b7 [SR] Beginning Verify and Repair transaction
2014-07-07 14:58:43, Info                  CSI    000000b8 Repair results created:
POQ 44 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\eac6f0d7c599cf01a31100007806a403._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa89f5d7c599cf01a41100007806a403.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    2: Move File: Source = [l:216{108}]"\SystemRoot\WinSxS\Temp\PendingRenames\6a4cfad7c599cf01a51100007806a403.$$_resources_fbee56ab048ab239.cdf-ms", Destination = [l:128{64}]"\SystemRoot\WinSxS\FileMaps\$$_resources_fbee56ab048ab239.cdf-ms"
    3: Move File: Source = [l:230{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\caadfcd7c599cf01a61100007806a403.$$_resources_themes_4d0d4910e83c2273.cdf-ms", Destination = [l:142{71}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_4d0d4910e83c2273.cdf-ms"
    4: Move File: Source = [l:240{120}]"\SystemRoot\WinSxS\Temp\PendingRenames\caadfcd7c599cf01a71100007806a403.$$_resources_themes_aero_3fd78bf4cb5fa2c4.cdf-ms", Destination = [l:152{76}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_3fd78bf4cb5fa2c4.cdf-ms"
    5: Move File: Source = [l:252{126}]"\SystemRoot\WinSxS\Temp\PendingRenames\8a7001d8c599cf01a81100007806a403.$$_resources_themes_aero_shell_a91dfa5124b343c4.cdf-ms", Destination = [l:164{82}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_shell_a91dfa5124b343c4.cdf-ms"
    6: Move File: Source = [l:276{138}]"\SystemRoot\WinSxS\Temp\PendingRenames\aa9408d8c599cf01a91100007806a403.$$_resources_themes_aero_shell_normalcolor_10be8ec981b35fb6.cdf-ms", Destination = [l:188{94}]"\SystemRoot\WinSxS\FileMaps\$$_resources_themes_aero_shell_normalcolor_10be8ec981b35fb6.cdf-ms"
    7: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\cab80fd8c599cf01aa1100007806a403.$$_schcache_f995a5d4decb8cc0.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_schcache_f995a5d4decb8cc0.cdf
2014-07-07 14:58:43, Info                  CSI    -ms"
    8: Move File: Source = [l:212{106}]"\SystemRoot\WinSxS\Temp\PendingRenames\cad948d8c599cf01ab1100007806a403.$$_msagent_be90584645cb9b95.cdf-ms", Destination = [l:124{62}]"\SystemRoot\WinSxS\FileMaps\$$_msagent_be90584645cb9b95.cdf-ms"
    9: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\4a7578d8c599cf01ac1100007806a403.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
    10: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\cafa81d8c599cf01ad1100007806a403.$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms"
    11: Move File: Source = [l:224{112}]"\SystemRoot\WinSxS\Temp\PendingRenames\aae18dd8c599cf01ae1100007806a403.$$_msagent_chars_9a5bcb5da392f588.cdf-ms", Destination = [l:136{68}]"\SystemRoot\WinSxS\FileMaps\$$_msagent_chars_9a5bcb5da392f588.cdf-ms"
POQ 107 ends.
2014-07-07 15:08:01, Info                  CSI    00000213 [SR] Repair complete
2014-07-07 15:08:01, Info                  CSI    00000214 [SR] Committing transaction
2014-07-07 15:08:01, Info                  CSI    00000215 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-07-07 15:08:01, Info                  CSI    00000216 Created NT transaction (seq 1) result 0x00000000, handle @0x4cc
2014-07-07 15:08:01, Info                  CSI
00000217@2014/7/7:09:38:01.060 CSI perf trace:
CSIPERF:TXCOMMIT;5
2014-07-07 15:08:01, Info                  CSI    00000218 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired
2014-07-07 15:15:58, Info                  CBS    Scavenge: Package store indicates there is no component to scavenge, skipping.

Hi,
First, I would suggest you using last known good configuration:
Using Last Known Good Configuration
http://windows.microsoft.com/en-in/windows/using-last-known-good-configuration#1TC=windows-vista
if this cannot bring your Windows Vista back to good state, I suggest you perform in-place upgrade to fix the corrupted files:
How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
http://support.microsoft.com/kb/2255099/en-us
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

After rendering the video is blurry and pixelated.

I have 70 + hours invested in this edit. I recently rendered it for the first time and it became blurry and pixellated. I published it to see if it would come out clear but it did not. I found the tab for deteting rendered files and this seemed to help a little. I published that one and it was a little less blurry but still poor quality. How can I get the video back to the pre-render quality. I am using Powerpoint slides saved as jpegs. I did this in another video and the finished video was super clear, however, now after I rendered this one I am unable to get that same quality.

cwrardin
You need to supply more details than you have in order to get to the core of the issue.
What version of Premiere Elements are you using and on what computer operating system is it running? What do your computer resources look like, installed and available RAM, total and free hard drive space, location and free space for the Scratch Disks?
What are the properties of the source media that you are putting on the Timeline?
Based on the properties of your source media, what is the project preset that you or the program are setting in the new project dialog?
Video (video audio compression, frame size, frame rate, interlaced or progressive, file extension, duration, PAL vs NTSC, camera source, etc.)
Photos (how many, what format, what pixel dimensions)
What is your export choice and settings?
Let us start here and then we can decide the troubleshooting strategy.
Thank you.
ATR

Problem opening Canon 6D RAW even after upgrade today to PS CS6, WinXP-SP3

Givens: PS CS5>CS6 upgrade via $199USD download today, Non-CC upgrade. OS: WinXP SP3, camera: Canon 6D RAW (.CR2 files) and prefer to work on RAWs via Bridge.
Main goal: view Canon 6D files in Bridge, do adjustments, open via ACR into PS CS6 for further work.
My fav workflow for photos is: Bridge>ACR>PS. Just got a Canon 6D camera. So I updated to PS CS6 today and I did go through PS CS6 menu: help>update mechanism for all available updates, which was one round of ACR (and Bridge) updates, no more were offered. That brought ACR from v7.0.0.308 to v7.1.0.354--still could not see Canon 6D RAW files. I went to Adobe.com and did manual download for ACR/DNG 7_3 but it did not enable Bridge to see my new camera files nor could I open the 6D .CR2 files in PS. Got PS error message about not recognizing filetype, update ACR, etc (which of course I just attempted). (Seems as through PS and Bridge did not know the ACR/DNG 7.3 "existed" IF that is a capability).
Then I tried to install ACR 8.7 from the "Fix your 6D RAW problems page" and got error messages in PS CS6 (perhaps bc I am on 32-bit system). Decided to start from scratch; uninstalled PS CS6 upgrade.
Secondary issue is: Now I have uninstalled PS CS6 and done System Restore to the point just after I downloaded PS CS6 upgrade. I want to reinstall but the installer fails. Support chat told me to download PS CS6 Upgrade again (doing that now), then reinstall.
Solve: Main problem: Be able to work on Canon 6D RAW through Bridge and ACR (prefer NOT to workaround with DNG if possible) At time of writing, as mentioned, I am downloading PS CS6 upgrade again, then plan to reinstall. If that works, then I need steps to update ACR so that I can work on 6D RAWs through Bridge and ACR. Please know that going through Photoshop's Help>Update mechanism does NOT seem to work. Do I need manual updates? If so, please direct me to the correct ones and order of procedure to execute this upgrade successfully.
Many thanks, Paul

Yammer, thanks for the info about Camera Raw 8.3--that is my goal to load PS CS6 Upgrade and update to Camera Raw 8.3 Currently, I am having problems installing PS CS6 upgrade after uninstall. I have used Adobe CC Cleaner several times. It seemed to help, and the installer proceeded further with next try. Then I looked and there was no PS CS6 icons. I have done system restore also several times and am about to try again. It seems that my original PS CS6 upgrade installed, but when I tried to load ACR update, problems arose. Is there a way to remove recent version Camera Raw remnants from my computer. There is no Photoshop CS6 folder and further none for the CameraRaw.8bi for PS CS6. One possible clue: Yesterday I did two upgrades: 1) PS CS4>CS5 via box, then 2) PS CS5.CS6 on-line download non-CC. In one round of update, I saw that PS CS*5* Extension Manager failed to update. Seems unrelated but mentioned here for thoroughness.
Running ACR 8.3 in XP SP3 would be most useful and timely today as I have work to do. Many thanks, Paul

DNG Converter 5.4 will not convert Canon 500d .cs2 raw files

Hello
I downloaded the DNG Converter 5.4 to try and convert the raw files from my new Canon 500d.
I got an error message stating "the file could not be created."
Has anyone with the same camera got the dng 5.4 converter to work with the 500d yet???
I am running osx 10.5.6 (latest version)
I know I should have checked before spending over £1000 pounds on a new setup that the camera will work in lightroom. I am very upset with myself.
If anyone can help let me know.
Thanks,
Matt

I'm running Windows XP - downloaded and installed both DNG Converter and ACR 5.4. Found a 500d raw file on the Internet and downloaded, opened ok in the DNG converter, produced a .dng file that then opened successfully in ACR. And the raw file also opened in ACR.
I would first check the installation process, perhaps someone on the forum with both 10.5 and a 500d can testify. Or if they have just 10.5 do the same as I did and download a test file.
Richard Southworth

Canon 500D/Rebel T1i and Raw files

Does anyone know when and if Apple will support raw files from the new Canon 500D/Rebel T1i?

There is a discussion related to this on the Adobe forums:
http://forums.adobe.com/thread/422600?tstart=0
It sounds as though they didn't get the RAW specs for the 500D in advance of the launch as they sometimes do so I'd assume the same is true for Apple. Given this, we could be waiting a few weeks or months..

Lightroom 5.6 cc for Mac and Canon 6D file corruption when adding to catalog

Hello,
I was testing my newly purchased (August 5, 2014) Canon 6D camera shooting out the window of a moving car and also by walking around. I was using the Scene Intelligence Auto setting, shooting in single shot mode and continuous shooting mode. I used the kit lens Canon EF 24-105mm f/4 for the 6D. I've been using LR 5.6 CC to download the CR2 files into a catalog. Before downloading I check the images on the 6D camera's preview feature and all the images look accurate - full color and image. However, when using LR, as I'm downloading the CR2s or converting them into DNGs for my LR catalog, I notice on the thumbnail strip changes some of the images that are being imported into thumbs showing color shifts and/or blank white areas. After LR has processed the images as CR2s and/or DNG the processed are now look like these corrupted thumbs. Many images came out with sections of each image showing a rectangular area of negative imagery (i.g. the sky was rendering purple, the trees orange, etc. Also two of the images blank white expect for the a quadrant of distorted color and negative imaging.
When I try the Canon download software, the images are accurate so I know camera's memory card and probably the camera are not at fault. Any suggestions as to why I may be encountering this problem and how to resolve it?
I use a 2012 Mac Book Pro and have my LR catalog on a external hard drive.
Thank you.

Based only on what you described seeing after the previews were built and having not seen an example, it sounds like a corruption of the actual file. I have experienced this myself and have usually found a bad connection/cable between the card reader and the Mac or a glitchy card reader. Over the weekend I had issues trying to import images because the USB cable I grabbed was for my Garmin GPS and the my Mac didn't even recognize the reader was attached until I swapped cables. It is not a perfect system. When it is working, life is great but when it is not...
The suggestion to copy your photos to your HDD first (@99jon) is what I would also suggest. This has worked best for me and has caused fewer problems than importing directly from the card. I have turned off the option to automatically start LR when a card is attached so I can manage the offload myself. I never import directly from the camera either since that just adds another layer of complexity which brings it's own compatibility issues. Finally, never, ever let Lightroom or the Mac OS delete your files from your card after import. When you are ready to erase the images from the card, put it back into your camera and use the camera's format utility (it's in your camera's menu but I am not a Canon shooter so I can't tell you where to find it). The memory cards are very cool technology but, since the makers have no idea how they will be used or by what, they are not always reliable. People have reported memory card issues when they delete images from the card in the camera. Best to offload them with a copy (not a move since that implies an OS delete) and then reformat the card in-camera.
One last thing. The in-camera previews are actually JPEGS produced by software in your camera. The default is to make a high contrast and saturated version off what was recorded by the sensor. The RAW image is the data that is taken right from the sensor with almost no modification. The RAW image however is going to utilize the camera's full bit depth and will have a much greater dynamic range than the converted 8-bit JPEG that you see in the display. Also, those little blinkie displays in camera also apply to the JPEG image and not the actual RAW file which can often hold detail the JPEG can't. The point is, my RAW previews always looked washed out and over exposed immediately after import into Lightroom but as long as my exposure is not pushed up against the right side of the histogram, I know the image has as much workable data as I could get. As long as the highlight data is not clipped, don't worry about your previews not looking as good as your in-camera JPEGs. There are development presets to create the same look after import (Develop module/Camera Calibration panel/Profile drop down). There you will see profiles such as Adobe Standard as well as a set of Camera profiles (Faithful, Landscape, Portrait, etc.). Select one of the Camera xxx profiles if you want an in-camera JPEG look. Not perfect, but a really good starting point.

Canon 10D RAW - Unsupported Image Format??

I have a folder of 66 Canon 10D RAW (.CRW and .THM) images. After importing to Aperture 1.5 I get 'Unsupported Image Format' for 29 of the images. If I try and open one of these images from the Finder in preview I also get a 'Cannot open' message.
Strange thing is iView Media Pro, RAW Developer, Canon DPP, Phase One C1, Photoshop CS2 and LightZone can all open and view these files! Only Aperture/OSX (Preview) is having the problem.
Any ideas how to 'recover' these images to Aperture?

You are indeed correct .... shame on me for not reading your post carefully.
Since you have .THM files, are you pulling the images into Canon's ImageBrowser or DP Professional before Aperture vs. importing direct to Aperture? The reason I ask is that iPhoto, Preview and Aperture all failing to read the same image is clearly systemic not application specific. It points to some level of corruption - - - as far as OS X is concerned - - - of the image and is obviously not application centric, save where the application calls on the OS support systems.
Is it possible for you to generate .DNG's for the "Unsupported" images and try importing these? It may be the CRW wrapper that is somehow unreadable at a myopically detailed level that other imaging tools blythly (and perhapds more appropriately) ignore. The DNG wrapper may allow the RAW content to be then read by Aperture.
Hopefully this is a more helpful response.
G.

Aperture 2 Canon G9 Raw problem

If you have any raw files in Aperture 1.5.x libraries they should be deleted fist before upgrading. This images were not compatible in 1.5.x and cannot be read. I kept them in 1.5.x thinking when an upgrade would come they would then be supported.
See intial post of the problem at: http://discussions.apple.com/thread.jspa?threadID=1408070&tstart=0
The solution is as follows:
Before upgrading to Aperture 2 back up your vault
Then delete any unsupported raw .cr2 files that may be in the library.
I tried exporting the raw files first before deleting them but files became corrupted. Try any way it may work for you.
Back up your library again under a different name to a new vault. This new vault will ne all images minus the raw.
You now will have to back ups of your Aperture 1.5.x libraries- one with raw and all other images - one of just your images and no raw.
This is done just to be super safe.
Make sure you have all upgrades of Leopard, Aperture 1.5.6 and Iphoto? loaded and running OK.
Now insert you Aperture 2 dvd disk and follow the instructions to upgrade.
All should go well with no worries off losing your images.
Today I will try the new features of Aperture 2. So far it does seem to run a little faster.
New raw files imported perfectly with no problems.
Again the problem I had is related to Canon G9 raw files that are not supported im Aperture 1.5.6 library then upgrade to Aperture 2 and tried to rad them and open them in CS3 within the new Aperture 2 taking out all the other jpg image in the same project.
Again for more detail on this problem read the initial post linked above.
Enjoy and remeber always back up even the backup.
SH

Well, I really should pay closer attention to Apple tech support. The Apple document here is correct: http://docs.info.apple.com/article.html?artnum=307342
The solution is EASY:
After importing a project with the Canon G9 RAW files into Aperture 2, they have incorrect aspect ratios, as we all experienced. I simply selected the distorted RAW files, chose File--> Migrate and checked the box to update my RAW files. Lo and behold! All fixed.
No more problem.
(I really should pay closer attention to what I read...)
Hope it works for you.

Canon 40D RAW (CR2) Files import

I've Photoshop and Aperture. Cannot install Elements which would be my preference - so help needed here.
Also - I use iPhoto mostly in the latest Apple OS, yet I cannot import Canon 40D RAW files. I get an error message saying they could not be imported - import failed.
Help please.
Freshacre

Freshacre:
Welcome to the Apple Discussions. What version of PS Elements are you trying to install? I've installed the PSE 6 demo without any problem.
What type of files are you trying to import and from where?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) 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 created 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. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

How to open canon 70D RAW files in Lightroom 4?

I have udated LR 4 to LR 4.4. It is supposed to open the newer Canon camera RAW files like the 70D. After updating with the download from Adobe LR ver. 4 will still not open the 70D RAW files. Does anyone have any suggestion? I must be doing something incorrect or am missing a step to the update. Thanks!

Not so, 70D support was added in Lightroom 5.2 ... Camera Raw plug-in | Supported cameras
You have a choice to upgrade to Lightroom 5.6 or use the DNG convertor to convert the CR2 files to DNG and import.

JPG files become corrupt after Exporting in LR 3

Does anyone have any idea what would cause
my JPG files to be corrupt after I export my edited Raw images in LR3? There are no problems with the Raw file, but once I edit them, apply what ever settings to them in LR I need, I export them as JPG to the same hard drive but in a sub folder where the raw files are, they will not open in photoshop or anywhere else. They are corrupt or lacking data???? When I upload them to my proofing website, there are colored streaks all through the image. Now, I noticed that when I go into that folder of RAW images, and delete the .xmp files, I have to start over, but it fixes the problem. So, now, I can't use .xmp sidecar files to save my editing. I'm fairly new to LR, so any suggestions would be great. I did recently upgrade my system to OS windows 7. Everythign was fine till I had to reinstall everything on my computer...and I also changed hard drives. I upgraded to a Terabyte drive moving all my images from a 500G to the terabyte. Could that cause my sidecar files to be corrupted?????
Thank you!!!!!

I doubt that the XMP files have anything to do with this, as Lightroom doesn't use these files when it creates an exported file.
It sounds like your hardware may be the culprit; these types of corrupt files are often caused by a failing hard drive. Some corruption may have happened in the transfer from one hard drive to another; or the new hard drive has some sort of problem.
Can you hook up the old hard drive again and see what happens to the photos there? Open one of them and compare it to the photo on the new hard drive.

Elements 6, Canon 50D Raw Files, Windows Vista

Hi all...my first post here...
I'm able to load and see my Raw files in the organizer after loading the latest ACR. But when I browse through the files, after a bit, I get an error message that Elements needs to close. After closing I check my task manager and notice that the organizer is at 25% CPU usage, so something is hanging things up. I just don't know enough to figure it out. (I'm a little tech savvy, but not a lot...)
I'm on a PC running Vista. Any thoughts would be very appreciated.
Thanks in advance.

"Bug Files"? That's a new one for me.
I've successfully imported a Thousand RAW files with thumbnails generated in the organizer.
I've got 4gigs of RAM.
I left the organizer open for 6 hours today and when I got back home, the RAW files still wanted to freeze, yet I was able to go to some jpg files and work on them before getting the "Elements is not responding and needs to close message". I'm going to go back to check on browsing the RAW files again.
I heard from someone on a DPReview Canon Forum who had the same problem with Elements 6 and the 50D Raw files and it disappeared when he upgraded to Elements 7.

DNG 4.2 and Canon G9 raw CR2 problem

I have been unsuccesful getting the 4.2 DNG to convert the CR2 Canon G9 files, getting an error message that the file type is not supported. Running Windows XP Home. Any ideas as to how I can fix this. Thanks, Jeff

I just helped my friend with the Canon G9 Raw file won't open and recognized on Mac Computer.
Problem when try to open or drag the Raw image (*.CR2 File), I got an error message says the file type is either not supported or corrupted, also the file in the browser are all grayed out, means can't click & select & open. So I re-install the software just to make sure the software is fine.
The software comes with the camera is easy to install, here is the thing I was stumbled but figured it out.
1. Use browser to find the raw file.
2. click to select the file
3. go to Menu Bar under "File" there is a section you'll see "Process Raw File" or something like that, then you are done, from there you can edit and open a Raw file.
My impression towards to the raw image quality and canon software: The software interface is not as nice compare to PS Element 4 Raw Plug-in, especially there is not button for "Processing Raw" on the browser window that you have to go to File >.. , I hope this is just for Mac users or I have to say the software is silly.

Canon 500D raw corrupt after rendering in LR, preview oke and zoombrowser raw oke

Similar Messages

Maybe you are looking for