Aw: Re: [darktable-user] darktable 4.4.0 released - macOS package corrupt under macOS 13.4.1
Hi Remco, the instructions on the darktable site don't help. The error message says that darktable would be damaged and the only options I am given is to either skip the loading or to move the application to the trash bin. And by the way, on the darktable Website under "Install" / "macOS" it says: "This bundle supports macOS versions starting with 10.14 (Mojave)." Is there a way I can clear my macOS system from any traces of darktable so that I could install it from scratch? Regards, Achim Homepage: achimdittrich.de / achimdittrich.com Instagram: achimdittrich_photography Gesendet: Donnerstag, 22. Juni 2023 um 10:42 Uhr Von: "Remco Viëtor" An: darktable-user@lists.darktable.org Betreff: Re: Aw: [darktable-user] darktable 4.4.0 released On jeudi 22 juin 2023 10:40:42 CEST Remco Viëtor wrote: > On jeudi 22 juin 2023 09:52:42 CEST Achim Dittrich wrote: > > Hi! > > > > To upgrade from my 4.2.1 installation on macOS Ventura 13.4.1, I > > downloaded > > the darktable-4.4.0-arm64 dmg file, opened and dragged it over to the > > application folder - the standard procedure, that always worked fine in > > the > > past. > > This time however, when I try to start darktable, I get the error message > > that the application would be damaged and can not be opened and that I > > shall move it to the bin. > > After proper deinstallation I tried to install it again but that failed. > > > > > > What can I do now? > > Latest versions of MacOS require applications to be signed. The key needed > for that needs to be purchased from Apple (at 100$/year iirc)... So > darktable isn't signed. > > There are ways to make such programs run anyway. A Google search should > help. (Sorry, I'm not an Apple user, so I can't give the details) Follow-up: Actually the darktable site has the instructions here: https://www.darktable.org/install/#macos darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org <>
Re: Aw: [darktable-user] darktable 4.4.0 released
On jeudi 22 juin 2023 10:40:42 CEST Remco Viëtor wrote: > On jeudi 22 juin 2023 09:52:42 CEST Achim Dittrich wrote: > > Hi! > > > > To upgrade from my 4.2.1 installation on macOS Ventura 13.4.1, I > > downloaded > > the darktable-4.4.0-arm64 dmg file, opened and dragged it over to the > > application folder - the standard procedure, that always worked fine in > > the > > past. > > This time however, when I try to start darktable, I get the error message > > that the application would be damaged and can not be opened and that I > > shall move it to the bin. > > After proper deinstallation I tried to install it again but that failed. > > > > > > What can I do now? > > Latest versions of MacOS require applications to be signed. The key needed > for that needs to be purchased from Apple (at 100$/year iirc)... So > darktable isn't signed. > > There are ways to make such programs run anyway. A Google search should > help. (Sorry, I'm not an Apple user, so I can't give the details) Follow-up: Actually the darktable site has the instructions here: https://www.darktable.org/install/#macos darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: Aw: [darktable-user] darktable 4.4.0 released
On jeudi 22 juin 2023 09:52:42 CEST Achim Dittrich wrote: > Hi! > > To upgrade from my 4.2.1 installation on macOS Ventura 13.4.1, I downloaded > the darktable-4.4.0-arm64 dmg file, opened and dragged it over to the > application folder - the standard procedure, that always worked fine in the > past. > This time however, when I try to start darktable, I get the error message > that the application would be damaged and can not be opened and that I > shall move it to the bin. > After proper deinstallation I tried to install it again but that failed. > > > What can I do now? Latest versions of MacOS require applications to be signed. The key needed for that needs to be purchased from Apple (at 100$/year iirc)... So darktable isn't signed. There are ways to make such programs run anyway. A Google search should help. (Sorry, I'm not an Apple user, so I can't give the details) Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Aw: [darktable-user] darktable 4.4.0 released
Hi! To upgrade from my 4.2.1 installation on macOS Ventura 13.4.1, I downloaded the darktable-4.4.0-arm64 dmg file, opened and dragged it over to the application folder - the standard procedure, that always worked fine in the past. This time however, when I try to start darktable, I get the error message that the application would be damaged and can not be opened and that I shall move it to the bin. After proper deinstallation I tried to install it again but that failed. What can I do now? Regards, Achim Homepage: achimdittrich.de / achimdittrich.com Instagram: achimdittrich_photography Gesendet: Mittwoch, 21. Juni 2023 um 17:28 Uhr Von: "Pascal Obry" An: "darktable-user" , "darktable-dev" Betreff: [darktable-user] darktable 4.4.0 released We're proud to announce the new feature release of darktable, 4.4.0! The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-4.4.0 As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: $ sha256sum darktable-4.4.0.tar.xz 8887fc34abd97c4998b0888c3197e0c509d63bdeab2238906915319811f3b080 darktable-4.4.0.tar.xz $ sha256sum darktable-4.4.0-x86_64.dmg 64af00c1ae160a6e95c459260c7789a431bb050f23afc62f87d6f23f3f06ced1 darktable-4.4.0-x86_64.dmg $ sha256sum darktable-4.4.0-arm64.dmg 40e41dcf508398fc67b2bce3441ac80b5dc5886e86cad15cf214530f42bf730d darktable-4.4.0-arm64.dmg $ sha256sum darktable-4.4.0-win64.exe 23a4831ca52c707984b64cc6b9122526e96606ce86b04a0906fe32fd8327d956 darktable-4.4.0-win64.exe When updating from the stable 4.2.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 4.2.x. You are strongly advised to take a backup first. Important note: to make sure that darktable can keep on supporting the raw file format for your camera, *please* read [this post](https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw samples you can contribute to ensure that we have the *full* raw sample set for your camera under CC0 license! Since darktable 4.2: - 2700 commits to darktable+rawspeed - 813 pull requests handled - 97 issues closed _Please note that the darktable documentation is not currently complete for release 4.4 and contributions are greatly appreciated. Please see the [project documentation](https://github.com/darktable-org/dtdocs#contributing) for more information on how to contribute._ ## The Big Ones The following is a summary of the main features added to darktable 4.4. Please see the user manual for more details of the individual changes (where available). - It is now possible to define multiple automatically-applied presets against a single processing module. Each preset after the first will be added to a new module instance immediately after the first instance in the pipeline. To better visualise which module instance corresponds to which preset, the module label will be automatically set to the name of any preset that matches the current module's parameters. If you subsequently alter those parameters, the label will be cleared, unless its parameters match to another preset, in which case it will be changed to the name of the matched preset. If the module label has been hand edited it will never be updated automatically. A new option (preferences > darkroom > automatically update module name) has been introduced to allow this functionality to be disabled. - The default parameters of some processing modules have been reworked to allow them to be more easily used in copy/paste, presets and styles. - Many modules have default parameters based on image metadata or current workflow, for example: - exposure: in a scene-referred workflow, the exposure is adjusted using the Exif exposure compensation value, - denoise (profiled): set based on camera and ISO, - lens correction: set based on camera, lens, focal length, focus distance, - base curve: set based on the camera maker, - white balance: set based on Exif metadata, - orientation: set based on Exif metadata, - color calibration: set based on Exif metadata For all of these modules it is now possible to paste settings while ensuring that the proper image metadata is used to set the module parameters. This is achieved by selecting the "Reset" column in the preset and style dialogs, which makes the module behave as if its reset button has been clicked. When creating or editing presets, a new option, "reset all module parameters to their default values", has been added. Choose this option to auto-add modules to matching images while retaining their default parameters (including any set based on image metadata). This functionality has allowed us to clean up a number of module-specific hacks that previously achieved similar functionality (albeit in a more limited way).
RE: [darktable-user] darktable 4.4.0 released
Thanks developers for spoiling us again with this new darktable version. Special thanks also to Simone Gotti, Bill Ferguson and last but not least Pascal Obry for the immediate support I experienced during my testing of one of the latest 4.3 builds. Marc (Belgium) -Oorspronkelijk bericht- Van: Pascal Obry Verzonden: woensdag 21 juni 2023 17:29 Aan: darktable-user ; darktable-dev Onderwerp: [darktable-user] darktable 4.4.0 released We're proud to announce the new feature release of darktable, 4.4.0! The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-4.4.0 As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: $ sha256sum darktable-4.4.0.tar.xz 8887fc34abd97c4998b0888c3197e0c509d63bdeab2238906915319811f3b080 darktable-4.4.0.tar.xz $ sha256sum darktable-4.4.0-x86_64.dmg 64af00c1ae160a6e95c459260c7789a431bb050f23afc62f87d6f23f3f06ced1 darktable-4.4.0-x86_64.dmg $ sha256sum darktable-4.4.0-arm64.dmg 40e41dcf508398fc67b2bce3441ac80b5dc5886e86cad15cf214530f42bf730d darktable-4.4.0-arm64.dmg $ sha256sum darktable-4.4.0-win64.exe 23a4831ca52c707984b64cc6b9122526e96606ce86b04a0906fe32fd8327d956 darktable-4.4.0-win64.exe When updating from the stable 4.2.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 4.2.x. You are strongly advised to take a backup first. Important note: to make sure that darktable can keep on supporting the raw file format for your camera, *please* read [this post](https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw samples you can contribute to ensure that we have the *full* raw sample set for your camera under CC0 license! Since darktable 4.2: - 2700 commits to darktable+rawspeed - 813 pull requests handled - 97 issues closed _Please note that the darktable documentation is not currently complete for release 4.4 and contributions are greatly appreciated. Please see the [project documentation](https://github.com/darktable-org/dtdocs#contributing) for more information on how to contribute._ ## The Big Ones The following is a summary of the main features added to darktable 4.4. Please see the user manual for more details of the individual changes (where available). - It is now possible to define multiple automatically-applied presets against a single processing module. Each preset after the first will be added to a new module instance immediately after the first instance in the pipeline. To better visualise which module instance corresponds to which preset, the module label will be automatically set to the name of any preset that matches the current module's parameters. If you subsequently alter those parameters, the label will be cleared, unless its parameters match to another preset, in which case it will be changed to the name of the matched preset. If the module label has been hand edited it will never be updated automatically. A new option (preferences > darkroom > automatically update module name) has been introduced to allow this functionality to be disabled. - The default parameters of some processing modules have been reworked to allow them to be more easily used in copy/paste, presets and styles. - Many modules have default parameters based on image metadata or current workflow, for example: - exposure: in a scene-referred workflow, the exposure is adjusted using the Exif exposure compensation value, - denoise (profiled): set based on camera and ISO, - lens correction: set based on camera, lens, focal length, focus distance, - base curve: set based on the camera maker, - white balance: set based on Exif metadata, - orientation: set based on Exif metadata, - color calibration: set based on Exif metadata For all of these modules it is now possible to paste settings while ensuring that the proper image metadata is used to set the module parameters. This is achieved by selecting the "Reset" column in the preset and style dialogs, which makes the module behave as if its reset button has been clicked. When creating or editing presets, a new option, "reset all module parameters to their default values", has been added. Choose this option to auto-add modules to matching images while retaining their default parameters (including any set based on image metadata). This functionality has allowed us to clean up a number of module-specific hacks that previously achieved similar functionality (albeit in a more limited way). - The default workflow configuration option (preferences > processing > auto-apply pixel workflow defaults) has now been adjusted to incorporate the previous chromatic adaptation workflow setting and to include the new sigmoid module. Options are now as follows: - sc
[darktable-user] darktable 4.4.0 released
We're proud to announce the new feature release of darktable, 4.4.0! The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-4.4.0 As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: $ sha256sum darktable-4.4.0.tar.xz 8887fc34abd97c4998b0888c3197e0c509d63bdeab2238906915319811f3b080 darktable-4.4.0.tar.xz $ sha256sum darktable-4.4.0-x86_64.dmg 64af00c1ae160a6e95c459260c7789a431bb050f23afc62f87d6f23f3f06ced1 darktable-4.4.0-x86_64.dmg $ sha256sum darktable-4.4.0-arm64.dmg 40e41dcf508398fc67b2bce3441ac80b5dc5886e86cad15cf214530f42bf730d darktable-4.4.0-arm64.dmg $ sha256sum darktable-4.4.0-win64.exe 23a4831ca52c707984b64cc6b9122526e96606ce86b04a0906fe32fd8327d956 darktable-4.4.0-win64.exe When updating from the stable 4.2.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 4.2.x. You are strongly advised to take a backup first. Important note: to make sure that darktable can keep on supporting the raw file format for your camera, *please* read [this post](https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw samples you can contribute to ensure that we have the *full* raw sample set for your camera under CC0 license! Since darktable 4.2: - 2700 commits to darktable+rawspeed - 813 pull requests handled - 97 issues closed _Please note that the darktable documentation is not currently complete for release 4.4 and contributions are greatly appreciated. Please see the [project documentation](https://github.com/darktable-org/dtdocs#contributing) for more information on how to contribute._ ## The Big Ones The following is a summary of the main features added to darktable 4.4. Please see the user manual for more details of the individual changes (where available). - It is now possible to define multiple automatically-applied presets against a single processing module. Each preset after the first will be added to a new module instance immediately after the first instance in the pipeline. To better visualise which module instance corresponds to which preset, the module label will be automatically set to the name of any preset that matches the current module's parameters. If you subsequently alter those parameters, the label will be cleared, unless its parameters match to another preset, in which case it will be changed to the name of the matched preset. If the module label has been hand edited it will never be updated automatically. A new option (preferences > darkroom > automatically update module name) has been introduced to allow this functionality to be disabled. - The default parameters of some processing modules have been reworked to allow them to be more easily used in copy/paste, presets and styles. - Many modules have default parameters based on image metadata or current workflow, for example: - exposure: in a scene-referred workflow, the exposure is adjusted using the Exif exposure compensation value, - denoise (profiled): set based on camera and ISO, - lens correction: set based on camera, lens, focal length, focus distance, - base curve: set based on the camera maker, - white balance: set based on Exif metadata, - orientation: set based on Exif metadata, - color calibration: set based on Exif metadata For all of these modules it is now possible to paste settings while ensuring that the proper image metadata is used to set the module parameters. This is achieved by selecting the "Reset" column in the preset and style dialogs, which makes the module behave as if its reset button has been clicked. When creating or editing presets, a new option, "reset all module parameters to their default values", has been added. Choose this option to auto-add modules to matching images while retaining their default parameters (including any set based on image metadata). This functionality has allowed us to clean up a number of module-specific hacks that previously achieved similar functionality (albeit in a more limited way). - The default workflow configuration option (preferences > processing > auto-apply pixel workflow defaults) has now been adjusted to incorporate the previous chromatic adaptation workflow setting and to include the new sigmoid module. Options are now as follows: - scene-referred (filmic) -- default - scene-referred (sigmoid) - display-referred (legacy) - None With these new options, the color calibration module and scene-referred module order will be automatically applied for all workflows except "display-referred (legacy)", which will continue to use only the white balance module for chromatic adaptation. The value in brackets represents the default module used for tone mapping (filmic/sigmoid). In the legacy mode, base curve will
