Dear all,
we just released another patch version for the stable branch 1.2. As usual you can find the source tarball here:
- source tarball
- The Ubuntu PPA has already been updated by Pascal (thanks!),
- OS X disk image
- other builds will follow soon
We don’t have too many commits to report but since quite some of those we picked concern support of new hardware we decided to release this version comparatively early making it more or less a “hardware release”:
- updated rawspeed r553. Support for
- Canon EOS 700D
- Nikon Coolpix P330
- New Olymbus base curve
- Updated Adobe Coeffs
Enhanced color matrices:
- Canon 700D (from Canon 650D)
- Canon 100D (from Canon 650D)
- Sony NEX-7
White balance presets:
- Some updates from UFRaw
- Canon 100D
- Canon 700D
- Sony SLT-A37
- Nikon Coolpix P330
Noise profiles:
- Canon EOS-M
- Olympus E-600 (from: Olympus E-30)
- Olympus E-620 (from: Olympus E-30)
- Samsung WB2000
- Sony A99v
- Panasonic DMC-G10 iso 100
- Nikon D60
Bug fixes:
- 0 star rating working again
- LT: ctrl+d duplicates per default now
- Some fixes concerning locale handling
- double click on film strip jumps to image
- remember position in collections
- ctrl+k jumps to previous collection
- Blending parameters are preserved when module is deactivated
- In full-preview (alt-1) ratings and labels are only applied to image shown
- Various OpenCL fixes, e.g. compilation on Mac OS X
- libsquish compilation now optional
- dr: deactivate interpolation at 200% zoom
Enjoy the release!
(and as usual: give feedback, report bugs, read our blog, try the development branch, go out and take photos…)
I've posted in another place the P330's noise profile. I've not received any feedback, so I do not know if I was wrong or what. I repost here the link
http://pastebin.com/AwkiFc4W
sorry anyway for the noise
thanks a lot for everything !!
please love to the apple!!
anyways, could you also upload the pdf graphs somewhere so i can check the profile makes any sense?
I'll do it as soon as I'm on that box. Thanks!
Thanks
Thanks all programmers, who make this possible!!!!
http://we.tl/E9vFBmC5uG
link availabe for 2 weeks
TIA
thanks a bunch!
I don't know if it's because nobody created it or it just hasn't been included yet.
Is there a way i can do it manually somehow?
Thanks
Process: darktable-bin [6268]
Path: /Applications/darktable.app/Contents/MacOS/darktable-bin
Identifier: org.darktable
Version: 1.2.2 (1.2.2.0)
Code Type: X86-64 (Native)
Parent Process: launchd [289]
User ID: 502
[crash report cut away]
Until then, though, I may compile and install it in its own prefix (and do likewise with GIMP 2.9). As an Olympus EM-5 shooter, I'm curious about Darktable's new Olympus base curve.
I saw and read the link above to the 1.1.1 release comment by Jo. I can code, but I recognize that if I try to implement that long list it is going to suck. And take forever because I'm an old transportation engineer, not a young graphics hacker. (Oh to be young and able to get by on a few hours of sleep again)
I would certainly donate debugging time, and would contribute to a kickstarter if that would be helpful, but until darktable supports the x100s sensor, I'm dead in the water with RAW images (I try only to run linux).
Good product, hope I can convince you to hack on the fuji x100s sensor.
$ LANG=C darktable
and it should pop up in English. We do not have a language switcher yet, there have been first attempts but it turned out to be problematic and we removed it again.
during my work with images I need write comments or tasks for all one image. Is there something as 'TODOs' or any posibilities how to write these comments for image?
If not...
I'm seeing weird results when setting the input color profile.
If I set the input profile to one I'm using in ufraw for my oly omd-em5,
I get a radical shift to red/magenta.
I've activated the "unbreak input profile" module to set the gamma and linearity, but it still shifts way too far red/magenta.
I have a sneaking suspicion I'm missing something?
I hope one day cause I got a X-E1 and Darktable is an excellent software.
http://www.darktable.org/2012/12/released-1-1-1/comment-page-1/#comment-8553
Darktable's default output for the OMD-EM5 should be quite good out of the box, with little need for external profiles.
More details:
http://www.darktable.org/2012/12/released-1-1-1/comment-page-1/#comment-8553
Any plans to implement a function which allow to see on a picture which auto focus points were used in darktable?
This functionality would help to learn how to avoid next time unsharp pictures?
In the meantime, are there any available tools which shows which auto focus point were/was used?
Thank you in advance,
Mic