Re: [darktable-user] darktable 4.2.1 released
Le 25/02/2023 à 22:34, tony Hamilton a écrit : Thanks for the suggestions. With respect, your observation is clearly easy for you to say, but (and I have a LOT of experience on this) not so easy for me to do. The explanation (aside from the opinion oft expressed by others that I'm chronically, endemically and terminally stupid) is indeed simple: those who write the instructions on how to compile have to write for a general audience and so make assumptions - sadly often wrong - about my computing environment and my ability to comprehend those instructions. The latter factor reflects the fact that they are written by obviously technically competent authors who are also subject matter experts (but not necessarily writers), writing for people like themselves - who, by very definition, do not need such instructions. Those instructions are, in consequence, usually inaccessible and inapplicable to people like myself. A significant part of the compile process is the handling of compilation errors; here the documentation is frequently inadequate, depending on a level of detailed knowledge and understanding which is beyond the average Linux application user. They are typified by impossible to parse scenarios which have an explanation of the nature of: "Oh, didn't we tell you about dependencies abc, hij, opq (which is incompatible with def, as long as you have, or, possibly, have not, included rst) and xyz (but not in version 2.99)? Sorry about that." Oh, maybe I'm just too old and lacking a sense of humour On 25/02/2023 15:19, Patrick Shanahan wrote: really building is simple and instructions are provided on github. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org Hello Tony, Assuming you are running Ubuntu, here is a working process I used, based upon the instructions on GitHub together with help kindly provided by people on this list : # Prérequis : Dépendances # sudo apt -y install gcc g++ cmake intltool xsltproc libgtk-3-dev libxml2-utils libxml2-dev liblensfun-dev librsvg2-dev libsqlite3-dev libcurl4-gnutls-dev libjpeg-dev libtiff5-dev liblcms2-dev libjson-glib-dev libexiv2-dev libpugixml-dev exiv2 libexiv2-27 libgmic1 libheif1 libraw20 checkinstall # Clônage du dépôt GIT ## git clone --recurse-submodules --depth 1 https://github.com/darktable-org/darktable.gitcd darktable git fetch --tags git checkout tags/release-4.2.1 # the version you intend to build # Récupération des sous-modules ### git submodule update --init # Build manuel # mkdir build/ cd build/ cmake -DCMAKE_INSTALL_PREFIX=/usr/ .. make sudo make install # or sudo checkinstall This will install dt in /usr instead of /opt, so you first might have to uninstall dt before : sudo apt -y autoremove darktable Should this help. Rgrds, J.-Luc darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] darktable 4.2.1 released
Not sure if the OBS repository is maintained any more... On 2/22/23 10:45, Pascal Obry wrote: We're proud to announce the new bug fix release of darktable, 4.2.1! The github release is here: [https://github.com/darktable-org/darktable/releases/tag/release-4.2.1](https://github.com/darktable-org/darktable/releases/tag/release-4.2.1). As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: ``` $ sha256sum darktable-4.2.1.tar.xz 603a39c6074291a601f7feb16ebb453fd0c5b02a6f5d3c7ab6db612eadc97bac darktable-4.2.1.tar.xz $ sha256sum darktable-4.2.1_arm64.dmg d037a23e8b37f6971a1f2b7c4cf3e03647b168ad2fb43080761d7a307b43048d darktable-4.2.1_arm64.dmg $ sha256sum darktable-4.2.1_x86_64.dmg 993a29685397c6e1a429d84be578da9271eefc06d2c75c10818ffc00b7d04a00 darktable-4.2.1_x86_64.dmg $ sha256sum darktable-4.2.1-win64.exe 31c4d6c522818eda87e48df44f267afd531339ef9d374fa02d44891e3755f7b5 darktable-4.2.1-win64.exe ``` When updating from the stable 4.0.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.0.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.0: - Almost 300 commits to darktable+rawspeed - 89 pull requests handled - 18 issues closed ## The Big Ones - N/A ## Other Changes - JPEG files are identified using magic bytes instead of file extension. This helps in cases where JPEG images end up in files with unexpected extensions. - Allow shortcuts to be assigned to the "quick access" style and preset menus at the bottom of the darkroom view - Add a collapsible section to the sigmoid module so that controls not used in standard processing scenarios are hidden by default. - Some minor modifications to image overlays in culling view to make them less intrusive. ## Bug Fixes - Fix possible bad pinned memory transfer on OpenCL. - Fix bug in date/time sanitization function that caused image capture timestamps to be corrupted when they contained a time zone with a negative offset. - Fix toast messages containing "%". - Fix collections module using exclude rules when the first filter is empty. - Fix RGB curve histogram display when "compensate middle gray" is set. - Fix possible infinite loop when a module fails to load. - Properly honor "hide histogram" setting when restarting. - Fix darktable-chart crash. - Fix Y0 mask calculations in the demosaic module. - Avoid using fscanf() for loading configuration to avoid broken Windows implementation. - Add RYB vectorscope option to the darktable configuration file to ensure proper histogram view settings on startup. - Ensure that wide popups are properly shown on the same display as the associated widget. - Fix possible crash in camera tethering. - Make yes/no buttons in dialog boxes respond to standard shortcuts alt+y and alt+n. - Fix preferences sanitization, which was completely ineffective due to incorrect loading order. - Add a link to the sigmoid module's online documentation. - Fix tooltip on color calibration expander. - Fix incorrect reporting of HEIF image bit depth, which resulted in incorrect color profile selection for images without embedded color profile data. - Fix snapshot invalidation, which was too pessimistic and made switching snapshots slow. - Fix some messages in LUT module. ## Lua - N/A ## Notes - N/A ## Changed Dependencies - Update bundled LibRaw version to 0.21.1. For systems providing LibRaw 0.21.1 or newer, it is now possible to disable building the bundled copy by defining -DDONT\_USE\_INTERNAL\_LIBRAW=ON ### Mandatory - Bump minimum required CMake version from 3.10 to 3.18. ### Optional - Bump libheif minimum required version from 1.9.0 to 1.13.0. - Relax libavif minimum required version from 0.9.1 back to 0.8.2. ## RawSpeed changes - Massive Fuji decompressor refactoring, up to -25% less wall time - Fuji GFX100(S): fix 16-bit sensor black/white levels - Fix decoding of compressed Fuji raws with large filesize ## Camera support, compared to 4.2.0 ### Base Support - Canon EOS Kiss X10 - Canon EOS Kiss X10i - Leica M9 (dng) - Nikon Z 30 (12bit-compressed, 14bit-compressed) - OM System OM-1 - OM System OM-5 - Panasonic DC-G95D (4:3) - Panasonic DC-G99D (4:3) - Ricoh GR IIIx (dng) ### Missing Compression Mode Support - Fujifilm "non-lossless"/lossy - Nikon high efficiency - Sony lossless ### White Balance Presets - Nikon Z 9 ### Noise Profiles - Fujifilm GFX100S - Fujifilm X-H2 - Fujifilm X-H2S - OM System OM-1 - Sony
Re: [darktable-user] darktable 4.2.1 released
On Sat, 25 Feb 2023 21:34:52 + tony Hamilton wrote: > A significant part of the compile process is the handling of > compilation errors; here the documentation is frequently inadequate, > depending on a level of detailed knowledge and understanding which is > beyond the average Linux application user. They are typified by > impossible to parse scenarios which have an explanation of the nature > of: "Oh, didn't we tell you about dependencies abc, hij, opq (which > is incompatible with def, as long as you have, or, possibly, have > not, included rst) and xyz (but not in version 2.99)? Sorry about > that." > If you can use a deb package I can send you one. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E mir datanom net https://pgp.key-server.io/pks/lookup?search=0xE501F51C mir miras org https://pgp.key-server.io/pks/lookup?search=0xE3E80917 -- 'During times of universal deceit, telling the truth becomes a revolutionary act.' -George Orwell /usr/games/fortune -es says: udp - universal dropping of an pigeon pgpauk7hkYHdw.pgp Description: OpenPGP digital signature
Re: [darktable-user] darktable 4.2.1 released
Tony Me too. I always recommend linux from scratch to those that wish to understand the compilation process, as well as learning much about the way in which the system hangs together. On Saturday, 25 February 2023 21:34:52 GMT tony Hamilton wrote: > Oh, maybe I'm just too old and lacking a sense of humour darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] darktable 4.2.1 released
Thanks for the suggestions. With respect, your observation is clearly easy for you to say, but (and I have a LOT of experience on this) not so easy for me to do. The explanation (aside from the opinion oft expressed by others that I'm chronically, endemically and terminally stupid) is indeed simple: those who write the instructions on how to compile have to write for a general audience and so make assumptions - sadly often wrong - about my computing environment and my ability to comprehend those instructions. The latter factor reflects the fact that they are written by obviously technically competent authors who are also subject matter experts (but not necessarily writers), writing for people like themselves - who, by very definition, do not need such instructions. Those instructions are, in consequence, usually inaccessible and inapplicable to people like myself. A significant part of the compile process is the handling of compilation errors; here the documentation is frequently inadequate, depending on a level of detailed knowledge and understanding which is beyond the average Linux application user. They are typified by impossible to parse scenarios which have an explanation of the nature of: "Oh, didn't we tell you about dependencies abc, hij, opq (which is incompatible with def, as long as you have, or, possibly, have not, included rst) and xyz (but not in version 2.99)? Sorry about that." Oh, maybe I'm just too old and lacking a sense of humour On 25/02/2023 15:19, Patrick Shanahan wrote: really building is simple and instructions are provided on github. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] darktable 4.2.1 released
* tony Hamilton [02-25-23 10:03]: > Forgive my impatient and selfish perspective, but for those of us blessed > with the inability to compile anything in Linux, even after 15 years of > trying, where can we look for an Ubuntu binary for dt version 4.2.1? The OBS > is still showing 4.2.0. > > On 22/02/2023 18:45, Pascal Obry wrote: > > We're proud to announce the new bug fix release of darktable, 4.2.1! > > > > The github release is here: > > [https://github.com/darktable-org/darktable/releases/tag/release-4.2.1](https://github.com/darktable-org/darktable/releases/tag/release-4.2.1). > > > > As always, please don't use the autogenerated tarball provided by > > github, but only our tar.xz file. The checksums are: > > > > ``` > > $ sha256sum darktable-4.2.1.tar.xz > > 603a39c6074291a601f7feb16ebb453fd0c5b02a6f5d3c7ab6db612eadc97bac > > darktable-4.2.1.tar.xz > > $ sha256sum darktable-4.2.1_arm64.dmg > > d037a23e8b37f6971a1f2b7c4cf3e03647b168ad2fb43080761d7a307b43048d > > darktable-4.2.1_arm64.dmg > > $ sha256sum darktable-4.2.1_x86_64.dmg > > 993a29685397c6e1a429d84be578da9271eefc06d2c75c10818ffc00b7d04a00 > > darktable-4.2.1_x86_64.dmg > > $ sha256sum darktable-4.2.1-win64.exe > > 31c4d6c522818eda87e48df44f267afd531339ef9d374fa02d44891e3755f7b5 > > darktable-4.2.1-win64.exe > > ``` > > > > When updating from the stable 4.0.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.0.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.0: > > > > - Almost 300 commits to darktable+rawspeed > > - 89 pull requests handled > > - 18 issues closed > > > > ## The Big Ones > > > > - N/A > > > > ## Other Changes > > > > - JPEG files are identified using magic bytes instead of file > >extension. This helps in cases where JPEG images end up in > >files with unexpected extensions. > > > > - Allow shortcuts to be assigned to the "quick access" style and preset > >menus at the bottom of the darkroom view > > > > - Add a collapsible section to the sigmoid module so that > >controls not used in standard processing scenarios are hidden > >by default. > > > > - Some minor modifications to image overlays in culling view to make > >them less intrusive. > > > > ## Bug Fixes > > > > - Fix possible bad pinned memory transfer on OpenCL. > > > > - Fix bug in date/time sanitization function that caused image capture > >timestamps to be corrupted when they contained a time zone with a > >negative offset. > > > > - Fix toast messages containing "%". > > > > - Fix collections module using exclude rules when the first filter is empty. > > > > - Fix RGB curve histogram display when "compensate middle gray" is set. > > > > - Fix possible infinite loop when a module fails to load. > > > > - Properly honor "hide histogram" setting when restarting. > > > > - Fix darktable-chart crash. > > > > - Fix Y0 mask calculations in the demosaic module. > > > > - Avoid using fscanf() for loading configuration to avoid broken Windows > >implementation. > > > > - Add RYB vectorscope option to the darktable configuration file to > >ensure proper histogram view settings on startup. > > > > - Ensure that wide popups are properly shown on the same display as > >the associated widget. > > > > - Fix possible crash in camera tethering. > > > > - Make yes/no buttons in dialog boxes respond to standard shortcuts > > alt+y > >and alt+n. > > > > - Fix preferences sanitization, which was completely ineffective due to > >incorrect loading order. > > > > - Add a link to the sigmoid module's online documentation. > > > > - Fix tooltip on color calibration expander. > > > > - Fix incorrect reporting of HEIF image bit depth, which resulted in > >incorrect color profile selection for images without embedded color > >profile data. > > > > - Fix snapshot invalidation, which was too pessimistic and made > >switching snapshots slow. > > > > - Fix some messages in LUT module. > > > > ## Lua > > > > - N/A > > > > ## Notes > > > > - N/A > > > > ## Changed Dependencies > > > > - Update bundled LibRaw version to 0.21.1. > > > >For systems providing LibRaw 0.21.1 or newer, it is now possible to > >disable building the bundled copy by defining > >-DDONT\_USE\_INTERNAL\_LIBRAW=ON > > > > ### Mandatory > > > > - Bump minimum required CMake version from 3.10 to 3.18. > > > > ### Optional > > > > - Bump libheif minimum required version from 1.9.0 to 1.13.0. > > > > -
Re: [darktable-user] darktable 4.2.1 released
packaging needs time and someone must spend his spare time to do it. So be patient… > Am 25.02.2023 um 11:06 schrieb tony Hamilton : > > Forgive my impatient and selfish perspective, but for those of us blessed > with the inability to compile anything in Linux, even after 15 years of > trying, where can we look for an Ubuntu binary for dt version 4.2.1? The OBS > is still showing 4.2.0. > >> > > 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: [darktable-user] darktable 4.2.1 released
Forgive my impatient and selfish perspective, but for those of us blessed with the inability to compile anything in Linux, even after 15 years of trying, where can we look for an Ubuntu binary for dt version 4.2.1? The OBS is still showing 4.2.0. On 22/02/2023 18:45, Pascal Obry wrote: We're proud to announce the new bug fix release of darktable, 4.2.1! The github release is here: [https://github.com/darktable-org/darktable/releases/tag/release-4.2.1](https://github.com/darktable-org/darktable/releases/tag/release-4.2.1). As always, please don't use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are: ``` $ sha256sum darktable-4.2.1.tar.xz 603a39c6074291a601f7feb16ebb453fd0c5b02a6f5d3c7ab6db612eadc97bac darktable-4.2.1.tar.xz $ sha256sum darktable-4.2.1_arm64.dmg d037a23e8b37f6971a1f2b7c4cf3e03647b168ad2fb43080761d7a307b43048d darktable-4.2.1_arm64.dmg $ sha256sum darktable-4.2.1_x86_64.dmg 993a29685397c6e1a429d84be578da9271eefc06d2c75c10818ffc00b7d04a00 darktable-4.2.1_x86_64.dmg $ sha256sum darktable-4.2.1-win64.exe 31c4d6c522818eda87e48df44f267afd531339ef9d374fa02d44891e3755f7b5 darktable-4.2.1-win64.exe ``` When updating from the stable 4.0.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.0.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.0: - Almost 300 commits to darktable+rawspeed - 89 pull requests handled - 18 issues closed ## The Big Ones - N/A ## Other Changes - JPEG files are identified using magic bytes instead of file extension. This helps in cases where JPEG images end up in files with unexpected extensions. - Allow shortcuts to be assigned to the "quick access" style and preset menus at the bottom of the darkroom view - Add a collapsible section to the sigmoid module so that controls not used in standard processing scenarios are hidden by default. - Some minor modifications to image overlays in culling view to make them less intrusive. ## Bug Fixes - Fix possible bad pinned memory transfer on OpenCL. - Fix bug in date/time sanitization function that caused image capture timestamps to be corrupted when they contained a time zone with a negative offset. - Fix toast messages containing "%". - Fix collections module using exclude rules when the first filter is empty. - Fix RGB curve histogram display when "compensate middle gray" is set. - Fix possible infinite loop when a module fails to load. - Properly honor "hide histogram" setting when restarting. - Fix darktable-chart crash. - Fix Y0 mask calculations in the demosaic module. - Avoid using fscanf() for loading configuration to avoid broken Windows implementation. - Add RYB vectorscope option to the darktable configuration file to ensure proper histogram view settings on startup. - Ensure that wide popups are properly shown on the same display as the associated widget. - Fix possible crash in camera tethering. - Make yes/no buttons in dialog boxes respond to standard shortcuts alt+y and alt+n. - Fix preferences sanitization, which was completely ineffective due to incorrect loading order. - Add a link to the sigmoid module's online documentation. - Fix tooltip on color calibration expander. - Fix incorrect reporting of HEIF image bit depth, which resulted in incorrect color profile selection for images without embedded color profile data. - Fix snapshot invalidation, which was too pessimistic and made switching snapshots slow. - Fix some messages in LUT module. ## Lua - N/A ## Notes - N/A ## Changed Dependencies - Update bundled LibRaw version to 0.21.1. For systems providing LibRaw 0.21.1 or newer, it is now possible to disable building the bundled copy by defining -DDONT\_USE\_INTERNAL\_LIBRAW=ON ### Mandatory - Bump minimum required CMake version from 3.10 to 3.18. ### Optional - Bump libheif minimum required version from 1.9.0 to 1.13.0. - Relax libavif minimum required version from 0.9.1 back to 0.8.2. ## RawSpeed changes - Massive Fuji decompressor refactoring, up to -25% less wall time - Fuji GFX100(S): fix 16-bit sensor black/white levels - Fix decoding of compressed Fuji raws with large filesize ## Camera support, compared to 4.2.0 ### Base Support - Canon EOS Kiss X10 - Canon EOS Kiss X10i - Leica M9 (dng) - Nikon Z 30 (12bit-compressed, 14bit-compressed) - OM System OM-1 - OM System OM-5 - Panasonic DC-G95D (4:3) - Panasonic DC-G99D (4:3) - Ricoh GR IIIx (dng) ### Missing Compression Mode Support - Fujifilm
