Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Let Capture One Pro 10 recognize Photoshop adjustment

AlbertoBedin
Select a raw file -> Edit with -> Adobe PS CC 2017 (tif) -> Add an adjustment layer -> save and close in PS

Now Capture One Pro 10 does not recognize the adjustment layer in the tiff file while Lightroom does.

Is there a way to change this behaviour? I think this is a MUST HAVE feature!
0

Comments

14 comments

Date Votes
  • H. Cremers
    [quote="AlbertoBedin" wrote:
    Select a raw file -> Edit with -> Adobe PS CC 2017 (tif) -> Add an adjustment layer -> save and close in PS

    Now Capture One Pro 10 does not recognize the adjustment layer in the tiff file while Lightroom does.

    Is there a way to change this behaviour? I think this is a MUST HAVE feature!


    Put in an enhancement request via the website.

    I don't think it has much chance. What would be the chances for photoshop to recognize the CO edits?
    0
  • AlbertoBedin
    PS is the standard in photo editing.

    I'm not only talking about adjustments layers, I'm also talking about a layer with transparency and blend mode overlay: it is not recognize at all by Capture one.
    0
  • SFA
    [quote="AlbertoBedin" wrote:
    PS is the standard in photo editing.

    I'm not only talking about adjustments layers, I'm also talking about a layer with transparency and blend mode overlay: it is not recognize at all by Capture one.


    Photoshop is Photoshop and does what Photoshop does.

    If you want Photoshop use Photoshop.

    Capture One is a different product technically and from a different developer. Why would you expect it to be the same?


    Grant
    0
  • AlbertoBedin
    I don't expect that they should be the same: I expect that C1 works together with photoshop to obtain the best from both!
    0
  • dredlew
    [quote="HCS" wrote:
    Put in an enhancement request via the website.

    This has been a well-known issue (for years) that the TIFF support is buggy.

    [quote="HCS" wrote:
    What would be the chances for photoshop to recognize the CO edits?

    Um, all C1 has to do is read the embedded JPG preview in the TIFF-file, which reflects every single edit PS makes. However, C1 apparently tries to read the whole TIFF file to create its own preview which is bound to be inaccurate and resource intensive. Hence, the insanely slow performance in the browser when switching from a Raw file to TIFF or vice versa. Or just open up the import dialog in C1 and browse to a folder with a bunch of big TIFF files in it. You don't even have to select anything, the whole app locks up for several minutes possibly (you better not force quit if you don't want your catalog destroyed), until it can display just a preview thumbnail (you know, like the one that's already embedded in the file). - It's quite ridiculous that this issue has been left unaddressed for years.
    0
  • Grant Kernan
    I use a scanning back that produces a 216 megapixel [650 megabyteTiff] file.
    I can process adjustments layers in PS and I do. Files can get up to 2 or 3 gigabytes with layers.

    But, If I need to print say a 38x52 inch print then I interpolate in C1 because it works so well.

    My working layered Tiff files stay out of C1.

    I place a colour correct flattened Tiff file into Capture and that opens quickly. I can interpolate as long as it does not exceed the 2 gigabyte threshold. It processes quickly too.

    There are some colour moves that need to be made to maintain colour. C1 can maintain the colour...

    BTW these are mostly fine art repro so everything needs to be as good as it gets.
    0
  • Keith Reeder
    [quote="AlbertoBedin" wrote:
    PS is the standard in photo editing.

    I'm not only talking about adjustments layers, I'm also talking about a layer with transparency and blend mode overlay: it is not recognize at all by Capture one.

    Lightroom and PhotoShop speak the same language - they use exactly the same algorithms - Capture One does not, so it's hard to see how this idea might work at all.

    It's therefore a good thing that Capture One doesn't even try.
    0
  • Keith Reeder
    [quote="dredlew" wrote:
    Um, all C1 has to do is read the embedded JPG preview in the TIFF-file

    And that will tell Capture One about PS adjustment layers, transparency, and blend mode overlay data?

    In fact, you seem to be responding to a question the OP didn't ask...
    0
  • AlbertoBedin
    [quote="Keith Reeder" wrote:
    [quote="dredlew" wrote:
    Um, all C1 has to do is read the embedded JPG preview in the TIFF-file

    And that will tell Capture One about PS adjustment layers, transparency, and blend mode overlay data?

    In fact, you seem to be responding to a question the OP didn't ask...


    Reading the embedded JPG is not the solution because it will not help while exporting the tiff from C1.

    The only workaround is to create a flattened layer on PS tiff above the edited one. However this dramatically increases the file size or it duplicates the tiff.

    I'm considering switching back to Lightroom: the possibility to see exactly the same image as Photoshop is better than the Color tools of C1.
    0
  • H. Cremers
    [quote="dredlew" wrote:
    [quote="HCS" wrote:
    Put in an enhancement request via the website.

    This has been a well-known issue (for years) that the TIFF support is buggy.

    [quote="HCS" wrote:
    What would be the chances for photoshop to recognize the CO edits?

    Um, all C1 has to do is read the embedded JPG preview in the TIFF-file, which reflects every single edit PS makes. However, C1 apparently tries to read the whole TIFF file to create its own preview which is bound to be inaccurate and resource intensive. Hence, the insanely slow performance in the browser when switching from a Raw file to TIFF or vice versa. Or just open up the import dialog in C1 and browse to a folder with a bunch of big TIFF files in it. You don't even have to select anything, the whole app locks up for several minutes possibly (you better not force quit if you don't want your catalog destroyed), until it can display just a preview thumbnail (you know, like the one that's already embedded in the file). - It's quite ridiculous that this issue has been left unaddressed for years.


    I find it quite curious that you focus on my reply to the OP's question, rather than to the OP's questions.

    However, i think the policy of P1 and the forum rules state that, that an enhancement request should be logged through the ticket system. Hence, i pointed the OP in that direction.

    Then i brought up the question why it should be logical that company A would understand company B's proprietary edits, while it wouldn't be logical in the reverse.

    I believe that would the OP have brought up the question why product 1 from the same company cannot understand product 2 from the same company, the OP would have had a point. But, between companies, not so much. Still, an enhancement request through the ticket tool is the only way to know for sure.

    The mere fact that CO should just read this or that from a photoshop managed file doesn't mean so much, as it is quite likely not the technical challenge that is getting in the way for this feature to appear. After all, all photoshop would have to do to recognize CO edits is to read the xmp file that belongs to the image file. Couldn't be hard, could it 😄 😄 😄
    0
  • H. Cremers
    [quote="AlbertoBedin" wrote:
    [quote="Keith Reeder" wrote:
    [quote="dredlew" wrote:
    Um, all C1 has to do is read the embedded JPG preview in the TIFF-file

    And that will tell Capture One about PS adjustment layers, transparency, and blend mode overlay data?

    In fact, you seem to be responding to a question the OP didn't ask...


    Reading the embedded JPG is not the solution because it will not help while exporting the tiff from C1.

    The only workaround is to create a flattened layer on PS tiff above the edited one. However this dramatically increases the file size or it duplicates the tiff.

    I'm considering switching back to Lightroom: the possibility to see exactly the same image as Photoshop is better than the Color tools of C1.


    IT is correct and has been explained above that the photoshop information in the TIFF file means nothing to CO until the layers are flattened.

    On a different note, if the ability to work on the same file between two pieces of software is more important to you than CO's colour capabilities, then i do believe Lr and photoshop are your tools of choice.
    0
  • dredlew
    [quote="Keith Reeder" wrote:
    And that will tell Capture One about PS adjustment layers, transparency, and blend mode overlay data?

    You do understand the concept of a file-preview and that it is flattened, yes?

    [quote="Keith Reeder" wrote:
    In fact, you seem to be responding to a question the OP didn't ask...

    I responded to the statements made in the quotes. If you didn't quote my reply, I would have guessed you don't know what quotes are. Maybe it's more an issue with reading comprehension.
    0
  • dredlew
    [quote="AlbertoBedin" wrote:
    Reading the embedded JPG is not the solution because it will not help while exporting the tiff from C1.

    No. The embedded JPG is for preview only.

    [quote="AlbertoBedin" wrote:
    The only workaround is to create a flattened layer on PS tiff above the edited one. However this dramatically increases the file size or it duplicates the tiff.

    No. The TIFF gets (temporarily I guess) flattened on export, there is no need for an extra layer.
    0
  • dredlew
    [quote="HCS" wrote:
    I find it quite curious that you focus on my reply to the OP's question, rather than to the OP's questions.

    Not sure what is curious about that, it's called quoting and replying. The OP can draw his own conclusions from my replies.

    [quote="HCS" wrote:
    However, i think the policy of P1 and the forum rules state that, that an enhancement request should be logged through the ticket system. Hence, i pointed the OP in that direction.

    And I pointed out that this is an longstanding, existing issue (that has been logged already). A quick search of the forum would reveal that but people are lazy so they just start new threads.
    And sure, feel free to log the issue again, I doubt that it'll get any more attention though. It's in the backlog and they'll get to it when they feel like it. - That's literally what it feels like.

    [quote="HCS" wrote:
    Then i brought up the question why it should be logical that company A would understand company B's proprietary edits, while it wouldn't be logical in the reverse.
    I believe that would the OP have brought up the question why product 1 from the same company cannot understand product 2 from the same company, the OP would have had a point. But, between companies, not so much.

    I explained why what you wrote is irrelevant to the issue and not the nature of the problem. Nothing proprietary needs to be read, yet that's exactly what they are trying to do. Hence the inaccuracy.

    [quote="HCS" wrote:
    The mere fact that CO should just read this or that from a photoshop managed file doesn't mean so much, as it is quite likely not the technical challenge that is getting in the way for this feature to appear.

    Again, you are still not getting the basic concept of an embedded file-preview. Does the Finder (or any other application for that matter) read a proprietary file format to display a preview of what's in that file? No, it uses the embedded preview (if available) to display a... preview. And does that preview in Finder show you all the edits you made in Photoshop/Affinity/Pixelmator/etc? Well yes, it does. Because it's a flat, rendered preview of the original content.

    [quote="HCS" wrote:
    After all, all photoshop would have to do to recognize CO edits is to read the xmp file that belongs to the image file. Couldn't be hard, could it 😄 😄 😄

    No. The XMP format may be somewhat open, but it's still largely "proprietary" to the application that created it. While you can share information with a standard like metadata, there is no standard for image editing across the various applications. In order for that to work, every application would have to have the same features, which wouldn't make any sense either.
    0

Post is closed for comments.