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. âš ī¸

CO Pro v9.1 not saving/restoring some export settings

Comments

14 comments

  • SFA
    Richard,

    I have just tried a quick test along the lines you have described.

    My changes for the recipe were retained as the new values. Now trying to remember to the old ones so I can reset them .... 😉

    Win 7 Pro.

    Sessions. (although I doubt that would make much difference.)


    Grant
    0
  • RichardT
    Hi Grant,

    Thanks for looking into this. I notice that you mention "recipe" - did you test it by using a process recipe in the Output tab, or by right-clicking on an image in the browser and selecting Export -> Variants..?

    It is the latter case that is causing the problem for me.

    In case there was an issue with my upgrade to v9.1, I have just done a complete uninstall and re-install, but the problem still persists â˜šī¸

    Richard
    0
  • RichardT
    After a bit of digging...

    In the folder:
    C:\Users\[username]\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn
    There are 2 sub folders corresponding to 2 versions of Capture One:
    9.0.3.14
    9.1.0.119

    Each sub-folder contains a file "user.config"

    In 9.0.3.14\user.config there is a section:

    <setting name="ExportDestinationProcessingSettings" serializeAs="Xml">
    <value>
    <DestinationProcessingSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SortIndex>0</SortIndex>
    <DefaultValues>false</DefaultValues>
    <ShowAllProfiles>true</ShowAllProfiles>
    <Name>Untitled Recipe</Name>
    <ScaleUnit>Pixels</ScaleUnit>
    <AutoOpenProgramName />
    <AutoOpenProgramPath />
    <ColorProfilePath>C:\Program Files\Phase One\Capture One 9\Color Profiles\Common\SRGB COLOR SPACE PROFILE.ICM</ColorProfilePath>
    <FileType>Jpeg</FileType>
    <TiffBits>8</TiffBits>
    <TiffCompression>tcNone</TiffCompression>
    <TileDimension>-1</TileDimension>
    <SkipThumbnail>false</SkipThumbnail>
    <JpegQuality>76</JpegQuality>
    <Resolution>300</Resolution>
    <ResolutionUnit>ruInch</ResolutionUnit>
    <ScaleType>LongEdge</ScaleType>
    <ScaleFixed>100</ScaleFixed>
    <ScaleLongEdge>1024</ScaleLongEdge>
    <ScaleShortEdge>1500</ScaleShortEdge>
    <ScaleWidthByHeightWidth>1500</ScaleWidthByHeightWidth>
    <ScaleWidthByHeightHeight>1500</ScaleWidthByHeightHeight>
    <NeverUpscale>true</NeverUpscale>
    <ScaleWidth>1500</ScaleWidth>
    <ScaleHeight>1500</ScaleHeight>
    <ScaleSize>
    <Width>1500</Width>
    <Height>1200</Height>
    </ScaleSize>
    <DisableSharpening>false</DisableSharpening>
    <IgnoreCrop>false</IgnoreCrop>
    <DestinationRootFolder>OutputFolder</DestinationRootFolder>
    <DestinationCustomRootFolder />
    <WatermarkType>None</WatermarkType>
    <WatermarkText />
    <WatermarkTextColor />
    <WatermarkTextRelativeSize>false</WatermarkTextRelativeSize>
    <WatermarkImagePath />
    <UpdateDisabled>false</UpdateDisabled>
    <WatermarkHImagePlacement>0.5</WatermarkHImagePlacement>
    <WatermarkVImagePlacement>0.5</WatermarkVImagePlacement>
    <WatermarkHTextPlacement>0.5</WatermarkHTextPlacement>
    <WatermarkVTextPlacement>0.5</WatermarkVTextPlacement>
    <WatermarkImageScale>1</WatermarkImageScale>
    <WatermarkTextScale>1</WatermarkTextScale>
    <WatermarkImageOpacity>0.5</WatermarkImageOpacity>
    <WatermarkTextOpacity>0.5</WatermarkTextOpacity>
    <MetadataIncludeRating>false</MetadataIncludeRating>
    <MetadataIncludeCopyright>true</MetadataIncludeCopyright>
    <MetadataIncludeGPS>true</MetadataIncludeGPS>
    <MetadataIncludeCameraData>true</MetadataIncludeCameraData>
    <MetadataIncludeAllOther>true</MetadataIncludeAllOther>
    </DestinationProcessingSettings>
    </value>
    </setting>


    But in 9.1.0.119\user.config there is just:


    <setting name="ExportDestinationProcessingSettings" serializeAs="Xml">
    <value />
    </setting>


    Richard
    0
  • SFA
    Richard,

    I have what appears to the be same well populated file in both folders.

    Something perhaps did not completely pick up on installation?

    I have parallel installed at this time.

    Try deleting the 9.1 truncated file and re-booting C1 to see if it goes searching. Failing that copy the full version from 9.0.3 to 9.1?

    Grant.
    0
  • RichardT
    Grant,

    I renamed the v9.3 user.config file as user.config.old.

    I then started Capture One. It immediately created a new user.config file. That file contained an "ExportDestinationProcessingSettings" section that was identical to the one in the v9.0.3 file (including my custom export settings).

    However, as soon as I opened the Export Image dialog, the contents of the "ExportDestinationProcessingSettings" section were truncated down to a single "<value />" element. The dialog displayed the default settings for Quality and Scale.

    Subsequent changes to the settings in the Export Image dialog were not written to the user.config file. Nor were they written when I closed Capture One.

    Richard
    0
  • SFA
    Richard,

    Interesting.

    I have used process and changed settings for outputs and the changes have been saved.

    Maybe repeat the experiment but use Process rather then Export to see if you get a different result?

    Since the file is for the entire list of user settings it's a little odd, to my mind, that is is left empty by the process. There must be something else going on.

    Maybe best to establish if it is only Export that gives that result and then create a Support Case?


    Grant
    0
  • RichardT
    Grant,

    The changes I make to a recipe are restored after restarting Capture One.

    The recipes are stored in individual files in the folder:
    C:\Users\[username]\AppData\Local\CaptureOne\Recipes91

    and not in the user.config file where the Export Image dialog settings are stored.

    For some reason I have always preferred using the Export function, rather than Output Process.

    I raised a support case (214706) earlier today.

    Richard
    0
  • SFA
    Hi Richard,

    If I open Export and make a change to the settings the config file (rather long in my case) is updated with a new time stamp but maintains its size.

    So not the behaviour you have described.

    You might try a re-install if you have not done so already?


    Grant
    0
  • RichardT
    Hi Grant,

    The section that has its settings removed is rather small compared to the overall size of the file (59 lines out of 2071).

    Please could you open your config file in a text editor and search for the string "ExportDestinationProcessingSettings" and see if its section contains 50+ settings, or just the single <value /> element?

    Yes, I have tried uninstalling and reinstalling Capture One (including removing the C:\Users\[username]\AppData\Local\CaptureOne folder), but it made no difference.

    cheers,
    Richard
    0
  • SFA
    Ah, I missed the word "section" earlier.

    My files for each version look the same as your. Nothing in the 9.1 initiated file.

    Revised settings persist during the current session but revert to previous settings on exit and restart.

    I now have a 93Mb tiff file to look at having run the export as part of the testing!


    Grant
    0
  • RichardT
    Thanks for checking that out, Grant. It's very useful to know it's not just affecting my machine.

    Yes those TIFF files can certainly eat up a lot of disk space. Luckily I don't need to use them very often 😄

    cheers,
    Richard
    0
  • Cal
    Hi guys,

    Is there something I can do to hold my or save my Export Menu Values as a default? Having them reset each time leads me to miss a setting like the ICC Profile or the File/Root Folder setting.

    Cal
    0
  • RichardT
    Hi Cal,

    I don't think there is anything we can do as users to fix the Export dialog. We need Phase One to fix this so it works like it did in previous versions. I have raised a support case, but I imagine they have received quite a few cases since v9.1 was released. If you were to also raise a case it could increase the priority for fixing this particular problem.

    As a workaround, you could try using a process recipe instead of using the Export dialog.

    Richard
    0
  • BeO
    Top Commenter
    [quote="RichardT" wrote:
    Thanks for checking that out, Grant. It's very useful to know it's not just affecting my machine.


    When I installed 9.3 I did a fresh install on my Win7 machine (complete deinstallataion including manual deletion of the config file (i.e. its parent folder).

    I have the same issue with Export>Variant. Process recipies work fine though.

    Cheers,
    BeO
    0

Post is closed for comments.