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

Styles and Presets not Populating in Software

Kommentare

12 Kommentare

  • Permanently deleted user

    I have the same configuration (Mojave on an old late 2013 MacBook Pro, Capture One 13.1.0.172), and it works with me. All my styles and presets are there.

    0
  • Britton Orrange

    Damn. Alright thanks Robert, I'll keep tinkering and see if anything corrects itself. 

    -1
  • A Photographer

    I have the same issue as Britton.  I'm on an ancient macpro running macOS 10.14.6.

    Under Styles and Presets tool, the User Styles and User Presets are empty.  The presets are present under Library/Application Support/.../Preset60.

    I have tried everything, deleted the presets, preferences, etc. - nothing helped.

    0
  • Kevin McLin

    I have this same issue as well. My user styles are not showing up in the software. They are present in the finder in the Styles folder. I have also tried deleting and remaking the styles. Removing the entire CaptureOne folder in ~/Library/Application Support. Didn't work, neither of them. I have deleted C1 and reinstalled. No dice.

    The interesting thing is that if I make a new user account, then the styles do show up in that account after I make some new ones there. It is only on my normal account that I am having problems.

    Today I did a clean install of the OS (Mac OS 10.15.5, Catalina, same as I had been running before). Rather than installing my applications from the old backup, I installed them all from fresh installers and packages... Yeah, this has been as fun as it sounds.

    So, after all that (it has taken more than seven hours) I still cannot get my user styles to show up. I did fix a couple other weird issues on my system, not C1 related, but my styles refuse to load. I hope C1 will fix this. I really do want to have access to my user-created styles without having to set them up for every new session I work on.

    1
  • Britton Orrange

    Anwar I'm on a MacPro 15 2017, sounds like we aren't correlating much between models. 

    Kevin that sounds like a rough day; thanks for reporting all the avenues you've tried.

    Based off your comment about this working on other user accounts, I checked with my other accounts and it works for me too. There must be some disconnect with our original home folders that just don't communicate properly. My original Admin account is migrated from the last laptop, while other accounts are built fresh with the new systems since they don't carry any baggage.

    My solution for now was to create a new Admin account and transfer over everything to that user. Not the simplest solution, but it's something I could do immediately to get back to normal. Everything seems to be in order after the change.

    0
  • A Photographer

    Thank you everybody for your updates.

    I believe the issue is a new bug (or feature) in the 20.1 build.  I never run any applications under an admin account.  My usual account is an unprivileged standard account. 

    I shall experiment with an admin account.  

     

     

    0
  • A Photographer

    I'm on a MacPro 2009!  I have an RX580 with 8GB to help C1. Perhaps my last desktop Mac.

    0
  • Britton Orrange

    Anwar, the type of user account doesn't seem crucial. I tested it on a standard user and it worked fine. I ended up making a replacement Admin account for the original Admin Account that was acting up. 

    Try just making another standard user account and see if you have similar results.

    0
  • Kevin McLin

    Yes, I concur. I found that if I make another normal user account I could see the styles I create and save in C1. It does not have to be an admin account.

    I pretty much never run as admin. It is a security risk.

     

    0
  • Britton Orrange

    Absolutely agree Kevin. 

    Also I've been in contact with support. Didn't seem like a known bug or anything, but they now know our issue and our current workaround. 

    0
  • A Photographer

    Hi

    I've finally managed to solve the problem.  I got in touch with C1 support who responded very quickly.

    The initial diagnosis was that I might have skipped over a request from C1 to permit accessing ~/Library by requesting permission to access my reminders.  I could see no request for reminders in the system preferences -> privacy tab.

    I tried reinstalling C1 to force it to request permission, but that did not work.  When support requested my logs using the Scripts->Get Logs menu, and the script kept failing it set me thinking.

    I have several disks in my computer - An ssd for the boot drive, 4 * 4TB HDDs in RAID10 configuration for the home drive, a fast NVME drive for my catalogues and the raw files are stored on a separate server connected by 10GB Ethernet.

    The Users directory is actually on the RAID10 drive, so there is a symbolic link in the root directory: /Users to /Volumes/RAID10/Users. I have my home directory under that.

    When I created my account, MacOS created the home directory under /Users which has worked perfectly well for over 10 years through the symbolic link.
    At some point the existence of the symbolic link in the path has caused a problem.
    As the admin user, I changed my home direcory setting in system preferences to use the actual path /Volumes/RAID10/Users/me.

    I logged in, and voilà I could see the user presets and sytles.

    I don't know why I'm able to write to that location from C1, but cannot read from the very same location. I suspect it's some sort of Apple security "feature" interacting with the way user styles and presets are loaded into memory.

    Anyway, it works so I thought I'll update the thread in case somebody else has a non-standard set up like mine.

    Thanks to everybody for the helpful suggestions.

    0
  • Kevin McLin

    Thanks much for posting this. I had a similar issue. At some point (a number of OS updates ago, I don't remember which exactly) my home directory got replaced with a username_1, which linked to my actual directory, username. This was weird, but I never thought to fix it because it didn't seem to cause any problems. Except apparently it did.

    To fix this, I reset the home directory for my account from the link (/Users/username_1) to the actual directory (/Users/username). I had to log out of my user account and log in to my admin account to do this.

    So it looks like the link is definitely the problem. It is very strange that we were both able to write to the directory using the link, but we were not able to read it. That is not the usual way these things tend to work. I would think it was a permission problem, but I checked the permissions and they seemed fine.

    Thanks again for posting the solution. It will be great to have my user styles back again.

    Kevin

    0

Post ist für Kommentare geschlossen.