Adjustments with a Process Recipe Selected

Tom de Meadows

• March 19, 2016 21:22

Just looking to understand better how C1 works, I recently noticed the following by accident: I was adjusting a raw file in C1 with a process recipe selected, the process recipe has an sRGB profile embedded and generates a JPG for online use; I accidentally changed the process recipe to a recipe with ProPhoto RGB profile embedded, this profile generates a full resolution TIFF, after changing the process recipe the look and feel of the image noticeably changed. So, having still more experience with Lightroom than with C1, I have 3 questions:

1) Does this mean that adjustments are soft proofed on the fly for the profile of the selected process recipe?
2) I understand that C1 uses internally ProPhoto RGB, does this mean that to have a 'neutral'/'internal' view I need to use a profile with ProPhoto RGB selected?
3) Does this mean that I need a variant for each intended output profile with each variant requiring it own set of slightly different adjustments?

0

• 

  SFA

  • March 20, 2016 00:10

  1) Yes.
  
  2) Your call.
  
  If you want to you can set the Proof Profile selection to None
  
  Or a Specific Profile.
  
  Or to use whatever the currently selected Process Recipe has set within it.
  
  3) It depends on what you need to achieve but potentially you might need that anyway.
  
  In which case (multiple output requirements for different media perhaps?) you might be looking at processing to a file specifically set for the different requirements rather than always going back and processing from the RAW. This would be especially true if you want to absolutely fix something to be repeatable. Re-interpreting from the RAW has advantages but is not guaranteed to be totally fixed and time passes and new methods of processing are introduced. It has always been thus, of course.
  
  
  HTH.
  
  
  Grant

  0
• 

  Tom de Meadows

  • March 20, 2016 17:18

  Thanks Grant. It is a slightly different way of working from what I am used to but don't have a problem with adapting the workflow accordingly. This still leaves open the question of how to organise a catalogue to cleanly handle having more than one derivative per raw files.
  
  My current catalogue is structured as follows:
  
  Raw Files
  ----2016
  ----------2016-03
  --------------------2016-03-20
  ----------------------------------Raw File 1
  ----------------------------------Raw File 2
  ----------------------------------...
  ----------------------------------Raw File n
  --------------------2016-03-21
  ----------------------------------Raw File 1
  ----------------------------------Raw File 2
  ----------------------------------...
  ----------------------------------Raw File n
  C1 Derivatives
  ----JPG
  ---------2016
  ---------------2016-03
  -------------------------2016-03-20
  --------------------------------------Raw File 1 JPG Derivative 1
  -------------------------2016-03-21
  --------------------------------------Raw File 1 JPG Derivative 1
  --------------------------------------Raw File 2 JPG Derivative 1
  ----TIFFs
  ---------2016
  ---------------2016-03
  -------------------------2016-03-20
  --------------------------------------Raw File 1 TIFF Derivative 1
  -------------------------2016-03-21
  --------------------------------------Raw File 1 TIFF Derivative 1
  --------------------------------------Raw File 2 TIFF Derivative 1
  
  It is structure that way for 2 reasons:
  
  a) The JPG folder automatically gets upload to a website
  b) A bad habit from the dates I used to write code
  
  Any thoughts?

  0

Post is closed for comments.