<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Corrupted CR2 File in EOS DSLR &amp; Mirrorless Cameras</title>
    <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479081#M116405</link>
    <description>&lt;P&gt;Dang ok. That's not ideal but it makes sense that things fail - I've written thousands and thousands of files via this camera over the years.&lt;/P&gt;&lt;P&gt;I have so much redundancy in my system from hardware to software on the capture and backup sides and I guess this is an example for when two things go wrong (user error on dual card setting and corrupt RAW) I still was able to deliver a decent photo to the client... which is pretty good.&lt;/P&gt;&lt;P&gt;Thanks for your input. Will make sure to put dual write back on right now!&lt;/P&gt;</description>
    <pubDate>Thu, 23 May 2024 16:23:41 GMT</pubDate>
    <dc:creator>disc_count</dc:creator>
    <dc:date>2024-05-23T16:23:41Z</dc:date>
    <item>
      <title>Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479079#M116403</link>
      <description>&lt;P&gt;Completed a shoot two days ago with around 400 exposures on my 5D IV.&lt;/P&gt;&lt;P&gt;I was shooting in RAW + JPG mode (I always have this enabled) and I thought I was shooting to both cards like I typically do (I wasn't).&lt;/P&gt;&lt;P&gt;When I got home Adobe LrC gave me an error that one file wasn't imported. I tried importing again and it still didn't work. I tried using Quicklook in Finder (Mac) and that didn't work. Tried opening in Adobe Ps, same error. Tried reimporting from the card thinking maybe it wasn't copied over properly, same error. Tried one more time to import from card but copied to the desktop and named it something different. Still wouldn't open.&lt;/P&gt;&lt;P&gt;Luckily the JPG version was normal so I used that and edited it as best I could. But this could have been really bad if it was one of the more important shots on a more important shoot, especially since I didn't have any indication of an error until I got home and tried to import.&lt;/P&gt;&lt;P&gt;Any ideas why this issue happens and how to prevent this issue going forward?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Edit:&lt;/STRONG&gt;&amp;nbsp;&lt;SPAN&gt;realized the other card actually WAS recording and dual-write was on in 5D IV (dual-write was off in my R6 and got the cards mixed up). So the other copy on the 5D IV SD card was fine. Redundancy win!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:48:07 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479079#M116403</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T16:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479080#M116404</link>
      <description>&lt;P&gt;It happens, there is not much you can do except the built in redundancies of writing RAW+JPEG or to both cards.&lt;/P&gt;&lt;P&gt;In Syl Arena's Speedliter's Handbook he shows an example that happened to him, so it can happen to anybody.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:04:08 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479080#M116404</guid>
      <dc:creator>kvbarkley</dc:creator>
      <dc:date>2024-05-23T16:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479081#M116405</link>
      <description>&lt;P&gt;Dang ok. That's not ideal but it makes sense that things fail - I've written thousands and thousands of files via this camera over the years.&lt;/P&gt;&lt;P&gt;I have so much redundancy in my system from hardware to software on the capture and backup sides and I guess this is an example for when two things go wrong (user error on dual card setting and corrupt RAW) I still was able to deliver a decent photo to the client... which is pretty good.&lt;/P&gt;&lt;P&gt;Thanks for your input. Will make sure to put dual write back on right now!&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:23:41 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479081#M116405</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T16:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479082#M116406</link>
      <description>&lt;P&gt;You might want to give Canon DPP a look, I have had files that Lightroom / Photoshop cannot work with and appear corrupt, but they do open in DPP. Then I have then been able to edit with DPP and get a 16-bit TIFF image that worked for me in my Lightroom workflow.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:28:51 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479082#M116406</guid>
      <dc:creator>p4pictures</dc:creator>
      <dc:date>2024-05-23T16:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479083#M116407</link>
      <description>&lt;P&gt;I don't have any solutions to offer, but I'm curious. Did the affected CR2 have a suspiciously smaller or larger file size than your other CR2 files? Was the affected file shot as part of a high frame rate burst? Maybe some early weakness showing up in a well used memory card . . ?&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:33:52 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479083#M116407</guid>
      <dc:creator>BurnUnit</dc:creator>
      <dc:date>2024-05-23T16:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479085#M116408</link>
      <description>&lt;P&gt;Oh very cool. I will look into this more. Seems like it could create a better workflow for me as well (current OG CamRanger user)&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:38:41 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479085#M116408</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T16:38:41Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479090#M116409</link>
      <description>&lt;P&gt;These are good questions, thanks for asking. No burst and the file was within range to the others. It was 41.1MB and the range on this shoot was between ~38-63MB at a quick glance.&lt;/P&gt;&lt;P&gt;Also: realized the other card actually WAS recording and dual-write on in 5D IV (dual-write was off in my R6 and got the cards mixed up). So the other copy was fine. Not sure what that means for troubleshooting though. I have used this CF card probably as long as I've had this camera.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:45:32 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479090#M116409</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T16:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479094#M116410</link>
      <description>&lt;P&gt;The uncorrupted version is 50.7MB...&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 16:50:10 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479094#M116410</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T16:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479120#M116412</link>
      <description>&lt;P&gt;Note that as far as SD cards go, micro cards in an adapter are less reliable than full size cards. (Not that this is your issue, but I thought I would throw it out there.)&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 17:10:38 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479120#M116412</guid>
      <dc:creator>kvbarkley</dc:creator>
      <dc:date>2024-05-23T17:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479122#M116413</link>
      <description>&lt;P&gt;I agree. Adapters have always spooked me. Using all "correct" sized cards here. I do use card readers to import instead of a cable direct from camera to laptop so I guess that could be a point of weakness.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 17:17:31 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479122#M116413</guid>
      <dc:creator>disc_count</dc:creator>
      <dc:date>2024-05-23T17:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted CR2 File from EOS 5D Mark IV</title>
      <link>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479126#M116416</link>
      <description>&lt;P&gt;Cables can fail, too. Having corruption while reading is much different than a corrupt file *written* to the card. If you read a corrupt file, it is always a good idea to try a few times with different methods, i.e., new cable, to see if it was a data transfer issue or actual bad data on the card.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2024 17:22:00 GMT</pubDate>
      <guid>https://community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/Corrupted-CR2-File-from-EOS-5D-Mark-IV/m-p/479126#M116416</guid>
      <dc:creator>kvbarkley</dc:creator>
      <dc:date>2024-05-23T17:22:00Z</dc:date>
    </item>
  </channel>
</rss>

