![]() Secondly: If the new OS has new features and functionality (i.e. It also involves discovering whether all older hardware and connected devices are also still usable. Which way that turns out after a new OS final release may not be entirely evident for a few weeks. Capture One offers a subscription model so we have the option of adopting the Adobe update payment model rather than the perpetual license model if we prefer that method of funding.Īs for the Support of new versions of OS's - there are two major considerations.įIrstly: will the released version of the OS result in breaking software that currently uses some older technology? If there is no problem running older versions of the software then there is no problem for the user using older versions and avoiding an enforced application update to go with the new OS. I understand that if I would want a new version of capture one I need to pay, but to have a software I paid a lot just a few months ago to ask for more money just because of an OS update seems like a robbery to me." "How is it possible that capture one asks for more money for capture one to work when the computer OS is updated. If you then still face problems, maybe you can raise a support ticket to help Capture One to fix the problem, which then could result in a new maintenance release Download the latest version of Capture One, install it and try again.Downgrade your system with the help of a Backup (Timemachine?). ![]() If you want to recover from the situation, I'd see two possibilities: ![]() If you change your OS Version to an unsupported version and you do not know for sure that your (business) critical/important SW is working, it is In the release notes for each version, Capture One describes the requirements and the supported OS versions. Oh, I almost forgot to mention it: There is nobody else to blame than yourself. Otherwise, here in the forum are several reports that the latest version of Capture One v22 works under Ventura? Did you even try to (re)install the latest version? E.g., last year CO v21 got a maintenance release to officially support Monterey. Thread 0 Crashed:: Dispatch queue: -threadĠ python 0x0000000103101293 PyBuffer_Release + 19ġ 0x00007fff24f74a8d data_release_info + 31Ģ 0x00007fff24f25f81 data_provider_finalize + 64ģ 0x00007fff24eebf8d data_provider_retain_count + 74Ĥ 0x00007fff204dadd8 _CFRelease + 474ĥ 0x00007fff24f51cff image_finalize + 103Ħ is it possible that capture one asks for more money for capture one to work when the computer OS is updated.ĭo you have a (reliable) source for that claim? The announcement of Capture One v23, does not exclude a maintenance release for CO v22. > unused shlib _TEXT 7fffde96f000-7fffe1cf3000 r-/r- SM=COW system shared lib _TEXT not used by this process Termination Reason: Namespace SIGNAL, Code 0xb Termination Signal: Segmentation fault: 11 Problem details and system configurationĪnonymous UUID: 34EA0CE8-BDD4-CCC6-1DBE-DE5330A5B79DĬrashed Thread: 0 Dispatch queue: -threadĮxception Codes: KERN_INVALID_ADDRESS at 0xffffffff00000008 Functions such as matplotlib trigger this problem. ![]() ![]() The error message indicates that python quit unexpectedly with the current OS. I upgraded my OS to MacOS Big Sur lately and the Pycharm could not function with my code. ![]()
0 Comments
Leave a Reply. |