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

gradient mask bug

Kommentare

10 Kommentare

  • Joshua
    I'm not seeing this bug (same version), Bob. Just tried it, created a gradient mask, quite C1. Reopened and it was there.
    0
  • Paul Steunebrink
    Hi Bob,

    I am not able to reproduce the issue. I have tried both session and catalog. CO Pro 7.1.1, OS X 10.8.3

    Do you have it in session and/or catalog? What is your software version and raw file?

    Tips, 2 different scenarios.
    - try to close and reopen the session/catalog without quitting CO7
    - try to close the session/catalog, next quit CO7, next start CO7, and open session/catalog.
    And:
    If you use catalog, do a verify.
    Both session and catalog, do a OS X repair permissions
    0
  • picman2
    Thanks to both for the replies! Here is some more information

    I am working in OSX 10.6.8 on a MacPro 12-core, 2x2.93 GHz 6-core Intel Xeon
    C1 version 7.0.2 (v65084)

    I went to 7.1.1 but (a) that did not solve the problem and (b) that moreover created another problem which I explained in the thread

    viewtopic.php?f=46&t=14187

    Paul: I do not use catalogs and I basically have only one session. I open all my files from folders in the Library tab.

    I have repaired permissions but that did not change anything.

    The adjustments also disappear when I close the session, do not close C1, and then reopen the session.

    Cheers, Bob.
    0
  • Jonathan Gilbert
    Use 7.1.1 and create a NEW session. If you use the old default session from 7.0.2 many old bugs can carry over.

    We also suggest upgrading to OS 10.7.5... this will be much more stable with Capture One.
    0
  • alessandro ceccnoi
    [quote="picman2"] wrote:
    Thanks to both for the replies! Here is some more information

    I am working in OSX 10.6.8 on a MacPro 12-core, 2x2.93 GHz 6-core Intel Xeon
    C1 version 7.0.2 (v65084)
    /quote]

    Bob, why are you still using 6.8?? There is really no reason not to upgrade to a much newer system. Lion and M Lion have made some drastic changes.
    0
  • Permanently deleted user
    I don't have any problems in masking with OS 10.8.3 and C1 7.1.1. until now.
    I think I had some random issues in local adjustment with OS 10.6.8 and C1 7.
    I think OS 10.6.8 has some issues with C1 7s. We can't blame too much for these issues regarding older OS, to C1...
    Also make sure that you have enough ram and not too many images in the capture folder. I used p65 and old 2008 Mac Pro with 18 ram. And ...keep the images in the capture folder(or any folder) less than 500.... Try to turn off other software as much as possible. I'm trying to give at least 10 ram to C1.
    0
  • picman2
    Thanks again all for the replies. You are all right, it is a 10.6.8 problem. I installed 10.8.2 on another internal HD and there the problem did not occur. I guess I'll (reluctantly) have to make the move. One reason I kept with 10.6.8 is that I am also a Protools 10 HD (music software + hardware) user and that simply runs much better on 10.6.8. Hence I'll just make two startup disks with 10.6.8 and with 10.8.3. Unfortunately, the second problem to which I alluded is not gone, also not in 10.8.3 and with 7.1.1. Oh well, hopefully a new version will solve it.

    Cheers, Bob.
    0
  • picman2
    Jon, you are also right. Even in 10.6.8, creating a new session seems to have solved the problem. It still shows some quirks and I haven't checked all files. I'll keep you posted.

    Cheers, Bob
    0
  • SFA
    Bob,

    I know little about Mac file systems but I assume the basic workings of C1 are architecturally about the same on Mac as they are in Windows machines - cos, cop files and so on.

    On that basis ...

    when you create a mask for a layer C1 7 creates a comask file as well as a cos file for the general edits. Your problem description sort of suggests that for some reason there can be a problem with creating or accessing the comask file, either every time or sometimes.

    Alternatively, if the problem is frustratingly erratic, there may be some sort of error in the session or catalog database that links all of the files together into a single user access "view".

    For example last weekend I saw a problem whereby C1 would freeze simply changing between images in the browser using the keyboard arrow keys (this on Windows of course but there is n reason why similar problems on Mac might not prsent in a similar way).

    1400+ images in the folder and I also noticed that one seemingly unrelated image showed a bad thumbnail. Later after regeneration of the previews it still looked bad so I decided to check the cos file. Something about it looked a little strange so I deleted it and then created a new edit for that image. Both problems, bad thumbnail and the "freezing" of C1 were solved.

    Now I don't know what caused the original problem but though very rare it is not entirely unheard of for an operating system to have a glitch writing a file once in a while. I assume that, or some problem in another as yet unidentified process, caused the file corruption and in effect scrambled the internal links in the session database.

    I suspect your mask problem may also have a cause related to either incorrect files and scrambled database links or a system permissions problem. On the balance of the progress you have made it sounds like permissions may be excused at this point (you have some images that appear to be working as expected?) so a dodgy edit file somewhere may be the prime suspect. It might not be one that is obvious.

    Of course your problem may be nothing like the one I had but it's a line of investigation that is worth considering even if only to eliminate it.

    HTH.


    Grant Perkins
    0
  • picman2
    Hi Grant,

    Thanks for your extensive explanation and insight. This is certainly something I will have to look into. I'll be off my computer for a while now, but when I get back to it I'll do some more testing and checking.

    Cheers, Bob.
    0

Post ist für Kommentare geschlossen.