I hesitate to bring this up because I haven't flushed it all out, but since 2.4.0 release is coming I think it might be work mentioning.
Images that printed more-orless fine under 2.2.x (see comments below though), came out with a deep green cast under 2.4.0-rc1. I haven't have a chance yet to try rc2. I suspect that it isn't a coincidence that the first images I opened after starting that (darktable) process were .tiff files I had already created using dcraw with a UniWB (-r 1 1 1 1). I did a little very trivial editing on those .tiff and then opened to a completely different folder of .NEF files and printed one. It printed with a very green cast. I made a few changes in the setup hoping to fix it, and printed again. It came out identically green cast. To make sure it wasn't a CUPS driver change, I printed from GIMP, which produced a normal looking output. Is it possible that the color matrix of an image opened earlier could be stored and used by the print module for a completely different image? -- I might mention also, that under version 2.2.x, when I went from editing in Darkroom directly to the print module, it almost always let out the latest edit changes. I learned to leave Darkroom to Lighttable, select a different image, then change the selection back to the original image and then the print module would include all the edit changes. I apologize for not having a code fix, or even figuring out exactly what is going on with the printing. I'm hoping this might ring a bell with someone already familiar with the module. --alan ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
