On Tue, May 6, 2014 at 8:21 PM, Jean-Pierre Verrue <[email protected]> wrote: > Today I have renewed all my previous tests with photoprint and > turboprint. I have also experimented a work around to produce a file > that LR can import. > > - I have re-installed photoprint and printed the jpg file produced by DT > from my old DNG file. The result is unacceptable because it's too > saturated, too yellowish, too greenish. There is curious noise added by > the software (of course, Iset color management and loadedpaper icc profile)
What ICC profile did you use here? Pascal's? ICC profiles need to be matched to the printer settings used for profiling. Otherwise the correction is just wrong. > - To work aroundthe inability to open files produced by dt with LR, I > opened the dt's tiff with gimp and just export a jpg. Now this jpg > was opened finely from LR. I printed the picture (with paper profile, of > course). The printed picture is fine. Saturation and color look like > what you can see on screen (of course, my screen is calibrated), no noise... So your printer is fine. That's actually a good thing to know. It's easy to get some clogged heads and spend a bunch of paper and ink chasing a non-existent profiling issue (ask me how I know). > I know that these three systems use different RIP : > - LR uses the RIP included in the EPSON driver > - Photoprint uses the Gutenprint RIP > - And TurboPrint uses is own RIP > I know that normally, I should use a specific profile for each RIP and > each paper, because colours can be rendered differently by RIPs, but it > is strange that whatever the profile, be it a profile provided by the > manufacturer of paper, or calculated by a profile provider, or a profile > made by myself with a spectrophotometer, whatever paper or printer, I > always get the same kind of results: printings look far too saturated, > too green, too yellow. Using a profile meant for another RIP is just a waste of paper and ink. And doing your own profiling is harder than it should be, but it's possible. If you want I can dig up my notes from doing it all by hand with argyll to get proper output on a R2880. > I have done so many unsuccessful tests, lost so much time, I have messed > so much paper and so much ink for several years, that today I affirmthat > there is no possibility to print photos correctly¹ with linux. I expect > to be shown to the contrary, with photographs to be shown. If you are > interested, I can send you my tests by mail. Your frustration is very familiar. Before I got a working workflow it was really disappointing. What I remember got me over the edge was setting the Gutenprint color profiling options to "Uncorrected" (or similar wording) to disable all color correction in Gutenprint and then profiling with the color munki. Before doing that the color munki profiles were no good. After that it started to work fine. The color management infrastructure in Linux isn't quite there yet but it has advanced very fast. colord/gnome-color-manager has been a huge step forward. That can be a different thing to try too. Pedro ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
