Re: [darktable-dev] Re: integration tests moved to sub-modules
Le vendredi 15 janvier 2021 à 12:56 -0500, Patrick Shanahan a écrit : > * Pascal Obry [01-01-70 12:34]: > > > > The sub-module is in place. > > > > > If you don't care about the integration tests and want to avoid > > > downloading the tests you can do: > > > > > > $ git config submodule.src/test/integration.update none > > > > A typo while writing this (missing s for tests): > > > > $ git config submodule.src/tests/integration.update none > > I do not know "git"! > > I did: > git config submodule.src/tests/integration.update none > > > and I do: > git clean -d -f -x > git submodule init Only needed first time a clone is done and if the clone was not done with recursive submodule option. > git submodule update Likewise, you don't need that if you only follow one branch. The git pull will do it. The command is needed when you switch branches and if they are not at the same sub-module version. > git pull --rebase --recurse-submodules The --recurse-submodules option is probably the culprit. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: integration tests moved to sub-modules
The sub-module is in place. > If you don't care about the integration tests and want to avoid > downloading the tests you can do: > > $ git config submodule.src/test/integration.update none A typo while writing this (missing s for tests): $ git config submodule.src/tests/integration.update none Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] integration tests moved to sub-modules
The integration tests are eating quite some band width for some people and will become hard to manage at some point. It has been decided to move the integration tests under a sub-module. This will require more work for the devs but seems to be a good compromise. The change will happen today. If you don't care about the integration tests and want to avoid downloading the tests you can do: $ git config submodule.src/test/integration.update none Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Import from camera/ memory card: some probleems
Le jeudi 07 janvier 2021 à 09:57 +0100, Laurent Zimmermann a écrit : > -> import from memory card doesn't copy anymore files to HD/SSD > (works like import folder). This is wrong or we are speaking of different things. I'm using this often and still be using it yesterday. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Crash in collect images
Le lundi 04 janvier 2021 à 08:57 +0100, Stefan Saam a écrit : > Hello, > > in darktable 3.4.0/Kubuntu 20.4 I always have crashes this way: > > * select "date taken" as first rule (now "date-taken time" appears > as > the second rule, set by darktable) > * click into the input-field of "date-taken time" -> crash A similar issue has been fixed recently on master. So should be ok in 3.4.1. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Dutch Translation
In the mean time you can have a look at the Wiki which has been updated: https://github.com/darktable-org/darktable/wiki/Translations -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.4 - GNU/Linux binaries
This year is special... The documentation comes with the release (in two versions!) and also the GNU/Linux binaries. Thanks to Andreas for this work, to download dt 3.4 for your favorite distribution head to: https://software.opensuse.org/download.html?project=graphics:darktable=darktable Have all a Merry Christmas and Happy New Year! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.4 released
er for this to work. - darktble uses Lua 5.3. Lua 5.4 has been released and is now the default Lua for some distributions. Please install the Lua 5.3 library package if your distribution is using Lua 5.4 as the default. If you compile darktable, then you may also set `DONT_USE_INTERNAL_LUA` to OFF in the DefineOptions.cmake file to use the internal Lua. ## Changed Dependencies - Due to the current GMIC version windows users may have to rename two libraries in the darktable bin folder to get lut3d module working:`libopencv_code4xx` and `libopencv_videoio4xx` should be renamed to `libopencv_code440` and `libopencv_videoio440` respectively. ## RawSpeed changes * CR2 decompressor was rewritten, the subsampled (mRAW/sRAw) data is now stored in packed format, which made interpolation beneficial for auto-vectorization by LLVM/Clang (after fixing over-eager common code hoisting (https://reviews.llvm.org/D84108), and teaching it to perform SROA after loop unrolling (https://reviews.llvm.org/D87972)), resulting in modest performance improvements, also, `4:2:0` case was parallelized: see https://github.com/darktable-org/rawspeed/commit/5743628b9d4649aa027df62b91f4882e78de7063 / https://github.com/darktable-org/rawspeed/commit/11eccf1e786dc80e13758ed876b2538a275438d2 ## Camera support, compared to 3.2.1 ### Base Support - Canon EOS REBEL T7i - Nikon Z 5 (14bit-compressed, 12bit-compressed) - Olympus E-M10 Mark IV - Panasonic DC-GX7MK3 (4:3) - Panasonic DC-S5 (3:2) - Sony ILCE-7C - Sony ZV-1 ### White Balance Presets - Canon EOS 200D - Canon EOS Kiss X9 - Canon EOS Rebel SL2 - Canon EOS M5 - Canon EOS M6 - Nikon 1 V2 - Nikon Z 50 - Sony ILCE-6600 ### Noise Profiles - Panasonic DC-G90 - Panasonic DC-G91 - Panasonic DC-G95 - Panasonic DC-G99 - Ricoh GR II - Sony NEX-5T ## Translations - Afrikaans - Czech - German - European Spanish - Finnish - French - Hebrew - Hungarian - Italian - Polish - Brazilian Portuguese - Russian - Slovak - Slovenian -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Change request for copying editing steps without crop module
Hi Dennis, > In the next version of Darktable, could you make sure that copying > editing steps via CTRL+C and CTRL+V copies everything like before, > except the cropping of images? You can always use Ctrl+Shift+C to control the modules to copy. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: darktable 3.4- string freeze - let's start translations
Hi Jeronimo, > Did this get into github? I fetched today and didn't see anything new > (neither in darktable's translations, checked with intltool-update, > nor in the manual, checked with make update-usermanual-pt_BR). Yes and your .po was changed (see that "film stock" translation is not commented out anymore). As I said this was in 3.2, was translated and got commented out because the string was not removed anymore. Just doing an update will un-comment the translation (of course if this was already translated in 3.2). So you just have to issue a new PR with your modified PO. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Planning 3.4
Hello ! As announced we are entering the string freeze now. This means that translators can start translating the dt strings for our next major release 3.4. I'll send the necessary information to all translators in a following message. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] 3.4 - entering feature freeze
Hello, Our loved application has entered "feature freeze" just after the week- end. We have now a small window of 15 days before the "string freeze". During this period we can fix bugs (of course!) and accommodate or add new strings if needed to prepare 3.4. After this period no more strings are allowed to be changed for the translator to have time to translate all of them. Note to translators. There is a quite big amount of work for the 3.4 release. I know that some are doing the translation on a regular basis, so that won't be an issue for them but if you plan to finalize the translation of dt for your language and did not update your language since 3.2 you've been warned :) As usual all translations not in good shape will not be shipped with the release. Best, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: Planning 3.4
Hello, The feature freeze is approaching fast now. At the end of the week it will be impossible to add any new features in the code base. >From this point and for one month we will concentrate on fixes and translations to prepare the (hopefully) best release ever. Have a nice day, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Introducing dtdocs
Le samedi 17 octobre 2020 à 09:28 +0100, Chris Elston a écrit : > At a rough estimate you should expect the translations to end up > perhaps no more than 50-60% complete in the best-case scenario. Probably a good move and I understand that rewording was needed but that it is tad harsh for translators. Maybe we should have told them upfront about this especially Jeronimo Pellegrini which has done a tremendous amount of work recently on the pt_BR translation. > > I'm still of the opinion that the benefits of a separate repo far > outweigh the negatives. I understand that you don't like having to > monitor a second repo No problem to monitor a second repo on my side. > but you don't necessarily have to be the main > maintainer for dtdocs - Mica and I are more than happy to shoulder > that responsibility That's really appreciated. > and it's clear that we will have other volunteers now that the format > has been simplified. I've put in well over 500 hours on this project > already, so I think I've demonstrated a dedication to > getting and keeping the docs up-to-date. No question about that, I had not even questioned this part. All clear to me that such a huge project is not just pushed for fun and to drop everything after. > It's also important for these sort of things to be copy-edited by > native English speakers and you would end up having to make non- > technical people maintainers on the main > darktable project - which seems risky. Sure. > Plus the issues around > pre-implementation code freezes and the fact that the manual updates > often trail behind the releases by a couple of months. I'm not sure this has anything to do with one repo or two repos. The problem is volunteer to write the doc. I had recently create a momentum on this side, I hope this will continue. > It seems like > maybe you're also arguing that developers can't cope with having to > update more than one repo? That's my main concerns. Having the doc "away" from main repo will not help. I don't know why exactly, but I've seen that on different projects. Maybe because the doc is away it feels less part of the project and there is less incentive to care for it? > There's no argument with dtorg, rawspeed and lua-scripts being > separate repos so I don't really see the difference here. Sure, if a second repo is needed dtorg is the natural choice. Don't get me wrong, I don't want to keep the doc part of darktable, I want the best solution for darktable project in the long term and on this I have a different opinion. But I'll follow you on this one as you are the driving force with Mica and certainly hope the best for this project. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Introducing dtdocs
Hi johnnybit, > I think it should be a separate repo under darktable org, same as > dtorg website. That way dtdocs can have less technical but more > writting oriented maintainers lowering the burden of keeping docs in > main repo. I don't agree with that since most of the documentation is written by the developers themselves. Having a separate repo will make ensuring the documentation is updated even harder. And I do really care about documentation as I have pushed hard recently to have things regularly updated. Now for the translators it shouldn't make a difference since a weblate will be used to update/translate if I have properly understood. All in all, in my experience having the documentation next to the project is always better. > -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Introducing dtdocs
Congrats! I'm looking forward moving away from docbook. I suppose one difficult point would be to reuse existing translation but this is very important. The pr_BR manual is up to date and the fr_FR one is 90% (was complete for 2.6). As translating the manual needs countless hours we cannot tell the translators to start from scratch again. Another question, I suppose this will be merged back at some point in current darktable repository ? So we will probably need to coordinate. Anyway keep us informed about the progress. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable freeze when trashing an image
Hi Terry, > Is this likely to be a local problem? No and the problem should now be fixed. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: Planning 3.4
Hello ! A gentle reminder that we are 1 month away from the feature freeze. So by any mean if you are working on something for 3.4 it must be ready before this date. After that only fixes will be allowed to be integrated. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation
Hi Maurizio, > in the Italian translation we used many Caps. as per Italian grammar. > I am not in the position to write the script but maybe you can use > the it.po file as a sort of 'template' for tests or something > similar Noted, could indeed a good way to check the script. Thanks, > -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation
I'm also against this all lower case rule. But, no the rule has not changed recently and will not change as a small step. I don't want to have non consistent GUI in dt, this will be very bad ! The only solution out of this is: - To create a script to rewrite all strings in the code with capital letters where needed. - To update all PO files to ensure the changed strings in the code will not invalidate all translations. - Optionally this script should be able to handle translated strings in PO files to help translator to use capital letters in translations. So now we need to find a volunteer to create this script. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Not flashing a blank space when loading an image?
Le mardi 06 octobre 2020 à 13:19 +, juli...@i2pmail.org a écrit : > Thanks all. Sorry I didn't check the GitHub prior to mailing. Will do > in future. And not one will pick-up issues or enhancements request on the mailing- list. If you want this to be followed and discussed you need to create GitHub issues. > For reference: > > I can't use github but.. So there is no chance to have those fixed. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Darktable build instructions for Ubuntu 20.04
Le dimanche 04 octobre 2020 à 15:50 +0200, Mikael Ståldal a écrit : > When I built Darktable for Ubuntu 20.04, I took notes of which apt > packages I needed to install. Can I contribute this documentation > somewhere? On the GitHub Wiki ? https://github.com/darktable-org/darktable/wiki -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Current master fails to build in Fedora 32
Hi Terry, $ rm -fr build > > /home/terry/rpmbuild/BUILD/darktable- > > 3.3.0/src/control/conf.c:27:10: fatal > error: conf_gen.h: No such file or directory >27 | #include "conf_gen.h" > | ^~~~ > compilation terminated. > > At this stage I'm assuming that it is a local problem. > Is there a new dependency required? And restart the build. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Planning 3.4
We are still away from 3.4, but planning now does not hurt. This message is only to share the big dates with you: - feature freeze : mid-november - string freeze : end-november - full freeze : mid-decembre The "full freeze" is now clearly identified and means that we let 10 days for the packagers to create the binary releases for Windows and MacOS and maybe the Linux maintainers will also be able to create the packages for different distributions. Do not hesitate if anything is not clear. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: RE: [darktable-dev] idea to consider
Le vendredi 04 septembre 2020 à 04:26 +0200, Jozef Dassen a écrit : > The question for me is not about processing JPG, but about > Cataloguing images. > Darktable by default is set up to have everything online in some huge > project. ??? I think I do know darktable but the above sentence makes no sense to me. > I have since the early days used Capyture One's Sessions in my > workflow. I think this is a really great concept. > You process a limited number of raw files and then archive them > complete with processing information and database. > Very easy to archive, very easy to restore. Perfect, that's exactly what darktable does. Import image, develop them and remove them. The .xmp left on the file system can be used to reimport the pictures. > I am using darktable in a similar way. I have some shell scripts that > create a 'darktable session', initiate a new database and process the > images in this limited scope project. Seems like a huge mess for something already supported. I'll stop reading here as this message seems to spread quite a lot of wrong information. Please read the manual. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] news about darktable development
Hello devs, The 3.2.1 release is now out since almost a week. Some issues have been discovered which is somewhat expected. The release schedule was tight and did not allow for publishing RCs. Anyway, all the issues are being worked on and will be in 3.4. I do not expect to release a 3.2.2 as the code freeze for 3.4 is about 3 months from now and I don't want more pressure during this period. My dream for 3.4 is to update the user's manual. Yes, we all love coding and we do forget the user manual. I have created lot of issues for sections to be updated, if you are a dev and have been working on one part which misses documentation, please assign the issue to you. I have already assigned 3 doc issues to me. https://github.com/darktable-org/darktable/issues?q=is%3Aissue+is%3Aopen+label%3A%22scope%3A+usermanual%22 The next part for 3.4 will be performance oriented. We have many PR opened already to improve the perfs of different parts of darktable. This work has been started by Ralf Brown and we have currently around 6 PRs. I also know that Aurélien Pierre is working on the OpenCL part of FilmicV4. Also, now that we have some integration tests (22 at the moment) do not hesitate to run them when change the code in dt to avoid regressions. This is especially important if the changes are touching de develop/* and/or iop/* files. If you have PR waiting to be integrated, please to not hesitate to send a status update of this PR. Checking that it is still compiling and maybe rebasing it on top of current master if needed. So, 3.4 is shaping as a perfs oriented release. Probably not much new features which is good to stabilize the current code base. Have a nice week-end! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules
Le jeudi 13 août 2020 à 00:21 +0200, Andreas Herold a écrit : > Screenshot 3.0.2: > https://www.dropbox.com/sh/orbifgwd23sgzw8/AAC3SjlwjRe-LvLhX7U5UZBaa?dl=0=Bildschirmfoto+2020-08-12+um+23.02.54+Kopie.jpg > Screenshot 3.2.1 custom: > https://www.dropbox.com/sh/orbifgwd23sgzw8/AAC3SjlwjRe-LvLhX7U5UZBaa?dl=0=Bildschirmfoto+2020-08-12+um+23.24.53+Kopie.jpg Those two screenshots are looking very similar. What is the issue? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules
Le mercredi 12 août 2020 à 22:03 +0200, Andreas Herold a écrit : > Thank you. I didn't notice that before. Currently it's showing > "custom" (which is the wrong order) and I can change it to "legacy", > which results in another wrong order. "custom" is not the wrong order (expect if there is a bug) but the order that is neither legacy or 3.0 because some modules where moved around in the pixelpipe. Wasn't this the case? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Upgrade from 3.0.2 to 3.2.1 destroys order of modules
Le mercredi 12 août 2020 à 21:32 +0200, KOVÁCS István a écrit : > I thought that setting changes which modules get auto-applied (base > curve or filmic+exposure or none). There's a 'module order' setting > in > the darkroom (below the modules, above 'more modules') that allows > you > to switch between 3.0 and legacy order -- however, in that respect, > 3.2.1 did not bring any changes, did it (that is, the order of > modules > between 3.0 and 3.2 is the same, is it not)? Yes, 3.0 and 3.2 are using the same module order. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: Aw: [darktable-dev] darktable 3.2.1 released
Hello Alexander, > One question: is the Ctrl+Click working in multiple shapes creation > in the retouch module for the pen tool? I can't simultaneously create > several pen shapes both in Linux (git master) and Windows (3.2.1 > release). Maybe I'm doing something wrong? Just double checked, and it is working for me on Linux GNU/Debian with GNOME Shell. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.2.1 released
sue when using two computers to edit images. If the three following options activated: - update database from selected xmp files - write sidecar file for each image - check xmp on start then darktable will write the XMP for each images each time you switch from one computer to another. This is due to an issue with the way timestamps are implemented and is being fixed for 3.4. You can follow the discussion here: https://github.com/darktable-org/darktable/pull/5869 A safe option if you are in this specific case is to wait to 3.4 release planned at the end of year. - The histogram has been deactivated on the print view because after lot of work on the histogram code it was not possible to have it ready for this view. The work on this part is almost ready now so the print view will get back its histogram for the 3.4 release. - An integration test suite has been added. This will ensure better quality and keeping old edits intact. This is an important tool for developers to ensure a rework of a module for performance reason for example does not change visually the image. ## Lua - API changed to 6.0.0 - facebook, flickr, and picasa removed from types.dt_imageio_storage_module_t. - piwigo added to type.dt_imageio_storage_module_t. - notes and version_name metadata fields added to types.dt_lua_image_t data type. - Added 4 new properties to dt_collection_properties_t, DT_COLLECTION_PROP_IMPORT_TIMESTAMP, DT_COLLECTION_PROP_CHANGE_TIMESTAMP, DT_COLLECTION_PROP_EXPORT_TIMESTAMP, DT_COLLECTION_PROP_PRINT_TIMESTAMP - added darktable.gui.panel_get_size and darktable.gui.panel_set_size functions to set the width of the left or right panels and the height of the bottom panel. - fixed is_password field of entry widget to work according to the API manual, so now when it is set to true the field is hidden. - Added function darktable.gui.views.lighttable.is_image_visible to check if an image is visible in lighttable view. - Added function darktable.gui.views.lighttable.set_image_visible to force an image to be visible in lighttable view. - Added a lua scripts installer to the default luarc ## Changed Dependencies ## RawSpeed changes - New Panasonic 'V6' decompressor - Huffman table implementations rewrite/cleanup - Fuji compressed raw decompressor performance improvements (-13% wall clock) - Canon CRW decoding performance improvements (-15% wall clock) - DNG LJpeg decompressor support for images with 2 components / pixel - DNG Deflate decompressor support for images with more than 1 component / pixel - Fuji compressed raw decompressor support for 16-bit raws - Continuation of ongoing collaboration with LLVM, highlights include many little steps towards making it possible to auto-vectorize GoPro's VC5 decompressor loops, Canon S-RAW interpolator loops; more changes upcoming. ## Camera support, compared to 3.0.0 ### Base Support - Fujifilm FinePix S1 - Fujifilm GFX 100 (compressed) - Fujifilm X-Pro3 (compressed) - Fujifilm X-T200 - Fujifilm X-T4 (compressed) - Fujifilm X100V (compressed) - Hasselblad H4D-50 - Hasselblad X1D II 50C - Hasselblad X1DM2-50c - Nikon COOLPIX P950 (12bit-uncompressed) - Nikon D780 (12bit-compressed, 14bit-compressed) - Nikon Z 50 (12bit-compressed, 14bit-compressed) - Olympus E-M1MarkIII - Olympus E-PL10 - Panasonic DC-FZ10002 (3:2) - Panasonic DC-GX880 (4:3) - Panasonic DC-S1 (3:2) - Panasonic DC-S1H (3:2) - Panasonic DC-S1R (3:2) - Panasonic DC-TZ91 (4:3) - Panasonic DC-TZ95 (4:3) - Panasonic DC-TZ96 (4:3) - Panasonic DC-ZS80 (4:3) - Panasonic DMC-FZ40 (1:1, 3:2, 16:9) - Panasonic DMC-FZ45 (1:1, 3:2, 16:9) - Sony ILCE-6100 - Sony ILCE-9M2 ### White Balance Presets - Canon EOS 77D - Canon EOS 9000D - Fujifilm X-E3 - Fujifilm X-T30 - Fujifilm X-T4 - Nikon COOLPIX P1000 - Olympus E-M1MarkIII - Olympus E-PL6 - Olympus TG-5 - Panasonic DC-GH5 - Panasonic DC-TZ95 - Panasonic DC-TZ96 - Panasonic DC-ZS80 - Samsung NX1 - Sony ILCE-7RM4 ### Noise Profiles - Canon EOS-1Ds - Fujifilm X-H1 - Fujifilm X-T100 - Fujifilm X-T30 - Fujifilm X-T4 - Nikon COOLPIX P1000 - Nikon Z 50 - Olympus E-510 - Olympus E-M1MarkIII - Olympus E-M5 Mark III - Olympus TG-6 - Panasonic DC-GF9 - Panasonic DC-GX800 - Panasonic DC-GX850 - Panasonic DC-GH5 - Panasonic DC-TZ95 - Panasonic DC-TZ96 - Panasonic DC-ZS80 - Sony DSC-RX100M6 - Sony DSC-RX100M7 - Sony ILCE-6600 - Sony ILCE-7RM4 - Sony ILCE-9 - Sony ILCE-9M2 ## Translations - German - European Spanish - French - Hebrew - Italian - Polish - Brazilian Portuguese - Russian - Slovenian -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] compile error
Le mardi 04 août 2020 à 08:09 -0400, Jesus Arocho a écrit : > Hello, > > I have been compiling dt for a while. Yesterday I ran the script to > update against github and compile. Got the error message: > > [ 8%] Built target opencl-program-guided_filter.cl > :1:10: fatal error: 'opencl-c.h' file not found > #include "opencl-c.h" > ^~~~ > [ 8%] Built target opencl-program-gaussian.cl $ git submodule update ? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] plan for 3.2 release
The plan for the 3.2 release is on track. We had some last minute patches to be integrated to fix some issues. The situation is a bit delicate as the 3.2 release has been planned late and so without the time to do RC. The 3.4 release is still planned on December and having RC for 3.2 would have mean that 3.4 release work would have been started just a month after. Anyway, the final sources have been cut today. There is still some time to create the binary packages for Windows and MacOS. The final announce for the release is still planned on August 10th. I'll send update if this plan cannot be achieved. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] preparing 3.2
@All devs ! If you have had some PR merged for 3.2 please can you review the latest RELEASE_NOTES.md that I have just pushed to ensure I don't have missed any important entry. Also, I think for 3.4 we should concentrate on the documentation which is now lacking many entries. So if you could write some description for the manual of the new feature you have added it would be nice. Either directly into the docbook on the repository with a PR or sending a plain text + screenshot if needed to me that I will volunteer to commit at the right place. Thanks all for the contributions! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] cannot compile OpenCL test program in git master
Le vendredi 19 juin 2020 à 19:44 +0300, Alexander Rabtchevich a écrit : > Latest git builds make the next output at compilation: > > > -- Found LLVM 6.0.0 Too old! I think you need at least version 8 or 9 IIRC. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Plan for release 3.2
Dear developers, Because of some instabilities with 3.0.2 on the new module re-ordering, issues that have been fixed in the current master it has been decided to do an interim release. It is not possible to issue a 3.0.3 with only the fix because darktable has seen many changes in many areas (more than 1800 commits at the moment), thanks to all the work done by the developer team! So, we will go with the 3.2 release around 10 August. We will accept new code until mid-june, string freeze will happen end of june and from this date to final release we will concentrate on stabilizing the code. Note that this is the current goal. It may not work if we discover too many issues and there is already some that we need to fix before the release. https://github.com/darktable-org/darktable/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.2 And yes we will have another release in December like all other years, it will be called 3.4. Hope this will work well, the 3.2 release will be especially a nice one because a lot of attention has been made into the UI making it more pro visually. The whole rewrite of the lighttable and culling mode from AlicVB come to mind (A huge work, thanks) but also many other small and not so small details from other devs (CSS rework, icons size & position,...). If you have anything prepared for the 3.2 release that is not yet published on GitHub issue a PR soon to see if it is possible to integrate it or not. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0.2 released
The darktable 3.0.2 release is out. The full description and release notes can be found here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.2 The Windows and MacOS packages are ready. As usual the Linux binary releases will come later when packagers will have time to build them. Thanks to all devs and testers who have been working really hard to make this release a reality. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] string should be in .po file, but it isn't...
Hi Jeronimo, > Did I miss something? You are not missing anything. src/common/metadata.c was not listed in POFILES.in. I've just fixed that. Thanks for reporting. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] your contributions
Dear developers, Just a little message to thanks you all. At the moment there is some many PR that I barely have time to do any coding on darktable. This is nice, very nice and shows that darktable is moving at a good pace ensuring that the project is alive and well. If you see some PR or issues that are getting time to be reviewed, do not worry, I'll come to it if needed, I just need to find some time. Have all a good day and I hope your are all well and safe at home. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] cannot desaturate after split toning is used
Le lundi 16 mars 2020 à 08:43 +, simon brown a écrit : > Understood. I can indeed solve the issue by reordering the modules. > > I would argue though that if monochrome (and perhaps any of the > saturation sliders) doesn't actually desaturate the image then it's > going to confuse a lot of users. Well split-toning is to do a "coloration" of light and dark tones from a monochrome image (and this well before digital pictures). So I would argue that if you don't want colors in your image don't use split- toning. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] cannot desaturate after split toning is used
Others have already answered about the module ordering. But to me this issue is in what you want to do. A simple way can be to use less saturated colors in split-toning. The other solution is to lesser the fusion of the split toning module. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0.1 released
The darktable 3.0.1 release is out. The full description and release notes can be found here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.1 The Windows and MacOS packages are ready. As usual the binary releases will come later when packagers will have time to build them. We are also conducting an anonymous survey to better understand darktable's users. The goal being a better sense of what point should be worked on for the future. If you can spend 5 minutes answering it will really help the project. http://www.poll-maker.com/QSDGDNJ Thanks to all devs and testers who have been working really hard to make this release a reality. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New documentation for 3.0
Hi Andreas, > You also need to update > > https://www.darktable.org/resources/ > > it still says v2.6 Yes, I said: "All the links will soon be updated on darktable.org." The PR is ready, I'm just waiting for approval :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] New documentation for 3.0
Thanks to Matt Maguire for building a script to build the documentation we are now in better shape to build it. So I have created the PDF which can be downloaded here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.0 And the online documentation has also been updated for 3.0: https://darktable.gitlab.io/doc/index.html All the links will soon be updated on darktable.org. Note that the 3.0 documentation is not finalized yet. Have a nice day! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] cannot open database
Le mercredi 05 février 2020 à 10:19 +0100, thokster a écrit : > After the latest change in git master darktable can't open the database > anymore. > > The pipe ordering rework merge was fine but the latest change leads to > the following error: > > [init] can't create folder index on film_rolls Should be fixed, for some reasons the index was still present in your case. Can you try with the last change? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] pipe ordering rework
Hello, Some of you may be aware that I've been working on the re- implementation of the pipe ordering in dt. This should have almost no visible effect to users except for a new module that will make it possible to reorder the pipe using the legacy order, the new one introduced in dt 3.0 (and also creating presets). Anyway, the PR is ready to be merged. This will happen very soon and this message is just a gentle reminder that you must make a backup in case something goes wrong. It is a deep rework, it has been tested by many people but I can anticipate issues. If you are not ready for this just avoid updating in the coming weeks. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Fwd: French translation typos and improvement submission
Laurent, Thanks, I had almost missed this. It is better to open a PR on our GitHub. Anyway, this is now integrated. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] removing broken storage and zoomable lighttable
Please see: https://github.com/darktable-org/darktable/issues/4008 And feel free to comment. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable : lot of changes today
Hello! I have merged today many PR that were waiting for 3.0.1. The merges have been made in master and in darktable-3.0.1. There is some PR still waiting to be merged but due the merges made today there is conflicts. So if you are a dev of one PR not yet merged, please double check that there is no conflict and do not hesitate to ping me by adding a message into the comments saying that it is still ready for merging. Also, the OpenCL headers are now pulled from the upstream repository instead of being copied and committed into dt. So with this in mind do not forget to: $ git submodule init $ git submodule update Next time you pull from dt repository. Thanks for helping making dt such a nice piece of software. Best wishes! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0.0 released
Hello! We are proud to announce the release of the 3.0 feature release. It is a very important major release with a redesign of many parts. It also brings many new features that have been missing for long time. This new release has more than 3000 modifications since last 2.6.0 release. Just impressive! It is also an important release as new developers have shined in and proposed some amazing features. It is good to see darktable developer's team growing. Thanks a lot to everyone involved! A full description of the release is there: https://github.com/darktable-org/darktable/releases/tag/release-3.0.0 The Windows and MacOS binaries are already available. The documentation will come a bit later. Enjoy the release and hope everyone will have nice end of year holidays. Best wishes, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Translation strings
Hi Maurizio, > during the translation I saw some 'guides' added to strings (for example > "module name" or "preferences" etc.). > Not all strings come with this additional guides but I found them > very helpful for the translation itself! Is it possible to add them > to rather all strings? Not all strings otherwise this will require to translate the same strings many times! But when there is ambiguities we do add them. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
Nazari, I have checked my list and I have gcc from 5 till 8. I removed 5 and tried > again - still the same error. > Should I remove all gcc or can I somehow point which gcc to use during > compilation? > You probably want to remove the build directory completely and start over again. Sincerely, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation
Hello Pierre, > As a non-native English speaker, I would vote against the rule. I do too ! > I also think users with English as their native language find it > strange if everything is written in small letters (don't the dt > developers know the spelling rules?). > If the rule is overturned, I would be willing to update the English part. That's a nice proposal. But it really means changing the casing of every single translatable strings in darktable code base. And to not break all translations we also want to update the English strings in all po files accordingly. >From there we could require the translator to keep current casing or update the mixed-case. I suppose all this will need a nice script to be written to help doing the change of the English part and propose to translators to go mixed- casing for their translation. Also, as this will require to review all strings (I don't expect the script to be 100% correct) we need a good coordination. As I said, probably a huge amount of work ahead :) If you are willing to work on this, please open an issue in GitHub to start a discussion of the proper way to go. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation
Le mercredi 11 décembre 2019 à 11:21 +, Richard Hobday a écrit : > On 11/12/2019 11:10, Maurizio Paglia wrote: > > in the Italian translation we changed all strings with the initial > > uppercase. > > This is because in Italian all sentences starts with an uppercase so we > > (Italian people) expect to see an uppercase at the beginning of a sentence. > > At the same time we expect to find an uppercase after a full stop (.) etc. > > Just as true for English, or at least British English. Yes that's true probably in most/all languages. The "rule" is in dt, nothing more than that. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation
Hi Pierre, > I will update the German translation accordingly in the next few days. Note that this rule is for the English strings. I suppose a translation can be made as you like it. We cannot impose a style for all languages. It was also discussed to change the rule and actually use mixed-case in the interface. But that would be a huge work ! Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
Hi Pierre, > with the pull request #3506 the translation of de.po will be complete. > Please merge this pull request into master. > > https://github.com/darktable-org/darktable/pull/3506 Now merged! Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] D850 does not appear in list (2)
And on Debian it is in : liblensfun-bin -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Database backups question
Hi Timur, > I'm a bit confused by files with suffix "-pre-3.0.0" in profile > directory. Is it some sort of safety feature create them all the time? > I understand that we have to make backups before migration but what's > the point of creating them for fresh library? It is a backup. As you have used the dev version this is certainly not very useful for you. But for all new users migrating from 2.6 to 3.0 it is expected to be a good thing! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] histogram and file export are broken in git master
Le samedi 23 novembre 2019 à 17:10 +0300, Timur Irikovich Davletshin a écrit : > I confirm. > > All new imports are black. Linux, builds from > https://software.opensuse.org/download.html?project=graphics:darktable:master=darktable Still cannot reproduce. Without more information as requested I don't see what could be done. And please open a GitHub issue, far more easier to follow and share the information with other devs. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] histogram and file export are broken in git master
Alexander, > An image is displayed correctly in the darkroom, but the histogram shows > it is almost black and the resulting file is black too. I cannot reproduce this. Can you open a GitHub ticket and tell us more about the context? Profile used? RAW ? Export profile? etc... Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] TIFF compression level
Hi Diederik, There was a missing reset=1 / reset=0 pair around the gui_init() call to the format plug-ins. Your message put me on the track. This is now fixed. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] basic adjustments
Le lundi 18 novembre 2019 à 20:13 +0100, Aurélien Pierre a écrit : > Don't, it's fine. > > But serious bug reports like crashes, regressions, Mac/Win/Nux and > CPU/GPU inconsistencies do pile up faster than fixes, so all the > cosmetic talk about the proper way to write grey is kind of > hilarious. I wonder sometimes if users realize we are just a handful > working on a day-to-day basis on darktable, and we are already > swamped. I fully agree, we need more man power than report at this time! I have been a bit rude those days about reports without any thinking before or trying to present the bug as simple as possible. We really don't have time to try to understand the problem, it should be obvious from the report. So please, yes do try to at least create the shortest reproducer for the issue. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] TIFF compression level
Hi Timur, > What is the point of giving user notification on dt start about TIFF > compression level? No point. That's a side effect of the toast being displayed when changing module sliders from a key without opening the module. Some of this has already been fixed by Diederik (in CC). There is more to fix at start time. I don't have time to look at this. Diederik, do you think you can have a look? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Styles → Hierarchy levels
Hi Timur, > There is another thing I noticed in master branch builds. It looks like > lighttable → styles supports hierarchy by using "|" as a divider. It > imposes no limits on the number of "|" and looks just fine. But in > darkroom mode only one level of hierarchy is supported, the rest is > just flattened being list of "level1 | level2". Right, this part would have to be enhanced. So not a bug, just a missing implementation. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0.0rc1 released
The darktable 3.0.0rc1 release is out. The full description and release notes can be found here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.0rc1 <https://github.com/darktable-org/darktable/releases/tag/release-3.0.0rc0> This is the second pre-release, test it and please be sure to report issues you found. If you are using RC0, please upgrade as soon as possible. This RC1 fixes the issues about iop-order notified yesterday. Thanks all! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-user] Re: AW:[darktable-dev] dt 3.0.0rc0
Hi August, > I have run into this a few times with 2.7 development versions; since > at that point encountering a conflict in 'iop-order' numbers caused > Darktable to crash, I worked around it by editing sidecar files to > eliminate the conflicts, mostly by substituting arbitrary 'iop-order' > values. Do you anticipate this causing any issues with the repaired > version? If this random and possibly wrong order works currently it will work with next version. But I think it is not a good idea to fix such issue this way. At least not substituting an arbitrary iop-order but one that could make sense seems preferable if you ask me :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: AW:[darktable-dev] dt 3.0.0rc0
Dear Axel, > is it possible to define "old edits"? All images edited with version previous to 3.0.0rc0. Starting working on new images is not a problem. > Also removing modules... I have hundreds of fotos edited with 2. 7 > ever since, but not yet exported e.g. for presentation. Would be > unfortunate, by that time to realize, a bunch of rework is > necessary. Not necessary. And at worst you'll have to reorder some modules. We are doing our best to have RC1 very soon which should fix this issue. Best wishes, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] dt 3.0.0rc0
Hello! Just a quick note to inform people that 3.0.0rc0 has an iop-order issue and so it is better to refrain from using it with old edits. There is no problem editing new pictures. We are working on a fix. See https://github.com/darktable-org/darktable/issues/3401 and https://github.com/darktable-org/darktable/pull/3409 Note that a solution exists which requires moving modules from the GUI. Best wishes, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-user] Re: [darktable-dev] darktable 3.0.0rc0 released
Le mercredi 06 novembre 2019 à 20:52 +, Simon a écrit : > > On 6 November 2019 20:27:30 GMT, Pascal Obry wrote: > > Hi Ihor, > > > > > When 3.0 GA is expected to be released? > > > > Sorry what is GA ? > > GA = General Availability. (I.e., out of beta and available to the masses) Ok, so as usual around Christmas. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0.0rc0 released
Hi Ihor, > When 3.0 GA is expected to be released? Sorry what is GA ? > Also, is the project public roadmap available somewhere? There is no roadmap, public or not. The project advance based on developers' proposals. Best wishes, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0.0rc0 released
The darktable 3.0.0rc0 release is out. The full description and release notes can be found here: https://github.com/darktable-org/darktable/releases/tag/release-3.0.0rc0 This is by far one of the best release ever. I understand that I have already said that for 2.6. But the list of enhancements in this release is just amazing! Lot of work as been done in almost all part of darktable. This is the first pre-release, test it and please be sure to report issues you found. There is one point to really check, we do suspect there is something wrong with the denoise profiled module. See: https://github.com/darktable-org/darktable/issues/3249 Fact is that many people are not reproducing this issue. What could help if you have the issue is to list the hardware (CPU & GPU, the memory and OpenCL driver) in used. We may find a pattern. Thanks all! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
I was speaking of the context in square brackets which is not only info. Le dim. 3 nov. 2019 à 10:16, Pascal Obry a écrit : > Le dimanche 03 novembre 2019 à 09:34 +0100, Jean-Luc Coulon (f5ibh) a > écrit : > > Hi, > > There is another way with gettext to give information to the translators: > > in the source code, you add a comment with /// (triple slash) and it > will appear in the .pot / .po files/ > > This is not only information it is a context. This make it possible to > translate the same string into different translation. All translations > are not 1-to-1 with the original text. > > -- > Pascal Obry / Magny Les Hameaux (78) > > The best way to travel is by means of imagination > > http://www.obry.net > > gpg --keyserver keys.gnupg.net --recv-key F949BD3B > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
Le dimanche 03 novembre 2019 à 09:34 +0100, Jean-Luc Coulon (f5ibh) a écrit : > Hi, > There is another way with gettext to give information to the translators: > in the source code, you add a comment with /// (triple slash) and it will > appear in the .pot / .po files/ This is not only information it is a context. This make it possible to translate the same string into different translation. All translations are not 1-to-1 with the original text. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
Le dimanche 03 novembre 2019 à 08:07 +0100, openhab.doc a écrit : > Good Morning developers, > > if I find some minor errors in the English original during the translation, > which file would I have to adapt (the pot file?) and return to the project > via a pull request? No, the original source files should be fixed. You can open a separate PR for that. It won't be for 3.0 as we are in string freeze. Alternatively if you don't know how to create PR just list the errors on a message to me. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 - let's start translations
Hello Pierre, > I have started with the translation into German. > In the po.file I will fine some entries: > > [CIRCLE] change size > [BRUSH] change opacity > ... > > Can I also translate the part in the square bracket or are they control > commands for darktable? No, not needed. The word in square bracket is the context in which the string is used. It is only a hint to help translating the string properly. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: darktable 3.0 - let's start translations
Dear Translators, An error was reported by our Russian translator (Thanks Timur) which prevented one string to be translated. Attached a new POT file to use. If you already have started the translation, no problem. Just finish with the previous pot file I sent and then do a second pass with the one attached to this message. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Drag-and-drop to change module order
Le vendredi 01 novembre 2019 à 14:56 -0400, Patrick Shanahan a écrit : > fwiw, I believe the pp order should remain static and *only* the visual > list should be changable. Amusing! You are probably saying that just because you don't know why the pp can be reordered. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] String freeze for 3.0
Dear all, As already announced, v3.0 string freeze will be starting tomorrow. This is the last day for changing strings in the code. The current plan is: - *feature* freeze end of September (DONE) - *strings* freeze end of October (TOMORROW) - Final translation can start (I'll send a message to all translators as requested) - *RC0* very early in November - *RC1* end of November - Final version in December Hope this will fit your agenda. This is the current plan, do not hesitate to share your thoughts and concerns if any. Let's just ensure dt 3.0 will be the best version ever! Thanks to all people involved in this release, it is amazing to see the developer community growing ! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: darktable 2.6.3 released
Just a quick message to announce that the Windows build is now available. Thanks to all involved in this release which is now complete. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 2.6.3 released
The darktable 2.6.3 release is out. The full description and release notes can be found here: https://github.com/darktable-org/darktable/releases/tag/release-2.6.3 For now only the sources and the binary versions for MacOS are available. The Windows version will follow. For GNU/Linux just grab the release from your favorite distrib. Best wishes, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New 2.6.x release
Le samedi 19 octobre 2019 à 15:18 +0200, parafin a écrit : > OK, I found that backport: > http://distfiles.gentoo.org/distfiles/darktable-2.6.2-gcc9.patch.tar.xz Thanks, it helped a bit but still had some conflicts. Anyway I have now a complete build with GCC-9 for 2.6.3. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New 2.6.x release
Le samedi 19 octobre 2019 à 15:30 +0300, Roman Lebedev a écrit : > Maybe done. Thanks a lot Roman. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New 2.6.x release
Le vendredi 18 octobre 2019 à 09:44 +0200, Germano Massullo a écrit : > Il ven 18 ott 2019, 08:28 Pascal Obry ha scritto: > > Le vendredi 18 octobre 2019 à 08:16 +0200, Germano Massullo a écrit : > > > Will you include also the patch for OpenMP on GCC 9? > > > > Which one? There has been many changes/patches on this side. I doubt > > that it will be possible to merge those anyway. > > #2550 There is conflict when rebased on top of darktable-2.6.x. So to have this in the darktable-2.6.x branch the author will have to rebase and resolved conflicts. This PR contains 98 commits :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New 2.6.x release
Le vendredi 18 octobre 2019 à 08:16 +0200, Germano Massullo a écrit : > Will you include also the patch for OpenMP on GCC 9? Which one? There has been many changes/patches on this side. I doubt that it will be possible to merge those anyway. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] New 2.6.x release
Hello Parafin, > I would vote for doing a 2.6.3 in order to release a fix for this macOS > bug: > https://github.com/darktable-org/darktable/issues/3107 > and I will try to fix another one this week too: > https://github.com/darktable-org/darktable/issues/1977 > > Not sure what else we might want to add. A new release why not. It is quite some work and we are two months away from next release. I suppose that we may want also to check with Roman if we can upgrade rawspeed at the same time to get support for new camera. Roman, what's your take on this? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Vibrance slider in the Basic adjustments tool
Le vendredi 11 octobre 2019 à 18:22 +0200, Keresztes Barna a écrit : > Thanks Aurélien! > > Formula changed, new version on Git ready for testing: > https://github.com/kbarni/darktable > (please test especially the OpenCL kernel, as I don't have the hardware to > test it!) If you want to have a little chance that this be tested please create a pull-request on the main darktable GitHub. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Feature freeze for 3.0
Hello Pierre, > If I remember correctly, a pot file was distributed last year to start the > translations for dt 2.6. Will this file also be distributed this year for > the new dt version? Yes, it will be as soon as we will be entering string freeze which is expected at the end of the month. > Where can I find it? I'll send a message to the list and to all translators. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Feature freeze for 3.0
Le mer. 2 oct. 2019 à 10:27, parafin a écrit : > On Tue, 01 Oct 2019 23:49:03 +0200 > Pascal Obry wrote: > > > Dear developers ! > > > > As announced back in August, we are now entering feature freeze. That > > is, at this point only bugs will be considered to be merged into > > master. > > Let's hope it's the opposite - bugs got merged before this point, and > now fixes will be introduced;) > :) Indeed, I meant bug fixes of course :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: Feature freeze for 3.0
Dear developers ! As announced back in August, we are now entering feature freeze. That is, at this point only bugs will be considered to be merged into master. I have one exception discussed with Aurélien which is working on the OpenCL version of Filmic RGB. Pending bugs worked on are: - fix implementation of iop-order to avoid possible clashes - fix metadata export to save status between session Of course bugs are malicious and we'll discover some others. So do not hesitate to test the current code base and report issues. As a reminder, the next steps are: - *strings* freeze end of October - *RC0* end of October - *RC1* end of November - Final version in December Thanks again for the hard jobs done by all developers to make this release a reality... And I can say a very nice reality. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Where to report bugs / changes for dt 3.0 user manual
Le jeudi 19 septembre 2019 à 14:02 -0700, jys a écrit : > > On Thu, Sep 19, 2019, at 13:42, openhab.doc wrote: > > > I prefer capital letters as well as spaces and a plus for separation to > > special characters. > > > > > > Ctrl-x will change to Ctrl + x and h will change to H. > > In most documentation I've seen there are no spaces in the sequence. For > whatever it's worth, the MS style guide agrees: > > > https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts > > Might be a good general reference, just to keep some consistency. Agreed and the letter should always be in capital letter. Ctrl+X in previous message and not Ctrl+x. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Where to report bugs / changes for dt 3.0 user manual
Hello Pierre, > Where can the changes or bugs be officially reported? (redmine or github) GitHub (Redmine is dead at this stage). > I like to go through the manual again and standardize the shortcut > spelling. But first , I would have clarifyed the spelling first (see > discussion from April 6 to April 11, 2018 with houz) @ > https://github.com/darktable-org/darktable/pull/1667#discussion_r179834220 Don't have a definite answer, I'm not native English speaker. A quick search on Internet seems to use : Keyboard Shortcuts Let native speakers shine in :) Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Piwigo export hanging after first successfull picture
Hi David, > I did not know that direct exports to Piwigo were possible from dt . what > script are you using? No script. This is available directly from dt in the export module since 2.6.2. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: Export to file hanging... (was:Re: [darktable-dev] Piwigo export hanging after first successfull picture)
Le mardi 17 septembre 2019 à 12:21 +0200, Wolfgang Goetz a écrit : > On Tue, 17 Sep 2019 11:59:27 +0200 > Wolfgang Goetz wrote: > > update: > > i tried export to file on disk. non-working, too. > > stuck after 5 pictures on disk, darktable states 4/157 exported, hanging. Cannot reproduce! I have just exported 17 pictures without issue. Not sure what could cause this. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Re: [darktable-dev] transformation module doesn't work in the git master
Hi Alexander, > After today updates the transformation module becomes broken. It shows > the frame outside the image. What is the transformation module? Please open a PR here: https://github.com/darktable-org/darktable/issues/new/choose And with a screenshot if possible. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] haze removal default values
Hi Andreas, > the haze removal default values are in 99% of the cases too strong. Is there > a > reason that they are this strong? > > My suggestions for default values would be: > > strength: 0.15 > distance: 0.200 I tend to agree and see the same issue on my side. I would keep strength at 0.20 though. A PR would be nice and we can let Heiko discuss this here. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] jsonschema version issues
Le jeudi 05 septembre 2019 à 10:25 +1000, Terry Duell a écrit : > Hello, > I regularly build dt on Fedora 30 from the git master. > About a week ago I had a build error because my version of jasonschema was > not 3.0.1, so I installed v3.0.1 and all was well. > A few days later Fedora updates provided v3.0.2, and as a result I had > another build error because v3.0.1 could not be found. > Is it necessary to explicitly specify the version required rather than > specify (say) v3.0.1 or later? I suppose you just have to delete the build directory and start the build again from scratch. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] How to transform coordinates
Hi Jens-Hanno, This should be the final fix: https://github.com/darktable-org/darktable/pull/2892 Can you test it and report if it works on your side? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] How to transform coordinates
Hi Jens-Hanno, > Pascal, Yes please. Ok, my PR is there: https://github.com/darktable-org/darktable/pull/2892 As I said in the changelog, the "jump" is fixed by the mask and the effect are not aligned. So we need something more here. I let you start from here. Let me know if you have other questions. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] How to transform coordinates
Hi Jens-Hanno, > i started correcting the dt problem with masks borders displayed at a wrong > position. > > There is a detail i don't understand and currently dont't know how to do. > > Lets assume i have a point p(x,y), x and y are both in the 0->1 range > covering the whole > raw data (no lensfun applied). > > So my question: > How can i calculate the position (also 0->1 range for both) **after** lensfun > correction? This is done by a transform function in the IOP. Actually each IOP must provide a distort_transform() and distort_backtransform() function that will transform a set of points. Fact is lens.cc seems to have the very same implementation in transform and backtransform which is obviously pretty wrong. I had started fixing that, but it seems there is something more. I can create a PR with what I have now if you want to start from that, let me know. When mask needs it calls a generic transform function in one direction or the other in the pipe and this will trigger calls to transform functions for each active IOP. Hope this helps, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Feature freeze for 3.0
Hello Pierre, > from my side I will help as last year at the German translation for > darktable and the German user manual. > > It would be nice if there would be a trigger signal when the translations > can be started. Sure. I'll send a notification here. > Does darktable 3.0 have its own branch or is this in master? Still master as the branching has not started. > Is the manual included in the same branch as darktable as in previous > versions or is the manual separated? In the same branch but we always do the translation from the master branch as when translation starts we have a feature and string freeze and the actual branch will be created for RC0 release. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
