Leeway of CO when manipulating 16bit TIF
hi there,
i just wanted to quickly check for your feedback. for some particular files i need to leave CO and do the raw dev in some other software. i'm bringing back a 16bit TIF, which should yield enough information to allow me to integrate with CO and do my sharpening, grading, b/w, styles, cropping and final output along with my other files.
however i feel that any changes to the TIF (small exposure changes, contrast, brightness) do NOT work as efficient and with equally great results. the odd thing is that the same file in photoshop is able to be shaped and bent... just CO feels very limited with TIF.
is anyone else having these issues? is there any particular format you'd recommend to have the "optimal" TIF for CO processing?
thanks for your feedback,
best
t
i just wanted to quickly check for your feedback. for some particular files i need to leave CO and do the raw dev in some other software. i'm bringing back a 16bit TIF, which should yield enough information to allow me to integrate with CO and do my sharpening, grading, b/w, styles, cropping and final output along with my other files.
however i feel that any changes to the TIF (small exposure changes, contrast, brightness) do NOT work as efficient and with equally great results. the odd thing is that the same file in photoshop is able to be shaped and bent... just CO feels very limited with TIF.
is anyone else having these issues? is there any particular format you'd recommend to have the "optimal" TIF for CO processing?
thanks for your feedback,
best
t
0
-
Short answer: yes, adjusting processed images in Capture One is limited compared to what you can do to raw images and compared to what you can do in Photoshop (and similar pixel editors) with processed images.
Capture One is primarily a raw processor (and workflow application).0 -
@Paul
In my experience C1 seems to be incredibly slow as soon as some TIF images come into play. While it seems to work for simple single layer I can easily make C1 unusable by saving Affinity Photo layered TIF and AFAIR also Photoshop layered TIF. C1 will then take minutes to render the image sharp and it will show a crash screen if one closes the program. This is not a new problem it is now since several releases and I already reported it0 -
[quote="Neonsquare" wrote:
@Paul
In my experience C1 seems to be incredibly slow as soon as some TIF images come into play. While it seems to work for simple single layer I can easily make C1 unusable by saving Affinity Photo layered TIF and AFAIR also Photoshop layered TIF. C1 will then take minutes to render the image sharp and it will show a crash screen if one closes the program. This is not a new problem it is now since several releases and I already reported it
I think you are expecting C1 to use C1 for work that it is not really developed to do.
As far as I can recall the editing of layered TIFF files is not currently supported and they need to be processed to flat files first.
Personally I can't see a lot of point, other than some basic DAM work maybe, in bringing files that have been significantly edited in PS or Affinity back into C1 for further processing. I may have missed something of course.
And yes, if you close an application somehow (you don't say how) when it seems to be in the middle of processing something it is quite likely to crash and probably leave some sort of mess behind. Not a great idea unless absolutely necessary for some important reason.
Grant0
Post is closed for comments.
Comments
3 comments