Zum Hauptinhalt gehen

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

C1 Changes Looks by itself

Kommentare

10 Kommentare

  • Josef Beyer

    i was asked a few questions, that i can already share here too:
    right click on the thumbnail (for example in order to render a new preview) already changes the file.
    the faders / adjustment do not move when C1 makes the changes - the same values are just shown differently.
    not always are the layers deleted, just sometimes all the layers disappear too.
    its not looks from older versions or sessions, it happens all in the same session, just a bit later after the first settings were done

    maybe these extra information help you.

    Thanks!

     

    0
  • Permanently deleted user

    Hi Josef,

    just a guess: do you have any additional controllers or input devices installed? If yes, maybe they trigger some action?

    Kassur

    0
  • Permanently deleted user

    Josef,

    Are your layers disappearing entirely? Or are your masks being emptied. For example, you have a gradient mask on a layer, then when your image changes, the gradient is gone but the adjustment layer remains?

     

    0
  • Josef Beyer

    Thank you both!

    There is no external device that can trigger any action. Thag was a good idea, but it is not the case.

    Gerald, the layers disappear entirely. Not only the adjustments in them, the whole set of layers are gone when this Problem Starts.

    0
  • Permanently deleted user

    Josef,

    That looks very weird, I can't reproduce it, and I would suggest to record a screen video shot and send it to the Capture One staff using the "Submit a request" link at the top right corner of this page.

    0
  • Permanently deleted user

    Josef,

    Okay good to know. I've been experiencing an issue where C1 will empty layer masks randomly. The layer and adjustments remain, but I have to re-make al the masks (gradients, luma range, brushed etc.), which is very time consuming. I've submitted service requests to C1 several times over the past 2 years, but they say they can't help because they can't duplicate the issue. 

    I would also echo Robert on the submitting a request. They will also want you to provide your COLlogs.

    0
  • Josef Beyer

    thank you Robert and Gerald!

     

    yes, i already filed a request to the C1 Team, but i got an automatic reply that it will take a long time because the team i from the Ukraine and has can't answer as usual, of course.

    but on this project we work for a high profile celebrity and i hoped to get rid of the problem as soon as possible...

    I have the feeling that some adjustments in the settings are set to "auto" - for example the Shadow Tone of the Dehaze Tool. Maybe this one produces some changes after a while when we come back to files that we adjusted earlier and when we click on the file one of these auto settings uses a new default point and makes some changes to the look. but i am not 100 percent sure, because many files in different folders have these Auto settings and it happens only to a few created looks in some folders. 

    i will do more research tomorrow and i also hope that someone has a few ideas for a possible solution. 

    thanks to everyone so far!

    josef

     

    0
  • Permanently deleted user

    Hi Josef,

    you are apparently using sessions. Have you tried to use a catalogue to see if the issues are there as well?

    A very, very wild guess - do you by any chance synchronise folders with sessions or is it a shared drive on a network accessed by multiple users? If yes, try to work for a while from a local folder, just to be able to rule out an issue outside of C1.

     

     

    0
  • Bonny Sadr

    Sounds like some caching issue? Honestly, I don't think I have ever run into this kind of problem before, hence I think it's some cache issue. 

    Maybe you have an app running that is conflicting with Capture One? The first thing I would suggest you do is to make a copy of Capture One settings (User/Library/Application Support/Capture One).

    Secondly, clean uninstall Capture One. Then quit all running applications and the ones running in the background.

    Third, reinstall Capture One and make sure no other program is running. Keep testing and see if the same issues happen again... If they don't, make a copy of the default Capture One settings (step one) and then replace the Capture One settings you copied in step one and test again. If the issues come back then you know that something is wrong with one of the settings. If not, restart the usual applications you usually run when Capture One is running but 1 by 1, and test after each application you are restarting to see if one of those apps is causing the issues you are facing. 

    If your issues still persist then I don't know

     

    Good luck

    0
  • Josef Beyer

    hi Jiri and Bonny.

     

    The Session is not on a shared Folder, it happens Local.
    And it also happens on older Capture Versions o other Computers, so the Cache is not the Issue.

     

    I did a lot of experiments and so far i have a good guess about one of the problems:

    It seems that the Dehaze Tool has an Automation Setting for the Shadow Tones as a reference. When we create a look and apply it to other Pictures everything is fine at the beginning, but it seems like sometimes C1 decides for a few Pictures with a certain Look, that the Shadow Tone Reference for that Picture should be something else. As soon as we click on the thumbnail of the Picture it loads another Tone and thats when the whole appearance of the Picture changes drastically. 
    That would explain why we don't see adjustment sliders moving, but get another look on the files.

    So we think that we need to set this Shadow Tone to manually mode before applying the look to other files and maybe that gives us some freedom in the future.

    I will do more research on this and will let you know if this is the solution.

    It doesn't solve the problem with the deleted Layers, but this Problem doesn't happen very often (at least...)

    THANK YOU EVERYONE!

    Josef

    0

Post ist für Kommentare geschlossen.