lprof-users Mailing List for LProf open source ICC profiler
Brought to you by:
hvengel
Menu
▾
▴
lprof-users — Mailing list for LProf users to exchange information and ideas about using LProf
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(7) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(12) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jurgen G. <jur...@pa...> - 2011-08-05 12:53:23
|
Hi, I'm pretty new to calibration and this is my first time trying to calibrate a scanner... so I went to coloraid and ordered 2 profiles... I just got my calibration cards from Wolf Faust to calibrate my scanner and DSLR. I could perfectly create the input and set the corners... but the pull-down menu next to IT8 Target... is empty (and there's no [...] button next to it to load a directory) Here's a screenshot: http://tinypic.com/view.php?pic=70ypfq&s=7 Anyone knows what I'm doing wrong? I have this issue in Ubuntu (both version 11.04 and 10.04 LTS). LProf version: 1.11.4 dfsg+1.11.4.1-5build1 Thanks, Jurgen. |
|
From: Kai-Uwe B. <ku...@gm...> - 2010-10-14 08:39:38
|
Hello, the libXcm/Xcm packages allows to parse EDID blobs and extract the colorimetry information. To obtain a EDID blob from the current connected monitors there is the oyranos-monitor tool. $ oyranos-monitor -x 0 -y 0 -f=edid -o=edid.bin $ xcmedid edid.bin mnft_id: 14499 model_id: 26237 week: 28 year: 2005 model: "LCD1980FXi" serial: "57104835YB" redx: 0.639648 redy: 0.34375 greenx: 0.290039 greeny: 0.608398 bluex: 0.144531 bluey: 0.0742188 whitex: 0.313477 whitey: 0.329102 gamma: 2.2 mnft: "NEC" manufacturer: "NEC" That could be utilised for LProf's monitor tab. What does you think? kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Kai-Uwe B. <ku...@gm...> - 2010-09-09 14:35:15
|
Students have sent in their final code or links to them. The code samples where are all evaluated. One student could reach an acceptable result. Congratulations to Yiannis Belias. Yiannis' API stabilisation for Oyranos project will allow the Colour Management System project to easier separate the underlying data from the public API. The goal is to let Oyranos expose more stable APIs. His work can officially be found here: http://code.google.com/p/google-summer-of-code-2010-openicc/downloads/list and more practical here: http://github.com/yiannis/gsoc2010/commits/ The final integration needs as usual still time. You might have noticed the fewer weekly reports in the second phase of the program on the according projects email lists. Unfortunedly we have found two students failing on the timeline and goals. Reasons where discussed between mentors and respective students. We are very sorry for this result. Despite of the final results, all students have at least started their projects and created code. So the current results are open to be further continued by interessted people. Thanks to all people who supported and participated with OpenICC in the program. Of course thanks to Google for organising and donating time and money to open source projects through the Google Summer of Code project. kind regards Kai-Uwe Behrmann -- Organiser for OpenICC @ Google Summer of Code 2010 http://freedesktop.org/wiki/OpenIcc/GoogleSoC2010 www.behrmann.name + www.oyranos.org |
|
From: Edward C. <edw...@gm...> - 2010-07-31 15:50:55
|
Hi, I'm using the version of lprof currently Ubuntu 10.04 (specifically lprof-1.11.4.dfsg+1.11.4.1). Initially I found it crashed with a buffer-overflow every time I tried to create a profile from a photo of a ColorChecker. Then I patched cmsprf.c to expand the temp2 array to 40. Now I am able to create a profile, but when I inspect it and check the dE report, I find that every patch has a "Got" value of "0 0 0". The profile turns images almost completely black (some very bright areas may show up, but only in monochrome). What could be causing this issue? Regards, Ed. |
|
From: Hal V. E. <hv...@as...> - 2010-01-31 21:08:49
|
On Saturday 30 January 2010 06:48:05 pm Martin Quinteros wrote: > Hi, mi name is Filo. I'm photographer of agentina. > I have a calibration target x-rite colorcheker classic. While the > outcome with the x-rite software and DNG profiles is good but. I'm not > completely satisfied. with this target I cloud create a color profile > icc with LProf? > Everything I read refers to IT8 targets. > > Thank you > > Filoquin Yes if you build LProf from CVS. But the ColorChecker targets have only a limited number of patches (24) and this limits how accurate the resulting profile is. I don't think you will be totally satisfied with the results no matter what profiling software you use. > > > Yo tengo un objetivo de calibración x-rite colorcheker classic. Si bien > el resultado de el software es bueno pero no estoy del todo conforme. > ¿Con este objetivo podría crear un perfil de color icc con LProf? Todo > lo que leí se refiere a objetivos IT8. > > Muchas Gracias > Filoquin > > --------------------------------------------------------------------------- > --- The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business Choose flexible plans and management services without long-term > contracts Personal 24x7 support from experience hosting pros just a phone > call away. http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Lprof-users mailing list > Lpr...@li... > https://lists.sourceforge.net/lists/listinfo/lprof-users > |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-08-27 09:07:36
|
Dear list readers, Google Summer of Code 2009 projects have officially finished. All projects at OpenICC are brought to successful end. Two projects could almost be completed as planed. One could be brought to a reasonable end. The code will shurely find its way into the according projects or is already included. Even though further work is needed to get it full functional. Many thanks to all three students for their great commitment during these months full of work and the community in giving a helpful hand. We obtained as well helpful feedback on email lists of device related projects. Hal V. Engel, the mentor of Amit Kumar, stated the Qt4 work on LProf is complete and is currently in a branch waiting to be merged into LProf main line. I plan on cleaning up the GSoC2009 branch over the next few weeks and merging it into the main line. This project ran ahead of schedule almost from the beginning. In part this was because it was not nearly as ambitious as the Oyranos related projects and it had well defined goals that were fairly easy to achieve in the allotted time frame. But it was also because the Amit worked hard on getting it done right from the beginning. The two Oyranos related projects, mentored by me, started partitial very early and up to the last day many things in Oyranos itself where not clear. So the two students also worked on defining and discussing module APIs and protocols for the three new Oyranos device configuration modules. This contributed very much to clearing of device related concepts in Oyranos. A very early start had the libraw and Sane modules from Yiannis Belias. He discussed many issues on te Sane email list and found a way, on how to tag colour relevance for Sane options. Still we have to prepare a patch to get this functionality included in Sane. After that it sould get ready to use. Joe Simon's CUPS module for Oyranos had many interessting ideas implemented, but was due to a lack of time not finished. Anyway the "cupsICCProfile" PPD attribute is now understood by this module in Oyranos git. This allowes reading of CUPS server side root only accessible configurations (PPDs). To know a way on how to tag PPD attributes for their colour relevance would be great. This would help to assign a local profile in Oyranos to a printing device with user rights like with all other device backends. The other part of Joe's OpenICC project the KolorManager CMS control panel for KDE could in parts completely be substitited to rely on Oyranos for obtaining device information, reading profile and storing custom ones. All this Oyranos related projects are still work in progress and in a pre-alpha state. Nevertheless this work helps much to advance in understanding many details related to the Oyranos CMS. And last but not least Yiannis and Joe showed interesst in continuing their contributions to Oyranos and KM. Kai-Uwe Behrmann for the OpenICC GSoC 2009 team -- Organiser for the OpenICC GSoC 2009 participation http://freedesktop.org/wiki/OpenIcc/GoogleSoC2009 PS: I am cc'ing OpenPrinting as Till expressed special interesst. |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-22 17:01:05
|
Am 22.06.09, 08:39 -0700 schrieb Hal V. Engel: > On Monday 22 June 2009 02:10:43 am Kai-Uwe Behrmann wrote: >> I know that the linux usb/permission system is a pure mess. E.g. many > The most likely cause is that you have not setup UDEV correctly for the Argyll > meter code. A simple chmod 666 of the device is likely not going to work. > Another possible test is to try this as root to make sure that it is really a > permission problem. See the udev sections of this > > http://www.argyllcms.com/doc/Installing_Linux.html This all might be distributor friendly, but it makes Linux as complicated as things like a Windows Registry. I am shurely not the only one having this problems to install and configure this usb stuff by hand. That said, the usb system(s) are clearly not in the responsibility of Argyll or LProf. But the projects need to dedicate a considerable amount of time to usb and not to colour. Btw. I could use a colorimeter and created the profiles. A chmod 0666 /dev/bus/usb/002/012 was the right thing on my setup. thanks for your hint, Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Hal V. E. <hv...@as...> - 2009-06-22 15:40:02
|
On Monday 22 June 2009 02:10:43 am Kai-Uwe Behrmann wrote: > Hello, > > I'd liked to profile a monitor with LProf, but had less success. > The attached error dialog poped up while accessing the measurement device. > My difficulty was not so much that permissions are not perfect. I had > rather spent a lot of time to find out, which file in the system I have to > chmod to 0666. > So frankly the location in the information window was useless to me: > usb:/bus/0/dev - where is this in the system? > After a while searching the archives and with the help of lsusb I found: > /dev/bus/usb/002/009, umm. > > I know that the linux usb/permission system is a pure mess. E.g. many > devices are mapped to some file but then this file is not communicated > correctly. But with a little more verbose message in LProf, I would have > been able to circumvent that quickly. Something like > ... usb:/bus/0/dev (file:///dev/bus/usb/002/009) ... > > > kind regards > Kai-Uwe Behrmann LProf uses the Argyll meter code. Some of this message is directly from the Argyll meter support back end. Specifically "Configuring USB port 'usb/bus0/deb )Xrite DTP94) to 1 failed with -1 (could not config 1: Die Operation ist nicht erlaubt)" is from Argyll and is all the information the LProf has other than what it was trying to do when this failed. The rest of the message is an attempt to make it more meaningful. The most likely cause is that you have not setup UDEV correctly for the Argyll meter code. A simple chmod 666 of the device is likely not going to work. Another possible test is to try this as root to make sure that it is really a permission problem. See the udev sections of this http://www.argyllcms.com/doc/Installing_Linux.html web page. A a side note the monitor calibration and profiling code is currently in a primitive state and is likely not going to work very well on anything other than a CRT. Hal |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-22 09:06:52
|
Hello, I'd liked to profile a monitor with LProf, but had less success. The attached error dialog poped up while accessing the measurement device. My difficulty was not so much that permissions are not perfect. I had rather spent a lot of time to find out, which file in the system I have to chmod to 0666. So frankly the location in the information window was useless to me: usb:/bus/0/dev - where is this in the system? After a while searching the archives and with the help of lsusb I found: /dev/bus/usb/002/009, umm. I know that the linux usb/permission system is a pure mess. E.g. many devices are mapped to some file but then this file is not communicated correctly. But with a little more verbose message in LProf, I would have been able to circumvent that quickly. Something like ... usb:/bus/0/dev (file:///dev/bus/usb/002/009) ... kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-17 18:30:58
|
Am 17.06.09, 09:04 -0700 schrieb Hal V. Engel: > On Wednesday 17 June 2009 08:46:16 am Kai-Uwe Behrmann wrote: >> scons: *** [translations/lprof_ru.qm] Error 1 >> scons: building terminated because of errors. > > This I don't know since it works here. But looking at my copy of > translations/lprof_ru.ts there is no '<' in column 2 of line 193 so this is a > very strange error message. Is it possible that you have a corrupted file? > Do a diff against CVS head to make sure the files match. Agreed, after removing that file and a a checkout, the message disappeared. All seems fine now :-) kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Hal V. E. <hv...@as...> - 2009-06-17 16:05:04
|
On Wednesday 17 June 2009 08:46:16 am Kai-Uwe Behrmann wrote: > Following your hint, Hal, with the QTDIR variable I get here: Actually you are better off using the qt_directory option for the lprof build since the build will remember this. But either should work. > > /usr/lib/qt4/bin/lrelease translations/lprof_ru.ts > lrelease error: Parse error at translations/lprof_ru.ts:193:2: Unexpected > '<'. > > scons: *** [translations/lprof_ru.qm] Error 1 > scons: building terminated because of errors. This I don't know since it works here. But looking at my copy of translations/lprof_ru.ts there is no '<' in column 2 of line 193 so this is a very strange error message. Is it possible that you have a corrupted file? Do a diff against CVS head to make sure the files match. |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-17 15:57:53
|
Am 17.06.09, 17:46 +0200 schrieb Kai-Uwe Behrmann: > /usr/lib/qt4/bin/lrelease translations/lprof_ru.ts > lrelease error: Parse error at translations/lprof_ru.ts:193:2: Unexpected '<'. This seems to be left over from a unresolved merge. I tried to clean that file and now scons compiles more... |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-17 15:42:57
|
Following your hint, Hal, with the QTDIR variable I get here: /usr/lib/qt4/bin/lrelease translations/lprof_ru.ts lrelease error: Parse error at translations/lprof_ru.ts:193:2: Unexpected '<'. scons: *** [translations/lprof_ru.qm] Error 1 scons: building terminated because of errors. |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-17 15:39:24
|
I installed some more libqt4 devel packages by guessing and after commenting out line qt4.py:241 scons went further on openSUSE10.3, qt packages are as fragmented as xorg, ... & python scons.py PREFIX=/opt/local scons: Reading SConscript files ... Looking for build directory for platform 'linux2' Exact match not found, finding closest guess Found directory build/linux, will build there scons: warning: The Options class is deprecated; use the Variables class instead. File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 41, in <module> scons: warning: The PathOption() function is deprecated; use the PathVariable() function instead. File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 42, in <module> scons: warning: The BoolOption() function is deprecated; use the BoolVariable() function instead. File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 50, in <module> checking endianess ... (cached) little little endian Checking for C header file tiff.h... (cached) yes Checking for C header file usb.h... (cached) yes Checking for C++ header file vigra/impex.hxx... (cached) yes Looking for build directory for platform 'linux2' Exact match not found, finding closest guess Found directory build/linux, will build there scons: done reading SConscript files. scons: Building targets ... /usr/lib/qt3/bin/uic -o build/linux/lprofqt/ui_lprofmainbase.h src/lprofqt/lprofmainbase.ui uic: File generated with too recent version of Qt Designer (4.0 vs. 3.3.8) scons: *** [build/linux/lprofqt/ui_lprofmainbase.h] Error 1 scons: building terminated because of errors. removing of kdelib3-devel, qt3-devel, arts-devel, compiz-devel and compiz-fusion-plugins-main-devel ... uff, hopefully I can restartt ;-) ... but hey scons starts to compile, just sending this email before I have to ... |
|
From: Hal V. E. <hv...@as...> - 2009-06-17 15:26:54
|
On Wednesday 17 June 2009 04:50:47 am Kai-Uwe Behrmann wrote:
> Thanks for your hint Hal.
> Now with scons 1.2 a bit better:
>
> & python scons.py PREFIX=/opt/
> local
> scons: Reading SConscript files ...
> Looking for build directory for platform 'linux2'
> Exact match not found, finding closest guess
> Found directory build/linux, will build there
>
> scons: warning: The Options class is deprecated; use the Variables class
> instead .
> File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 41, in
> <module>
>
> scons: warning: The PathOption() function is deprecated; use the
> PathVariable() function instead.
> File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 42, in
> <module>
>
> scons: warning: The BoolOption() function is deprecated; use the
> BoolVariable() function instead.
> File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 50, in
> <module> NameError: global name 'fullpath1' is not defined:
> File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 71:
> env.Tool('qt4', toolpath=['.'])
> File "/usr/lib/python2.5/site-packages/SCons/Environment.py", line 1690:
> tool(self)
> File "/usr/lib/python2.5/site-packages/SCons/Tool/__init__.py", line
> 181: apply(self.generate, ( env, ) + args, kw)
> File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 260:
> QT4_RCC = locateQt4Command(env,'rcc', env['QTDIR']),
> File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 241:
> raise "Qt4 command '" + command + "' not found. Tried: " + fullpath1 +
> " and "+ fullpath2
The last line is the clue. It can't find your Qt4 installation. You need to
set the qt_directory like this:
scons qt_directory=<path to qt4 installation>
It also appears that QTDIR is not set. On many systems this is either not set
at all (SuSE is like this) or it points to the Qt3 installation (my distro is
this way). So the other option is to do something like this:
QTDIR=<path th Qt4 install> scons
But if you use the first version it will remember this and you only have to do
it the first time you use the scons command in the lprof source tree.
Hal
|
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-17 11:47:29
|
Thanks for your hint Hal.
Now with scons 1.2 a bit better:
& python scons.py PREFIX=/opt/
local
scons: Reading SConscript files ...
Looking for build directory for platform 'linux2'
Exact match not found, finding closest guess
Found directory build/linux, will build there
scons: warning: The Options class is deprecated; use the Variables class instead
.
File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 41, in <module>
scons: warning: The PathOption() function is deprecated; use the PathVariable()
function instead.
File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 42, in <module>
scons: warning: The BoolOption() function is deprecated; use the BoolVariable()
function instead.
File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 50, in <module>
NameError: global name 'fullpath1' is not defined:
File "/data3/CD/programme/Grafik/lcms/lprof/SConstruct", line 71:
env.Tool('qt4', toolpath=['.'])
File "/usr/lib/python2.5/site-packages/SCons/Environment.py", line 1690:
tool(self)
File "/usr/lib/python2.5/site-packages/SCons/Tool/__init__.py", line 181:
apply(self.generate, ( env, ) + args, kw)
File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 260:
QT4_RCC = locateQt4Command(env,'rcc', env['QTDIR']),
File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 241:
raise "Qt4 command '" + command + "' not found. Tried: " + fullpath1 + " and "+ fullpath2
|
|
From: Hal V. E. <hv...@as...> - 2009-06-16 18:03:44
|
On Tuesday 16 June 2009 02:48:32 am Kai-Uwe Behrmann wrote:
> Dear developers,
>
> is scons the actual build system for CVS?
> v1.11.4.1 seems to work fine though.
>
> In a actual CVS directory following output appears, with a scons dir
> copied from the actual tarball:
>
> & python scons.py PREFIX=/opt/local
> scons: Reading SConscript files ...
> Looking for build directory for platform 'linux2'
> Exact match not found, finding closest guess
> Found directory build/linux, will build there
> <type 'exceptions.NameError'>: global name 'fullpath1' is not defined:
> File "SConstruct", line 71:
> env.Tool('qt4', toolpath=['.'])
> File
> "/data3/CD/programme/Grafik/lcms/lprof/scons-local-0.96.91/SCons/Environmen
>t.py", line 1091: tool(self)
> File
> "/data3/CD/programme/Grafik/lcms/lprof/scons-local-0.96.91/SCons/Tool/__ini
>t__.py", line 128: apply(self.generate, ( env, ) + args, kw)
> File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 260:
> QT4_RCC = locateQt4Command(env,'rcc', env['QTDIR']),
> File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 241:
> raise "Qt4 command '" + command + "' not found. Tried: " + fullpath1 +
> " and "+ fullpath2
>
>
> kind regards
> Kai-Uwe Behrmann
Kai-Uwe,
Yes scons is the build system for CVS versions of LProf. In the read me it
has details about how to set the build for CVS versions. But I think CVS now
needs something newer than scons-0.96 since older versions did not have Qt4
support. Try it with something newer like version 1.2 and it should be fine.
The README file probably needs to be updated to reflect this.
Also it is probably better to just install scons on your system rather than
using a local copy in the lprof tree. The reason that older versions of LProf
included a local copy was that at the time many users distros did not supply a
new enough version and it was simpler to include a local copy then to deal
with all of the issues related to the versions that distros typically had. I
think that this is no longer an issue at least for newer distros.
Hal
|
|
From: Kai-Uwe B. <ku...@gm...> - 2009-06-16 09:45:24
|
Dear developers,
is scons the actual build system for CVS?
v1.11.4.1 seems to work fine though.
In a actual CVS directory following output appears, with a scons dir
copied from the actual tarball:
& python scons.py PREFIX=/opt/local
scons: Reading SConscript files ...
Looking for build directory for platform 'linux2'
Exact match not found, finding closest guess
Found directory build/linux, will build there
<type 'exceptions.NameError'>: global name 'fullpath1' is not defined:
File "SConstruct", line 71:
env.Tool('qt4', toolpath=['.'])
File
"/data3/CD/programme/Grafik/lcms/lprof/scons-local-0.96.91/SCons/Environment.py", line 1091:
tool(self)
File
"/data3/CD/programme/Grafik/lcms/lprof/scons-local-0.96.91/SCons/Tool/__init__.py", line 128:
apply(self.generate, ( env, ) + args, kw)
File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 260:
QT4_RCC = locateQt4Command(env,'rcc', env['QTDIR']),
File "/data3/CD/programme/Grafik/lcms/lprof/qt4.py", line 241:
raise "Qt4 command '" + command + "' not found. Tried: " + fullpath1 + " and "+ fullpath2
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
|
|
From: Hal V. E. <hv...@as...> - 2008-07-03 17:51:06
|
On Wednesday 02 July 2008 08:47:38 pm wayne tedder wrote: > Hi, > > I am an avid linux user, (since 1996, yes pre-netscape) and I am trying to > set up a digital darkroom studio for my girlfriend who is a > amature/semi-pro photographer that has decided to make the jump to digital. > > I have been doing a lot of research and messing around with software and > equiptment and have found some suitable equiptment that should work under > linux however there are still some issues with color management that I am > unsure of. She is using a Nikon D80 and I was able to find the color > profile for the camera however we do not own a monitor or a printer that > can handle the ICC color profiles to match. You need to look at your workflow here. Most folks are not using in camera processing if they are at all serious about this stuff at least with DSLRs. Instead I would recommend using a raw workflow of some sort. It si a little more work but you will get a lot more out of your camera. I personally use UFRAW with my Nikon D70. I use profiles created with LProf using a DigitaL TargeT 003 target and I get wonderful results. In the past I have used IT8.7 targets from Wolf Faust for profiling cameras and these also give very good results under most conditions and are significantly less costly (actually they are very afordable). > > The only wide gamut monitor in our price range is the NEC LCD2690WUXi that > can be found here. > > http://www.newegg.com/Product/Product.aspx?Item=N82E16824002169 > > This (and other) LCD wide gamut monitors use special software to calibrate > the color between the graphics card and the monitor, The NEC software actually adjusts the monitors internal color look up tables (LUTs) to calibrate things like gamma, gray balance, black point, black level and for some monitors the white point. In addition, it adjusts white level by adjusting the back light level and adjusts the white point of LED based monitors by adjusting the level of the red, green and blue LEDs in the back light (this gives better results than using the LUT). In addition, the software will create an ICC profile for the monitor once it has completed the monitor calibration step. Most LCD vendors have this type of software for at least some monitor models. And at least in some cases they sell the software bundled with a color meter and the software will only work with the color meter they sell (this is the case for the Samgun software at least). I do not know if the NEC SpectraView II software will work with meters that are not supplied by NEC or which meters this software will work with but looking at their web site it appears that it does not require a NEC supplied meter and that it does work with a wide range of meters many of which are also supported by LProf and ArgyllCMS. By the way stay away from the DataColor devices (Spyder) as this vendor has been openly hostil to the open source community. And by all means get a meter that is support by LProf and ArgyllCMS (we use the same meter libraries). For LCD monitors calibration using the monitors internal LUTs is the best way to do this. Unfortunately none of the monitor vendors other than Ezio will make the specifications for the communications protocol for this available to third parties and this is not part of the VESA DCC/IC standard so every vendor may be (likely is) doing this in different ways. So this functionality is not supported by any software that does not come from the device vendor at this time. One of the LProf developers has the Ezio documentation for this and it is possible that at some point LProf will support this on Ezio monitors. > and I am not sure if > there is a way to handle that under linux. I don't know but the only options for using the vendors software are wine or a virtual Windows session or a virtual OS/X session. You will need to ask NEC support about running this software on a Linux box (but don't expect them to have a clue). You might also check to see if the wine supported software list includes this software. Sorry but there is no way to know without trying the software and I don't have this software. But if you can get the software from a place that accepts returns you could test it using wine and/or a virtual Windows session to see if it can be made to work. If it does not you can return the software. > > LPROF is the only current (up to date) way to calibrate for color pofiles > for my monitor, No there is also ArgyllCMS. It is command line only and not very user friendly but it has powerful, well sorted out calibration and profiling routines. Version 1.0 was just released the day before yesterday. > I was wondering if this can be done with one of the current > wide gammut LCD monitors available or if there is another project or method > for dealing with this? At this point I would recommend using ArgyllCMS since it's display calibration and profiling algorithms are more mature than those in LProf (which are at best alpha level at this time). But keep in mind that no third party software will be able to calibrate the monitor LUTs for any monitor and as a result all of the LUT type calibration will occur in the video card LUTs. This is not the best solution but it can still give very good results. But this depends on the user adjusting the monitor controls correctly to minimize the amount of correction needed in the video card LUT. Looking at the manual for the monitor you are considering it has an extensive set of controls that should allow you to make these adjustments. It even has adjustments for black level and black point which is highly unusual for an LCD monitor. Both LProf (CVS) and ArgyllCMS have interfaces to help users adjust these controls based on measurements from a color meter or spectrophotometer. |
|
From: wayne t. <way...@gm...> - 2008-07-03 03:47:41
|
Hi, I am an avid linux user, (since 1996, yes pre-netscape) and I am trying to set up a digital darkroom studio for my girlfriend who is a amature/semi-pro photographer that has decided to make the jump to digital. I have been doing a lot of research and messing around with software and equiptment and have found some suitable equiptment that should work under linux however there are still some issues with color management that I am unsure of. She is using a Nikon D80 and I was able to find the color profile for the camera however we do not own a monitor or a printer that can handle the ICC color profiles to match. The only wide gamut monitor in our price range is the NEC LCD2690WUXi that can be found here. http://www.newegg.com/Product/Product.aspx?Item=N82E16824002169 This (and other) LCD wide gamut monitors use special software to calibrate the color between the graphics card and the monitor, and I am not sure if there is a way to handle that under linux. LPROF is the only current (up to date) way to calibrate for color pofiles for my monitor, I was wondering if this can be done with one of the current wide gammut LCD monitors available or if there is another project or method for dealing with this? We are also thinking of purchasing the Epson stylus pro 3800 printer. Since we are still in the process of purchasing equiptment I am trying to get any and all advise that I can scrape up. Thanks :) Wayne |
|
From: Kai-Uwe B. <ku...@gm...> - 2008-03-31 09:56:31
|
Hello, as the organisator for the OpenICC participation in Goggles Summer of Code program 2008, I would like to remember you that proposals belonging to LProf should be filled in very soon. http://code.google.com/soc/2008/faqs.html#0.1_timeline The proposals themself including the LProf ones are to be found here: http://www.freedesktop.org/wiki/OpenIccForGoogleSoC2008 kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Paul W. <pa...@wa...> - 2008-01-25 19:56:54
|
On Friday 25 January 2008 2:54:34 pm Paul Waldo wrote: > Thanks for the reply, Hal. No luck... :-) > > I started from scratch, reinstalling the reference file and choosing the > correct picker. I then exited lprof and looked at the RC file. Here is > what was there: > > > TARGET0=/home/paul/.lprof/target_refsR060101.txt > TARGET_DIR=/home/paul/.lprof/target_refs > TEMPLATE0=/home/paul/.lprof/templates/IT8_22.ITX > TEMPLATE_DIR=/home/paul/.lprof/templates > > I then re-opened the target image and selected the corners. Still got only > 19 columns :-( > > I'm attaching the entire RC file, and I'll try out the CVS version. > > Paul Sorry, forgot the attachment :-) Paul |
|
From: Paul W. <pa...@wa...> - 2008-01-25 19:54:48
|
On Friday 25 January 2008 2:31:16 pm Hal V. Engel wrote: > On Friday 25 January 2008 06:56:00 Paul Waldo wrote: > > Hi all, > > > > I'm using lprof-1.11.4.1. I select my IT8 target, which is a 22-column > > target from Wolf Faust. I select "IT8.7/2 - 22 column picker" for my > > Pick template. I select OK, then Done. When I got to select the corners > > on my image file, I only get 19 columns of green squares, not 22. > > > > Here is another interesting data point. If I select the 22-col pick > > template first, then point to the Target directory, the OK button is > > greyed out. I have to select another Template, before the OK button is > > clickable. > > > > I'm getting very poor results at 19 columns: > > > > I have chosen CIE XYZ as PCS > > Unknown white point (X:1e-314, Y:7e-312, Z:7e-312) > > Primaries (x-y): [Red: 0.625415, 0.277302] [Green: 0, 1] [Blue: > > 0.0833993, 0] Estimated gamma: [Red: 1.19788] [Green: 1.22472] [Blue: > > 1.24135] Loading sheets... > > Reference sheet: /home/paul/.lprof/target_refs/R060101.txt > > Measurement sheet: /home/paul/.lprof/temp/meaurement.cgt > > Gamut hull: 195 inside, 0 outside, 57 on boundaries > > Fitting error (delta E CIELAB): mean=1.97997, RMS=3.01769, 95%%=6.1929, > > median=1.09214, MAD=0.666138 > > Fitting error (delta E CIE94): mean=1.10034, RMS=1.5087, 95%%=3.06707, > > median=0.777355, MAD=0.432199 > > Performing 2-fold cross validation ... > > 2-fold CV: estimated RMS dE=4.04654, dE94=2.04384 > > 2-fold adj. CV: estimated RMS dE=3.70133, dE94=1.86485 > > > > Here are my profile parameters: > > > > Resolution (CLUT points): 33 > > Profile verbosity: Store anything > > Regression: > > Smoothness: 0.500 > > Deviation: 1.00e-05 > > Linear Bradford > > > > I am hoping that getting the additional 3 columns will improve the dE, > > although I somehow doubt it... > > > > Any help would be appreciated! > > > > Paul > > There is a bug in 1.11.4.x that in some cases results in the reference file > being incorrectly installed. Predicting when this might happen is > difficult and it happens more often on Windows machines than on unix like > machines. But it does occasionally happen on *nix machines. You are the > third person to report this problem on a Linux box. This is fixed in CVS > and this work was done as part of the Google Summer of Code project. For > 1.11.4.x there is a simple work around that only takes a few minutes. > > To fix this you need to modify the lprof configuration file. For *nix > users this file is: > > /home/<user id>/.lprof/config/lprofrc > > It is a text file and to fix the problem you will need to edit the file and > make a small change. The file is divided into sections. The section you > are interested in is the [Files] section. In that section you will find > some lines that looks something like this: > > TARGET0=/home/heng/.lprof/target_refs/R041110.txt > TEMPLATE0=/home/heng/.lprof/templates/IT8_22.ITX > > These are the configuration items that pair up a target and the targets > template. The likely issue for you is that you either have extra /'s or a > missing a / at the path/file name location in one of these entries (I > forget off hand if it is an extra / or a missing /). Just correct that so > that the path/file names for both are correct and it should start working. > > If you do not find the / issue please post back here and I will have a > closer look. But I am 95% sure that this is what you are seeing. And if > it works please let us know. > > Hal Thanks for the reply, Hal. No luck... :-) I started from scratch, reinstalling the reference file and choosing the correct picker. I then exited lprof and looked at the RC file. Here is what was there: TARGET0=/home/paul/.lprof/target_refsR060101.txt TARGET_DIR=/home/paul/.lprof/target_refs TEMPLATE0=/home/paul/.lprof/templates/IT8_22.ITX TEMPLATE_DIR=/home/paul/.lprof/templates I then re-opened the target image and selected the corners. Still got only 19 columns :-( I'm attaching the entire RC file, and I'll try out the CVS version. Paul |
|
From: Hal V. E. <hv...@as...> - 2008-01-25 19:31:19
|
On Friday 25 January 2008 06:56:00 Paul Waldo wrote: > Hi all, > > I'm using lprof-1.11.4.1. I select my IT8 target, which is a 22-column > target from Wolf Faust. I select "IT8.7/2 - 22 column picker" for my Pick > template. I select OK, then Done. When I got to select the corners on my > image file, I only get 19 columns of green squares, not 22. > > Here is another interesting data point. If I select the 22-col pick > template first, then point to the Target directory, the OK button is greyed > out. I have to select another Template, before the OK button is clickable. > > I'm getting very poor results at 19 columns: > > I have chosen CIE XYZ as PCS > Unknown white point (X:1e-314, Y:7e-312, Z:7e-312) > Primaries (x-y): [Red: 0.625415, 0.277302] [Green: 0, 1] [Blue: 0.0833993, > 0] Estimated gamma: [Red: 1.19788] [Green: 1.22472] [Blue: 1.24135] > Loading sheets... > Reference sheet: /home/paul/.lprof/target_refs/R060101.txt > Measurement sheet: /home/paul/.lprof/temp/meaurement.cgt > Gamut hull: 195 inside, 0 outside, 57 on boundaries > Fitting error (delta E CIELAB): mean=1.97997, RMS=3.01769, 95%%=6.1929, > median=1.09214, MAD=0.666138 > Fitting error (delta E CIE94): mean=1.10034, RMS=1.5087, 95%%=3.06707, > median=0.777355, MAD=0.432199 > Performing 2-fold cross validation ... > 2-fold CV: estimated RMS dE=4.04654, dE94=2.04384 > 2-fold adj. CV: estimated RMS dE=3.70133, dE94=1.86485 > > Here are my profile parameters: > > Resolution (CLUT points): 33 > Profile verbosity: Store anything > Regression: > Smoothness: 0.500 > Deviation: 1.00e-05 > Linear Bradford > > I am hoping that getting the additional 3 columns will improve the dE, > although I somehow doubt it... > > Any help would be appreciated! > > Paul There is a bug in 1.11.4.x that in some cases results in the reference file being incorrectly installed. Predicting when this might happen is difficult and it happens more often on Windows machines than on unix like machines. But it does occasionally happen on *nix machines. You are the third person to report this problem on a Linux box. This is fixed in CVS and this work was done as part of the Google Summer of Code project. For 1.11.4.x there is a simple work around that only takes a few minutes. To fix this you need to modify the lprof configuration file. For *nix users this file is: /home/<user id>/.lprof/config/lprofrc It is a text file and to fix the problem you will need to edit the file and make a small change. The file is divided into sections. The section you are interested in is the [Files] section. In that section you will find some lines that looks something like this: TARGET0=/home/heng/.lprof/target_refs/R041110.txt TEMPLATE0=/home/heng/.lprof/templates/IT8_22.ITX These are the configuration items that pair up a target and the targets template. The likely issue for you is that you either have extra /'s or a missing a / at the path/file name location in one of these entries (I forget off hand if it is an extra / or a missing /). Just correct that so that the path/file names for both are correct and it should start working. If you do not find the / issue please post back here and I will have a closer look. But I am 95% sure that this is what you are seeing. And if it works please let us know. Hal |
|
From: Hal V. E. <hv...@as...> - 2008-01-25 19:09:14
|
On Friday 25 January 2008 00:31:26 Kai-Uwe Behrmann wrote: > Hello, > > I am missing scons.py from a recent CVS checkout. > > README: > $ python scons.py PREFIX=/where/to/install > > Is this the way to build LProf? What is needed for a bootstrap? > > kind regards > Kai-Uwe Behrmann scons.py is from scons.local which is included with the tarballs but is not part of CVS. The README has information on building from CVS. You need to either drop a copy of scons.local into the root of the source tree or have a copy of scons installed and use it. You will need scons(.local) verion 0.97 or later to build CVS head. Also currently most of the work going on is in the Qt4-port branch of CVS and we will likely be merging it into the main line soon. For the most part it is working about as well as CVS head (IE the Qt3 version) and in some areas it is working better. So you might want to consider testing this. Both builds (IE. Qt3 and Qt4) can coexist if installed into different prefixes. This branch also has an experimental cmake build. Hal |
1 message has been excluded from this view by a project administrator.
