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. ⚠️

Brush & Gradient Mask NOT exported!

Comments

15 comments

  • Permanently deleted user
    What do you mean by catalogue : library or session?

    If you mean library I strongly suggest you to avoid using this method...too many bugs for the moment. Wait until it is stable.

    If you work with session as C1 used to work in previous version you should not have this kind of problem (since I avoid working with library I can work with C1 whithout issues), and maybe you should try opening a new session and open the folder containing your images with adjustment layers, maybe you will recover your work.

    My 2 cents

    Best regards
    0
  • ThomasGeist
    Sorry, yes, I meant Library.

    The problem is that as long as you work with a Library, nothing is written outside of the Library, so there is nothing to recover from.

    That is why I exported Originals from my corrupt Library. That process will create the "Capture One" subfolders that contain settings. However, they obviously do NOT contain anything done with Brush and Gradient Mask. Just the Adjustment Layers with their settings that were created.
    0
  • Permanently deleted user
    [quote="ThomasGeist" wrote:
    Sorry, yes, I meant Library.

    The problem is that as long as you work with a Library, nothing is written outside of the Library, so there is nothing to recover from.

    That is why I exported Originals from my corrupt Library. That process will create the "Capture One" subfolders that contain settings. However, they obviously do NOT contain anything done with Brush and Gradient Mask. Just the Adjustment Layers with their settings that were created.


    Ok sorry for you... ☹️
    0
  • ThomasGeist
    Unfortunately I have more bad news:

    The Adjustment Layers that get exported out of a Library are non-functional.
    They show the settings done (like Exposure settings etc.) but even if you paint on them, nothing happens and also no mask will show up. You will need to create a new Adjustment Layer.

    All in all I dare to say the the whole Library section of C1 v7 is totally screwed up and I share Benjamin's recommendation:
    Do NOT use the Library functionality.
    0
  • Paul Steunebrink
    This is really a serious issue.

    By the way, Thomas used the correct term initially: catalog. The Library is the tool, with can show you either the Catalog or the Session.
    0
  • ThomasGeist
    [quote="Paul_E" wrote:
    This is really a serious issue.

    By the way, Thomas used the correct term initially: catalog. The Library is the tool, with can show you either the Catalog or the Session.

    Thank you for the clarification. I changed the term but wherever I wrote "Library" I meant "Catalog".

    IMO Phase One need to completely overhaul the Catalog engine. Much of what Media Pro can do would look great.
    0
  • Permanently deleted user
    [quote="ThomasGeist" wrote:
    [quote="Paul_E" wrote:
    This is really a serious issue.

    By the way, Thomas used the correct term initially: catalog. The Library is the tool, with can show you either the Catalog or the Session.

    Thank you for the clarification. I changed the term but wherever I wrote "Library" I meant "Catalog".

    IMO Phase One need to completely overhaul the Catalog engine. Much of what Media Pro can do would look great.


    Sorry it is my fault on this... 😄

    Anyway, you are definitely right the Catalog system is not ready, as soon as I came back with Session I did not have any issue so far...I hope it is gonna be fix very soon...
    0
  • ThomasGeist
    [quote="Benjamin Didier" wrote:
    ... If you work with session as C1 used to work in previous version you should not have this kind of problem (since I avoid working with library I can work with C1 whithout issues), ...

    Don't be so sure!

    I just had the newly created Session crash and after opening every image is there twice!

    Oh my!
    0
  • Permanently deleted user
    [quote="ThomasGeist" wrote:
    [quote="Benjamin Didier" wrote:
    ... If you work with session as C1 used to work in previous version you should not have this kind of problem (since I avoid working with library I can work with C1 whithout issues), ...

    Don't be so sure!

    I just had the newly created Session crash and after opening every image is there twice!

    Oh my!



    You are cursed!!! ☹️

    If so remove/delete your session database file : xxxx.cosessiondb . Don't worry it will not delete your adjustments (only your session album etc...) and create a new session.
    0
  • Valentin3
    They don't work period when using catalogs.

    If you want to add a new adjustment layer, the changes will be applied globally (like the background layer) instead on the masked area.
    0
  • Paul Steunebrink
    [quote="Valentin3" wrote:
    They don't work period when using catalogs.

    If you want to add a new adjustment layer, the changes will be applied globally (like the background layer) instead on the masked area.

    Hmm, maybe a different issue. You might want to read this:
    viewtopic.php?f=46&t=13172
    about global versus local adjustments when working with layers.
    0
  • Paul Steunebrink
    [quote="ThomasGeist" wrote:
    I had to export all the images in a catalog to recover from a crashed catalog (my goal was to generate the "Capture One" subfolders on export to retrieve image settings in import into a fresh catalog).

    All this is bad enough.

    But I discovered that while Adjustment Layers are exported, the actual Brush and Gradient Mask data is NOT. So all these Local Adjustments are basically lost now.

    C1 definitely needs to export ALL image settings!

    I just reported the issue to Phase One. It is a Catalog/Mac only issue, so with Sessions you should be save.
    0
  • Thomas Geist
    Yes, staying with sessions for now.
    0
  • ThomasGeist
    I haven't checked with 7.0.1, but this issue is definitely solved in 7.0.2
    0
  • Paul Steunebrink
    [quote="ThomasGeist" wrote:
    I haven't checked with 7.0.1, but this issue is definitely solved in 7.0.2

    That's great! Thanks for reporting back.
    0

Post is closed for comments.