Skip to main content

Capture One 23 (16.2.3) release notes

Comments

4 comments

  • Per Borjesson

    Seems to me that Mac bug fixes are copied from 16.2.2

    0
  • Denis Huk
    Moderator

    Thanks Per Borjesson, updated.

    0
  • syborg

    I wonder if these anonymous crash dump submissions are ever analyzed on a dev side, or just go to some black hole.
    Managed to stay stable for about 7 minutes.
    Using this application is like walking on a minefield. Every time I click some tool I hold my breath - will it crash? I can imagine how professional photographers feel when their income and reputation depend on this piece of code... Why this exception is "unhandled"? May I suggest reading this https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/exceptions ?

    ffs...

                                                            **| The process was terminated due to an unhandled exception.
                                                            **| Stack:
                                                            **| at ImgCore.ImgCoreDll.ICP_GetAutoSettings(ImgCore.ImageCoreProcessorHandle, ImgCore.IC_ProcessSettings ByRef, ImgCore.IC_AutoFeature, IntPtr ByRef)
                                                            **| at ImgCore.ImgCoreDll.ICP_GetAutoSettings(ImgCore.ImageCoreProcessorHandle, ImgCore.IC_ProcessSettings ByRef, ImgCore.IC_AutoFeature, IntPtr ByRef)
                                                            **| at ImgCore.ImgCoreDll.ICP_GetAutoSettings(ImgCore.ImageCoreProcessorHandle, ImgCore.IC_ProcessSettings ByRef, ImgCore.IC_AutoFeature, ImgCore.IC_AutoProperty[] ByRef)
                                                            **| at P1.C1.ImageCoreWrapper.ImageCore.ImageCoreProcessor.GetAutoSettings(P1.C1.ImageCoreWrapper.ICProcessSettings, ImgCore.IC_AutoFeature, ImgCore.IC_AutoProperty[] ByRef)
                                                            **| at P1.C1.Components.AutoAdjust.AutoAdjustHelper.CalculateAutoAdjustments(System.String[], System.Func`2<ImgCore.IC_ProcessSettings,ImgCore.IC_ProcessSettings>)
                                                            **| at P1.C1.Components.InspectorTools.VariantPropertyAutoAdjuster+<>c__DisplayClass9_0.<Adjust>b__0(P1.C1.Components.AutoAdjust.AutoAdjustHelper)
                                                            **| at P1.C1.Components.VariantProcessHelper.AutoAdjust(P1.C1.Core.ModelEntities.ICoreImageAvailabilityChecker, P1.C1.Core.ICoreVariant[], System.Func`2<P1.C1.Components.AutoAdjust.AutoAdjustHelper,Boolean>, P1.C1.ModelEntities.UndoInterfaces.IUndoManager, Boolean, Boolean)
                                                            **| at P1.C1.Components.VariantProcessHelper.AutoAdjust(P1.C1.Core.ModelEntities.ICoreImageAvailabilityChecker, P1.C1.Core.ICoreVariant[], Boolean, System.Func`2<P1.C1.Components.AutoAdjust.AutoAdjustHelper,Boolean>, P1.C1.ModelEntities.UndoInterfaces.IUndoManager, Boolean, Boolean)
                                                            **| at P1.C1.Components.VariantProcessHelper+<>c__DisplayClass5_0.<AutoAdjustAsync>b__0()
                                                            **| at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
                                                            **| at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread)

    0
  • SFA
    Top Commenter

    syborg,

    If you have a repeatable problem the best advice is to use the "Request Support" link near the top of every page and create a Support Case with Capture One.

     

    The Automatic Crash reports provided by Microsoft, Apple, etc, never ever create any sort of support operation but may be used in some sort of statistical analysis sometimes. Maybe.

     

    If you have a repeating problem that results in a crash that is "not trapped" then something somewhere within your installation is not seeing data that it knows what to do with and that is not trapped by any operating system controls being used.

    It could be anything.

     

    In my experience of using C1 on Windows I can only remember one instance of such a repeating problem, back in V7, and that turned out to be a corrupt file fragment that had been written to disk with an incomplete name and was, about once every 10 images, delivered incorrectly to the processing engine by the Operating System, loading it with data that was inappropriate for the field it claimed to be populating. 

    It was tricky to spot, but eventually I identified a possible problem image edit file, deleted it and re-edited the image and all was well. Such things are not unheard of but they are rare. As are similar problems that do not present themselves in a way that may become visible eventually.

    The support Team can help to identify the problem or perhaps just provide guidance on the best way to move forward and eliminate the problem without spending a lot of time looking into the details of something that might be a one-off glitch unlikely to be seem again.

    1

Please sign in to leave a comment.