It is done, 1.0 is out. I sent out most of the new features with the announcement for 1.0rc2 a few weeks ago already, but for completeness, here it is again:
- New cameras supported
- Leica M9
- NX100/NX5/NX10/NX11
- Panasonic DMC-GX1
- Pentax K-r
- Canon Powershot S100
- Olympus XZ-1
- Olympus E-P3
- Sony DSLR A330
- Sony NEX-5N
- Canon EOS 1000D
- Canon EOS 600D
- Sony Alpha 390
- Fuji Finepix HS20EXR
- New and updated translations (we now have chinese!)
- New modules:
- shadows & highlights
- enhanced tone curve. now operates in a and b channels as well
- Refactored modules:
- import
- snapshots (enable sliding separation line between before/after images)
- metadata
- New image cache
- faster concurrent access and insertion
- reduces needed memory
- more thumbnails stored on disk
- read embedded jpegs for creating thumbnails (faster folder import)
- Increased general speed on sqlite3 (journaled, pagesize optimizations)
- Reworked, modular UI
- Keyboard shortcuts support – key accelerators (GSoC)
- Unity launcher support (Ubuntu)
- Quicktool bar: exposure, presets and styles
- New color picker
- Web gallery export now with next/prev buttons per image
- Removed gconf: not used anymore, we have our own backend
- Bugfixes
Also, a couple of caveats to keep in mind this time:
- We don’t support fuji superccd at this point (more or less a simple fix, if you want to do it, contact us …)
- We disabled openmp by default for mac builds, as gcc on that platform seems to have some issues (<gcc 4.6, that is).
- We had to roll back libraw to <14.5, so the fuji X10 is not working at the moment.
- There have been issues with memory on 32-bit systems. seems to be okay currently, but something to keep in mind. use 64-bits if you can!
And as always a couple of links, just in case.
-
Source tar.gz:
https://sourceforge.net/projects/darktable/files/latest/download
-
Ubuntu Packages are readily available on Pascal’s PPA, for Lucid, Natty, Oneiric and Precise. Support for Maverick has been fully deprecated.
https://launchpad.net/~pmjdebruijn/+archive/darktable-release
https://launchpad.net/~pmjdebruijn/+archive/darktable-release-plus
If you have 0.9.3 already installed and are upgrading using update-manager, it may ask about a partial upgrade, which should be ok (since we are rejecting the old darktable-plugins-experimental package).
-
Pascal’s screen casts (for the 0.9 series, but still valid):
https://encrypted.pcode.nl/blog/2011/11/05/darktable-0-9-screencast-library-addition/
-
Our blog with some cool insider info:
And some advertising, we might be looking for students to take on GSoC this year:
https://sourceforge.net/apps/trac/darktable/wiki/GSOC
https://sourceforge.net/apps/trac/darktable/wiki/GSOC_idea_list
And of course, huge thanks to all who helped make this possible! every half hour you can steal from your jobs and families makes a difference ;)
Also a darktable release announcement can’t come without the warning that this version will soon be completely obsoleted feature-wise by the git version. We have some cool stuff sitting around in branches, waiting to be merged (spoiler: cleaner, more unified module UI with new widgets, similarity-based image clustering and search, refined conditional blend modes, maybe at some point geo tagging with map support in the center view, and possibly masking).
Have a lot of fun.
now your new fun will be to implement the possibility to apply the corrections/effects with brush in limited areas.
With this implementation will be the best program ever!
question: for the rest of the cameras, will be 400d supported later?
http://darktable.git.sourceforge.net/git/gitweb.cgi?p=darktable/darktable;a=blob;f=src/common/colormatrices.c
so you should be fine and get quite nice results for your RAW files right out of the box.
sorry for bothering, that means.. that already in this new [1.0] version?
and what is "tethering"
This is the program for which I could definitely leave Windows.
Tethering (tethered shooting): e.g. http://www.brighthub.com/multimedia/photography/articles/40216.aspx
can someone reproduce this thing?
screenshot:
thanks in advance, great program anyway
indeed this is a config thing. In some cases when upgrading from an older version darktable has no correct values for this.
Go to the options menu (the small gear wheel in the top panel) and check the values for "width of image drawing area" and "height of image drawing area". I assume both are set to 0. Set both to something close to your screen resolution (not completely since you have the sidepanels covering some screen) and after a restart of dt you should be fine.
Best regards,
Simon
Darktable is awesome, just upgrade to 1.0 in Ubuntu. Tonight is a long night of work!
Maybe you want to file a bug?
http://sourceforge.net/apps/trac/darktable/report/1
Anyway thanks for the hard work, I love your software !
Getting some out of place fonts/controls: https://img577.imageshack.us/img577/8787/capturanoua00029darkfon.jpg that 1.0-rc2 and older did not have.
What am I missing?
Any ideas how to solve this ?
By the way, thank you for your hard work, I love your software !
(PS : the comments on the website don't seem to work with Opera)
Debian Sid 64bit, git compiled, some font sizes and controls are wrong: https://img577.imageshack.us/img577/8787/capturanoua00029darkfon.jpg yet there were ok on the RCs. What am I missing?
I'm using Ubuntu 10.4 LTS and I'm also getting the skull thumbnails problem. It hasn't crashed so far though. Should I purge my previous thumbnails cache? TIA :)
you are on the wrong version of darktable. You pulled recent master, which has already received lots of additions many of them in a very early stage. This is not what you want! Either get darktable-1.0 tarball from the resource mentioned above, or pull git branch "darktable-1.0.x" where we only put in bug fixes for 1.0, not new features.
Now 2 other things, first I can't really tell if OpenCL is really used, 'nvidia-smi -q' does not report more memory used up while running darktable, and darktable-opencl seems to fail somehow: http://pastebin.com/qtbnZf5G
And second, while running darktable some sort of sqlite errors occur: http://pastebin.com/dcfdJPUM
1. you can run "darktable -d opencl" and it will give you detailed information about its efforts running opencl.
2. Hm, could you please try to run with a new db? maybe something went wrong while upgrading from 0.9.3. Remove ~/.config/darktable/library.db for this.
Could you maybe provide an example raw file?
1. looks like opencl is working ok in darktable, yet the test program behaves strangely like that.
2. i've deleted the library db several times while playing with 1.0rc and final, yet i always see those sqlite3 errors.
3. is it ok for darktable to use 5.5gb of RAM ( out of 6 ) and 1.5gb of swap space when I just open a file from a previously scanned folder?
First I thought it might be Cinnamon Desktop but same happens if I switch to Xfce.
Now DT is working fine for the first pictures I'm working on, but begins to be really slow after a few pictures.
The problem comes from the RAM management, DT is unable to free my RAM memory after I open a new picture. I took a screenshot of the Ubuntu Monitor as I open around 6 pictures. You can clearly see the ram use increasing each time I open a picture; after reaching the RAM limit (4 Go), it uses the swap and begins lagging...
Here is the sceenshot : http://my.opera.com/Wangtim/albums/showpic.dml?album=9739912&picture=148132402
Should I file a bug on sourceforge ? Is there a way to solve this problem ?
Thank you !
thank you devs!
If you still get errors, please try to run darktable from the command line and contact us in darktable-devel at lists.sourceforge.net
What is that a French documentation is planned for V1.
Why do not to create a documentation in the form of Minmap, including tutoriels, usable with Freeplane, and also in French language of course.
It would allow to structure the documentation according to what we want to make on Darktable.
Of what think of it you?
* number of background threads must be 1
* host memory limit should be 500
* minimum amount ... single buffer should be 16 or 8
With this you should normally get no skulls even on a 32bit system.
All of them are Jpegs.
I tested the latest unstable version but it did not solve anything. It's quite annoying since it's making the software almost unusable...
Thank you for your help !
could you please run darktable from console with
darktable -d memory
and
darktable -d cache
This should get us some more informations that help to track down that issue.
/Simon
[memory] at startup
[memory] max address space (vmpeak): 164536 kB
[memory] cur address space (vmsize): 164536 kB
[memory] max used memory (vmhwm ): 5744 kB
[memory] cur used memory (vmrss ): 5744 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 390528 kB
[memory] cur address space (vmsize): 377172 kB
[memory] max used memory (vmhwm ): 42344 kB
[memory] cur used memory (vmrss ): 42344 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 509316 kB
[memory] cur address space (vmsize): 495960 kB
[memory] max used memory (vmhwm ): 161380 kB
[memory] cur used memory (vmrss ): 161380 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 589688 kB
[memory] cur address space (vmsize): 576332 kB
[memory] max used memory (vmhwm ): 161400 kB
[memory] cur used memory (vmrss ): 161400 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 670048 kB
[memory] cur address space (vmsize): 656692 kB
[memory] max used memory (vmhwm ): 161408 kB
[memory] cur used memory (vmrss ): 161408 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 750404 kB
[memory] cur address space (vmsize): 737048 kB
[memory] max used memory (vmhwm ): 161412 kB
[memory] cur used memory (vmrss ): 161412 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 830760 kB
[memory] cur address space (vmsize): 817404 kB
[memory] max used memory (vmhwm ): 161416 kB
[memory] cur used memory (vmrss ): 161416 kB
[memory] after cache initialization
[memory] max address space (vmpeak): 911116 kB
[memory] cur address space (vmsize): 897760 kB
[memory] max used memory (vmhwm ): 161420 kB
[memory] cur used memory (vmrss ): 161420 kB
[memory] after successful startup
[memory] max address space (vmpeak): 1516016 kB
[memory] cur address space (vmsize): 1502660 kB
[memory] max used memory (vmhwm ): 241556 kB
[memory] cur used memory (vmrss ): 241556 kB
[memory] before pixelpipe process
[memory] max address space (vmpeak): 2515512 kB
[memory] cur address space (vmsize): 2502156 kB
[memory] max used memory (vmhwm ): 773196 kB
[memory] cur used memory (vmrss ): 709380 kB
darktable -d memory after the RAM is full :
[memory] before pixelpipe process
[memory] max address space (vmpeak): 4716372 kB
[memory] cur address space (vmsize): 4067788 kB
[memory] max used memory (vmhwm ): 3201696 kB
[memory] cur used memory (vmrss ): 2858916 kB
darktable -d cache at startup :
[image_cache] has 262144 entries
[mipmap_cache_init] cache has 1024 entries for mip 0 ( 78.48 MB).
[mipmap_cache_init] cache has 256 entries for mip 1 ( 78.47 MB).
[mipmap_cache_init] cache has 64 entries for mip 2 ( 78.47 MB).
[mipmap_cache_init] cache has 16 entries for mip 3 ( 78.47 MB).
[mipmap_cache_init] cache has 4 entries for mip 4 ( 78.47 MB).
darktable -d cache after opening a few pictures on the lighttable :
[mipmap_cache] level 0 fill 32.34/70.64 MB (45.79% in 422/1024 buffers)
[mipmap_cache] level 1 fill 0.00/70.63 MB (0.00% in 0/256 buffers)
[mipmap_cache] level 2 fill 0.00/70.62 MB (0.00% in 0/64 buffers)
[mipmap_cache] level 3 fill 0.00/70.62 MB (0.00% in 0/16 buffers)
[mipmap_cache] level 4 fill 0.00/70.62 MB (0.00% in 0/4 buffers)
[mipmap_cache] level [full] fill 1/3 slots (33.33% in 1/16 buffers)
Is it helping ? I'm not that familiar with console...
What about a migration tool for the late Bibble disappointed users ?
I rely heavily on the curve tool, and someone decided it was a good idea to put "guides" onto the curve tool, restricting its free manipulation. Yes, I can get the curve I want, but only with a lot of effort. I see no way of turning these "guides" off.
This is actually a "killer" for me in the sense that I find Darktable unusable in it's current form. It's a shame because it looks really nice otherwise.
(Incidentally, it installs without trouble under Xubuntu 10.04)
If you too have encountered this problem, take heart - there seems to be a fix. Simply remove your database file (user/config/darktable) so the lighttable appears empty of images, and add each image to be edited individually, removing them again after export. This keeps memory usage down enough to make the program usable.
could you please check for the settings "width/height of image drawing area" - are they really big? Set them to something around your screen resolution (a bit less) and try again.
cheers,
Simon
if you want to join working on documentation best thing right now would be joining the (users) mailing list and find people to help you. Don't be afraid of your English, most of us aren't natives... :)
Simon
we appreciate patches!
Since none of the developers (afaik) uses (or ever used Bibble) we might need some external expert on this - you? :)
Those "guides" (if you mean the light grey areas) have been there for a long time I think. They just prevent you to "break" the line and make sure you have smooth transitions.
Maybe you can describe (or even better: take a screencast) how this inhibits your workflow so we can take a look how to improve that.
Please send a mail to the devel's mailing list: https://lists.sourceforge.net/lists/listinfo/darktable-devel
hopefully we can find a way for you so you can enjoy using darktable...
best regards,
Simon
this is a rather hacky way. Did you check your settings? Have a look at:
"don't use jpegs but half-sized raws" OFF
"memory in bytes to use for mipmap cache" something that suits your RAM
As far as I understand you don't have problems with the processing itself but with the thumbnail cache?
The couple of time I've tried it, I've also been quite frustrated with the curve tool. That is the main reason why I have only used it for testing. I want to manipulate the curve the way I like; add as many points as I wish, bend the curve as I wish. I'm not always looking for natural look. Please consider adding a button: "remove guides".
The second slight disappointment is the highlight recovery. At least AfterShot Pro seems to do a lot better in that section.
Keep up the good work!
I made a few tests and it seems the problem is only happening with jpegs, and not with raws. I shooted a lot of raws and the ram memory was quite stable; but as soon as I work with jpeg, the memory increase each time I open a new picture and never comes down (not until I close DT).
Hope it helps solving the bug :)
I will try to post an e-mail with some more details in the developers mailing list (I did try this about a month ago, but it never got posted).
Other than that it's great! Keep it up, I can't wait for 1.1!
My system:
AMD FX-4100
8 GB RAM
64 GB SSD
Vanilla Ubuntu Oneiric 64-bit
Thanks!!!
Regards from Spain!!!