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

Can "Proof Margin" and other Viewer-Display-Settings not be saved in a custom workspace anymore?

Permanently deleted user

Dear community,

I have searched the forum and the current user guide in regard of this issue. However, I have not found a answer to my questions so far.

I have just upgraded from Capture One 11 Pro to the current release of version 21 (14). I am used to switch between custom workspaces I have created over time. Using now Capture One Pro 21, I notice that some viewer settings are not saved in a workspace anymore. Here are two examples:

* The activation/deactivation of proof margin (viewer setting)

* the activation/deactivation of displaying the camera data etc. on the bottom of the image (viewer setting)

Is this really so, that you cannot save viewer settings in a workspace anymore? I tried it in my imported old workspaces and I also tried it by creating new custom workspaces. Many thanks for sharing your experiences in this manner.

Kind regards,
Patrick

0

Comments

6 comments

Date Votes
  • SFA
    • Edited

    I can't speak for Macs as I use Windows but the settings you mention are user runtime configurations.

    For Windows they are in a user.config file. I believe the Mac equivalent is plist.

    Each C1 INstallation and each user of that installation will have their own user.config file in Windows.

    Within the file  C1 keeps a record of the most recent user preferences applied for each individual Catalog and session recently opened. I have never tried to work out whether there are cut-off points applied for removing settings data related to catalog or session settings but I suspect there would have to be something for sessions. Users working with just one or two catalogs may have no need for any built-in automatic "housecleaning" since the updates are dynamic and therefore automatically "saved" upon exit.

    If you are not seeing that result I can think of 3 possibilities to consider - untested by me since in part there may be differences between Mac and Windows.

    1. For some reason when you restart C1 or open a new session/catalog the system is not re-reading the previous version of the file OR is replacing it with an older iteration that happens to contain different settings.

    2. If forcing a "new" session or catalog on opening - i.e. not re-opening a previous activity with its "last known state" for that user - you may end up with default settings that are not what you are expecting. 

    3. If the settings are not appearing in different workspaces - even personal Workspaces that have been saved with non-default "View" settings - are not appearing as you expected them to then further investigation may be required. Without taking a deeper look, which I do not have time to do right at this moment, I am not sure what might be the expectations for that.

    I cannot recall reading about anything that has been specifically changed in this area of functionality but I may well have missed something or changes may have been applied without being specifically mentioned. That would be quite rare for GUI functionality in general but this is a more specific and possibly less widely used requirement and so information may not have hit the mainstream information feeds even if changes have been implemented.

    0
  • Permanently deleted user

    Dear SFA,

    Many thanks for your very prompt and detailed answer. Very kind of you!

    You are right. In macOS C1 saves the workspaces in *.plist-files. They are stored here: /Users/<username>/Library/Application Support/Capture One/Workspaces.

    I can still change something in a current workspace and save it. This functionality is perfectly working. But I think, that it is no longer possible to include certain viewing settings in a custom workspace.

    Example: I used to have a workspace for selecting images and another for developing files. I configured the second workspace for example by activating the proof margin and by deactivating the metadata information below each image in the viewer. These settings were definetly also saved in the custom workspace - well, at least until Capture One 11.

    With Capture One 21 I have tested this issue on two installations (both macs). It seems to me, that you can no longer save viewer settings as such in a custom workspace. This is no major issue, of course. Still I was wondering why Capture One would exclude the option of saving viewer settings in a custom workspace? I thought, maybe I have missed something on the way, because I was working until now in version 11.

    Have a good eveing.

    Kind regards,
    Patrick

     

    0
  • SFA

    Hi Patrick,

    I've taken some time to go back through some of the Workspace definitions saved on my older machine for several versions back to V9 and none of them seems to have any instructions related to visibility of any of the "View" variables for the Viewer other than the Toolbar setting.

    The settings for all managed variables are boolean  - so listed as either "true" or "false" and therefore I think it is reasonable to assume that all managed variables within the Workspace definitions are shown in all cases. In other words there are no settings that only appear if a value is changed.

    Now the caveat is that I am using Windows and there is a possibility that this can be handled differently for Macs, but I'm not sure that would be a good way to go even if technically possible. That said I seem to recall that there are some differences in these sorts of areas and something at the back of my mind keeps nudging me into a vague memory that the Workspace Definition Files are not shareable between Mac and Windows. I may be wrong - it might have been something else.

    So everything I can see points to the "View" menu dynamic settings being the controlling factor for labels and margin and, presumably, multiview.

    Maybe it is worth considering setting up some keyboard shortcuts?

    Can Applescript be used to toggle the settings for all of those in which one is interested at the same time?

    0
  • Permanently deleted user

    Dear SFA,

    Again, many thanks for your effort and help. Very appreciated.

    I have played a little by editing the workspace-plist-files in BBEdit, but I did not succeed. Well, this is no mayor problem for me. You are right. It would be probably a good opportunity to use some custom keyboard shortcuts. And yes, I think it would be even possible to use Applescript, if I was keen enough to do so.

    So, again, thank you for your time and help.

    Have a good evening.

    Kind regards,
    Patrick

    0
  • SFA

    Hi Patrick,

    I think the settings are controlled only by the user.config file in Windows and so, presumably, by its equivalent function for the Macs.

    The more I think about it the more I think that extending the Workspace settings to allow setting such values as defaults could be useful. Maybe the simple approach would be to allow a number of default settings options to be applied automatically for new sessions and catalogues as they are created - and perhaps used as a "reset" at other times if required.

    Perhaps not something that is critical functionality for most users but certainly a "nice to have" concept if there happens to be a fairly simple way to provide it. 

    0
  • Permanently deleted user

    Hi there,

    This change is apparently by design. Here is what Phase One Support has answered me:

    Hi Patrick,

    I double-checked this with R&D and the current behavior is by-design.

    I have forwarded your comments on saving the Proof Margin preference in a workspace to our Product Management team as something to consider in a future release. Hopefully your feedback contributes towards a future version of Capture One.

    And thank you for this feedback on Capture One - we appreciate the time you've taken to contribute towards the development of the software.

    Denis,
    Capture One Support.

    Kind Regards,
    Patrick

    0

Post is closed for comments.