Can I force thumbnails to be rebuilt?

Dave R

• 2010年12月20日 13:12

I am using Capture One 6 Express. When I want to do complex conversion to black and white I use the outpiut module. What I do is specify a 16bit TIFF and in "open with" I specify Silver Efex Pro (the Lightroom "plug in" is in fact a .exe file and opens a stand alone version of Silver Efex Pro), the directory specified is the same as that which holds the original RAW file. All works very well except that on export Capture One seems to generate a thumbnail which is attached to the TIFF. When the processed black and white file is back in Capture One the thumbnail in the browser is still in colour, clicking on this to see the full scale image gives an initial colour image which quickly changes to black and white, that is ok. However, the print module uses the colour thumbnail rather than the processed Black and White image so it is not possible to pre-view properly in the print module. If I delete the Capture One/cache sub directory in the directory holding the black and white TIFF then the next time I open Capture One the thumbnails are rebuilt and the processed TIFF thumbnail is now in Black and White and displays in the print module in Black and White. This is all very well but a bit long winded - question, is there a way to force Capture One to rebuild just one individual thumbnail?
I call these things thumbnails, I assume they are actually full size pre-views like in Lightroom.

Edit
I have now looked a bit closer at the cache file. In the directory .../Capture one/Cache/Proxies there are associated .cof and .cop files for each image, the .cof file is small (10-30kB) and I guess it is the thumbnail in the browser while the .cop file is large (2MB) and I suppose is the full size pre-view. When I export to Silver Efex Pro these cache files are generated immediatly and stored in the target directory before the TIFF file is opened in Silver Efex Pro. When the modified TIFF is opened in Capture One these files are not updated but for some reason the full size display does update to the black and white version. Deleting the .cop and .cof files does cause these to be regenerated next time Capture One opens and everything is then correct but as I saw this is a very convoluted way of getting the files to regenerate.

0

• 

  Paul Steunebrink

  • 2010年12月22日 07:49

  You answered your question correct, in that removing the proxy files starts regeneration, hence updating the preview.
  
  The workflow you describe is not what Capture One was designed for. The thumbnail and preview reflect the RAW or RGB output (TIFF/JPEG) file when opened the first time plus your adjustments. RAW files are considered static, but RGB output files are not. Editing or previewing the RGB files with CO is considered a bonus, not a main target for the program. It allows a photographer to process them in the same raw workflow when necessary. The can come in handy when images of a certain event come from different sources and type of file formats.
  
  The concept is the CO is a sequential input-output processing unit. When you edit your image after output, feed it into CO as new input (with a file name suffix for example).

  0
• 

  Dave R

  • 2010年12月22日 12:43

  Thank's, I will think about that though I think Capture One are missing a trick by not catering for independent plug ins.

  0

投稿コメントは受け付けていません。