Processing Canon 5D Mark II/Mark III using C1 7.1.2 / 7.1.3

TonicPhoto

• 12. September 2013 18:01

Hello All,
We have run into some issues processing Canon 5D MKII/III RAW files with C1 (ver. 7.1.2 and 7.1.3)

Backstory - Until this past week we had no issues using C1 (7.1.2, or 7.0 in case of MacBook Pro), 2 different MK II bodies (in studio) as well as a rented MK III body; the files we processed were the same size (pixel dimension) as they were shot. We recently purchased a new MK III body and it "seems" this is what triggered this issue.

We have been testing on three different MACs; all are showing the same problem in (7.1.2):
1. Mac Pro Tower
2. iMac
3. MacBook Pro (this is version 7.0; was functioning "correctly" as the 7.1.2 versions)

We can shoot tethered or to a card; problem shows both ways (so should not be cable issue). The native pixel dimensions for MK II files are (5616x3744), MK III files are (5760x3840). These are the dimensions that C1 shows in the metadata menu. We proceed to process the files (recipes are HiRes tif / uncompressed and HiRes jpg / 100% quality), 100% size, etc (we confirmed these settings this morning). Within the process summary (prior to file processing) as well as the final processed file we get the following results:

MK III - process size: 5586x3724 versus 5760x3840(as shot pixel dimensions)
MKII - process size: 5447x3632 versus 5616x3744(as shot pixel dimensions)

it is worth noting after talking to Chris Benes @ DigitalFusion I did the following:

Deleted all preferences, proxies, log files, etc. and installed 7.1.3 on my iMac (copied over 7.1.2.; not a fresh install).

Issue is the same, but different.
MK III results are now: 5651x3768 (processed) versus 5760x3840 (as shot PixDim) - larger than previous test, but still not the "correct" size.
MK II results are the same as before.

We are curious if anyone else has this issue, is there a resolution/answer to the problem, etc.

Thanks in advance for any input.

0

• 

  Paul Steunebrink

  • 12. September 2013 18:04

  Have you considered the automatic lens correction? To disable it set it to Generic or set the distortion slider to zero.

  0
• 

  Doug Peterson

  • 12. September 2013 18:39

  +1 lens correction distortion correction is on. Tell Chris that Doug says he should have known that! (I'm just teasing him – he's a great resource and will undoubtedly hit himself for having missed it)

  0
• 

  Permanently deleted user

  • 12. September 2013 19:04

  This issue sounds definately like the activated lens correction. Please disable Distortion within the lens tab and re-check whether is fixes the issue. If so, you could use the preset from Capture Integration and apply it to each imported image to prevent it from lens correction.

  0
• 

  TonicPhoto

  • 12. September 2013 19:19

  Thanks for the quick responses. The lens correction setting does appear to be the issue. I have tested on two machines so far - setting to "generic" (0% distortion) has fixed the issue on these machines.
  
  THANKS!

  0
• 

  Christian Gruner

  • 12. September 2013 19:21

  [quote="TonicPhoto" wrote:
  Thanks for the quick responses. The lens correction setting does appear to be the issue. I have tested on two machines so far - setting to "generic" (0% distortion) has fixed the issue on these machines.
  
  THANKS!

  
  
  You'll have an option to disable this automatic correction in an upcoming release of CO. Stay tuned 😊

  0
• 

  Edward Caruso

  • 13. September 2013 04:04

  i've used other applications/plugins for years that corrected lens aberrations before it was automated in C1P and Photoshop and it always truncated image size where it had to adjust the image to correct the distortion. many here complained about the default lens correction applied in C1Pv7. it did take Phase One quite awhile to address this issue, hopefully the service release comes out soon.

  0

Post ist für Kommentare geschlossen.