Hugo source code and other artifacts used to generate the public Darktable website, found at https://www.darktable.org/
Make sure you have hugo version 0.78.2 installed. You can run make install-mac or make install-linux.
Then, run make server and navigate to http://localhost:1313.
FYI, Firefox is telling that the SSL certificate for darktable.org is expired. Same story for redmine.darktable.org.
www.darktable.org uses an invalid security certificate.
The certificate expired on August 19, 2018, 12:01:50 AM GMT-7. The current time is August 19, 2018, 12:51 PM.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Same story using a private window or Chromium (never visited darktable.org via Chromium before.)
As usual, I have set up a place where we can draft the blog post for darktable 4.0. Please feel free to write some stuff here
I tried to include a link to darktable.org on my LinkedIn profile and it doesn't show a preview image. The title it picks up is "by photographers" and the description is "darktable is created for photographers, by photographers . Having developers that are also avid photographers as part of the target audience is good for understanding the real world problems, challenges, and workflows. darktable edits your images...".
It would be nice to include some metadata so that this stuff populates correctly when linking from external sites.
Some googling suggests that LinkedIn (for example) needs the following:
<meta property='og:title' content='Title of the article"/>
<meta property='og:image' content='//media.example.com/ 1234567.jpg"/>
<meta property='og:description' content='Description that will show in the preview"/>
<meta property='og:url' content='//www.example.com/URL of the article" />
At least two dead links in https://www.darktable.org/2021/07/darktable-3-6/ aka https://github.com/darktable-org/dtorg/blob/master/content/blog/2021-07-03-darktable-3.6/index.md:
Thanks to countless hours of work of very dedicated contributors, all of the new features are fully documented in time in the user manual
https://docs.darktable.org/usermanual/3.6/en/ works.
This time we are also launching a new version of the lua documentation, here.
No idea what the correct URL is here.
Found english content in the german manual.
I only checked these four:
https://darktable.gitlab.io/doc/en/
https://darktable.gitlab.io/doc/fr/
https://darktable.gitlab.io/doc/de/
https://darktable.gitlab.io/doc/it/
Sends me here:
https://gitlab.com/users/sign_in
see title.
@patdavid: Just as the title, go on news page and blog page and see that there no automatically generated thumb image.
As last time, I've created a page on hackmd for us to begin drafting the release article for darktable 3.6.
For now I've assumed we're going for a summer solstice release (20 June 2021).
Since pages in darktable.org are usually rather long, it would be nice to have a TOP button at the bottom of each page.
Viceversa also a 'stick' header/menu will do the same service.
It's that time of year again. I've set up an empty (for now) hackmd page to start the draft here
A common question on the pixls forums goes along the lines of "I want feature X, would you develop it if I donate some money". Rather than answer the question every time and repeat the same discussion it would be great if we could have a specific "contributing" page on darktable.org itself to which we can link. I would suggest that it should explain that the project accepts contributions of people's time (testing, bug reports, pull requests, forums etc.) but not money, giving reasons (e.g. the effort of administration/organization vs likely income, difficulty of working out how to allocate the money, tax issues etc.).
The dtorg README.md file currently says this as the very first complete sentence in the file:
"A work-in-progress for a hugo port of the darktable website."
I heard a rumor that the public darktable.org web site is now actually backed by the code in this repo. I'm still not sure if that's the case.
If this is the repo that backs the current production site, I recommend changing that text to something like:
"Hugo source code and other artifacts used to generate the public Darktable website, found at https://www.darktable.org/"
Seeing the "in progress" wording in the README.md file on this repo prevented me from realizing that this was, in fact, the right place to report other issues with the web site. That wording led me to believe that this was an in-progress migration effort that would probably not appreciate reports of other things on the public website.
See http://rawspeed.org/ for how it should be
As darktable 4.0 will be with now grey theme by default, maybe screenshot on darktable.org homepage will need to be updated for the darktable 4.0 release day?
Actual screenshot is mine (with some of my photos).
@elstoc: as this move is thanks to you, I think it would be good if that time screenshot is from your side. If you want of course.
At the bottom of http://www.darktable.org/development/, the instructions to contribute insist a lot on using git format-patch origin/master, but barely mention pull-requests. If I understand correctly, GitHub pull-requests are the preferred way to contribute (but I may well have missed something). The text should probably:
git format-patch but state more clearly that it is an alternative for people who don't want to use GitHubContact page currently has
development mailing list: bugs, ideas, patches, translations – all goes here. This is also the right place to report vulnerabilities.
This should be updated to reflect that github is the place for these things, though I'm not sure what we should say the mailing list is for.
Currently https://www.darktable.org/install/ refers to 3.6.0 release, while 3.6.1 is already out.
Please make sure that you use darktable-3.6.1.6.dmg build for macOS, not darktable-3.6.1.5.dmg, since older build has a bug limiting supported OS versions (see darktable-org/darktable#10087 for details).
Just like the 4.2 release notes, the https://www.darktable.org/resources/camera-support/ page should also clearly state (before the table preferably) that these compression modes are not currently supported:
This should help set expectations and reduce constant opening of related duplicate issues.
Which new feature or section need to be documented/updated
Currently on the install page (http://www.darktable.org/install/#macos), the Homebrew install command is listed as:
brew cask install darktableWhich results in an error on the latest version of brew (2.7.3 at time of writing).
Error: Calling brew cask install is disabled! Use brew install [--cask] instead.With the latest version of Homebrew, the recommend command should be:
brew install --cask darktable$ brew -v
Homebrew 2.7.3
Homebrew/homebrew-core (git revision e2dd38; last commit 2021-01-13)
Homebrew/homebrew-cask (git revision f44435; last commit 2021-01-13)Search results involving darktable point to: https://www.darktable.org/usermanual/en/
Which has the old 2.4 documentation.
The current location for the latest documentation (3.0 atm) is to be found here: https://darktable.gitlab.io/doc/en/
Although a markdown conversion is being done at the moment that will make building the docs on the main darktable site easier it would probably be a good idea to create a redirect from on site to the other.
This will fix:
PS: I got the hint on IRC that I should ping @patdavid for this.
color balance rgb
Finally, the linear color-grading takes place in a specific RGB color space (published in 2019) to exhibit a uniform repartition of Munsell hues across the luminance range.
(Cannot send a PR, as I don't know what space is used.)
Color calibration
darktable 3.6 also introduces an OpenCL kernel for color calibration, which should be 0.3× to 8× faster than the CPU path, depending on hardware.
This is hard to interpret. If the speed is 0.3x that of the CPU path, it means it's slower. If the time taken is 30% less, then the 8x figure is meaningless ('the time taken is 800% less').
Crop, Shapes, Retouch and Pipe Distortions
In addition, the gradient mask can now have its curvature set before it is placed on the image, and with greater accuracy.'
Maybe it's just me, but this sentence reads weird. Does this mean that the curvature of the mask can now be set more accurately?
RCD
This method is also orders of magnitude faster than AMaZE
Is it really over 100x (2 orders of magnitude) as fast? If it's just a figure of speech, wouldn't an order of magnitude be a better choice? Or simply a lot faster than, several times as fast as?
Reverse blend modes
The darktable default for blending modes is to apply the module output over the module input with some optional transparency (using classical alpha compositing and assuming a fully opaque input). The reversed modes instead apply the input over the output.
It think it'd be worth mentioning that this is only important when drawn or parametric masks are involved (see https://discuss.pixls.us/t/find-a-creative-use-case-for-each-blend-mode/25089/3). But maybe that belongs to the manual?
I think it'd be a good idea to move to a static site generator that we're using more and more in the community, hugo. It's a single binary, battery included package that is fast. You don't have to worry about upgrading python versions or keeping up to date with plugins. It just works.
The darktable.org/install/#3rdparty section, documents the existence of third party packages and PPAs for various Ubuntu versions, including Ubuntu 20.04 LTS. However, the offered "latest release" and "master" PPAs and binaries for Ubuntu 20.04 do not work because of a series of severe dependency conflicts and problems that cannot be solved by simple installation of missing packages.
Important: This issue is not about troubleshooting those installation resources.
In spite of darktable.org not being the developer of those resources, and regardless of whether those issues are or are not going to be solved and by whom, the darktable.org documentation is referencing that [wrong] information, thus it's (like it or not) bound to it. The site is naturally seeked as a reference, and expected be curated to at least exclude bad information when detected. Therefore, that section needs an urgent update by removing "Ubuntu 20.04" from the list of supported installation by those specific resources, until and if they ever get corrected or replaced by any demonstrably working resources.
One possible alternative could be modifying the wording of the page to make it (currently it is not) very explicit that DT.org does not maintain, test or endorse any claims made by any third party resources listed in the page.
However: unfortunately, it is also true that such honest wording in the document implies and provokes a sense of distrust to whomever is seeking it for good source of documentation. That would lower the level of usefulness and trustability to that of any random online blog offering a "How To Install", which makes this a very bad idea for a serious project: Nobody goes to e.g. https://developer.mozilla.org to look for a reference that "may or may not" be correct.
Furthermore, I would suggest that any third parties that would like to be referenced as a good installation resource by the official documentation, should offer a public, direct support contact to those responsible for it, so that users can report issues and feel that there is ownership. Sadly, that's not the case in this very issue.
The following illustrates the issue that misleaded users trying those resources are facing:
Attempting to install a binary package for Ubuntu 20.04 will result in this:
$ sudo dpkg -i darktable_3.2.1-1.1_amd64.deb
Selecting previously unselected package darktable.
(Reading database ... 466817 files and directories currently installed.)
Preparing to unpack darktable_3.2.1-1.1_amd64.deb ...
Unpacking darktable (3.2.1-1.1) ...
dpkg: dependency problems prevent configuration of darktable:
darktable depends on libexiv2-27 (>= 0.27.3); however:
Version of libexiv2-27:amd64 on system is 0.27.2-8ubuntu2.
darktable depends on libilmbase25 (>= 2.5.3); however:
Package libilmbase25 is not installed.
darktable depends on libjson-glib-1.0-0 (>= 1.5.2); however:
Version of libjson-glib-1.0-0:amd64 on system is 1.4.4-2ubuntu2.
darktable depends on libopenexr25 (>= 2.5.3); however:
Package libopenexr25 is not installed.
And attempting to use the aforementioned PPA for the same distribution will generate this kind of errors:
darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed
Depends: libilmbase25 (>= 2.5.3) but it is not installable
Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed
Depends: libopenexr25 (>= 2.5.3) but it is not installable
E: Unable to correct problems, you have held broken packages.```
It will be more comfortable if the top menu on pages will remain visible while scrolling down contents.
It is quite commonly written incorrectly, so i suppose a FAQ(?) entry might be in order.
https://www.darktable.org/resources/
You can either read the manual online or download it in PDF format:
* English
* French
* Italian
* Spanish
Every single time i press on english, and it opens pdf download.
something like this would be less hostile.
You can either read the manual online:
* English
or download it in PDF format:
* English
* French
* Italian
* Spanish
Search works only if the 'www' prefix is used.
I observed someone come to the conclusion that darktable wasn't available on MacOS because they didn't recognize the MacOS option here: https://www.darktable.org/install/ (Is it using the Leopard logo?)
I think these would be greatly improved with using text alongside or instead of the logos, and perhaps grouping the many Unicies separately.
Some good examples:
https://transmissionbt.com/download/
https://code.visualstudio.com/download
https://signal.org/en/download/
The website shows outdated Darktable logos:
Both should be updated to the current Darktable logo
https://github.com/darktable-org/darktable/blob/master/data/pixmaps/scalable/darktable.svg
The Fujifilm X-T5 not listed as supported on Camera Support page.
Here are the series of steps (as a user) that describe how I got here.
I tried to load a RAW lossy compressed file from a Fujifilm X-T5 into Darktable 4.2.0, and it gave me an error that directed me to camera support | darktable
That page did not list the Fujifilm X-T5 as being supported by Darktable (it was missing from the table on that page, which is automatically generated dynamically from a different place).
That led me to the What's involved with adding support for new cameras | darktable page, which in turn links back to Pixls.us on this article What’s involved with adding support for new cameras. I considered asking for help there, but the last comment on that thread was two years old, and it seemed like a bad idea.
After more digging, it turns out that Darktable does support the Fujifilm X-T5, but it just doesn’t support the RAW lossy compressed files.
Anyway, I think the Darktable web site should probably list the Fujifilm X-T5 as supported. The release notes say it's supported. And Darktable 4.2.0 itself definitely supports it (or at least the RAW lossless compressed files).
Just to be clear, I’m not asking for lossy RAW file support. That was just an experiment. I want the lossless raw files. But what I’m really trying to say is that the Darktable web site should probably say that it does support the Fujifilm X-T5, when in fact, it does. It took me a while to figure that out.
The mac builds are now to 10.14 (https://github.com/darktable-org/darktable/blob/master/packaging/macosx/BUILD.txt). I think the website should say 10.14 instead of 10.7 (Lion).
I've been approached by a user who runs this YT channel (https://www.youtube.com/channel/UC126kKAgMILMnVIi7HvQGlw) that was interested in having his channel listed on the page alongside folks like Huttons videos - would this be ok @houz?
Several pages won't show images where the text clearly shows there should be one. Example links:
In the concerned pages, where the image should be there's code like:
<figure markdown="span" role="group">
<figcaption>*Figure 1:* the gradient test image – follow the link, download and play with it in darktable</figcaption>
</figure>
which shows up like
*Figure 1:* the gradient test image –
follow the link, download and play with it
in darktable```
Check for example this blog entry, there is a big empty space for a broken link to the thumbnail picture:
https://darktable.org/dtorg/sh-thumb.sm_.jpghttps://darktable.org/dtorg/2012/02/shadow-recovery-revisited/sh-thumb.sm_.jpgI guess the handling of wordpress_lede needs to be changed, but I don't know this framework, so I cannot give you a patch myself.
Some image links in the english user manual are broken
Example:
https://darktable.gitlab.io/doc/en/user_interface.html
The english manual links to this image:
https://darktable.gitlab.io/home/pegelow/darktable/build/doc/usermanual/media/images/lighttable_view.jpg
The french manual links to this image:
https://darktable.gitlab.io/doc/images/lighttable_view.jpg
E.g. lens corrections is fully lensfun area;
lens field in image information module is exiv2, with a bit of dt's magic in https://github.com/darktable-org/darktable/blob/master/src/common/exif.cc
I use Darktable on my Chromebook (works well) but I realised that the main installation page on the website doesn't even tell people it works on Chromebooks. I think having instructions for Chromebook would be really helpful given the number of Chromebooks there are.
I've written some basic instructions which should give people all the information they need, but I'm sure could be refined.
Step 1: Enable Linux support on your Chromebook by following these instructions, not all older Chromebooks are compatible.
Step 2: Once you have done this you can install through the Linux Terminal either through:
Option 1: use these commands to install and uninstall Darktable
Install: sudo apt install darktable
Uninstall: sudo apt remove darktable && sudo apt autoremove
Option 2: Install through Flatpak
Install FlatPak using these instructions
Install Darktable using the command line instruction on this page
For the darktable 2.6 article (#25), I'd like to have a table of contents at the top (the article is around 30-screens long ...).
Appartently, there's a way to do that with Pelican and it seems at least partly-activated in pelicanconf.py:
# toc(permalink=True) sets all headers to have an id
# set, and an <a> after the heading.
# see: http://pythonhosted.org/Markdown/extensions/toc.html
MARKDOWN = {
'extension_configs' : {
#'markdown.extensions.fenced_code' : {},
#'markdown.extensions.codehilite' : {'css_class': 'codehilite'},
'markdown.extensions.extra' : {},
'markdown.extensions.headerid' : {},
'markdown.extensions.toc(permalink=)' : {}
}
}
Unfortunately:
Adding [TOC] in the .md files only results in having [TOC] displayed in the article :-(
The page linked to is broken currently down, but it's still available as https://web.archive.org/web/20170513185232/http://pythonhosted.org/Markdown/extensions/toc.html
Any idea how to use TOC in darktable.org?
Thanks,
Hi,
when I was browsing the user manual with window width around 1250px, the font started alternating back and forth between smaller and bigger (Safari 12.1.1).
I can upload a screencast if needed.
I get these paragraph marks for anchor picture. Is this intentional?
After taking a look at the 'resources' page on the darktable website it came to my mind that an update should be done.
First of all this is a very long page containing different topics. Currently there are:
To increase the website's lucidity I recommend splitting these topics into two pages, one with manuals/tutorials for learning the program usage and one with the remaining resources.
An idea is to call the new page 'learning' with the following content:
This would lead to this remaining 'resources' page:
The 'learning' content could need an update. Some of the linked resources are not available anymore.
Moreover, there are many newer sites and video channels which are not listed on the page and should be included.
I could make an overview of the learning material, which is up-to-date, outdated or not available anymore.
Then I could provide a list of learning resources that could be added to the 'learning' page
Then I could provide two markdown files to contribute.
https://www.darktable.org/resources/ lists 'Robert Hutton’s darktable screencast playlist' as 'Screencasts recorded using the latest development versions of darktable'; however, his youtube playlist https://www.youtube.com/playlist?list=PLmvlUro_Up1NBX7VK8UUuyWo1B468zEA0 has not been updated since 2016.
Python 2.7 is EOL and can't be installed on Fedora 31.
I'm not able to find a reference on the website to darktablerc.html. This is generated by the darktable build process. See https://github.com/darktable-org/darktable/blob/master/doc/CMakeLists.txt#L26
In Issue darktable-org/darktable#7123 @floemker referenced article https://github.com/darktable-org/dtorg/blob/master/content/blog/2012-10-23-whats-involved-with-adding-support-for-new-cameras/2012-10-23-whats-involved-with-adding-support-for-new-cameras.md which in turns reffer old script.
Can the article be changed to link to current resources in the header notice? I mean - reference https://github.com/darktable-org/darktable/wiki/Camera-support :)
The camera support list here ans here,
The first point is opinionated though, but it may be more useful or convenient for the user to focus on what's supported, and better for the darktable project communication to focus on achievements.
Without turning the list into a christmas tree like this (I'm the one who did this one), it may be possible to produce something better. I have not found the generator of the table but I see you already use an html table so it may be possible to do more catchy styling. Even without coloring the text or the cell background, one can simply add a coloured emoji (a bit like this other one I did, though I would recommend keeping the “Yes“ and “No” word as you have the space for them).
Here is a very simple example done by just swapping the boldness and capitalization from “No” to “Yes”, and adding a green checkmark next to Yes.
I chose the ✔️ emoji here in this issue because it is drawn as green in GitHub (but usually black without background, GitHub does weird stuff with emojis), but you may prefers others like ✅ (usually white on green but GitHub…) or ☑️ (usually white on blue but GitHub…), or simply a green square 🟩. You would select the best one according to the font used on darktable.org.
| Camera 699 (100%) |
WB Presets 453 (64%) |
Noise Profile 373 (53%) |
Custom Matrix 116 (16%) |
|---|---|---|---|
| Canon EOS 1000D | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS Digital Rebel XS | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS Kiss Digital F | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS 100D | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS Kiss X7 | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS Rebel SL1 | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS 10D | ✔️ YES | No | No |
| Canon EOS 1100D | ✔️ YES | ✔️ YES | No |
| Canon EOS Rebel T3 | ✔️ YES | ✔️ YES | No |
| Canon EOS 1200D | ✔️ YES | ✔️ YES | No |
| Canon EOS Kiss X70 | ✔️ YES | ✔️ YES | No |
| Canon EOS Rebel T5 | ✔️ YES | ✔️ YES | No |
| Canon EOS 1300D | ✔️ YES | ✔️ YES | No |
| Canon EOS Kiss X80 | ✔️ YES | ✔️ YES | No |
| Canon EOS Rebel T6 | ✔️ YES | ✔️ YES | No |
| Canon EOS 1500D | No | No | No |
| Canon EOS 2000D | No | No | No |
| Canon EOS Rebel T7 | No | No | No |
| Canon EOS 200D | ✔️ YES | ✔️ YES | No |
| Canon EOS Kiss X9 | ✔️ YES | ✔️ YES | No |
| Canon EOS Rebel SL2 | ✔️ YES | ✔️ YES | No |
| Canon EOS 20D | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS 300D | ✔️ YES | No | No |
| Canon EOS Digital Rebel | ✔️ YES | No | No |
| Canon EOS Kiss Digital | ✔️ YES | No | No |
| Canon EOS 30D | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon Digital Rebel XT | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon EOS 350D | ✔️ YES | ✔️ YES | ✔️ YES |
| Canon Kiss Digital N | ✔️ YES | ✔️ YES | ✔️ YES |
| Sony ZV-1 | No | No | No |
You may even add next to the camera name a symbol that quickly summarizes the support completeness for a camera so the other columns only have to be read when it's either not fully supported or not supported at all.
| Camera 699 (100%) |
WB Presets 453 (64%) |
Noise Profile 373 (53%) |
Custom Matrix 116 (16%) |
|---|---|---|---|
| 🟩 Canon EOS 1000D | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS Digital Rebel XS | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS Kiss Digital F | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS 100D | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS Kiss X7 | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS Rebel SL1 | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟧 Canon EOS 10D | ✔️ YES | No | No |
| 🟩 Canon EOS 1100D | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS Rebel T3 | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS 1200D | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS Kiss X70 | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS Rebel T5 | ✔️ YES | ✔️ YES | No |
| 🟩 EOS 1300D | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS Kiss X80 | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS Rebel T6 | ✔️ YES | ✔️ YES | No |
| ⬛ Canon EOS 1500D | No | No | No |
| ⬛ Canon EOS 2000D | No | No | No |
| ⬛ Canon EOS Rebel T7 | No | No | No |
| 🟧 Canon EOS 200D | ✔️ YES | ✔️ YES | No |
| 🟧 Canon EOS Kiss X9 | ✔️ YES | ✔️ YES | No |
| 🟧 Canon EOS Rebel SL2 | ✔️ YES | ✔️ YES | No |
| 🟩 Canon EOS 20D | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟧 Canon EOS 300D | ✔️ YES | No | No |
| 🟧 Canon EOS Digital Rebel | ✔️ YES | No | No |
| 🟧 Canon EOS Kiss Digital | ✔️ YES | No | No |
| 🟩 Canon EOS 30D | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon Digital Rebel XT | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon EOS 350D | ✔️ YES | ✔️ YES | ✔️ YES |
| 🟩 Canon Kiss Digital N | ✔️ YES | ✔️ YES | ✔️ YES |
| ⬛ Sony ZV-1 | No | No | No |
Note: instead of ⬛ you can use 🟥 but it may break the “focus on what is supported“ principle, there are other options: ◻🔲◻️, etc.
Edit: As the first column “may be enough”, readibility may be better this way by not catching the eye with what is only needed to be read when it's not fully on or off:
| Camera 699 (100%) |
WB Presets 453 (64%) |
Noise Profile 373 (53%) |
Custom Matrix 116 (16%) |
|---|---|---|---|
| 🟩 Canon EOS 1000D | YES | YES | YES |
| 🟩 Canon EOS Digital Rebel XS | YES | YES | YES |
| 🟩 Canon EOS Kiss Digital F | YES | YES | YES |
| 🟩 Canon EOS 100D | YES | YES | YES |
| 🟩 Canon EOS Kiss X7 | YES | YES | YES |
| 🟩 Canon EOS Rebel SL1 | YES | YES | YES |
| 🟧 Canon EOS 10D | YES | No | No |
| 🟩 Canon EOS 1100D | YES | YES | No |
| 🟩 Canon EOS Rebel T3 | YES | YES | No |
| 🟩 Canon EOS 1200D | YES | YES | No |
| 🟩 Canon EOS Kiss X70 | YES | YES | No |
| 🟩 Canon EOS Rebel T5 | YES | YES | No |
| 🟩 EOS 1300D | YES | YES | No |
| 🟩 Canon EOS Kiss X80 | YES | YES | No |
| 🟩 Canon EOS Rebel T6 | YES | YES | No |
| ⬛ Canon EOS 1500D | No | No | No |
| ⬛ Canon EOS 2000D | No | No | No |
| ⬛ Canon EOS Rebel T7 | No | No | No |
| 🟧 Canon EOS 200D | YES | YES | No |
| 🟧 Canon EOS Kiss X9 | YES | YES | No |
| 🟧 Canon EOS Rebel SL2 | YES | YES | No |
| 🟩 Canon EOS 20D | YES | YES | YES |
| 🟧 Canon EOS 300D | YES | No | No |
| 🟧 Canon EOS Digital Rebel | YES | No | No |
| 🟧 Canon EOS Kiss Digital | YES | No | No |
| 🟩 Canon EOS 30D | YES | YES | YES |
| 🟩 Canon Digital Rebel XT | YES | YES | YES |
| 🟩 Canon EOS 350D | YES | YES | YES |
| 🟩 Canon Kiss Digital N | YES | YES | YES |
| ⬛ Sony ZV-1 | No | No | No |
The resources page currently provides links to the olde worlde version of the 3.4 user manual. For English, this should point instead to the 3.4-tagged dtdocs version.
The Features page has some broken links to blogs, I think these are the correct links:
Ulrich's post (shadows and highlights): https://www.darktable.org/2012/02/shadow-recovery-revisited/
Ulrich's post (tone curve): https://www.darktable.org/2012/02/mastering-color-with-lab-tone-curves/
Johannes' post (color correction): https://www.darktable.org/2012/03/color-correction/
Henrik's post (vibrance): https://www.darktable.org/2011/10/different-kind-of-saturation/
"this post" (color LUT): https://www.darktable.org/2016/05/colour-manipulation-with-the-colour-checker-lut-module/
liquify post: https://www.darktable.org/2016/04/liquify-liquify/
perspective correction: https://www.darktable.org/2016/03/a-new-module-for-automatic-perspective-correction/
profiled denoise: https://www.darktable.org/2012/12/profiling-sensor-and-photon-noise/
Ulrich's post (lowpass): https://www.darktable.org/2012/02/using-lowpass-filter-to-recover-shadows/
Hi,
The article I've started on the future 2.6 release (#25) might be translated into other languages (discussions started about an Italian version on the darktable-users mailing list). Is non-English content acceptable on darktable.org? If so, what is the best way to integrate translations in the website?
Thanks,
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.