From hughsient at gmail.com Mon Feb 1 11:05:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 1 Feb 2010 11:05:13 +0000 Subject: GNOME Color Manager 2.29.3 Message-ID: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> gnome-color-manager is a session program that makes it easy to manage, install and generate color profiles in the GNOME desktop. Version 2.29.3 ~~~~~~~~~~~~~~ Released: 2010-02-01 * Translations - Added Italian translation (Francesco Groccia) - Updated Danish translation (Joe Hansen) - Updated French translation (Claude Paroz) - Updated German translation (Mario Bl?ttermann) - Updated Norwegian bokm?l translation (Kjartan Maraas) - Updated Portuguese translation (Ant?nio Lima) - Updated Russian translation (Alexandre Prokoudine) - Updated Slovenian translation (Andrej ?nidar?i?) - Updated Swedish translation (Daniel Nylander) * New Features: - Enable the rendering intent and default colorspace UI elements (Richard Hughes) - Show whether the ICC profile has a VCGT tag in the UI (Richard Hughes) - Filter out non RGB and CMYK color space profiles from the combo-boxes using a heuristic (Richard Hughes) - Add a new DBus method GetProfileForWindow which can return a profile for a supplied XID (Richard Hughes) - Add some new text and tooltips to the prefs dialog (Richard Hughes) - Add per-user OSX ICC profiles at startup (Richard Hughes) - Add OSX and Windows ICC profiles if they exist from mounted volumes. Fixes #607390 (Richard Hughes) - Add a device profile entry of 'Other profile...' to be able to easily import a profile. Fixes #607389 (Richard Hughes) - Add a precision GConf variable to control the time a calibration takes. Fixes #605558 (Richard Hughes) - Screenscrape the Argyll output to better support other hardware devices. Fixes #605558 (Richard Hughes) - Do not show the 'Fine tuning' expander by default, and have configuration in GConf (Richard Hughes) * Bugfix: - Zero out GErrors after freeing. Fixes crash (Christian Hergert) - Add gnome-desktop path as fallback for pci.ids (Frederic Crozat) - Do not generate an error if a display profile does not have CLUT data (Richard Hughes) - Add gcm-fix-profile to load and then re-save existing profiles using lcms (Richard Hughes) - Fix compile when using an ld that defaults to --as-needed (Richard Hughes) - Do not allow the colorspace combobox to be zero sized. Fixes #606484 (Richard Hughes) - Make gcm-prefs a normal dialog rather than a modal dialog (Richard Hughes) - Only scan ICC locations with hfs partition types for OSX and msdos/NTFS types for Windows (Richard Hughes) - Make gcm-prefs startup a few hundred ms quicker by not loading the list of screens (Richard Hughes) - Cache gnome_rr_screen_new and take 0.7 seconds off the start time (Richard Hughes) - Don't resize the window on startup. Fixes #607391 (Richard Hughes) - Update the Free Software Foundation address (Richard Hughes) Richard. From pmjdebruijn at pcode.nl Mon Feb 1 18:29:31 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 1 Feb 2010 19:29:31 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> Message-ID: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > gnome-color-manager is a session program that makes it easy to manage, install > and generate color profiles in the GNOME desktop. > > Version 2.29.3 > ~~~~~~~~~~~~~~ > Released: 2010-02-01 As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's available on my gcm-release PPA: https://launchpad.net/~pmjdebruijn/+archive/gcm-release ArgyllCMS 1.1.0 is also available on my argyll-release PPA, to complement GNOME Color Manager: https://launchpad.net/~pmjdebruijn/+archive/argyll-release Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 5 12:55:32 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 13:55:32 +0100 Subject: Information re. display gamma Message-ID: <1265374532.31703.61.camel@athlon> Hello, while translating the gcm, I spotted the following: -- Gamma is adjusted to affect the color of the attached monitor. Traditionally Linux has used a gamma value of 1.0, but this makes monitors look washed out compared Windows XP or OS X. Apple traditionally used a value of 1.8 for a long time, but now use the same value as Microsoft. Microsoft has always used a value of 2.2. -- Where does the information that Linux has used a gamma of 1.0 come from? I would assume it is a wrong interpretation of technical data. Both Mac/Win tools prefer to tell the user the final viewing gamma (which is a combination of gamma adjustment in LUT of graphics card and of the monitor's native gamma). These tools expect that the monitor native gamma is 2.2 (which is close to sRGB). In the past, Mac monitors had native gama 1.8. Linux tools - like xgamma and gcm - instead tell the number, which is applied to LUT only. Note that the final viewing gamma is equal to monitor's native gamma divided by LUT gamma. In other words, an image (untagged by ICC profile) displayed in Windows and Linux will appear the same, provided that the same video card and monitor is used and no colour management/calibration is applied. This is also the reason, why display ICC profiles created in Windows can be used in Linux. If the information quoted above remains, users will be confused and try to set gamma 2.2 in gcm. I would propose to change the text so that it is clear that the user can correct the monitor's native gamma and that it is not the final viewing gamma. Or am I wrong? Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Fri Feb 5 13:32:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 5 Feb 2010 13:32:12 +0000 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> On 5 February 2010 12:55, Milan Kn??ek wrote: > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. That sounds about right to me. Feel free to change it so it's clearer. Thanks. Richard. From knizek.confy at volny.cz Fri Feb 5 20:09:20 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:09:20 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> Message-ID: <1265400560.29899.18.camel@athlon> Pascal de Bruijn p??e v Po 01. 02. 2010 v 19:29 +0100: > On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > > gnome-color-manager is a session program that makes it easy to manage, install > > and generate color profiles in the GNOME desktop. > > > > Version 2.29.3 > > ~~~~~~~~~~~~~~ > > Released: 2010-02-01 > > As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's > available on my gcm-release PPA: > > https://launchpad.net/~pmjdebruijn/+archive/gcm-release Is it an expected change in this release that the "fine tuning" option on the main screen of gcm-prefs disappeared? regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From knizek.confy at volny.cz Fri Feb 5 20:39:06 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:39:06 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> Message-ID: <1265402346.29899.48.camel@athlon> Richard Hughes p??e v P? 05. 02. 2010 v 13:32 +0000: > On 5 February 2010 12:55, Milan Kn??ek wrote: > > I would propose to change the text so that it is clear that the user can > > correct the monitor's native gamma and that it is not the final viewing > > gamma. > > That sounds about right to me. Feel free to change it so it's clearer. Thanks. > > Richard. > I will look at the text and propose a new wording. Additionally, it may also be helpful to update the "fine tuning" gamma slider. The slider has "hooks" for 1.8 and 2.2 -this would make sense if the user had a monitor with native gamma value of 1. Then, setting the slider to 2.2 would result in viewing gamma value of 2.2. This probably would not be the case for anyone. Hence, removing the "hooks" would help avoiding confusion. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Sat Feb 6 02:10:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 06 Feb 2010 13:10:48 +1100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <4B6CCFA8.3000107@argyllcms.com> Milan Kn??ek wrote: > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple Sounds bogus. Unix machines have "traditionally" used RGB encoded for display on a typical native CRT gamma. Linux is no different - "traditionally" raw RGB numbers have been sent to the monitor, and you get native CRT gamma or an emulation of it if it's an LCD monitor, so the encoding is notionally set for a gamma of 2.2. But there are exceptions - SGI's had a different scheme, and people creating synthetic images (CGI) have often left their images linear light, and expect the display process to counteract the displays natural gamma, even though this introduces quantization problems if they use 8 bits. > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. Note a couple of things: Latest OS X (10.6 "Snow Leopard") has a default of 2.2, but it seems that "1.8" of the Mac mac prior to this is actually a misnomer, the encoding is actually closer to 1/1.72, which is corrected by a framebuffer ramp of 1/1.45 for display on a CRT of 2.5, giving an overall system gamma of 1.0. Real CRT's have a gamma of nearer 2.4 - 2.5 (although such numbers are very sensitive to the setting of the black level). "Traditionally" from the TV world, material is broadcast with a gamma of 0.45 (ie. 1/2.22) with the expectation that it will be displayed on a monitor that has a gamma of 2.5, the discrepancy applying a viewing conditions transform that accounts for the different appearance between the bright TV studio lighting and the usually dim viewing conditions use with a CRT monitor. For all the details please refer to Charles Poynton's book "Digital Video and HDTV". > Linux tools - like xgamma and gcm - instead tell the number, which is > applied to LUT only. Note that the final viewing gamma is equal to > monitor's native gamma divided by LUT gamma. Right, and the final overall gamma should be 1.0, or (allowing for the viewing condition transform, about 1.1 - 1.2). > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. > > Or am I wrong? Most people are unfamiliar with the concept of overall system gamma. They might easily confuse the encoding gamma, display gamma and system gamma. The distinction between encoding gamma and display gamma is probably lost on most people too (strictly speaking the encoding gamma for "2.2" is 1/2.2 which is about 0.45, and the overall gamma is the product of the encoding gamma and the display gamma.) I think that if this is a display calibration application, then really it should talk about what the display is being set to, and could indicate how this corresponds to the encoding expectation. So typically a CRT display in a dim viewing environment should be calibrated to have a gamma of about 2.4, with the expectation that it is being fed material that has been encoded with a gamma of 1/2.2. If the display is brighter and in a brighter environment, then a calibration gamma of < 2.4 might be desirable, for the same 2.2 gamma encoded material. Graeme Gill. Graeme Gill. From knizek.confy at volny.cz Sat Feb 6 10:39:03 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 06 Feb 2010 11:39:03 +0100 Subject: Information re. display gamma In-Reply-To: <4B6CCFA8.3000107@argyllcms.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> Message-ID: <1265452743.22070.45.camel@athlon> Graeme Gill p??e v So 06. 02. 2010 v 13:10 +1100: > I think that if this is a display calibration application, then > really it should talk about what the display is being set to, and > could indicate how this corresponds to the encoding expectation. > This means that the GCM would have to change a bit more: GCM must know what the native monitor gamma is. Such an information can be taken from the ICC profile, either supplied by the user, created with GCM and colorimeter or created with GCM and "eye-measured" calibration. The lack of eye-measured calibration is already reported as bug 605019 https://bugzilla.gnome.org/show_bug.cgi?id=605019 which also refers to a tutorial how ColorSync on Mac did it: http://www.computer-darkroom.com/colorsync-display/colorsync_2.htm regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 6 11:46:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 11:46:06 +0000 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <1265400560.29899.18.camel@athlon> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> <1265400560.29899.18.camel@athlon> Message-ID: <15e53e181002060346u2d547bb1g7d6c1cd01ccff1ae@mail.gmail.com> On 5 February 2010 20:09, Milan Kn??ek wrote: > Is it an expected change in this release that the "fine tuning" option > on the main screen of gcm-prefs disappeared? Yes. There's a GConf key to re-enable it if you need the UI, but it's hidden by default until we make the UI nicer to use. It's on my TODO, but didn't quite make the release. New contributors welcome! :) Richard. From j at jonathanleighton.com Sat Feb 6 12:29:46 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Sat, 06 Feb 2010 12:29:46 +0000 Subject: ColorVision Spyder Message-ID: <1265459386.23788.9.camel@tybalt> Hi there, I have a ColorVision Spyder colorimeter. I have just been trying out gnome-color-manager (very impressive!) but the calibration buttons are disabled, even when I plug in my colorimeter. Do I need to take additional steps to use the colorimeter through GCM, or is the support just not there yet or something? Many thanks, Jon PS. Please CC me in replies - I'm not on the list. From hughsient at gmail.com Sat Feb 6 15:55:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:55:31 +0000 Subject: Information re. display gamma In-Reply-To: <1265452743.22070.45.camel@athlon> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> Message-ID: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> On 6 February 2010 10:39, Milan Kn??ek wrote: > This means that the GCM would have to change a bit more: GCM must know > what the native monitor gamma is. We can do this, but in my experience the EDID data from the monitor is wrong more often than it's right... Richard. From hughsient at gmail.com Sat Feb 6 15:57:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:57:50 +0000 Subject: ColorVision Spyder In-Reply-To: <1265459386.23788.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> Message-ID: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> On 6 February 2010 12:29, Jon Leighton wrote: > I have a ColorVision Spyder colorimeter. I have just been trying out > gnome-color-manager (very impressive!) but the calibration buttons are > disabled, even when I plug in my colorimeter. What version ArgyllCMS do you have installed? If it's less than 1.1.0 you'll need to add --disable-hardware-detection to ./configure -- it also only works for display devices for now (patches welcome!). > Do I need to take additional steps to use the colorimeter through GCM, > or is the support just not there yet or something? Well, if it's supported in Argyll then it's supported by GCM. Richard. From knizek.confy at volny.cz Sun Feb 7 11:23:57 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sun, 07 Feb 2010 12:23:57 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> Message-ID: <1265541838.20793.5.camel@athlon> Richard Hughes p??e v So 06. 02. 2010 v 15:55 +0000: > On 6 February 2010 10:39, Milan Kn??ek wrote: > > This means that the GCM would have to change a bit more: GCM must know > > what the native monitor gamma is. > > We can do this, but in my experience the EDID data from the monitor is > wrong more often than it's right... > > Richard. > I understand that getting the EDID data is unreliable at the moment. In addition, some wide-gamut displays support pre-set calibration modes emulating various colour spaces. The modes can be changed via hardware buttons on the LCD. For the time being, I would leave up to the user to select the proper display profile (depending on the attached monitor and its calibration mode) rather then only relying on EDID. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Mon Feb 8 01:27:50 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 12:27:50 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <4B6F6896.9050406@argyllcms.com> Richard Hughes wrote: > Well, if it's supported in Argyll then it's supported by GCM. But note that the Spyder 2 needs to have firmware. In Argyll the spyd2en utility needs to be run to extract the firmware from the distribution disk. See Graeme Gill. From hughsient at gmail.com Mon Feb 8 07:58:05 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 07:58:05 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6F6896.9050406@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> Message-ID: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> On 8 February 2010 01:27, Graeme Gill wrote: > But note that the Spyder 2 needs to have firmware. In Argyll > the spyd2en utility needs to be run to extract the firmware from > the distribution disk. > See What's the output from argyllcms if there is no firmware? Or does the device just not appear? Thanks, Richard. From graeme2 at argyllcms.com Mon Feb 8 08:22:18 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 19:22:18 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> Message-ID: <4B6FC9BA.5030905@argyllcms.com> Richard Hughes wrote: > What's the output from argyllcms if there is no firmware? Or does the > device just not appear? There will be an error message containing: "No PLD firmware pattern is available" Graeme Gill. From hughsient at gmail.com Mon Feb 8 08:40:17 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 08:40:17 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6FC9BA.5030905@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> <4B6FC9BA.5030905@argyllcms.com> Message-ID: <15e53e181002080040o56051e39k39dc13f01163194d@mail.gmail.com> On 8 February 2010 08:22, Graeme Gill wrote: > There will be an error message containing: > > "No PLD firmware pattern is available" That's great, thanks. Richard. From hughsient at gmail.com Mon Feb 8 09:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:16:56 +0000 Subject: Small thumbnails of targets Message-ID: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> The attached file shows some new UI in gnome-color-manager -- it now supports more types of targets than just IT8. To be able to show the user a preview of what each target looks like, we need some 200x150 pixel thumbnails of the different target types. These need to be GPLv2+ licenced, and have the specific vendor data removed. See the screenshot for an example. This would be a great way to help out gnome-color-manager if you are not comfortable with coding. The list of target types I need as thumbnails are: CMP_Digital_Target-3 CMP_DT_003 ColorChecker ColorCheckerDC ColorCheckerSG Hutchcolor i1_RGB_Scan_1.4 LaserSoftDCPro QPcard_201 I've already done IT8. Please cc the list if you send me a type, and then we won't get duplicated effort. Note: you can't just copy and paste from the manufacturers website, as they may have copyright on the image. Basically, the rule is if you're not sure about the copyright of the image, then it's not suitable. The best way would be to scan the target yourself and send it to me. If you send files, please state where you got them from, and that they are redistributable as part of a project that is GPLv2+. Thanks, Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 44590 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 09:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <15e53e181002080147l7e6f4246pf92afe936ffd28b5@mail.gmail.com> On 8 February 2010 09:16, Richard Hughes wrote: > The best way would be to scan the > target yourself and send it to me. If you send files, please state > where you got them from, and that they are redistributable as part of > a project that is GPLv2+. I forgot to mention. They also have to be PNG format. Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 10:00:38 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 10:00:38 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <1265623238.9194.9.camel@tybalt> On Sat, 2010-02-06 at 15:57 +0000, Richard Hughes wrote: > On 6 February 2010 12:29, Jon Leighton wrote: > > I have a ColorVision Spyder colorimeter. I have just been trying out > > gnome-color-manager (very impressive!) but the calibration buttons are > > disabled, even when I plug in my colorimeter. > > What version ArgyllCMS do you have installed? If it's less than 1.1.0 > you'll need to add --disable-hardware-detection to ./configure -- it > also only works for display devices for now (patches welcome!). Aha, that was it. I've installed latest argyll, and now the button is enabled. However, when I click it and select LCD, I then get the "Display setup" dialog. If I click OK nothing happens - the dialog closes but nothing else comes up. I tried running with -vvv and the following came up: TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 - failed to calibrate: failed to match display as RandR is faulty TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,170 - min=0.000000,max=1.000000 TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,176 - falling back to dummy gamma TI:09:52:12 FI:gcm-device-xrandr.c FN:gcm_device_xrandr_set_gamma_fallback,351 - using PER-SCREEN gamma tables as driver is not XRANDR 1.3 compliant TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_output_profile,477 - found default, removing atom TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_root_window_profile,239 - removing root window ICC profile atom Any ideas? Thanks From hughsient at gmail.com Mon Feb 8 10:39:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 10:39:12 +0000 Subject: ColorVision Spyder In-Reply-To: <1265623238.9194.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> Message-ID: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> On 8 February 2010 10:00, Jon Leighton wrote: > Aha, that was it. I've installed latest argyll, and now the button is > enabled. That's good. > TI:09:52:12 ? ? FI:gcm-prefs.c ?FN:gcm_prefs_calibrate_display,381 > ?- failed to calibrate: failed to match display as RandR is faulty What video driver are you using? Can you attach the output of xrandr please? Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 11:12:37 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 11:12:37 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> Message-ID: <1265627557.9194.11.camel@tybalt> Hi, On Mon, 2010-02-08 at 10:39 +0000, Richard Hughes wrote: > > TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 > > - failed to calibrate: failed to match display as RandR is faulty > > What video driver are you using? I'm using the nVidia driver, version 185.18.36. > Can you attach the output of xrandr please? Thanks. Yep. Cheers, Jon -------------- next part -------------- Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 50.0 51.0 52.0* 1600x1024 53.0 1440x900 54.0 1360x768 55.0 56.0 1280x1024 57.0 1280x960 58.0 1152x864 59.0 1024x768 60.0 960x600 61.0 960x540 62.0 840x525 63.0 64.0 800x600 65.0 66.0 800x512 67.0 720x450 68.0 700x525 69.0 680x384 70.0 71.0 640x512 72.0 640x480 73.0 74.0 576x432 75.0 512x384 76.0 400x300 77.0 320x240 78.0 From hughsient at gmail.com Mon Feb 8 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 11:20:27 +0000 Subject: ColorVision Spyder In-Reply-To: <1265627557.9194.11.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> Message-ID: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> On 8 February 2010 11:12, Jon Leighton wrote: > I'm using the nVidia driver, version 185.18.36. Hmm, I fear this maybe another case of broken binary drivers. Is there any chance you could try with the nouveau driver please? Thanks. Richard. From graeme2 at argyllcms.com Mon Feb 8 11:58:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 22:58:48 +1100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4B6FFC78.9010503@argyllcms.com> I've sent Richard an image of the ColorCheckerDC. Graeme Gill From j at jonathanleighton.com Mon Feb 8 14:18:05 2010 From: j at jonathanleighton.com (Jonathan Leighton) Date: Mon, 8 Feb 2010 14:18:05 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> Message-ID: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Hi, On 8 February 2010 11:20, Richard Hughes wrote: > On 8 February 2010 11:12, Jon Leighton wrote: >> I'm using the nVidia driver, version 185.18.36. > > Hmm, I fear this maybe another case of broken binary drivers. Is there > any chance you could try with the nouveau driver please? Thanks. Yes, it worked under nouveau. (Incidentally, the calibration seemed pretty quick, and I'm not sure the results were great in my case. Are there any plans to have an option of "quick profile" vs "good profile"?) Cheers, Jon From pmjdebruijn at pcode.nl Mon Feb 8 14:27:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:27:24 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > ColorChecker I have just done these two... > I've already done IT8. I redid the IT8, we should called this IT8.7/2, since that's it's proper name... There are other IT8 charts (I think those are mostly for printing), using the full name should prevent any confusion. With all the images, I scanned my own targets, and then followed this procedure: 1. Despeckle, Adaptive enabled, Recursive dislabed, Radius 3, Black level 6, White level 255 2. Then possibly rotate the chart a bit to align it, and then crop it. 3. Then use GIMP Resynthesize to remove vendor text "Smart remove selection", with 10px. 4. Possibly have GIMP do Auto White Balance (doesn't work always) Without distorting aspect, my images could all be rounded to 200px by 140px. I think we should not distort aspect in any visible way. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: IT872.png Type: image/png Size: 31624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ColorChecker24.png Type: image/png Size: 32929 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CMP-DigitalTarget3.png Type: image/png Size: 44514 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 14:52:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 14:52:23 +0000 Subject: ColorVision Spyder In-Reply-To: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Message-ID: <15e53e181002080652j1616f139h65a133fb55b1e895@mail.gmail.com> On 8 February 2010 14:18, Jonathan Leighton wrote: > (Incidentally, the calibration seemed pretty quick, and I'm not sure > the results were great in my case. Are there any plans to have an > option of "quick profile" vs "good profile"?) Grab gcm from git master, and then set /apps/gnome-color-manager/calibration_length in GConf Editor. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 14:56:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:56:17 +0100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4B6FFC78.9010503@argyllcms.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> Message-ID: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: > I've sent Richard an image of the ColorCheckerDC. I noticed it got commited... But it's aspect ratio is slightly off... You obviously did that to comply with Richard's 200x150 specification... But 200x140 as a baseline would be better for most charts... You're ColorCheckerDC image looks much better when rescaled to 200x140. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Mon Feb 8 15:04:06 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:04:06 +0100 Subject: Camera profile generation options Message-ID: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Hi, Are camera profiles generated with Argyll's default options? -q m -a l ? This might be fine for IT8 or other targets with lots of patches... But it's probably not such a good idea for a 24 patch ColorChecker, -q l -a S seems more appropriate... Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:04:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:04:27 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> Message-ID: <15e53e181002080704o79716ec2kd131bf0fbf8feafb@mail.gmail.com> On 8 February 2010 14:27, Pascal de Bruijn wrote: > I have just done these two... Brilliant, thanks. >> I've already done IT8. > > I redid the IT8, we should called this IT8.7/2, since that's it's > proper name... There are other IT8 charts (I think those are mostly > for printing), using the full name should prevent any confusion. Done, thanks. > Without distorting aspect, my images could all be rounded to 200px by > 140px. I think we should not distort aspect in any visible way. Okay, I've changed the others to be 200x140 also. Thanks. Richard. From hughsient at gmail.com Mon Feb 8 15:12:35 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:12:35 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Message-ID: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> On 8 February 2010 15:04, Pascal de Bruijn wrote: > Are camera profiles generated with Argyll's default options? -q m -a l ? > > This might be fine for IT8 or other targets with lots of patches... > > But it's probably not such a good idea for a 24 patch ColorChecker, -q > l -a S seems more appropriate... Yes, this is a good idea, and a perfect patch for you to submit :-) The kind of profile is listed in src/gcm-calibrate-argyll.h, which is saved to priv->reference_kind, which is private data for the GcmCalibrateArgyll object. You probably need to add a simple "if (priv->reference_kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just getting the type of profile (using gcm_calibrate_argyll_precision_to_quality_arg) in the function gcm_calibrate_argyll_device_generate_profile() which lives in src/gcm-calibrate-argyll.c Make a few changes, and just do "git diff > test.patch" Attach the test.patch to an email (on the mailing list if you're feeling brave, or just to me if you're feeling timid) and I'll give you some feedback. Grab me on IRC if you are feeling really stuck / lazy / busy. Richard. From hughsient at gmail.com Mon Feb 8 15:14:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:14:22 +0000 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> Message-ID: <15e53e181002080714y11dad8afxb11eb95cbd801a85@mail.gmail.com> On 8 February 2010 14:56, Pascal de Bruijn wrote: > On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: >> I've sent Richard an image of the ColorCheckerDC. > > I noticed it got commited... But it's aspect ratio is slightly off... > You obviously did that to comply with Richard's 200x150 > specification... No, I did that, Graeme sent me the original image. I've sent you the profile for the same love. > But 200x140 as a baseline would be better for most charts... You're > ColorCheckerDC image looks much better when rescaled to 200x140. Agreed. Richard. From hughsient at gmail.com Mon Feb 8 15:16:29 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:16:29 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? Message-ID: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> I've got sources that look like this: if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) return "CMP_Digital_Target-3.cht"; if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) return "CMP_DT_003.cht"; Are they actually the same profile type? What's the difference in the chart versions? Thanks, Richard. From pmjdebruijn at pcode.nl Mon Feb 8 15:46:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:46:17 +0100 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> Message-ID: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> On Mon, Feb 8, 2010 at 4:16 PM, Richard Hughes wrote: > I've got sources that look like this: > > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) > ? ? ? ? ? ? ? ?return "CMP_Digital_Target-3.cht"; > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) > ? ? ? ? ? ? ? ?return "CMP_DT_003.cht"; > > Are they actually the same profile type? What's the difference in the > chart versions? They are different charts... I have this one (3): http://www.cmp-color.fr/eng%20digital%20target.html Are there is the 003 one: http://www.argyllcms.com/doc/CMP_DT_003.jpg Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:48:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:48:53 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> Message-ID: <15e53e181002080748i4f953979j9999944c092cc31@mail.gmail.com> On 8 February 2010 15:46, Pascal de Bruijn wrote: > They are different charts... Cool, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 21:32:32 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:32:32 +0100 Subject: Camera profile generation options In-Reply-To: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> Message-ID: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> On Mon, Feb 8, 2010 at 4:12 PM, Richard Hughes wrote: > On 8 February 2010 15:04, Pascal de Bruijn wrote: >> Are camera profiles generated with Argyll's default options? -q m -a l ? >> >> This might be fine for IT8 or other targets with lots of patches... >> >> But it's probably not such a good idea for a 24 patch ColorChecker, -q >> l -a S seems more appropriate... > > Yes, this is a good idea, and a perfect patch for you to submit :-) > > The kind of profile is listed in src/gcm-calibrate-argyll.h, which is > saved to priv->reference_kind, which is private data for the > GcmCalibrateArgyll object. You probably need to add a simple "if > (priv->reference_kind == > GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just > getting the type of profile (using > gcm_calibrate_argyll_precision_to_quality_arg) in the function > gcm_calibrate_argyll_device_generate_profile() which lives in > src/gcm-calibrate-argyll.c > > Make a few changes, and just do "git diff > test.patch" I think this patch should do it, it seems to work, though I didn't extensively test it. I also included the QPcard as well, it's a similar target... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-calibrate-argyll-low-patch-count-target-low-quality-single-shaper.patch Type: text/x-patch Size: 2556 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 8 21:58:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:58:24 +0100 Subject: Camera Profiling GUI Dialog Order Message-ID: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Hi, Currently to profile a camera, the GUI first asks for both files, and then asks for the chart type... This seems odd to me... It seems more natural to me, to first ask about the chart type, and then ask about the files... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-ask-reference-kind-first.patch Type: text/x-patch Size: 1241 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:23:07 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:23:07 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> Message-ID: <15e53e181002081423g6279830eq5c07be8d8aca9e9e@mail.gmail.com> On 8 February 2010 21:32, Pascal de Bruijn wrote: > I think this patch should do it, it seems to work, though I didn't > extensively test it. Great stuff. I've modified your patch a little (just passing the calibrate_argyll object and renaming a function) and committed it. I've attached the changed version. Well done! Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Do-low-quality-calibration-when-using-targets-with-a.patch Type: text/x-patch Size: 3393 bytes Desc: not available URL: From amluto at gmail.com Mon Feb 8 22:23:02 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Mon, 8 Feb 2010 17:23:02 -0500 Subject: Reduce autoconf requirement Message-ID: Hi all- For kicks, I just grabbed gnome-color-manager out of git, built it, and ran it on KDE4 on Fedora 12. (why not?) It seems to work (I haven't tested its Argyll integration yet.) To make it build, though, I had to decrease the autoconf required version, like this: diff --git a/configure.ac b/configure.ac index bf4e31f..d4f422b 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_PREREQ(2.65) +AC_PREREQ(2.63) AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) AC_CONFIG_SRCDIR(src) Is there any reason we require autogen 2.65? 2.63 from F12 seems to work just fine. shared-color-targets needs the same patch. As an aside, what's the profile graph on the right? Is it the calibration (VCGT), the gray axis of the profile, or something else? (I assume it's not the gray axis -- it doesn't really look like xicclu's output.) Thanks, Andy From hughsient at gmail.com Mon Feb 8 22:24:45 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:24:45 +0000 Subject: Camera Profiling GUI Dialog Order In-Reply-To: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> References: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Message-ID: <15e53e181002081424hc401819k29fc0a3c0ad96d8@mail.gmail.com> On 8 February 2010 21:58, Pascal de Bruijn wrote: > Currently to profile a camera, the GUI first asks for both files, and > then asks for the chart type... This seems odd to me... Agreed. > It seems more natural to me, to first ask about the chart type, and > then ask about the files... Committed, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 22:26:34 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 23:26:34 +0100 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> On Mon, Feb 8, 2010 at 11:23 PM, Andrew Lutomirski wrote: > Hi all- > > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) > > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) > > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. I apply the attached patch to git to make it work on Ubuntu Karmic. > shared-color-targets needs the same patch. > > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) If I'm not mistaken those are the TRC's... VCGT is only relevant for displays... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-git-demodernize-configure-ac.patch Type: text/x-patch Size: 2099 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:27:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:27:40 +0000 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <15e53e181002081427m68ba1894w9810233b37c1cf53@mail.gmail.com> On 8 February 2010 22:23, Andrew Lutomirski wrote: > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) Sure, it should work. > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) The 2.63 BR was from autoupdate'ing the scripts. > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. If it works, great! > shared-color-targets needs the same patch. Will do. > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) I think we need graph labels in this case. It's actually the TRC. Richard. From hughsient at gmail.com Mon Feb 8 22:28:44 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:28:44 +0000 Subject: Reduce autoconf requirement In-Reply-To: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> References: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> Message-ID: <15e53e181002081428p43926011mf3d6510d720a492c@mail.gmail.com> On 8 February 2010 22:26, Pascal de Bruijn wrote: > I apply the attached patch to git to make it work on Ubuntu Karmic. Hmm, that seems a bit drastic. Doesn't changing the version to 2.63 work okay in the Karmic case? Richard. From pmjdebruijn at pcode.nl Tue Feb 9 11:29:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:29:44 +0100 Subject: QPcard 201 thumbnail Message-ID: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> Hi, Here's a QPcard_201 thumbnail, postprocessed from a scanned image, submitted on the ArgyllCMS mailing list by Wallden Magnus. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201.png Type: image/png Size: 14124 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Tue Feb 9 11:35:55 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:35:55 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> Message-ID: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> On Tue, Feb 9, 2010 at 12:34 PM, Pascal de Bruijn wrote: > On Tue, Feb 9, 2010 at 12:29 PM, Pascal de Bruijn wrote: >> Hi, >> >> Here's a QPcard_201 thumbnail, postprocessed from a scanned image, >> submitted on the ArgyllCMS mailing list by Wallden Magnus. > > Whoops, forgot to remove the branding. Whoops, posted the hires version, not the thumbnail... Sorry, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201_unbranded.png Type: image/png Size: 12926 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 9 12:06:32 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 12:06:32 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> Message-ID: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> On 9 February 2010 11:35, Pascal de Bruijn wrote: > Whoops, posted the hires version, not the thumbnail... I've committed this after padding the height to 140 like the others. I really don't want the dialog resizing as the combobox elements are selected. Thanks, Richard. From pmjdebruijn at pcode.nl Tue Feb 9 13:10:48 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 14:10:48 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> Message-ID: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> On Tue, Feb 9, 2010 at 1:06 PM, Richard Hughes wrote: > On 9 February 2010 11:35, Pascal de Bruijn wrote: >> Whoops, posted the hires version, not the thumbnail... > > I've committed this after padding the height to 140 like the others. I > really don't want the dialog resizing as the combobox elements are > selected. I noticed you centered the image... Though, the white background suggests it's a big white card, with the patches centered, while it's not. We should use transparency here. I'll "fix" the image tonight, if you don't get to it first. Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 13:11:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:11:43 +0000 Subject: Using SANE? Message-ID: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> I'm thinking of using SANE (rather than udev like we do now) to get the list of scanners, and hopefully to be able to change settings on the device. It also allows us to change remote devices, not just locally plugged in USB ones. Is sane-backends-libs a problem for you distro guys? I'm not sure if it's installed by default on most distros, but it does pull in a few deps. Comments? Richard. From hughsient at gmail.com Tue Feb 9 13:17:15 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:17:15 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> Message-ID: <15e53e181002090517m76d879bdyba6cc199da454ebd@mail.gmail.com> On 9 February 2010 13:10, Pascal de Bruijn wrote: > I noticed you centered the image... Though, the white background > suggests it's a big white card, with the patches centered, while it's > not. Point taken. > We should use transparency here. I'll "fix" the image tonight, if you > don't get to it first. Okay. when you're submitting new binary files, the easiest way (for me) to do it, is this: git checkout -b the-subject-of-the-change git commit -a -m "Make the image background transparent" --author "Me Mine " ( the -a means "all changes to the working tree", the -m means "this is the commit message", and --author is so the right person gets listed in NEWS) git format-patch master git checkout master Then, all I have to do is use the command "git am" and I don't have to copy and paste your name, email, or come up with a commit message. If you get stuck, let me know. Richard. From fred at crozat.net Tue Feb 9 14:01:39 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:01:39 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> Message-ID: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> 2010/2/9 Richard Hughes : > I'm thinking of using SANE (rather than udev like we do now) to get > the list of scanners, and hopefully to be able to change settings on > the device. It also allows us to change remote devices, not just > locally plugged in USB ones. Is sane-backends-libs a problem for you > distro guys? I'm not sure if it's installed by default on most > distros, but it does pull in a few deps. How about using PackageKit to install it "on demand" ? ;) gnome-color-manager is installed "by default" in Mandriva 2010.0 but I'd like to keep sane ouf of the default install, if we can. -- Frederic Crozat From hughsient at gmail.com Tue Feb 9 14:21:02 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 14:21:02 +0000 Subject: Using SANE? In-Reply-To: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> Message-ID: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> On 9 February 2010 14:01, Frederic Crozat wrote: > 2010/2/9 Richard Hughes : >> I'm thinking of using SANE (rather than udev like we do now) to get >> the list of scanners, and hopefully to be able to change settings on >> the device. It also allows us to change remote devices, not just >> locally plugged in USB ones. Is sane-backends-libs a problem for you >> distro guys? I'm not sure if it's installed by default on most >> distros, but it does pull in a few deps. > > How about using PackageKit to install it "on demand" ? ;) Heh, this would be a library dep, not a tool dep. > gnome-color-manager is installed "by default" in Mandriva 2010.0 but > I'd like to keep sane ouf of the default install, if we can. You mean sane-backends-libs, rather than sane itself, right? Richard. From fred at crozat.net Tue Feb 9 14:34:22 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:34:22 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: <21ad25711002090634y7ef9e181oa77e6a7796a63c99@mail.gmail.com> 2010/2/9 Richard Hughes : > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Ah :( >> gnome-color-manager is installed "by default" in Mandriva 2010.0 but >> I'd like to keep sane ouf of the default install, if we can. > > You mean sane-backends-libs, rather than sane itself, right? Yes, I mean the lib package. It is 7.7MB installed, without checking its dependencies (of course, now, I've discovered openoffice-common is pulling libsane by default too :( If it could be a plugin, that would be nice :) -- Frederic Crozat From amluto at gmail.com Tue Feb 9 15:15:28 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Tue, 9 Feb 2010 10:15:28 -0500 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: On Tue, Feb 9, 2010 at 9:21 AM, Richard Hughes wrote: > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Is it safe to assume that anyone who wants to profile a scanner already has sane-backends-libs installed? If so, you could dlopen it and if that fails assume that there aren't any scanners. --Andy From pmjdebruijn at pcode.nl Tue Feb 9 19:28:41 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 20:28:41 +0100 Subject: Disconnected devices: create profiles for device disabled Message-ID: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Hi, When I have a EOS 400D disconnected, the "Create profiles for device" button is disabled, is this intentional? There is no good reason why my camera would need to be connected... For displays, it has it's advantages having the display connected for profiling though :p Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 19:49:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 19:49:22 +0000 Subject: Disconnected devices: create profiles for device disabled In-Reply-To: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> References: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Message-ID: <15e53e181002091149q7815c328n20cd83e87060efd6@mail.gmail.com> On 9 February 2010 19:28, Pascal de Bruijn wrote: > For displays, it has it's advantages having the display connected for > profiling though :p commit 9da8afc4f5dd9c7a0e252fa42483616c74696695 Author: Richard Hughes Date: Tue Feb 9 19:34:43 2010 +0000 Only require the device to be present if it is a display type :100644 100644 66af4b3... f25d118... M src/gcm-prefs.c Richard. From lars.tore at mulebakken.net Wed Feb 10 13:29:22 2010 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 10 Feb 2010 14:29:22 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > CMP_DT_003 > ColorChecker > ColorCheckerDC > ColorCheckerSG > Hutchcolor > i1_RGB_Scan_1.4 Here is a photo of the i1_RGB_Scan_1.4 scan target. I have removed the eye-one name. And it's OK with GPLv2+ Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: i1_RGB_Scan_14.png Type: image/png Size: 36266 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 10 19:38:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 10 Feb 2010 19:38:39 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> Message-ID: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> On 10 February 2010 17:17, Pascal de Bruijn wrote: > I modified the thumbnail slightly to even out the lighting, and > improve contrast. Looks great. > I attached a patch for the modified version for git master. Tanks, I've also merged the Makefile.am and gcm-prefs.c parts too. Thanks. Richard. From knizek.confy at volny.cz Wed Feb 10 20:01:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 21:01:36 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo Message-ID: <1265832096.26568.43.camel@athlon> Hello everyone on the list! GCM is getting feature-rich - display, scanner and camera profiling is already supported, but printer characterisation is still missing. Richard H would like to code the few bytes ;-) but he does not have a spectrophotometer at hand. On Richard's blog, Paul Finnigan proposed a donation from users - the ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 in the U.K., were Richard lives. The more expensive variant would require about 10 people @ USD 50 donation each. (Or less donors to buy in the U.S. and someone to actually deliver across the ocean.) At the moment, three of us offered a contribution. Anybody else here willing to help with even a smaller amount (probably via PayPal)? Or other suggestions? best regards, Milan Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Wed Feb 10 20:52:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 10 Feb 2010 21:52:27 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> On Wed, Feb 10, 2010 at 9:01 PM, Milan Kn??ek wrote: > Hello everyone on the list! > > ... > > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? I'd be willing to pitch in (PayPal) for about 25EUR... Regards, Pascal de Bruijn From knizek.confy at volny.cz Wed Feb 10 22:31:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 23:31:36 +0100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <1265841096.7579.76.camel@athlon> Getting back to update of the text: > -- > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. > -- Taking into account Graeme's points (thanks, it was helpful), how about this: (The GCM gamma fine tuning tool remains as it is - i.e. pure adjustment to LUT, not taking care about the monitor native gamma) --- Overall system gamma is a product of image encoding gamma, video card gamma and native gamma of the monitor and normally it should be equal to 1. You may want to adjust gamma to allow for non-standard viewing conditions (e.g increasing gamma in dim light at home). Refer to User Manual for more details. --- And this be included in User Manual: --- CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually emulate the same value. Traditionally, Linux and MS Windows operating systems use image encoding of 1/2.2 and do not apply any gamma adjustment to the image or video card LUT. Therefore the overall gamma is expected to be around 1.1 (which is useful to allow for dim viewing conditions at home environment). Apple used to use image encoding gamma close to 1/1.8 to naturally match the native gamma of printing devices (and therefore internally applied gamma adjustment of 1/1.45 before displaying images on monitor so that the images displayed correctly). Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding gamma has also the value of 1/2.2 to meet the requirements of consumer imaging industry. Before fine tuning the gamma in GCM, you should know what your monitor native gamma is, what display gamma you want to reach and then do the math yourself. --- regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pedro at pedrocr.net Thu Feb 11 08:49:07 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 00:49:07 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> Message-ID: <62e8012c1002110049j76960ec1jbeac96b428a2221c@mail.gmail.com> On Wed, Feb 10, 2010 at 12:52 PM, Pascal de Bruijn > I'd be willing to pitch in (PayPal) for about 25EUR... You can count me in for another 50$. Pedro From paul at fincc.com Thu Feb 11 09:54:05 2010 From: paul at fincc.com (Paul Finnigan) Date: Thu, 11 Feb 2010 09:54:05 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <1265882045.4190.8.camel@localhost> Hi everyone Sorry, I took a few days off reading the postings. Thanks Milan for trying to drive this one. On Wed, 2010-02-10 at 21:01 +0100, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. > > The more expensive variant would require about 10 people @ USD 50 > donation each. (Or less donors to buy in the U.S. and someone to > actually deliver across the ocean.) I am a photographer who likes to keep up with the Jones' (MS/Apple). To do this while running Linux I have had to make compromise after compromise with regard to 'Free' software. This is my own choice and I am not complaining about it. As an example I have paid for the Turbo Linux printer drivers. I have to say they are good, I do not begrudge the author his 29 euros. If I want free software then I believe it will cost me money at times. What Richard is providing is something, as a photographer, I have wanted for some time. He is also providing the source to the community. I know others are involved (thanks to everyone who is helping). I admit my suggestion of $50 was perhaps high. I just thought that as I know that TurboLinux drivers are popular with photographers I could pitch in a little above that price ($38). I am sure that we as a community can support ourselves. Look at what the Gnome community has already done. What is being asked here is that we get some hardware for a key developer to ensure that the software does what we all want, to help us manage colour. To get the ball rolling we need to set up an account. I am willing to let Richard have my $50 even if we do not reach the target of $500. If Richard or anyone else would like to mail me directly my address is paul at fincc dot com. -- Paul Finnigan From pmjdebruijn at pcode.nl Thu Feb 11 10:38:54 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 11:38:54 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> Message-ID: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> On Wed, Feb 10, 2010 at 8:38 PM, Richard Hughes wrote: > On 10 February 2010 17:17, Pascal de Bruijn wrote: >> I modified the thumbnail slightly to even out the lighting, and >> improve contrast. > > Looks great. I just processed the ColorCheckerSG image submitted by Hening Betterman on the ArgyllCMS mailing list. I attached a patch. Please verify before committing. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-ColorCheckerSG-target-image-submitted-by-Hening-.patch Type: text/x-patch Size: 45877 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 11 10:53:42 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:53:42 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> Message-ID: <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> On 11 February 2010 10:38, Pascal de Bruijn wrote: > I just processed the ColorCheckerSG image submitted by Hening > Betterman on the ArgyllCMS mailing list. > > I attached a patch. Please verify before committing. Perfect. Thanks. Richard. From hughsient at gmail.com Thu Feb 11 10:55:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:55:40 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> On 11 February 2010 09:54, Paul Finnigan wrote: > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If we don't reach the target I just have to convince my wife that it's a work thing and pony up the rest. Richard. From hughsient at gmail.com Thu Feb 11 11:05:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 11:05:28 +0000 Subject: Information re. display gamma In-Reply-To: <1265841096.7579.76.camel@athlon> References: <1265374532.31703.61.camel@athlon> <1265841096.7579.76.camel@athlon> Message-ID: <15e53e181002110305h113bd2c8kd8b863fbc1a4005e@mail.gmail.com> On 10 February 2010 22:31, Milan Kn??ek wrote: > Overall system gamma is a product of image encoding gamma, video card > gamma and native gamma of the monitor and normally it should be equal to > 1. You may want to adjust gamma to allow for non-standard viewing > conditions (e.g increasing gamma in dim light at home). Refer to User > Manual for more details. > --- > And this be included in User Manual: > --- > CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually > emulate the same value. > > Traditionally, Linux and MS Windows operating systems use image encoding > of 1/2.2 and do not apply any gamma adjustment to the image or video > card LUT. Therefore the overall gamma is expected to be around 1.1 > (which is useful to allow for dim viewing conditions at home > environment). > > Apple used to use image encoding gamma close to 1/1.8 to naturally match > the native gamma of printing devices (and therefore internally applied > gamma adjustment of 1/1.45 before displaying images on monitor so that > the images displayed correctly). > > Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding > gamma has also the value of 1/2.2 to meet the requirements of consumer > imaging industry. > > Before fine tuning the gamma in GCM, you should know what your monitor > native gamma is, what display gamma you want to reach and then do the > math yourself. Sounds good to me. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 11 11:57:49 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 12:57:49 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> Message-ID: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> On Thu, Feb 11, 2010 at 11:55 AM, Richard Hughes wrote: > On 11 February 2010 09:54, Paul Finnigan wrote: >> To get the ball rolling we need to set up an account. I am willing to >> let Richard have my $50 even if we do not reach the target of $500. > > If we don't reach the target I just have to convince my wife that it's > a work thing and pony up the rest. Then setup a PayPal account, and leave the details here :) Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 11 12:55:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 12:55:27 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> Message-ID: <15e53e181002110455l21da13pfe21eccf360fc192@mail.gmail.com> On 11 February 2010 11:57, Pascal de Bruijn wrote: > Then setup a PayPal account, and leave the details here :) I've already got a paypal account, richard at hughsie.com Please leave me your email addresses in any payments, in case we make nowhere near the total and I have to refund people. Thanks. Richard. From alexandre.prokoudine at gmail.com Thu Feb 11 19:30:38 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Thu, 11 Feb 2010 22:30:38 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> On 2/10/10, Milan Kn??ek wrote: > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? Yes, via PayPal. Count me in. Alexandre From pmjdebruijn at pcode.nl Thu Feb 11 20:44:25 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 21:44:25 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> Message-ID: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> On Thu, Feb 11, 2010 at 8:30 PM, Alexandre Prokoudine wrote: > On 2/10/10, Milan Kn??ek wrote: > >> Anybody else here willing to help with even a smaller amount (probably >> via PayPal)? Or other suggestions? > > Yes, via PayPal. Count me in. I just PayPalled 25 EUR... Regards, Pascal de Bruijn From pedro at pedrocr.net Fri Feb 12 01:42:10 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 17:42:10 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> Message-ID: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: > I just PayPalled 25 EUR... Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware organizations do this in scale? It would be great to be able to pitch in money to a common fund saying "I'd like this specific piece/type of hardware to work better in Linux" so that developers could get free access to hardware. By the way Richard, I've recently been through the battle of profiling my Epson R2880 with color munki, directly with argyll commands. I kept a few notes so I can tell you the commands that worked, the number of patches that were reasonable and especially about a small hack I did to be able to use much smaller patches with the color munki (and thus use less paper). Cheers, Pedro From pmjdebruijn at pcode.nl Fri Feb 12 07:38:57 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 08:38:57 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> On Fri, Feb 12, 2010 at 2:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: >> I just PayPalled 25 EUR... > > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? It would be great to be able to pitch > in money to a common fund saying "I'd like this specific piece/type of > hardware to work better in Linux" so that developers could get free > access to hardware. > > By the way Richard, I've recently been through the battle of profiling > my Epson R2880 with color munki, directly with argyll commands. I kept > a few notes so I can tell you the commands that worked, the number of > patches that were reasonable and especially about a small hack I did > to be able to use much smaller patches with the color munki (and thus > use less paper). Your hack was pretty cool, but it's not really handy to implement as a generic solution for GCM, we need no fuss solutions. This works very well for me... and would be a great default for medium quality: argyll-targen -v -d2 -f 210 xxx printtarg -v -i CM -h -T 300 -p A4 xxx colprof -q m -a l xxx For low quality the -h parameter can be dropped from printtarg, and lower the number of patches to ~90, whatever fits on a A4 piece of paper... One the the main problems is that these settings can vary from spectrophotometer to spectrophotometer... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 08:54:11 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:54:11 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <15e53e181002120054j23a0b855n55a671f870605644@mail.gmail.com> On 12 February 2010 07:38, Pascal de Bruijn > One the the main problems is that these settings can vary from > spectrophotometer to spectrophotometer... Sure, but we only care about a handful of types, and we can quite easily use the GUdev data to build up a profile for each device type, falling back if the device is unknown. I think it would be very useful to make Munki-specific data, as long as we have good fallbacks for the devices people keep secret. Richard. From hughsient at gmail.com Fri Feb 12 08:57:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:57:26 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> Message-ID: <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> On 11 February 2010 18:31, Pascal de Bruijn > But it's even worse, I screwed up the image as well... Here's a replacement. Applied, thanks. Do you want me to arrange for you to get GNOME commit access? It would mean you can commit this sort of thing without asking? Richard. From pedro at pedrocr.net Fri Feb 12 10:42:17 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:42:17 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: > Your hack was pretty cool, but it's not really handy to implement as a > generic solution for GCM, we need no fuss solutions. We will surely need a default mode that does that but my experience with doing it like you do bellow is that 200 patches isn't really reasonable. With the default settings you need 2 Letter pages to do ~190 and that generates pretty useless profiles. So to do the ~450+900 patches I ended up using for a decent profile you'd need ~15 pages which is a terrible waste of paper and ink. Like Richard says, it would be great to have the profiling instruments defined in a config somewhere, so that one can define a "Munki" and a "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" UI probably makes sense too as people doing color profiling would tend to be advanced users. > This works very well for me... and would be a great default for medium quality: > ?argyll-targen -v -d2 -f 210 xxx I ended up only getting good results at 450+900 patches. I suppose lower than that could also work. This should probably be given as an option to the user. Maybe a slider with markings or poor - basic - good - great and an automatic calculation of how many pages it is going to print, so that the user can do the tradeoff himself. > ?printtarg -v -i CM -h -T 300 -p A4 xxx My hack uses "-i i1". I haven't used the -T one. What does increasing the resolution help with? > ?colprof -q m -a l xxx "-a l" is default and I had also "-c mt" and "-d pp". Maybe they are not really needed. Cheers, Pedro From pedro at pedrocr.net Fri Feb 12 10:54:55 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:54:55 -0800 Subject: Building a library of ICC profiles Message-ID: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Hi, Is there any package that collects free (as in speech) ICC profiles? I see that Pascal's PPA has one printer, one camera and two or three displays. Are these just the ones you did yourself Pascal? I'd be more than happy to add the profiles I've been doing for the printer and monitor to some repository so that users without a calibration instrument can just use a profile from the library. I already have profiles for a Dell U2410 and an Epson R2880 with Glossy Epson paper. I'll be adding more papers to that too. One thing I haven't done yet is profiling my camera. How is that done and what is the benefit? I have a Sony A700 DSLR. Cheers, Pedro From hughsient at gmail.com Fri Feb 12 11:14:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:14:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Message-ID: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> On 12 February 2010 10:54, Pedro C?rte-Real wrote: > Is there any package that collects free (as in speech) ICC profiles? I > see that Pascal's PPA has one printer, one camera and two or three > displays. Are these just the ones you did yourself Pascal? There's http://github.com/hughsie/shared-color-profiles which may be of interest to you. > I'd be more than happy to add the profiles I've been doing for the > printer and monitor to some repository so that users without a > calibration instrument can just use a profile from the library. I > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > Epson paper. I'll be adding more papers to that too. I'm not so sure submitting user-generated profiles makes so much sense, I mean, your Epson R2880 probably has a quite different response to my (hypothetical) Epson R2880. If people think this is a good idea, I'd be wiling to set something like this up, as lets face it, a profile that is 3% off correct is better than no profile at all. > One thing I > haven't done yet is profiling my camera. How is that done and what is > the benefit? I have a Sony A700 DSLR. That's something you really want to do. We probably want to add a whole load of text in the help file in how to do this (sunny day, etc) but using GCM the process itself should be pretty easy. Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:15:52 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:15:52 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> Message-ID: <4c2c37f91002120315vc4ee9fcy7e31caaee1db3a4c@mail.gmail.com> On Fri, Feb 12, 2010 at 11:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: >> Your hack was pretty cool, but it's not really handy to implement as a >> generic solution for GCM, we need no fuss solutions. > > We will surely need a default mode that does that but my experience > with doing it like you do bellow is that 200 patches isn't really > reasonable. With the default settings you need 2 Letter pages to do > ~190 and that generates pretty useless profiles. So to do the ~450+900 > patches I ended up using for a decent profile you'd need ~15 pages > which is a terrible waste of paper and ink. > > Like Richard says, it would be great to have the profiling instruments > defined in a config somewhere, so that one can define a "Munki" and a > "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" > UI probably makes sense too as people doing color profiling would tend > to be advanced users. > >> This works very well for me... and would be a great default for medium quality: >> ?argyll-targen -v -d2 -f 210 xxx > > I ended up only getting good results at 450+900 patches. I suppose > lower than that could also work. This should probably be given as an > option to the user. Maybe a slider with markings or poor - basic - > good - great and an automatic calculation of how many pages it is > going to print, so that the user can do the tradeoff himself. Highly depends on what kind of accuracy ones expects... 210 patches and -qm works reasonably well... I actually tried making a profile using 840 patches, and -qh, and I don't see a big difference here... Though my printer is much crappier than yours. >> ?printtarg -v -i CM -h -T 300 -p A4 xxx Anyway, patches count should most likely always be multiple of what a single sheet can hold... 1x A4 -> 210 2x A4 -> 420 3x A4 -> 630 4x A4 -> 840 This may be different for letter (190?). > My hack uses "-i i1". I haven't used the -T one. What does increasing > the resolution help with? This is seriously not an option for GCM... requiring users to make their own DIY patch reading guide. The colorimeter/spectrophotometer should work as develivered by the manufacturer... GNOME is about making things work as expected... not requiring DIY hobbying/hacks... For these kinds of strategies, using the Argyll commandline tools should be fine. Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:20:27 +0000 Subject: Adding a libtiff dep? Message-ID: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to add a libtiff hard dep on gnome-color-manager. All distros should already be installing this by default, but I wanted to check to see if anyone had any issue with this. Speak now, or forever hold your peace! :-) Thanks, Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:22:46 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:22:46 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: >> Is there any package that collects free (as in speech) ICC profiles? I >> see that Pascal's PPA has one printer, one camera and two or three >> displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. Those profiles are mostly for my private use... The camera profiles are probably generally usable though... >> I'd be more than happy to add the profiles I've been doing for the >> printer and monitor to some repository so that users without a >> calibration instrument can just use a profile from the library. I >> already have profiles for a Dell U2410 and an Epson R2880 with Glossy >> Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. One big problem with printer profiles are driver setttings, since profiles are also very specific to driver settings... I have no clue on how to solve that... Ideally you'd want the printer settings to be embedded in the profile. > If people think this is a good idea, I'd be wiling to set something > like this up, as lets face it, a profile that is 3% off correct is > better than no profile at all. Yeah sortof... >> One thing I >> haven't done yet is profiling my camera. How is that done and what is >> the benefit? I have a Sony A700 DSLR. > > That's something you really want to do. We probably want to add a > whole load of text in the help file in how to do this (sunny day, etc) > but using GCM the process itself should be pretty easy. I wrote about this here: http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Though the article is dated, and should be revised... I did make a few new discoveries... For example, I only recently noticed that strobes actually work well as reference light for generic profiles... I'm probably going to do a new blog post over the weekend... Here are some generic tips van raw photography with UFRaw in general: http://blog.pcode.nl/2009/08/23/ufraw-faq/ Most of it should apply to other dcraw based applications as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Fri Feb 12 11:24:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:24:10 +0100 Subject: Adding a libtiff dep? In-Reply-To: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> Message-ID: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> On Fri, Feb 12, 2010 at 12:20 PM, Richard Hughes wrote: > To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to > add a libtiff hard dep on gnome-color-manager. All distros should > already be installing this by default, but I wanted to check to see if > anyone had any issue with this. > > Speak now, or forever hold your peace! :-) Seems fine... Doesn't eog already depend on libtiff anyway? Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:26:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:26:28 +0000 Subject: Adding a libtiff dep? In-Reply-To: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> Message-ID: <15e53e181002120326q1d693e40wa44d44ab56c5efe0@mail.gmail.com> On 12 February 2010 11:24, Pascal de Bruijn wrote: > Seems fine... Doesn't eog already depend on libtiff anyway? Sure, but eog might not be installed on the live-cd, and g-c-m probably should... Richard. From hughsient at gmail.com Fri Feb 12 11:28:54 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:28:54 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> On 12 February 2010 11:22, Pascal de Bruijn wrote: > I wrote about this here: > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Yes, this entry is very helpful, and I would love to see a large chunk added to the GNOME Color Manager help pages, if you're okay with re-licensing the content. Richard. From dan at berrange.com Fri Feb 12 11:30:51 2010 From: dan at berrange.com (Daniel P. Berrange) Date: Fri, 12 Feb 2010 11:30:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <20100212113051.GA13638@berrange.com> On Fri, Feb 12, 2010 at 11:14:51AM +0000, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: > > Is there any package that collects free (as in speech) ICC profiles? I > > see that Pascal's PPA has one printer, one camera and two or three > > displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. > > > I'd be more than happy to add the profiles I've been doing for the > > printer and monitor to some repository so that users without a > > calibration instrument can just use a profile from the library. I > > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > > Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. IIUC, printer profiles will vary on the set (hardware, ink, driver, paper) so building a library of profiles is quite large task. You could make it more managable by initially concentrating on the printer manufacturer's own recommended brand/combination of ink+paper+drivers Regards, Daniel -- |: http://berrange.com/ -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://freshmeat.net/~danielpb/ -o- http://gtk-vnc.sourceforge.net :| From pmjdebruijn at pcode.nl Fri Feb 12 12:01:33 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 13:01:33 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> Message-ID: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> On Fri, Feb 12, 2010 at 12:28 PM, Richard Hughes wrote: > On 12 February 2010 11:22, Pascal de Bruijn wrote: >> I wrote about this here: >> ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Yes, this entry is very helpful, and I would love to see a large chunk > added to the GNOME Color Manager help pages, if you're okay with > re-licensing the content. No problem, but I'd like my rewrite to be in the help pages :) Not this particular article... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 12:09:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 12:09:23 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> Message-ID: <15e53e181002120409veeecbbcn1f4a04d55b353beb@mail.gmail.com> On 12 February 2010 12:01, Pascal de Bruijn wrote: > No problem, but I'd like my rewrite to be in the help pages :) Cool. Just add text to help/C/gnome-color-manager.xml and format a patch as normal. If you get stuck with docbook, give me a shout. Richard. From alexandre.prokoudine at gmail.com Fri Feb 12 12:54:08 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 12 Feb 2010 15:54:08 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <733f2c731002120454p2f0143ddgf9dfe37e4b9a3713@mail.gmail.com> On Fri, Feb 12, 2010 at 4:42 AM, Pedro C?rte-Real wrote: > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? http://linuxfund.org/ Alexandre From hughsient at gmail.com Fri Feb 12 15:10:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 15:10:10 +0000 Subject: Color correcting projectors? Message-ID: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> In GCM we currently support two types of display profiling. Internal (LVDS) panels are internal to the system, and external panels (DVI and the others) are external to the system. What different settings do we need to do for projectors? We certainly need to give different instructions (which we also need to write), but will argyll just process these like a low-gamut LCD screen? Are there any options we need to add? Richard. From pmjdebruijn at pcode.nl Fri Feb 12 15:25:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 16:25:50 +0100 Subject: Color correcting projectors? In-Reply-To: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> Message-ID: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> On Fri, Feb 12, 2010 at 4:10 PM, Richard Hughes wrote: > In GCM we currently support two types of display profiling. Internal > (LVDS) panels are internal to the system, and external panels (DVI and > the others) are external to the system. > > What different settings do we need to do for projectors? We certainly > need to give different instructions (which we also need to write), but > will argyll just process these like a low-gamut LCD screen? Are there > any options we need to add? Well I think Argyll has a -p option :) And the instructions obviously need to be different, there's a "rule" which states the colorimeter should be 1.5 times the height of the projected image away from the "screen", or something like that... Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 12 20:28:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 12 Feb 2010 21:28:14 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <1266006494.22377.14.camel@athlon> Paul Finnigan p??e v ?t 11. 02. 2010 v 09:54 +0000: > I am a photographer who likes to keep up with the Jones' (MS/Apple). To > do this while running Linux I have had to make compromise after > compromise with regard to 'Free' software. This is my own choice and I > am not complaining about it. Paul said it well, it fits my experience. I had to learn a lot of things to be able to use Linux for my photographic hobby and I hope that soon the photographer's life with Linux be more user friendly. > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If > Richard or anyone else would like to mail me directly my address is paul > at fincc dot com. I have given ?100, maybe a bit more than usual but anyway I hope Richard will not feel obliged to prefer my wishes about GCM - it is a donation, not a wage. Also, no need to return if the target is not reached. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Fri Feb 12 22:00:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 23:00:20 +0100 Subject: Perspective Distortion Compensation Message-ID: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Hi, Currently input profile calibration can fail because a target has even the slightest perspective distortion. Argyll can compensate for that within reason. This patch should enable perspective distortion compensation. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-have-scanin-compensate-for-perspective-distortion.patch Type: text/x-patch Size: 911 bytes Desc: not available URL: From paul at fincc.com Sat Feb 13 01:16:32 2010 From: paul at fincc.com (Paul Finnigan) Date: Sat, 13 Feb 2010 01:16:32 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266006494.22377.14.camel@athlon> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> Message-ID: <1266023792.2313.21.camel@localhost> Milan On Fri, 2010-02-12 at 21:28 +0100, Milan Kn??ek wrote: > I have given ?100, maybe a bit more than usual but anyway I hope Richard > will not feel obliged to prefer my wishes about GCM - it is a donation, > not a wage. Also, no need to return if the target is not reached. What a nice way of putting it! It sounds like you are used to being part of a community, rather than a gathering of geeks. It is amazing but through everyone's (OK in the main Richard's) efforts I feel part of this community without putting anything in myself (I am still attempting to get setup in paypal. I am ancient and not used to money being passed over the ether. Don't worry Richard I will put my money where my mouth is as soon as I can get money into paypal). Thanks to this project I have found many new friends. How can I help? Richard has suggested people to write the help documentation. I am willing but what format and how? Is there a howto I can read anywhere that would help? I am desperate to do more but my skills are in the area of project and service management not coding. -- Paul Finnigan From graeme2 at argyllcms.com Sat Feb 13 01:17:23 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 13 Feb 2010 12:17:23 +1100 Subject: Color correcting projectors? In-Reply-To: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> Message-ID: <4B75FDA3.9050601@argyllcms.com> Pascal de Bruijn wrote: > Well I think Argyll has a -p option :) -p is an instrument config. option, and is currently only applicable to a single instrument, the ColorMunki. You can use other instruments to measure projectors, but they don't have a special mode for it. (I think I'll changed dispcal and dispread to automatically fallback to display mode if the instrument doesn't have a projector mode, to make them a bit more forgiving). Graeme Gill. From hughsient at gmail.com Sat Feb 13 09:17:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:17:06 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266023792.2313.21.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> <1266023792.2313.21.camel@localhost> Message-ID: <15e53e181002130117s270af2b9kcc97bc7ef471c82@mail.gmail.com> On 13 February 2010 01:16, Paul Finnigan wrote: > What a nice way of putting it! It sounds like you are used to being part > of a community, rather than a gathering of geeks. It is amazing but > through everyone's (OK in the main Richard's) efforts I feel part of > this community without putting anything in myself (I am still attempting > to get setup in paypal. I am ancient and not used to money being passed > over the ether. Don't worry Richard I will put my money where my mouth > is as soon as I can get money into paypal). We've very nearly reached the total! I'm nearly at the "amount I can sneak on the shared credit card without the wife noticing" stage :-) > Thanks to this project I have found many new friends. How can I help? > Richard has suggested people to write the help documentation. I am > willing but what format and how? Is there a howto I can read anywhere > that would help? I am desperate to do more but my skills are in the area > of project and service management not coding. Right, then we need to start with some documentation or UI fixes, and then work on from there. My spelling and grammar are notoriously bad, so this is where I need the most help. If you first: * download the git package (using yum, apt-get, or your distro tool) * "clone" the developers checkout. For this you want to follow http://live.gnome.org/Git/Developers -- specifically the project name is gnome-color-manager (you can also ignore 90% of that page, it's overly complicated, but maybe a good read if you want detail) * create you're own personal branch (not on the server): git checkout -b my-playground-branch * Edit the file help/C/gnome-color-manager.xml, copying the syntax (e.g. using for a new paragraph), making the changes you want * "commit" the changes, which basically means you save them, and give them a description: git commit -a -m "Correct the spelling of Colour to Color" --author "Richard Hughes " * get a text file of the changes you want to send to us: "git format-patch master" (this generates 0001-a-file-with-a-peculiar-name.patch) Send the 0001-a-file-with-a-peculiar-name.patch as an attachment to this mailing list. Then you can either go back to the pristine upstream tree "git checkout master" or stay on your private tree and make more changes. You can commit many small changes and then do "git format-patch" and you get files 0001, 0002, 0003, 0004, etc and send them all in one long email. If you break stuff, then you can get rid of all your changes (since the last time you committed them) with "git reset --hard", and you can ensure you've got the latest changes from upstream by doing "git checkout master && git pull --rebase" It sounds complicated, but give it a try and yell when you get stuck. Weekdays I'm on IRC if that helps. Richard. From hughsient at gmail.com Sat Feb 13 09:19:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:19:58 +0000 Subject: Perspective Distortion Compensation In-Reply-To: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> References: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Message-ID: <15e53e181002130119k4b3d9a16j403ff3c4aa2f4c31@mail.gmail.com> On 12 February 2010 22:00, Pascal de Bruijn wrote: > This patch should enable perspective distortion compensation. Applied, thanks. Richard. From pmjdebruijn at pcode.nl Sat Feb 13 10:43:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 11:43:44 +0100 Subject: Bug #605259: Colorimeter name in profile description Message-ID: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Hi, Currently on my Ubuntu Karmic system, the colorimeter name still isn't getting into the profile description... Could you give me any pointer how the colorimeter is resolved? And where I should look into the sources? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 14:09:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 14:09:51 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Message-ID: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> On 13 February 2010 10:43, Pascal de Bruijn wrote: > Currently on my Ubuntu Karmic system, the colorimeter name still isn't > getting into the profile description... Hmm, I'm getting "Huey" prepended to my profile. > Could you give me any pointer how the colorimeter is resolved? And > where I should look into the sources? Well, take a look at src/gcm-color-device.c and make sure that the model and vendor are being set correctly. It's possible you need to add: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="usb-db %p" to your 55-Argyll.rules file, if your device doesn't have an entry in the kernel USB driver. That's what I've done in hargyll, and if it fixes it for you too, I'll push this patch to Graeme. Richard From pmjdebruijn at pcode.nl Sat Feb 13 19:40:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 20:40:24 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> On Fri, Feb 12, 2010 at 12:22 PM, Pascal de Bruijn wrote: > On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: >> On 12 February 2010 10:54, Pedro C?rte-Real wrote: >>> One thing I >>> haven't done yet is profiling my camera. How is that done and what is >>> the benefit? I have a Sony A700 DSLR. >> >> That's something you really want to do. We probably want to add a >> whole load of text in the help file in how to do this (sunny day, etc) >> but using GCM the process itself should be pretty easy. > > I wrote about this here: > > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Though the article is dated, and should be revised... I did make a few > new discoveries... > > For example, I only recently noticed that strobes actually work well > as reference light for generic profiles... > > I'm probably going to do a new blog post over the weekend... > > Here are some generic tips van raw photography with UFRaw in general: > > ?http://blog.pcode.nl/2009/08/23/ufraw-faq/ > > Most of it should apply to other dcraw based applications as well. I'm rewriting my article as I type this, it should already be accessible as a preview: http://blog.pcode.nl/?p=551&preview=true Any comments before I publish? Any thing not clear? If all goes well (I still need to do some more testing), this article can be reworked into GCM help. Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 21:27:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 21:27:34 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <15e53e181002131327l76d8dc0du282ca3c5a5be4423@mail.gmail.com> On 10 February 2010 20:01, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. We've reached the total! Thanks guys, I feel very humbled. Thanks. ColorMunki Photo is ordered, and will arrive in about a weeks time. Richard. From hughsient at gmail.com Sun Feb 14 20:56:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 14 Feb 2010 20:56:10 +0000 Subject: Request for colorimeter figures Message-ID: <15e53e181002141256t1c39960dle71b65839ca6d451@mail.gmail.com> Hey guys, I've added support to GCM today to display images to help the user attach the colorimeter device to the screen, and to set it to correct mode. I've attached two images as examples. If anybody is interested in drawing pictures (or improving mine) it would be very welcome. I don't mind how many images we add. Ideally we should show images of the most common colorimeters in existence, and how to switch things to the correct modes. You'll have to create SVG figures yourself (I used inkscape) and obviously not include any trademarks. If you're a worse artist than me, feel free to send a photo of the colorimeter attached to the screen, and switching between different modes and one of us geeks on list can convert this to a SVG. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: huey-attach.svg Type: image/svg+xml Size: 61010 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: munki-projector.svg Type: image/svg+xml Size: 66407 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 15 01:23:01 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 02:23:01 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> Message-ID: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> On Sat, Feb 13, 2010 at 3:09 PM, Richard Hughes wrote: > On 13 February 2010 10:43, Pascal de Bruijn wrote: >> Currently on my Ubuntu Karmic system, the colorimeter name still isn't >> getting into the profile description... > > Hmm, I'm getting "Huey" prepended to my profile. > >> Could you give me any pointer how the colorimeter is resolved? And >> where I should look into the sources? > > Well, take a look at src/gcm-color-device.c and make sure that the > model and vendor are being set correctly. It's possible you need to > add: > > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="usb-db %p" > > to your 55-Argyll.rules file, if your device doesn't have an entry in > the kernel USB driver. That's what I've done in hargyll, and if it > fixes it for you too, I'll push this patch to Graeme. It's not fixing it for me now... But I don't think I have the usb-db utility installed... Where should I have gotten it from? Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 11:34:49 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 11:34:49 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> Message-ID: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> On 15 February 2010 01:23, Pascal de Bruijn wrote: > It's not fixing it for me now... But I don't think I have the usb-db > utility installed... Where should I have gotten it from? Any modern udev should have it. Use "udevadm monitor" to monitor the device events as the device is plugged in. Richard. From pmjdebruijn at pcode.nl Mon Feb 15 11:36:12 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 12:36:12 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> Message-ID: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: > On 15 February 2010 01:23, Pascal de Bruijn wrote: >> It's not fixing it for me now... But I don't think I have the usb-db >> utility installed... Where should I have gotten it from? > > Any modern udev should have it. Use "udevadm monitor" to monitor the > device events as the device is plugged in. Indeed $ dpkg -L udev | grep usb-db /lib/udev/usb-db But it's not in my path, I'm not sure whether that matters? I'll try udev monitor later today. Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 20:34:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 20:34:26 +0000 Subject: Adding support for xsane Message-ID: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> I've coded some initial support for xsane-based application in a private branch. It basically writes the right thing in the per-user xsane directories for the system and device settings. I'm not sure whether to merge it to master or not, as it's pretty hacky code. Ideally we would talk to easy-scan / gnome-scan in the future using a nice DBus interface, but I think that's a few years away. It does not depend on sane (that's a separate branch...) and if you don't use xsane then the file just gets written and nothing uses it. So, what do you guys think? Richard. From knizek.confy at volny.cz Mon Feb 15 21:19:05 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 15 Feb 2010 22:19:05 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> Message-ID: <1266268745.6707.9.camel@athlon> Pascal de Bruijn p??e v So 13. 02. 2010 v 20:40 +0100: > I'm rewriting my article as I type this, it should already be > accessible as a preview: > > http://blog.pcode.nl/?p=551&preview=true > > Any comments before I publish? Any thing not clear? > Pascal - the page is "not found". I guess you would actually have to post it to make it available to public. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 15 22:09:10 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 16 Feb 2010 01:09:10 +0300 Subject: Adding support for xsane In-Reply-To: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> Message-ID: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> On 2/15/10, Richard Hughes wrote: > Ideally we would talk to easy-scan / gnome-scan in the future using a > nice DBus interface, but I think that's a few years away. Robert Ancell blogged recently that he is going to implement color management after 1.0, and his is now in post 0.9.0 bugfixing mode. So it's probably not that bad :) Alexandre From hughsient at gmail.com Mon Feb 15 22:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 22:16:56 +0000 Subject: Adding support for xsane In-Reply-To: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> Message-ID: <15e53e181002151416p37413a9je110eab793646198@mail.gmail.com> On 15 February 2010 22:09, Alexandre Prokoudine wrote: > Robert Ancell blogged recently that he is going to implement color > management after 1.0, and his is now in post 0.9.0 bugfixing mode. So > it's probably not that bad :) Cool. What we need him to do is: * Provide a method to scan a target without applying any icc profiles at all, so we can use it to calibrate the device. * Get the default icc profile assigned by GCM using the udev path or the SANE id, for normal scans. * Tag the resulting scans with the assigned ICC profile Should be no more than an afternoons hacking :-) Richard. From paul at fincc.com Tue Feb 16 00:45:54 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 00:45:54 +0000 Subject: Camera Support Message-ID: <1266281154.2768.8.camel@localhost> Hi I decided to attempt to use a profile with my camera. The camera does not appear on the list of devices, even when it is plugged in. Am I missing something? I can import my profiles but I cannot assign them to a device. The camera is a Nikon D700. Gnome recognises the camera and allows me to open a nautilus viewer on the memory card, open photographs etc. I can see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b0 ProdID=0422 Rev= 1.00 S: Manufacturer=NIKON S: Product=NIKON DSC D700 S: SerialNumber=000002034583 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=usbfs E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms If I run gcm in verbose mode: TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 So we see the camera connect. Am I missing something? I am running off a copy from the GIT -- Paul Finnigan Finnigan Computer Consultants Ltd. From hughsient at gmail.com Tue Feb 16 09:26:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 09:26:26 +0000 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> On 16 February 2010 00:45, Paul Finnigan wrote: > If I run gcm in verbose mode: > > TI:00:40:05 FI:gcm-colorimeter.c ? ? ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:05 ? ? FI:gcm-colorimeter.c ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > > So we see the camera connect. Am I missing something? Is that all you get when you connect the camera? Could you attach the output from "udevadm monitor" when you plug in the device please. I'm a little surprised it doesn't work, given my D60 works fine. Thanks. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 11:54:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 12:54:27 +0100 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > Hi > > I decided to attempt to use a profile with my camera. The camera does > not appear on the list of devices, even when it is plugged in. Am I > missing something? I can import my profiles but I cannot assign them to > a device. Currently assigning camera profiles in GCM has no real function yet, since the RAW converters don't use this information. > The camera is a Nikon D700. Gnome recognises the camera and allows me to > open a nautilus viewer on the memory card, open photographs etc. I can > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > snip snip > > So we see the camera connect. Am I missing something? > > I am running off a copy from the GIT It works just fine with my EOS 400D as well... Also does your D700 have a recent firmware? Regards, Pascal de Bruijn From paul at fincc.com Tue Feb 16 11:57:31 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 11:57:31 +0000 Subject: Camera Support In-Reply-To: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> Message-ID: <1266321451.6701.12.camel@localhost> Richard On Tue, 2010-02-16 at 09:26 +0000, Richard Hughes wrote: > On 16 February 2010 00:45, Paul Finnigan wrote: > > If I run gcm in verbose mode: > > > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > > > So we see the camera connect. Am I missing something? > > Is that all you get when you connect the camera? Could you attach the > output from "udevadm monitor" when you plug in the device please. I'm > a little surprised it doesn't work, given my D60 works fine. Thanks. > > Richard. That is all I get from gcm. I am running Fedora 12 and have compiled gcm from the GIT. I only ever connect my camera to copy files to disc. I never ever read them directly with an application, or not in my normal workflow. That is I only use my Nikon as a (very expensive) memory stick! OK Fedora uses gphoto2 and gvfs. As requested 'udevadm moniotor' when connecting the camera gives: [paul at ewing ~]udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266321215.801858] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) KERNEL[1266321215.802262] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) UDEV [1266321215.813200] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) UDEV [1266321215.821229] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) Nautilus then lets me view photos using: gphoto2://[usb:001,009]/DCIM/100ND700 Thanks -- Paul Finnigan From paul at fincc.com Tue Feb 16 12:19:26 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 12:19:26 +0000 Subject: Camera Support In-Reply-To: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> Message-ID: <1266322766.6701.21.camel@localhost> Pascal On Tue, 2010-02-16 at 12:54 +0100, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > > Hi > > > > I decided to attempt to use a profile with my camera. The camera does > > not appear on the list of devices, even when it is plugged in. Am I > > missing something? I can import my profiles but I cannot assign them to > > a device. > > Currently assigning camera profiles in GCM has no real function yet, > since the RAW converters don't use this information. I knew that, which is why I had not tired it until now. I am looking at the help pages as I had (stupidly) volunteered and wanted to show an input device on the menu. My current scanner a Canon Lide 500 does not work with Sane so I cannot show that. > > The camera is a Nikon D700. Gnome recognises the camera and allows me to > > open a nautilus viewer on the memory card, open photographs etc. I can > > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > > > > snip snip > > > > > So we see the camera connect. Am I missing something? > > > > I am running off a copy from the GIT > > It works just fine with my EOS 400D as well... Also does your D700 > have a recent firmware? I would guess not. I have had it over 12 months, and have never had a need to update the firmware. If I need to I will update the firmware. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Tue Feb 16 12:29:45 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 13:29:45 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> Message-ID: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> On Mon, Feb 15, 2010 at 12:36 PM, Pascal de Bruijn wrote: > On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: >> On 15 February 2010 01:23, Pascal de Bruijn wrote: >>> It's not fixing it for me now... But I don't think I have the usb-db >>> utility installed... Where should I have gotten it from? >> >> Any modern udev should have it. Use "udevadm monitor" to monitor the >> device events as the device is plugged in. > > Indeed > > $ dpkg -L udev | grep usb-db > /lib/udev/usb-db > > But it's not in my path, I'm not sure whether that matters? I changed the udev-rule to include the full path of usb-db: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="/lib/udev/usb-db %p" Does this need to be in a particular place in 55-Argyll.rules? I attached the full file. After making the above change, I rebooted my system, and ran the udevadm monitor while plugging in the Huey. The results are attached. Regards, Pascal de Bruijn -------------- next part -------------- pmjdebruijn at biovore:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266323110.972649] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323110.975186] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323111.064958] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323111.106596] add /module/usbhid (module) KERNEL[1266323111.108080] add /bus/hid/drivers/generic-usb (drivers) UDEV [1266323111.108125] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323111.108145] add /bus/usb/drivers/hiddev (drivers) KERNEL[1266323111.108161] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.108519] add /bus/usb/drivers/hiddev (drivers) UDEV [1266323111.108804] add /module/usbhid (module) UDEV [1266323111.109292] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.110702] add /bus/hid/drivers/generic-usb (drivers) KERNEL[1266323117.762463] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323117.762504] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323117.763909] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323117.766370] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.321652] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.328367] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323121.338002] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323121.341140] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) pmjdebruijn at biovore:~$ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG -------------- next part -------------- A non-text attachment was scrubbed... Name: 55-Argyll.rules Type: application/octet-stream Size: 1953 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 16 21:43:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 21:43:31 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> Message-ID: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> On 16 February 2010 12:29, Pascal de Bruijn wrote: > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="/lib/udev/usb-db %p" Hmm, I don't think you need to include the full path this. > Does this need to be in a particular place in 55-Argyll.rules? I > attached the full file. > > After making the above change, I rebooted my system, and ran the > udevadm monitor while plugging in the Huey. The results are attached. Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I assume this is a Huey: 0971 Gretag-Macbeth AG 2005 Huey If it's not a Huey, then we have a problem, and we need to add an entry to usb.ids. See http://www.linux-usb.org/usb-ids.html if this is the case. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 21:56:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 22:56:10 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> Message-ID: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: > On 16 February 2010 12:29, Pascal de Bruijn wrote: >> # color calibration device >> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >> IMPORT{program}="/lib/udev/usb-db %p" > > Hmm, I don't think you need to include the full path this. Well the other lines include full paths, it would seem good practice consistency-wise. >> Does this need to be in a particular place in 55-Argyll.rules? I >> attached the full file. >> >> After making the above change, I rebooted my system, and ran the >> udevadm monitor while plugging in the Huey. The results are attached. > > Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like > ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I > assume this is a Huey: > > 0971 ?Gretag-Macbeth AG > ? ? ? ?2005 ?Huey I updated the usb database, and guess what: $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG ID_MODEL_FROM_DATABASE=Huey Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:13:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:13:17 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <4c2c37f91002161413w182c491cu2f8a269bf6bd91c4@mail.gmail.com> On Tue, Feb 16, 2010 at 10:56 PM, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: >> On 16 February 2010 12:29, Pascal de Bruijn wrote: >>> # color calibration device >>> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >>> IMPORT{program}="/lib/udev/usb-db %p" >> >> Hmm, I don't think you need to include the full path this. > > Well the other lines include full paths, it would seem good practice > consistency-wise. > >>> Does this need to be in a particular place in 55-Argyll.rules? I >>> attached the full file. >>> >>> After making the above change, I rebooted my system, and ran the >>> udevadm monitor while plugging in the Huey. The results are attached. >> >> Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like >> ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I >> assume this is a Huey: >> >> 0971 ?Gretag-Macbeth AG >> ? ? ? ?2005 ?Huey > > I updated the usb database, and guess what: > > $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 > ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG > ID_MODEL_FROM_DATABASE=Huey Ugh, I just calibrated my screen and it worked like a charm... Please push the udev rule to Graeme. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:31:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:31:38 +0100 Subject: [PATCH] New USB ID: X-Rite/Gretag-MacBeth ColorMunki Message-ID: <4c2c37f91002161431l7989a672gd240def3bbcf5a23@mail.gmail.com> Hi, The included patch has the USB ID for: http://www.colormunki.com/ The device is a spectrophotometer from X-Rite which recently acquired Gretag-Macbeth. I've tested using udev's usb-db, and the lookup works with my device. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: usb-ids-colormunki.patch Type: text/x-patch Size: 312 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 17 09:33:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 09:33:21 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <15e53e181002170133j3c968710y4dc7996dc31bc5b@mail.gmail.com> On 16 February 2010 21:56, Pascal de Bruijn wrote: > Well the other lines include full paths, it would seem good practice > consistency-wise. I disagree, but it shouldn't hurt as even on 64 bit the early udev boot is in /lib, not /lib64. Richard. From hughsient at gmail.com Wed Feb 17 14:05:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 14:05:27 +0000 Subject: Adding printer profiling support Message-ID: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> In a few days time, my nice lovely ColorMunki should be delivered. Before it is, I figured I should get up to speed on how to profile printers, so we know what UI to add to GCM, and so I can get up to speed quickly. So. Does anybody have any hints, tips or suggestions on how to calibrate a printer. Device specific options (e.g. "The ColorMunki works really well with -f234 -g567") are more than welcome, as we already know the colorimeter device type. In particular, we need to support printing to 6x4 inch cards, A4 and letter paper. I would love to integrate this better with CUPS (using the GTK print dialog for instance) than what we can do on the command line. We'll also need scans of the patches sheets that we send out, so we can show the user _how_ to scan in the patches. We'll also probably need a timer for "waiting for the ink to dry" and that sort of thing. Ideas very welcome. Thanks, Richard. From hughsient at gmail.com Wed Feb 17 19:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 19:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> Message-ID: <15e53e181002171147u290e197fnfe1e857f62b6723a@mail.gmail.com> On 17 February 2010 17:20, Pascal de Bruijn wrote: > J?rg Rosenkranz privately submitted an image of the LaserSoftDCPro > target to me. The attached patch should make it available for GCM. Applied, thanks. Richard. From pedro at pedrocr.net Thu Feb 18 04:50:09 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Wed, 17 Feb 2010 20:50:09 -0800 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: > In a few days time, my nice lovely ColorMunki should be delivered. > Before it is, I figured I should get up to speed on how to profile > printers, so we know what UI to add to GCM, and so I can get up to > speed quickly. > > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Here is my experience with the Munki from my notes. I've used it successfully to both profile a Dell U2410 LCD screen and an Epson R2880. The LCD profiling should work already but I ended up using the tools directly because g-c-m was failing to interact correctly with the argyll tools when they asked to change the position of the device. I think this has been fixed but haven't checked. Anyway for the printing profiling my steps were: 1 - Generate a set of color patches $argyll-targen -f 900 -v -d2 -c -A.8 This gave good results in the end. I did a first round of profiling with 450 patches and that was used as BestPreviousProfile. For the first round it would be instead: $argyll-targen -f 450 -v -d2 In general the number of patches to create is a judgment call. I don't know how we can present this option to the user. Maybe doing the calculation in reverse and asking him how many sheets he is willing to print and scan and then giving him an idea of how good a profile that generates. To then actually generate the files to print: $ printtarg -t -v -iCM -pLetter "Letter" should obviously be changed to whatever paper the user wants to use. The -iCM generates normally sized patches for the Munki, which will require many sheets of paper to fit the 900 patches. See bellow for a discussion of the hack I did to avoid this. 2. Print out the patches I printed the resulting tiff files with PhotoPrint. I believe it uses Gutenprint directly to drive the printer and is the only solution I know right now that can actually apply the ICC profile when printing later. The important thing here is to set the Gutenprint setting "Color Correction" to "Uncorrected", and then any of the image settings for the setup being used (type of paper, resolution, dithering, etc). 3. Read back the patches $chartread Munki will need to first be set to the self calibrate position, then to the profiling position and then run through each of the patch lines in turn while pressing its button. chartread asks for each of the lines and will ask for them again if there is any error. The interface needs to expose this. The last version allows you to reread a patch line at will. I wonder if it would be possible to have some kind of idea of how good the reads were and advise the user to reread one of the lines if it is found to not be too good. 4. Generate the profile $ colprof -v -D"" -qm -S -cmt -dpp This runs by itself without problems. The specific flags are arguable of course. I'm curious as to how changing -q (quality) to high or ultra changes the profile. Some considerations: - Some decent automatic naming would be nice - Selecting the source profile would be nice too (defaulting to sRGB) and possibly allowing the user to later generate the same profile with another profile (e.g. AdobeRGB) as source might be useful. - All the colprof settings can be changed without running the process from the beginning again. I wonder if g-c-m should have the notion of "Profiling runs" from which several actual profiles can be created. This would solve the sRGB/AdobeRGB selection as well. - Colprof outputs a final result with the mean and maximum error of the profile. It would be great to give this result to the user in plain English. Telling him the profile is "Poor/Fair/Good/Excellent" or even a result out of 100. The generated profile works in PhotoPrint. I assume it would also work to transform an image before sending it to the general CUPS pipeline. In theory the generated profile is only valid for the specific set of settings used for the printer. In practice using the same profile on even a different but similar paper is probably better than none at all. And using it at a different resolution on the same paper may very well be decent as well. I have no idea. > In particular, we need to support printing to 6x4 inch cards, A4 and > letter paper. I would love to integrate this better with CUPS (using > the GTK print dialog for instance) than what we can do on the command > line. We'll also need scans of the patches sheets that we send out, so > we can show the user _how_ to scan in the patches. We'll also probably > need a timer for "waiting for the ink to dry" and that sort of thing. My only other comment about the process is that using the Munki with default size patches is an incredible waste of paper and ink. In the argyll mailing list someone pointed out some user's hack on dpreview so I built one myself: http://pedrocr.net/MunkiHelper.jpg I'm not in any way suggesting that users should be expected to build one of these but I would like to be able to configure g-c-m to have not only the configuration for the normal Color Munki but also this hack. The only difference is to change the -iCM flag to printtarg to the -ii1, making the patches much smaller (by printing a sheet as if it was for another instrument). I know Pascal disagrees though. I share the sentiment of wanting to make this as simple to the user as possible. However my experience with this is that if we don't allow the user to fiddle with some of the advanced settings, whenever he hits a speed bump the only option is to fall back on argyll command line tools and totally bypass g-c-m. That doesn't seem like much of a solution either. My suggestion would be to have a set of default settings for each of the supported instruments that work in a straightforward way and then an "Advanced..." button to go and customize the settings. Cheers, Pedro From hughsient at gmail.com Thu Feb 18 09:28:41 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 18 Feb 2010 09:28:41 +0000 Subject: gnome-color-management test day Message-ID: <15e53e181002180128p9c9e977g8619a1518f86afd7@mail.gmail.com> Guys, We've got a GNOME Color Management test day happening today: https://fedoraproject.org/wiki/Test_Day:2010-02-18_Color_management It's very Fedora-centric, but I'm guessing as most of the testing and bugs will be common between distros, I guess it makes you more than welcome to join in. I'll be in the #fedora-test-day channel (on freenode) all day, answering questions and fixing bugs. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 18 17:57:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 18 Feb 2010 18:57:20 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> Message-ID: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: >> In a few days time, my nice lovely ColorMunki should be delivered. >> Before it is, I figured I should get up to speed on how to profile >> printers, so we know what UI to add to GCM, and so I can get up to >> speed quickly. >> >> So. Does anybody have any hints, tips or suggestions on how to >> calibrate a printer. Device specific options (e.g. "The ColorMunki >> works really well with -f234 -g567") are more than welcome, as we >> already know the colorimeter device type. > > Here is my experience with the Munki from my notes. I've used it > successfully to both profile a Dell U2410 LCD screen and an Epson > R2880. The LCD profiling should work already but I ended up using the > tools directly because g-c-m was failing to interact correctly with > the argyll tools when they asked to change the position of the device. > I think this has been fixed but haven't checked. I didn't have any such issues, so I guess this has been fixed for a while. > Anyway for the printing profiling my steps were: > > 1 - Generate a set of color patches > > $argyll-targen -f 900 -v -d2 -c -A.8 The -c option is very advanced, and requires a lot of logic in GCM in determining what the best previous profile actually was... Or it requires the user to select their best previous profile, and if they select the wrong profile (or GCM automatically selects the wrong profile) it all goes horribly wrong... So in the short run using preconditioning (-c) probably will do more harm than good... This could very well be reconsidered when GCM matures. The 900 patch count is probably way too high for default, since we don't want to waste 4 sheets of expensive paper _by default_. Especially since some packages of expensive paper come in per 10 sheets packages. We'd be wasting 40% :) Please remember the ColorMunki vendor software only uses 90 or so patches by default, so having 210/190 (1x A4/Letter) is a huge improvement... Thus far I've had excellent results using only 210 patches with no preconditioning, and it only requires a single sheet of paper. So I'd highly recommend to use this as default. Anything that requires more than a single sheet of paper should probably go in high quality/advanced mode... Also I'd recon we should not really talk about patch counts, but the amount of paper... For for A4 we would use 210/420/630/840/1050 patches, or for Letter 190/380/470/660? > To then actually generate the files to print: > > $ printtarg -t -v -iCM -pLetter printtarg has a -h option, which will generate smaller patches for the ColorMunki, which fits 210 patches onto A4 instead of 90 or so... This option basically shrinks the rows to a third size, so the ColorMunki is exactly as wide as 3 rows with the aperture exactly over the middle row. > 2. Print out the patches > > I printed the resulting tiff files with PhotoPrint. I believe it uses > Gutenprint directly to drive the printer and is the only solution I > know right now that can actually apply the ICC profile when printing > later. The important thing here is to set the Gutenprint setting > "Color Correction" to "Uncorrected", and then any of the image > settings for the setup being used (type of paper, resolution, > dithering, etc). Not everybody uses a gutenprint supported printer... :) It's basically possible to profile any application with any printer driver, as long as the app nor the printer driver do any dynamic transforms... Your case is very optimal... HPIJS for example does not have an uncorrected mode, but the output is static, so it can be profiled. I apply my printer profile in F-Spot, so I also used F-Spot to print my target images... In theory this should not be very relevant. > 3. Read back the patches > > $chartread > > Munki will need to first be set to the self calibrate position, then > to the profiling position and then run through each of the patch lines > in turn while pressing its button. chartread asks for each of the > lines and will ask for them again if there is any error. The interface > needs to expose this. The last version allows you to reread a patch > line at will. I wonder if it would be possible to have some kind of > idea of how good the reads were and advise the user to reread one of > the lines if it is found to not be too good. I don't think argyll does this yet... But it would be cool indeed... > 4. Generate the profile > > $ colprof -v -D"" -qm -S > -cmt -dpp Using -qm for 210 is an excellent default, but when we go into advanced mode with > 500 patches, we should probably use -qh. I've never used the -S -cmt -dpp options, so I highly doubt they are required... We shouldn't pass random arguments unless strongly indicated that we should. Otherwise we should trust Argyll's defaults... > This runs by itself without problems. The specific flags are arguable > of course. I'm curious as to how changing -q (quality) to high or > ultra changes the profile. Some considerations: Graeme highly discourages the ultra mode, in his words: ultra mode exists to prove that nothing above high is required. > - Some decent automatic naming would be nice > - Selecting the source profile would be nice too (defaulting to sRGB) > and possibly allowing the user to later generate the same profile with > another profile (e.g. AdobeRGB) as source might be useful. Huh? printer profiles usually use LAB as Profile Connection Space, this has nothing to do with sRGB/AdobeRGB. The pipeline: Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> printer native RGB/CMYK -> hpijs/gutenprint > - All the colprof settings can be changed without running the process > from the beginning again. I wonder if g-c-m should have the notion of > "Profiling runs" from which several actual profiles can be created. > This would solve the sRGB/AdobeRGB selection as well. I'd probably be against this too (at least for the short run). This will complicate the user interface (and GCM's codebase), and probably won't be used much by most people, so this is not in line with GNOME's goals. In the long run we could re-evaluate this... > - Colprof outputs a final result with the mean and maximum error of > the profile. It would be great to give this result to the user in > plain English. Telling him the profile is "Poor/Fair/Good/Excellent" > or even a result out of 100. That would be nice... I'd stick to Poor/Fair/Good/Excellent, everybody understands that. Though we need to be very careful about how we determine what is what. > The generated profile works in PhotoPrint. I assume it would also work > to transform an image before sending it to the general CUPS pipeline. > In theory the generated profile is only valid for the specific set of > settings used for the printer. In practice using the same profile on > even a different but similar paper is probably better than none at > all. And using it at a different resolution on the same paper may very > well be decent as well. I have no idea. > >> In particular, we need to support printing to 6x4 inch cards, A4 and >> letter paper. I would love to integrate this better with CUPS (using >> the GTK print dialog for instance) than what we can do on the command >> line. We'll also need scans of the patches sheets that we send out, so >> we can show the user _how_ to scan in the patches. We'll also probably >> need a timer for "waiting for the ink to dry" and that sort of thing. >From most sources I gather a minimum od 15 minutes of drying-time should be enough for most cases. > My only other comment about the process is that using the Munki with > default size patches is an incredible waste of paper and ink. In the > argyll mailing list someone pointed out some user's hack on dpreview > so I built one myself: > > http://pedrocr.net/MunkiHelper.jpg Are you actually aware of the -h option for printtarg? Graeme semi-solved this issue long ago... My current workflow is like this # argyll-targen -v -d 2 -g 20 -f 210 test # printtarg -v -i CM -h -t 300 -p A4 test # chartread -v test # colprof -v -A "bla" -M "bla" -D "bla" -C "bla" -a l -q m test Regards, Pascal de Bruijn From knizek.confy at volny.cz Thu Feb 18 18:46:34 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Thu, 18 Feb 2010 19:46:34 +0100 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> Message-ID: <1266518794.18345.36.camel@athlon> Pascal de Bruijn p??e v ?t 18. 02. 2010 v 18:57 +0100: > On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > > - Selecting the source profile would be nice too (defaulting to sRGB) > > and possibly allowing the user to later generate the same profile with > > another profile (e.g. AdobeRGB) as source might be useful. > > Huh? printer profiles usually use LAB as Profile Connection Space, > this has nothing to do with sRGB/AdobeRGB. > > The pipeline: > Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> > printer native RGB/CMYK -> hpijs/gutenprint It looks like Pedro was referring to -S option of colprof: Argyllcms docs quote [1]: -- Where the resulting profile will be used conventionally (ie. using collink -s, or cctiff or most other "dumb" CMMs) it is important to specify that gamut mapping should be computed for the output (B2A) perceptual and saturation tables. This is done by specifying a device profile as the parameter to the colprof -S flag. When you intend to create a "general use" profile, it can be a good technique to specify the source gamut as the opposite type of profile to that being created, i.e. if a printer profile is being created, specify a display profile (e.g. sRGB) as the source gamut. If a display profile is being created, then specify a printer profile as the source (e.g. SWOP). -- Argyllcms docs quote [2]: ... [Note that Shaper/Matrix profiles are always Colorimetric intent, since there is only a single transformation, and it does not have the necessary flexibility to accommodate gamut mapping.] ... So to construct the perceptual and saturation intent mapping tables, a source profile or source gamut needs to be specified, so that a gamut mapping can be constructed. -- [2] http://www.argyllcms.com/doc/Scenarios.html#PP5 [1] http://www.argyllcms.com/doc/iccgamutmapping.html I do not have much experience on this topic... regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Fri Feb 19 10:41:19 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 10:41:19 +0000 Subject: Help update Message-ID: <1266576079.2381.5.camel@localhost> Richard Attached is my first attempt to help. Sorry it has taken me so long but I had a lot of reading to do about Gnome documentation. I have only altered the Introduction and Usage sections. I will set about the other sections if this is acceptable. If anyone wants to tell me where I am going wrong then please do. I admit this little effort has made me realise just what Richard is doing! There is more to gcm than I expected. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Correct-help-Intro-and-Usage.patch Type: text/x-patch Size: 3064 bytes Desc: not available URL: From hughsient at gmail.com Fri Feb 19 11:02:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 11:02:43 +0000 Subject: Help update In-Reply-To: <1266576079.2381.5.camel@localhost> References: <1266576079.2381.5.camel@localhost> Message-ID: <15e53e181002190302r1ffa130ay22236854ce8574d3@mail.gmail.com> On 19 February 2010 10:41, Paul Finnigan wrote: > Attached is my first attempt to help. Sorry it has taken me so long but > I had a lot of reading to do about Gnome documentation. Sure, it takes a fair bit to get up to speed. > I have only altered the Introduction and Usage sections. I will set > about the other sections if this is acceptable. I've committed your patch, thanks. One thing to note (any maybe repair in your next patch :-) is the trailing whitespace issue. git doesn't like trailing whitespace (tabs and spaces at the end of the line) and highlights them in red. Could you please make sure future patches don't add more trailing whitespace please? Thanks. > If anyone wants to tell me where I am going wrong then please do. I > admit this little effort has made me realise just what Richard is doing! Heh. Thanks. > There is more to gcm than I expected. Sure, and it's getting bigger every day. To do the printer profiling properly I'm having to deal with print dialogs and rendering to random cairo surfaces. Both things that were not in the original scope for GCM... Anyway, keep up the good work. Thanks. Richard. From paul at fincc.com Fri Feb 19 12:48:30 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 12:48:30 +0000 Subject: Selecting Device Profiles Message-ID: <1266583710.2381.14.camel@localhost> Hi I was just looking at improving the preferences help page and I came across a small UI problem someone else may like to look at. If the device profile is not loaded you can select "Other profile..." this takes you to the profile install routine, via a Gnome file select window. That is good. But once the profile is installed I have to go back to the Color Profile selector and select it. I think what should happen is: 1. If the profile is good for the device it should be selected. 2. If the profile is not good for the device then a message should be issued and the device profile is unaltered. What should never happen is that the "Other profile" selection remains against the device. Another point is that for a new device the profile should be "None" rather than blank. This will keep it consistent with selecting None from the profile list. What does everyone else think? -- Paul Finnigan From hughsient at gmail.com Fri Feb 19 13:05:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 13:05:10 +0000 Subject: Selecting Device Profiles In-Reply-To: <1266583710.2381.14.camel@localhost> References: <1266583710.2381.14.camel@localhost> Message-ID: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> On 19 February 2010 12:48, Paul Finnigan wrote: > If the device profile is not loaded you can select "Other profile..." > this takes you to the profile install routine, via a Gnome file select > window. That is good. But once the profile is installed I have to go > back to the Color Profile selector and select it. That's just a bug: commit 5c4731bce32ce55467449d793b6a508b48b09eda Author: Richard Hughes Date: Fri Feb 19 13:03:14 2010 +0000 trivial: Set the profile we chose as 'Other' as the current device default > I think what should happen is: > > 1. If the profile is good for the device it should be selected. Sure, agreed. > 2. If the profile is not good for the device then a message should be > issued and the device profile is unaltered. We need to add that. > What should never happen is that the "Other profile" selection remains > against the device. What happens if the device chosen is unsuitable? Go back to the previous profile, or 'None'? Richard. From paul at fincc.com Fri Feb 19 13:15:29 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 13:15:29 +0000 Subject: Selecting Device Profiles In-Reply-To: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> References: <1266583710.2381.14.camel@localhost> <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> Message-ID: <1266585329.2381.16.camel@localhost> Richard On Fri, 2010-02-19 at 13:05 +0000, Richard Hughes wrote: > What happens if the device chosen is unsuitable? Go back to the > previous profile, or 'None'? > > Richard. I would suggest the previous profile. The warning can then say that the profile is unsuitable and the setting has not been altered. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Fri Feb 19 23:03:26 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 00:03:26 +0100 Subject: gcm-git not building (as package) Message-ID: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Hi, There are some trivial problems with gcm-git: cc1: warnings being treated as errors gcm-calibrate.c: In function 'gcm_calibrate_device': gcm-calibrate.c:654: error: unused variable 'dialog' make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Sat Feb 20 00:14:20 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:14:20 +0300 Subject: Small thumbnails of targets In-Reply-To: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> Message-ID: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> On 2/10/10, Lars Tore Gustavsen wrote: >> This would be a great way to help out gnome-color-manager if you are >> not comfortable with coding. The list of target types I need as >> thumbnails are: >> >> CMP_Digital_Target-3 >> CMP_DT_003 >> ColorChecker >> ColorCheckerDC >> ColorCheckerSG >> Hutchcolor >> i1_RGB_Scan_1.4 Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) Alexandre From alexandre.prokoudine at gmail.com Sat Feb 20 00:10:43 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:10:43 +0300 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <733f2c731002191610q5bea9bd2l347287afcf42abc9@mail.gmail.com> On 2/17/10, Richard Hughes wrote: > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Just in case, make sure you've seen GPLin (http://bit.ly/aTmim3). Maybe it has some useful code for you. Alexandre From pedro at pedrocr.net Fri Feb 19 21:01:20 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 19 Feb 2010 13:01:20 -0800 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> Message-ID: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> (I'm CC'ing this to the list to keep the discussion there, hope it's ok) On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > Some applications (even commercial ones) don't support LUT display > profiles properly. > > Argyll can generate Matrix+LUT profiles, but then you have the problem > that one app uses the matrix and the other the LUT, this can give odd > inconsistencies... So it's not recommended for defaults... Makes sense. Do you know if I'll be ok with a LUT using GIMP/f-spot/ufraw? I should probably try g-c-m again to see what profile it comes up with. When I did the LUT one with 2000 patches the result seemed to have a fair amount of extra contrast that looked good. Don't know where that came from. > This is true, however, 210 is already a _big_ improvement over 90... Sure. Although I need to test it again as it was too little for me before. But here is Graeme Gill's opinion on number of needed patches (600-1000 for a "well-behaved" printer): http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,22 I guess this one is easy to expose to the user by asking him how many sheets to print. > Please also note, that you're passing all kinds of options with > unknown effects... I just passed the options recommended by argyll itself (the mailing list and the docs). > Please try again with exactly the options I gave... > > Also make sure you have an up to date version of Argyll (1.1.0-final)... Yes, this I did use in the last run but not the previous ones, so that could be the problem with 210 patches. > -q has little do to with actual quality with LUT profiles, it has to > do with detailedness of the generated profiles... Generating a high > detail profiles with low patches seems silly at best. Makes sense, thanks. >> Again the scenarios and the mailing list tell us to use a source >> profile. Milan had an explanation for it. > > Do you have a reference for that? Sure. Here are the docs: http://www.argyllcms.com/doc/Scenarios.html#PP5 And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try different profiles there: http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 It could be that we can actually get away without -S for a decent default. We should probably start a thread in the argyll mailing list about what to use as sensible defaults for profiling printers (and monitors/scanners/cameras too maybe). > We aren't catering to the masses... But even advanced hobby > photographers and professional photographers see color management as a > necessary evil, and most don't want to bother with patch counts and > all kinds of settings, they just want a reasonable match by clicking > on "Next" a couple of times... Yes, I agree completely. My point wasn't that the GUI shouldn't start as a straight-through "get a decent enough profile and be done with it". I was just arguing that the user shouldn't be dumped into learning all these argyll command line options every time he wants to do something even moderately advanced. > Again, the big question would be how often you _really need_ the > advanced settings... Liking to fiddle with them and needing them are > two different things... > > Trying to control to much was a mistake I made in the past as well, > sticking to Argyll's defaults has generally improved my results. I totally agree there. Only settings that are actually needed should be exposed. I don't yet know what those are though considering all the advice to fiddle with different settings I got from the argyll list. Maybe most of that advice can actually be the default and not need changing. >> I think the underlying assumption behind telling users who want >> advanced stuff to go to the argyll tools is that someone that wants >> advanced calibration/color in Linux is also an advanced Linux user. >> Whereas in reality it would be good to be able to support advanced >> photographers/artists that are also non-geek computer users. It's an >> uphill battle right now with GIMP not supporting 16-bit images, f-spot >> not very complete and raw converters still not particularly good. >> We're advancing in all three fronts though and g-c-m is a much needed >> complement. > > Patience is key here... No doubt. I wouldn't be using Linux to do photography work if I wasn't happy to put up with and work around the shortcomings. >> why -g? > > Adds greyscale patches. So why deviate from the argyll standard there? This one didn't get mentioned in my thread. Is it to improve the tone curve for B&W printing? >>> # printtarg -v -i CM -h -t 300 -p A4 test >> >> Does -t 300 help? I was getting some non-sharp edges on my patches >> maybe it was because of this. > > This doesn't particularly matter much, you're not measuring the edges. I wasn't too worried about it although I guessed it could mess up the patch detection and maybe sometimes interfere with a reading, especially when using the smaller patches. Cheers, Pedro From knizek.confy at volny.cz Sat Feb 20 08:15:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 09:15:14 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266653714.2961.28.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). > I completely agree to get some hints from argyllcms mailing list users. Also, sooner or later, GCM would need to solve the problem of a general photographer (I do not want to know how things work but still want my pictures nicely printed). A good example is here: http://photo.net/digital-darkroom-forum/00ViCO William Palmer wonders what to do to solve the problem that printed images look fine on direct sun-light, but when hanged on the wall inside, they look "dark". At the end, Andrew Rodney mentions some "advanced profiling solutions", which can compensate for different viewing conditions, but William does not get the point (which is understandable). That is what ArgyllCMS takes care by -c and -d parameters for colprof: -- Since appearance space is used in the gamut mapping (just as it is in collink), the viewing conditions for the source and destination colorspaces should really be specified. The source colorspace is the profile specified with the -s or -S flag, and the destination is the profile being created. The -c and -d options allow specification of their respective, associated viewing conditions. The viewing condition information is used to map the profile PCS (Profile Connection Space, which us either XYZ or L*a*b*) color into appearance space (CIECAM02), which is a better colorspace to do gamut mapping in. The viewing conditions allow the conversion into appearance space to take account of how color will be seen under particular viewing conditions. -- I do also not think that exposing the colprof parameters to a user is a good idea. Nonetheless, how about asking the user - "Will your print be viewed in a dim light environmnet?" "Will it hang in a room well lit by daylight?") And similarly for "-g" paramater of targen: "Do you print black and white photographs and want a higher emphasise on grey neutrality then on colour fidelity?" Using such questions, the user could be navigated to get a good profile for his own use. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 20 08:44:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 20 Feb 2010 08:44:50 +0000 Subject: gcm-git not building (as package) In-Reply-To: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> References: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Message-ID: <15e53e181002200044j180d4e97kf865fb3054fd2092@mail.gmail.com> On 19 February 2010 23:03, Pascal de Bruijn wrote: > cc1: warnings being treated as errors > gcm-calibrate.c: In function 'gcm_calibrate_device': > gcm-calibrate.c:654: error: unused variable 'dialog' > make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 commit 8c711eb8ba43a8bad65d7f45899859b3ed7fdc81 Author: Richard Hughes Date: Sat Feb 20 08:43:38 2010 +0000 trivial: fix compile from git master when compiling without PackageKit Richard. From pmjdebruijn at pcode.nl Sat Feb 20 11:45:23 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 12:45:23 +0100 Subject: Small thumbnails of targets In-Reply-To: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> Message-ID: <4c2c37f91002200345l1a221c69tb8612a35b5c0ff26@mail.gmail.com> On Sat, Feb 20, 2010 at 1:14 AM, Alexandre Prokoudine wrote: > On 2/10/10, Lars Tore Gustavsen wrote: > >>> This would be a great way to help out gnome-color-manager if you are >>> not comfortable with coding. The list of target types I need as >>> thumbnails are: >>> >>> CMP_Digital_Target-3 >>> CMP_DT_003 >>> ColorChecker >>> ColorCheckerDC >>> ColorCheckerSG >>> Hutchcolor >>> i1_RGB_Scan_1.4 > > Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) IT8 = IT8, doesn't really matter which vendor... At least it shouldn't it think... Regards, Pascal de Bruijn From knizek.confy at volny.cz Sat Feb 20 16:58:55 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 17:58:55 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266685135.5298.5.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > >> Again the scenarios and the mailing list tell us to use a source > >> profile. Milan had an explanation for it. > > > > Do you have a reference for that? > > Sure. Here are the docs: > > http://www.argyllcms.com/doc/Scenarios.html#PP5 > > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). How about using the RGB working colourspace, which is set in GCM defaults tab, for -S colour space? We can assume that majority of the images would be in that space. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Mon Feb 22 12:16:11 2010 From: paul at fincc.com (Paul Finnigan) Date: Mon, 22 Feb 2010 12:16:11 +0000 Subject: Updated Help Text Message-ID: <1266840971.2539.8.camel@localhost> Richard I have amended the text around the preferences and advanced preferences sections of the help file. I have included (but not altered) the text you said should go in about gamma. The text is not perfect but I think that it is better than what was there. I cannot alter the section on Calibration as I do not have the hardware to check out the interface yet (gcm is the first software that made me want to buy it!). If anyone has anything to add to the help files but does not want to update them then just let me know. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-Help-Preferences-Text.patch Type: text/x-patch Size: 7012 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 22 12:31:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:31:50 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220431j4a0f4c37lce0c558756c98d7e@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > The text is not perfect but I think that it is better than what was > there. Agreed, thanks. I've applied it with minor changes. You also need to set your email address so git formatted patches display the right email (and so lazy me can just use git am). To do this, just set export GIT_AUTHOR_EMAIL=dave at dave.com in ~/.bash_profile for future patches. Thanks! Richard. From hughsient at gmail.com Mon Feb 22 12:38:59 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:38:59 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > If anyone has anything to add to the help files but does not want to > update them then just let me know. In particular, we need lots more FAQ entries filled out: * What colorimeter devices are supported * What target types are supported? * Where do I purchase targets from? * How do I get a profile from my display vendor * How do I get a reference image using a digital camera? * ...lots of other details about color management.... If you're scared by docbook and git, then just submit some prose to the mailing list, and one of the other contributors can format it up and submit a patch on your behalf. Thanks, Richard. From alexandre.prokoudine at gmail.com Mon Feb 22 13:43:41 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 22 Feb 2010 16:43:41 +0300 Subject: Updated Help Text In-Reply-To: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> References: <1266840971.2539.8.camel@localhost> <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> Message-ID: <733f2c731002220543x3c160251v4a546c11e44a7210@mail.gmail.com> On 2/22/10, Richard Hughes wrote: > In particular, we need lots more FAQ entries filled out: > > * What colorimeter devices are supported Committed > * What target types are supported? Committed > * Where do I purchase targets from? Committed Alexandre From hughsient at gmail.com Mon Feb 22 14:46:19 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 14:46:19 +0000 Subject: ColorMunki works Message-ID: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> My ColorMunki arrived this morning, and I've just committed quite a few patches to make it work calibrating the screen. There are still quite a few rough edges we need to fix (hardcode) but it basically works. Now I'm going to move onto adding initial printing support, although this might take a couple of weeks. Richard. From pmjdebruijn at pcode.nl Mon Feb 22 17:22:37 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 22 Feb 2010 18:22:37 +0100 Subject: ColorMunki works In-Reply-To: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> References: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> Message-ID: <4c2c37f91002220922m77984a56o1c441985dbc9d099@mail.gmail.com> On Mon, Feb 22, 2010 at 3:46 PM, Richard Hughes wrote: > My ColorMunki arrived this morning, and I've just committed quite a > few patches to make it work calibrating the screen. There are still > quite a few rough edges we need to fix (hardcode) but it basically > works. Now I'm going to move onto adding initial printing support, > although this might take a couple of weeks. Indeed it does, there are some cosmetic issues though: https://bugzilla.gnome.org/show_bug.cgi?id=605856 I'm looking forward to the printer stuff, especially the CUPS integration, it would severely kick ass if there would be an extra CUPS Color Management tab, on which output color profiles could be specified. Regards, Pascal de Bruijn From knizek.confy at volny.cz Mon Feb 22 20:51:30 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 21:51:30 +0100 Subject: Make default - what is it supposed to do? Message-ID: <1266871890.982.23.camel@athlon> Hello, what is the expected behaviour of "Make Default" button in gcm-prefs? The notification message reads "Save these profiles for all users", but after pressing it I can see the verbose output reading: - running: pkexec /usr/sbin/gcm-install-system-wide --id xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" Content type was incorrect: application/octet-stream It tries to install the monitor profile, however, I also have a webcam profile set. And as far as I can tell, nothing happens. The profile is not copied to /usr/share/color/... or /usr/local/share/color/... locations, I cannot find anything useful in /etc/... or /var/lib/... and starting a session of a different user does not show any profile set in gcm-prefs. Is this is a bug or not-yet-implemented thing? Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 22 21:11:25 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 23 Feb 2010 00:11:25 +0300 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> On 2/22/10, Milan Kn??ek wrote: > Hello, > > what is the expected behaviour of "Make Default" button in gcm-prefs? http://www.libregraphicsworld.org/articles.php?article_id=11 "To make your preferences available to all users of a system you can use the Make Default button in the bottom of the dialog. What it will do is ask for superuser password and copy all the active display profiles to a system-wide directory (/var/lib/color) where the new filename matches the device-id. So when a new user logs in, if there is no device-profiles entry for the device, the system-wide profile is used." Alexandre From knizek.confy at volny.cz Mon Feb 22 22:07:42 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 23:07:42 +0100 Subject: Make default - what is it supposed to do? In-Reply-To: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> References: <1266871890.982.23.camel@athlon> <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> Message-ID: <1266876462.20402.8.camel@athlon> Alexandre Prokoudine p??e v ?t 23. 02. 2010 v 00:11 +0300: > On 2/22/10, Milan Kn??ek wrote: > > Hello, > > > > what is the expected behaviour of "Make Default" button in gcm-prefs? > > http://www.libregraphicsworld.org/articles.php?article_id=11 > > "To make your preferences available to all users of a system you can > use the Make Default button in the bottom of the dialog. What it will > do is ask for superuser password and copy all the active display > profiles to a system-wide directory (/var/lib/color) where the new > filename matches the device-id. So when a new user logs in, if there > is no device-profiles entry for the device, the system-wide profile is > used." > Then it seems to be a bug - on two computers (same system though - Ubuntu 9.10 amd64) the directory /var/lib/color exists, but it remains empty. Authorisation seems to be okay, I also tried to run with sudo and as root in console - no success, just the error message: Content type was incorrect: application/octet-stream regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Mon Feb 22 23:17:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 23:17:13 +0000 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <15e53e181002221517t65dc049aqccb1f4580470e478@mail.gmail.com> On 22 February 2010 20:51, Milan Kn??ek wrote: > ?- running: pkexec /usr/sbin/gcm-install-system-wide --id > xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" > Content type was incorrect: application/octet-stream Looks like your version of shared-mime-info is too old. We can't do the .icc/.icm fallback in this case as gcm-install-system-wide is running as root as we have to be careful of maliciously created profiles. > Is this is a bug or not-yet-implemented thing? The former :-) Richard. From hughsient at gmail.com Tue Feb 23 14:21:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 14:21:39 +0000 Subject: Blog post about GCM Message-ID: <15e53e181002230621t76746c6elb9c4dcc2344b59c@mail.gmail.com> I've made a blog post about GCM that some of you might find interesting: http://blogs.gnome.org/hughsie/2010/02/23/gnome-color-manager-and-printer-profiling/ Good job on the documentation file btw, it's coming along nicely now. Richard. From hughsient at gmail.com Tue Feb 23 15:50:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 15:50:21 +0000 Subject: Strategic direction Message-ID: <15e53e181002230750r1b8414a2l2503a7079cfd4f2d@mail.gmail.com> Big ideas I think we need to work towards: * Assigning more than one profile to a device[1] (and having one default profile per device) * Having virtual devices that we can't connect, for instance "Bob's Photo Processing Shop" Any one got any more ideas? Richard. [1] The DBus API already supports this, although it only ever returns one profile. From pmjdebruijn at pcode.nl Tue Feb 23 17:44:13 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 18:44:13 +0100 Subject: New print profiling functionality Message-ID: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Hi, I just tried the brand spanking new print profiling functionality... And of course there's something to bitch about... * It only generated 45 patches, while on A4 I can fit 210 ColorMunki patches in double density mode (-h). * Some patches got clipped (because of margins), because the generated image isn't centered (or it is getting stretched for no reason, since the generated image doesn't include margins). * The generated image is pretty low resolution, the text looks like crap, consider (printtarg -T 200 or 300)? * GCM should not report "reading the patches" during self-calibration, we need a seperate dialog for this! Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 23 17:51:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 17:51:53 +0000 Subject: New print profiling functionality In-Reply-To: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Message-ID: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> On 23 February 2010 17:44, Pascal de Bruijn wrote: > I just tried the brand spanking new print profiling functionality... > And of course there's something to bitch about... Heh, good. :-) > * It only generated 45 patches, while on A4 I can fit 210 ColorMunki > patches in double density mode (-h). Right, this is something I need help with. How many patches do we use for quick, normal and slow profiling? I'm already using -h for ColorMunki. > * Some patches got clipped (because of margins), because the generated > image isn't centered (or it is getting stretched for no reason, since > the generated image doesn't include margins). Ahh, I'm just blitting it to the cairo surface, without preserving aspect. I guess we need to do that. I'm using gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > * The generated image is pretty low resolution, the text looks like > crap, consider (printtarg -T 200 or 300)? Hmm, it should already be using 300DPI thanks to the -t300 option. > * GCM should not report "reading the patches" during self-calibration, > we need a seperate dialog for this! Sure, I can't get my ColorMunki to self calibrate using chartread (see the Argyll m/l) so I've not tested past this point. Richard. From hughsient at gmail.com Tue Feb 23 20:20:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 20:20:13 +0000 Subject: New print profiling functionality In-Reply-To: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> Message-ID: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> On 23 February 2010 17:51, Richard Hughes wrote: > Ahh, I'm just blitting it to the cairo surface, without preserving > aspect. I guess we need to do that. I'm using > gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. I've done the scaling in cairo now; see below. >> * The generated image is pretty low resolution, the text looks like >> crap, consider (printtarg -T 200 or 300)? > > Hmm, it should already be using 300DPI thanks to the -t300 option. I've just pushed a commit to do the scaling in cairo, rather than GDK, which makes it look much better. Richard. From pmjdebruijn at pcode.nl Tue Feb 23 22:22:30 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:22:30 +0100 Subject: New print profiling functionality In-Reply-To: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> Message-ID: <4c2c37f91002231422g6836f6e5s1a7ff1a8db4e8c7f@mail.gmail.com> On Tue, Feb 23, 2010 at 9:20 PM, Richard Hughes wrote: > On 23 February 2010 17:51, Richard Hughes wrote: >> Ahh, I'm just blitting it to the cairo surface, without preserving >> aspect. I guess we need to do that. I'm using >> gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > > I've done the scaling in cairo now; see below. > >>> * The generated image is pretty low resolution, the text looks like >>> crap, consider (printtarg -T 200 or 300)? >> >> Hmm, it should already be using 300DPI thanks to the -t300 option. > > I've just pushed a commit to do the scaling in cairo, rather than GDK, > which makes it look much better. Actually, since you're using cairo, which is very vector-aware, right? Wouldn't it make sense to use the EPS output (printtarg -e). Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 23 22:28:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:28:50 +0100 Subject: Printshop calibration/profiling Message-ID: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Hi, Another thing I noticed, is the very cool dialog which also allows you to profile printshops, however I can only get to this dialog whenever I have a printer in GCM, and the spectrophotometer connected, even though I only want to generate a chart to send to my printshop. This is not a huge problem, more of a nuisance... Maybe it's a thought to create a "Printshop" virtual device? Honestly I'm not sure that's a much better solution, since sooner or later we'll end up with 100 by default created virtual devices for all kinds of corner cases... This message is mainly intended to get a discussion going... Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Tue Feb 23 22:32:52 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Wed, 24 Feb 2010 01:32:52 +0300 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <733f2c731002231432j6144ec13h1ffd278e038064c0@mail.gmail.com> On 2/24/10, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... This is not a huge problem when you have a printer. Well, I don't have one :) Alexandre From hughsient at gmail.com Tue Feb 23 22:33:36 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 22:33:36 +0000 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <15e53e181002231433j2138420bg216e2efe3d84ad3c@mail.gmail.com> On 23 February 2010 22:28, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... Sure, agreed. > Maybe it's a thought to create a "Printshop" virtual device? Honestly > I'm not sure that's a much better solution, since sooner or later > we'll end up with 100 by default created virtual devices for all kinds > of corner cases... I do think we need virtual devices. It's bad usability, as you have to enter everything manually, but a useful thing for power users. Richard. From pmjdebruijn at pcode.nl Wed Feb 24 22:06:08 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 24 Feb 2010 23:06:08 +0100 Subject: Double Density Mode for ColorMunki Message-ID: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Hi, To my dismay I noticed you've dropped the double density mode for the ColorMunki. What would be the problem with this? Maybe I can help? Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 08:43:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 08:43:34 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Message-ID: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> On 24 February 2010 22:06, Pascal de Bruijn wrote: > To my dismay I noticed you've dropped the double density mode for the > ColorMunki. What would be the problem with this? Maybe I can help? I just couldn't get double density to work correctly. Maybe I'm clumsy or something, but the single density was much easier to scan. Perhaps we can just have it as a simple dialog choice? ________________________________ Target Choice ________________________________ Your calibration device can use much smaller sized squares to save on paper and ink, although it will be harder to use the device. Enable double density mode? [Help] [No] [Yes] ________________________________ Richard. From pmjdebruijn at pcode.nl Thu Feb 25 10:58:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 25 Feb 2010 11:58:38 +0100 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> Message-ID: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> On Thu, Feb 25, 2010 at 9:43 AM, Richard Hughes wrote: > On 24 February 2010 22:06, Pascal de Bruijn wrote: >> To my dismay I noticed you've dropped the double density mode for the >> ColorMunki. What would be the problem with this? Maybe I can help? > > I just couldn't get double density to work correctly. Maybe I'm clumsy > or something, but the single density was much easier to scan. I'm guessing you didn't print it at proper scale... In double density mode, three rows are exactly as wide as the ColorMunki, so the rows themselves can be used as a visual guide. And because the patches are smaller you need to scan a bit slower. > Perhaps we can just have it as a simple dialog choice? No that's silly... Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 11:36:33 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 11:36:33 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> Message-ID: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> On 25 February 2010 10:58, Pascal de Bruijn wrote: > I'm guessing you didn't print it at proper scale... Well, argyll formats it as a single page tiff file, so I'm pretty sure I did. I've attached a photo to show you the pages. > In double density mode, three rows are exactly as wide as the > ColorMunki, so the rows themselves can be used as a visual guide. And > because the patches are smaller you need to scan a bit slower. Right, maybe I'm just a bit clumsy. >> Perhaps we can just have it as a simple dialog choice? > > No that's silly... Agreed. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: double-density.jpg Type: image/jpeg Size: 23813 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 25 12:07:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 12:07:28 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> Message-ID: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> On 25 February 2010 11:36, Richard Hughes wrote: > Right, maybe I'm just a bit clumsy. I've found I can use the double density scan 99% correctly, if I rotate the page and "push" the colormunki away from me. If I try to scan from left to right then it only works 10% of the time. I'll do you deal. I'll re-instate the double density feature (with extra love) if you write a section in the help file on how to scan in a target, with tips. :-) Deal? Richard. From pedro at pedrocr.net Thu Feb 25 21:10:18 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 25 Feb 2010 13:10:18 -0800 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> Message-ID: <62e8012c1002251310t6c02124cnd3f62db919b2b5dd@mail.gmail.com> On Thu, Feb 25, 2010 at 4:07 AM, Richard Hughes wrote: > I'll do you deal. I'll re-instate the double density feature (with > extra love) if you write a section in the help file on how to scan in > a target, with tips. :-) If I write a section for the manual on how to build and use the simple guide rules to use the munki with EyeOne targets can we get that mode too? In my experience it makes scanning much simpler than even normal density patches freehand and the guide takes 5 minutes and only basic supplies to build. If someone was selling an after-market solution for this I assume no one would have a problem with it so I don't see why a home-made one isn't fine as well. It would at least be nice if the instrument definitions were setup in config files for each instrument so that even if you don't want to have this in mainline people could hack together their own config files and still take advantage of the g-c-m UI. Pedro From hughsient at gmail.com Mon Feb 1 11:05:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 1 Feb 2010 11:05:13 +0000 Subject: GNOME Color Manager 2.29.3 Message-ID: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> gnome-color-manager is a session program that makes it easy to manage, install and generate color profiles in the GNOME desktop. Version 2.29.3 ~~~~~~~~~~~~~~ Released: 2010-02-01 * Translations - Added Italian translation (Francesco Groccia) - Updated Danish translation (Joe Hansen) - Updated French translation (Claude Paroz) - Updated German translation (Mario Bl?ttermann) - Updated Norwegian bokm?l translation (Kjartan Maraas) - Updated Portuguese translation (Ant?nio Lima) - Updated Russian translation (Alexandre Prokoudine) - Updated Slovenian translation (Andrej ?nidar?i?) - Updated Swedish translation (Daniel Nylander) * New Features: - Enable the rendering intent and default colorspace UI elements (Richard Hughes) - Show whether the ICC profile has a VCGT tag in the UI (Richard Hughes) - Filter out non RGB and CMYK color space profiles from the combo-boxes using a heuristic (Richard Hughes) - Add a new DBus method GetProfileForWindow which can return a profile for a supplied XID (Richard Hughes) - Add some new text and tooltips to the prefs dialog (Richard Hughes) - Add per-user OSX ICC profiles at startup (Richard Hughes) - Add OSX and Windows ICC profiles if they exist from mounted volumes. Fixes #607390 (Richard Hughes) - Add a device profile entry of 'Other profile...' to be able to easily import a profile. Fixes #607389 (Richard Hughes) - Add a precision GConf variable to control the time a calibration takes. Fixes #605558 (Richard Hughes) - Screenscrape the Argyll output to better support other hardware devices. Fixes #605558 (Richard Hughes) - Do not show the 'Fine tuning' expander by default, and have configuration in GConf (Richard Hughes) * Bugfix: - Zero out GErrors after freeing. Fixes crash (Christian Hergert) - Add gnome-desktop path as fallback for pci.ids (Frederic Crozat) - Do not generate an error if a display profile does not have CLUT data (Richard Hughes) - Add gcm-fix-profile to load and then re-save existing profiles using lcms (Richard Hughes) - Fix compile when using an ld that defaults to --as-needed (Richard Hughes) - Do not allow the colorspace combobox to be zero sized. Fixes #606484 (Richard Hughes) - Make gcm-prefs a normal dialog rather than a modal dialog (Richard Hughes) - Only scan ICC locations with hfs partition types for OSX and msdos/NTFS types for Windows (Richard Hughes) - Make gcm-prefs startup a few hundred ms quicker by not loading the list of screens (Richard Hughes) - Cache gnome_rr_screen_new and take 0.7 seconds off the start time (Richard Hughes) - Don't resize the window on startup. Fixes #607391 (Richard Hughes) - Update the Free Software Foundation address (Richard Hughes) Richard. From pmjdebruijn at pcode.nl Mon Feb 1 18:29:31 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 1 Feb 2010 19:29:31 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> Message-ID: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > gnome-color-manager is a session program that makes it easy to manage, install > and generate color profiles in the GNOME desktop. > > Version 2.29.3 > ~~~~~~~~~~~~~~ > Released: 2010-02-01 As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's available on my gcm-release PPA: https://launchpad.net/~pmjdebruijn/+archive/gcm-release ArgyllCMS 1.1.0 is also available on my argyll-release PPA, to complement GNOME Color Manager: https://launchpad.net/~pmjdebruijn/+archive/argyll-release Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 5 12:55:32 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 13:55:32 +0100 Subject: Information re. display gamma Message-ID: <1265374532.31703.61.camel@athlon> Hello, while translating the gcm, I spotted the following: -- Gamma is adjusted to affect the color of the attached monitor. Traditionally Linux has used a gamma value of 1.0, but this makes monitors look washed out compared Windows XP or OS X. Apple traditionally used a value of 1.8 for a long time, but now use the same value as Microsoft. Microsoft has always used a value of 2.2. -- Where does the information that Linux has used a gamma of 1.0 come from? I would assume it is a wrong interpretation of technical data. Both Mac/Win tools prefer to tell the user the final viewing gamma (which is a combination of gamma adjustment in LUT of graphics card and of the monitor's native gamma). These tools expect that the monitor native gamma is 2.2 (which is close to sRGB). In the past, Mac monitors had native gama 1.8. Linux tools - like xgamma and gcm - instead tell the number, which is applied to LUT only. Note that the final viewing gamma is equal to monitor's native gamma divided by LUT gamma. In other words, an image (untagged by ICC profile) displayed in Windows and Linux will appear the same, provided that the same video card and monitor is used and no colour management/calibration is applied. This is also the reason, why display ICC profiles created in Windows can be used in Linux. If the information quoted above remains, users will be confused and try to set gamma 2.2 in gcm. I would propose to change the text so that it is clear that the user can correct the monitor's native gamma and that it is not the final viewing gamma. Or am I wrong? Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Fri Feb 5 13:32:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 5 Feb 2010 13:32:12 +0000 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> On 5 February 2010 12:55, Milan Kn??ek wrote: > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. That sounds about right to me. Feel free to change it so it's clearer. Thanks. Richard. From knizek.confy at volny.cz Fri Feb 5 20:09:20 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:09:20 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> Message-ID: <1265400560.29899.18.camel@athlon> Pascal de Bruijn p??e v Po 01. 02. 2010 v 19:29 +0100: > On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > > gnome-color-manager is a session program that makes it easy to manage, install > > and generate color profiles in the GNOME desktop. > > > > Version 2.29.3 > > ~~~~~~~~~~~~~~ > > Released: 2010-02-01 > > As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's > available on my gcm-release PPA: > > https://launchpad.net/~pmjdebruijn/+archive/gcm-release Is it an expected change in this release that the "fine tuning" option on the main screen of gcm-prefs disappeared? regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From knizek.confy at volny.cz Fri Feb 5 20:39:06 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:39:06 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> Message-ID: <1265402346.29899.48.camel@athlon> Richard Hughes p??e v P? 05. 02. 2010 v 13:32 +0000: > On 5 February 2010 12:55, Milan Kn??ek wrote: > > I would propose to change the text so that it is clear that the user can > > correct the monitor's native gamma and that it is not the final viewing > > gamma. > > That sounds about right to me. Feel free to change it so it's clearer. Thanks. > > Richard. > I will look at the text and propose a new wording. Additionally, it may also be helpful to update the "fine tuning" gamma slider. The slider has "hooks" for 1.8 and 2.2 -this would make sense if the user had a monitor with native gamma value of 1. Then, setting the slider to 2.2 would result in viewing gamma value of 2.2. This probably would not be the case for anyone. Hence, removing the "hooks" would help avoiding confusion. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Sat Feb 6 02:10:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 06 Feb 2010 13:10:48 +1100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <4B6CCFA8.3000107@argyllcms.com> Milan Kn??ek wrote: > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple Sounds bogus. Unix machines have "traditionally" used RGB encoded for display on a typical native CRT gamma. Linux is no different - "traditionally" raw RGB numbers have been sent to the monitor, and you get native CRT gamma or an emulation of it if it's an LCD monitor, so the encoding is notionally set for a gamma of 2.2. But there are exceptions - SGI's had a different scheme, and people creating synthetic images (CGI) have often left their images linear light, and expect the display process to counteract the displays natural gamma, even though this introduces quantization problems if they use 8 bits. > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. Note a couple of things: Latest OS X (10.6 "Snow Leopard") has a default of 2.2, but it seems that "1.8" of the Mac mac prior to this is actually a misnomer, the encoding is actually closer to 1/1.72, which is corrected by a framebuffer ramp of 1/1.45 for display on a CRT of 2.5, giving an overall system gamma of 1.0. Real CRT's have a gamma of nearer 2.4 - 2.5 (although such numbers are very sensitive to the setting of the black level). "Traditionally" from the TV world, material is broadcast with a gamma of 0.45 (ie. 1/2.22) with the expectation that it will be displayed on a monitor that has a gamma of 2.5, the discrepancy applying a viewing conditions transform that accounts for the different appearance between the bright TV studio lighting and the usually dim viewing conditions use with a CRT monitor. For all the details please refer to Charles Poynton's book "Digital Video and HDTV". > Linux tools - like xgamma and gcm - instead tell the number, which is > applied to LUT only. Note that the final viewing gamma is equal to > monitor's native gamma divided by LUT gamma. Right, and the final overall gamma should be 1.0, or (allowing for the viewing condition transform, about 1.1 - 1.2). > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. > > Or am I wrong? Most people are unfamiliar with the concept of overall system gamma. They might easily confuse the encoding gamma, display gamma and system gamma. The distinction between encoding gamma and display gamma is probably lost on most people too (strictly speaking the encoding gamma for "2.2" is 1/2.2 which is about 0.45, and the overall gamma is the product of the encoding gamma and the display gamma.) I think that if this is a display calibration application, then really it should talk about what the display is being set to, and could indicate how this corresponds to the encoding expectation. So typically a CRT display in a dim viewing environment should be calibrated to have a gamma of about 2.4, with the expectation that it is being fed material that has been encoded with a gamma of 1/2.2. If the display is brighter and in a brighter environment, then a calibration gamma of < 2.4 might be desirable, for the same 2.2 gamma encoded material. Graeme Gill. Graeme Gill. From knizek.confy at volny.cz Sat Feb 6 10:39:03 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 06 Feb 2010 11:39:03 +0100 Subject: Information re. display gamma In-Reply-To: <4B6CCFA8.3000107@argyllcms.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> Message-ID: <1265452743.22070.45.camel@athlon> Graeme Gill p??e v So 06. 02. 2010 v 13:10 +1100: > I think that if this is a display calibration application, then > really it should talk about what the display is being set to, and > could indicate how this corresponds to the encoding expectation. > This means that the GCM would have to change a bit more: GCM must know what the native monitor gamma is. Such an information can be taken from the ICC profile, either supplied by the user, created with GCM and colorimeter or created with GCM and "eye-measured" calibration. The lack of eye-measured calibration is already reported as bug 605019 https://bugzilla.gnome.org/show_bug.cgi?id=605019 which also refers to a tutorial how ColorSync on Mac did it: http://www.computer-darkroom.com/colorsync-display/colorsync_2.htm regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 6 11:46:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 11:46:06 +0000 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <1265400560.29899.18.camel@athlon> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> <1265400560.29899.18.camel@athlon> Message-ID: <15e53e181002060346u2d547bb1g7d6c1cd01ccff1ae@mail.gmail.com> On 5 February 2010 20:09, Milan Kn??ek wrote: > Is it an expected change in this release that the "fine tuning" option > on the main screen of gcm-prefs disappeared? Yes. There's a GConf key to re-enable it if you need the UI, but it's hidden by default until we make the UI nicer to use. It's on my TODO, but didn't quite make the release. New contributors welcome! :) Richard. From j at jonathanleighton.com Sat Feb 6 12:29:46 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Sat, 06 Feb 2010 12:29:46 +0000 Subject: ColorVision Spyder Message-ID: <1265459386.23788.9.camel@tybalt> Hi there, I have a ColorVision Spyder colorimeter. I have just been trying out gnome-color-manager (very impressive!) but the calibration buttons are disabled, even when I plug in my colorimeter. Do I need to take additional steps to use the colorimeter through GCM, or is the support just not there yet or something? Many thanks, Jon PS. Please CC me in replies - I'm not on the list. From hughsient at gmail.com Sat Feb 6 15:55:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:55:31 +0000 Subject: Information re. display gamma In-Reply-To: <1265452743.22070.45.camel@athlon> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> Message-ID: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> On 6 February 2010 10:39, Milan Kn??ek wrote: > This means that the GCM would have to change a bit more: GCM must know > what the native monitor gamma is. We can do this, but in my experience the EDID data from the monitor is wrong more often than it's right... Richard. From hughsient at gmail.com Sat Feb 6 15:57:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:57:50 +0000 Subject: ColorVision Spyder In-Reply-To: <1265459386.23788.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> Message-ID: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> On 6 February 2010 12:29, Jon Leighton wrote: > I have a ColorVision Spyder colorimeter. I have just been trying out > gnome-color-manager (very impressive!) but the calibration buttons are > disabled, even when I plug in my colorimeter. What version ArgyllCMS do you have installed? If it's less than 1.1.0 you'll need to add --disable-hardware-detection to ./configure -- it also only works for display devices for now (patches welcome!). > Do I need to take additional steps to use the colorimeter through GCM, > or is the support just not there yet or something? Well, if it's supported in Argyll then it's supported by GCM. Richard. From knizek.confy at volny.cz Sun Feb 7 11:23:57 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sun, 07 Feb 2010 12:23:57 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> Message-ID: <1265541838.20793.5.camel@athlon> Richard Hughes p??e v So 06. 02. 2010 v 15:55 +0000: > On 6 February 2010 10:39, Milan Kn??ek wrote: > > This means that the GCM would have to change a bit more: GCM must know > > what the native monitor gamma is. > > We can do this, but in my experience the EDID data from the monitor is > wrong more often than it's right... > > Richard. > I understand that getting the EDID data is unreliable at the moment. In addition, some wide-gamut displays support pre-set calibration modes emulating various colour spaces. The modes can be changed via hardware buttons on the LCD. For the time being, I would leave up to the user to select the proper display profile (depending on the attached monitor and its calibration mode) rather then only relying on EDID. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Mon Feb 8 01:27:50 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 12:27:50 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <4B6F6896.9050406@argyllcms.com> Richard Hughes wrote: > Well, if it's supported in Argyll then it's supported by GCM. But note that the Spyder 2 needs to have firmware. In Argyll the spyd2en utility needs to be run to extract the firmware from the distribution disk. See Graeme Gill. From hughsient at gmail.com Mon Feb 8 07:58:05 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 07:58:05 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6F6896.9050406@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> Message-ID: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> On 8 February 2010 01:27, Graeme Gill wrote: > But note that the Spyder 2 needs to have firmware. In Argyll > the spyd2en utility needs to be run to extract the firmware from > the distribution disk. > See What's the output from argyllcms if there is no firmware? Or does the device just not appear? Thanks, Richard. From graeme2 at argyllcms.com Mon Feb 8 08:22:18 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 19:22:18 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> Message-ID: <4B6FC9BA.5030905@argyllcms.com> Richard Hughes wrote: > What's the output from argyllcms if there is no firmware? Or does the > device just not appear? There will be an error message containing: "No PLD firmware pattern is available" Graeme Gill. From hughsient at gmail.com Mon Feb 8 08:40:17 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 08:40:17 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6FC9BA.5030905@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> <4B6FC9BA.5030905@argyllcms.com> Message-ID: <15e53e181002080040o56051e39k39dc13f01163194d@mail.gmail.com> On 8 February 2010 08:22, Graeme Gill wrote: > There will be an error message containing: > > "No PLD firmware pattern is available" That's great, thanks. Richard. From hughsient at gmail.com Mon Feb 8 09:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:16:56 +0000 Subject: Small thumbnails of targets Message-ID: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> The attached file shows some new UI in gnome-color-manager -- it now supports more types of targets than just IT8. To be able to show the user a preview of what each target looks like, we need some 200x150 pixel thumbnails of the different target types. These need to be GPLv2+ licenced, and have the specific vendor data removed. See the screenshot for an example. This would be a great way to help out gnome-color-manager if you are not comfortable with coding. The list of target types I need as thumbnails are: CMP_Digital_Target-3 CMP_DT_003 ColorChecker ColorCheckerDC ColorCheckerSG Hutchcolor i1_RGB_Scan_1.4 LaserSoftDCPro QPcard_201 I've already done IT8. Please cc the list if you send me a type, and then we won't get duplicated effort. Note: you can't just copy and paste from the manufacturers website, as they may have copyright on the image. Basically, the rule is if you're not sure about the copyright of the image, then it's not suitable. The best way would be to scan the target yourself and send it to me. If you send files, please state where you got them from, and that they are redistributable as part of a project that is GPLv2+. Thanks, Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 44590 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 09:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <15e53e181002080147l7e6f4246pf92afe936ffd28b5@mail.gmail.com> On 8 February 2010 09:16, Richard Hughes wrote: > The best way would be to scan the > target yourself and send it to me. If you send files, please state > where you got them from, and that they are redistributable as part of > a project that is GPLv2+. I forgot to mention. They also have to be PNG format. Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 10:00:38 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 10:00:38 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <1265623238.9194.9.camel@tybalt> On Sat, 2010-02-06 at 15:57 +0000, Richard Hughes wrote: > On 6 February 2010 12:29, Jon Leighton wrote: > > I have a ColorVision Spyder colorimeter. I have just been trying out > > gnome-color-manager (very impressive!) but the calibration buttons are > > disabled, even when I plug in my colorimeter. > > What version ArgyllCMS do you have installed? If it's less than 1.1.0 > you'll need to add --disable-hardware-detection to ./configure -- it > also only works for display devices for now (patches welcome!). Aha, that was it. I've installed latest argyll, and now the button is enabled. However, when I click it and select LCD, I then get the "Display setup" dialog. If I click OK nothing happens - the dialog closes but nothing else comes up. I tried running with -vvv and the following came up: TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 - failed to calibrate: failed to match display as RandR is faulty TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,170 - min=0.000000,max=1.000000 TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,176 - falling back to dummy gamma TI:09:52:12 FI:gcm-device-xrandr.c FN:gcm_device_xrandr_set_gamma_fallback,351 - using PER-SCREEN gamma tables as driver is not XRANDR 1.3 compliant TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_output_profile,477 - found default, removing atom TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_root_window_profile,239 - removing root window ICC profile atom Any ideas? Thanks From hughsient at gmail.com Mon Feb 8 10:39:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 10:39:12 +0000 Subject: ColorVision Spyder In-Reply-To: <1265623238.9194.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> Message-ID: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> On 8 February 2010 10:00, Jon Leighton wrote: > Aha, that was it. I've installed latest argyll, and now the button is > enabled. That's good. > TI:09:52:12 ? ? FI:gcm-prefs.c ?FN:gcm_prefs_calibrate_display,381 > ?- failed to calibrate: failed to match display as RandR is faulty What video driver are you using? Can you attach the output of xrandr please? Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 11:12:37 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 11:12:37 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> Message-ID: <1265627557.9194.11.camel@tybalt> Hi, On Mon, 2010-02-08 at 10:39 +0000, Richard Hughes wrote: > > TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 > > - failed to calibrate: failed to match display as RandR is faulty > > What video driver are you using? I'm using the nVidia driver, version 185.18.36. > Can you attach the output of xrandr please? Thanks. Yep. Cheers, Jon -------------- next part -------------- Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 50.0 51.0 52.0* 1600x1024 53.0 1440x900 54.0 1360x768 55.0 56.0 1280x1024 57.0 1280x960 58.0 1152x864 59.0 1024x768 60.0 960x600 61.0 960x540 62.0 840x525 63.0 64.0 800x600 65.0 66.0 800x512 67.0 720x450 68.0 700x525 69.0 680x384 70.0 71.0 640x512 72.0 640x480 73.0 74.0 576x432 75.0 512x384 76.0 400x300 77.0 320x240 78.0 From hughsient at gmail.com Mon Feb 8 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 11:20:27 +0000 Subject: ColorVision Spyder In-Reply-To: <1265627557.9194.11.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> Message-ID: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> On 8 February 2010 11:12, Jon Leighton wrote: > I'm using the nVidia driver, version 185.18.36. Hmm, I fear this maybe another case of broken binary drivers. Is there any chance you could try with the nouveau driver please? Thanks. Richard. From graeme2 at argyllcms.com Mon Feb 8 11:58:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 22:58:48 +1100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4B6FFC78.9010503@argyllcms.com> I've sent Richard an image of the ColorCheckerDC. Graeme Gill From j at jonathanleighton.com Mon Feb 8 14:18:05 2010 From: j at jonathanleighton.com (Jonathan Leighton) Date: Mon, 8 Feb 2010 14:18:05 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> Message-ID: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Hi, On 8 February 2010 11:20, Richard Hughes wrote: > On 8 February 2010 11:12, Jon Leighton wrote: >> I'm using the nVidia driver, version 185.18.36. > > Hmm, I fear this maybe another case of broken binary drivers. Is there > any chance you could try with the nouveau driver please? Thanks. Yes, it worked under nouveau. (Incidentally, the calibration seemed pretty quick, and I'm not sure the results were great in my case. Are there any plans to have an option of "quick profile" vs "good profile"?) Cheers, Jon From pmjdebruijn at pcode.nl Mon Feb 8 14:27:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:27:24 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > ColorChecker I have just done these two... > I've already done IT8. I redid the IT8, we should called this IT8.7/2, since that's it's proper name... There are other IT8 charts (I think those are mostly for printing), using the full name should prevent any confusion. With all the images, I scanned my own targets, and then followed this procedure: 1. Despeckle, Adaptive enabled, Recursive dislabed, Radius 3, Black level 6, White level 255 2. Then possibly rotate the chart a bit to align it, and then crop it. 3. Then use GIMP Resynthesize to remove vendor text "Smart remove selection", with 10px. 4. Possibly have GIMP do Auto White Balance (doesn't work always) Without distorting aspect, my images could all be rounded to 200px by 140px. I think we should not distort aspect in any visible way. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: IT872.png Type: image/png Size: 31624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ColorChecker24.png Type: image/png Size: 32929 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CMP-DigitalTarget3.png Type: image/png Size: 44514 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 14:52:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 14:52:23 +0000 Subject: ColorVision Spyder In-Reply-To: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Message-ID: <15e53e181002080652j1616f139h65a133fb55b1e895@mail.gmail.com> On 8 February 2010 14:18, Jonathan Leighton wrote: > (Incidentally, the calibration seemed pretty quick, and I'm not sure > the results were great in my case. Are there any plans to have an > option of "quick profile" vs "good profile"?) Grab gcm from git master, and then set /apps/gnome-color-manager/calibration_length in GConf Editor. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 14:56:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:56:17 +0100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4B6FFC78.9010503@argyllcms.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> Message-ID: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: > I've sent Richard an image of the ColorCheckerDC. I noticed it got commited... But it's aspect ratio is slightly off... You obviously did that to comply with Richard's 200x150 specification... But 200x140 as a baseline would be better for most charts... You're ColorCheckerDC image looks much better when rescaled to 200x140. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Mon Feb 8 15:04:06 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:04:06 +0100 Subject: Camera profile generation options Message-ID: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Hi, Are camera profiles generated with Argyll's default options? -q m -a l ? This might be fine for IT8 or other targets with lots of patches... But it's probably not such a good idea for a 24 patch ColorChecker, -q l -a S seems more appropriate... Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:04:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:04:27 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> Message-ID: <15e53e181002080704o79716ec2kd131bf0fbf8feafb@mail.gmail.com> On 8 February 2010 14:27, Pascal de Bruijn wrote: > I have just done these two... Brilliant, thanks. >> I've already done IT8. > > I redid the IT8, we should called this IT8.7/2, since that's it's > proper name... There are other IT8 charts (I think those are mostly > for printing), using the full name should prevent any confusion. Done, thanks. > Without distorting aspect, my images could all be rounded to 200px by > 140px. I think we should not distort aspect in any visible way. Okay, I've changed the others to be 200x140 also. Thanks. Richard. From hughsient at gmail.com Mon Feb 8 15:12:35 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:12:35 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Message-ID: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> On 8 February 2010 15:04, Pascal de Bruijn wrote: > Are camera profiles generated with Argyll's default options? -q m -a l ? > > This might be fine for IT8 or other targets with lots of patches... > > But it's probably not such a good idea for a 24 patch ColorChecker, -q > l -a S seems more appropriate... Yes, this is a good idea, and a perfect patch for you to submit :-) The kind of profile is listed in src/gcm-calibrate-argyll.h, which is saved to priv->reference_kind, which is private data for the GcmCalibrateArgyll object. You probably need to add a simple "if (priv->reference_kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just getting the type of profile (using gcm_calibrate_argyll_precision_to_quality_arg) in the function gcm_calibrate_argyll_device_generate_profile() which lives in src/gcm-calibrate-argyll.c Make a few changes, and just do "git diff > test.patch" Attach the test.patch to an email (on the mailing list if you're feeling brave, or just to me if you're feeling timid) and I'll give you some feedback. Grab me on IRC if you are feeling really stuck / lazy / busy. Richard. From hughsient at gmail.com Mon Feb 8 15:14:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:14:22 +0000 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> Message-ID: <15e53e181002080714y11dad8afxb11eb95cbd801a85@mail.gmail.com> On 8 February 2010 14:56, Pascal de Bruijn wrote: > On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: >> I've sent Richard an image of the ColorCheckerDC. > > I noticed it got commited... But it's aspect ratio is slightly off... > You obviously did that to comply with Richard's 200x150 > specification... No, I did that, Graeme sent me the original image. I've sent you the profile for the same love. > But 200x140 as a baseline would be better for most charts... You're > ColorCheckerDC image looks much better when rescaled to 200x140. Agreed. Richard. From hughsient at gmail.com Mon Feb 8 15:16:29 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:16:29 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? Message-ID: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> I've got sources that look like this: if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) return "CMP_Digital_Target-3.cht"; if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) return "CMP_DT_003.cht"; Are they actually the same profile type? What's the difference in the chart versions? Thanks, Richard. From pmjdebruijn at pcode.nl Mon Feb 8 15:46:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:46:17 +0100 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> Message-ID: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> On Mon, Feb 8, 2010 at 4:16 PM, Richard Hughes wrote: > I've got sources that look like this: > > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) > ? ? ? ? ? ? ? ?return "CMP_Digital_Target-3.cht"; > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) > ? ? ? ? ? ? ? ?return "CMP_DT_003.cht"; > > Are they actually the same profile type? What's the difference in the > chart versions? They are different charts... I have this one (3): http://www.cmp-color.fr/eng%20digital%20target.html Are there is the 003 one: http://www.argyllcms.com/doc/CMP_DT_003.jpg Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:48:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:48:53 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> Message-ID: <15e53e181002080748i4f953979j9999944c092cc31@mail.gmail.com> On 8 February 2010 15:46, Pascal de Bruijn wrote: > They are different charts... Cool, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 21:32:32 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:32:32 +0100 Subject: Camera profile generation options In-Reply-To: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> Message-ID: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> On Mon, Feb 8, 2010 at 4:12 PM, Richard Hughes wrote: > On 8 February 2010 15:04, Pascal de Bruijn wrote: >> Are camera profiles generated with Argyll's default options? -q m -a l ? >> >> This might be fine for IT8 or other targets with lots of patches... >> >> But it's probably not such a good idea for a 24 patch ColorChecker, -q >> l -a S seems more appropriate... > > Yes, this is a good idea, and a perfect patch for you to submit :-) > > The kind of profile is listed in src/gcm-calibrate-argyll.h, which is > saved to priv->reference_kind, which is private data for the > GcmCalibrateArgyll object. You probably need to add a simple "if > (priv->reference_kind == > GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just > getting the type of profile (using > gcm_calibrate_argyll_precision_to_quality_arg) in the function > gcm_calibrate_argyll_device_generate_profile() which lives in > src/gcm-calibrate-argyll.c > > Make a few changes, and just do "git diff > test.patch" I think this patch should do it, it seems to work, though I didn't extensively test it. I also included the QPcard as well, it's a similar target... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-calibrate-argyll-low-patch-count-target-low-quality-single-shaper.patch Type: text/x-patch Size: 2556 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 8 21:58:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:58:24 +0100 Subject: Camera Profiling GUI Dialog Order Message-ID: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Hi, Currently to profile a camera, the GUI first asks for both files, and then asks for the chart type... This seems odd to me... It seems more natural to me, to first ask about the chart type, and then ask about the files... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-ask-reference-kind-first.patch Type: text/x-patch Size: 1241 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:23:07 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:23:07 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> Message-ID: <15e53e181002081423g6279830eq5c07be8d8aca9e9e@mail.gmail.com> On 8 February 2010 21:32, Pascal de Bruijn wrote: > I think this patch should do it, it seems to work, though I didn't > extensively test it. Great stuff. I've modified your patch a little (just passing the calibrate_argyll object and renaming a function) and committed it. I've attached the changed version. Well done! Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Do-low-quality-calibration-when-using-targets-with-a.patch Type: text/x-patch Size: 3393 bytes Desc: not available URL: From amluto at gmail.com Mon Feb 8 22:23:02 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Mon, 8 Feb 2010 17:23:02 -0500 Subject: Reduce autoconf requirement Message-ID: Hi all- For kicks, I just grabbed gnome-color-manager out of git, built it, and ran it on KDE4 on Fedora 12. (why not?) It seems to work (I haven't tested its Argyll integration yet.) To make it build, though, I had to decrease the autoconf required version, like this: diff --git a/configure.ac b/configure.ac index bf4e31f..d4f422b 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_PREREQ(2.65) +AC_PREREQ(2.63) AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) AC_CONFIG_SRCDIR(src) Is there any reason we require autogen 2.65? 2.63 from F12 seems to work just fine. shared-color-targets needs the same patch. As an aside, what's the profile graph on the right? Is it the calibration (VCGT), the gray axis of the profile, or something else? (I assume it's not the gray axis -- it doesn't really look like xicclu's output.) Thanks, Andy From hughsient at gmail.com Mon Feb 8 22:24:45 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:24:45 +0000 Subject: Camera Profiling GUI Dialog Order In-Reply-To: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> References: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Message-ID: <15e53e181002081424hc401819k29fc0a3c0ad96d8@mail.gmail.com> On 8 February 2010 21:58, Pascal de Bruijn wrote: > Currently to profile a camera, the GUI first asks for both files, and > then asks for the chart type... This seems odd to me... Agreed. > It seems more natural to me, to first ask about the chart type, and > then ask about the files... Committed, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 22:26:34 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 23:26:34 +0100 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> On Mon, Feb 8, 2010 at 11:23 PM, Andrew Lutomirski wrote: > Hi all- > > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) > > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) > > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. I apply the attached patch to git to make it work on Ubuntu Karmic. > shared-color-targets needs the same patch. > > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) If I'm not mistaken those are the TRC's... VCGT is only relevant for displays... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-git-demodernize-configure-ac.patch Type: text/x-patch Size: 2099 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:27:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:27:40 +0000 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <15e53e181002081427m68ba1894w9810233b37c1cf53@mail.gmail.com> On 8 February 2010 22:23, Andrew Lutomirski wrote: > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) Sure, it should work. > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) The 2.63 BR was from autoupdate'ing the scripts. > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. If it works, great! > shared-color-targets needs the same patch. Will do. > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) I think we need graph labels in this case. It's actually the TRC. Richard. From hughsient at gmail.com Mon Feb 8 22:28:44 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:28:44 +0000 Subject: Reduce autoconf requirement In-Reply-To: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> References: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> Message-ID: <15e53e181002081428p43926011mf3d6510d720a492c@mail.gmail.com> On 8 February 2010 22:26, Pascal de Bruijn wrote: > I apply the attached patch to git to make it work on Ubuntu Karmic. Hmm, that seems a bit drastic. Doesn't changing the version to 2.63 work okay in the Karmic case? Richard. From pmjdebruijn at pcode.nl Tue Feb 9 11:29:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:29:44 +0100 Subject: QPcard 201 thumbnail Message-ID: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> Hi, Here's a QPcard_201 thumbnail, postprocessed from a scanned image, submitted on the ArgyllCMS mailing list by Wallden Magnus. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201.png Type: image/png Size: 14124 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Tue Feb 9 11:35:55 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:35:55 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> Message-ID: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> On Tue, Feb 9, 2010 at 12:34 PM, Pascal de Bruijn wrote: > On Tue, Feb 9, 2010 at 12:29 PM, Pascal de Bruijn wrote: >> Hi, >> >> Here's a QPcard_201 thumbnail, postprocessed from a scanned image, >> submitted on the ArgyllCMS mailing list by Wallden Magnus. > > Whoops, forgot to remove the branding. Whoops, posted the hires version, not the thumbnail... Sorry, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201_unbranded.png Type: image/png Size: 12926 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 9 12:06:32 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 12:06:32 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> Message-ID: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> On 9 February 2010 11:35, Pascal de Bruijn wrote: > Whoops, posted the hires version, not the thumbnail... I've committed this after padding the height to 140 like the others. I really don't want the dialog resizing as the combobox elements are selected. Thanks, Richard. From pmjdebruijn at pcode.nl Tue Feb 9 13:10:48 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 14:10:48 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> Message-ID: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> On Tue, Feb 9, 2010 at 1:06 PM, Richard Hughes wrote: > On 9 February 2010 11:35, Pascal de Bruijn wrote: >> Whoops, posted the hires version, not the thumbnail... > > I've committed this after padding the height to 140 like the others. I > really don't want the dialog resizing as the combobox elements are > selected. I noticed you centered the image... Though, the white background suggests it's a big white card, with the patches centered, while it's not. We should use transparency here. I'll "fix" the image tonight, if you don't get to it first. Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 13:11:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:11:43 +0000 Subject: Using SANE? Message-ID: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> I'm thinking of using SANE (rather than udev like we do now) to get the list of scanners, and hopefully to be able to change settings on the device. It also allows us to change remote devices, not just locally plugged in USB ones. Is sane-backends-libs a problem for you distro guys? I'm not sure if it's installed by default on most distros, but it does pull in a few deps. Comments? Richard. From hughsient at gmail.com Tue Feb 9 13:17:15 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:17:15 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> Message-ID: <15e53e181002090517m76d879bdyba6cc199da454ebd@mail.gmail.com> On 9 February 2010 13:10, Pascal de Bruijn wrote: > I noticed you centered the image... Though, the white background > suggests it's a big white card, with the patches centered, while it's > not. Point taken. > We should use transparency here. I'll "fix" the image tonight, if you > don't get to it first. Okay. when you're submitting new binary files, the easiest way (for me) to do it, is this: git checkout -b the-subject-of-the-change git commit -a -m "Make the image background transparent" --author "Me Mine " ( the -a means "all changes to the working tree", the -m means "this is the commit message", and --author is so the right person gets listed in NEWS) git format-patch master git checkout master Then, all I have to do is use the command "git am" and I don't have to copy and paste your name, email, or come up with a commit message. If you get stuck, let me know. Richard. From fred at crozat.net Tue Feb 9 14:01:39 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:01:39 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> Message-ID: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> 2010/2/9 Richard Hughes : > I'm thinking of using SANE (rather than udev like we do now) to get > the list of scanners, and hopefully to be able to change settings on > the device. It also allows us to change remote devices, not just > locally plugged in USB ones. Is sane-backends-libs a problem for you > distro guys? I'm not sure if it's installed by default on most > distros, but it does pull in a few deps. How about using PackageKit to install it "on demand" ? ;) gnome-color-manager is installed "by default" in Mandriva 2010.0 but I'd like to keep sane ouf of the default install, if we can. -- Frederic Crozat From hughsient at gmail.com Tue Feb 9 14:21:02 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 14:21:02 +0000 Subject: Using SANE? In-Reply-To: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> Message-ID: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> On 9 February 2010 14:01, Frederic Crozat wrote: > 2010/2/9 Richard Hughes : >> I'm thinking of using SANE (rather than udev like we do now) to get >> the list of scanners, and hopefully to be able to change settings on >> the device. It also allows us to change remote devices, not just >> locally plugged in USB ones. Is sane-backends-libs a problem for you >> distro guys? I'm not sure if it's installed by default on most >> distros, but it does pull in a few deps. > > How about using PackageKit to install it "on demand" ? ;) Heh, this would be a library dep, not a tool dep. > gnome-color-manager is installed "by default" in Mandriva 2010.0 but > I'd like to keep sane ouf of the default install, if we can. You mean sane-backends-libs, rather than sane itself, right? Richard. From fred at crozat.net Tue Feb 9 14:34:22 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:34:22 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: <21ad25711002090634y7ef9e181oa77e6a7796a63c99@mail.gmail.com> 2010/2/9 Richard Hughes : > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Ah :( >> gnome-color-manager is installed "by default" in Mandriva 2010.0 but >> I'd like to keep sane ouf of the default install, if we can. > > You mean sane-backends-libs, rather than sane itself, right? Yes, I mean the lib package. It is 7.7MB installed, without checking its dependencies (of course, now, I've discovered openoffice-common is pulling libsane by default too :( If it could be a plugin, that would be nice :) -- Frederic Crozat From amluto at gmail.com Tue Feb 9 15:15:28 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Tue, 9 Feb 2010 10:15:28 -0500 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: On Tue, Feb 9, 2010 at 9:21 AM, Richard Hughes wrote: > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Is it safe to assume that anyone who wants to profile a scanner already has sane-backends-libs installed? If so, you could dlopen it and if that fails assume that there aren't any scanners. --Andy From pmjdebruijn at pcode.nl Tue Feb 9 19:28:41 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 20:28:41 +0100 Subject: Disconnected devices: create profiles for device disabled Message-ID: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Hi, When I have a EOS 400D disconnected, the "Create profiles for device" button is disabled, is this intentional? There is no good reason why my camera would need to be connected... For displays, it has it's advantages having the display connected for profiling though :p Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 19:49:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 19:49:22 +0000 Subject: Disconnected devices: create profiles for device disabled In-Reply-To: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> References: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Message-ID: <15e53e181002091149q7815c328n20cd83e87060efd6@mail.gmail.com> On 9 February 2010 19:28, Pascal de Bruijn wrote: > For displays, it has it's advantages having the display connected for > profiling though :p commit 9da8afc4f5dd9c7a0e252fa42483616c74696695 Author: Richard Hughes Date: Tue Feb 9 19:34:43 2010 +0000 Only require the device to be present if it is a display type :100644 100644 66af4b3... f25d118... M src/gcm-prefs.c Richard. From lars.tore at mulebakken.net Wed Feb 10 13:29:22 2010 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 10 Feb 2010 14:29:22 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > CMP_DT_003 > ColorChecker > ColorCheckerDC > ColorCheckerSG > Hutchcolor > i1_RGB_Scan_1.4 Here is a photo of the i1_RGB_Scan_1.4 scan target. I have removed the eye-one name. And it's OK with GPLv2+ Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: i1_RGB_Scan_14.png Type: image/png Size: 36266 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 10 19:38:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 10 Feb 2010 19:38:39 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> Message-ID: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> On 10 February 2010 17:17, Pascal de Bruijn wrote: > I modified the thumbnail slightly to even out the lighting, and > improve contrast. Looks great. > I attached a patch for the modified version for git master. Tanks, I've also merged the Makefile.am and gcm-prefs.c parts too. Thanks. Richard. From knizek.confy at volny.cz Wed Feb 10 20:01:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 21:01:36 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo Message-ID: <1265832096.26568.43.camel@athlon> Hello everyone on the list! GCM is getting feature-rich - display, scanner and camera profiling is already supported, but printer characterisation is still missing. Richard H would like to code the few bytes ;-) but he does not have a spectrophotometer at hand. On Richard's blog, Paul Finnigan proposed a donation from users - the ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 in the U.K., were Richard lives. The more expensive variant would require about 10 people @ USD 50 donation each. (Or less donors to buy in the U.S. and someone to actually deliver across the ocean.) At the moment, three of us offered a contribution. Anybody else here willing to help with even a smaller amount (probably via PayPal)? Or other suggestions? best regards, Milan Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Wed Feb 10 20:52:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 10 Feb 2010 21:52:27 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> On Wed, Feb 10, 2010 at 9:01 PM, Milan Kn??ek wrote: > Hello everyone on the list! > > ... > > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? I'd be willing to pitch in (PayPal) for about 25EUR... Regards, Pascal de Bruijn From knizek.confy at volny.cz Wed Feb 10 22:31:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 23:31:36 +0100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <1265841096.7579.76.camel@athlon> Getting back to update of the text: > -- > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. > -- Taking into account Graeme's points (thanks, it was helpful), how about this: (The GCM gamma fine tuning tool remains as it is - i.e. pure adjustment to LUT, not taking care about the monitor native gamma) --- Overall system gamma is a product of image encoding gamma, video card gamma and native gamma of the monitor and normally it should be equal to 1. You may want to adjust gamma to allow for non-standard viewing conditions (e.g increasing gamma in dim light at home). Refer to User Manual for more details. --- And this be included in User Manual: --- CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually emulate the same value. Traditionally, Linux and MS Windows operating systems use image encoding of 1/2.2 and do not apply any gamma adjustment to the image or video card LUT. Therefore the overall gamma is expected to be around 1.1 (which is useful to allow for dim viewing conditions at home environment). Apple used to use image encoding gamma close to 1/1.8 to naturally match the native gamma of printing devices (and therefore internally applied gamma adjustment of 1/1.45 before displaying images on monitor so that the images displayed correctly). Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding gamma has also the value of 1/2.2 to meet the requirements of consumer imaging industry. Before fine tuning the gamma in GCM, you should know what your monitor native gamma is, what display gamma you want to reach and then do the math yourself. --- regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pedro at pedrocr.net Thu Feb 11 08:49:07 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 00:49:07 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> Message-ID: <62e8012c1002110049j76960ec1jbeac96b428a2221c@mail.gmail.com> On Wed, Feb 10, 2010 at 12:52 PM, Pascal de Bruijn > I'd be willing to pitch in (PayPal) for about 25EUR... You can count me in for another 50$. Pedro From paul at fincc.com Thu Feb 11 09:54:05 2010 From: paul at fincc.com (Paul Finnigan) Date: Thu, 11 Feb 2010 09:54:05 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <1265882045.4190.8.camel@localhost> Hi everyone Sorry, I took a few days off reading the postings. Thanks Milan for trying to drive this one. On Wed, 2010-02-10 at 21:01 +0100, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. > > The more expensive variant would require about 10 people @ USD 50 > donation each. (Or less donors to buy in the U.S. and someone to > actually deliver across the ocean.) I am a photographer who likes to keep up with the Jones' (MS/Apple). To do this while running Linux I have had to make compromise after compromise with regard to 'Free' software. This is my own choice and I am not complaining about it. As an example I have paid for the Turbo Linux printer drivers. I have to say they are good, I do not begrudge the author his 29 euros. If I want free software then I believe it will cost me money at times. What Richard is providing is something, as a photographer, I have wanted for some time. He is also providing the source to the community. I know others are involved (thanks to everyone who is helping). I admit my suggestion of $50 was perhaps high. I just thought that as I know that TurboLinux drivers are popular with photographers I could pitch in a little above that price ($38). I am sure that we as a community can support ourselves. Look at what the Gnome community has already done. What is being asked here is that we get some hardware for a key developer to ensure that the software does what we all want, to help us manage colour. To get the ball rolling we need to set up an account. I am willing to let Richard have my $50 even if we do not reach the target of $500. If Richard or anyone else would like to mail me directly my address is paul at fincc dot com. -- Paul Finnigan From pmjdebruijn at pcode.nl Thu Feb 11 10:38:54 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 11:38:54 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> Message-ID: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> On Wed, Feb 10, 2010 at 8:38 PM, Richard Hughes wrote: > On 10 February 2010 17:17, Pascal de Bruijn wrote: >> I modified the thumbnail slightly to even out the lighting, and >> improve contrast. > > Looks great. I just processed the ColorCheckerSG image submitted by Hening Betterman on the ArgyllCMS mailing list. I attached a patch. Please verify before committing. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-ColorCheckerSG-target-image-submitted-by-Hening-.patch Type: text/x-patch Size: 45877 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 11 10:53:42 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:53:42 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> Message-ID: <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> On 11 February 2010 10:38, Pascal de Bruijn wrote: > I just processed the ColorCheckerSG image submitted by Hening > Betterman on the ArgyllCMS mailing list. > > I attached a patch. Please verify before committing. Perfect. Thanks. Richard. From hughsient at gmail.com Thu Feb 11 10:55:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:55:40 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> On 11 February 2010 09:54, Paul Finnigan wrote: > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If we don't reach the target I just have to convince my wife that it's a work thing and pony up the rest. Richard. From hughsient at gmail.com Thu Feb 11 11:05:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 11:05:28 +0000 Subject: Information re. display gamma In-Reply-To: <1265841096.7579.76.camel@athlon> References: <1265374532.31703.61.camel@athlon> <1265841096.7579.76.camel@athlon> Message-ID: <15e53e181002110305h113bd2c8kd8b863fbc1a4005e@mail.gmail.com> On 10 February 2010 22:31, Milan Kn??ek wrote: > Overall system gamma is a product of image encoding gamma, video card > gamma and native gamma of the monitor and normally it should be equal to > 1. You may want to adjust gamma to allow for non-standard viewing > conditions (e.g increasing gamma in dim light at home). Refer to User > Manual for more details. > --- > And this be included in User Manual: > --- > CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually > emulate the same value. > > Traditionally, Linux and MS Windows operating systems use image encoding > of 1/2.2 and do not apply any gamma adjustment to the image or video > card LUT. Therefore the overall gamma is expected to be around 1.1 > (which is useful to allow for dim viewing conditions at home > environment). > > Apple used to use image encoding gamma close to 1/1.8 to naturally match > the native gamma of printing devices (and therefore internally applied > gamma adjustment of 1/1.45 before displaying images on monitor so that > the images displayed correctly). > > Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding > gamma has also the value of 1/2.2 to meet the requirements of consumer > imaging industry. > > Before fine tuning the gamma in GCM, you should know what your monitor > native gamma is, what display gamma you want to reach and then do the > math yourself. Sounds good to me. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 11 11:57:49 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 12:57:49 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> Message-ID: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> On Thu, Feb 11, 2010 at 11:55 AM, Richard Hughes wrote: > On 11 February 2010 09:54, Paul Finnigan wrote: >> To get the ball rolling we need to set up an account. I am willing to >> let Richard have my $50 even if we do not reach the target of $500. > > If we don't reach the target I just have to convince my wife that it's > a work thing and pony up the rest. Then setup a PayPal account, and leave the details here :) Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 11 12:55:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 12:55:27 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> Message-ID: <15e53e181002110455l21da13pfe21eccf360fc192@mail.gmail.com> On 11 February 2010 11:57, Pascal de Bruijn wrote: > Then setup a PayPal account, and leave the details here :) I've already got a paypal account, richard at hughsie.com Please leave me your email addresses in any payments, in case we make nowhere near the total and I have to refund people. Thanks. Richard. From alexandre.prokoudine at gmail.com Thu Feb 11 19:30:38 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Thu, 11 Feb 2010 22:30:38 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> On 2/10/10, Milan Kn??ek wrote: > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? Yes, via PayPal. Count me in. Alexandre From pmjdebruijn at pcode.nl Thu Feb 11 20:44:25 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 21:44:25 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> Message-ID: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> On Thu, Feb 11, 2010 at 8:30 PM, Alexandre Prokoudine wrote: > On 2/10/10, Milan Kn??ek wrote: > >> Anybody else here willing to help with even a smaller amount (probably >> via PayPal)? Or other suggestions? > > Yes, via PayPal. Count me in. I just PayPalled 25 EUR... Regards, Pascal de Bruijn From pedro at pedrocr.net Fri Feb 12 01:42:10 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 17:42:10 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> Message-ID: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: > I just PayPalled 25 EUR... Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware organizations do this in scale? It would be great to be able to pitch in money to a common fund saying "I'd like this specific piece/type of hardware to work better in Linux" so that developers could get free access to hardware. By the way Richard, I've recently been through the battle of profiling my Epson R2880 with color munki, directly with argyll commands. I kept a few notes so I can tell you the commands that worked, the number of patches that were reasonable and especially about a small hack I did to be able to use much smaller patches with the color munki (and thus use less paper). Cheers, Pedro From pmjdebruijn at pcode.nl Fri Feb 12 07:38:57 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 08:38:57 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> On Fri, Feb 12, 2010 at 2:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: >> I just PayPalled 25 EUR... > > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? It would be great to be able to pitch > in money to a common fund saying "I'd like this specific piece/type of > hardware to work better in Linux" so that developers could get free > access to hardware. > > By the way Richard, I've recently been through the battle of profiling > my Epson R2880 with color munki, directly with argyll commands. I kept > a few notes so I can tell you the commands that worked, the number of > patches that were reasonable and especially about a small hack I did > to be able to use much smaller patches with the color munki (and thus > use less paper). Your hack was pretty cool, but it's not really handy to implement as a generic solution for GCM, we need no fuss solutions. This works very well for me... and would be a great default for medium quality: argyll-targen -v -d2 -f 210 xxx printtarg -v -i CM -h -T 300 -p A4 xxx colprof -q m -a l xxx For low quality the -h parameter can be dropped from printtarg, and lower the number of patches to ~90, whatever fits on a A4 piece of paper... One the the main problems is that these settings can vary from spectrophotometer to spectrophotometer... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 08:54:11 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:54:11 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <15e53e181002120054j23a0b855n55a671f870605644@mail.gmail.com> On 12 February 2010 07:38, Pascal de Bruijn > One the the main problems is that these settings can vary from > spectrophotometer to spectrophotometer... Sure, but we only care about a handful of types, and we can quite easily use the GUdev data to build up a profile for each device type, falling back if the device is unknown. I think it would be very useful to make Munki-specific data, as long as we have good fallbacks for the devices people keep secret. Richard. From hughsient at gmail.com Fri Feb 12 08:57:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:57:26 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> Message-ID: <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> On 11 February 2010 18:31, Pascal de Bruijn > But it's even worse, I screwed up the image as well... Here's a replacement. Applied, thanks. Do you want me to arrange for you to get GNOME commit access? It would mean you can commit this sort of thing without asking? Richard. From pedro at pedrocr.net Fri Feb 12 10:42:17 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:42:17 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: > Your hack was pretty cool, but it's not really handy to implement as a > generic solution for GCM, we need no fuss solutions. We will surely need a default mode that does that but my experience with doing it like you do bellow is that 200 patches isn't really reasonable. With the default settings you need 2 Letter pages to do ~190 and that generates pretty useless profiles. So to do the ~450+900 patches I ended up using for a decent profile you'd need ~15 pages which is a terrible waste of paper and ink. Like Richard says, it would be great to have the profiling instruments defined in a config somewhere, so that one can define a "Munki" and a "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" UI probably makes sense too as people doing color profiling would tend to be advanced users. > This works very well for me... and would be a great default for medium quality: > ?argyll-targen -v -d2 -f 210 xxx I ended up only getting good results at 450+900 patches. I suppose lower than that could also work. This should probably be given as an option to the user. Maybe a slider with markings or poor - basic - good - great and an automatic calculation of how many pages it is going to print, so that the user can do the tradeoff himself. > ?printtarg -v -i CM -h -T 300 -p A4 xxx My hack uses "-i i1". I haven't used the -T one. What does increasing the resolution help with? > ?colprof -q m -a l xxx "-a l" is default and I had also "-c mt" and "-d pp". Maybe they are not really needed. Cheers, Pedro From pedro at pedrocr.net Fri Feb 12 10:54:55 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:54:55 -0800 Subject: Building a library of ICC profiles Message-ID: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Hi, Is there any package that collects free (as in speech) ICC profiles? I see that Pascal's PPA has one printer, one camera and two or three displays. Are these just the ones you did yourself Pascal? I'd be more than happy to add the profiles I've been doing for the printer and monitor to some repository so that users without a calibration instrument can just use a profile from the library. I already have profiles for a Dell U2410 and an Epson R2880 with Glossy Epson paper. I'll be adding more papers to that too. One thing I haven't done yet is profiling my camera. How is that done and what is the benefit? I have a Sony A700 DSLR. Cheers, Pedro From hughsient at gmail.com Fri Feb 12 11:14:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:14:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Message-ID: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> On 12 February 2010 10:54, Pedro C?rte-Real wrote: > Is there any package that collects free (as in speech) ICC profiles? I > see that Pascal's PPA has one printer, one camera and two or three > displays. Are these just the ones you did yourself Pascal? There's http://github.com/hughsie/shared-color-profiles which may be of interest to you. > I'd be more than happy to add the profiles I've been doing for the > printer and monitor to some repository so that users without a > calibration instrument can just use a profile from the library. I > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > Epson paper. I'll be adding more papers to that too. I'm not so sure submitting user-generated profiles makes so much sense, I mean, your Epson R2880 probably has a quite different response to my (hypothetical) Epson R2880. If people think this is a good idea, I'd be wiling to set something like this up, as lets face it, a profile that is 3% off correct is better than no profile at all. > One thing I > haven't done yet is profiling my camera. How is that done and what is > the benefit? I have a Sony A700 DSLR. That's something you really want to do. We probably want to add a whole load of text in the help file in how to do this (sunny day, etc) but using GCM the process itself should be pretty easy. Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:15:52 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:15:52 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> Message-ID: <4c2c37f91002120315vc4ee9fcy7e31caaee1db3a4c@mail.gmail.com> On Fri, Feb 12, 2010 at 11:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: >> Your hack was pretty cool, but it's not really handy to implement as a >> generic solution for GCM, we need no fuss solutions. > > We will surely need a default mode that does that but my experience > with doing it like you do bellow is that 200 patches isn't really > reasonable. With the default settings you need 2 Letter pages to do > ~190 and that generates pretty useless profiles. So to do the ~450+900 > patches I ended up using for a decent profile you'd need ~15 pages > which is a terrible waste of paper and ink. > > Like Richard says, it would be great to have the profiling instruments > defined in a config somewhere, so that one can define a "Munki" and a > "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" > UI probably makes sense too as people doing color profiling would tend > to be advanced users. > >> This works very well for me... and would be a great default for medium quality: >> ?argyll-targen -v -d2 -f 210 xxx > > I ended up only getting good results at 450+900 patches. I suppose > lower than that could also work. This should probably be given as an > option to the user. Maybe a slider with markings or poor - basic - > good - great and an automatic calculation of how many pages it is > going to print, so that the user can do the tradeoff himself. Highly depends on what kind of accuracy ones expects... 210 patches and -qm works reasonably well... I actually tried making a profile using 840 patches, and -qh, and I don't see a big difference here... Though my printer is much crappier than yours. >> ?printtarg -v -i CM -h -T 300 -p A4 xxx Anyway, patches count should most likely always be multiple of what a single sheet can hold... 1x A4 -> 210 2x A4 -> 420 3x A4 -> 630 4x A4 -> 840 This may be different for letter (190?). > My hack uses "-i i1". I haven't used the -T one. What does increasing > the resolution help with? This is seriously not an option for GCM... requiring users to make their own DIY patch reading guide. The colorimeter/spectrophotometer should work as develivered by the manufacturer... GNOME is about making things work as expected... not requiring DIY hobbying/hacks... For these kinds of strategies, using the Argyll commandline tools should be fine. Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:20:27 +0000 Subject: Adding a libtiff dep? Message-ID: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to add a libtiff hard dep on gnome-color-manager. All distros should already be installing this by default, but I wanted to check to see if anyone had any issue with this. Speak now, or forever hold your peace! :-) Thanks, Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:22:46 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:22:46 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: >> Is there any package that collects free (as in speech) ICC profiles? I >> see that Pascal's PPA has one printer, one camera and two or three >> displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. Those profiles are mostly for my private use... The camera profiles are probably generally usable though... >> I'd be more than happy to add the profiles I've been doing for the >> printer and monitor to some repository so that users without a >> calibration instrument can just use a profile from the library. I >> already have profiles for a Dell U2410 and an Epson R2880 with Glossy >> Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. One big problem with printer profiles are driver setttings, since profiles are also very specific to driver settings... I have no clue on how to solve that... Ideally you'd want the printer settings to be embedded in the profile. > If people think this is a good idea, I'd be wiling to set something > like this up, as lets face it, a profile that is 3% off correct is > better than no profile at all. Yeah sortof... >> One thing I >> haven't done yet is profiling my camera. How is that done and what is >> the benefit? I have a Sony A700 DSLR. > > That's something you really want to do. We probably want to add a > whole load of text in the help file in how to do this (sunny day, etc) > but using GCM the process itself should be pretty easy. I wrote about this here: http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Though the article is dated, and should be revised... I did make a few new discoveries... For example, I only recently noticed that strobes actually work well as reference light for generic profiles... I'm probably going to do a new blog post over the weekend... Here are some generic tips van raw photography with UFRaw in general: http://blog.pcode.nl/2009/08/23/ufraw-faq/ Most of it should apply to other dcraw based applications as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Fri Feb 12 11:24:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:24:10 +0100 Subject: Adding a libtiff dep? In-Reply-To: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> Message-ID: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> On Fri, Feb 12, 2010 at 12:20 PM, Richard Hughes wrote: > To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to > add a libtiff hard dep on gnome-color-manager. All distros should > already be installing this by default, but I wanted to check to see if > anyone had any issue with this. > > Speak now, or forever hold your peace! :-) Seems fine... Doesn't eog already depend on libtiff anyway? Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:26:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:26:28 +0000 Subject: Adding a libtiff dep? In-Reply-To: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> Message-ID: <15e53e181002120326q1d693e40wa44d44ab56c5efe0@mail.gmail.com> On 12 February 2010 11:24, Pascal de Bruijn wrote: > Seems fine... Doesn't eog already depend on libtiff anyway? Sure, but eog might not be installed on the live-cd, and g-c-m probably should... Richard. From hughsient at gmail.com Fri Feb 12 11:28:54 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:28:54 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> On 12 February 2010 11:22, Pascal de Bruijn wrote: > I wrote about this here: > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Yes, this entry is very helpful, and I would love to see a large chunk added to the GNOME Color Manager help pages, if you're okay with re-licensing the content. Richard. From dan at berrange.com Fri Feb 12 11:30:51 2010 From: dan at berrange.com (Daniel P. Berrange) Date: Fri, 12 Feb 2010 11:30:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <20100212113051.GA13638@berrange.com> On Fri, Feb 12, 2010 at 11:14:51AM +0000, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: > > Is there any package that collects free (as in speech) ICC profiles? I > > see that Pascal's PPA has one printer, one camera and two or three > > displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. > > > I'd be more than happy to add the profiles I've been doing for the > > printer and monitor to some repository so that users without a > > calibration instrument can just use a profile from the library. I > > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > > Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. IIUC, printer profiles will vary on the set (hardware, ink, driver, paper) so building a library of profiles is quite large task. You could make it more managable by initially concentrating on the printer manufacturer's own recommended brand/combination of ink+paper+drivers Regards, Daniel -- |: http://berrange.com/ -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://freshmeat.net/~danielpb/ -o- http://gtk-vnc.sourceforge.net :| From pmjdebruijn at pcode.nl Fri Feb 12 12:01:33 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 13:01:33 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> Message-ID: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> On Fri, Feb 12, 2010 at 12:28 PM, Richard Hughes wrote: > On 12 February 2010 11:22, Pascal de Bruijn wrote: >> I wrote about this here: >> ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Yes, this entry is very helpful, and I would love to see a large chunk > added to the GNOME Color Manager help pages, if you're okay with > re-licensing the content. No problem, but I'd like my rewrite to be in the help pages :) Not this particular article... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 12:09:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 12:09:23 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> Message-ID: <15e53e181002120409veeecbbcn1f4a04d55b353beb@mail.gmail.com> On 12 February 2010 12:01, Pascal de Bruijn wrote: > No problem, but I'd like my rewrite to be in the help pages :) Cool. Just add text to help/C/gnome-color-manager.xml and format a patch as normal. If you get stuck with docbook, give me a shout. Richard. From alexandre.prokoudine at gmail.com Fri Feb 12 12:54:08 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 12 Feb 2010 15:54:08 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <733f2c731002120454p2f0143ddgf9dfe37e4b9a3713@mail.gmail.com> On Fri, Feb 12, 2010 at 4:42 AM, Pedro C?rte-Real wrote: > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? http://linuxfund.org/ Alexandre From hughsient at gmail.com Fri Feb 12 15:10:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 15:10:10 +0000 Subject: Color correcting projectors? Message-ID: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> In GCM we currently support two types of display profiling. Internal (LVDS) panels are internal to the system, and external panels (DVI and the others) are external to the system. What different settings do we need to do for projectors? We certainly need to give different instructions (which we also need to write), but will argyll just process these like a low-gamut LCD screen? Are there any options we need to add? Richard. From pmjdebruijn at pcode.nl Fri Feb 12 15:25:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 16:25:50 +0100 Subject: Color correcting projectors? In-Reply-To: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> Message-ID: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> On Fri, Feb 12, 2010 at 4:10 PM, Richard Hughes wrote: > In GCM we currently support two types of display profiling. Internal > (LVDS) panels are internal to the system, and external panels (DVI and > the others) are external to the system. > > What different settings do we need to do for projectors? We certainly > need to give different instructions (which we also need to write), but > will argyll just process these like a low-gamut LCD screen? Are there > any options we need to add? Well I think Argyll has a -p option :) And the instructions obviously need to be different, there's a "rule" which states the colorimeter should be 1.5 times the height of the projected image away from the "screen", or something like that... Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 12 20:28:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 12 Feb 2010 21:28:14 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <1266006494.22377.14.camel@athlon> Paul Finnigan p??e v ?t 11. 02. 2010 v 09:54 +0000: > I am a photographer who likes to keep up with the Jones' (MS/Apple). To > do this while running Linux I have had to make compromise after > compromise with regard to 'Free' software. This is my own choice and I > am not complaining about it. Paul said it well, it fits my experience. I had to learn a lot of things to be able to use Linux for my photographic hobby and I hope that soon the photographer's life with Linux be more user friendly. > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If > Richard or anyone else would like to mail me directly my address is paul > at fincc dot com. I have given ?100, maybe a bit more than usual but anyway I hope Richard will not feel obliged to prefer my wishes about GCM - it is a donation, not a wage. Also, no need to return if the target is not reached. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Fri Feb 12 22:00:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 23:00:20 +0100 Subject: Perspective Distortion Compensation Message-ID: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Hi, Currently input profile calibration can fail because a target has even the slightest perspective distortion. Argyll can compensate for that within reason. This patch should enable perspective distortion compensation. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-have-scanin-compensate-for-perspective-distortion.patch Type: text/x-patch Size: 911 bytes Desc: not available URL: From paul at fincc.com Sat Feb 13 01:16:32 2010 From: paul at fincc.com (Paul Finnigan) Date: Sat, 13 Feb 2010 01:16:32 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266006494.22377.14.camel@athlon> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> Message-ID: <1266023792.2313.21.camel@localhost> Milan On Fri, 2010-02-12 at 21:28 +0100, Milan Kn??ek wrote: > I have given ?100, maybe a bit more than usual but anyway I hope Richard > will not feel obliged to prefer my wishes about GCM - it is a donation, > not a wage. Also, no need to return if the target is not reached. What a nice way of putting it! It sounds like you are used to being part of a community, rather than a gathering of geeks. It is amazing but through everyone's (OK in the main Richard's) efforts I feel part of this community without putting anything in myself (I am still attempting to get setup in paypal. I am ancient and not used to money being passed over the ether. Don't worry Richard I will put my money where my mouth is as soon as I can get money into paypal). Thanks to this project I have found many new friends. How can I help? Richard has suggested people to write the help documentation. I am willing but what format and how? Is there a howto I can read anywhere that would help? I am desperate to do more but my skills are in the area of project and service management not coding. -- Paul Finnigan From graeme2 at argyllcms.com Sat Feb 13 01:17:23 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 13 Feb 2010 12:17:23 +1100 Subject: Color correcting projectors? In-Reply-To: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> Message-ID: <4B75FDA3.9050601@argyllcms.com> Pascal de Bruijn wrote: > Well I think Argyll has a -p option :) -p is an instrument config. option, and is currently only applicable to a single instrument, the ColorMunki. You can use other instruments to measure projectors, but they don't have a special mode for it. (I think I'll changed dispcal and dispread to automatically fallback to display mode if the instrument doesn't have a projector mode, to make them a bit more forgiving). Graeme Gill. From hughsient at gmail.com Sat Feb 13 09:17:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:17:06 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266023792.2313.21.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> <1266023792.2313.21.camel@localhost> Message-ID: <15e53e181002130117s270af2b9kcc97bc7ef471c82@mail.gmail.com> On 13 February 2010 01:16, Paul Finnigan wrote: > What a nice way of putting it! It sounds like you are used to being part > of a community, rather than a gathering of geeks. It is amazing but > through everyone's (OK in the main Richard's) efforts I feel part of > this community without putting anything in myself (I am still attempting > to get setup in paypal. I am ancient and not used to money being passed > over the ether. Don't worry Richard I will put my money where my mouth > is as soon as I can get money into paypal). We've very nearly reached the total! I'm nearly at the "amount I can sneak on the shared credit card without the wife noticing" stage :-) > Thanks to this project I have found many new friends. How can I help? > Richard has suggested people to write the help documentation. I am > willing but what format and how? Is there a howto I can read anywhere > that would help? I am desperate to do more but my skills are in the area > of project and service management not coding. Right, then we need to start with some documentation or UI fixes, and then work on from there. My spelling and grammar are notoriously bad, so this is where I need the most help. If you first: * download the git package (using yum, apt-get, or your distro tool) * "clone" the developers checkout. For this you want to follow http://live.gnome.org/Git/Developers -- specifically the project name is gnome-color-manager (you can also ignore 90% of that page, it's overly complicated, but maybe a good read if you want detail) * create you're own personal branch (not on the server): git checkout -b my-playground-branch * Edit the file help/C/gnome-color-manager.xml, copying the syntax (e.g. using for a new paragraph), making the changes you want * "commit" the changes, which basically means you save them, and give them a description: git commit -a -m "Correct the spelling of Colour to Color" --author "Richard Hughes " * get a text file of the changes you want to send to us: "git format-patch master" (this generates 0001-a-file-with-a-peculiar-name.patch) Send the 0001-a-file-with-a-peculiar-name.patch as an attachment to this mailing list. Then you can either go back to the pristine upstream tree "git checkout master" or stay on your private tree and make more changes. You can commit many small changes and then do "git format-patch" and you get files 0001, 0002, 0003, 0004, etc and send them all in one long email. If you break stuff, then you can get rid of all your changes (since the last time you committed them) with "git reset --hard", and you can ensure you've got the latest changes from upstream by doing "git checkout master && git pull --rebase" It sounds complicated, but give it a try and yell when you get stuck. Weekdays I'm on IRC if that helps. Richard. From hughsient at gmail.com Sat Feb 13 09:19:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:19:58 +0000 Subject: Perspective Distortion Compensation In-Reply-To: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> References: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Message-ID: <15e53e181002130119k4b3d9a16j403ff3c4aa2f4c31@mail.gmail.com> On 12 February 2010 22:00, Pascal de Bruijn wrote: > This patch should enable perspective distortion compensation. Applied, thanks. Richard. From pmjdebruijn at pcode.nl Sat Feb 13 10:43:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 11:43:44 +0100 Subject: Bug #605259: Colorimeter name in profile description Message-ID: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Hi, Currently on my Ubuntu Karmic system, the colorimeter name still isn't getting into the profile description... Could you give me any pointer how the colorimeter is resolved? And where I should look into the sources? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 14:09:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 14:09:51 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Message-ID: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> On 13 February 2010 10:43, Pascal de Bruijn wrote: > Currently on my Ubuntu Karmic system, the colorimeter name still isn't > getting into the profile description... Hmm, I'm getting "Huey" prepended to my profile. > Could you give me any pointer how the colorimeter is resolved? And > where I should look into the sources? Well, take a look at src/gcm-color-device.c and make sure that the model and vendor are being set correctly. It's possible you need to add: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="usb-db %p" to your 55-Argyll.rules file, if your device doesn't have an entry in the kernel USB driver. That's what I've done in hargyll, and if it fixes it for you too, I'll push this patch to Graeme. Richard From pmjdebruijn at pcode.nl Sat Feb 13 19:40:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 20:40:24 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> On Fri, Feb 12, 2010 at 12:22 PM, Pascal de Bruijn wrote: > On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: >> On 12 February 2010 10:54, Pedro C?rte-Real wrote: >>> One thing I >>> haven't done yet is profiling my camera. How is that done and what is >>> the benefit? I have a Sony A700 DSLR. >> >> That's something you really want to do. We probably want to add a >> whole load of text in the help file in how to do this (sunny day, etc) >> but using GCM the process itself should be pretty easy. > > I wrote about this here: > > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Though the article is dated, and should be revised... I did make a few > new discoveries... > > For example, I only recently noticed that strobes actually work well > as reference light for generic profiles... > > I'm probably going to do a new blog post over the weekend... > > Here are some generic tips van raw photography with UFRaw in general: > > ?http://blog.pcode.nl/2009/08/23/ufraw-faq/ > > Most of it should apply to other dcraw based applications as well. I'm rewriting my article as I type this, it should already be accessible as a preview: http://blog.pcode.nl/?p=551&preview=true Any comments before I publish? Any thing not clear? If all goes well (I still need to do some more testing), this article can be reworked into GCM help. Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 21:27:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 21:27:34 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <15e53e181002131327l76d8dc0du282ca3c5a5be4423@mail.gmail.com> On 10 February 2010 20:01, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. We've reached the total! Thanks guys, I feel very humbled. Thanks. ColorMunki Photo is ordered, and will arrive in about a weeks time. Richard. From hughsient at gmail.com Sun Feb 14 20:56:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 14 Feb 2010 20:56:10 +0000 Subject: Request for colorimeter figures Message-ID: <15e53e181002141256t1c39960dle71b65839ca6d451@mail.gmail.com> Hey guys, I've added support to GCM today to display images to help the user attach the colorimeter device to the screen, and to set it to correct mode. I've attached two images as examples. If anybody is interested in drawing pictures (or improving mine) it would be very welcome. I don't mind how many images we add. Ideally we should show images of the most common colorimeters in existence, and how to switch things to the correct modes. You'll have to create SVG figures yourself (I used inkscape) and obviously not include any trademarks. If you're a worse artist than me, feel free to send a photo of the colorimeter attached to the screen, and switching between different modes and one of us geeks on list can convert this to a SVG. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: huey-attach.svg Type: image/svg+xml Size: 61010 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: munki-projector.svg Type: image/svg+xml Size: 66407 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 15 01:23:01 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 02:23:01 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> Message-ID: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> On Sat, Feb 13, 2010 at 3:09 PM, Richard Hughes wrote: > On 13 February 2010 10:43, Pascal de Bruijn wrote: >> Currently on my Ubuntu Karmic system, the colorimeter name still isn't >> getting into the profile description... > > Hmm, I'm getting "Huey" prepended to my profile. > >> Could you give me any pointer how the colorimeter is resolved? And >> where I should look into the sources? > > Well, take a look at src/gcm-color-device.c and make sure that the > model and vendor are being set correctly. It's possible you need to > add: > > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="usb-db %p" > > to your 55-Argyll.rules file, if your device doesn't have an entry in > the kernel USB driver. That's what I've done in hargyll, and if it > fixes it for you too, I'll push this patch to Graeme. It's not fixing it for me now... But I don't think I have the usb-db utility installed... Where should I have gotten it from? Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 11:34:49 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 11:34:49 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> Message-ID: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> On 15 February 2010 01:23, Pascal de Bruijn wrote: > It's not fixing it for me now... But I don't think I have the usb-db > utility installed... Where should I have gotten it from? Any modern udev should have it. Use "udevadm monitor" to monitor the device events as the device is plugged in. Richard. From pmjdebruijn at pcode.nl Mon Feb 15 11:36:12 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 12:36:12 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> Message-ID: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: > On 15 February 2010 01:23, Pascal de Bruijn wrote: >> It's not fixing it for me now... But I don't think I have the usb-db >> utility installed... Where should I have gotten it from? > > Any modern udev should have it. Use "udevadm monitor" to monitor the > device events as the device is plugged in. Indeed $ dpkg -L udev | grep usb-db /lib/udev/usb-db But it's not in my path, I'm not sure whether that matters? I'll try udev monitor later today. Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 20:34:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 20:34:26 +0000 Subject: Adding support for xsane Message-ID: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> I've coded some initial support for xsane-based application in a private branch. It basically writes the right thing in the per-user xsane directories for the system and device settings. I'm not sure whether to merge it to master or not, as it's pretty hacky code. Ideally we would talk to easy-scan / gnome-scan in the future using a nice DBus interface, but I think that's a few years away. It does not depend on sane (that's a separate branch...) and if you don't use xsane then the file just gets written and nothing uses it. So, what do you guys think? Richard. From knizek.confy at volny.cz Mon Feb 15 21:19:05 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 15 Feb 2010 22:19:05 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> Message-ID: <1266268745.6707.9.camel@athlon> Pascal de Bruijn p??e v So 13. 02. 2010 v 20:40 +0100: > I'm rewriting my article as I type this, it should already be > accessible as a preview: > > http://blog.pcode.nl/?p=551&preview=true > > Any comments before I publish? Any thing not clear? > Pascal - the page is "not found". I guess you would actually have to post it to make it available to public. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 15 22:09:10 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 16 Feb 2010 01:09:10 +0300 Subject: Adding support for xsane In-Reply-To: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> Message-ID: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> On 2/15/10, Richard Hughes wrote: > Ideally we would talk to easy-scan / gnome-scan in the future using a > nice DBus interface, but I think that's a few years away. Robert Ancell blogged recently that he is going to implement color management after 1.0, and his is now in post 0.9.0 bugfixing mode. So it's probably not that bad :) Alexandre From hughsient at gmail.com Mon Feb 15 22:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 22:16:56 +0000 Subject: Adding support for xsane In-Reply-To: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> Message-ID: <15e53e181002151416p37413a9je110eab793646198@mail.gmail.com> On 15 February 2010 22:09, Alexandre Prokoudine wrote: > Robert Ancell blogged recently that he is going to implement color > management after 1.0, and his is now in post 0.9.0 bugfixing mode. So > it's probably not that bad :) Cool. What we need him to do is: * Provide a method to scan a target without applying any icc profiles at all, so we can use it to calibrate the device. * Get the default icc profile assigned by GCM using the udev path or the SANE id, for normal scans. * Tag the resulting scans with the assigned ICC profile Should be no more than an afternoons hacking :-) Richard. From paul at fincc.com Tue Feb 16 00:45:54 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 00:45:54 +0000 Subject: Camera Support Message-ID: <1266281154.2768.8.camel@localhost> Hi I decided to attempt to use a profile with my camera. The camera does not appear on the list of devices, even when it is plugged in. Am I missing something? I can import my profiles but I cannot assign them to a device. The camera is a Nikon D700. Gnome recognises the camera and allows me to open a nautilus viewer on the memory card, open photographs etc. I can see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b0 ProdID=0422 Rev= 1.00 S: Manufacturer=NIKON S: Product=NIKON DSC D700 S: SerialNumber=000002034583 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=usbfs E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms If I run gcm in verbose mode: TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 So we see the camera connect. Am I missing something? I am running off a copy from the GIT -- Paul Finnigan Finnigan Computer Consultants Ltd. From hughsient at gmail.com Tue Feb 16 09:26:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 09:26:26 +0000 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> On 16 February 2010 00:45, Paul Finnigan wrote: > If I run gcm in verbose mode: > > TI:00:40:05 FI:gcm-colorimeter.c ? ? ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:05 ? ? FI:gcm-colorimeter.c ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > > So we see the camera connect. Am I missing something? Is that all you get when you connect the camera? Could you attach the output from "udevadm monitor" when you plug in the device please. I'm a little surprised it doesn't work, given my D60 works fine. Thanks. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 11:54:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 12:54:27 +0100 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > Hi > > I decided to attempt to use a profile with my camera. The camera does > not appear on the list of devices, even when it is plugged in. Am I > missing something? I can import my profiles but I cannot assign them to > a device. Currently assigning camera profiles in GCM has no real function yet, since the RAW converters don't use this information. > The camera is a Nikon D700. Gnome recognises the camera and allows me to > open a nautilus viewer on the memory card, open photographs etc. I can > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > snip snip > > So we see the camera connect. Am I missing something? > > I am running off a copy from the GIT It works just fine with my EOS 400D as well... Also does your D700 have a recent firmware? Regards, Pascal de Bruijn From paul at fincc.com Tue Feb 16 11:57:31 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 11:57:31 +0000 Subject: Camera Support In-Reply-To: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> Message-ID: <1266321451.6701.12.camel@localhost> Richard On Tue, 2010-02-16 at 09:26 +0000, Richard Hughes wrote: > On 16 February 2010 00:45, Paul Finnigan wrote: > > If I run gcm in verbose mode: > > > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > > > So we see the camera connect. Am I missing something? > > Is that all you get when you connect the camera? Could you attach the > output from "udevadm monitor" when you plug in the device please. I'm > a little surprised it doesn't work, given my D60 works fine. Thanks. > > Richard. That is all I get from gcm. I am running Fedora 12 and have compiled gcm from the GIT. I only ever connect my camera to copy files to disc. I never ever read them directly with an application, or not in my normal workflow. That is I only use my Nikon as a (very expensive) memory stick! OK Fedora uses gphoto2 and gvfs. As requested 'udevadm moniotor' when connecting the camera gives: [paul at ewing ~]udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266321215.801858] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) KERNEL[1266321215.802262] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) UDEV [1266321215.813200] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) UDEV [1266321215.821229] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) Nautilus then lets me view photos using: gphoto2://[usb:001,009]/DCIM/100ND700 Thanks -- Paul Finnigan From paul at fincc.com Tue Feb 16 12:19:26 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 12:19:26 +0000 Subject: Camera Support In-Reply-To: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> Message-ID: <1266322766.6701.21.camel@localhost> Pascal On Tue, 2010-02-16 at 12:54 +0100, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > > Hi > > > > I decided to attempt to use a profile with my camera. The camera does > > not appear on the list of devices, even when it is plugged in. Am I > > missing something? I can import my profiles but I cannot assign them to > > a device. > > Currently assigning camera profiles in GCM has no real function yet, > since the RAW converters don't use this information. I knew that, which is why I had not tired it until now. I am looking at the help pages as I had (stupidly) volunteered and wanted to show an input device on the menu. My current scanner a Canon Lide 500 does not work with Sane so I cannot show that. > > The camera is a Nikon D700. Gnome recognises the camera and allows me to > > open a nautilus viewer on the memory card, open photographs etc. I can > > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > > > > snip snip > > > > > So we see the camera connect. Am I missing something? > > > > I am running off a copy from the GIT > > It works just fine with my EOS 400D as well... Also does your D700 > have a recent firmware? I would guess not. I have had it over 12 months, and have never had a need to update the firmware. If I need to I will update the firmware. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Tue Feb 16 12:29:45 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 13:29:45 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> Message-ID: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> On Mon, Feb 15, 2010 at 12:36 PM, Pascal de Bruijn wrote: > On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: >> On 15 February 2010 01:23, Pascal de Bruijn wrote: >>> It's not fixing it for me now... But I don't think I have the usb-db >>> utility installed... Where should I have gotten it from? >> >> Any modern udev should have it. Use "udevadm monitor" to monitor the >> device events as the device is plugged in. > > Indeed > > $ dpkg -L udev | grep usb-db > /lib/udev/usb-db > > But it's not in my path, I'm not sure whether that matters? I changed the udev-rule to include the full path of usb-db: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="/lib/udev/usb-db %p" Does this need to be in a particular place in 55-Argyll.rules? I attached the full file. After making the above change, I rebooted my system, and ran the udevadm monitor while plugging in the Huey. The results are attached. Regards, Pascal de Bruijn -------------- next part -------------- pmjdebruijn at biovore:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266323110.972649] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323110.975186] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323111.064958] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323111.106596] add /module/usbhid (module) KERNEL[1266323111.108080] add /bus/hid/drivers/generic-usb (drivers) UDEV [1266323111.108125] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323111.108145] add /bus/usb/drivers/hiddev (drivers) KERNEL[1266323111.108161] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.108519] add /bus/usb/drivers/hiddev (drivers) UDEV [1266323111.108804] add /module/usbhid (module) UDEV [1266323111.109292] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.110702] add /bus/hid/drivers/generic-usb (drivers) KERNEL[1266323117.762463] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323117.762504] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323117.763909] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323117.766370] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.321652] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.328367] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323121.338002] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323121.341140] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) pmjdebruijn at biovore:~$ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG -------------- next part -------------- A non-text attachment was scrubbed... Name: 55-Argyll.rules Type: application/octet-stream Size: 1953 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 16 21:43:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 21:43:31 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> Message-ID: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> On 16 February 2010 12:29, Pascal de Bruijn wrote: > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="/lib/udev/usb-db %p" Hmm, I don't think you need to include the full path this. > Does this need to be in a particular place in 55-Argyll.rules? I > attached the full file. > > After making the above change, I rebooted my system, and ran the > udevadm monitor while plugging in the Huey. The results are attached. Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I assume this is a Huey: 0971 Gretag-Macbeth AG 2005 Huey If it's not a Huey, then we have a problem, and we need to add an entry to usb.ids. See http://www.linux-usb.org/usb-ids.html if this is the case. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 21:56:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 22:56:10 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> Message-ID: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: > On 16 February 2010 12:29, Pascal de Bruijn wrote: >> # color calibration device >> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >> IMPORT{program}="/lib/udev/usb-db %p" > > Hmm, I don't think you need to include the full path this. Well the other lines include full paths, it would seem good practice consistency-wise. >> Does this need to be in a particular place in 55-Argyll.rules? I >> attached the full file. >> >> After making the above change, I rebooted my system, and ran the >> udevadm monitor while plugging in the Huey. The results are attached. > > Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like > ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I > assume this is a Huey: > > 0971 ?Gretag-Macbeth AG > ? ? ? ?2005 ?Huey I updated the usb database, and guess what: $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG ID_MODEL_FROM_DATABASE=Huey Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:13:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:13:17 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <4c2c37f91002161413w182c491cu2f8a269bf6bd91c4@mail.gmail.com> On Tue, Feb 16, 2010 at 10:56 PM, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: >> On 16 February 2010 12:29, Pascal de Bruijn wrote: >>> # color calibration device >>> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >>> IMPORT{program}="/lib/udev/usb-db %p" >> >> Hmm, I don't think you need to include the full path this. > > Well the other lines include full paths, it would seem good practice > consistency-wise. > >>> Does this need to be in a particular place in 55-Argyll.rules? I >>> attached the full file. >>> >>> After making the above change, I rebooted my system, and ran the >>> udevadm monitor while plugging in the Huey. The results are attached. >> >> Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like >> ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I >> assume this is a Huey: >> >> 0971 ?Gretag-Macbeth AG >> ? ? ? ?2005 ?Huey > > I updated the usb database, and guess what: > > $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 > ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG > ID_MODEL_FROM_DATABASE=Huey Ugh, I just calibrated my screen and it worked like a charm... Please push the udev rule to Graeme. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:31:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:31:38 +0100 Subject: [PATCH] New USB ID: X-Rite/Gretag-MacBeth ColorMunki Message-ID: <4c2c37f91002161431l7989a672gd240def3bbcf5a23@mail.gmail.com> Hi, The included patch has the USB ID for: http://www.colormunki.com/ The device is a spectrophotometer from X-Rite which recently acquired Gretag-Macbeth. I've tested using udev's usb-db, and the lookup works with my device. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: usb-ids-colormunki.patch Type: text/x-patch Size: 312 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 17 09:33:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 09:33:21 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <15e53e181002170133j3c968710y4dc7996dc31bc5b@mail.gmail.com> On 16 February 2010 21:56, Pascal de Bruijn wrote: > Well the other lines include full paths, it would seem good practice > consistency-wise. I disagree, but it shouldn't hurt as even on 64 bit the early udev boot is in /lib, not /lib64. Richard. From hughsient at gmail.com Wed Feb 17 14:05:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 14:05:27 +0000 Subject: Adding printer profiling support Message-ID: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> In a few days time, my nice lovely ColorMunki should be delivered. Before it is, I figured I should get up to speed on how to profile printers, so we know what UI to add to GCM, and so I can get up to speed quickly. So. Does anybody have any hints, tips or suggestions on how to calibrate a printer. Device specific options (e.g. "The ColorMunki works really well with -f234 -g567") are more than welcome, as we already know the colorimeter device type. In particular, we need to support printing to 6x4 inch cards, A4 and letter paper. I would love to integrate this better with CUPS (using the GTK print dialog for instance) than what we can do on the command line. We'll also need scans of the patches sheets that we send out, so we can show the user _how_ to scan in the patches. We'll also probably need a timer for "waiting for the ink to dry" and that sort of thing. Ideas very welcome. Thanks, Richard. From hughsient at gmail.com Wed Feb 17 19:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 19:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> Message-ID: <15e53e181002171147u290e197fnfe1e857f62b6723a@mail.gmail.com> On 17 February 2010 17:20, Pascal de Bruijn wrote: > J?rg Rosenkranz privately submitted an image of the LaserSoftDCPro > target to me. The attached patch should make it available for GCM. Applied, thanks. Richard. From pedro at pedrocr.net Thu Feb 18 04:50:09 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Wed, 17 Feb 2010 20:50:09 -0800 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: > In a few days time, my nice lovely ColorMunki should be delivered. > Before it is, I figured I should get up to speed on how to profile > printers, so we know what UI to add to GCM, and so I can get up to > speed quickly. > > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Here is my experience with the Munki from my notes. I've used it successfully to both profile a Dell U2410 LCD screen and an Epson R2880. The LCD profiling should work already but I ended up using the tools directly because g-c-m was failing to interact correctly with the argyll tools when they asked to change the position of the device. I think this has been fixed but haven't checked. Anyway for the printing profiling my steps were: 1 - Generate a set of color patches $argyll-targen -f 900 -v -d2 -c -A.8 This gave good results in the end. I did a first round of profiling with 450 patches and that was used as BestPreviousProfile. For the first round it would be instead: $argyll-targen -f 450 -v -d2 In general the number of patches to create is a judgment call. I don't know how we can present this option to the user. Maybe doing the calculation in reverse and asking him how many sheets he is willing to print and scan and then giving him an idea of how good a profile that generates. To then actually generate the files to print: $ printtarg -t -v -iCM -pLetter "Letter" should obviously be changed to whatever paper the user wants to use. The -iCM generates normally sized patches for the Munki, which will require many sheets of paper to fit the 900 patches. See bellow for a discussion of the hack I did to avoid this. 2. Print out the patches I printed the resulting tiff files with PhotoPrint. I believe it uses Gutenprint directly to drive the printer and is the only solution I know right now that can actually apply the ICC profile when printing later. The important thing here is to set the Gutenprint setting "Color Correction" to "Uncorrected", and then any of the image settings for the setup being used (type of paper, resolution, dithering, etc). 3. Read back the patches $chartread Munki will need to first be set to the self calibrate position, then to the profiling position and then run through each of the patch lines in turn while pressing its button. chartread asks for each of the lines and will ask for them again if there is any error. The interface needs to expose this. The last version allows you to reread a patch line at will. I wonder if it would be possible to have some kind of idea of how good the reads were and advise the user to reread one of the lines if it is found to not be too good. 4. Generate the profile $ colprof -v -D"" -qm -S -cmt -dpp This runs by itself without problems. The specific flags are arguable of course. I'm curious as to how changing -q (quality) to high or ultra changes the profile. Some considerations: - Some decent automatic naming would be nice - Selecting the source profile would be nice too (defaulting to sRGB) and possibly allowing the user to later generate the same profile with another profile (e.g. AdobeRGB) as source might be useful. - All the colprof settings can be changed without running the process from the beginning again. I wonder if g-c-m should have the notion of "Profiling runs" from which several actual profiles can be created. This would solve the sRGB/AdobeRGB selection as well. - Colprof outputs a final result with the mean and maximum error of the profile. It would be great to give this result to the user in plain English. Telling him the profile is "Poor/Fair/Good/Excellent" or even a result out of 100. The generated profile works in PhotoPrint. I assume it would also work to transform an image before sending it to the general CUPS pipeline. In theory the generated profile is only valid for the specific set of settings used for the printer. In practice using the same profile on even a different but similar paper is probably better than none at all. And using it at a different resolution on the same paper may very well be decent as well. I have no idea. > In particular, we need to support printing to 6x4 inch cards, A4 and > letter paper. I would love to integrate this better with CUPS (using > the GTK print dialog for instance) than what we can do on the command > line. We'll also need scans of the patches sheets that we send out, so > we can show the user _how_ to scan in the patches. We'll also probably > need a timer for "waiting for the ink to dry" and that sort of thing. My only other comment about the process is that using the Munki with default size patches is an incredible waste of paper and ink. In the argyll mailing list someone pointed out some user's hack on dpreview so I built one myself: http://pedrocr.net/MunkiHelper.jpg I'm not in any way suggesting that users should be expected to build one of these but I would like to be able to configure g-c-m to have not only the configuration for the normal Color Munki but also this hack. The only difference is to change the -iCM flag to printtarg to the -ii1, making the patches much smaller (by printing a sheet as if it was for another instrument). I know Pascal disagrees though. I share the sentiment of wanting to make this as simple to the user as possible. However my experience with this is that if we don't allow the user to fiddle with some of the advanced settings, whenever he hits a speed bump the only option is to fall back on argyll command line tools and totally bypass g-c-m. That doesn't seem like much of a solution either. My suggestion would be to have a set of default settings for each of the supported instruments that work in a straightforward way and then an "Advanced..." button to go and customize the settings. Cheers, Pedro From hughsient at gmail.com Thu Feb 18 09:28:41 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 18 Feb 2010 09:28:41 +0000 Subject: gnome-color-management test day Message-ID: <15e53e181002180128p9c9e977g8619a1518f86afd7@mail.gmail.com> Guys, We've got a GNOME Color Management test day happening today: https://fedoraproject.org/wiki/Test_Day:2010-02-18_Color_management It's very Fedora-centric, but I'm guessing as most of the testing and bugs will be common between distros, I guess it makes you more than welcome to join in. I'll be in the #fedora-test-day channel (on freenode) all day, answering questions and fixing bugs. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 18 17:57:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 18 Feb 2010 18:57:20 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> Message-ID: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: >> In a few days time, my nice lovely ColorMunki should be delivered. >> Before it is, I figured I should get up to speed on how to profile >> printers, so we know what UI to add to GCM, and so I can get up to >> speed quickly. >> >> So. Does anybody have any hints, tips or suggestions on how to >> calibrate a printer. Device specific options (e.g. "The ColorMunki >> works really well with -f234 -g567") are more than welcome, as we >> already know the colorimeter device type. > > Here is my experience with the Munki from my notes. I've used it > successfully to both profile a Dell U2410 LCD screen and an Epson > R2880. The LCD profiling should work already but I ended up using the > tools directly because g-c-m was failing to interact correctly with > the argyll tools when they asked to change the position of the device. > I think this has been fixed but haven't checked. I didn't have any such issues, so I guess this has been fixed for a while. > Anyway for the printing profiling my steps were: > > 1 - Generate a set of color patches > > $argyll-targen -f 900 -v -d2 -c -A.8 The -c option is very advanced, and requires a lot of logic in GCM in determining what the best previous profile actually was... Or it requires the user to select their best previous profile, and if they select the wrong profile (or GCM automatically selects the wrong profile) it all goes horribly wrong... So in the short run using preconditioning (-c) probably will do more harm than good... This could very well be reconsidered when GCM matures. The 900 patch count is probably way too high for default, since we don't want to waste 4 sheets of expensive paper _by default_. Especially since some packages of expensive paper come in per 10 sheets packages. We'd be wasting 40% :) Please remember the ColorMunki vendor software only uses 90 or so patches by default, so having 210/190 (1x A4/Letter) is a huge improvement... Thus far I've had excellent results using only 210 patches with no preconditioning, and it only requires a single sheet of paper. So I'd highly recommend to use this as default. Anything that requires more than a single sheet of paper should probably go in high quality/advanced mode... Also I'd recon we should not really talk about patch counts, but the amount of paper... For for A4 we would use 210/420/630/840/1050 patches, or for Letter 190/380/470/660? > To then actually generate the files to print: > > $ printtarg -t -v -iCM -pLetter printtarg has a -h option, which will generate smaller patches for the ColorMunki, which fits 210 patches onto A4 instead of 90 or so... This option basically shrinks the rows to a third size, so the ColorMunki is exactly as wide as 3 rows with the aperture exactly over the middle row. > 2. Print out the patches > > I printed the resulting tiff files with PhotoPrint. I believe it uses > Gutenprint directly to drive the printer and is the only solution I > know right now that can actually apply the ICC profile when printing > later. The important thing here is to set the Gutenprint setting > "Color Correction" to "Uncorrected", and then any of the image > settings for the setup being used (type of paper, resolution, > dithering, etc). Not everybody uses a gutenprint supported printer... :) It's basically possible to profile any application with any printer driver, as long as the app nor the printer driver do any dynamic transforms... Your case is very optimal... HPIJS for example does not have an uncorrected mode, but the output is static, so it can be profiled. I apply my printer profile in F-Spot, so I also used F-Spot to print my target images... In theory this should not be very relevant. > 3. Read back the patches > > $chartread > > Munki will need to first be set to the self calibrate position, then > to the profiling position and then run through each of the patch lines > in turn while pressing its button. chartread asks for each of the > lines and will ask for them again if there is any error. The interface > needs to expose this. The last version allows you to reread a patch > line at will. I wonder if it would be possible to have some kind of > idea of how good the reads were and advise the user to reread one of > the lines if it is found to not be too good. I don't think argyll does this yet... But it would be cool indeed... > 4. Generate the profile > > $ colprof -v -D"" -qm -S > -cmt -dpp Using -qm for 210 is an excellent default, but when we go into advanced mode with > 500 patches, we should probably use -qh. I've never used the -S -cmt -dpp options, so I highly doubt they are required... We shouldn't pass random arguments unless strongly indicated that we should. Otherwise we should trust Argyll's defaults... > This runs by itself without problems. The specific flags are arguable > of course. I'm curious as to how changing -q (quality) to high or > ultra changes the profile. Some considerations: Graeme highly discourages the ultra mode, in his words: ultra mode exists to prove that nothing above high is required. > - Some decent automatic naming would be nice > - Selecting the source profile would be nice too (defaulting to sRGB) > and possibly allowing the user to later generate the same profile with > another profile (e.g. AdobeRGB) as source might be useful. Huh? printer profiles usually use LAB as Profile Connection Space, this has nothing to do with sRGB/AdobeRGB. The pipeline: Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> printer native RGB/CMYK -> hpijs/gutenprint > - All the colprof settings can be changed without running the process > from the beginning again. I wonder if g-c-m should have the notion of > "Profiling runs" from which several actual profiles can be created. > This would solve the sRGB/AdobeRGB selection as well. I'd probably be against this too (at least for the short run). This will complicate the user interface (and GCM's codebase), and probably won't be used much by most people, so this is not in line with GNOME's goals. In the long run we could re-evaluate this... > - Colprof outputs a final result with the mean and maximum error of > the profile. It would be great to give this result to the user in > plain English. Telling him the profile is "Poor/Fair/Good/Excellent" > or even a result out of 100. That would be nice... I'd stick to Poor/Fair/Good/Excellent, everybody understands that. Though we need to be very careful about how we determine what is what. > The generated profile works in PhotoPrint. I assume it would also work > to transform an image before sending it to the general CUPS pipeline. > In theory the generated profile is only valid for the specific set of > settings used for the printer. In practice using the same profile on > even a different but similar paper is probably better than none at > all. And using it at a different resolution on the same paper may very > well be decent as well. I have no idea. > >> In particular, we need to support printing to 6x4 inch cards, A4 and >> letter paper. I would love to integrate this better with CUPS (using >> the GTK print dialog for instance) than what we can do on the command >> line. We'll also need scans of the patches sheets that we send out, so >> we can show the user _how_ to scan in the patches. We'll also probably >> need a timer for "waiting for the ink to dry" and that sort of thing. >From most sources I gather a minimum od 15 minutes of drying-time should be enough for most cases. > My only other comment about the process is that using the Munki with > default size patches is an incredible waste of paper and ink. In the > argyll mailing list someone pointed out some user's hack on dpreview > so I built one myself: > > http://pedrocr.net/MunkiHelper.jpg Are you actually aware of the -h option for printtarg? Graeme semi-solved this issue long ago... My current workflow is like this # argyll-targen -v -d 2 -g 20 -f 210 test # printtarg -v -i CM -h -t 300 -p A4 test # chartread -v test # colprof -v -A "bla" -M "bla" -D "bla" -C "bla" -a l -q m test Regards, Pascal de Bruijn From knizek.confy at volny.cz Thu Feb 18 18:46:34 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Thu, 18 Feb 2010 19:46:34 +0100 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> Message-ID: <1266518794.18345.36.camel@athlon> Pascal de Bruijn p??e v ?t 18. 02. 2010 v 18:57 +0100: > On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > > - Selecting the source profile would be nice too (defaulting to sRGB) > > and possibly allowing the user to later generate the same profile with > > another profile (e.g. AdobeRGB) as source might be useful. > > Huh? printer profiles usually use LAB as Profile Connection Space, > this has nothing to do with sRGB/AdobeRGB. > > The pipeline: > Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> > printer native RGB/CMYK -> hpijs/gutenprint It looks like Pedro was referring to -S option of colprof: Argyllcms docs quote [1]: -- Where the resulting profile will be used conventionally (ie. using collink -s, or cctiff or most other "dumb" CMMs) it is important to specify that gamut mapping should be computed for the output (B2A) perceptual and saturation tables. This is done by specifying a device profile as the parameter to the colprof -S flag. When you intend to create a "general use" profile, it can be a good technique to specify the source gamut as the opposite type of profile to that being created, i.e. if a printer profile is being created, specify a display profile (e.g. sRGB) as the source gamut. If a display profile is being created, then specify a printer profile as the source (e.g. SWOP). -- Argyllcms docs quote [2]: ... [Note that Shaper/Matrix profiles are always Colorimetric intent, since there is only a single transformation, and it does not have the necessary flexibility to accommodate gamut mapping.] ... So to construct the perceptual and saturation intent mapping tables, a source profile or source gamut needs to be specified, so that a gamut mapping can be constructed. -- [2] http://www.argyllcms.com/doc/Scenarios.html#PP5 [1] http://www.argyllcms.com/doc/iccgamutmapping.html I do not have much experience on this topic... regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Fri Feb 19 10:41:19 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 10:41:19 +0000 Subject: Help update Message-ID: <1266576079.2381.5.camel@localhost> Richard Attached is my first attempt to help. Sorry it has taken me so long but I had a lot of reading to do about Gnome documentation. I have only altered the Introduction and Usage sections. I will set about the other sections if this is acceptable. If anyone wants to tell me where I am going wrong then please do. I admit this little effort has made me realise just what Richard is doing! There is more to gcm than I expected. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Correct-help-Intro-and-Usage.patch Type: text/x-patch Size: 3064 bytes Desc: not available URL: From hughsient at gmail.com Fri Feb 19 11:02:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 11:02:43 +0000 Subject: Help update In-Reply-To: <1266576079.2381.5.camel@localhost> References: <1266576079.2381.5.camel@localhost> Message-ID: <15e53e181002190302r1ffa130ay22236854ce8574d3@mail.gmail.com> On 19 February 2010 10:41, Paul Finnigan wrote: > Attached is my first attempt to help. Sorry it has taken me so long but > I had a lot of reading to do about Gnome documentation. Sure, it takes a fair bit to get up to speed. > I have only altered the Introduction and Usage sections. I will set > about the other sections if this is acceptable. I've committed your patch, thanks. One thing to note (any maybe repair in your next patch :-) is the trailing whitespace issue. git doesn't like trailing whitespace (tabs and spaces at the end of the line) and highlights them in red. Could you please make sure future patches don't add more trailing whitespace please? Thanks. > If anyone wants to tell me where I am going wrong then please do. I > admit this little effort has made me realise just what Richard is doing! Heh. Thanks. > There is more to gcm than I expected. Sure, and it's getting bigger every day. To do the printer profiling properly I'm having to deal with print dialogs and rendering to random cairo surfaces. Both things that were not in the original scope for GCM... Anyway, keep up the good work. Thanks. Richard. From paul at fincc.com Fri Feb 19 12:48:30 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 12:48:30 +0000 Subject: Selecting Device Profiles Message-ID: <1266583710.2381.14.camel@localhost> Hi I was just looking at improving the preferences help page and I came across a small UI problem someone else may like to look at. If the device profile is not loaded you can select "Other profile..." this takes you to the profile install routine, via a Gnome file select window. That is good. But once the profile is installed I have to go back to the Color Profile selector and select it. I think what should happen is: 1. If the profile is good for the device it should be selected. 2. If the profile is not good for the device then a message should be issued and the device profile is unaltered. What should never happen is that the "Other profile" selection remains against the device. Another point is that for a new device the profile should be "None" rather than blank. This will keep it consistent with selecting None from the profile list. What does everyone else think? -- Paul Finnigan From hughsient at gmail.com Fri Feb 19 13:05:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 13:05:10 +0000 Subject: Selecting Device Profiles In-Reply-To: <1266583710.2381.14.camel@localhost> References: <1266583710.2381.14.camel@localhost> Message-ID: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> On 19 February 2010 12:48, Paul Finnigan wrote: > If the device profile is not loaded you can select "Other profile..." > this takes you to the profile install routine, via a Gnome file select > window. That is good. But once the profile is installed I have to go > back to the Color Profile selector and select it. That's just a bug: commit 5c4731bce32ce55467449d793b6a508b48b09eda Author: Richard Hughes Date: Fri Feb 19 13:03:14 2010 +0000 trivial: Set the profile we chose as 'Other' as the current device default > I think what should happen is: > > 1. If the profile is good for the device it should be selected. Sure, agreed. > 2. If the profile is not good for the device then a message should be > issued and the device profile is unaltered. We need to add that. > What should never happen is that the "Other profile" selection remains > against the device. What happens if the device chosen is unsuitable? Go back to the previous profile, or 'None'? Richard. From paul at fincc.com Fri Feb 19 13:15:29 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 13:15:29 +0000 Subject: Selecting Device Profiles In-Reply-To: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> References: <1266583710.2381.14.camel@localhost> <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> Message-ID: <1266585329.2381.16.camel@localhost> Richard On Fri, 2010-02-19 at 13:05 +0000, Richard Hughes wrote: > What happens if the device chosen is unsuitable? Go back to the > previous profile, or 'None'? > > Richard. I would suggest the previous profile. The warning can then say that the profile is unsuitable and the setting has not been altered. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Fri Feb 19 23:03:26 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 00:03:26 +0100 Subject: gcm-git not building (as package) Message-ID: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Hi, There are some trivial problems with gcm-git: cc1: warnings being treated as errors gcm-calibrate.c: In function 'gcm_calibrate_device': gcm-calibrate.c:654: error: unused variable 'dialog' make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Sat Feb 20 00:14:20 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:14:20 +0300 Subject: Small thumbnails of targets In-Reply-To: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> Message-ID: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> On 2/10/10, Lars Tore Gustavsen wrote: >> This would be a great way to help out gnome-color-manager if you are >> not comfortable with coding. The list of target types I need as >> thumbnails are: >> >> CMP_Digital_Target-3 >> CMP_DT_003 >> ColorChecker >> ColorCheckerDC >> ColorCheckerSG >> Hutchcolor >> i1_RGB_Scan_1.4 Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) Alexandre From alexandre.prokoudine at gmail.com Sat Feb 20 00:10:43 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:10:43 +0300 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <733f2c731002191610q5bea9bd2l347287afcf42abc9@mail.gmail.com> On 2/17/10, Richard Hughes wrote: > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Just in case, make sure you've seen GPLin (http://bit.ly/aTmim3). Maybe it has some useful code for you. Alexandre From pedro at pedrocr.net Fri Feb 19 21:01:20 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 19 Feb 2010 13:01:20 -0800 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> Message-ID: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> (I'm CC'ing this to the list to keep the discussion there, hope it's ok) On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > Some applications (even commercial ones) don't support LUT display > profiles properly. > > Argyll can generate Matrix+LUT profiles, but then you have the problem > that one app uses the matrix and the other the LUT, this can give odd > inconsistencies... So it's not recommended for defaults... Makes sense. Do you know if I'll be ok with a LUT using GIMP/f-spot/ufraw? I should probably try g-c-m again to see what profile it comes up with. When I did the LUT one with 2000 patches the result seemed to have a fair amount of extra contrast that looked good. Don't know where that came from. > This is true, however, 210 is already a _big_ improvement over 90... Sure. Although I need to test it again as it was too little for me before. But here is Graeme Gill's opinion on number of needed patches (600-1000 for a "well-behaved" printer): http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,22 I guess this one is easy to expose to the user by asking him how many sheets to print. > Please also note, that you're passing all kinds of options with > unknown effects... I just passed the options recommended by argyll itself (the mailing list and the docs). > Please try again with exactly the options I gave... > > Also make sure you have an up to date version of Argyll (1.1.0-final)... Yes, this I did use in the last run but not the previous ones, so that could be the problem with 210 patches. > -q has little do to with actual quality with LUT profiles, it has to > do with detailedness of the generated profiles... Generating a high > detail profiles with low patches seems silly at best. Makes sense, thanks. >> Again the scenarios and the mailing list tell us to use a source >> profile. Milan had an explanation for it. > > Do you have a reference for that? Sure. Here are the docs: http://www.argyllcms.com/doc/Scenarios.html#PP5 And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try different profiles there: http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 It could be that we can actually get away without -S for a decent default. We should probably start a thread in the argyll mailing list about what to use as sensible defaults for profiling printers (and monitors/scanners/cameras too maybe). > We aren't catering to the masses... But even advanced hobby > photographers and professional photographers see color management as a > necessary evil, and most don't want to bother with patch counts and > all kinds of settings, they just want a reasonable match by clicking > on "Next" a couple of times... Yes, I agree completely. My point wasn't that the GUI shouldn't start as a straight-through "get a decent enough profile and be done with it". I was just arguing that the user shouldn't be dumped into learning all these argyll command line options every time he wants to do something even moderately advanced. > Again, the big question would be how often you _really need_ the > advanced settings... Liking to fiddle with them and needing them are > two different things... > > Trying to control to much was a mistake I made in the past as well, > sticking to Argyll's defaults has generally improved my results. I totally agree there. Only settings that are actually needed should be exposed. I don't yet know what those are though considering all the advice to fiddle with different settings I got from the argyll list. Maybe most of that advice can actually be the default and not need changing. >> I think the underlying assumption behind telling users who want >> advanced stuff to go to the argyll tools is that someone that wants >> advanced calibration/color in Linux is also an advanced Linux user. >> Whereas in reality it would be good to be able to support advanced >> photographers/artists that are also non-geek computer users. It's an >> uphill battle right now with GIMP not supporting 16-bit images, f-spot >> not very complete and raw converters still not particularly good. >> We're advancing in all three fronts though and g-c-m is a much needed >> complement. > > Patience is key here... No doubt. I wouldn't be using Linux to do photography work if I wasn't happy to put up with and work around the shortcomings. >> why -g? > > Adds greyscale patches. So why deviate from the argyll standard there? This one didn't get mentioned in my thread. Is it to improve the tone curve for B&W printing? >>> # printtarg -v -i CM -h -t 300 -p A4 test >> >> Does -t 300 help? I was getting some non-sharp edges on my patches >> maybe it was because of this. > > This doesn't particularly matter much, you're not measuring the edges. I wasn't too worried about it although I guessed it could mess up the patch detection and maybe sometimes interfere with a reading, especially when using the smaller patches. Cheers, Pedro From knizek.confy at volny.cz Sat Feb 20 08:15:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 09:15:14 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266653714.2961.28.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). > I completely agree to get some hints from argyllcms mailing list users. Also, sooner or later, GCM would need to solve the problem of a general photographer (I do not want to know how things work but still want my pictures nicely printed). A good example is here: http://photo.net/digital-darkroom-forum/00ViCO William Palmer wonders what to do to solve the problem that printed images look fine on direct sun-light, but when hanged on the wall inside, they look "dark". At the end, Andrew Rodney mentions some "advanced profiling solutions", which can compensate for different viewing conditions, but William does not get the point (which is understandable). That is what ArgyllCMS takes care by -c and -d parameters for colprof: -- Since appearance space is used in the gamut mapping (just as it is in collink), the viewing conditions for the source and destination colorspaces should really be specified. The source colorspace is the profile specified with the -s or -S flag, and the destination is the profile being created. The -c and -d options allow specification of their respective, associated viewing conditions. The viewing condition information is used to map the profile PCS (Profile Connection Space, which us either XYZ or L*a*b*) color into appearance space (CIECAM02), which is a better colorspace to do gamut mapping in. The viewing conditions allow the conversion into appearance space to take account of how color will be seen under particular viewing conditions. -- I do also not think that exposing the colprof parameters to a user is a good idea. Nonetheless, how about asking the user - "Will your print be viewed in a dim light environmnet?" "Will it hang in a room well lit by daylight?") And similarly for "-g" paramater of targen: "Do you print black and white photographs and want a higher emphasise on grey neutrality then on colour fidelity?" Using such questions, the user could be navigated to get a good profile for his own use. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 20 08:44:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 20 Feb 2010 08:44:50 +0000 Subject: gcm-git not building (as package) In-Reply-To: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> References: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Message-ID: <15e53e181002200044j180d4e97kf865fb3054fd2092@mail.gmail.com> On 19 February 2010 23:03, Pascal de Bruijn wrote: > cc1: warnings being treated as errors > gcm-calibrate.c: In function 'gcm_calibrate_device': > gcm-calibrate.c:654: error: unused variable 'dialog' > make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 commit 8c711eb8ba43a8bad65d7f45899859b3ed7fdc81 Author: Richard Hughes Date: Sat Feb 20 08:43:38 2010 +0000 trivial: fix compile from git master when compiling without PackageKit Richard. From pmjdebruijn at pcode.nl Sat Feb 20 11:45:23 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 12:45:23 +0100 Subject: Small thumbnails of targets In-Reply-To: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> Message-ID: <4c2c37f91002200345l1a221c69tb8612a35b5c0ff26@mail.gmail.com> On Sat, Feb 20, 2010 at 1:14 AM, Alexandre Prokoudine wrote: > On 2/10/10, Lars Tore Gustavsen wrote: > >>> This would be a great way to help out gnome-color-manager if you are >>> not comfortable with coding. The list of target types I need as >>> thumbnails are: >>> >>> CMP_Digital_Target-3 >>> CMP_DT_003 >>> ColorChecker >>> ColorCheckerDC >>> ColorCheckerSG >>> Hutchcolor >>> i1_RGB_Scan_1.4 > > Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) IT8 = IT8, doesn't really matter which vendor... At least it shouldn't it think... Regards, Pascal de Bruijn From knizek.confy at volny.cz Sat Feb 20 16:58:55 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 17:58:55 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266685135.5298.5.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > >> Again the scenarios and the mailing list tell us to use a source > >> profile. Milan had an explanation for it. > > > > Do you have a reference for that? > > Sure. Here are the docs: > > http://www.argyllcms.com/doc/Scenarios.html#PP5 > > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). How about using the RGB working colourspace, which is set in GCM defaults tab, for -S colour space? We can assume that majority of the images would be in that space. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Mon Feb 22 12:16:11 2010 From: paul at fincc.com (Paul Finnigan) Date: Mon, 22 Feb 2010 12:16:11 +0000 Subject: Updated Help Text Message-ID: <1266840971.2539.8.camel@localhost> Richard I have amended the text around the preferences and advanced preferences sections of the help file. I have included (but not altered) the text you said should go in about gamma. The text is not perfect but I think that it is better than what was there. I cannot alter the section on Calibration as I do not have the hardware to check out the interface yet (gcm is the first software that made me want to buy it!). If anyone has anything to add to the help files but does not want to update them then just let me know. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-Help-Preferences-Text.patch Type: text/x-patch Size: 7012 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 22 12:31:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:31:50 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220431j4a0f4c37lce0c558756c98d7e@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > The text is not perfect but I think that it is better than what was > there. Agreed, thanks. I've applied it with minor changes. You also need to set your email address so git formatted patches display the right email (and so lazy me can just use git am). To do this, just set export GIT_AUTHOR_EMAIL=dave at dave.com in ~/.bash_profile for future patches. Thanks! Richard. From hughsient at gmail.com Mon Feb 22 12:38:59 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:38:59 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > If anyone has anything to add to the help files but does not want to > update them then just let me know. In particular, we need lots more FAQ entries filled out: * What colorimeter devices are supported * What target types are supported? * Where do I purchase targets from? * How do I get a profile from my display vendor * How do I get a reference image using a digital camera? * ...lots of other details about color management.... If you're scared by docbook and git, then just submit some prose to the mailing list, and one of the other contributors can format it up and submit a patch on your behalf. Thanks, Richard. From alexandre.prokoudine at gmail.com Mon Feb 22 13:43:41 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 22 Feb 2010 16:43:41 +0300 Subject: Updated Help Text In-Reply-To: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> References: <1266840971.2539.8.camel@localhost> <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> Message-ID: <733f2c731002220543x3c160251v4a546c11e44a7210@mail.gmail.com> On 2/22/10, Richard Hughes wrote: > In particular, we need lots more FAQ entries filled out: > > * What colorimeter devices are supported Committed > * What target types are supported? Committed > * Where do I purchase targets from? Committed Alexandre From hughsient at gmail.com Mon Feb 22 14:46:19 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 14:46:19 +0000 Subject: ColorMunki works Message-ID: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> My ColorMunki arrived this morning, and I've just committed quite a few patches to make it work calibrating the screen. There are still quite a few rough edges we need to fix (hardcode) but it basically works. Now I'm going to move onto adding initial printing support, although this might take a couple of weeks. Richard. From pmjdebruijn at pcode.nl Mon Feb 22 17:22:37 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 22 Feb 2010 18:22:37 +0100 Subject: ColorMunki works In-Reply-To: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> References: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> Message-ID: <4c2c37f91002220922m77984a56o1c441985dbc9d099@mail.gmail.com> On Mon, Feb 22, 2010 at 3:46 PM, Richard Hughes wrote: > My ColorMunki arrived this morning, and I've just committed quite a > few patches to make it work calibrating the screen. There are still > quite a few rough edges we need to fix (hardcode) but it basically > works. Now I'm going to move onto adding initial printing support, > although this might take a couple of weeks. Indeed it does, there are some cosmetic issues though: https://bugzilla.gnome.org/show_bug.cgi?id=605856 I'm looking forward to the printer stuff, especially the CUPS integration, it would severely kick ass if there would be an extra CUPS Color Management tab, on which output color profiles could be specified. Regards, Pascal de Bruijn From knizek.confy at volny.cz Mon Feb 22 20:51:30 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 21:51:30 +0100 Subject: Make default - what is it supposed to do? Message-ID: <1266871890.982.23.camel@athlon> Hello, what is the expected behaviour of "Make Default" button in gcm-prefs? The notification message reads "Save these profiles for all users", but after pressing it I can see the verbose output reading: - running: pkexec /usr/sbin/gcm-install-system-wide --id xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" Content type was incorrect: application/octet-stream It tries to install the monitor profile, however, I also have a webcam profile set. And as far as I can tell, nothing happens. The profile is not copied to /usr/share/color/... or /usr/local/share/color/... locations, I cannot find anything useful in /etc/... or /var/lib/... and starting a session of a different user does not show any profile set in gcm-prefs. Is this is a bug or not-yet-implemented thing? Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 22 21:11:25 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 23 Feb 2010 00:11:25 +0300 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> On 2/22/10, Milan Kn??ek wrote: > Hello, > > what is the expected behaviour of "Make Default" button in gcm-prefs? http://www.libregraphicsworld.org/articles.php?article_id=11 "To make your preferences available to all users of a system you can use the Make Default button in the bottom of the dialog. What it will do is ask for superuser password and copy all the active display profiles to a system-wide directory (/var/lib/color) where the new filename matches the device-id. So when a new user logs in, if there is no device-profiles entry for the device, the system-wide profile is used." Alexandre From knizek.confy at volny.cz Mon Feb 22 22:07:42 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 23:07:42 +0100 Subject: Make default - what is it supposed to do? In-Reply-To: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> References: <1266871890.982.23.camel@athlon> <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> Message-ID: <1266876462.20402.8.camel@athlon> Alexandre Prokoudine p??e v ?t 23. 02. 2010 v 00:11 +0300: > On 2/22/10, Milan Kn??ek wrote: > > Hello, > > > > what is the expected behaviour of "Make Default" button in gcm-prefs? > > http://www.libregraphicsworld.org/articles.php?article_id=11 > > "To make your preferences available to all users of a system you can > use the Make Default button in the bottom of the dialog. What it will > do is ask for superuser password and copy all the active display > profiles to a system-wide directory (/var/lib/color) where the new > filename matches the device-id. So when a new user logs in, if there > is no device-profiles entry for the device, the system-wide profile is > used." > Then it seems to be a bug - on two computers (same system though - Ubuntu 9.10 amd64) the directory /var/lib/color exists, but it remains empty. Authorisation seems to be okay, I also tried to run with sudo and as root in console - no success, just the error message: Content type was incorrect: application/octet-stream regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Mon Feb 22 23:17:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 23:17:13 +0000 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <15e53e181002221517t65dc049aqccb1f4580470e478@mail.gmail.com> On 22 February 2010 20:51, Milan Kn??ek wrote: > ?- running: pkexec /usr/sbin/gcm-install-system-wide --id > xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" > Content type was incorrect: application/octet-stream Looks like your version of shared-mime-info is too old. We can't do the .icc/.icm fallback in this case as gcm-install-system-wide is running as root as we have to be careful of maliciously created profiles. > Is this is a bug or not-yet-implemented thing? The former :-) Richard. From hughsient at gmail.com Tue Feb 23 14:21:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 14:21:39 +0000 Subject: Blog post about GCM Message-ID: <15e53e181002230621t76746c6elb9c4dcc2344b59c@mail.gmail.com> I've made a blog post about GCM that some of you might find interesting: http://blogs.gnome.org/hughsie/2010/02/23/gnome-color-manager-and-printer-profiling/ Good job on the documentation file btw, it's coming along nicely now. Richard. From hughsient at gmail.com Tue Feb 23 15:50:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 15:50:21 +0000 Subject: Strategic direction Message-ID: <15e53e181002230750r1b8414a2l2503a7079cfd4f2d@mail.gmail.com> Big ideas I think we need to work towards: * Assigning more than one profile to a device[1] (and having one default profile per device) * Having virtual devices that we can't connect, for instance "Bob's Photo Processing Shop" Any one got any more ideas? Richard. [1] The DBus API already supports this, although it only ever returns one profile. From pmjdebruijn at pcode.nl Tue Feb 23 17:44:13 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 18:44:13 +0100 Subject: New print profiling functionality Message-ID: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Hi, I just tried the brand spanking new print profiling functionality... And of course there's something to bitch about... * It only generated 45 patches, while on A4 I can fit 210 ColorMunki patches in double density mode (-h). * Some patches got clipped (because of margins), because the generated image isn't centered (or it is getting stretched for no reason, since the generated image doesn't include margins). * The generated image is pretty low resolution, the text looks like crap, consider (printtarg -T 200 or 300)? * GCM should not report "reading the patches" during self-calibration, we need a seperate dialog for this! Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 23 17:51:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 17:51:53 +0000 Subject: New print profiling functionality In-Reply-To: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Message-ID: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> On 23 February 2010 17:44, Pascal de Bruijn wrote: > I just tried the brand spanking new print profiling functionality... > And of course there's something to bitch about... Heh, good. :-) > * It only generated 45 patches, while on A4 I can fit 210 ColorMunki > patches in double density mode (-h). Right, this is something I need help with. How many patches do we use for quick, normal and slow profiling? I'm already using -h for ColorMunki. > * Some patches got clipped (because of margins), because the generated > image isn't centered (or it is getting stretched for no reason, since > the generated image doesn't include margins). Ahh, I'm just blitting it to the cairo surface, without preserving aspect. I guess we need to do that. I'm using gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > * The generated image is pretty low resolution, the text looks like > crap, consider (printtarg -T 200 or 300)? Hmm, it should already be using 300DPI thanks to the -t300 option. > * GCM should not report "reading the patches" during self-calibration, > we need a seperate dialog for this! Sure, I can't get my ColorMunki to self calibrate using chartread (see the Argyll m/l) so I've not tested past this point. Richard. From hughsient at gmail.com Tue Feb 23 20:20:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 20:20:13 +0000 Subject: New print profiling functionality In-Reply-To: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> Message-ID: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> On 23 February 2010 17:51, Richard Hughes wrote: > Ahh, I'm just blitting it to the cairo surface, without preserving > aspect. I guess we need to do that. I'm using > gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. I've done the scaling in cairo now; see below. >> * The generated image is pretty low resolution, the text looks like >> crap, consider (printtarg -T 200 or 300)? > > Hmm, it should already be using 300DPI thanks to the -t300 option. I've just pushed a commit to do the scaling in cairo, rather than GDK, which makes it look much better. Richard. From pmjdebruijn at pcode.nl Tue Feb 23 22:22:30 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:22:30 +0100 Subject: New print profiling functionality In-Reply-To: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> Message-ID: <4c2c37f91002231422g6836f6e5s1a7ff1a8db4e8c7f@mail.gmail.com> On Tue, Feb 23, 2010 at 9:20 PM, Richard Hughes wrote: > On 23 February 2010 17:51, Richard Hughes wrote: >> Ahh, I'm just blitting it to the cairo surface, without preserving >> aspect. I guess we need to do that. I'm using >> gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > > I've done the scaling in cairo now; see below. > >>> * The generated image is pretty low resolution, the text looks like >>> crap, consider (printtarg -T 200 or 300)? >> >> Hmm, it should already be using 300DPI thanks to the -t300 option. > > I've just pushed a commit to do the scaling in cairo, rather than GDK, > which makes it look much better. Actually, since you're using cairo, which is very vector-aware, right? Wouldn't it make sense to use the EPS output (printtarg -e). Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 23 22:28:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:28:50 +0100 Subject: Printshop calibration/profiling Message-ID: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Hi, Another thing I noticed, is the very cool dialog which also allows you to profile printshops, however I can only get to this dialog whenever I have a printer in GCM, and the spectrophotometer connected, even though I only want to generate a chart to send to my printshop. This is not a huge problem, more of a nuisance... Maybe it's a thought to create a "Printshop" virtual device? Honestly I'm not sure that's a much better solution, since sooner or later we'll end up with 100 by default created virtual devices for all kinds of corner cases... This message is mainly intended to get a discussion going... Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Tue Feb 23 22:32:52 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Wed, 24 Feb 2010 01:32:52 +0300 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <733f2c731002231432j6144ec13h1ffd278e038064c0@mail.gmail.com> On 2/24/10, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... This is not a huge problem when you have a printer. Well, I don't have one :) Alexandre From hughsient at gmail.com Tue Feb 23 22:33:36 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 22:33:36 +0000 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <15e53e181002231433j2138420bg216e2efe3d84ad3c@mail.gmail.com> On 23 February 2010 22:28, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... Sure, agreed. > Maybe it's a thought to create a "Printshop" virtual device? Honestly > I'm not sure that's a much better solution, since sooner or later > we'll end up with 100 by default created virtual devices for all kinds > of corner cases... I do think we need virtual devices. It's bad usability, as you have to enter everything manually, but a useful thing for power users. Richard. From pmjdebruijn at pcode.nl Wed Feb 24 22:06:08 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 24 Feb 2010 23:06:08 +0100 Subject: Double Density Mode for ColorMunki Message-ID: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Hi, To my dismay I noticed you've dropped the double density mode for the ColorMunki. What would be the problem with this? Maybe I can help? Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 08:43:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 08:43:34 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Message-ID: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> On 24 February 2010 22:06, Pascal de Bruijn wrote: > To my dismay I noticed you've dropped the double density mode for the > ColorMunki. What would be the problem with this? Maybe I can help? I just couldn't get double density to work correctly. Maybe I'm clumsy or something, but the single density was much easier to scan. Perhaps we can just have it as a simple dialog choice? ________________________________ Target Choice ________________________________ Your calibration device can use much smaller sized squares to save on paper and ink, although it will be harder to use the device. Enable double density mode? [Help] [No] [Yes] ________________________________ Richard. From pmjdebruijn at pcode.nl Thu Feb 25 10:58:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 25 Feb 2010 11:58:38 +0100 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> Message-ID: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> On Thu, Feb 25, 2010 at 9:43 AM, Richard Hughes wrote: > On 24 February 2010 22:06, Pascal de Bruijn wrote: >> To my dismay I noticed you've dropped the double density mode for the >> ColorMunki. What would be the problem with this? Maybe I can help? > > I just couldn't get double density to work correctly. Maybe I'm clumsy > or something, but the single density was much easier to scan. I'm guessing you didn't print it at proper scale... In double density mode, three rows are exactly as wide as the ColorMunki, so the rows themselves can be used as a visual guide. And because the patches are smaller you need to scan a bit slower. > Perhaps we can just have it as a simple dialog choice? No that's silly... Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 11:36:33 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 11:36:33 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> Message-ID: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> On 25 February 2010 10:58, Pascal de Bruijn wrote: > I'm guessing you didn't print it at proper scale... Well, argyll formats it as a single page tiff file, so I'm pretty sure I did. I've attached a photo to show you the pages. > In double density mode, three rows are exactly as wide as the > ColorMunki, so the rows themselves can be used as a visual guide. And > because the patches are smaller you need to scan a bit slower. Right, maybe I'm just a bit clumsy. >> Perhaps we can just have it as a simple dialog choice? > > No that's silly... Agreed. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: double-density.jpg Type: image/jpeg Size: 23813 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 25 12:07:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 12:07:28 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> Message-ID: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> On 25 February 2010 11:36, Richard Hughes wrote: > Right, maybe I'm just a bit clumsy. I've found I can use the double density scan 99% correctly, if I rotate the page and "push" the colormunki away from me. If I try to scan from left to right then it only works 10% of the time. I'll do you deal. I'll re-instate the double density feature (with extra love) if you write a section in the help file on how to scan in a target, with tips. :-) Deal? Richard. From pedro at pedrocr.net Thu Feb 25 21:10:18 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 25 Feb 2010 13:10:18 -0800 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> Message-ID: <62e8012c1002251310t6c02124cnd3f62db919b2b5dd@mail.gmail.com> On Thu, Feb 25, 2010 at 4:07 AM, Richard Hughes wrote: > I'll do you deal. I'll re-instate the double density feature (with > extra love) if you write a section in the help file on how to scan in > a target, with tips. :-) If I write a section for the manual on how to build and use the simple guide rules to use the munki with EyeOne targets can we get that mode too? In my experience it makes scanning much simpler than even normal density patches freehand and the guide takes 5 minutes and only basic supplies to build. If someone was selling an after-market solution for this I assume no one would have a problem with it so I don't see why a home-made one isn't fine as well. It would at least be nice if the instrument definitions were setup in config files for each instrument so that even if you don't want to have this in mainline people could hack together their own config files and still take advantage of the g-c-m UI. Pedro From hughsient at gmail.com Mon Feb 1 11:05:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 1 Feb 2010 11:05:13 +0000 Subject: GNOME Color Manager 2.29.3 Message-ID: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> gnome-color-manager is a session program that makes it easy to manage, install and generate color profiles in the GNOME desktop. Version 2.29.3 ~~~~~~~~~~~~~~ Released: 2010-02-01 * Translations - Added Italian translation (Francesco Groccia) - Updated Danish translation (Joe Hansen) - Updated French translation (Claude Paroz) - Updated German translation (Mario Bl?ttermann) - Updated Norwegian bokm?l translation (Kjartan Maraas) - Updated Portuguese translation (Ant?nio Lima) - Updated Russian translation (Alexandre Prokoudine) - Updated Slovenian translation (Andrej ?nidar?i?) - Updated Swedish translation (Daniel Nylander) * New Features: - Enable the rendering intent and default colorspace UI elements (Richard Hughes) - Show whether the ICC profile has a VCGT tag in the UI (Richard Hughes) - Filter out non RGB and CMYK color space profiles from the combo-boxes using a heuristic (Richard Hughes) - Add a new DBus method GetProfileForWindow which can return a profile for a supplied XID (Richard Hughes) - Add some new text and tooltips to the prefs dialog (Richard Hughes) - Add per-user OSX ICC profiles at startup (Richard Hughes) - Add OSX and Windows ICC profiles if they exist from mounted volumes. Fixes #607390 (Richard Hughes) - Add a device profile entry of 'Other profile...' to be able to easily import a profile. Fixes #607389 (Richard Hughes) - Add a precision GConf variable to control the time a calibration takes. Fixes #605558 (Richard Hughes) - Screenscrape the Argyll output to better support other hardware devices. Fixes #605558 (Richard Hughes) - Do not show the 'Fine tuning' expander by default, and have configuration in GConf (Richard Hughes) * Bugfix: - Zero out GErrors after freeing. Fixes crash (Christian Hergert) - Add gnome-desktop path as fallback for pci.ids (Frederic Crozat) - Do not generate an error if a display profile does not have CLUT data (Richard Hughes) - Add gcm-fix-profile to load and then re-save existing profiles using lcms (Richard Hughes) - Fix compile when using an ld that defaults to --as-needed (Richard Hughes) - Do not allow the colorspace combobox to be zero sized. Fixes #606484 (Richard Hughes) - Make gcm-prefs a normal dialog rather than a modal dialog (Richard Hughes) - Only scan ICC locations with hfs partition types for OSX and msdos/NTFS types for Windows (Richard Hughes) - Make gcm-prefs startup a few hundred ms quicker by not loading the list of screens (Richard Hughes) - Cache gnome_rr_screen_new and take 0.7 seconds off the start time (Richard Hughes) - Don't resize the window on startup. Fixes #607391 (Richard Hughes) - Update the Free Software Foundation address (Richard Hughes) Richard. From pmjdebruijn at pcode.nl Mon Feb 1 18:29:31 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 1 Feb 2010 19:29:31 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> Message-ID: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > gnome-color-manager is a session program that makes it easy to manage, install > and generate color profiles in the GNOME desktop. > > Version 2.29.3 > ~~~~~~~~~~~~~~ > Released: 2010-02-01 As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's available on my gcm-release PPA: https://launchpad.net/~pmjdebruijn/+archive/gcm-release ArgyllCMS 1.1.0 is also available on my argyll-release PPA, to complement GNOME Color Manager: https://launchpad.net/~pmjdebruijn/+archive/argyll-release Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 5 12:55:32 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 13:55:32 +0100 Subject: Information re. display gamma Message-ID: <1265374532.31703.61.camel@athlon> Hello, while translating the gcm, I spotted the following: -- Gamma is adjusted to affect the color of the attached monitor. Traditionally Linux has used a gamma value of 1.0, but this makes monitors look washed out compared Windows XP or OS X. Apple traditionally used a value of 1.8 for a long time, but now use the same value as Microsoft. Microsoft has always used a value of 2.2. -- Where does the information that Linux has used a gamma of 1.0 come from? I would assume it is a wrong interpretation of technical data. Both Mac/Win tools prefer to tell the user the final viewing gamma (which is a combination of gamma adjustment in LUT of graphics card and of the monitor's native gamma). These tools expect that the monitor native gamma is 2.2 (which is close to sRGB). In the past, Mac monitors had native gama 1.8. Linux tools - like xgamma and gcm - instead tell the number, which is applied to LUT only. Note that the final viewing gamma is equal to monitor's native gamma divided by LUT gamma. In other words, an image (untagged by ICC profile) displayed in Windows and Linux will appear the same, provided that the same video card and monitor is used and no colour management/calibration is applied. This is also the reason, why display ICC profiles created in Windows can be used in Linux. If the information quoted above remains, users will be confused and try to set gamma 2.2 in gcm. I would propose to change the text so that it is clear that the user can correct the monitor's native gamma and that it is not the final viewing gamma. Or am I wrong? Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Fri Feb 5 13:32:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 5 Feb 2010 13:32:12 +0000 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> On 5 February 2010 12:55, Milan Kn??ek wrote: > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. That sounds about right to me. Feel free to change it so it's clearer. Thanks. Richard. From knizek.confy at volny.cz Fri Feb 5 20:09:20 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:09:20 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> Message-ID: <1265400560.29899.18.camel@athlon> Pascal de Bruijn p??e v Po 01. 02. 2010 v 19:29 +0100: > On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > > gnome-color-manager is a session program that makes it easy to manage, install > > and generate color profiles in the GNOME desktop. > > > > Version 2.29.3 > > ~~~~~~~~~~~~~~ > > Released: 2010-02-01 > > As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's > available on my gcm-release PPA: > > https://launchpad.net/~pmjdebruijn/+archive/gcm-release Is it an expected change in this release that the "fine tuning" option on the main screen of gcm-prefs disappeared? regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From knizek.confy at volny.cz Fri Feb 5 20:39:06 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:39:06 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> Message-ID: <1265402346.29899.48.camel@athlon> Richard Hughes p??e v P? 05. 02. 2010 v 13:32 +0000: > On 5 February 2010 12:55, Milan Kn??ek wrote: > > I would propose to change the text so that it is clear that the user can > > correct the monitor's native gamma and that it is not the final viewing > > gamma. > > That sounds about right to me. Feel free to change it so it's clearer. Thanks. > > Richard. > I will look at the text and propose a new wording. Additionally, it may also be helpful to update the "fine tuning" gamma slider. The slider has "hooks" for 1.8 and 2.2 -this would make sense if the user had a monitor with native gamma value of 1. Then, setting the slider to 2.2 would result in viewing gamma value of 2.2. This probably would not be the case for anyone. Hence, removing the "hooks" would help avoiding confusion. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Sat Feb 6 02:10:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 06 Feb 2010 13:10:48 +1100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <4B6CCFA8.3000107@argyllcms.com> Milan Kn??ek wrote: > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple Sounds bogus. Unix machines have "traditionally" used RGB encoded for display on a typical native CRT gamma. Linux is no different - "traditionally" raw RGB numbers have been sent to the monitor, and you get native CRT gamma or an emulation of it if it's an LCD monitor, so the encoding is notionally set for a gamma of 2.2. But there are exceptions - SGI's had a different scheme, and people creating synthetic images (CGI) have often left their images linear light, and expect the display process to counteract the displays natural gamma, even though this introduces quantization problems if they use 8 bits. > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. Note a couple of things: Latest OS X (10.6 "Snow Leopard") has a default of 2.2, but it seems that "1.8" of the Mac mac prior to this is actually a misnomer, the encoding is actually closer to 1/1.72, which is corrected by a framebuffer ramp of 1/1.45 for display on a CRT of 2.5, giving an overall system gamma of 1.0. Real CRT's have a gamma of nearer 2.4 - 2.5 (although such numbers are very sensitive to the setting of the black level). "Traditionally" from the TV world, material is broadcast with a gamma of 0.45 (ie. 1/2.22) with the expectation that it will be displayed on a monitor that has a gamma of 2.5, the discrepancy applying a viewing conditions transform that accounts for the different appearance between the bright TV studio lighting and the usually dim viewing conditions use with a CRT monitor. For all the details please refer to Charles Poynton's book "Digital Video and HDTV". > Linux tools - like xgamma and gcm - instead tell the number, which is > applied to LUT only. Note that the final viewing gamma is equal to > monitor's native gamma divided by LUT gamma. Right, and the final overall gamma should be 1.0, or (allowing for the viewing condition transform, about 1.1 - 1.2). > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. > > Or am I wrong? Most people are unfamiliar with the concept of overall system gamma. They might easily confuse the encoding gamma, display gamma and system gamma. The distinction between encoding gamma and display gamma is probably lost on most people too (strictly speaking the encoding gamma for "2.2" is 1/2.2 which is about 0.45, and the overall gamma is the product of the encoding gamma and the display gamma.) I think that if this is a display calibration application, then really it should talk about what the display is being set to, and could indicate how this corresponds to the encoding expectation. So typically a CRT display in a dim viewing environment should be calibrated to have a gamma of about 2.4, with the expectation that it is being fed material that has been encoded with a gamma of 1/2.2. If the display is brighter and in a brighter environment, then a calibration gamma of < 2.4 might be desirable, for the same 2.2 gamma encoded material. Graeme Gill. Graeme Gill. From knizek.confy at volny.cz Sat Feb 6 10:39:03 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 06 Feb 2010 11:39:03 +0100 Subject: Information re. display gamma In-Reply-To: <4B6CCFA8.3000107@argyllcms.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> Message-ID: <1265452743.22070.45.camel@athlon> Graeme Gill p??e v So 06. 02. 2010 v 13:10 +1100: > I think that if this is a display calibration application, then > really it should talk about what the display is being set to, and > could indicate how this corresponds to the encoding expectation. > This means that the GCM would have to change a bit more: GCM must know what the native monitor gamma is. Such an information can be taken from the ICC profile, either supplied by the user, created with GCM and colorimeter or created with GCM and "eye-measured" calibration. The lack of eye-measured calibration is already reported as bug 605019 https://bugzilla.gnome.org/show_bug.cgi?id=605019 which also refers to a tutorial how ColorSync on Mac did it: http://www.computer-darkroom.com/colorsync-display/colorsync_2.htm regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 6 11:46:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 11:46:06 +0000 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <1265400560.29899.18.camel@athlon> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> <1265400560.29899.18.camel@athlon> Message-ID: <15e53e181002060346u2d547bb1g7d6c1cd01ccff1ae@mail.gmail.com> On 5 February 2010 20:09, Milan Kn??ek wrote: > Is it an expected change in this release that the "fine tuning" option > on the main screen of gcm-prefs disappeared? Yes. There's a GConf key to re-enable it if you need the UI, but it's hidden by default until we make the UI nicer to use. It's on my TODO, but didn't quite make the release. New contributors welcome! :) Richard. From j at jonathanleighton.com Sat Feb 6 12:29:46 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Sat, 06 Feb 2010 12:29:46 +0000 Subject: ColorVision Spyder Message-ID: <1265459386.23788.9.camel@tybalt> Hi there, I have a ColorVision Spyder colorimeter. I have just been trying out gnome-color-manager (very impressive!) but the calibration buttons are disabled, even when I plug in my colorimeter. Do I need to take additional steps to use the colorimeter through GCM, or is the support just not there yet or something? Many thanks, Jon PS. Please CC me in replies - I'm not on the list. From hughsient at gmail.com Sat Feb 6 15:55:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:55:31 +0000 Subject: Information re. display gamma In-Reply-To: <1265452743.22070.45.camel@athlon> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> Message-ID: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> On 6 February 2010 10:39, Milan Kn??ek wrote: > This means that the GCM would have to change a bit more: GCM must know > what the native monitor gamma is. We can do this, but in my experience the EDID data from the monitor is wrong more often than it's right... Richard. From hughsient at gmail.com Sat Feb 6 15:57:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:57:50 +0000 Subject: ColorVision Spyder In-Reply-To: <1265459386.23788.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> Message-ID: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> On 6 February 2010 12:29, Jon Leighton wrote: > I have a ColorVision Spyder colorimeter. I have just been trying out > gnome-color-manager (very impressive!) but the calibration buttons are > disabled, even when I plug in my colorimeter. What version ArgyllCMS do you have installed? If it's less than 1.1.0 you'll need to add --disable-hardware-detection to ./configure -- it also only works for display devices for now (patches welcome!). > Do I need to take additional steps to use the colorimeter through GCM, > or is the support just not there yet or something? Well, if it's supported in Argyll then it's supported by GCM. Richard. From knizek.confy at volny.cz Sun Feb 7 11:23:57 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sun, 07 Feb 2010 12:23:57 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> Message-ID: <1265541838.20793.5.camel@athlon> Richard Hughes p??e v So 06. 02. 2010 v 15:55 +0000: > On 6 February 2010 10:39, Milan Kn??ek wrote: > > This means that the GCM would have to change a bit more: GCM must know > > what the native monitor gamma is. > > We can do this, but in my experience the EDID data from the monitor is > wrong more often than it's right... > > Richard. > I understand that getting the EDID data is unreliable at the moment. In addition, some wide-gamut displays support pre-set calibration modes emulating various colour spaces. The modes can be changed via hardware buttons on the LCD. For the time being, I would leave up to the user to select the proper display profile (depending on the attached monitor and its calibration mode) rather then only relying on EDID. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Mon Feb 8 01:27:50 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 12:27:50 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <4B6F6896.9050406@argyllcms.com> Richard Hughes wrote: > Well, if it's supported in Argyll then it's supported by GCM. But note that the Spyder 2 needs to have firmware. In Argyll the spyd2en utility needs to be run to extract the firmware from the distribution disk. See Graeme Gill. From hughsient at gmail.com Mon Feb 8 07:58:05 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 07:58:05 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6F6896.9050406@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> Message-ID: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> On 8 February 2010 01:27, Graeme Gill wrote: > But note that the Spyder 2 needs to have firmware. In Argyll > the spyd2en utility needs to be run to extract the firmware from > the distribution disk. > See What's the output from argyllcms if there is no firmware? Or does the device just not appear? Thanks, Richard. From graeme2 at argyllcms.com Mon Feb 8 08:22:18 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 19:22:18 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> Message-ID: <4B6FC9BA.5030905@argyllcms.com> Richard Hughes wrote: > What's the output from argyllcms if there is no firmware? Or does the > device just not appear? There will be an error message containing: "No PLD firmware pattern is available" Graeme Gill. From hughsient at gmail.com Mon Feb 8 08:40:17 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 08:40:17 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6FC9BA.5030905@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> <4B6FC9BA.5030905@argyllcms.com> Message-ID: <15e53e181002080040o56051e39k39dc13f01163194d@mail.gmail.com> On 8 February 2010 08:22, Graeme Gill wrote: > There will be an error message containing: > > "No PLD firmware pattern is available" That's great, thanks. Richard. From hughsient at gmail.com Mon Feb 8 09:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:16:56 +0000 Subject: Small thumbnails of targets Message-ID: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> The attached file shows some new UI in gnome-color-manager -- it now supports more types of targets than just IT8. To be able to show the user a preview of what each target looks like, we need some 200x150 pixel thumbnails of the different target types. These need to be GPLv2+ licenced, and have the specific vendor data removed. See the screenshot for an example. This would be a great way to help out gnome-color-manager if you are not comfortable with coding. The list of target types I need as thumbnails are: CMP_Digital_Target-3 CMP_DT_003 ColorChecker ColorCheckerDC ColorCheckerSG Hutchcolor i1_RGB_Scan_1.4 LaserSoftDCPro QPcard_201 I've already done IT8. Please cc the list if you send me a type, and then we won't get duplicated effort. Note: you can't just copy and paste from the manufacturers website, as they may have copyright on the image. Basically, the rule is if you're not sure about the copyright of the image, then it's not suitable. The best way would be to scan the target yourself and send it to me. If you send files, please state where you got them from, and that they are redistributable as part of a project that is GPLv2+. Thanks, Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 44590 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 09:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <15e53e181002080147l7e6f4246pf92afe936ffd28b5@mail.gmail.com> On 8 February 2010 09:16, Richard Hughes wrote: > The best way would be to scan the > target yourself and send it to me. If you send files, please state > where you got them from, and that they are redistributable as part of > a project that is GPLv2+. I forgot to mention. They also have to be PNG format. Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 10:00:38 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 10:00:38 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <1265623238.9194.9.camel@tybalt> On Sat, 2010-02-06 at 15:57 +0000, Richard Hughes wrote: > On 6 February 2010 12:29, Jon Leighton wrote: > > I have a ColorVision Spyder colorimeter. I have just been trying out > > gnome-color-manager (very impressive!) but the calibration buttons are > > disabled, even when I plug in my colorimeter. > > What version ArgyllCMS do you have installed? If it's less than 1.1.0 > you'll need to add --disable-hardware-detection to ./configure -- it > also only works for display devices for now (patches welcome!). Aha, that was it. I've installed latest argyll, and now the button is enabled. However, when I click it and select LCD, I then get the "Display setup" dialog. If I click OK nothing happens - the dialog closes but nothing else comes up. I tried running with -vvv and the following came up: TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 - failed to calibrate: failed to match display as RandR is faulty TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,170 - min=0.000000,max=1.000000 TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,176 - falling back to dummy gamma TI:09:52:12 FI:gcm-device-xrandr.c FN:gcm_device_xrandr_set_gamma_fallback,351 - using PER-SCREEN gamma tables as driver is not XRANDR 1.3 compliant TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_output_profile,477 - found default, removing atom TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_root_window_profile,239 - removing root window ICC profile atom Any ideas? Thanks From hughsient at gmail.com Mon Feb 8 10:39:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 10:39:12 +0000 Subject: ColorVision Spyder In-Reply-To: <1265623238.9194.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> Message-ID: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> On 8 February 2010 10:00, Jon Leighton wrote: > Aha, that was it. I've installed latest argyll, and now the button is > enabled. That's good. > TI:09:52:12 ? ? FI:gcm-prefs.c ?FN:gcm_prefs_calibrate_display,381 > ?- failed to calibrate: failed to match display as RandR is faulty What video driver are you using? Can you attach the output of xrandr please? Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 11:12:37 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 11:12:37 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> Message-ID: <1265627557.9194.11.camel@tybalt> Hi, On Mon, 2010-02-08 at 10:39 +0000, Richard Hughes wrote: > > TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 > > - failed to calibrate: failed to match display as RandR is faulty > > What video driver are you using? I'm using the nVidia driver, version 185.18.36. > Can you attach the output of xrandr please? Thanks. Yep. Cheers, Jon -------------- next part -------------- Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 50.0 51.0 52.0* 1600x1024 53.0 1440x900 54.0 1360x768 55.0 56.0 1280x1024 57.0 1280x960 58.0 1152x864 59.0 1024x768 60.0 960x600 61.0 960x540 62.0 840x525 63.0 64.0 800x600 65.0 66.0 800x512 67.0 720x450 68.0 700x525 69.0 680x384 70.0 71.0 640x512 72.0 640x480 73.0 74.0 576x432 75.0 512x384 76.0 400x300 77.0 320x240 78.0 From hughsient at gmail.com Mon Feb 8 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 11:20:27 +0000 Subject: ColorVision Spyder In-Reply-To: <1265627557.9194.11.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> Message-ID: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> On 8 February 2010 11:12, Jon Leighton wrote: > I'm using the nVidia driver, version 185.18.36. Hmm, I fear this maybe another case of broken binary drivers. Is there any chance you could try with the nouveau driver please? Thanks. Richard. From graeme2 at argyllcms.com Mon Feb 8 11:58:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 22:58:48 +1100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4B6FFC78.9010503@argyllcms.com> I've sent Richard an image of the ColorCheckerDC. Graeme Gill From j at jonathanleighton.com Mon Feb 8 14:18:05 2010 From: j at jonathanleighton.com (Jonathan Leighton) Date: Mon, 8 Feb 2010 14:18:05 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> Message-ID: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Hi, On 8 February 2010 11:20, Richard Hughes wrote: > On 8 February 2010 11:12, Jon Leighton wrote: >> I'm using the nVidia driver, version 185.18.36. > > Hmm, I fear this maybe another case of broken binary drivers. Is there > any chance you could try with the nouveau driver please? Thanks. Yes, it worked under nouveau. (Incidentally, the calibration seemed pretty quick, and I'm not sure the results were great in my case. Are there any plans to have an option of "quick profile" vs "good profile"?) Cheers, Jon From pmjdebruijn at pcode.nl Mon Feb 8 14:27:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:27:24 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > ColorChecker I have just done these two... > I've already done IT8. I redid the IT8, we should called this IT8.7/2, since that's it's proper name... There are other IT8 charts (I think those are mostly for printing), using the full name should prevent any confusion. With all the images, I scanned my own targets, and then followed this procedure: 1. Despeckle, Adaptive enabled, Recursive dislabed, Radius 3, Black level 6, White level 255 2. Then possibly rotate the chart a bit to align it, and then crop it. 3. Then use GIMP Resynthesize to remove vendor text "Smart remove selection", with 10px. 4. Possibly have GIMP do Auto White Balance (doesn't work always) Without distorting aspect, my images could all be rounded to 200px by 140px. I think we should not distort aspect in any visible way. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: IT872.png Type: image/png Size: 31624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ColorChecker24.png Type: image/png Size: 32929 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CMP-DigitalTarget3.png Type: image/png Size: 44514 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 14:52:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 14:52:23 +0000 Subject: ColorVision Spyder In-Reply-To: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Message-ID: <15e53e181002080652j1616f139h65a133fb55b1e895@mail.gmail.com> On 8 February 2010 14:18, Jonathan Leighton wrote: > (Incidentally, the calibration seemed pretty quick, and I'm not sure > the results were great in my case. Are there any plans to have an > option of "quick profile" vs "good profile"?) Grab gcm from git master, and then set /apps/gnome-color-manager/calibration_length in GConf Editor. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 14:56:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:56:17 +0100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4B6FFC78.9010503@argyllcms.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> Message-ID: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: > I've sent Richard an image of the ColorCheckerDC. I noticed it got commited... But it's aspect ratio is slightly off... You obviously did that to comply with Richard's 200x150 specification... But 200x140 as a baseline would be better for most charts... You're ColorCheckerDC image looks much better when rescaled to 200x140. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Mon Feb 8 15:04:06 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:04:06 +0100 Subject: Camera profile generation options Message-ID: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Hi, Are camera profiles generated with Argyll's default options? -q m -a l ? This might be fine for IT8 or other targets with lots of patches... But it's probably not such a good idea for a 24 patch ColorChecker, -q l -a S seems more appropriate... Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:04:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:04:27 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> Message-ID: <15e53e181002080704o79716ec2kd131bf0fbf8feafb@mail.gmail.com> On 8 February 2010 14:27, Pascal de Bruijn wrote: > I have just done these two... Brilliant, thanks. >> I've already done IT8. > > I redid the IT8, we should called this IT8.7/2, since that's it's > proper name... There are other IT8 charts (I think those are mostly > for printing), using the full name should prevent any confusion. Done, thanks. > Without distorting aspect, my images could all be rounded to 200px by > 140px. I think we should not distort aspect in any visible way. Okay, I've changed the others to be 200x140 also. Thanks. Richard. From hughsient at gmail.com Mon Feb 8 15:12:35 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:12:35 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Message-ID: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> On 8 February 2010 15:04, Pascal de Bruijn wrote: > Are camera profiles generated with Argyll's default options? -q m -a l ? > > This might be fine for IT8 or other targets with lots of patches... > > But it's probably not such a good idea for a 24 patch ColorChecker, -q > l -a S seems more appropriate... Yes, this is a good idea, and a perfect patch for you to submit :-) The kind of profile is listed in src/gcm-calibrate-argyll.h, which is saved to priv->reference_kind, which is private data for the GcmCalibrateArgyll object. You probably need to add a simple "if (priv->reference_kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just getting the type of profile (using gcm_calibrate_argyll_precision_to_quality_arg) in the function gcm_calibrate_argyll_device_generate_profile() which lives in src/gcm-calibrate-argyll.c Make a few changes, and just do "git diff > test.patch" Attach the test.patch to an email (on the mailing list if you're feeling brave, or just to me if you're feeling timid) and I'll give you some feedback. Grab me on IRC if you are feeling really stuck / lazy / busy. Richard. From hughsient at gmail.com Mon Feb 8 15:14:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:14:22 +0000 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> Message-ID: <15e53e181002080714y11dad8afxb11eb95cbd801a85@mail.gmail.com> On 8 February 2010 14:56, Pascal de Bruijn wrote: > On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: >> I've sent Richard an image of the ColorCheckerDC. > > I noticed it got commited... But it's aspect ratio is slightly off... > You obviously did that to comply with Richard's 200x150 > specification... No, I did that, Graeme sent me the original image. I've sent you the profile for the same love. > But 200x140 as a baseline would be better for most charts... You're > ColorCheckerDC image looks much better when rescaled to 200x140. Agreed. Richard. From hughsient at gmail.com Mon Feb 8 15:16:29 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:16:29 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? Message-ID: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> I've got sources that look like this: if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) return "CMP_Digital_Target-3.cht"; if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) return "CMP_DT_003.cht"; Are they actually the same profile type? What's the difference in the chart versions? Thanks, Richard. From pmjdebruijn at pcode.nl Mon Feb 8 15:46:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:46:17 +0100 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> Message-ID: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> On Mon, Feb 8, 2010 at 4:16 PM, Richard Hughes wrote: > I've got sources that look like this: > > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) > ? ? ? ? ? ? ? ?return "CMP_Digital_Target-3.cht"; > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) > ? ? ? ? ? ? ? ?return "CMP_DT_003.cht"; > > Are they actually the same profile type? What's the difference in the > chart versions? They are different charts... I have this one (3): http://www.cmp-color.fr/eng%20digital%20target.html Are there is the 003 one: http://www.argyllcms.com/doc/CMP_DT_003.jpg Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:48:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:48:53 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> Message-ID: <15e53e181002080748i4f953979j9999944c092cc31@mail.gmail.com> On 8 February 2010 15:46, Pascal de Bruijn wrote: > They are different charts... Cool, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 21:32:32 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:32:32 +0100 Subject: Camera profile generation options In-Reply-To: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> Message-ID: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> On Mon, Feb 8, 2010 at 4:12 PM, Richard Hughes wrote: > On 8 February 2010 15:04, Pascal de Bruijn wrote: >> Are camera profiles generated with Argyll's default options? -q m -a l ? >> >> This might be fine for IT8 or other targets with lots of patches... >> >> But it's probably not such a good idea for a 24 patch ColorChecker, -q >> l -a S seems more appropriate... > > Yes, this is a good idea, and a perfect patch for you to submit :-) > > The kind of profile is listed in src/gcm-calibrate-argyll.h, which is > saved to priv->reference_kind, which is private data for the > GcmCalibrateArgyll object. You probably need to add a simple "if > (priv->reference_kind == > GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just > getting the type of profile (using > gcm_calibrate_argyll_precision_to_quality_arg) in the function > gcm_calibrate_argyll_device_generate_profile() which lives in > src/gcm-calibrate-argyll.c > > Make a few changes, and just do "git diff > test.patch" I think this patch should do it, it seems to work, though I didn't extensively test it. I also included the QPcard as well, it's a similar target... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-calibrate-argyll-low-patch-count-target-low-quality-single-shaper.patch Type: text/x-patch Size: 2556 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 8 21:58:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:58:24 +0100 Subject: Camera Profiling GUI Dialog Order Message-ID: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Hi, Currently to profile a camera, the GUI first asks for both files, and then asks for the chart type... This seems odd to me... It seems more natural to me, to first ask about the chart type, and then ask about the files... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-ask-reference-kind-first.patch Type: text/x-patch Size: 1241 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:23:07 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:23:07 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> Message-ID: <15e53e181002081423g6279830eq5c07be8d8aca9e9e@mail.gmail.com> On 8 February 2010 21:32, Pascal de Bruijn wrote: > I think this patch should do it, it seems to work, though I didn't > extensively test it. Great stuff. I've modified your patch a little (just passing the calibrate_argyll object and renaming a function) and committed it. I've attached the changed version. Well done! Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Do-low-quality-calibration-when-using-targets-with-a.patch Type: text/x-patch Size: 3393 bytes Desc: not available URL: From amluto at gmail.com Mon Feb 8 22:23:02 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Mon, 8 Feb 2010 17:23:02 -0500 Subject: Reduce autoconf requirement Message-ID: Hi all- For kicks, I just grabbed gnome-color-manager out of git, built it, and ran it on KDE4 on Fedora 12. (why not?) It seems to work (I haven't tested its Argyll integration yet.) To make it build, though, I had to decrease the autoconf required version, like this: diff --git a/configure.ac b/configure.ac index bf4e31f..d4f422b 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_PREREQ(2.65) +AC_PREREQ(2.63) AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) AC_CONFIG_SRCDIR(src) Is there any reason we require autogen 2.65? 2.63 from F12 seems to work just fine. shared-color-targets needs the same patch. As an aside, what's the profile graph on the right? Is it the calibration (VCGT), the gray axis of the profile, or something else? (I assume it's not the gray axis -- it doesn't really look like xicclu's output.) Thanks, Andy From hughsient at gmail.com Mon Feb 8 22:24:45 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:24:45 +0000 Subject: Camera Profiling GUI Dialog Order In-Reply-To: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> References: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Message-ID: <15e53e181002081424hc401819k29fc0a3c0ad96d8@mail.gmail.com> On 8 February 2010 21:58, Pascal de Bruijn wrote: > Currently to profile a camera, the GUI first asks for both files, and > then asks for the chart type... This seems odd to me... Agreed. > It seems more natural to me, to first ask about the chart type, and > then ask about the files... Committed, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 22:26:34 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 23:26:34 +0100 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> On Mon, Feb 8, 2010 at 11:23 PM, Andrew Lutomirski wrote: > Hi all- > > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) > > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) > > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. I apply the attached patch to git to make it work on Ubuntu Karmic. > shared-color-targets needs the same patch. > > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) If I'm not mistaken those are the TRC's... VCGT is only relevant for displays... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-git-demodernize-configure-ac.patch Type: text/x-patch Size: 2099 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:27:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:27:40 +0000 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <15e53e181002081427m68ba1894w9810233b37c1cf53@mail.gmail.com> On 8 February 2010 22:23, Andrew Lutomirski wrote: > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) Sure, it should work. > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) The 2.63 BR was from autoupdate'ing the scripts. > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. If it works, great! > shared-color-targets needs the same patch. Will do. > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) I think we need graph labels in this case. It's actually the TRC. Richard. From hughsient at gmail.com Mon Feb 8 22:28:44 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:28:44 +0000 Subject: Reduce autoconf requirement In-Reply-To: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> References: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> Message-ID: <15e53e181002081428p43926011mf3d6510d720a492c@mail.gmail.com> On 8 February 2010 22:26, Pascal de Bruijn wrote: > I apply the attached patch to git to make it work on Ubuntu Karmic. Hmm, that seems a bit drastic. Doesn't changing the version to 2.63 work okay in the Karmic case? Richard. From pmjdebruijn at pcode.nl Tue Feb 9 11:29:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:29:44 +0100 Subject: QPcard 201 thumbnail Message-ID: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> Hi, Here's a QPcard_201 thumbnail, postprocessed from a scanned image, submitted on the ArgyllCMS mailing list by Wallden Magnus. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201.png Type: image/png Size: 14124 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Tue Feb 9 11:35:55 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:35:55 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> Message-ID: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> On Tue, Feb 9, 2010 at 12:34 PM, Pascal de Bruijn wrote: > On Tue, Feb 9, 2010 at 12:29 PM, Pascal de Bruijn wrote: >> Hi, >> >> Here's a QPcard_201 thumbnail, postprocessed from a scanned image, >> submitted on the ArgyllCMS mailing list by Wallden Magnus. > > Whoops, forgot to remove the branding. Whoops, posted the hires version, not the thumbnail... Sorry, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201_unbranded.png Type: image/png Size: 12926 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 9 12:06:32 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 12:06:32 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> Message-ID: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> On 9 February 2010 11:35, Pascal de Bruijn wrote: > Whoops, posted the hires version, not the thumbnail... I've committed this after padding the height to 140 like the others. I really don't want the dialog resizing as the combobox elements are selected. Thanks, Richard. From pmjdebruijn at pcode.nl Tue Feb 9 13:10:48 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 14:10:48 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> Message-ID: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> On Tue, Feb 9, 2010 at 1:06 PM, Richard Hughes wrote: > On 9 February 2010 11:35, Pascal de Bruijn wrote: >> Whoops, posted the hires version, not the thumbnail... > > I've committed this after padding the height to 140 like the others. I > really don't want the dialog resizing as the combobox elements are > selected. I noticed you centered the image... Though, the white background suggests it's a big white card, with the patches centered, while it's not. We should use transparency here. I'll "fix" the image tonight, if you don't get to it first. Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 13:11:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:11:43 +0000 Subject: Using SANE? Message-ID: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> I'm thinking of using SANE (rather than udev like we do now) to get the list of scanners, and hopefully to be able to change settings on the device. It also allows us to change remote devices, not just locally plugged in USB ones. Is sane-backends-libs a problem for you distro guys? I'm not sure if it's installed by default on most distros, but it does pull in a few deps. Comments? Richard. From hughsient at gmail.com Tue Feb 9 13:17:15 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:17:15 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> Message-ID: <15e53e181002090517m76d879bdyba6cc199da454ebd@mail.gmail.com> On 9 February 2010 13:10, Pascal de Bruijn wrote: > I noticed you centered the image... Though, the white background > suggests it's a big white card, with the patches centered, while it's > not. Point taken. > We should use transparency here. I'll "fix" the image tonight, if you > don't get to it first. Okay. when you're submitting new binary files, the easiest way (for me) to do it, is this: git checkout -b the-subject-of-the-change git commit -a -m "Make the image background transparent" --author "Me Mine " ( the -a means "all changes to the working tree", the -m means "this is the commit message", and --author is so the right person gets listed in NEWS) git format-patch master git checkout master Then, all I have to do is use the command "git am" and I don't have to copy and paste your name, email, or come up with a commit message. If you get stuck, let me know. Richard. From fred at crozat.net Tue Feb 9 14:01:39 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:01:39 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> Message-ID: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> 2010/2/9 Richard Hughes : > I'm thinking of using SANE (rather than udev like we do now) to get > the list of scanners, and hopefully to be able to change settings on > the device. It also allows us to change remote devices, not just > locally plugged in USB ones. Is sane-backends-libs a problem for you > distro guys? I'm not sure if it's installed by default on most > distros, but it does pull in a few deps. How about using PackageKit to install it "on demand" ? ;) gnome-color-manager is installed "by default" in Mandriva 2010.0 but I'd like to keep sane ouf of the default install, if we can. -- Frederic Crozat From hughsient at gmail.com Tue Feb 9 14:21:02 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 14:21:02 +0000 Subject: Using SANE? In-Reply-To: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> Message-ID: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> On 9 February 2010 14:01, Frederic Crozat wrote: > 2010/2/9 Richard Hughes : >> I'm thinking of using SANE (rather than udev like we do now) to get >> the list of scanners, and hopefully to be able to change settings on >> the device. It also allows us to change remote devices, not just >> locally plugged in USB ones. Is sane-backends-libs a problem for you >> distro guys? I'm not sure if it's installed by default on most >> distros, but it does pull in a few deps. > > How about using PackageKit to install it "on demand" ? ;) Heh, this would be a library dep, not a tool dep. > gnome-color-manager is installed "by default" in Mandriva 2010.0 but > I'd like to keep sane ouf of the default install, if we can. You mean sane-backends-libs, rather than sane itself, right? Richard. From fred at crozat.net Tue Feb 9 14:34:22 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:34:22 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: <21ad25711002090634y7ef9e181oa77e6a7796a63c99@mail.gmail.com> 2010/2/9 Richard Hughes : > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Ah :( >> gnome-color-manager is installed "by default" in Mandriva 2010.0 but >> I'd like to keep sane ouf of the default install, if we can. > > You mean sane-backends-libs, rather than sane itself, right? Yes, I mean the lib package. It is 7.7MB installed, without checking its dependencies (of course, now, I've discovered openoffice-common is pulling libsane by default too :( If it could be a plugin, that would be nice :) -- Frederic Crozat From amluto at gmail.com Tue Feb 9 15:15:28 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Tue, 9 Feb 2010 10:15:28 -0500 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: On Tue, Feb 9, 2010 at 9:21 AM, Richard Hughes wrote: > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Is it safe to assume that anyone who wants to profile a scanner already has sane-backends-libs installed? If so, you could dlopen it and if that fails assume that there aren't any scanners. --Andy From pmjdebruijn at pcode.nl Tue Feb 9 19:28:41 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 20:28:41 +0100 Subject: Disconnected devices: create profiles for device disabled Message-ID: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Hi, When I have a EOS 400D disconnected, the "Create profiles for device" button is disabled, is this intentional? There is no good reason why my camera would need to be connected... For displays, it has it's advantages having the display connected for profiling though :p Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 19:49:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 19:49:22 +0000 Subject: Disconnected devices: create profiles for device disabled In-Reply-To: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> References: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Message-ID: <15e53e181002091149q7815c328n20cd83e87060efd6@mail.gmail.com> On 9 February 2010 19:28, Pascal de Bruijn wrote: > For displays, it has it's advantages having the display connected for > profiling though :p commit 9da8afc4f5dd9c7a0e252fa42483616c74696695 Author: Richard Hughes Date: Tue Feb 9 19:34:43 2010 +0000 Only require the device to be present if it is a display type :100644 100644 66af4b3... f25d118... M src/gcm-prefs.c Richard. From lars.tore at mulebakken.net Wed Feb 10 13:29:22 2010 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 10 Feb 2010 14:29:22 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > CMP_DT_003 > ColorChecker > ColorCheckerDC > ColorCheckerSG > Hutchcolor > i1_RGB_Scan_1.4 Here is a photo of the i1_RGB_Scan_1.4 scan target. I have removed the eye-one name. And it's OK with GPLv2+ Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: i1_RGB_Scan_14.png Type: image/png Size: 36266 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 10 19:38:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 10 Feb 2010 19:38:39 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> Message-ID: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> On 10 February 2010 17:17, Pascal de Bruijn wrote: > I modified the thumbnail slightly to even out the lighting, and > improve contrast. Looks great. > I attached a patch for the modified version for git master. Tanks, I've also merged the Makefile.am and gcm-prefs.c parts too. Thanks. Richard. From knizek.confy at volny.cz Wed Feb 10 20:01:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 21:01:36 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo Message-ID: <1265832096.26568.43.camel@athlon> Hello everyone on the list! GCM is getting feature-rich - display, scanner and camera profiling is already supported, but printer characterisation is still missing. Richard H would like to code the few bytes ;-) but he does not have a spectrophotometer at hand. On Richard's blog, Paul Finnigan proposed a donation from users - the ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 in the U.K., were Richard lives. The more expensive variant would require about 10 people @ USD 50 donation each. (Or less donors to buy in the U.S. and someone to actually deliver across the ocean.) At the moment, three of us offered a contribution. Anybody else here willing to help with even a smaller amount (probably via PayPal)? Or other suggestions? best regards, Milan Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Wed Feb 10 20:52:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 10 Feb 2010 21:52:27 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> On Wed, Feb 10, 2010 at 9:01 PM, Milan Kn??ek wrote: > Hello everyone on the list! > > ... > > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? I'd be willing to pitch in (PayPal) for about 25EUR... Regards, Pascal de Bruijn From knizek.confy at volny.cz Wed Feb 10 22:31:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 23:31:36 +0100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <1265841096.7579.76.camel@athlon> Getting back to update of the text: > -- > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. > -- Taking into account Graeme's points (thanks, it was helpful), how about this: (The GCM gamma fine tuning tool remains as it is - i.e. pure adjustment to LUT, not taking care about the monitor native gamma) --- Overall system gamma is a product of image encoding gamma, video card gamma and native gamma of the monitor and normally it should be equal to 1. You may want to adjust gamma to allow for non-standard viewing conditions (e.g increasing gamma in dim light at home). Refer to User Manual for more details. --- And this be included in User Manual: --- CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually emulate the same value. Traditionally, Linux and MS Windows operating systems use image encoding of 1/2.2 and do not apply any gamma adjustment to the image or video card LUT. Therefore the overall gamma is expected to be around 1.1 (which is useful to allow for dim viewing conditions at home environment). Apple used to use image encoding gamma close to 1/1.8 to naturally match the native gamma of printing devices (and therefore internally applied gamma adjustment of 1/1.45 before displaying images on monitor so that the images displayed correctly). Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding gamma has also the value of 1/2.2 to meet the requirements of consumer imaging industry. Before fine tuning the gamma in GCM, you should know what your monitor native gamma is, what display gamma you want to reach and then do the math yourself. --- regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pedro at pedrocr.net Thu Feb 11 08:49:07 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 00:49:07 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> Message-ID: <62e8012c1002110049j76960ec1jbeac96b428a2221c@mail.gmail.com> On Wed, Feb 10, 2010 at 12:52 PM, Pascal de Bruijn > I'd be willing to pitch in (PayPal) for about 25EUR... You can count me in for another 50$. Pedro From paul at fincc.com Thu Feb 11 09:54:05 2010 From: paul at fincc.com (Paul Finnigan) Date: Thu, 11 Feb 2010 09:54:05 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <1265882045.4190.8.camel@localhost> Hi everyone Sorry, I took a few days off reading the postings. Thanks Milan for trying to drive this one. On Wed, 2010-02-10 at 21:01 +0100, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. > > The more expensive variant would require about 10 people @ USD 50 > donation each. (Or less donors to buy in the U.S. and someone to > actually deliver across the ocean.) I am a photographer who likes to keep up with the Jones' (MS/Apple). To do this while running Linux I have had to make compromise after compromise with regard to 'Free' software. This is my own choice and I am not complaining about it. As an example I have paid for the Turbo Linux printer drivers. I have to say they are good, I do not begrudge the author his 29 euros. If I want free software then I believe it will cost me money at times. What Richard is providing is something, as a photographer, I have wanted for some time. He is also providing the source to the community. I know others are involved (thanks to everyone who is helping). I admit my suggestion of $50 was perhaps high. I just thought that as I know that TurboLinux drivers are popular with photographers I could pitch in a little above that price ($38). I am sure that we as a community can support ourselves. Look at what the Gnome community has already done. What is being asked here is that we get some hardware for a key developer to ensure that the software does what we all want, to help us manage colour. To get the ball rolling we need to set up an account. I am willing to let Richard have my $50 even if we do not reach the target of $500. If Richard or anyone else would like to mail me directly my address is paul at fincc dot com. -- Paul Finnigan From pmjdebruijn at pcode.nl Thu Feb 11 10:38:54 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 11:38:54 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> Message-ID: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> On Wed, Feb 10, 2010 at 8:38 PM, Richard Hughes wrote: > On 10 February 2010 17:17, Pascal de Bruijn wrote: >> I modified the thumbnail slightly to even out the lighting, and >> improve contrast. > > Looks great. I just processed the ColorCheckerSG image submitted by Hening Betterman on the ArgyllCMS mailing list. I attached a patch. Please verify before committing. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-ColorCheckerSG-target-image-submitted-by-Hening-.patch Type: text/x-patch Size: 45877 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 11 10:53:42 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:53:42 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> Message-ID: <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> On 11 February 2010 10:38, Pascal de Bruijn wrote: > I just processed the ColorCheckerSG image submitted by Hening > Betterman on the ArgyllCMS mailing list. > > I attached a patch. Please verify before committing. Perfect. Thanks. Richard. From hughsient at gmail.com Thu Feb 11 10:55:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:55:40 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> On 11 February 2010 09:54, Paul Finnigan wrote: > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If we don't reach the target I just have to convince my wife that it's a work thing and pony up the rest. Richard. From hughsient at gmail.com Thu Feb 11 11:05:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 11:05:28 +0000 Subject: Information re. display gamma In-Reply-To: <1265841096.7579.76.camel@athlon> References: <1265374532.31703.61.camel@athlon> <1265841096.7579.76.camel@athlon> Message-ID: <15e53e181002110305h113bd2c8kd8b863fbc1a4005e@mail.gmail.com> On 10 February 2010 22:31, Milan Kn??ek wrote: > Overall system gamma is a product of image encoding gamma, video card > gamma and native gamma of the monitor and normally it should be equal to > 1. You may want to adjust gamma to allow for non-standard viewing > conditions (e.g increasing gamma in dim light at home). Refer to User > Manual for more details. > --- > And this be included in User Manual: > --- > CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually > emulate the same value. > > Traditionally, Linux and MS Windows operating systems use image encoding > of 1/2.2 and do not apply any gamma adjustment to the image or video > card LUT. Therefore the overall gamma is expected to be around 1.1 > (which is useful to allow for dim viewing conditions at home > environment). > > Apple used to use image encoding gamma close to 1/1.8 to naturally match > the native gamma of printing devices (and therefore internally applied > gamma adjustment of 1/1.45 before displaying images on monitor so that > the images displayed correctly). > > Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding > gamma has also the value of 1/2.2 to meet the requirements of consumer > imaging industry. > > Before fine tuning the gamma in GCM, you should know what your monitor > native gamma is, what display gamma you want to reach and then do the > math yourself. Sounds good to me. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 11 11:57:49 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 12:57:49 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> Message-ID: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> On Thu, Feb 11, 2010 at 11:55 AM, Richard Hughes wrote: > On 11 February 2010 09:54, Paul Finnigan wrote: >> To get the ball rolling we need to set up an account. I am willing to >> let Richard have my $50 even if we do not reach the target of $500. > > If we don't reach the target I just have to convince my wife that it's > a work thing and pony up the rest. Then setup a PayPal account, and leave the details here :) Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 11 12:55:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 12:55:27 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> Message-ID: <15e53e181002110455l21da13pfe21eccf360fc192@mail.gmail.com> On 11 February 2010 11:57, Pascal de Bruijn wrote: > Then setup a PayPal account, and leave the details here :) I've already got a paypal account, richard at hughsie.com Please leave me your email addresses in any payments, in case we make nowhere near the total and I have to refund people. Thanks. Richard. From alexandre.prokoudine at gmail.com Thu Feb 11 19:30:38 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Thu, 11 Feb 2010 22:30:38 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> On 2/10/10, Milan Kn??ek wrote: > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? Yes, via PayPal. Count me in. Alexandre From pmjdebruijn at pcode.nl Thu Feb 11 20:44:25 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 21:44:25 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> Message-ID: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> On Thu, Feb 11, 2010 at 8:30 PM, Alexandre Prokoudine wrote: > On 2/10/10, Milan Kn??ek wrote: > >> Anybody else here willing to help with even a smaller amount (probably >> via PayPal)? Or other suggestions? > > Yes, via PayPal. Count me in. I just PayPalled 25 EUR... Regards, Pascal de Bruijn From pedro at pedrocr.net Fri Feb 12 01:42:10 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 17:42:10 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> Message-ID: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: > I just PayPalled 25 EUR... Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware organizations do this in scale? It would be great to be able to pitch in money to a common fund saying "I'd like this specific piece/type of hardware to work better in Linux" so that developers could get free access to hardware. By the way Richard, I've recently been through the battle of profiling my Epson R2880 with color munki, directly with argyll commands. I kept a few notes so I can tell you the commands that worked, the number of patches that were reasonable and especially about a small hack I did to be able to use much smaller patches with the color munki (and thus use less paper). Cheers, Pedro From pmjdebruijn at pcode.nl Fri Feb 12 07:38:57 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 08:38:57 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> On Fri, Feb 12, 2010 at 2:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: >> I just PayPalled 25 EUR... > > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? It would be great to be able to pitch > in money to a common fund saying "I'd like this specific piece/type of > hardware to work better in Linux" so that developers could get free > access to hardware. > > By the way Richard, I've recently been through the battle of profiling > my Epson R2880 with color munki, directly with argyll commands. I kept > a few notes so I can tell you the commands that worked, the number of > patches that were reasonable and especially about a small hack I did > to be able to use much smaller patches with the color munki (and thus > use less paper). Your hack was pretty cool, but it's not really handy to implement as a generic solution for GCM, we need no fuss solutions. This works very well for me... and would be a great default for medium quality: argyll-targen -v -d2 -f 210 xxx printtarg -v -i CM -h -T 300 -p A4 xxx colprof -q m -a l xxx For low quality the -h parameter can be dropped from printtarg, and lower the number of patches to ~90, whatever fits on a A4 piece of paper... One the the main problems is that these settings can vary from spectrophotometer to spectrophotometer... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 08:54:11 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:54:11 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <15e53e181002120054j23a0b855n55a671f870605644@mail.gmail.com> On 12 February 2010 07:38, Pascal de Bruijn > One the the main problems is that these settings can vary from > spectrophotometer to spectrophotometer... Sure, but we only care about a handful of types, and we can quite easily use the GUdev data to build up a profile for each device type, falling back if the device is unknown. I think it would be very useful to make Munki-specific data, as long as we have good fallbacks for the devices people keep secret. Richard. From hughsient at gmail.com Fri Feb 12 08:57:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:57:26 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> Message-ID: <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> On 11 February 2010 18:31, Pascal de Bruijn > But it's even worse, I screwed up the image as well... Here's a replacement. Applied, thanks. Do you want me to arrange for you to get GNOME commit access? It would mean you can commit this sort of thing without asking? Richard. From pedro at pedrocr.net Fri Feb 12 10:42:17 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:42:17 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: > Your hack was pretty cool, but it's not really handy to implement as a > generic solution for GCM, we need no fuss solutions. We will surely need a default mode that does that but my experience with doing it like you do bellow is that 200 patches isn't really reasonable. With the default settings you need 2 Letter pages to do ~190 and that generates pretty useless profiles. So to do the ~450+900 patches I ended up using for a decent profile you'd need ~15 pages which is a terrible waste of paper and ink. Like Richard says, it would be great to have the profiling instruments defined in a config somewhere, so that one can define a "Munki" and a "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" UI probably makes sense too as people doing color profiling would tend to be advanced users. > This works very well for me... and would be a great default for medium quality: > ?argyll-targen -v -d2 -f 210 xxx I ended up only getting good results at 450+900 patches. I suppose lower than that could also work. This should probably be given as an option to the user. Maybe a slider with markings or poor - basic - good - great and an automatic calculation of how many pages it is going to print, so that the user can do the tradeoff himself. > ?printtarg -v -i CM -h -T 300 -p A4 xxx My hack uses "-i i1". I haven't used the -T one. What does increasing the resolution help with? > ?colprof -q m -a l xxx "-a l" is default and I had also "-c mt" and "-d pp". Maybe they are not really needed. Cheers, Pedro From pedro at pedrocr.net Fri Feb 12 10:54:55 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:54:55 -0800 Subject: Building a library of ICC profiles Message-ID: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Hi, Is there any package that collects free (as in speech) ICC profiles? I see that Pascal's PPA has one printer, one camera and two or three displays. Are these just the ones you did yourself Pascal? I'd be more than happy to add the profiles I've been doing for the printer and monitor to some repository so that users without a calibration instrument can just use a profile from the library. I already have profiles for a Dell U2410 and an Epson R2880 with Glossy Epson paper. I'll be adding more papers to that too. One thing I haven't done yet is profiling my camera. How is that done and what is the benefit? I have a Sony A700 DSLR. Cheers, Pedro From hughsient at gmail.com Fri Feb 12 11:14:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:14:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Message-ID: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> On 12 February 2010 10:54, Pedro C?rte-Real wrote: > Is there any package that collects free (as in speech) ICC profiles? I > see that Pascal's PPA has one printer, one camera and two or three > displays. Are these just the ones you did yourself Pascal? There's http://github.com/hughsie/shared-color-profiles which may be of interest to you. > I'd be more than happy to add the profiles I've been doing for the > printer and monitor to some repository so that users without a > calibration instrument can just use a profile from the library. I > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > Epson paper. I'll be adding more papers to that too. I'm not so sure submitting user-generated profiles makes so much sense, I mean, your Epson R2880 probably has a quite different response to my (hypothetical) Epson R2880. If people think this is a good idea, I'd be wiling to set something like this up, as lets face it, a profile that is 3% off correct is better than no profile at all. > One thing I > haven't done yet is profiling my camera. How is that done and what is > the benefit? I have a Sony A700 DSLR. That's something you really want to do. We probably want to add a whole load of text in the help file in how to do this (sunny day, etc) but using GCM the process itself should be pretty easy. Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:15:52 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:15:52 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> Message-ID: <4c2c37f91002120315vc4ee9fcy7e31caaee1db3a4c@mail.gmail.com> On Fri, Feb 12, 2010 at 11:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: >> Your hack was pretty cool, but it's not really handy to implement as a >> generic solution for GCM, we need no fuss solutions. > > We will surely need a default mode that does that but my experience > with doing it like you do bellow is that 200 patches isn't really > reasonable. With the default settings you need 2 Letter pages to do > ~190 and that generates pretty useless profiles. So to do the ~450+900 > patches I ended up using for a decent profile you'd need ~15 pages > which is a terrible waste of paper and ink. > > Like Richard says, it would be great to have the profiling instruments > defined in a config somewhere, so that one can define a "Munki" and a > "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" > UI probably makes sense too as people doing color profiling would tend > to be advanced users. > >> This works very well for me... and would be a great default for medium quality: >> ?argyll-targen -v -d2 -f 210 xxx > > I ended up only getting good results at 450+900 patches. I suppose > lower than that could also work. This should probably be given as an > option to the user. Maybe a slider with markings or poor - basic - > good - great and an automatic calculation of how many pages it is > going to print, so that the user can do the tradeoff himself. Highly depends on what kind of accuracy ones expects... 210 patches and -qm works reasonably well... I actually tried making a profile using 840 patches, and -qh, and I don't see a big difference here... Though my printer is much crappier than yours. >> ?printtarg -v -i CM -h -T 300 -p A4 xxx Anyway, patches count should most likely always be multiple of what a single sheet can hold... 1x A4 -> 210 2x A4 -> 420 3x A4 -> 630 4x A4 -> 840 This may be different for letter (190?). > My hack uses "-i i1". I haven't used the -T one. What does increasing > the resolution help with? This is seriously not an option for GCM... requiring users to make their own DIY patch reading guide. The colorimeter/spectrophotometer should work as develivered by the manufacturer... GNOME is about making things work as expected... not requiring DIY hobbying/hacks... For these kinds of strategies, using the Argyll commandline tools should be fine. Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:20:27 +0000 Subject: Adding a libtiff dep? Message-ID: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to add a libtiff hard dep on gnome-color-manager. All distros should already be installing this by default, but I wanted to check to see if anyone had any issue with this. Speak now, or forever hold your peace! :-) Thanks, Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:22:46 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:22:46 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: >> Is there any package that collects free (as in speech) ICC profiles? I >> see that Pascal's PPA has one printer, one camera and two or three >> displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. Those profiles are mostly for my private use... The camera profiles are probably generally usable though... >> I'd be more than happy to add the profiles I've been doing for the >> printer and monitor to some repository so that users without a >> calibration instrument can just use a profile from the library. I >> already have profiles for a Dell U2410 and an Epson R2880 with Glossy >> Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. One big problem with printer profiles are driver setttings, since profiles are also very specific to driver settings... I have no clue on how to solve that... Ideally you'd want the printer settings to be embedded in the profile. > If people think this is a good idea, I'd be wiling to set something > like this up, as lets face it, a profile that is 3% off correct is > better than no profile at all. Yeah sortof... >> One thing I >> haven't done yet is profiling my camera. How is that done and what is >> the benefit? I have a Sony A700 DSLR. > > That's something you really want to do. We probably want to add a > whole load of text in the help file in how to do this (sunny day, etc) > but using GCM the process itself should be pretty easy. I wrote about this here: http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Though the article is dated, and should be revised... I did make a few new discoveries... For example, I only recently noticed that strobes actually work well as reference light for generic profiles... I'm probably going to do a new blog post over the weekend... Here are some generic tips van raw photography with UFRaw in general: http://blog.pcode.nl/2009/08/23/ufraw-faq/ Most of it should apply to other dcraw based applications as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Fri Feb 12 11:24:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:24:10 +0100 Subject: Adding a libtiff dep? In-Reply-To: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> Message-ID: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> On Fri, Feb 12, 2010 at 12:20 PM, Richard Hughes wrote: > To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to > add a libtiff hard dep on gnome-color-manager. All distros should > already be installing this by default, but I wanted to check to see if > anyone had any issue with this. > > Speak now, or forever hold your peace! :-) Seems fine... Doesn't eog already depend on libtiff anyway? Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:26:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:26:28 +0000 Subject: Adding a libtiff dep? In-Reply-To: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> Message-ID: <15e53e181002120326q1d693e40wa44d44ab56c5efe0@mail.gmail.com> On 12 February 2010 11:24, Pascal de Bruijn wrote: > Seems fine... Doesn't eog already depend on libtiff anyway? Sure, but eog might not be installed on the live-cd, and g-c-m probably should... Richard. From hughsient at gmail.com Fri Feb 12 11:28:54 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:28:54 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> On 12 February 2010 11:22, Pascal de Bruijn wrote: > I wrote about this here: > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Yes, this entry is very helpful, and I would love to see a large chunk added to the GNOME Color Manager help pages, if you're okay with re-licensing the content. Richard. From dan at berrange.com Fri Feb 12 11:30:51 2010 From: dan at berrange.com (Daniel P. Berrange) Date: Fri, 12 Feb 2010 11:30:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <20100212113051.GA13638@berrange.com> On Fri, Feb 12, 2010 at 11:14:51AM +0000, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: > > Is there any package that collects free (as in speech) ICC profiles? I > > see that Pascal's PPA has one printer, one camera and two or three > > displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. > > > I'd be more than happy to add the profiles I've been doing for the > > printer and monitor to some repository so that users without a > > calibration instrument can just use a profile from the library. I > > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > > Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. IIUC, printer profiles will vary on the set (hardware, ink, driver, paper) so building a library of profiles is quite large task. You could make it more managable by initially concentrating on the printer manufacturer's own recommended brand/combination of ink+paper+drivers Regards, Daniel -- |: http://berrange.com/ -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://freshmeat.net/~danielpb/ -o- http://gtk-vnc.sourceforge.net :| From pmjdebruijn at pcode.nl Fri Feb 12 12:01:33 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 13:01:33 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> Message-ID: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> On Fri, Feb 12, 2010 at 12:28 PM, Richard Hughes wrote: > On 12 February 2010 11:22, Pascal de Bruijn wrote: >> I wrote about this here: >> ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Yes, this entry is very helpful, and I would love to see a large chunk > added to the GNOME Color Manager help pages, if you're okay with > re-licensing the content. No problem, but I'd like my rewrite to be in the help pages :) Not this particular article... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 12:09:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 12:09:23 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> Message-ID: <15e53e181002120409veeecbbcn1f4a04d55b353beb@mail.gmail.com> On 12 February 2010 12:01, Pascal de Bruijn wrote: > No problem, but I'd like my rewrite to be in the help pages :) Cool. Just add text to help/C/gnome-color-manager.xml and format a patch as normal. If you get stuck with docbook, give me a shout. Richard. From alexandre.prokoudine at gmail.com Fri Feb 12 12:54:08 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 12 Feb 2010 15:54:08 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <733f2c731002120454p2f0143ddgf9dfe37e4b9a3713@mail.gmail.com> On Fri, Feb 12, 2010 at 4:42 AM, Pedro C?rte-Real wrote: > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? http://linuxfund.org/ Alexandre From hughsient at gmail.com Fri Feb 12 15:10:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 15:10:10 +0000 Subject: Color correcting projectors? Message-ID: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> In GCM we currently support two types of display profiling. Internal (LVDS) panels are internal to the system, and external panels (DVI and the others) are external to the system. What different settings do we need to do for projectors? We certainly need to give different instructions (which we also need to write), but will argyll just process these like a low-gamut LCD screen? Are there any options we need to add? Richard. From pmjdebruijn at pcode.nl Fri Feb 12 15:25:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 16:25:50 +0100 Subject: Color correcting projectors? In-Reply-To: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> Message-ID: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> On Fri, Feb 12, 2010 at 4:10 PM, Richard Hughes wrote: > In GCM we currently support two types of display profiling. Internal > (LVDS) panels are internal to the system, and external panels (DVI and > the others) are external to the system. > > What different settings do we need to do for projectors? We certainly > need to give different instructions (which we also need to write), but > will argyll just process these like a low-gamut LCD screen? Are there > any options we need to add? Well I think Argyll has a -p option :) And the instructions obviously need to be different, there's a "rule" which states the colorimeter should be 1.5 times the height of the projected image away from the "screen", or something like that... Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 12 20:28:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 12 Feb 2010 21:28:14 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <1266006494.22377.14.camel@athlon> Paul Finnigan p??e v ?t 11. 02. 2010 v 09:54 +0000: > I am a photographer who likes to keep up with the Jones' (MS/Apple). To > do this while running Linux I have had to make compromise after > compromise with regard to 'Free' software. This is my own choice and I > am not complaining about it. Paul said it well, it fits my experience. I had to learn a lot of things to be able to use Linux for my photographic hobby and I hope that soon the photographer's life with Linux be more user friendly. > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If > Richard or anyone else would like to mail me directly my address is paul > at fincc dot com. I have given ?100, maybe a bit more than usual but anyway I hope Richard will not feel obliged to prefer my wishes about GCM - it is a donation, not a wage. Also, no need to return if the target is not reached. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Fri Feb 12 22:00:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 23:00:20 +0100 Subject: Perspective Distortion Compensation Message-ID: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Hi, Currently input profile calibration can fail because a target has even the slightest perspective distortion. Argyll can compensate for that within reason. This patch should enable perspective distortion compensation. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-have-scanin-compensate-for-perspective-distortion.patch Type: text/x-patch Size: 911 bytes Desc: not available URL: From paul at fincc.com Sat Feb 13 01:16:32 2010 From: paul at fincc.com (Paul Finnigan) Date: Sat, 13 Feb 2010 01:16:32 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266006494.22377.14.camel@athlon> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> Message-ID: <1266023792.2313.21.camel@localhost> Milan On Fri, 2010-02-12 at 21:28 +0100, Milan Kn??ek wrote: > I have given ?100, maybe a bit more than usual but anyway I hope Richard > will not feel obliged to prefer my wishes about GCM - it is a donation, > not a wage. Also, no need to return if the target is not reached. What a nice way of putting it! It sounds like you are used to being part of a community, rather than a gathering of geeks. It is amazing but through everyone's (OK in the main Richard's) efforts I feel part of this community without putting anything in myself (I am still attempting to get setup in paypal. I am ancient and not used to money being passed over the ether. Don't worry Richard I will put my money where my mouth is as soon as I can get money into paypal). Thanks to this project I have found many new friends. How can I help? Richard has suggested people to write the help documentation. I am willing but what format and how? Is there a howto I can read anywhere that would help? I am desperate to do more but my skills are in the area of project and service management not coding. -- Paul Finnigan From graeme2 at argyllcms.com Sat Feb 13 01:17:23 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 13 Feb 2010 12:17:23 +1100 Subject: Color correcting projectors? In-Reply-To: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> Message-ID: <4B75FDA3.9050601@argyllcms.com> Pascal de Bruijn wrote: > Well I think Argyll has a -p option :) -p is an instrument config. option, and is currently only applicable to a single instrument, the ColorMunki. You can use other instruments to measure projectors, but they don't have a special mode for it. (I think I'll changed dispcal and dispread to automatically fallback to display mode if the instrument doesn't have a projector mode, to make them a bit more forgiving). Graeme Gill. From hughsient at gmail.com Sat Feb 13 09:17:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:17:06 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266023792.2313.21.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> <1266023792.2313.21.camel@localhost> Message-ID: <15e53e181002130117s270af2b9kcc97bc7ef471c82@mail.gmail.com> On 13 February 2010 01:16, Paul Finnigan wrote: > What a nice way of putting it! It sounds like you are used to being part > of a community, rather than a gathering of geeks. It is amazing but > through everyone's (OK in the main Richard's) efforts I feel part of > this community without putting anything in myself (I am still attempting > to get setup in paypal. I am ancient and not used to money being passed > over the ether. Don't worry Richard I will put my money where my mouth > is as soon as I can get money into paypal). We've very nearly reached the total! I'm nearly at the "amount I can sneak on the shared credit card without the wife noticing" stage :-) > Thanks to this project I have found many new friends. How can I help? > Richard has suggested people to write the help documentation. I am > willing but what format and how? Is there a howto I can read anywhere > that would help? I am desperate to do more but my skills are in the area > of project and service management not coding. Right, then we need to start with some documentation or UI fixes, and then work on from there. My spelling and grammar are notoriously bad, so this is where I need the most help. If you first: * download the git package (using yum, apt-get, or your distro tool) * "clone" the developers checkout. For this you want to follow http://live.gnome.org/Git/Developers -- specifically the project name is gnome-color-manager (you can also ignore 90% of that page, it's overly complicated, but maybe a good read if you want detail) * create you're own personal branch (not on the server): git checkout -b my-playground-branch * Edit the file help/C/gnome-color-manager.xml, copying the syntax (e.g. using for a new paragraph), making the changes you want * "commit" the changes, which basically means you save them, and give them a description: git commit -a -m "Correct the spelling of Colour to Color" --author "Richard Hughes " * get a text file of the changes you want to send to us: "git format-patch master" (this generates 0001-a-file-with-a-peculiar-name.patch) Send the 0001-a-file-with-a-peculiar-name.patch as an attachment to this mailing list. Then you can either go back to the pristine upstream tree "git checkout master" or stay on your private tree and make more changes. You can commit many small changes and then do "git format-patch" and you get files 0001, 0002, 0003, 0004, etc and send them all in one long email. If you break stuff, then you can get rid of all your changes (since the last time you committed them) with "git reset --hard", and you can ensure you've got the latest changes from upstream by doing "git checkout master && git pull --rebase" It sounds complicated, but give it a try and yell when you get stuck. Weekdays I'm on IRC if that helps. Richard. From hughsient at gmail.com Sat Feb 13 09:19:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:19:58 +0000 Subject: Perspective Distortion Compensation In-Reply-To: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> References: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Message-ID: <15e53e181002130119k4b3d9a16j403ff3c4aa2f4c31@mail.gmail.com> On 12 February 2010 22:00, Pascal de Bruijn wrote: > This patch should enable perspective distortion compensation. Applied, thanks. Richard. From pmjdebruijn at pcode.nl Sat Feb 13 10:43:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 11:43:44 +0100 Subject: Bug #605259: Colorimeter name in profile description Message-ID: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Hi, Currently on my Ubuntu Karmic system, the colorimeter name still isn't getting into the profile description... Could you give me any pointer how the colorimeter is resolved? And where I should look into the sources? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 14:09:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 14:09:51 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Message-ID: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> On 13 February 2010 10:43, Pascal de Bruijn wrote: > Currently on my Ubuntu Karmic system, the colorimeter name still isn't > getting into the profile description... Hmm, I'm getting "Huey" prepended to my profile. > Could you give me any pointer how the colorimeter is resolved? And > where I should look into the sources? Well, take a look at src/gcm-color-device.c and make sure that the model and vendor are being set correctly. It's possible you need to add: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="usb-db %p" to your 55-Argyll.rules file, if your device doesn't have an entry in the kernel USB driver. That's what I've done in hargyll, and if it fixes it for you too, I'll push this patch to Graeme. Richard From pmjdebruijn at pcode.nl Sat Feb 13 19:40:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 20:40:24 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> On Fri, Feb 12, 2010 at 12:22 PM, Pascal de Bruijn wrote: > On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: >> On 12 February 2010 10:54, Pedro C?rte-Real wrote: >>> One thing I >>> haven't done yet is profiling my camera. How is that done and what is >>> the benefit? I have a Sony A700 DSLR. >> >> That's something you really want to do. We probably want to add a >> whole load of text in the help file in how to do this (sunny day, etc) >> but using GCM the process itself should be pretty easy. > > I wrote about this here: > > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Though the article is dated, and should be revised... I did make a few > new discoveries... > > For example, I only recently noticed that strobes actually work well > as reference light for generic profiles... > > I'm probably going to do a new blog post over the weekend... > > Here are some generic tips van raw photography with UFRaw in general: > > ?http://blog.pcode.nl/2009/08/23/ufraw-faq/ > > Most of it should apply to other dcraw based applications as well. I'm rewriting my article as I type this, it should already be accessible as a preview: http://blog.pcode.nl/?p=551&preview=true Any comments before I publish? Any thing not clear? If all goes well (I still need to do some more testing), this article can be reworked into GCM help. Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 21:27:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 21:27:34 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <15e53e181002131327l76d8dc0du282ca3c5a5be4423@mail.gmail.com> On 10 February 2010 20:01, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. We've reached the total! Thanks guys, I feel very humbled. Thanks. ColorMunki Photo is ordered, and will arrive in about a weeks time. Richard. From hughsient at gmail.com Sun Feb 14 20:56:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 14 Feb 2010 20:56:10 +0000 Subject: Request for colorimeter figures Message-ID: <15e53e181002141256t1c39960dle71b65839ca6d451@mail.gmail.com> Hey guys, I've added support to GCM today to display images to help the user attach the colorimeter device to the screen, and to set it to correct mode. I've attached two images as examples. If anybody is interested in drawing pictures (or improving mine) it would be very welcome. I don't mind how many images we add. Ideally we should show images of the most common colorimeters in existence, and how to switch things to the correct modes. You'll have to create SVG figures yourself (I used inkscape) and obviously not include any trademarks. If you're a worse artist than me, feel free to send a photo of the colorimeter attached to the screen, and switching between different modes and one of us geeks on list can convert this to a SVG. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: huey-attach.svg Type: image/svg+xml Size: 61010 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: munki-projector.svg Type: image/svg+xml Size: 66407 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 15 01:23:01 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 02:23:01 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> Message-ID: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> On Sat, Feb 13, 2010 at 3:09 PM, Richard Hughes wrote: > On 13 February 2010 10:43, Pascal de Bruijn wrote: >> Currently on my Ubuntu Karmic system, the colorimeter name still isn't >> getting into the profile description... > > Hmm, I'm getting "Huey" prepended to my profile. > >> Could you give me any pointer how the colorimeter is resolved? And >> where I should look into the sources? > > Well, take a look at src/gcm-color-device.c and make sure that the > model and vendor are being set correctly. It's possible you need to > add: > > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="usb-db %p" > > to your 55-Argyll.rules file, if your device doesn't have an entry in > the kernel USB driver. That's what I've done in hargyll, and if it > fixes it for you too, I'll push this patch to Graeme. It's not fixing it for me now... But I don't think I have the usb-db utility installed... Where should I have gotten it from? Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 11:34:49 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 11:34:49 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> Message-ID: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> On 15 February 2010 01:23, Pascal de Bruijn wrote: > It's not fixing it for me now... But I don't think I have the usb-db > utility installed... Where should I have gotten it from? Any modern udev should have it. Use "udevadm monitor" to monitor the device events as the device is plugged in. Richard. From pmjdebruijn at pcode.nl Mon Feb 15 11:36:12 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 12:36:12 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> Message-ID: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: > On 15 February 2010 01:23, Pascal de Bruijn wrote: >> It's not fixing it for me now... But I don't think I have the usb-db >> utility installed... Where should I have gotten it from? > > Any modern udev should have it. Use "udevadm monitor" to monitor the > device events as the device is plugged in. Indeed $ dpkg -L udev | grep usb-db /lib/udev/usb-db But it's not in my path, I'm not sure whether that matters? I'll try udev monitor later today. Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 20:34:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 20:34:26 +0000 Subject: Adding support for xsane Message-ID: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> I've coded some initial support for xsane-based application in a private branch. It basically writes the right thing in the per-user xsane directories for the system and device settings. I'm not sure whether to merge it to master or not, as it's pretty hacky code. Ideally we would talk to easy-scan / gnome-scan in the future using a nice DBus interface, but I think that's a few years away. It does not depend on sane (that's a separate branch...) and if you don't use xsane then the file just gets written and nothing uses it. So, what do you guys think? Richard. From knizek.confy at volny.cz Mon Feb 15 21:19:05 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 15 Feb 2010 22:19:05 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> Message-ID: <1266268745.6707.9.camel@athlon> Pascal de Bruijn p??e v So 13. 02. 2010 v 20:40 +0100: > I'm rewriting my article as I type this, it should already be > accessible as a preview: > > http://blog.pcode.nl/?p=551&preview=true > > Any comments before I publish? Any thing not clear? > Pascal - the page is "not found". I guess you would actually have to post it to make it available to public. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 15 22:09:10 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 16 Feb 2010 01:09:10 +0300 Subject: Adding support for xsane In-Reply-To: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> Message-ID: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> On 2/15/10, Richard Hughes wrote: > Ideally we would talk to easy-scan / gnome-scan in the future using a > nice DBus interface, but I think that's a few years away. Robert Ancell blogged recently that he is going to implement color management after 1.0, and his is now in post 0.9.0 bugfixing mode. So it's probably not that bad :) Alexandre From hughsient at gmail.com Mon Feb 15 22:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 22:16:56 +0000 Subject: Adding support for xsane In-Reply-To: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> Message-ID: <15e53e181002151416p37413a9je110eab793646198@mail.gmail.com> On 15 February 2010 22:09, Alexandre Prokoudine wrote: > Robert Ancell blogged recently that he is going to implement color > management after 1.0, and his is now in post 0.9.0 bugfixing mode. So > it's probably not that bad :) Cool. What we need him to do is: * Provide a method to scan a target without applying any icc profiles at all, so we can use it to calibrate the device. * Get the default icc profile assigned by GCM using the udev path or the SANE id, for normal scans. * Tag the resulting scans with the assigned ICC profile Should be no more than an afternoons hacking :-) Richard. From paul at fincc.com Tue Feb 16 00:45:54 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 00:45:54 +0000 Subject: Camera Support Message-ID: <1266281154.2768.8.camel@localhost> Hi I decided to attempt to use a profile with my camera. The camera does not appear on the list of devices, even when it is plugged in. Am I missing something? I can import my profiles but I cannot assign them to a device. The camera is a Nikon D700. Gnome recognises the camera and allows me to open a nautilus viewer on the memory card, open photographs etc. I can see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b0 ProdID=0422 Rev= 1.00 S: Manufacturer=NIKON S: Product=NIKON DSC D700 S: SerialNumber=000002034583 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=usbfs E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms If I run gcm in verbose mode: TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 So we see the camera connect. Am I missing something? I am running off a copy from the GIT -- Paul Finnigan Finnigan Computer Consultants Ltd. From hughsient at gmail.com Tue Feb 16 09:26:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 09:26:26 +0000 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> On 16 February 2010 00:45, Paul Finnigan wrote: > If I run gcm in verbose mode: > > TI:00:40:05 FI:gcm-colorimeter.c ? ? ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:05 ? ? FI:gcm-colorimeter.c ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > > So we see the camera connect. Am I missing something? Is that all you get when you connect the camera? Could you attach the output from "udevadm monitor" when you plug in the device please. I'm a little surprised it doesn't work, given my D60 works fine. Thanks. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 11:54:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 12:54:27 +0100 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > Hi > > I decided to attempt to use a profile with my camera. The camera does > not appear on the list of devices, even when it is plugged in. Am I > missing something? I can import my profiles but I cannot assign them to > a device. Currently assigning camera profiles in GCM has no real function yet, since the RAW converters don't use this information. > The camera is a Nikon D700. Gnome recognises the camera and allows me to > open a nautilus viewer on the memory card, open photographs etc. I can > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > snip snip > > So we see the camera connect. Am I missing something? > > I am running off a copy from the GIT It works just fine with my EOS 400D as well... Also does your D700 have a recent firmware? Regards, Pascal de Bruijn From paul at fincc.com Tue Feb 16 11:57:31 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 11:57:31 +0000 Subject: Camera Support In-Reply-To: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> Message-ID: <1266321451.6701.12.camel@localhost> Richard On Tue, 2010-02-16 at 09:26 +0000, Richard Hughes wrote: > On 16 February 2010 00:45, Paul Finnigan wrote: > > If I run gcm in verbose mode: > > > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > > > So we see the camera connect. Am I missing something? > > Is that all you get when you connect the camera? Could you attach the > output from "udevadm monitor" when you plug in the device please. I'm > a little surprised it doesn't work, given my D60 works fine. Thanks. > > Richard. That is all I get from gcm. I am running Fedora 12 and have compiled gcm from the GIT. I only ever connect my camera to copy files to disc. I never ever read them directly with an application, or not in my normal workflow. That is I only use my Nikon as a (very expensive) memory stick! OK Fedora uses gphoto2 and gvfs. As requested 'udevadm moniotor' when connecting the camera gives: [paul at ewing ~]udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266321215.801858] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) KERNEL[1266321215.802262] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) UDEV [1266321215.813200] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) UDEV [1266321215.821229] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) Nautilus then lets me view photos using: gphoto2://[usb:001,009]/DCIM/100ND700 Thanks -- Paul Finnigan From paul at fincc.com Tue Feb 16 12:19:26 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 12:19:26 +0000 Subject: Camera Support In-Reply-To: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> Message-ID: <1266322766.6701.21.camel@localhost> Pascal On Tue, 2010-02-16 at 12:54 +0100, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > > Hi > > > > I decided to attempt to use a profile with my camera. The camera does > > not appear on the list of devices, even when it is plugged in. Am I > > missing something? I can import my profiles but I cannot assign them to > > a device. > > Currently assigning camera profiles in GCM has no real function yet, > since the RAW converters don't use this information. I knew that, which is why I had not tired it until now. I am looking at the help pages as I had (stupidly) volunteered and wanted to show an input device on the menu. My current scanner a Canon Lide 500 does not work with Sane so I cannot show that. > > The camera is a Nikon D700. Gnome recognises the camera and allows me to > > open a nautilus viewer on the memory card, open photographs etc. I can > > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > > > > snip snip > > > > > So we see the camera connect. Am I missing something? > > > > I am running off a copy from the GIT > > It works just fine with my EOS 400D as well... Also does your D700 > have a recent firmware? I would guess not. I have had it over 12 months, and have never had a need to update the firmware. If I need to I will update the firmware. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Tue Feb 16 12:29:45 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 13:29:45 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> Message-ID: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> On Mon, Feb 15, 2010 at 12:36 PM, Pascal de Bruijn wrote: > On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: >> On 15 February 2010 01:23, Pascal de Bruijn wrote: >>> It's not fixing it for me now... But I don't think I have the usb-db >>> utility installed... Where should I have gotten it from? >> >> Any modern udev should have it. Use "udevadm monitor" to monitor the >> device events as the device is plugged in. > > Indeed > > $ dpkg -L udev | grep usb-db > /lib/udev/usb-db > > But it's not in my path, I'm not sure whether that matters? I changed the udev-rule to include the full path of usb-db: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="/lib/udev/usb-db %p" Does this need to be in a particular place in 55-Argyll.rules? I attached the full file. After making the above change, I rebooted my system, and ran the udevadm monitor while plugging in the Huey. The results are attached. Regards, Pascal de Bruijn -------------- next part -------------- pmjdebruijn at biovore:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266323110.972649] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323110.975186] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323111.064958] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323111.106596] add /module/usbhid (module) KERNEL[1266323111.108080] add /bus/hid/drivers/generic-usb (drivers) UDEV [1266323111.108125] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323111.108145] add /bus/usb/drivers/hiddev (drivers) KERNEL[1266323111.108161] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.108519] add /bus/usb/drivers/hiddev (drivers) UDEV [1266323111.108804] add /module/usbhid (module) UDEV [1266323111.109292] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.110702] add /bus/hid/drivers/generic-usb (drivers) KERNEL[1266323117.762463] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323117.762504] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323117.763909] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323117.766370] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.321652] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.328367] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323121.338002] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323121.341140] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) pmjdebruijn at biovore:~$ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG -------------- next part -------------- A non-text attachment was scrubbed... Name: 55-Argyll.rules Type: application/octet-stream Size: 1953 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 16 21:43:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 21:43:31 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> Message-ID: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> On 16 February 2010 12:29, Pascal de Bruijn wrote: > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="/lib/udev/usb-db %p" Hmm, I don't think you need to include the full path this. > Does this need to be in a particular place in 55-Argyll.rules? I > attached the full file. > > After making the above change, I rebooted my system, and ran the > udevadm monitor while plugging in the Huey. The results are attached. Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I assume this is a Huey: 0971 Gretag-Macbeth AG 2005 Huey If it's not a Huey, then we have a problem, and we need to add an entry to usb.ids. See http://www.linux-usb.org/usb-ids.html if this is the case. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 21:56:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 22:56:10 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> Message-ID: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: > On 16 February 2010 12:29, Pascal de Bruijn wrote: >> # color calibration device >> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >> IMPORT{program}="/lib/udev/usb-db %p" > > Hmm, I don't think you need to include the full path this. Well the other lines include full paths, it would seem good practice consistency-wise. >> Does this need to be in a particular place in 55-Argyll.rules? I >> attached the full file. >> >> After making the above change, I rebooted my system, and ran the >> udevadm monitor while plugging in the Huey. The results are attached. > > Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like > ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I > assume this is a Huey: > > 0971 ?Gretag-Macbeth AG > ? ? ? ?2005 ?Huey I updated the usb database, and guess what: $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG ID_MODEL_FROM_DATABASE=Huey Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:13:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:13:17 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <4c2c37f91002161413w182c491cu2f8a269bf6bd91c4@mail.gmail.com> On Tue, Feb 16, 2010 at 10:56 PM, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: >> On 16 February 2010 12:29, Pascal de Bruijn wrote: >>> # color calibration device >>> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >>> IMPORT{program}="/lib/udev/usb-db %p" >> >> Hmm, I don't think you need to include the full path this. > > Well the other lines include full paths, it would seem good practice > consistency-wise. > >>> Does this need to be in a particular place in 55-Argyll.rules? I >>> attached the full file. >>> >>> After making the above change, I rebooted my system, and ran the >>> udevadm monitor while plugging in the Huey. The results are attached. >> >> Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like >> ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I >> assume this is a Huey: >> >> 0971 ?Gretag-Macbeth AG >> ? ? ? ?2005 ?Huey > > I updated the usb database, and guess what: > > $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 > ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG > ID_MODEL_FROM_DATABASE=Huey Ugh, I just calibrated my screen and it worked like a charm... Please push the udev rule to Graeme. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:31:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:31:38 +0100 Subject: [PATCH] New USB ID: X-Rite/Gretag-MacBeth ColorMunki Message-ID: <4c2c37f91002161431l7989a672gd240def3bbcf5a23@mail.gmail.com> Hi, The included patch has the USB ID for: http://www.colormunki.com/ The device is a spectrophotometer from X-Rite which recently acquired Gretag-Macbeth. I've tested using udev's usb-db, and the lookup works with my device. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: usb-ids-colormunki.patch Type: text/x-patch Size: 312 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 17 09:33:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 09:33:21 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <15e53e181002170133j3c968710y4dc7996dc31bc5b@mail.gmail.com> On 16 February 2010 21:56, Pascal de Bruijn wrote: > Well the other lines include full paths, it would seem good practice > consistency-wise. I disagree, but it shouldn't hurt as even on 64 bit the early udev boot is in /lib, not /lib64. Richard. From hughsient at gmail.com Wed Feb 17 14:05:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 14:05:27 +0000 Subject: Adding printer profiling support Message-ID: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> In a few days time, my nice lovely ColorMunki should be delivered. Before it is, I figured I should get up to speed on how to profile printers, so we know what UI to add to GCM, and so I can get up to speed quickly. So. Does anybody have any hints, tips or suggestions on how to calibrate a printer. Device specific options (e.g. "The ColorMunki works really well with -f234 -g567") are more than welcome, as we already know the colorimeter device type. In particular, we need to support printing to 6x4 inch cards, A4 and letter paper. I would love to integrate this better with CUPS (using the GTK print dialog for instance) than what we can do on the command line. We'll also need scans of the patches sheets that we send out, so we can show the user _how_ to scan in the patches. We'll also probably need a timer for "waiting for the ink to dry" and that sort of thing. Ideas very welcome. Thanks, Richard. From hughsient at gmail.com Wed Feb 17 19:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 19:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> Message-ID: <15e53e181002171147u290e197fnfe1e857f62b6723a@mail.gmail.com> On 17 February 2010 17:20, Pascal de Bruijn wrote: > J?rg Rosenkranz privately submitted an image of the LaserSoftDCPro > target to me. The attached patch should make it available for GCM. Applied, thanks. Richard. From pedro at pedrocr.net Thu Feb 18 04:50:09 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Wed, 17 Feb 2010 20:50:09 -0800 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: > In a few days time, my nice lovely ColorMunki should be delivered. > Before it is, I figured I should get up to speed on how to profile > printers, so we know what UI to add to GCM, and so I can get up to > speed quickly. > > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Here is my experience with the Munki from my notes. I've used it successfully to both profile a Dell U2410 LCD screen and an Epson R2880. The LCD profiling should work already but I ended up using the tools directly because g-c-m was failing to interact correctly with the argyll tools when they asked to change the position of the device. I think this has been fixed but haven't checked. Anyway for the printing profiling my steps were: 1 - Generate a set of color patches $argyll-targen -f 900 -v -d2 -c -A.8 This gave good results in the end. I did a first round of profiling with 450 patches and that was used as BestPreviousProfile. For the first round it would be instead: $argyll-targen -f 450 -v -d2 In general the number of patches to create is a judgment call. I don't know how we can present this option to the user. Maybe doing the calculation in reverse and asking him how many sheets he is willing to print and scan and then giving him an idea of how good a profile that generates. To then actually generate the files to print: $ printtarg -t -v -iCM -pLetter "Letter" should obviously be changed to whatever paper the user wants to use. The -iCM generates normally sized patches for the Munki, which will require many sheets of paper to fit the 900 patches. See bellow for a discussion of the hack I did to avoid this. 2. Print out the patches I printed the resulting tiff files with PhotoPrint. I believe it uses Gutenprint directly to drive the printer and is the only solution I know right now that can actually apply the ICC profile when printing later. The important thing here is to set the Gutenprint setting "Color Correction" to "Uncorrected", and then any of the image settings for the setup being used (type of paper, resolution, dithering, etc). 3. Read back the patches $chartread Munki will need to first be set to the self calibrate position, then to the profiling position and then run through each of the patch lines in turn while pressing its button. chartread asks for each of the lines and will ask for them again if there is any error. The interface needs to expose this. The last version allows you to reread a patch line at will. I wonder if it would be possible to have some kind of idea of how good the reads were and advise the user to reread one of the lines if it is found to not be too good. 4. Generate the profile $ colprof -v -D"" -qm -S -cmt -dpp This runs by itself without problems. The specific flags are arguable of course. I'm curious as to how changing -q (quality) to high or ultra changes the profile. Some considerations: - Some decent automatic naming would be nice - Selecting the source profile would be nice too (defaulting to sRGB) and possibly allowing the user to later generate the same profile with another profile (e.g. AdobeRGB) as source might be useful. - All the colprof settings can be changed without running the process from the beginning again. I wonder if g-c-m should have the notion of "Profiling runs" from which several actual profiles can be created. This would solve the sRGB/AdobeRGB selection as well. - Colprof outputs a final result with the mean and maximum error of the profile. It would be great to give this result to the user in plain English. Telling him the profile is "Poor/Fair/Good/Excellent" or even a result out of 100. The generated profile works in PhotoPrint. I assume it would also work to transform an image before sending it to the general CUPS pipeline. In theory the generated profile is only valid for the specific set of settings used for the printer. In practice using the same profile on even a different but similar paper is probably better than none at all. And using it at a different resolution on the same paper may very well be decent as well. I have no idea. > In particular, we need to support printing to 6x4 inch cards, A4 and > letter paper. I would love to integrate this better with CUPS (using > the GTK print dialog for instance) than what we can do on the command > line. We'll also need scans of the patches sheets that we send out, so > we can show the user _how_ to scan in the patches. We'll also probably > need a timer for "waiting for the ink to dry" and that sort of thing. My only other comment about the process is that using the Munki with default size patches is an incredible waste of paper and ink. In the argyll mailing list someone pointed out some user's hack on dpreview so I built one myself: http://pedrocr.net/MunkiHelper.jpg I'm not in any way suggesting that users should be expected to build one of these but I would like to be able to configure g-c-m to have not only the configuration for the normal Color Munki but also this hack. The only difference is to change the -iCM flag to printtarg to the -ii1, making the patches much smaller (by printing a sheet as if it was for another instrument). I know Pascal disagrees though. I share the sentiment of wanting to make this as simple to the user as possible. However my experience with this is that if we don't allow the user to fiddle with some of the advanced settings, whenever he hits a speed bump the only option is to fall back on argyll command line tools and totally bypass g-c-m. That doesn't seem like much of a solution either. My suggestion would be to have a set of default settings for each of the supported instruments that work in a straightforward way and then an "Advanced..." button to go and customize the settings. Cheers, Pedro From hughsient at gmail.com Thu Feb 18 09:28:41 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 18 Feb 2010 09:28:41 +0000 Subject: gnome-color-management test day Message-ID: <15e53e181002180128p9c9e977g8619a1518f86afd7@mail.gmail.com> Guys, We've got a GNOME Color Management test day happening today: https://fedoraproject.org/wiki/Test_Day:2010-02-18_Color_management It's very Fedora-centric, but I'm guessing as most of the testing and bugs will be common between distros, I guess it makes you more than welcome to join in. I'll be in the #fedora-test-day channel (on freenode) all day, answering questions and fixing bugs. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 18 17:57:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 18 Feb 2010 18:57:20 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> Message-ID: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: >> In a few days time, my nice lovely ColorMunki should be delivered. >> Before it is, I figured I should get up to speed on how to profile >> printers, so we know what UI to add to GCM, and so I can get up to >> speed quickly. >> >> So. Does anybody have any hints, tips or suggestions on how to >> calibrate a printer. Device specific options (e.g. "The ColorMunki >> works really well with -f234 -g567") are more than welcome, as we >> already know the colorimeter device type. > > Here is my experience with the Munki from my notes. I've used it > successfully to both profile a Dell U2410 LCD screen and an Epson > R2880. The LCD profiling should work already but I ended up using the > tools directly because g-c-m was failing to interact correctly with > the argyll tools when they asked to change the position of the device. > I think this has been fixed but haven't checked. I didn't have any such issues, so I guess this has been fixed for a while. > Anyway for the printing profiling my steps were: > > 1 - Generate a set of color patches > > $argyll-targen -f 900 -v -d2 -c -A.8 The -c option is very advanced, and requires a lot of logic in GCM in determining what the best previous profile actually was... Or it requires the user to select their best previous profile, and if they select the wrong profile (or GCM automatically selects the wrong profile) it all goes horribly wrong... So in the short run using preconditioning (-c) probably will do more harm than good... This could very well be reconsidered when GCM matures. The 900 patch count is probably way too high for default, since we don't want to waste 4 sheets of expensive paper _by default_. Especially since some packages of expensive paper come in per 10 sheets packages. We'd be wasting 40% :) Please remember the ColorMunki vendor software only uses 90 or so patches by default, so having 210/190 (1x A4/Letter) is a huge improvement... Thus far I've had excellent results using only 210 patches with no preconditioning, and it only requires a single sheet of paper. So I'd highly recommend to use this as default. Anything that requires more than a single sheet of paper should probably go in high quality/advanced mode... Also I'd recon we should not really talk about patch counts, but the amount of paper... For for A4 we would use 210/420/630/840/1050 patches, or for Letter 190/380/470/660? > To then actually generate the files to print: > > $ printtarg -t -v -iCM -pLetter printtarg has a -h option, which will generate smaller patches for the ColorMunki, which fits 210 patches onto A4 instead of 90 or so... This option basically shrinks the rows to a third size, so the ColorMunki is exactly as wide as 3 rows with the aperture exactly over the middle row. > 2. Print out the patches > > I printed the resulting tiff files with PhotoPrint. I believe it uses > Gutenprint directly to drive the printer and is the only solution I > know right now that can actually apply the ICC profile when printing > later. The important thing here is to set the Gutenprint setting > "Color Correction" to "Uncorrected", and then any of the image > settings for the setup being used (type of paper, resolution, > dithering, etc). Not everybody uses a gutenprint supported printer... :) It's basically possible to profile any application with any printer driver, as long as the app nor the printer driver do any dynamic transforms... Your case is very optimal... HPIJS for example does not have an uncorrected mode, but the output is static, so it can be profiled. I apply my printer profile in F-Spot, so I also used F-Spot to print my target images... In theory this should not be very relevant. > 3. Read back the patches > > $chartread > > Munki will need to first be set to the self calibrate position, then > to the profiling position and then run through each of the patch lines > in turn while pressing its button. chartread asks for each of the > lines and will ask for them again if there is any error. The interface > needs to expose this. The last version allows you to reread a patch > line at will. I wonder if it would be possible to have some kind of > idea of how good the reads were and advise the user to reread one of > the lines if it is found to not be too good. I don't think argyll does this yet... But it would be cool indeed... > 4. Generate the profile > > $ colprof -v -D"" -qm -S > -cmt -dpp Using -qm for 210 is an excellent default, but when we go into advanced mode with > 500 patches, we should probably use -qh. I've never used the -S -cmt -dpp options, so I highly doubt they are required... We shouldn't pass random arguments unless strongly indicated that we should. Otherwise we should trust Argyll's defaults... > This runs by itself without problems. The specific flags are arguable > of course. I'm curious as to how changing -q (quality) to high or > ultra changes the profile. Some considerations: Graeme highly discourages the ultra mode, in his words: ultra mode exists to prove that nothing above high is required. > - Some decent automatic naming would be nice > - Selecting the source profile would be nice too (defaulting to sRGB) > and possibly allowing the user to later generate the same profile with > another profile (e.g. AdobeRGB) as source might be useful. Huh? printer profiles usually use LAB as Profile Connection Space, this has nothing to do with sRGB/AdobeRGB. The pipeline: Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> printer native RGB/CMYK -> hpijs/gutenprint > - All the colprof settings can be changed without running the process > from the beginning again. I wonder if g-c-m should have the notion of > "Profiling runs" from which several actual profiles can be created. > This would solve the sRGB/AdobeRGB selection as well. I'd probably be against this too (at least for the short run). This will complicate the user interface (and GCM's codebase), and probably won't be used much by most people, so this is not in line with GNOME's goals. In the long run we could re-evaluate this... > - Colprof outputs a final result with the mean and maximum error of > the profile. It would be great to give this result to the user in > plain English. Telling him the profile is "Poor/Fair/Good/Excellent" > or even a result out of 100. That would be nice... I'd stick to Poor/Fair/Good/Excellent, everybody understands that. Though we need to be very careful about how we determine what is what. > The generated profile works in PhotoPrint. I assume it would also work > to transform an image before sending it to the general CUPS pipeline. > In theory the generated profile is only valid for the specific set of > settings used for the printer. In practice using the same profile on > even a different but similar paper is probably better than none at > all. And using it at a different resolution on the same paper may very > well be decent as well. I have no idea. > >> In particular, we need to support printing to 6x4 inch cards, A4 and >> letter paper. I would love to integrate this better with CUPS (using >> the GTK print dialog for instance) than what we can do on the command >> line. We'll also need scans of the patches sheets that we send out, so >> we can show the user _how_ to scan in the patches. We'll also probably >> need a timer for "waiting for the ink to dry" and that sort of thing. >From most sources I gather a minimum od 15 minutes of drying-time should be enough for most cases. > My only other comment about the process is that using the Munki with > default size patches is an incredible waste of paper and ink. In the > argyll mailing list someone pointed out some user's hack on dpreview > so I built one myself: > > http://pedrocr.net/MunkiHelper.jpg Are you actually aware of the -h option for printtarg? Graeme semi-solved this issue long ago... My current workflow is like this # argyll-targen -v -d 2 -g 20 -f 210 test # printtarg -v -i CM -h -t 300 -p A4 test # chartread -v test # colprof -v -A "bla" -M "bla" -D "bla" -C "bla" -a l -q m test Regards, Pascal de Bruijn From knizek.confy at volny.cz Thu Feb 18 18:46:34 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Thu, 18 Feb 2010 19:46:34 +0100 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> Message-ID: <1266518794.18345.36.camel@athlon> Pascal de Bruijn p??e v ?t 18. 02. 2010 v 18:57 +0100: > On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > > - Selecting the source profile would be nice too (defaulting to sRGB) > > and possibly allowing the user to later generate the same profile with > > another profile (e.g. AdobeRGB) as source might be useful. > > Huh? printer profiles usually use LAB as Profile Connection Space, > this has nothing to do with sRGB/AdobeRGB. > > The pipeline: > Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> > printer native RGB/CMYK -> hpijs/gutenprint It looks like Pedro was referring to -S option of colprof: Argyllcms docs quote [1]: -- Where the resulting profile will be used conventionally (ie. using collink -s, or cctiff or most other "dumb" CMMs) it is important to specify that gamut mapping should be computed for the output (B2A) perceptual and saturation tables. This is done by specifying a device profile as the parameter to the colprof -S flag. When you intend to create a "general use" profile, it can be a good technique to specify the source gamut as the opposite type of profile to that being created, i.e. if a printer profile is being created, specify a display profile (e.g. sRGB) as the source gamut. If a display profile is being created, then specify a printer profile as the source (e.g. SWOP). -- Argyllcms docs quote [2]: ... [Note that Shaper/Matrix profiles are always Colorimetric intent, since there is only a single transformation, and it does not have the necessary flexibility to accommodate gamut mapping.] ... So to construct the perceptual and saturation intent mapping tables, a source profile or source gamut needs to be specified, so that a gamut mapping can be constructed. -- [2] http://www.argyllcms.com/doc/Scenarios.html#PP5 [1] http://www.argyllcms.com/doc/iccgamutmapping.html I do not have much experience on this topic... regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Fri Feb 19 10:41:19 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 10:41:19 +0000 Subject: Help update Message-ID: <1266576079.2381.5.camel@localhost> Richard Attached is my first attempt to help. Sorry it has taken me so long but I had a lot of reading to do about Gnome documentation. I have only altered the Introduction and Usage sections. I will set about the other sections if this is acceptable. If anyone wants to tell me where I am going wrong then please do. I admit this little effort has made me realise just what Richard is doing! There is more to gcm than I expected. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Correct-help-Intro-and-Usage.patch Type: text/x-patch Size: 3064 bytes Desc: not available URL: From hughsient at gmail.com Fri Feb 19 11:02:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 11:02:43 +0000 Subject: Help update In-Reply-To: <1266576079.2381.5.camel@localhost> References: <1266576079.2381.5.camel@localhost> Message-ID: <15e53e181002190302r1ffa130ay22236854ce8574d3@mail.gmail.com> On 19 February 2010 10:41, Paul Finnigan wrote: > Attached is my first attempt to help. Sorry it has taken me so long but > I had a lot of reading to do about Gnome documentation. Sure, it takes a fair bit to get up to speed. > I have only altered the Introduction and Usage sections. I will set > about the other sections if this is acceptable. I've committed your patch, thanks. One thing to note (any maybe repair in your next patch :-) is the trailing whitespace issue. git doesn't like trailing whitespace (tabs and spaces at the end of the line) and highlights them in red. Could you please make sure future patches don't add more trailing whitespace please? Thanks. > If anyone wants to tell me where I am going wrong then please do. I > admit this little effort has made me realise just what Richard is doing! Heh. Thanks. > There is more to gcm than I expected. Sure, and it's getting bigger every day. To do the printer profiling properly I'm having to deal with print dialogs and rendering to random cairo surfaces. Both things that were not in the original scope for GCM... Anyway, keep up the good work. Thanks. Richard. From paul at fincc.com Fri Feb 19 12:48:30 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 12:48:30 +0000 Subject: Selecting Device Profiles Message-ID: <1266583710.2381.14.camel@localhost> Hi I was just looking at improving the preferences help page and I came across a small UI problem someone else may like to look at. If the device profile is not loaded you can select "Other profile..." this takes you to the profile install routine, via a Gnome file select window. That is good. But once the profile is installed I have to go back to the Color Profile selector and select it. I think what should happen is: 1. If the profile is good for the device it should be selected. 2. If the profile is not good for the device then a message should be issued and the device profile is unaltered. What should never happen is that the "Other profile" selection remains against the device. Another point is that for a new device the profile should be "None" rather than blank. This will keep it consistent with selecting None from the profile list. What does everyone else think? -- Paul Finnigan From hughsient at gmail.com Fri Feb 19 13:05:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 13:05:10 +0000 Subject: Selecting Device Profiles In-Reply-To: <1266583710.2381.14.camel@localhost> References: <1266583710.2381.14.camel@localhost> Message-ID: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> On 19 February 2010 12:48, Paul Finnigan wrote: > If the device profile is not loaded you can select "Other profile..." > this takes you to the profile install routine, via a Gnome file select > window. That is good. But once the profile is installed I have to go > back to the Color Profile selector and select it. That's just a bug: commit 5c4731bce32ce55467449d793b6a508b48b09eda Author: Richard Hughes Date: Fri Feb 19 13:03:14 2010 +0000 trivial: Set the profile we chose as 'Other' as the current device default > I think what should happen is: > > 1. If the profile is good for the device it should be selected. Sure, agreed. > 2. If the profile is not good for the device then a message should be > issued and the device profile is unaltered. We need to add that. > What should never happen is that the "Other profile" selection remains > against the device. What happens if the device chosen is unsuitable? Go back to the previous profile, or 'None'? Richard. From paul at fincc.com Fri Feb 19 13:15:29 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 13:15:29 +0000 Subject: Selecting Device Profiles In-Reply-To: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> References: <1266583710.2381.14.camel@localhost> <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> Message-ID: <1266585329.2381.16.camel@localhost> Richard On Fri, 2010-02-19 at 13:05 +0000, Richard Hughes wrote: > What happens if the device chosen is unsuitable? Go back to the > previous profile, or 'None'? > > Richard. I would suggest the previous profile. The warning can then say that the profile is unsuitable and the setting has not been altered. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Fri Feb 19 23:03:26 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 00:03:26 +0100 Subject: gcm-git not building (as package) Message-ID: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Hi, There are some trivial problems with gcm-git: cc1: warnings being treated as errors gcm-calibrate.c: In function 'gcm_calibrate_device': gcm-calibrate.c:654: error: unused variable 'dialog' make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Sat Feb 20 00:14:20 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:14:20 +0300 Subject: Small thumbnails of targets In-Reply-To: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> Message-ID: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> On 2/10/10, Lars Tore Gustavsen wrote: >> This would be a great way to help out gnome-color-manager if you are >> not comfortable with coding. The list of target types I need as >> thumbnails are: >> >> CMP_Digital_Target-3 >> CMP_DT_003 >> ColorChecker >> ColorCheckerDC >> ColorCheckerSG >> Hutchcolor >> i1_RGB_Scan_1.4 Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) Alexandre From alexandre.prokoudine at gmail.com Sat Feb 20 00:10:43 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:10:43 +0300 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <733f2c731002191610q5bea9bd2l347287afcf42abc9@mail.gmail.com> On 2/17/10, Richard Hughes wrote: > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Just in case, make sure you've seen GPLin (http://bit.ly/aTmim3). Maybe it has some useful code for you. Alexandre From pedro at pedrocr.net Fri Feb 19 21:01:20 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 19 Feb 2010 13:01:20 -0800 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> Message-ID: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> (I'm CC'ing this to the list to keep the discussion there, hope it's ok) On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > Some applications (even commercial ones) don't support LUT display > profiles properly. > > Argyll can generate Matrix+LUT profiles, but then you have the problem > that one app uses the matrix and the other the LUT, this can give odd > inconsistencies... So it's not recommended for defaults... Makes sense. Do you know if I'll be ok with a LUT using GIMP/f-spot/ufraw? I should probably try g-c-m again to see what profile it comes up with. When I did the LUT one with 2000 patches the result seemed to have a fair amount of extra contrast that looked good. Don't know where that came from. > This is true, however, 210 is already a _big_ improvement over 90... Sure. Although I need to test it again as it was too little for me before. But here is Graeme Gill's opinion on number of needed patches (600-1000 for a "well-behaved" printer): http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,22 I guess this one is easy to expose to the user by asking him how many sheets to print. > Please also note, that you're passing all kinds of options with > unknown effects... I just passed the options recommended by argyll itself (the mailing list and the docs). > Please try again with exactly the options I gave... > > Also make sure you have an up to date version of Argyll (1.1.0-final)... Yes, this I did use in the last run but not the previous ones, so that could be the problem with 210 patches. > -q has little do to with actual quality with LUT profiles, it has to > do with detailedness of the generated profiles... Generating a high > detail profiles with low patches seems silly at best. Makes sense, thanks. >> Again the scenarios and the mailing list tell us to use a source >> profile. Milan had an explanation for it. > > Do you have a reference for that? Sure. Here are the docs: http://www.argyllcms.com/doc/Scenarios.html#PP5 And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try different profiles there: http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 It could be that we can actually get away without -S for a decent default. We should probably start a thread in the argyll mailing list about what to use as sensible defaults for profiling printers (and monitors/scanners/cameras too maybe). > We aren't catering to the masses... But even advanced hobby > photographers and professional photographers see color management as a > necessary evil, and most don't want to bother with patch counts and > all kinds of settings, they just want a reasonable match by clicking > on "Next" a couple of times... Yes, I agree completely. My point wasn't that the GUI shouldn't start as a straight-through "get a decent enough profile and be done with it". I was just arguing that the user shouldn't be dumped into learning all these argyll command line options every time he wants to do something even moderately advanced. > Again, the big question would be how often you _really need_ the > advanced settings... Liking to fiddle with them and needing them are > two different things... > > Trying to control to much was a mistake I made in the past as well, > sticking to Argyll's defaults has generally improved my results. I totally agree there. Only settings that are actually needed should be exposed. I don't yet know what those are though considering all the advice to fiddle with different settings I got from the argyll list. Maybe most of that advice can actually be the default and not need changing. >> I think the underlying assumption behind telling users who want >> advanced stuff to go to the argyll tools is that someone that wants >> advanced calibration/color in Linux is also an advanced Linux user. >> Whereas in reality it would be good to be able to support advanced >> photographers/artists that are also non-geek computer users. It's an >> uphill battle right now with GIMP not supporting 16-bit images, f-spot >> not very complete and raw converters still not particularly good. >> We're advancing in all three fronts though and g-c-m is a much needed >> complement. > > Patience is key here... No doubt. I wouldn't be using Linux to do photography work if I wasn't happy to put up with and work around the shortcomings. >> why -g? > > Adds greyscale patches. So why deviate from the argyll standard there? This one didn't get mentioned in my thread. Is it to improve the tone curve for B&W printing? >>> # printtarg -v -i CM -h -t 300 -p A4 test >> >> Does -t 300 help? I was getting some non-sharp edges on my patches >> maybe it was because of this. > > This doesn't particularly matter much, you're not measuring the edges. I wasn't too worried about it although I guessed it could mess up the patch detection and maybe sometimes interfere with a reading, especially when using the smaller patches. Cheers, Pedro From knizek.confy at volny.cz Sat Feb 20 08:15:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 09:15:14 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266653714.2961.28.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). > I completely agree to get some hints from argyllcms mailing list users. Also, sooner or later, GCM would need to solve the problem of a general photographer (I do not want to know how things work but still want my pictures nicely printed). A good example is here: http://photo.net/digital-darkroom-forum/00ViCO William Palmer wonders what to do to solve the problem that printed images look fine on direct sun-light, but when hanged on the wall inside, they look "dark". At the end, Andrew Rodney mentions some "advanced profiling solutions", which can compensate for different viewing conditions, but William does not get the point (which is understandable). That is what ArgyllCMS takes care by -c and -d parameters for colprof: -- Since appearance space is used in the gamut mapping (just as it is in collink), the viewing conditions for the source and destination colorspaces should really be specified. The source colorspace is the profile specified with the -s or -S flag, and the destination is the profile being created. The -c and -d options allow specification of their respective, associated viewing conditions. The viewing condition information is used to map the profile PCS (Profile Connection Space, which us either XYZ or L*a*b*) color into appearance space (CIECAM02), which is a better colorspace to do gamut mapping in. The viewing conditions allow the conversion into appearance space to take account of how color will be seen under particular viewing conditions. -- I do also not think that exposing the colprof parameters to a user is a good idea. Nonetheless, how about asking the user - "Will your print be viewed in a dim light environmnet?" "Will it hang in a room well lit by daylight?") And similarly for "-g" paramater of targen: "Do you print black and white photographs and want a higher emphasise on grey neutrality then on colour fidelity?" Using such questions, the user could be navigated to get a good profile for his own use. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 20 08:44:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 20 Feb 2010 08:44:50 +0000 Subject: gcm-git not building (as package) In-Reply-To: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> References: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Message-ID: <15e53e181002200044j180d4e97kf865fb3054fd2092@mail.gmail.com> On 19 February 2010 23:03, Pascal de Bruijn wrote: > cc1: warnings being treated as errors > gcm-calibrate.c: In function 'gcm_calibrate_device': > gcm-calibrate.c:654: error: unused variable 'dialog' > make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 commit 8c711eb8ba43a8bad65d7f45899859b3ed7fdc81 Author: Richard Hughes Date: Sat Feb 20 08:43:38 2010 +0000 trivial: fix compile from git master when compiling without PackageKit Richard. From pmjdebruijn at pcode.nl Sat Feb 20 11:45:23 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 12:45:23 +0100 Subject: Small thumbnails of targets In-Reply-To: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> Message-ID: <4c2c37f91002200345l1a221c69tb8612a35b5c0ff26@mail.gmail.com> On Sat, Feb 20, 2010 at 1:14 AM, Alexandre Prokoudine wrote: > On 2/10/10, Lars Tore Gustavsen wrote: > >>> This would be a great way to help out gnome-color-manager if you are >>> not comfortable with coding. The list of target types I need as >>> thumbnails are: >>> >>> CMP_Digital_Target-3 >>> CMP_DT_003 >>> ColorChecker >>> ColorCheckerDC >>> ColorCheckerSG >>> Hutchcolor >>> i1_RGB_Scan_1.4 > > Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) IT8 = IT8, doesn't really matter which vendor... At least it shouldn't it think... Regards, Pascal de Bruijn From knizek.confy at volny.cz Sat Feb 20 16:58:55 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 17:58:55 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266685135.5298.5.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > >> Again the scenarios and the mailing list tell us to use a source > >> profile. Milan had an explanation for it. > > > > Do you have a reference for that? > > Sure. Here are the docs: > > http://www.argyllcms.com/doc/Scenarios.html#PP5 > > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). How about using the RGB working colourspace, which is set in GCM defaults tab, for -S colour space? We can assume that majority of the images would be in that space. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Mon Feb 22 12:16:11 2010 From: paul at fincc.com (Paul Finnigan) Date: Mon, 22 Feb 2010 12:16:11 +0000 Subject: Updated Help Text Message-ID: <1266840971.2539.8.camel@localhost> Richard I have amended the text around the preferences and advanced preferences sections of the help file. I have included (but not altered) the text you said should go in about gamma. The text is not perfect but I think that it is better than what was there. I cannot alter the section on Calibration as I do not have the hardware to check out the interface yet (gcm is the first software that made me want to buy it!). If anyone has anything to add to the help files but does not want to update them then just let me know. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-Help-Preferences-Text.patch Type: text/x-patch Size: 7012 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 22 12:31:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:31:50 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220431j4a0f4c37lce0c558756c98d7e@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > The text is not perfect but I think that it is better than what was > there. Agreed, thanks. I've applied it with minor changes. You also need to set your email address so git formatted patches display the right email (and so lazy me can just use git am). To do this, just set export GIT_AUTHOR_EMAIL=dave at dave.com in ~/.bash_profile for future patches. Thanks! Richard. From hughsient at gmail.com Mon Feb 22 12:38:59 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:38:59 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > If anyone has anything to add to the help files but does not want to > update them then just let me know. In particular, we need lots more FAQ entries filled out: * What colorimeter devices are supported * What target types are supported? * Where do I purchase targets from? * How do I get a profile from my display vendor * How do I get a reference image using a digital camera? * ...lots of other details about color management.... If you're scared by docbook and git, then just submit some prose to the mailing list, and one of the other contributors can format it up and submit a patch on your behalf. Thanks, Richard. From alexandre.prokoudine at gmail.com Mon Feb 22 13:43:41 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 22 Feb 2010 16:43:41 +0300 Subject: Updated Help Text In-Reply-To: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> References: <1266840971.2539.8.camel@localhost> <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> Message-ID: <733f2c731002220543x3c160251v4a546c11e44a7210@mail.gmail.com> On 2/22/10, Richard Hughes wrote: > In particular, we need lots more FAQ entries filled out: > > * What colorimeter devices are supported Committed > * What target types are supported? Committed > * Where do I purchase targets from? Committed Alexandre From hughsient at gmail.com Mon Feb 22 14:46:19 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 14:46:19 +0000 Subject: ColorMunki works Message-ID: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> My ColorMunki arrived this morning, and I've just committed quite a few patches to make it work calibrating the screen. There are still quite a few rough edges we need to fix (hardcode) but it basically works. Now I'm going to move onto adding initial printing support, although this might take a couple of weeks. Richard. From pmjdebruijn at pcode.nl Mon Feb 22 17:22:37 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 22 Feb 2010 18:22:37 +0100 Subject: ColorMunki works In-Reply-To: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> References: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> Message-ID: <4c2c37f91002220922m77984a56o1c441985dbc9d099@mail.gmail.com> On Mon, Feb 22, 2010 at 3:46 PM, Richard Hughes wrote: > My ColorMunki arrived this morning, and I've just committed quite a > few patches to make it work calibrating the screen. There are still > quite a few rough edges we need to fix (hardcode) but it basically > works. Now I'm going to move onto adding initial printing support, > although this might take a couple of weeks. Indeed it does, there are some cosmetic issues though: https://bugzilla.gnome.org/show_bug.cgi?id=605856 I'm looking forward to the printer stuff, especially the CUPS integration, it would severely kick ass if there would be an extra CUPS Color Management tab, on which output color profiles could be specified. Regards, Pascal de Bruijn From knizek.confy at volny.cz Mon Feb 22 20:51:30 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 21:51:30 +0100 Subject: Make default - what is it supposed to do? Message-ID: <1266871890.982.23.camel@athlon> Hello, what is the expected behaviour of "Make Default" button in gcm-prefs? The notification message reads "Save these profiles for all users", but after pressing it I can see the verbose output reading: - running: pkexec /usr/sbin/gcm-install-system-wide --id xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" Content type was incorrect: application/octet-stream It tries to install the monitor profile, however, I also have a webcam profile set. And as far as I can tell, nothing happens. The profile is not copied to /usr/share/color/... or /usr/local/share/color/... locations, I cannot find anything useful in /etc/... or /var/lib/... and starting a session of a different user does not show any profile set in gcm-prefs. Is this is a bug or not-yet-implemented thing? Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 22 21:11:25 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 23 Feb 2010 00:11:25 +0300 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> On 2/22/10, Milan Kn??ek wrote: > Hello, > > what is the expected behaviour of "Make Default" button in gcm-prefs? http://www.libregraphicsworld.org/articles.php?article_id=11 "To make your preferences available to all users of a system you can use the Make Default button in the bottom of the dialog. What it will do is ask for superuser password and copy all the active display profiles to a system-wide directory (/var/lib/color) where the new filename matches the device-id. So when a new user logs in, if there is no device-profiles entry for the device, the system-wide profile is used." Alexandre From knizek.confy at volny.cz Mon Feb 22 22:07:42 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 23:07:42 +0100 Subject: Make default - what is it supposed to do? In-Reply-To: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> References: <1266871890.982.23.camel@athlon> <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> Message-ID: <1266876462.20402.8.camel@athlon> Alexandre Prokoudine p??e v ?t 23. 02. 2010 v 00:11 +0300: > On 2/22/10, Milan Kn??ek wrote: > > Hello, > > > > what is the expected behaviour of "Make Default" button in gcm-prefs? > > http://www.libregraphicsworld.org/articles.php?article_id=11 > > "To make your preferences available to all users of a system you can > use the Make Default button in the bottom of the dialog. What it will > do is ask for superuser password and copy all the active display > profiles to a system-wide directory (/var/lib/color) where the new > filename matches the device-id. So when a new user logs in, if there > is no device-profiles entry for the device, the system-wide profile is > used." > Then it seems to be a bug - on two computers (same system though - Ubuntu 9.10 amd64) the directory /var/lib/color exists, but it remains empty. Authorisation seems to be okay, I also tried to run with sudo and as root in console - no success, just the error message: Content type was incorrect: application/octet-stream regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Mon Feb 22 23:17:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 23:17:13 +0000 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <15e53e181002221517t65dc049aqccb1f4580470e478@mail.gmail.com> On 22 February 2010 20:51, Milan Kn??ek wrote: > ?- running: pkexec /usr/sbin/gcm-install-system-wide --id > xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" > Content type was incorrect: application/octet-stream Looks like your version of shared-mime-info is too old. We can't do the .icc/.icm fallback in this case as gcm-install-system-wide is running as root as we have to be careful of maliciously created profiles. > Is this is a bug or not-yet-implemented thing? The former :-) Richard. From hughsient at gmail.com Tue Feb 23 14:21:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 14:21:39 +0000 Subject: Blog post about GCM Message-ID: <15e53e181002230621t76746c6elb9c4dcc2344b59c@mail.gmail.com> I've made a blog post about GCM that some of you might find interesting: http://blogs.gnome.org/hughsie/2010/02/23/gnome-color-manager-and-printer-profiling/ Good job on the documentation file btw, it's coming along nicely now. Richard. From hughsient at gmail.com Tue Feb 23 15:50:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 15:50:21 +0000 Subject: Strategic direction Message-ID: <15e53e181002230750r1b8414a2l2503a7079cfd4f2d@mail.gmail.com> Big ideas I think we need to work towards: * Assigning more than one profile to a device[1] (and having one default profile per device) * Having virtual devices that we can't connect, for instance "Bob's Photo Processing Shop" Any one got any more ideas? Richard. [1] The DBus API already supports this, although it only ever returns one profile. From pmjdebruijn at pcode.nl Tue Feb 23 17:44:13 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 18:44:13 +0100 Subject: New print profiling functionality Message-ID: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Hi, I just tried the brand spanking new print profiling functionality... And of course there's something to bitch about... * It only generated 45 patches, while on A4 I can fit 210 ColorMunki patches in double density mode (-h). * Some patches got clipped (because of margins), because the generated image isn't centered (or it is getting stretched for no reason, since the generated image doesn't include margins). * The generated image is pretty low resolution, the text looks like crap, consider (printtarg -T 200 or 300)? * GCM should not report "reading the patches" during self-calibration, we need a seperate dialog for this! Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 23 17:51:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 17:51:53 +0000 Subject: New print profiling functionality In-Reply-To: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Message-ID: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> On 23 February 2010 17:44, Pascal de Bruijn wrote: > I just tried the brand spanking new print profiling functionality... > And of course there's something to bitch about... Heh, good. :-) > * It only generated 45 patches, while on A4 I can fit 210 ColorMunki > patches in double density mode (-h). Right, this is something I need help with. How many patches do we use for quick, normal and slow profiling? I'm already using -h for ColorMunki. > * Some patches got clipped (because of margins), because the generated > image isn't centered (or it is getting stretched for no reason, since > the generated image doesn't include margins). Ahh, I'm just blitting it to the cairo surface, without preserving aspect. I guess we need to do that. I'm using gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > * The generated image is pretty low resolution, the text looks like > crap, consider (printtarg -T 200 or 300)? Hmm, it should already be using 300DPI thanks to the -t300 option. > * GCM should not report "reading the patches" during self-calibration, > we need a seperate dialog for this! Sure, I can't get my ColorMunki to self calibrate using chartread (see the Argyll m/l) so I've not tested past this point. Richard. From hughsient at gmail.com Tue Feb 23 20:20:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 20:20:13 +0000 Subject: New print profiling functionality In-Reply-To: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> Message-ID: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> On 23 February 2010 17:51, Richard Hughes wrote: > Ahh, I'm just blitting it to the cairo surface, without preserving > aspect. I guess we need to do that. I'm using > gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. I've done the scaling in cairo now; see below. >> * The generated image is pretty low resolution, the text looks like >> crap, consider (printtarg -T 200 or 300)? > > Hmm, it should already be using 300DPI thanks to the -t300 option. I've just pushed a commit to do the scaling in cairo, rather than GDK, which makes it look much better. Richard. From pmjdebruijn at pcode.nl Tue Feb 23 22:22:30 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:22:30 +0100 Subject: New print profiling functionality In-Reply-To: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> Message-ID: <4c2c37f91002231422g6836f6e5s1a7ff1a8db4e8c7f@mail.gmail.com> On Tue, Feb 23, 2010 at 9:20 PM, Richard Hughes wrote: > On 23 February 2010 17:51, Richard Hughes wrote: >> Ahh, I'm just blitting it to the cairo surface, without preserving >> aspect. I guess we need to do that. I'm using >> gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > > I've done the scaling in cairo now; see below. > >>> * The generated image is pretty low resolution, the text looks like >>> crap, consider (printtarg -T 200 or 300)? >> >> Hmm, it should already be using 300DPI thanks to the -t300 option. > > I've just pushed a commit to do the scaling in cairo, rather than GDK, > which makes it look much better. Actually, since you're using cairo, which is very vector-aware, right? Wouldn't it make sense to use the EPS output (printtarg -e). Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 23 22:28:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:28:50 +0100 Subject: Printshop calibration/profiling Message-ID: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Hi, Another thing I noticed, is the very cool dialog which also allows you to profile printshops, however I can only get to this dialog whenever I have a printer in GCM, and the spectrophotometer connected, even though I only want to generate a chart to send to my printshop. This is not a huge problem, more of a nuisance... Maybe it's a thought to create a "Printshop" virtual device? Honestly I'm not sure that's a much better solution, since sooner or later we'll end up with 100 by default created virtual devices for all kinds of corner cases... This message is mainly intended to get a discussion going... Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Tue Feb 23 22:32:52 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Wed, 24 Feb 2010 01:32:52 +0300 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <733f2c731002231432j6144ec13h1ffd278e038064c0@mail.gmail.com> On 2/24/10, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... This is not a huge problem when you have a printer. Well, I don't have one :) Alexandre From hughsient at gmail.com Tue Feb 23 22:33:36 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 22:33:36 +0000 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <15e53e181002231433j2138420bg216e2efe3d84ad3c@mail.gmail.com> On 23 February 2010 22:28, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... Sure, agreed. > Maybe it's a thought to create a "Printshop" virtual device? Honestly > I'm not sure that's a much better solution, since sooner or later > we'll end up with 100 by default created virtual devices for all kinds > of corner cases... I do think we need virtual devices. It's bad usability, as you have to enter everything manually, but a useful thing for power users. Richard. From pmjdebruijn at pcode.nl Wed Feb 24 22:06:08 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 24 Feb 2010 23:06:08 +0100 Subject: Double Density Mode for ColorMunki Message-ID: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Hi, To my dismay I noticed you've dropped the double density mode for the ColorMunki. What would be the problem with this? Maybe I can help? Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 08:43:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 08:43:34 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Message-ID: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> On 24 February 2010 22:06, Pascal de Bruijn wrote: > To my dismay I noticed you've dropped the double density mode for the > ColorMunki. What would be the problem with this? Maybe I can help? I just couldn't get double density to work correctly. Maybe I'm clumsy or something, but the single density was much easier to scan. Perhaps we can just have it as a simple dialog choice? ________________________________ Target Choice ________________________________ Your calibration device can use much smaller sized squares to save on paper and ink, although it will be harder to use the device. Enable double density mode? [Help] [No] [Yes] ________________________________ Richard. From pmjdebruijn at pcode.nl Thu Feb 25 10:58:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 25 Feb 2010 11:58:38 +0100 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> Message-ID: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> On Thu, Feb 25, 2010 at 9:43 AM, Richard Hughes wrote: > On 24 February 2010 22:06, Pascal de Bruijn wrote: >> To my dismay I noticed you've dropped the double density mode for the >> ColorMunki. What would be the problem with this? Maybe I can help? > > I just couldn't get double density to work correctly. Maybe I'm clumsy > or something, but the single density was much easier to scan. I'm guessing you didn't print it at proper scale... In double density mode, three rows are exactly as wide as the ColorMunki, so the rows themselves can be used as a visual guide. And because the patches are smaller you need to scan a bit slower. > Perhaps we can just have it as a simple dialog choice? No that's silly... Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 11:36:33 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 11:36:33 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> Message-ID: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> On 25 February 2010 10:58, Pascal de Bruijn wrote: > I'm guessing you didn't print it at proper scale... Well, argyll formats it as a single page tiff file, so I'm pretty sure I did. I've attached a photo to show you the pages. > In double density mode, three rows are exactly as wide as the > ColorMunki, so the rows themselves can be used as a visual guide. And > because the patches are smaller you need to scan a bit slower. Right, maybe I'm just a bit clumsy. >> Perhaps we can just have it as a simple dialog choice? > > No that's silly... Agreed. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: double-density.jpg Type: image/jpeg Size: 23813 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 25 12:07:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 12:07:28 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> Message-ID: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> On 25 February 2010 11:36, Richard Hughes wrote: > Right, maybe I'm just a bit clumsy. I've found I can use the double density scan 99% correctly, if I rotate the page and "push" the colormunki away from me. If I try to scan from left to right then it only works 10% of the time. I'll do you deal. I'll re-instate the double density feature (with extra love) if you write a section in the help file on how to scan in a target, with tips. :-) Deal? Richard. From pedro at pedrocr.net Thu Feb 25 21:10:18 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 25 Feb 2010 13:10:18 -0800 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> Message-ID: <62e8012c1002251310t6c02124cnd3f62db919b2b5dd@mail.gmail.com> On Thu, Feb 25, 2010 at 4:07 AM, Richard Hughes wrote: > I'll do you deal. I'll re-instate the double density feature (with > extra love) if you write a section in the help file on how to scan in > a target, with tips. :-) If I write a section for the manual on how to build and use the simple guide rules to use the munki with EyeOne targets can we get that mode too? In my experience it makes scanning much simpler than even normal density patches freehand and the guide takes 5 minutes and only basic supplies to build. If someone was selling an after-market solution for this I assume no one would have a problem with it so I don't see why a home-made one isn't fine as well. It would at least be nice if the instrument definitions were setup in config files for each instrument so that even if you don't want to have this in mainline people could hack together their own config files and still take advantage of the g-c-m UI. Pedro From hughsient at gmail.com Mon Feb 1 11:05:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 1 Feb 2010 11:05:13 +0000 Subject: GNOME Color Manager 2.29.3 Message-ID: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> gnome-color-manager is a session program that makes it easy to manage, install and generate color profiles in the GNOME desktop. Version 2.29.3 ~~~~~~~~~~~~~~ Released: 2010-02-01 * Translations - Added Italian translation (Francesco Groccia) - Updated Danish translation (Joe Hansen) - Updated French translation (Claude Paroz) - Updated German translation (Mario Bl?ttermann) - Updated Norwegian bokm?l translation (Kjartan Maraas) - Updated Portuguese translation (Ant?nio Lima) - Updated Russian translation (Alexandre Prokoudine) - Updated Slovenian translation (Andrej ?nidar?i?) - Updated Swedish translation (Daniel Nylander) * New Features: - Enable the rendering intent and default colorspace UI elements (Richard Hughes) - Show whether the ICC profile has a VCGT tag in the UI (Richard Hughes) - Filter out non RGB and CMYK color space profiles from the combo-boxes using a heuristic (Richard Hughes) - Add a new DBus method GetProfileForWindow which can return a profile for a supplied XID (Richard Hughes) - Add some new text and tooltips to the prefs dialog (Richard Hughes) - Add per-user OSX ICC profiles at startup (Richard Hughes) - Add OSX and Windows ICC profiles if they exist from mounted volumes. Fixes #607390 (Richard Hughes) - Add a device profile entry of 'Other profile...' to be able to easily import a profile. Fixes #607389 (Richard Hughes) - Add a precision GConf variable to control the time a calibration takes. Fixes #605558 (Richard Hughes) - Screenscrape the Argyll output to better support other hardware devices. Fixes #605558 (Richard Hughes) - Do not show the 'Fine tuning' expander by default, and have configuration in GConf (Richard Hughes) * Bugfix: - Zero out GErrors after freeing. Fixes crash (Christian Hergert) - Add gnome-desktop path as fallback for pci.ids (Frederic Crozat) - Do not generate an error if a display profile does not have CLUT data (Richard Hughes) - Add gcm-fix-profile to load and then re-save existing profiles using lcms (Richard Hughes) - Fix compile when using an ld that defaults to --as-needed (Richard Hughes) - Do not allow the colorspace combobox to be zero sized. Fixes #606484 (Richard Hughes) - Make gcm-prefs a normal dialog rather than a modal dialog (Richard Hughes) - Only scan ICC locations with hfs partition types for OSX and msdos/NTFS types for Windows (Richard Hughes) - Make gcm-prefs startup a few hundred ms quicker by not loading the list of screens (Richard Hughes) - Cache gnome_rr_screen_new and take 0.7 seconds off the start time (Richard Hughes) - Don't resize the window on startup. Fixes #607391 (Richard Hughes) - Update the Free Software Foundation address (Richard Hughes) Richard. From pmjdebruijn at pcode.nl Mon Feb 1 18:29:31 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 1 Feb 2010 19:29:31 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> Message-ID: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > gnome-color-manager is a session program that makes it easy to manage, install > and generate color profiles in the GNOME desktop. > > Version 2.29.3 > ~~~~~~~~~~~~~~ > Released: 2010-02-01 As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's available on my gcm-release PPA: https://launchpad.net/~pmjdebruijn/+archive/gcm-release ArgyllCMS 1.1.0 is also available on my argyll-release PPA, to complement GNOME Color Manager: https://launchpad.net/~pmjdebruijn/+archive/argyll-release Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 5 12:55:32 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 13:55:32 +0100 Subject: Information re. display gamma Message-ID: <1265374532.31703.61.camel@athlon> Hello, while translating the gcm, I spotted the following: -- Gamma is adjusted to affect the color of the attached monitor. Traditionally Linux has used a gamma value of 1.0, but this makes monitors look washed out compared Windows XP or OS X. Apple traditionally used a value of 1.8 for a long time, but now use the same value as Microsoft. Microsoft has always used a value of 2.2. -- Where does the information that Linux has used a gamma of 1.0 come from? I would assume it is a wrong interpretation of technical data. Both Mac/Win tools prefer to tell the user the final viewing gamma (which is a combination of gamma adjustment in LUT of graphics card and of the monitor's native gamma). These tools expect that the monitor native gamma is 2.2 (which is close to sRGB). In the past, Mac monitors had native gama 1.8. Linux tools - like xgamma and gcm - instead tell the number, which is applied to LUT only. Note that the final viewing gamma is equal to monitor's native gamma divided by LUT gamma. In other words, an image (untagged by ICC profile) displayed in Windows and Linux will appear the same, provided that the same video card and monitor is used and no colour management/calibration is applied. This is also the reason, why display ICC profiles created in Windows can be used in Linux. If the information quoted above remains, users will be confused and try to set gamma 2.2 in gcm. I would propose to change the text so that it is clear that the user can correct the monitor's native gamma and that it is not the final viewing gamma. Or am I wrong? Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Fri Feb 5 13:32:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 5 Feb 2010 13:32:12 +0000 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> On 5 February 2010 12:55, Milan Kn??ek wrote: > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. That sounds about right to me. Feel free to change it so it's clearer. Thanks. Richard. From knizek.confy at volny.cz Fri Feb 5 20:09:20 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:09:20 +0100 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> Message-ID: <1265400560.29899.18.camel@athlon> Pascal de Bruijn p??e v Po 01. 02. 2010 v 19:29 +0100: > On Mon, Feb 1, 2010 at 12:05 PM, Richard Hughes wrote: > > gnome-color-manager is a session program that makes it easy to manage, install > > and generate color profiles in the GNOME desktop. > > > > Version 2.29.3 > > ~~~~~~~~~~~~~~ > > Released: 2010-02-01 > > As usual, I've built GNOME Color Manager for Ubuntu Karmic, and it's > available on my gcm-release PPA: > > https://launchpad.net/~pmjdebruijn/+archive/gcm-release Is it an expected change in this release that the "fine tuning" option on the main screen of gcm-prefs disappeared? regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From knizek.confy at volny.cz Fri Feb 5 20:39:06 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 05 Feb 2010 21:39:06 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <15e53e181002050532oe6b5a4fv4794c6449f20ab94@mail.gmail.com> Message-ID: <1265402346.29899.48.camel@athlon> Richard Hughes p??e v P? 05. 02. 2010 v 13:32 +0000: > On 5 February 2010 12:55, Milan Kn??ek wrote: > > I would propose to change the text so that it is clear that the user can > > correct the monitor's native gamma and that it is not the final viewing > > gamma. > > That sounds about right to me. Feel free to change it so it's clearer. Thanks. > > Richard. > I will look at the text and propose a new wording. Additionally, it may also be helpful to update the "fine tuning" gamma slider. The slider has "hooks" for 1.8 and 2.2 -this would make sense if the user had a monitor with native gamma value of 1. Then, setting the slider to 2.2 would result in viewing gamma value of 2.2. This probably would not be the case for anyone. Hence, removing the "hooks" would help avoiding confusion. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Sat Feb 6 02:10:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 06 Feb 2010 13:10:48 +1100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <4B6CCFA8.3000107@argyllcms.com> Milan Kn??ek wrote: > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple Sounds bogus. Unix machines have "traditionally" used RGB encoded for display on a typical native CRT gamma. Linux is no different - "traditionally" raw RGB numbers have been sent to the monitor, and you get native CRT gamma or an emulation of it if it's an LCD monitor, so the encoding is notionally set for a gamma of 2.2. But there are exceptions - SGI's had a different scheme, and people creating synthetic images (CGI) have often left their images linear light, and expect the display process to counteract the displays natural gamma, even though this introduces quantization problems if they use 8 bits. > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. Note a couple of things: Latest OS X (10.6 "Snow Leopard") has a default of 2.2, but it seems that "1.8" of the Mac mac prior to this is actually a misnomer, the encoding is actually closer to 1/1.72, which is corrected by a framebuffer ramp of 1/1.45 for display on a CRT of 2.5, giving an overall system gamma of 1.0. Real CRT's have a gamma of nearer 2.4 - 2.5 (although such numbers are very sensitive to the setting of the black level). "Traditionally" from the TV world, material is broadcast with a gamma of 0.45 (ie. 1/2.22) with the expectation that it will be displayed on a monitor that has a gamma of 2.5, the discrepancy applying a viewing conditions transform that accounts for the different appearance between the bright TV studio lighting and the usually dim viewing conditions use with a CRT monitor. For all the details please refer to Charles Poynton's book "Digital Video and HDTV". > Linux tools - like xgamma and gcm - instead tell the number, which is > applied to LUT only. Note that the final viewing gamma is equal to > monitor's native gamma divided by LUT gamma. Right, and the final overall gamma should be 1.0, or (allowing for the viewing condition transform, about 1.1 - 1.2). > I would propose to change the text so that it is clear that the user can > correct the monitor's native gamma and that it is not the final viewing > gamma. > > Or am I wrong? Most people are unfamiliar with the concept of overall system gamma. They might easily confuse the encoding gamma, display gamma and system gamma. The distinction between encoding gamma and display gamma is probably lost on most people too (strictly speaking the encoding gamma for "2.2" is 1/2.2 which is about 0.45, and the overall gamma is the product of the encoding gamma and the display gamma.) I think that if this is a display calibration application, then really it should talk about what the display is being set to, and could indicate how this corresponds to the encoding expectation. So typically a CRT display in a dim viewing environment should be calibrated to have a gamma of about 2.4, with the expectation that it is being fed material that has been encoded with a gamma of 1/2.2. If the display is brighter and in a brighter environment, then a calibration gamma of < 2.4 might be desirable, for the same 2.2 gamma encoded material. Graeme Gill. Graeme Gill. From knizek.confy at volny.cz Sat Feb 6 10:39:03 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 06 Feb 2010 11:39:03 +0100 Subject: Information re. display gamma In-Reply-To: <4B6CCFA8.3000107@argyllcms.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> Message-ID: <1265452743.22070.45.camel@athlon> Graeme Gill p??e v So 06. 02. 2010 v 13:10 +1100: > I think that if this is a display calibration application, then > really it should talk about what the display is being set to, and > could indicate how this corresponds to the encoding expectation. > This means that the GCM would have to change a bit more: GCM must know what the native monitor gamma is. Such an information can be taken from the ICC profile, either supplied by the user, created with GCM and colorimeter or created with GCM and "eye-measured" calibration. The lack of eye-measured calibration is already reported as bug 605019 https://bugzilla.gnome.org/show_bug.cgi?id=605019 which also refers to a tutorial how ColorSync on Mac did it: http://www.computer-darkroom.com/colorsync-display/colorsync_2.htm regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 6 11:46:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 11:46:06 +0000 Subject: GNOME Color Manager 2.29.3 In-Reply-To: <1265400560.29899.18.camel@athlon> References: <15e53e181002010305g11518316xb8d1083a8d357d90@mail.gmail.com> <4c2c37f91002011029g3d302947n742e5f4a28b01685@mail.gmail.com> <1265400560.29899.18.camel@athlon> Message-ID: <15e53e181002060346u2d547bb1g7d6c1cd01ccff1ae@mail.gmail.com> On 5 February 2010 20:09, Milan Kn??ek wrote: > Is it an expected change in this release that the "fine tuning" option > on the main screen of gcm-prefs disappeared? Yes. There's a GConf key to re-enable it if you need the UI, but it's hidden by default until we make the UI nicer to use. It's on my TODO, but didn't quite make the release. New contributors welcome! :) Richard. From j at jonathanleighton.com Sat Feb 6 12:29:46 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Sat, 06 Feb 2010 12:29:46 +0000 Subject: ColorVision Spyder Message-ID: <1265459386.23788.9.camel@tybalt> Hi there, I have a ColorVision Spyder colorimeter. I have just been trying out gnome-color-manager (very impressive!) but the calibration buttons are disabled, even when I plug in my colorimeter. Do I need to take additional steps to use the colorimeter through GCM, or is the support just not there yet or something? Many thanks, Jon PS. Please CC me in replies - I'm not on the list. From hughsient at gmail.com Sat Feb 6 15:55:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:55:31 +0000 Subject: Information re. display gamma In-Reply-To: <1265452743.22070.45.camel@athlon> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> Message-ID: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> On 6 February 2010 10:39, Milan Kn??ek wrote: > This means that the GCM would have to change a bit more: GCM must know > what the native monitor gamma is. We can do this, but in my experience the EDID data from the monitor is wrong more often than it's right... Richard. From hughsient at gmail.com Sat Feb 6 15:57:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 6 Feb 2010 15:57:50 +0000 Subject: ColorVision Spyder In-Reply-To: <1265459386.23788.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> Message-ID: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> On 6 February 2010 12:29, Jon Leighton wrote: > I have a ColorVision Spyder colorimeter. I have just been trying out > gnome-color-manager (very impressive!) but the calibration buttons are > disabled, even when I plug in my colorimeter. What version ArgyllCMS do you have installed? If it's less than 1.1.0 you'll need to add --disable-hardware-detection to ./configure -- it also only works for display devices for now (patches welcome!). > Do I need to take additional steps to use the colorimeter through GCM, > or is the support just not there yet or something? Well, if it's supported in Argyll then it's supported by GCM. Richard. From knizek.confy at volny.cz Sun Feb 7 11:23:57 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sun, 07 Feb 2010 12:23:57 +0100 Subject: Information re. display gamma In-Reply-To: <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> References: <1265374532.31703.61.camel@athlon> <4B6CCFA8.3000107@argyllcms.com> <1265452743.22070.45.camel@athlon> <15e53e181002060755l201687ebn2867abb38d3a853f@mail.gmail.com> Message-ID: <1265541838.20793.5.camel@athlon> Richard Hughes p??e v So 06. 02. 2010 v 15:55 +0000: > On 6 February 2010 10:39, Milan Kn??ek wrote: > > This means that the GCM would have to change a bit more: GCM must know > > what the native monitor gamma is. > > We can do this, but in my experience the EDID data from the monitor is > wrong more often than it's right... > > Richard. > I understand that getting the EDID data is unreliable at the moment. In addition, some wide-gamut displays support pre-set calibration modes emulating various colour spaces. The modes can be changed via hardware buttons on the LCD. For the time being, I would leave up to the user to select the proper display profile (depending on the attached monitor and its calibration mode) rather then only relying on EDID. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From graeme2 at argyllcms.com Mon Feb 8 01:27:50 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 12:27:50 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <4B6F6896.9050406@argyllcms.com> Richard Hughes wrote: > Well, if it's supported in Argyll then it's supported by GCM. But note that the Spyder 2 needs to have firmware. In Argyll the spyd2en utility needs to be run to extract the firmware from the distribution disk. See Graeme Gill. From hughsient at gmail.com Mon Feb 8 07:58:05 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 07:58:05 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6F6896.9050406@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> Message-ID: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> On 8 February 2010 01:27, Graeme Gill wrote: > But note that the Spyder 2 needs to have firmware. In Argyll > the spyd2en utility needs to be run to extract the firmware from > the distribution disk. > See What's the output from argyllcms if there is no firmware? Or does the device just not appear? Thanks, Richard. From graeme2 at argyllcms.com Mon Feb 8 08:22:18 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 19:22:18 +1100 Subject: ColorVision Spyder In-Reply-To: <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> Message-ID: <4B6FC9BA.5030905@argyllcms.com> Richard Hughes wrote: > What's the output from argyllcms if there is no firmware? Or does the > device just not appear? There will be an error message containing: "No PLD firmware pattern is available" Graeme Gill. From hughsient at gmail.com Mon Feb 8 08:40:17 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 08:40:17 +0000 Subject: ColorVision Spyder In-Reply-To: <4B6FC9BA.5030905@argyllcms.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <4B6F6896.9050406@argyllcms.com> <15e53e181002072358w37ec05c4gbe5f44154fa423f@mail.gmail.com> <4B6FC9BA.5030905@argyllcms.com> Message-ID: <15e53e181002080040o56051e39k39dc13f01163194d@mail.gmail.com> On 8 February 2010 08:22, Graeme Gill wrote: > There will be an error message containing: > > "No PLD firmware pattern is available" That's great, thanks. Richard. From hughsient at gmail.com Mon Feb 8 09:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:16:56 +0000 Subject: Small thumbnails of targets Message-ID: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> The attached file shows some new UI in gnome-color-manager -- it now supports more types of targets than just IT8. To be able to show the user a preview of what each target looks like, we need some 200x150 pixel thumbnails of the different target types. These need to be GPLv2+ licenced, and have the specific vendor data removed. See the screenshot for an example. This would be a great way to help out gnome-color-manager if you are not comfortable with coding. The list of target types I need as thumbnails are: CMP_Digital_Target-3 CMP_DT_003 ColorChecker ColorCheckerDC ColorCheckerSG Hutchcolor i1_RGB_Scan_1.4 LaserSoftDCPro QPcard_201 I've already done IT8. Please cc the list if you send me a type, and then we won't get duplicated effort. Note: you can't just copy and paste from the manufacturers website, as they may have copyright on the image. Basically, the rule is if you're not sure about the copyright of the image, then it's not suitable. The best way would be to scan the target yourself and send it to me. If you send files, please state where you got them from, and that they are redistributable as part of a project that is GPLv2+. Thanks, Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot.png Type: image/png Size: 44590 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 09:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 09:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <15e53e181002080147l7e6f4246pf92afe936ffd28b5@mail.gmail.com> On 8 February 2010 09:16, Richard Hughes wrote: > The best way would be to scan the > target yourself and send it to me. If you send files, please state > where you got them from, and that they are redistributable as part of > a project that is GPLv2+. I forgot to mention. They also have to be PNG format. Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 10:00:38 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 10:00:38 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> Message-ID: <1265623238.9194.9.camel@tybalt> On Sat, 2010-02-06 at 15:57 +0000, Richard Hughes wrote: > On 6 February 2010 12:29, Jon Leighton wrote: > > I have a ColorVision Spyder colorimeter. I have just been trying out > > gnome-color-manager (very impressive!) but the calibration buttons are > > disabled, even when I plug in my colorimeter. > > What version ArgyllCMS do you have installed? If it's less than 1.1.0 > you'll need to add --disable-hardware-detection to ./configure -- it > also only works for display devices for now (patches welcome!). Aha, that was it. I've installed latest argyll, and now the button is enabled. However, when I click it and select LCD, I then get the "Display setup" dialog. If I click OK nothing happens - the dialog closes but nothing else comes up. I tried running with -vvv and the following came up: TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 - failed to calibrate: failed to match display as RandR is faulty TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,170 - min=0.000000,max=1.000000 TI:09:52:12 FI:gcm-clut.c FN:gcm_clut_get_array,176 - falling back to dummy gamma TI:09:52:12 FI:gcm-device-xrandr.c FN:gcm_device_xrandr_set_gamma_fallback,351 - using PER-SCREEN gamma tables as driver is not XRANDR 1.3 compliant TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_output_profile,477 - found default, removing atom TI:09:52:12 FI:gcm-xserver.c FN:gcm_xserver_remove_root_window_profile,239 - removing root window ICC profile atom Any ideas? Thanks From hughsient at gmail.com Mon Feb 8 10:39:12 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 10:39:12 +0000 Subject: ColorVision Spyder In-Reply-To: <1265623238.9194.9.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> Message-ID: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> On 8 February 2010 10:00, Jon Leighton wrote: > Aha, that was it. I've installed latest argyll, and now the button is > enabled. That's good. > TI:09:52:12 ? ? FI:gcm-prefs.c ?FN:gcm_prefs_calibrate_display,381 > ?- failed to calibrate: failed to match display as RandR is faulty What video driver are you using? Can you attach the output of xrandr please? Thanks. Richard. From j at jonathanleighton.com Mon Feb 8 11:12:37 2010 From: j at jonathanleighton.com (Jon Leighton) Date: Mon, 08 Feb 2010 11:12:37 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> Message-ID: <1265627557.9194.11.camel@tybalt> Hi, On Mon, 2010-02-08 at 10:39 +0000, Richard Hughes wrote: > > TI:09:52:12 FI:gcm-prefs.c FN:gcm_prefs_calibrate_display,381 > > - failed to calibrate: failed to match display as RandR is faulty > > What video driver are you using? I'm using the nVidia driver, version 185.18.36. > Can you attach the output of xrandr please? Thanks. Yep. Cheers, Jon -------------- next part -------------- Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 50.0 51.0 52.0* 1600x1024 53.0 1440x900 54.0 1360x768 55.0 56.0 1280x1024 57.0 1280x960 58.0 1152x864 59.0 1024x768 60.0 960x600 61.0 960x540 62.0 840x525 63.0 64.0 800x600 65.0 66.0 800x512 67.0 720x450 68.0 700x525 69.0 680x384 70.0 71.0 640x512 72.0 640x480 73.0 74.0 576x432 75.0 512x384 76.0 400x300 77.0 320x240 78.0 From hughsient at gmail.com Mon Feb 8 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 11:20:27 +0000 Subject: ColorVision Spyder In-Reply-To: <1265627557.9194.11.camel@tybalt> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> Message-ID: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> On 8 February 2010 11:12, Jon Leighton wrote: > I'm using the nVidia driver, version 185.18.36. Hmm, I fear this maybe another case of broken binary drivers. Is there any chance you could try with the nouveau driver please? Thanks. Richard. From graeme2 at argyllcms.com Mon Feb 8 11:58:48 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Mon, 08 Feb 2010 22:58:48 +1100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4B6FFC78.9010503@argyllcms.com> I've sent Richard an image of the ColorCheckerDC. Graeme Gill From j at jonathanleighton.com Mon Feb 8 14:18:05 2010 From: j at jonathanleighton.com (Jonathan Leighton) Date: Mon, 8 Feb 2010 14:18:05 +0000 Subject: ColorVision Spyder In-Reply-To: <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> Message-ID: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Hi, On 8 February 2010 11:20, Richard Hughes wrote: > On 8 February 2010 11:12, Jon Leighton wrote: >> I'm using the nVidia driver, version 185.18.36. > > Hmm, I fear this maybe another case of broken binary drivers. Is there > any chance you could try with the nouveau driver please? Thanks. Yes, it worked under nouveau. (Incidentally, the calibration seemed pretty quick, and I'm not sure the results were great in my case. Are there any plans to have an option of "quick profile" vs "good profile"?) Cheers, Jon From pmjdebruijn at pcode.nl Mon Feb 8 14:27:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:27:24 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > ColorChecker I have just done these two... > I've already done IT8. I redid the IT8, we should called this IT8.7/2, since that's it's proper name... There are other IT8 charts (I think those are mostly for printing), using the full name should prevent any confusion. With all the images, I scanned my own targets, and then followed this procedure: 1. Despeckle, Adaptive enabled, Recursive dislabed, Radius 3, Black level 6, White level 255 2. Then possibly rotate the chart a bit to align it, and then crop it. 3. Then use GIMP Resynthesize to remove vendor text "Smart remove selection", with 10px. 4. Possibly have GIMP do Auto White Balance (doesn't work always) Without distorting aspect, my images could all be rounded to 200px by 140px. I think we should not distort aspect in any visible way. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: IT872.png Type: image/png Size: 31624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ColorChecker24.png Type: image/png Size: 32929 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CMP-DigitalTarget3.png Type: image/png Size: 44514 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 14:52:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 14:52:23 +0000 Subject: ColorVision Spyder In-Reply-To: <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> References: <1265459386.23788.9.camel@tybalt> <15e53e181002060757g294b51a4i424d6c4014664ade@mail.gmail.com> <1265623238.9194.9.camel@tybalt> <15e53e181002080239u5cc3fda4s37ae03c85588f36a@mail.gmail.com> <1265627557.9194.11.camel@tybalt> <15e53e181002080320v7d8e97e1j2fa7398b84b6d562@mail.gmail.com> <854dd6441002080618u4875a30ew20f5946b61668e56@mail.gmail.com> Message-ID: <15e53e181002080652j1616f139h65a133fb55b1e895@mail.gmail.com> On 8 February 2010 14:18, Jonathan Leighton wrote: > (Incidentally, the calibration seemed pretty quick, and I'm not sure > the results were great in my case. Are there any plans to have an > option of "quick profile" vs "good profile"?) Grab gcm from git master, and then set /apps/gnome-color-manager/calibration_length in GConf Editor. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 14:56:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 15:56:17 +0100 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4B6FFC78.9010503@argyllcms.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> Message-ID: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: > I've sent Richard an image of the ColorCheckerDC. I noticed it got commited... But it's aspect ratio is slightly off... You obviously did that to comply with Richard's 200x150 specification... But 200x140 as a baseline would be better for most charts... You're ColorCheckerDC image looks much better when rescaled to 200x140. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Mon Feb 8 15:04:06 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:04:06 +0100 Subject: Camera profile generation options Message-ID: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Hi, Are camera profiles generated with Argyll's default options? -q m -a l ? This might be fine for IT8 or other targets with lots of patches... But it's probably not such a good idea for a 24 patch ColorChecker, -q l -a S seems more appropriate... Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:04:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:04:27 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4c2c37f91002080627n5cfabf5er1cb07943dc49db65@mail.gmail.com> Message-ID: <15e53e181002080704o79716ec2kd131bf0fbf8feafb@mail.gmail.com> On 8 February 2010 14:27, Pascal de Bruijn wrote: > I have just done these two... Brilliant, thanks. >> I've already done IT8. > > I redid the IT8, we should called this IT8.7/2, since that's it's > proper name... There are other IT8 charts (I think those are mostly > for printing), using the full name should prevent any confusion. Done, thanks. > Without distorting aspect, my images could all be rounded to 200px by > 140px. I think we should not distort aspect in any visible way. Okay, I've changed the others to be 200x140 also. Thanks. Richard. From hughsient at gmail.com Mon Feb 8 15:12:35 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:12:35 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> Message-ID: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> On 8 February 2010 15:04, Pascal de Bruijn wrote: > Are camera profiles generated with Argyll's default options? -q m -a l ? > > This might be fine for IT8 or other targets with lots of patches... > > But it's probably not such a good idea for a 24 patch ColorChecker, -q > l -a S seems more appropriate... Yes, this is a good idea, and a perfect patch for you to submit :-) The kind of profile is listed in src/gcm-calibrate-argyll.h, which is saved to priv->reference_kind, which is private data for the GcmCalibrateArgyll object. You probably need to add a simple "if (priv->reference_kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just getting the type of profile (using gcm_calibrate_argyll_precision_to_quality_arg) in the function gcm_calibrate_argyll_device_generate_profile() which lives in src/gcm-calibrate-argyll.c Make a few changes, and just do "git diff > test.patch" Attach the test.patch to an email (on the mailing list if you're feeling brave, or just to me if you're feeling timid) and I'll give you some feedback. Grab me on IRC if you are feeling really stuck / lazy / busy. Richard. From hughsient at gmail.com Mon Feb 8 15:14:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:14:22 +0000 Subject: Small thumbnails of targets (ColorCheckerDC) In-Reply-To: <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <4B6FFC78.9010503@argyllcms.com> <4c2c37f91002080656u1d34af63m612d1309606be2b2@mail.gmail.com> Message-ID: <15e53e181002080714y11dad8afxb11eb95cbd801a85@mail.gmail.com> On 8 February 2010 14:56, Pascal de Bruijn wrote: > On Mon, Feb 8, 2010 at 12:58 PM, Graeme Gill wrote: >> I've sent Richard an image of the ColorCheckerDC. > > I noticed it got commited... But it's aspect ratio is slightly off... > You obviously did that to comply with Richard's 200x150 > specification... No, I did that, Graeme sent me the original image. I've sent you the profile for the same love. > But 200x140 as a baseline would be better for most charts... You're > ColorCheckerDC image looks much better when rescaled to 200x140. Agreed. Richard. From hughsient at gmail.com Mon Feb 8 15:16:29 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:16:29 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? Message-ID: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> I've got sources that look like this: if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) return "CMP_Digital_Target-3.cht"; if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) return "CMP_DT_003.cht"; Are they actually the same profile type? What's the difference in the chart versions? Thanks, Richard. From pmjdebruijn at pcode.nl Mon Feb 8 15:46:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 16:46:17 +0100 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> Message-ID: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> On Mon, Feb 8, 2010 at 4:16 PM, Richard Hughes wrote: > I've got sources that look like this: > > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DIGITAL_TARGET_3) > ? ? ? ? ? ? ? ?return "CMP_Digital_Target-3.cht"; > ? ? ? ?if (kind == GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_CMP_DT_003) > ? ? ? ? ? ? ? ?return "CMP_DT_003.cht"; > > Are they actually the same profile type? What's the difference in the > chart versions? They are different charts... I have this one (3): http://www.cmp-color.fr/eng%20digital%20target.html Are there is the 003 one: http://www.argyllcms.com/doc/CMP_DT_003.jpg Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 8 15:48:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 15:48:53 +0000 Subject: is CMP_Digital_Target-3 == CMP_DT_003?? In-Reply-To: <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> References: <15e53e181002080716q54d129e7l46c54c651f220868@mail.gmail.com> <4c2c37f91002080746m38507654w7f6a5c2a561f8295@mail.gmail.com> Message-ID: <15e53e181002080748i4f953979j9999944c092cc31@mail.gmail.com> On 8 February 2010 15:46, Pascal de Bruijn wrote: > They are different charts... Cool, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 21:32:32 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:32:32 +0100 Subject: Camera profile generation options In-Reply-To: <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> Message-ID: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> On Mon, Feb 8, 2010 at 4:12 PM, Richard Hughes wrote: > On 8 February 2010 15:04, Pascal de Bruijn wrote: >> Are camera profiles generated with Argyll's default options? -q m -a l ? >> >> This might be fine for IT8 or other targets with lots of patches... >> >> But it's probably not such a good idea for a 24 patch ColorChecker, -q >> l -a S seems more appropriate... > > Yes, this is a good idea, and a perfect patch for you to submit :-) > > The kind of profile is listed in src/gcm-calibrate-argyll.h, which is > saved to priv->reference_kind, which is private data for the > GcmCalibrateArgyll object. You probably need to add a simple "if > (priv->reference_kind == > GCM_CALIBRATE_ARGYLL_REFERENCE_KIND_COLOR_CHECKER)" rather than just > getting the type of profile (using > gcm_calibrate_argyll_precision_to_quality_arg) in the function > gcm_calibrate_argyll_device_generate_profile() which lives in > src/gcm-calibrate-argyll.c > > Make a few changes, and just do "git diff > test.patch" I think this patch should do it, it seems to work, though I didn't extensively test it. I also included the QPcard as well, it's a similar target... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-calibrate-argyll-low-patch-count-target-low-quality-single-shaper.patch Type: text/x-patch Size: 2556 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 8 21:58:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 22:58:24 +0100 Subject: Camera Profiling GUI Dialog Order Message-ID: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Hi, Currently to profile a camera, the GUI first asks for both files, and then asks for the chart type... This seems odd to me... It seems more natural to me, to first ask about the chart type, and then ask about the files... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-prefs-ask-reference-kind-first.patch Type: text/x-patch Size: 1241 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:23:07 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:23:07 +0000 Subject: Camera profile generation options In-Reply-To: <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> References: <4c2c37f91002080704h5b351c25v2e646f7674c57db9@mail.gmail.com> <15e53e181002080712i4429f3bay9915e365de1909ef@mail.gmail.com> <4c2c37f91002081332o5e3ccd9es962fcdc5b6c2e472@mail.gmail.com> Message-ID: <15e53e181002081423g6279830eq5c07be8d8aca9e9e@mail.gmail.com> On 8 February 2010 21:32, Pascal de Bruijn wrote: > I think this patch should do it, it seems to work, though I didn't > extensively test it. Great stuff. I've modified your patch a little (just passing the calibrate_argyll object and renaming a function) and committed it. I've attached the changed version. Well done! Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Do-low-quality-calibration-when-using-targets-with-a.patch Type: text/x-patch Size: 3393 bytes Desc: not available URL: From amluto at gmail.com Mon Feb 8 22:23:02 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Mon, 8 Feb 2010 17:23:02 -0500 Subject: Reduce autoconf requirement Message-ID: Hi all- For kicks, I just grabbed gnome-color-manager out of git, built it, and ran it on KDE4 on Fedora 12. (why not?) It seems to work (I haven't tested its Argyll integration yet.) To make it build, though, I had to decrease the autoconf required version, like this: diff --git a/configure.ac b/configure.ac index bf4e31f..d4f422b 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_PREREQ(2.65) +AC_PREREQ(2.63) AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) AC_CONFIG_SRCDIR(src) Is there any reason we require autogen 2.65? 2.63 from F12 seems to work just fine. shared-color-targets needs the same patch. As an aside, what's the profile graph on the right? Is it the calibration (VCGT), the gray axis of the profile, or something else? (I assume it's not the gray axis -- it doesn't really look like xicclu's output.) Thanks, Andy From hughsient at gmail.com Mon Feb 8 22:24:45 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:24:45 +0000 Subject: Camera Profiling GUI Dialog Order In-Reply-To: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> References: <4c2c37f91002081358y7d4d34a1r2d32b52de4f7d59f@mail.gmail.com> Message-ID: <15e53e181002081424hc401819k29fc0a3c0ad96d8@mail.gmail.com> On 8 February 2010 21:58, Pascal de Bruijn wrote: > Currently to profile a camera, the GUI first asks for both files, and > then asks for the chart type... This seems odd to me... Agreed. > It seems more natural to me, to first ask about the chart type, and > then ask about the files... Committed, thanks. Richard. From pmjdebruijn at pcode.nl Mon Feb 8 22:26:34 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 8 Feb 2010 23:26:34 +0100 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> On Mon, Feb 8, 2010 at 11:23 PM, Andrew Lutomirski wrote: > Hi all- > > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) > > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) > > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. I apply the attached patch to git to make it work on Ubuntu Karmic. > shared-color-targets needs the same patch. > > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) If I'm not mistaken those are the TRC's... VCGT is only relevant for displays... Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: gcm-git-demodernize-configure-ac.patch Type: text/x-patch Size: 2099 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 8 22:27:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:27:40 +0000 Subject: Reduce autoconf requirement In-Reply-To: References: Message-ID: <15e53e181002081427m68ba1894w9810233b37c1cf53@mail.gmail.com> On 8 February 2010 22:23, Andrew Lutomirski wrote: > For kicks, I just grabbed gnome-color-manager out of git, built it, > and ran it on KDE4 on Fedora 12. ?(why not?) ?It seems to work (I > haven't tested its Argyll integration yet.) Sure, it should work. > To make it build, though, I had to decrease the autoconf required > version, like this: > > diff --git a/configure.ac b/configure.ac > index bf4e31f..d4f422b 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -1,4 +1,4 @@ > -AC_PREREQ(2.65) > +AC_PREREQ(2.63) > > ?AC_INIT([gnome-color-manager],[2.29.4],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager]) > ?AC_CONFIG_SRCDIR(src) The 2.63 BR was from autoupdate'ing the scripts. > Is there any reason we require autogen 2.65? ?2.63 from F12 seems to > work just fine. If it works, great! > shared-color-targets needs the same patch. Will do. > As an aside, what's the profile graph on the right? ?Is it the > calibration (VCGT), the gray axis of the profile, or something else? > (I assume it's not the gray axis -- it doesn't really look like > xicclu's output.) I think we need graph labels in this case. It's actually the TRC. Richard. From hughsient at gmail.com Mon Feb 8 22:28:44 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 8 Feb 2010 22:28:44 +0000 Subject: Reduce autoconf requirement In-Reply-To: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> References: <4c2c37f91002081426n580031edj72e2016689d7d4ea@mail.gmail.com> Message-ID: <15e53e181002081428p43926011mf3d6510d720a492c@mail.gmail.com> On 8 February 2010 22:26, Pascal de Bruijn wrote: > I apply the attached patch to git to make it work on Ubuntu Karmic. Hmm, that seems a bit drastic. Doesn't changing the version to 2.63 work okay in the Karmic case? Richard. From pmjdebruijn at pcode.nl Tue Feb 9 11:29:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:29:44 +0100 Subject: QPcard 201 thumbnail Message-ID: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> Hi, Here's a QPcard_201 thumbnail, postprocessed from a scanned image, submitted on the ArgyllCMS mailing list by Wallden Magnus. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201.png Type: image/png Size: 14124 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Tue Feb 9 11:35:55 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 12:35:55 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> Message-ID: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> On Tue, Feb 9, 2010 at 12:34 PM, Pascal de Bruijn wrote: > On Tue, Feb 9, 2010 at 12:29 PM, Pascal de Bruijn wrote: >> Hi, >> >> Here's a QPcard_201 thumbnail, postprocessed from a scanned image, >> submitted on the ArgyllCMS mailing list by Wallden Magnus. > > Whoops, forgot to remove the branding. Whoops, posted the hires version, not the thumbnail... Sorry, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: QPcard_201_unbranded.png Type: image/png Size: 12926 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 9 12:06:32 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 12:06:32 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> Message-ID: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> On 9 February 2010 11:35, Pascal de Bruijn wrote: > Whoops, posted the hires version, not the thumbnail... I've committed this after padding the height to 140 like the others. I really don't want the dialog resizing as the combobox elements are selected. Thanks, Richard. From pmjdebruijn at pcode.nl Tue Feb 9 13:10:48 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 14:10:48 +0100 Subject: QPcard 201 thumbnail In-Reply-To: <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> Message-ID: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> On Tue, Feb 9, 2010 at 1:06 PM, Richard Hughes wrote: > On 9 February 2010 11:35, Pascal de Bruijn wrote: >> Whoops, posted the hires version, not the thumbnail... > > I've committed this after padding the height to 140 like the others. I > really don't want the dialog resizing as the combobox elements are > selected. I noticed you centered the image... Though, the white background suggests it's a big white card, with the patches centered, while it's not. We should use transparency here. I'll "fix" the image tonight, if you don't get to it first. Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 13:11:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:11:43 +0000 Subject: Using SANE? Message-ID: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> I'm thinking of using SANE (rather than udev like we do now) to get the list of scanners, and hopefully to be able to change settings on the device. It also allows us to change remote devices, not just locally plugged in USB ones. Is sane-backends-libs a problem for you distro guys? I'm not sure if it's installed by default on most distros, but it does pull in a few deps. Comments? Richard. From hughsient at gmail.com Tue Feb 9 13:17:15 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 13:17:15 +0000 Subject: QPcard 201 thumbnail In-Reply-To: <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> References: <4c2c37f91002090329t4e29171egb88da4116d579b6d@mail.gmail.com> <4c2c37f91002090334q3c2f8398g2238ab37e5b4c204@mail.gmail.com> <4c2c37f91002090335r6b3dccdama090e78877327d5d@mail.gmail.com> <15e53e181002090406q2bf3c0fcucba0ec6828c08d91@mail.gmail.com> <4c2c37f91002090510p4a911181n3e07401803649170@mail.gmail.com> Message-ID: <15e53e181002090517m76d879bdyba6cc199da454ebd@mail.gmail.com> On 9 February 2010 13:10, Pascal de Bruijn wrote: > I noticed you centered the image... Though, the white background > suggests it's a big white card, with the patches centered, while it's > not. Point taken. > We should use transparency here. I'll "fix" the image tonight, if you > don't get to it first. Okay. when you're submitting new binary files, the easiest way (for me) to do it, is this: git checkout -b the-subject-of-the-change git commit -a -m "Make the image background transparent" --author "Me Mine " ( the -a means "all changes to the working tree", the -m means "this is the commit message", and --author is so the right person gets listed in NEWS) git format-patch master git checkout master Then, all I have to do is use the command "git am" and I don't have to copy and paste your name, email, or come up with a commit message. If you get stuck, let me know. Richard. From fred at crozat.net Tue Feb 9 14:01:39 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:01:39 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> Message-ID: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> 2010/2/9 Richard Hughes : > I'm thinking of using SANE (rather than udev like we do now) to get > the list of scanners, and hopefully to be able to change settings on > the device. It also allows us to change remote devices, not just > locally plugged in USB ones. Is sane-backends-libs a problem for you > distro guys? I'm not sure if it's installed by default on most > distros, but it does pull in a few deps. How about using PackageKit to install it "on demand" ? ;) gnome-color-manager is installed "by default" in Mandriva 2010.0 but I'd like to keep sane ouf of the default install, if we can. -- Frederic Crozat From hughsient at gmail.com Tue Feb 9 14:21:02 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 14:21:02 +0000 Subject: Using SANE? In-Reply-To: <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> Message-ID: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> On 9 February 2010 14:01, Frederic Crozat wrote: > 2010/2/9 Richard Hughes : >> I'm thinking of using SANE (rather than udev like we do now) to get >> the list of scanners, and hopefully to be able to change settings on >> the device. It also allows us to change remote devices, not just >> locally plugged in USB ones. Is sane-backends-libs a problem for you >> distro guys? I'm not sure if it's installed by default on most >> distros, but it does pull in a few deps. > > How about using PackageKit to install it "on demand" ? ;) Heh, this would be a library dep, not a tool dep. > gnome-color-manager is installed "by default" in Mandriva 2010.0 but > I'd like to keep sane ouf of the default install, if we can. You mean sane-backends-libs, rather than sane itself, right? Richard. From fred at crozat.net Tue Feb 9 14:34:22 2010 From: fred at crozat.net (Frederic Crozat) Date: Tue, 9 Feb 2010 15:34:22 +0100 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: <21ad25711002090634y7ef9e181oa77e6a7796a63c99@mail.gmail.com> 2010/2/9 Richard Hughes : > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Ah :( >> gnome-color-manager is installed "by default" in Mandriva 2010.0 but >> I'd like to keep sane ouf of the default install, if we can. > > You mean sane-backends-libs, rather than sane itself, right? Yes, I mean the lib package. It is 7.7MB installed, without checking its dependencies (of course, now, I've discovered openoffice-common is pulling libsane by default too :( If it could be a plugin, that would be nice :) -- Frederic Crozat From amluto at gmail.com Tue Feb 9 15:15:28 2010 From: amluto at gmail.com (Andrew Lutomirski) Date: Tue, 9 Feb 2010 10:15:28 -0500 Subject: Using SANE? In-Reply-To: <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> References: <15e53e181002090511j7670d09eu17536ed3f8a71e37@mail.gmail.com> <21ad25711002090601y7acd4bdt2d3ab24ebbd5e5ba@mail.gmail.com> <15e53e181002090621o6357e17ev8af02615cb7ed031@mail.gmail.com> Message-ID: On Tue, Feb 9, 2010 at 9:21 AM, Richard Hughes wrote: > On 9 February 2010 14:01, Frederic Crozat wrote: >> 2010/2/9 Richard Hughes : >>> I'm thinking of using SANE (rather than udev like we do now) to get >>> the list of scanners, and hopefully to be able to change settings on >>> the device. It also allows us to change remote devices, not just >>> locally plugged in USB ones. Is sane-backends-libs a problem for you >>> distro guys? I'm not sure if it's installed by default on most >>> distros, but it does pull in a few deps. >> >> How about using PackageKit to install it "on demand" ? ;) > > Heh, this would be a library dep, not a tool dep. Is it safe to assume that anyone who wants to profile a scanner already has sane-backends-libs installed? If so, you could dlopen it and if that fails assume that there aren't any scanners. --Andy From pmjdebruijn at pcode.nl Tue Feb 9 19:28:41 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 9 Feb 2010 20:28:41 +0100 Subject: Disconnected devices: create profiles for device disabled Message-ID: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Hi, When I have a EOS 400D disconnected, the "Create profiles for device" button is disabled, is this intentional? There is no good reason why my camera would need to be connected... For displays, it has it's advantages having the display connected for profiling though :p Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 9 19:49:22 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 9 Feb 2010 19:49:22 +0000 Subject: Disconnected devices: create profiles for device disabled In-Reply-To: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> References: <4c2c37f91002091128g6cae5184xc69a3431c5aea64a@mail.gmail.com> Message-ID: <15e53e181002091149q7815c328n20cd83e87060efd6@mail.gmail.com> On 9 February 2010 19:28, Pascal de Bruijn wrote: > For displays, it has it's advantages having the display connected for > profiling though :p commit 9da8afc4f5dd9c7a0e252fa42483616c74696695 Author: Richard Hughes Date: Tue Feb 9 19:34:43 2010 +0000 Only require the device to be present if it is a display type :100644 100644 66af4b3... f25d118... M src/gcm-prefs.c Richard. From lars.tore at mulebakken.net Wed Feb 10 13:29:22 2010 From: lars.tore at mulebakken.net (Lars Tore Gustavsen) Date: Wed, 10 Feb 2010 14:29:22 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> Message-ID: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> On Mon, Feb 8, 2010 at 10:16 AM, Richard Hughes wrote: > The attached file shows some new UI in gnome-color-manager -- it now > supports more types of targets than just IT8. To be able to show the > user a preview of what each target looks like, we need some 200x150 > pixel thumbnails of the different target types. These need to be > GPLv2+ licenced, and have the specific vendor data removed. See the > screenshot for an example. > > This would be a great way to help out gnome-color-manager if you are > not comfortable with coding. The list of target types I need as > thumbnails are: > > CMP_Digital_Target-3 > CMP_DT_003 > ColorChecker > ColorCheckerDC > ColorCheckerSG > Hutchcolor > i1_RGB_Scan_1.4 Here is a photo of the i1_RGB_Scan_1.4 scan target. I have removed the eye-one name. And it's OK with GPLv2+ Lars Tore Gustavsen -------------- next part -------------- A non-text attachment was scrubbed... Name: i1_RGB_Scan_14.png Type: image/png Size: 36266 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 10 19:38:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 10 Feb 2010 19:38:39 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> Message-ID: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> On 10 February 2010 17:17, Pascal de Bruijn wrote: > I modified the thumbnail slightly to even out the lighting, and > improve contrast. Looks great. > I attached a patch for the modified version for git master. Tanks, I've also merged the Makefile.am and gcm-prefs.c parts too. Thanks. Richard. From knizek.confy at volny.cz Wed Feb 10 20:01:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 21:01:36 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo Message-ID: <1265832096.26568.43.camel@athlon> Hello everyone on the list! GCM is getting feature-rich - display, scanner and camera profiling is already supported, but printer characterisation is still missing. Richard H would like to code the few bytes ;-) but he does not have a spectrophotometer at hand. On Richard's blog, Paul Finnigan proposed a donation from users - the ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 in the U.K., were Richard lives. The more expensive variant would require about 10 people @ USD 50 donation each. (Or less donors to buy in the U.S. and someone to actually deliver across the ocean.) At the moment, three of us offered a contribution. Anybody else here willing to help with even a smaller amount (probably via PayPal)? Or other suggestions? best regards, Milan Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Wed Feb 10 20:52:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 10 Feb 2010 21:52:27 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> On Wed, Feb 10, 2010 at 9:01 PM, Milan Kn??ek wrote: > Hello everyone on the list! > > ... > > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? I'd be willing to pitch in (PayPal) for about 25EUR... Regards, Pascal de Bruijn From knizek.confy at volny.cz Wed Feb 10 22:31:36 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Wed, 10 Feb 2010 23:31:36 +0100 Subject: Information re. display gamma In-Reply-To: <1265374532.31703.61.camel@athlon> References: <1265374532.31703.61.camel@athlon> Message-ID: <1265841096.7579.76.camel@athlon> Getting back to update of the text: > -- > Gamma is adjusted to affect the color of the attached monitor. > Traditionally Linux has used a gamma value of 1.0, but this makes > monitors look washed out compared Windows XP or OS X. Apple > traditionally used a value of 1.8 for a long time, but now use the same > value as Microsoft. Microsoft has always used a value of 2.2. > -- Taking into account Graeme's points (thanks, it was helpful), how about this: (The GCM gamma fine tuning tool remains as it is - i.e. pure adjustment to LUT, not taking care about the monitor native gamma) --- Overall system gamma is a product of image encoding gamma, video card gamma and native gamma of the monitor and normally it should be equal to 1. You may want to adjust gamma to allow for non-standard viewing conditions (e.g increasing gamma in dim light at home). Refer to User Manual for more details. --- And this be included in User Manual: --- CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually emulate the same value. Traditionally, Linux and MS Windows operating systems use image encoding of 1/2.2 and do not apply any gamma adjustment to the image or video card LUT. Therefore the overall gamma is expected to be around 1.1 (which is useful to allow for dim viewing conditions at home environment). Apple used to use image encoding gamma close to 1/1.8 to naturally match the native gamma of printing devices (and therefore internally applied gamma adjustment of 1/1.45 before displaying images on monitor so that the images displayed correctly). Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding gamma has also the value of 1/2.2 to meet the requirements of consumer imaging industry. Before fine tuning the gamma in GCM, you should know what your monitor native gamma is, what display gamma you want to reach and then do the math yourself. --- regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pedro at pedrocr.net Thu Feb 11 08:49:07 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 00:49:07 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <4c2c37f91002101252y3c9b927t4ff40c07198f0e01@mail.gmail.com> Message-ID: <62e8012c1002110049j76960ec1jbeac96b428a2221c@mail.gmail.com> On Wed, Feb 10, 2010 at 12:52 PM, Pascal de Bruijn > I'd be willing to pitch in (PayPal) for about 25EUR... You can count me in for another 50$. Pedro From paul at fincc.com Thu Feb 11 09:54:05 2010 From: paul at fincc.com (Paul Finnigan) Date: Thu, 11 Feb 2010 09:54:05 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <1265882045.4190.8.camel@localhost> Hi everyone Sorry, I took a few days off reading the postings. Thanks Milan for trying to drive this one. On Wed, 2010-02-10 at 21:01 +0100, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. > > The more expensive variant would require about 10 people @ USD 50 > donation each. (Or less donors to buy in the U.S. and someone to > actually deliver across the ocean.) I am a photographer who likes to keep up with the Jones' (MS/Apple). To do this while running Linux I have had to make compromise after compromise with regard to 'Free' software. This is my own choice and I am not complaining about it. As an example I have paid for the Turbo Linux printer drivers. I have to say they are good, I do not begrudge the author his 29 euros. If I want free software then I believe it will cost me money at times. What Richard is providing is something, as a photographer, I have wanted for some time. He is also providing the source to the community. I know others are involved (thanks to everyone who is helping). I admit my suggestion of $50 was perhaps high. I just thought that as I know that TurboLinux drivers are popular with photographers I could pitch in a little above that price ($38). I am sure that we as a community can support ourselves. Look at what the Gnome community has already done. What is being asked here is that we get some hardware for a key developer to ensure that the software does what we all want, to help us manage colour. To get the ball rolling we need to set up an account. I am willing to let Richard have my $50 even if we do not reach the target of $500. If Richard or anyone else would like to mail me directly my address is paul at fincc dot com. -- Paul Finnigan From pmjdebruijn at pcode.nl Thu Feb 11 10:38:54 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 11:38:54 +0100 Subject: Small thumbnails of targets In-Reply-To: <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> Message-ID: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> On Wed, Feb 10, 2010 at 8:38 PM, Richard Hughes wrote: > On 10 February 2010 17:17, Pascal de Bruijn wrote: >> I modified the thumbnail slightly to even out the lighting, and >> improve contrast. > > Looks great. I just processed the ColorCheckerSG image submitted by Hening Betterman on the ArgyllCMS mailing list. I attached a patch. Please verify before committing. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-ColorCheckerSG-target-image-submitted-by-Hening-.patch Type: text/x-patch Size: 45877 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 11 10:53:42 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:53:42 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> Message-ID: <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> On 11 February 2010 10:38, Pascal de Bruijn wrote: > I just processed the ColorCheckerSG image submitted by Hening > Betterman on the ArgyllCMS mailing list. > > I attached a patch. Please verify before committing. Perfect. Thanks. Richard. From hughsient at gmail.com Thu Feb 11 10:55:40 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 10:55:40 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> On 11 February 2010 09:54, Paul Finnigan wrote: > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If we don't reach the target I just have to convince my wife that it's a work thing and pony up the rest. Richard. From hughsient at gmail.com Thu Feb 11 11:05:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 11:05:28 +0000 Subject: Information re. display gamma In-Reply-To: <1265841096.7579.76.camel@athlon> References: <1265374532.31703.61.camel@athlon> <1265841096.7579.76.camel@athlon> Message-ID: <15e53e181002110305h113bd2c8kd8b863fbc1a4005e@mail.gmail.com> On 10 February 2010 22:31, Milan Kn??ek wrote: > Overall system gamma is a product of image encoding gamma, video card > gamma and native gamma of the monitor and normally it should be equal to > 1. You may want to adjust gamma to allow for non-standard viewing > conditions (e.g increasing gamma in dim light at home). Refer to User > Manual for more details. > --- > And this be included in User Manual: > --- > CRT monitors have native gamma around 2.4 - 2.5 and LCD monitors usually > emulate the same value. > > Traditionally, Linux and MS Windows operating systems use image encoding > of 1/2.2 and do not apply any gamma adjustment to the image or video > card LUT. Therefore the overall gamma is expected to be around 1.1 > (which is useful to allow for dim viewing conditions at home > environment). > > Apple used to use image encoding gamma close to 1/1.8 to naturally match > the native gamma of printing devices (and therefore internally applied > gamma adjustment of 1/1.45 before displaying images on monitor so that > the images displayed correctly). > > Nonetheless, since OS X (v10.6 Snow Leopard) the default image encoding > gamma has also the value of 1/2.2 to meet the requirements of consumer > imaging industry. > > Before fine tuning the gamma in GCM, you should know what your monitor > native gamma is, what display gamma you want to reach and then do the > math yourself. Sounds good to me. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 11 11:57:49 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 12:57:49 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> Message-ID: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> On Thu, Feb 11, 2010 at 11:55 AM, Richard Hughes wrote: > On 11 February 2010 09:54, Paul Finnigan wrote: >> To get the ball rolling we need to set up an account. I am willing to >> let Richard have my $50 even if we do not reach the target of $500. > > If we don't reach the target I just have to convince my wife that it's > a work thing and pony up the rest. Then setup a PayPal account, and leave the details here :) Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 11 12:55:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 11 Feb 2010 12:55:27 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <15e53e181002110255p39f6c616k3adb4aacbd0fa4ba@mail.gmail.com> <4c2c37f91002110357r79c4f945s6289a75448e9a117@mail.gmail.com> Message-ID: <15e53e181002110455l21da13pfe21eccf360fc192@mail.gmail.com> On 11 February 2010 11:57, Pascal de Bruijn wrote: > Then setup a PayPal account, and leave the details here :) I've already got a paypal account, richard at hughsie.com Please leave me your email addresses in any payments, in case we make nowhere near the total and I have to refund people. Thanks. Richard. From alexandre.prokoudine at gmail.com Thu Feb 11 19:30:38 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Thu, 11 Feb 2010 22:30:38 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> On 2/10/10, Milan Kn??ek wrote: > Anybody else here willing to help with even a smaller amount (probably > via PayPal)? Or other suggestions? Yes, via PayPal. Count me in. Alexandre From pmjdebruijn at pcode.nl Thu Feb 11 20:44:25 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 11 Feb 2010 21:44:25 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> Message-ID: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> On Thu, Feb 11, 2010 at 8:30 PM, Alexandre Prokoudine wrote: > On 2/10/10, Milan Kn??ek wrote: > >> Anybody else here willing to help with even a smaller amount (probably >> via PayPal)? Or other suggestions? > > Yes, via PayPal. Count me in. I just PayPalled 25 EUR... Regards, Pascal de Bruijn From pedro at pedrocr.net Fri Feb 12 01:42:10 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 11 Feb 2010 17:42:10 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> Message-ID: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: > I just PayPalled 25 EUR... Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware organizations do this in scale? It would be great to be able to pitch in money to a common fund saying "I'd like this specific piece/type of hardware to work better in Linux" so that developers could get free access to hardware. By the way Richard, I've recently been through the battle of profiling my Epson R2880 with color munki, directly with argyll commands. I kept a few notes so I can tell you the commands that worked, the number of patches that were reasonable and especially about a small hack I did to be able to use much smaller patches with the color munki (and thus use less paper). Cheers, Pedro From pmjdebruijn at pcode.nl Fri Feb 12 07:38:57 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 08:38:57 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> On Fri, Feb 12, 2010 at 2:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 12:44 PM, Pascal de Bruijn wrote: >> I just PayPalled 25 EUR... > > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? It would be great to be able to pitch > in money to a common fund saying "I'd like this specific piece/type of > hardware to work better in Linux" so that developers could get free > access to hardware. > > By the way Richard, I've recently been through the battle of profiling > my Epson R2880 with color munki, directly with argyll commands. I kept > a few notes so I can tell you the commands that worked, the number of > patches that were reasonable and especially about a small hack I did > to be able to use much smaller patches with the color munki (and thus > use less paper). Your hack was pretty cool, but it's not really handy to implement as a generic solution for GCM, we need no fuss solutions. This works very well for me... and would be a great default for medium quality: argyll-targen -v -d2 -f 210 xxx printtarg -v -i CM -h -T 300 -p A4 xxx colprof -q m -a l xxx For low quality the -h parameter can be dropped from printtarg, and lower the number of patches to ~90, whatever fits on a A4 piece of paper... One the the main problems is that these settings can vary from spectrophotometer to spectrophotometer... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 08:54:11 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:54:11 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <15e53e181002120054j23a0b855n55a671f870605644@mail.gmail.com> On 12 February 2010 07:38, Pascal de Bruijn > One the the main problems is that these settings can vary from > spectrophotometer to spectrophotometer... Sure, but we only care about a handful of types, and we can quite easily use the GUdev data to build up a profile for each device type, falling back if the device is unknown. I think it would be very useful to make Munki-specific data, as long as we have good fallbacks for the devices people keep secret. Richard. From hughsient at gmail.com Fri Feb 12 08:57:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 08:57:26 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> Message-ID: <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> On 11 February 2010 18:31, Pascal de Bruijn > But it's even worse, I screwed up the image as well... Here's a replacement. Applied, thanks. Do you want me to arrange for you to get GNOME commit access? It would mean you can commit this sort of thing without asking? Richard. From pedro at pedrocr.net Fri Feb 12 10:42:17 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:42:17 -0800 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> Message-ID: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: > Your hack was pretty cool, but it's not really handy to implement as a > generic solution for GCM, we need no fuss solutions. We will surely need a default mode that does that but my experience with doing it like you do bellow is that 200 patches isn't really reasonable. With the default settings you need 2 Letter pages to do ~190 and that generates pretty useless profiles. So to do the ~450+900 patches I ended up using for a decent profile you'd need ~15 pages which is a terrible waste of paper and ink. Like Richard says, it would be great to have the profiling instruments defined in a config somewhere, so that one can define a "Munki" and a "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" UI probably makes sense too as people doing color profiling would tend to be advanced users. > This works very well for me... and would be a great default for medium quality: > ?argyll-targen -v -d2 -f 210 xxx I ended up only getting good results at 450+900 patches. I suppose lower than that could also work. This should probably be given as an option to the user. Maybe a slider with markings or poor - basic - good - great and an automatic calculation of how many pages it is going to print, so that the user can do the tradeoff himself. > ?printtarg -v -i CM -h -T 300 -p A4 xxx My hack uses "-i i1". I haven't used the -T one. What does increasing the resolution help with? > ?colprof -q m -a l xxx "-a l" is default and I had also "-c mt" and "-d pp". Maybe they are not really needed. Cheers, Pedro From pedro at pedrocr.net Fri Feb 12 10:54:55 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 12 Feb 2010 02:54:55 -0800 Subject: Building a library of ICC profiles Message-ID: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Hi, Is there any package that collects free (as in speech) ICC profiles? I see that Pascal's PPA has one printer, one camera and two or three displays. Are these just the ones you did yourself Pascal? I'd be more than happy to add the profiles I've been doing for the printer and monitor to some repository so that users without a calibration instrument can just use a profile from the library. I already have profiles for a Dell U2410 and an Epson R2880 with Glossy Epson paper. I'll be adding more papers to that too. One thing I haven't done yet is profiling my camera. How is that done and what is the benefit? I have a Sony A700 DSLR. Cheers, Pedro From hughsient at gmail.com Fri Feb 12 11:14:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:14:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> Message-ID: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> On 12 February 2010 10:54, Pedro C?rte-Real wrote: > Is there any package that collects free (as in speech) ICC profiles? I > see that Pascal's PPA has one printer, one camera and two or three > displays. Are these just the ones you did yourself Pascal? There's http://github.com/hughsie/shared-color-profiles which may be of interest to you. > I'd be more than happy to add the profiles I've been doing for the > printer and monitor to some repository so that users without a > calibration instrument can just use a profile from the library. I > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > Epson paper. I'll be adding more papers to that too. I'm not so sure submitting user-generated profiles makes so much sense, I mean, your Epson R2880 probably has a quite different response to my (hypothetical) Epson R2880. If people think this is a good idea, I'd be wiling to set something like this up, as lets face it, a profile that is 3% off correct is better than no profile at all. > One thing I > haven't done yet is profiling my camera. How is that done and what is > the benefit? I have a Sony A700 DSLR. That's something you really want to do. We probably want to add a whole load of text in the help file in how to do this (sunny day, etc) but using GCM the process itself should be pretty easy. Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:15:52 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:15:52 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> <4c2c37f91002112338y13c9f6f3s90b48100a0716bbf@mail.gmail.com> <62e8012c1002120242m29dfe726pcf8a35587bcfcafa@mail.gmail.com> Message-ID: <4c2c37f91002120315vc4ee9fcy7e31caaee1db3a4c@mail.gmail.com> On Fri, Feb 12, 2010 at 11:42 AM, Pedro C?rte-Real wrote: > On Thu, Feb 11, 2010 at 11:38 PM, Pascal de Bruijn wrote: >> Your hack was pretty cool, but it's not really handy to implement as a >> generic solution for GCM, we need no fuss solutions. > > We will surely need a default mode that does that but my experience > with doing it like you do bellow is that 200 patches isn't really > reasonable. With the default settings you need 2 Letter pages to do > ~190 and that generates pretty useless profiles. So to do the ~450+900 > patches I ended up using for a decent profile you'd need ~15 pages > which is a terrible waste of paper and ink. > > Like Richard says, it would be great to have the profiling instruments > defined in a config somewhere, so that one can define a "Munki" and a > "Pimped-out Munki". Exposing the argyll config flags in an "Advanced" > UI probably makes sense too as people doing color profiling would tend > to be advanced users. > >> This works very well for me... and would be a great default for medium quality: >> ?argyll-targen -v -d2 -f 210 xxx > > I ended up only getting good results at 450+900 patches. I suppose > lower than that could also work. This should probably be given as an > option to the user. Maybe a slider with markings or poor - basic - > good - great and an automatic calculation of how many pages it is > going to print, so that the user can do the tradeoff himself. Highly depends on what kind of accuracy ones expects... 210 patches and -qm works reasonably well... I actually tried making a profile using 840 patches, and -qh, and I don't see a big difference here... Though my printer is much crappier than yours. >> ?printtarg -v -i CM -h -T 300 -p A4 xxx Anyway, patches count should most likely always be multiple of what a single sheet can hold... 1x A4 -> 210 2x A4 -> 420 3x A4 -> 630 4x A4 -> 840 This may be different for letter (190?). > My hack uses "-i i1". I haven't used the -T one. What does increasing > the resolution help with? This is seriously not an option for GCM... requiring users to make their own DIY patch reading guide. The colorimeter/spectrophotometer should work as develivered by the manufacturer... GNOME is about making things work as expected... not requiring DIY hobbying/hacks... For these kinds of strategies, using the Argyll commandline tools should be fine. Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:20:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:20:27 +0000 Subject: Adding a libtiff dep? Message-ID: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to add a libtiff hard dep on gnome-color-manager. All distros should already be installing this by default, but I wanted to check to see if anyone had any issue with this. Speak now, or forever hold your peace! :-) Thanks, Richard. From pmjdebruijn at pcode.nl Fri Feb 12 11:22:46 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:22:46 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: >> Is there any package that collects free (as in speech) ICC profiles? I >> see that Pascal's PPA has one printer, one camera and two or three >> displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. Those profiles are mostly for my private use... The camera profiles are probably generally usable though... >> I'd be more than happy to add the profiles I've been doing for the >> printer and monitor to some repository so that users without a >> calibration instrument can just use a profile from the library. I >> already have profiles for a Dell U2410 and an Epson R2880 with Glossy >> Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. One big problem with printer profiles are driver setttings, since profiles are also very specific to driver settings... I have no clue on how to solve that... Ideally you'd want the printer settings to be embedded in the profile. > If people think this is a good idea, I'd be wiling to set something > like this up, as lets face it, a profile that is 3% off correct is > better than no profile at all. Yeah sortof... >> One thing I >> haven't done yet is profiling my camera. How is that done and what is >> the benefit? I have a Sony A700 DSLR. > > That's something you really want to do. We probably want to add a > whole load of text in the help file in how to do this (sunny day, etc) > but using GCM the process itself should be pretty easy. I wrote about this here: http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Though the article is dated, and should be revised... I did make a few new discoveries... For example, I only recently noticed that strobes actually work well as reference light for generic profiles... I'm probably going to do a new blog post over the weekend... Here are some generic tips van raw photography with UFRaw in general: http://blog.pcode.nl/2009/08/23/ufraw-faq/ Most of it should apply to other dcraw based applications as well. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Fri Feb 12 11:24:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 12:24:10 +0100 Subject: Adding a libtiff dep? In-Reply-To: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> Message-ID: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> On Fri, Feb 12, 2010 at 12:20 PM, Richard Hughes wrote: > To fix https://bugzilla.gnome.org/show_bug.cgi?id=609444, I need to > add a libtiff hard dep on gnome-color-manager. All distros should > already be installing this by default, but I wanted to check to see if > anyone had any issue with this. > > Speak now, or forever hold your peace! :-) Seems fine... Doesn't eog already depend on libtiff anyway? Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 11:26:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:26:28 +0000 Subject: Adding a libtiff dep? In-Reply-To: <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> References: <15e53e181002120320r68e510adw2dfe43b6b4717d02@mail.gmail.com> <4c2c37f91002120324v2e67aeay84081f4459a194e9@mail.gmail.com> Message-ID: <15e53e181002120326q1d693e40wa44d44ab56c5efe0@mail.gmail.com> On 12 February 2010 11:24, Pascal de Bruijn wrote: > Seems fine... Doesn't eog already depend on libtiff anyway? Sure, but eog might not be installed on the live-cd, and g-c-m probably should... Richard. From hughsient at gmail.com Fri Feb 12 11:28:54 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 11:28:54 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> On 12 February 2010 11:22, Pascal de Bruijn wrote: > I wrote about this here: > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ Yes, this entry is very helpful, and I would love to see a large chunk added to the GNOME Color Manager help pages, if you're okay with re-licensing the content. Richard. From dan at berrange.com Fri Feb 12 11:30:51 2010 From: dan at berrange.com (Daniel P. Berrange) Date: Fri, 12 Feb 2010 11:30:51 +0000 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> Message-ID: <20100212113051.GA13638@berrange.com> On Fri, Feb 12, 2010 at 11:14:51AM +0000, Richard Hughes wrote: > On 12 February 2010 10:54, Pedro C?rte-Real wrote: > > Is there any package that collects free (as in speech) ICC profiles? I > > see that Pascal's PPA has one printer, one camera and two or three > > displays. Are these just the ones you did yourself Pascal? > > There's http://github.com/hughsie/shared-color-profiles which may be > of interest to you. > > > I'd be more than happy to add the profiles I've been doing for the > > printer and monitor to some repository so that users without a > > calibration instrument can just use a profile from the library. I > > already have profiles for a Dell U2410 and an Epson R2880 with Glossy > > Epson paper. I'll be adding more papers to that too. > > I'm not so sure submitting user-generated profiles makes so much > sense, I mean, your Epson R2880 probably has a quite different > response to my (hypothetical) Epson R2880. IIUC, printer profiles will vary on the set (hardware, ink, driver, paper) so building a library of profiles is quite large task. You could make it more managable by initially concentrating on the printer manufacturer's own recommended brand/combination of ink+paper+drivers Regards, Daniel -- |: http://berrange.com/ -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://freshmeat.net/~danielpb/ -o- http://gtk-vnc.sourceforge.net :| From pmjdebruijn at pcode.nl Fri Feb 12 12:01:33 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 13:01:33 +0100 Subject: Building a library of ICC profiles In-Reply-To: <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> Message-ID: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> On Fri, Feb 12, 2010 at 12:28 PM, Richard Hughes wrote: > On 12 February 2010 11:22, Pascal de Bruijn wrote: >> I wrote about this here: >> ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Yes, this entry is very helpful, and I would love to see a large chunk > added to the GNOME Color Manager help pages, if you're okay with > re-licensing the content. No problem, but I'd like my rewrite to be in the help pages :) Not this particular article... Regards, Pascal de Bruijn From hughsient at gmail.com Fri Feb 12 12:09:23 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 12:09:23 +0000 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <15e53e181002120328y7b6b36c9k423e77b23bc8fc51@mail.gmail.com> <4c2c37f91002120401x52808edal9a87b47d8a1eaa55@mail.gmail.com> Message-ID: <15e53e181002120409veeecbbcn1f4a04d55b353beb@mail.gmail.com> On 12 February 2010 12:01, Pascal de Bruijn wrote: > No problem, but I'd like my rewrite to be in the help pages :) Cool. Just add text to help/C/gnome-color-manager.xml and format a patch as normal. If you get stuck with docbook, give me a shout. Richard. From alexandre.prokoudine at gmail.com Fri Feb 12 12:54:08 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Fri, 12 Feb 2010 15:54:08 +0300 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> References: <1265832096.26568.43.camel@athlon> <733f2c731002111130r1995f23er96d0b22b9276b588@mail.gmail.com> <4c2c37f91002111244q6a99e26axe75879ca1f567ca5@mail.gmail.com> <62e8012c1002111742w170b09acs1a9d1b68fdfc52e2@mail.gmail.com> Message-ID: <733f2c731002120454p2f0143ddgf9dfe37e4b9a3713@mail.gmail.com> On Fri, Feb 12, 2010 at 4:42 AM, Pedro C?rte-Real wrote: > Just paypalled mine as well. Doesn't any of the Linux/FreeSoftware > organizations do this in scale? http://linuxfund.org/ Alexandre From hughsient at gmail.com Fri Feb 12 15:10:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 12 Feb 2010 15:10:10 +0000 Subject: Color correcting projectors? Message-ID: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> In GCM we currently support two types of display profiling. Internal (LVDS) panels are internal to the system, and external panels (DVI and the others) are external to the system. What different settings do we need to do for projectors? We certainly need to give different instructions (which we also need to write), but will argyll just process these like a low-gamut LCD screen? Are there any options we need to add? Richard. From pmjdebruijn at pcode.nl Fri Feb 12 15:25:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 16:25:50 +0100 Subject: Color correcting projectors? In-Reply-To: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> Message-ID: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> On Fri, Feb 12, 2010 at 4:10 PM, Richard Hughes wrote: > In GCM we currently support two types of display profiling. Internal > (LVDS) panels are internal to the system, and external panels (DVI and > the others) are external to the system. > > What different settings do we need to do for projectors? We certainly > need to give different instructions (which we also need to write), but > will argyll just process these like a low-gamut LCD screen? Are there > any options we need to add? Well I think Argyll has a -p option :) And the instructions obviously need to be different, there's a "rule" which states the colorimeter should be 1.5 times the height of the projected image away from the "screen", or something like that... Regards, Pascal de Bruijn From knizek.confy at volny.cz Fri Feb 12 20:28:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Fri, 12 Feb 2010 21:28:14 +0100 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265882045.4190.8.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> Message-ID: <1266006494.22377.14.camel@athlon> Paul Finnigan p??e v ?t 11. 02. 2010 v 09:54 +0000: > I am a photographer who likes to keep up with the Jones' (MS/Apple). To > do this while running Linux I have had to make compromise after > compromise with regard to 'Free' software. This is my own choice and I > am not complaining about it. Paul said it well, it fits my experience. I had to learn a lot of things to be able to use Linux for my photographic hobby and I hope that soon the photographer's life with Linux be more user friendly. > To get the ball rolling we need to set up an account. I am willing to > let Richard have my $50 even if we do not reach the target of $500. If > Richard or anyone else would like to mail me directly my address is paul > at fincc dot com. I have given ?100, maybe a bit more than usual but anyway I hope Richard will not feel obliged to prefer my wishes about GCM - it is a donation, not a wage. Also, no need to return if the target is not reached. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From pmjdebruijn at pcode.nl Fri Feb 12 22:00:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Fri, 12 Feb 2010 23:00:20 +0100 Subject: Perspective Distortion Compensation Message-ID: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Hi, Currently input profile calibration can fail because a target has even the slightest perspective distortion. Argyll can compensate for that within reason. This patch should enable perspective distortion compensation. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-have-scanin-compensate-for-perspective-distortion.patch Type: text/x-patch Size: 911 bytes Desc: not available URL: From paul at fincc.com Sat Feb 13 01:16:32 2010 From: paul at fincc.com (Paul Finnigan) Date: Sat, 13 Feb 2010 01:16:32 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266006494.22377.14.camel@athlon> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> Message-ID: <1266023792.2313.21.camel@localhost> Milan On Fri, 2010-02-12 at 21:28 +0100, Milan Kn??ek wrote: > I have given ?100, maybe a bit more than usual but anyway I hope Richard > will not feel obliged to prefer my wishes about GCM - it is a donation, > not a wage. Also, no need to return if the target is not reached. What a nice way of putting it! It sounds like you are used to being part of a community, rather than a gathering of geeks. It is amazing but through everyone's (OK in the main Richard's) efforts I feel part of this community without putting anything in myself (I am still attempting to get setup in paypal. I am ancient and not used to money being passed over the ether. Don't worry Richard I will put my money where my mouth is as soon as I can get money into paypal). Thanks to this project I have found many new friends. How can I help? Richard has suggested people to write the help documentation. I am willing but what format and how? Is there a howto I can read anywhere that would help? I am desperate to do more but my skills are in the area of project and service management not coding. -- Paul Finnigan From graeme2 at argyllcms.com Sat Feb 13 01:17:23 2010 From: graeme2 at argyllcms.com (Graeme Gill) Date: Sat, 13 Feb 2010 12:17:23 +1100 Subject: Color correcting projectors? In-Reply-To: <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> References: <15e53e181002120710ua82ff96s57478766c1442c44@mail.gmail.com> <4c2c37f91002120725j19b408afh79c55b9e7ee95c61@mail.gmail.com> Message-ID: <4B75FDA3.9050601@argyllcms.com> Pascal de Bruijn wrote: > Well I think Argyll has a -p option :) -p is an instrument config. option, and is currently only applicable to a single instrument, the ColorMunki. You can use other instruments to measure projectors, but they don't have a special mode for it. (I think I'll changed dispcal and dispread to automatically fallback to display mode if the instrument doesn't have a projector mode, to make them a bit more forgiving). Graeme Gill. From hughsient at gmail.com Sat Feb 13 09:17:06 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:17:06 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1266023792.2313.21.camel@localhost> References: <1265832096.26568.43.camel@athlon> <1265882045.4190.8.camel@localhost> <1266006494.22377.14.camel@athlon> <1266023792.2313.21.camel@localhost> Message-ID: <15e53e181002130117s270af2b9kcc97bc7ef471c82@mail.gmail.com> On 13 February 2010 01:16, Paul Finnigan wrote: > What a nice way of putting it! It sounds like you are used to being part > of a community, rather than a gathering of geeks. It is amazing but > through everyone's (OK in the main Richard's) efforts I feel part of > this community without putting anything in myself (I am still attempting > to get setup in paypal. I am ancient and not used to money being passed > over the ether. Don't worry Richard I will put my money where my mouth > is as soon as I can get money into paypal). We've very nearly reached the total! I'm nearly at the "amount I can sneak on the shared credit card without the wife noticing" stage :-) > Thanks to this project I have found many new friends. How can I help? > Richard has suggested people to write the help documentation. I am > willing but what format and how? Is there a howto I can read anywhere > that would help? I am desperate to do more but my skills are in the area > of project and service management not coding. Right, then we need to start with some documentation or UI fixes, and then work on from there. My spelling and grammar are notoriously bad, so this is where I need the most help. If you first: * download the git package (using yum, apt-get, or your distro tool) * "clone" the developers checkout. For this you want to follow http://live.gnome.org/Git/Developers -- specifically the project name is gnome-color-manager (you can also ignore 90% of that page, it's overly complicated, but maybe a good read if you want detail) * create you're own personal branch (not on the server): git checkout -b my-playground-branch * Edit the file help/C/gnome-color-manager.xml, copying the syntax (e.g. using for a new paragraph), making the changes you want * "commit" the changes, which basically means you save them, and give them a description: git commit -a -m "Correct the spelling of Colour to Color" --author "Richard Hughes " * get a text file of the changes you want to send to us: "git format-patch master" (this generates 0001-a-file-with-a-peculiar-name.patch) Send the 0001-a-file-with-a-peculiar-name.patch as an attachment to this mailing list. Then you can either go back to the pristine upstream tree "git checkout master" or stay on your private tree and make more changes. You can commit many small changes and then do "git format-patch" and you get files 0001, 0002, 0003, 0004, etc and send them all in one long email. If you break stuff, then you can get rid of all your changes (since the last time you committed them) with "git reset --hard", and you can ensure you've got the latest changes from upstream by doing "git checkout master && git pull --rebase" It sounds complicated, but give it a try and yell when you get stuck. Weekdays I'm on IRC if that helps. Richard. From hughsient at gmail.com Sat Feb 13 09:19:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 09:19:58 +0000 Subject: Perspective Distortion Compensation In-Reply-To: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> References: <4c2c37f91002121400j7e9a6917y2a1b360e30ce7f03@mail.gmail.com> Message-ID: <15e53e181002130119k4b3d9a16j403ff3c4aa2f4c31@mail.gmail.com> On 12 February 2010 22:00, Pascal de Bruijn wrote: > This patch should enable perspective distortion compensation. Applied, thanks. Richard. From pmjdebruijn at pcode.nl Sat Feb 13 10:43:44 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 11:43:44 +0100 Subject: Bug #605259: Colorimeter name in profile description Message-ID: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Hi, Currently on my Ubuntu Karmic system, the colorimeter name still isn't getting into the profile description... Could you give me any pointer how the colorimeter is resolved? And where I should look into the sources? Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 14:09:51 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 14:09:51 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> Message-ID: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> On 13 February 2010 10:43, Pascal de Bruijn wrote: > Currently on my Ubuntu Karmic system, the colorimeter name still isn't > getting into the profile description... Hmm, I'm getting "Huey" prepended to my profile. > Could you give me any pointer how the colorimeter is resolved? And > where I should look into the sources? Well, take a look at src/gcm-color-device.c and make sure that the model and vendor are being set correctly. It's possible you need to add: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="usb-db %p" to your 55-Argyll.rules file, if your device doesn't have an entry in the kernel USB driver. That's what I've done in hargyll, and if it fixes it for you too, I'll push this patch to Graeme. Richard From pmjdebruijn at pcode.nl Sat Feb 13 19:40:24 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 13 Feb 2010 20:40:24 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> Message-ID: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> On Fri, Feb 12, 2010 at 12:22 PM, Pascal de Bruijn wrote: > On Fri, Feb 12, 2010 at 12:14 PM, Richard Hughes wrote: >> On 12 February 2010 10:54, Pedro C?rte-Real wrote: >>> One thing I >>> haven't done yet is profiling my camera. How is that done and what is >>> the benefit? I have a Sony A700 DSLR. >> >> That's something you really want to do. We probably want to add a >> whole load of text in the help file in how to do this (sunny day, etc) >> but using GCM the process itself should be pretty easy. > > I wrote about this here: > > ?http://blog.pcode.nl/2008/11/15/color-profiling-your-own-dslr-redux/ > > Though the article is dated, and should be revised... I did make a few > new discoveries... > > For example, I only recently noticed that strobes actually work well > as reference light for generic profiles... > > I'm probably going to do a new blog post over the weekend... > > Here are some generic tips van raw photography with UFRaw in general: > > ?http://blog.pcode.nl/2009/08/23/ufraw-faq/ > > Most of it should apply to other dcraw based applications as well. I'm rewriting my article as I type this, it should already be accessible as a preview: http://blog.pcode.nl/?p=551&preview=true Any comments before I publish? Any thing not clear? If all goes well (I still need to do some more testing), this article can be reworked into GCM help. Regards, Pascal de Bruijn From hughsient at gmail.com Sat Feb 13 21:27:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 13 Feb 2010 21:27:34 +0000 Subject: Looking for supporters to provide Richard H with ColorMunki Photo In-Reply-To: <1265832096.26568.43.camel@athlon> References: <1265832096.26568.43.camel@athlon> Message-ID: <15e53e181002131327l76d8dc0du282ca3c5a5be4423@mail.gmail.com> On 10 February 2010 20:01, Milan Kn??ek wrote: > On Richard's blog, Paul Finnigan proposed a donation from users - the > ColorMunki Photo costs about USD 300 in the U.S. and more then USD 500 > in the U.K., were Richard lives. We've reached the total! Thanks guys, I feel very humbled. Thanks. ColorMunki Photo is ordered, and will arrive in about a weeks time. Richard. From hughsient at gmail.com Sun Feb 14 20:56:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sun, 14 Feb 2010 20:56:10 +0000 Subject: Request for colorimeter figures Message-ID: <15e53e181002141256t1c39960dle71b65839ca6d451@mail.gmail.com> Hey guys, I've added support to GCM today to display images to help the user attach the colorimeter device to the screen, and to set it to correct mode. I've attached two images as examples. If anybody is interested in drawing pictures (or improving mine) it would be very welcome. I don't mind how many images we add. Ideally we should show images of the most common colorimeters in existence, and how to switch things to the correct modes. You'll have to create SVG figures yourself (I used inkscape) and obviously not include any trademarks. If you're a worse artist than me, feel free to send a photo of the colorimeter attached to the screen, and switching between different modes and one of us geeks on list can convert this to a SVG. Thanks. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: huey-attach.svg Type: image/svg+xml Size: 61010 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: munki-projector.svg Type: image/svg+xml Size: 66407 bytes Desc: not available URL: From pmjdebruijn at pcode.nl Mon Feb 15 01:23:01 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 02:23:01 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> Message-ID: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> On Sat, Feb 13, 2010 at 3:09 PM, Richard Hughes wrote: > On 13 February 2010 10:43, Pascal de Bruijn wrote: >> Currently on my Ubuntu Karmic system, the colorimeter name still isn't >> getting into the profile description... > > Hmm, I'm getting "Huey" prepended to my profile. > >> Could you give me any pointer how the colorimeter is resolved? And >> where I should look into the sources? > > Well, take a look at src/gcm-color-device.c and make sure that the > model and vendor are being set correctly. It's possible you need to > add: > > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="usb-db %p" > > to your 55-Argyll.rules file, if your device doesn't have an entry in > the kernel USB driver. That's what I've done in hargyll, and if it > fixes it for you too, I'll push this patch to Graeme. It's not fixing it for me now... But I don't think I have the usb-db utility installed... Where should I have gotten it from? Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 11:34:49 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 11:34:49 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> Message-ID: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> On 15 February 2010 01:23, Pascal de Bruijn wrote: > It's not fixing it for me now... But I don't think I have the usb-db > utility installed... Where should I have gotten it from? Any modern udev should have it. Use "udevadm monitor" to monitor the device events as the device is plugged in. Richard. From pmjdebruijn at pcode.nl Mon Feb 15 11:36:12 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 15 Feb 2010 12:36:12 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> Message-ID: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: > On 15 February 2010 01:23, Pascal de Bruijn wrote: >> It's not fixing it for me now... But I don't think I have the usb-db >> utility installed... Where should I have gotten it from? > > Any modern udev should have it. Use "udevadm monitor" to monitor the > device events as the device is plugged in. Indeed $ dpkg -L udev | grep usb-db /lib/udev/usb-db But it's not in my path, I'm not sure whether that matters? I'll try udev monitor later today. Regards, Pascal de Bruijn From hughsient at gmail.com Mon Feb 15 20:34:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 20:34:26 +0000 Subject: Adding support for xsane Message-ID: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> I've coded some initial support for xsane-based application in a private branch. It basically writes the right thing in the per-user xsane directories for the system and device settings. I'm not sure whether to merge it to master or not, as it's pretty hacky code. Ideally we would talk to easy-scan / gnome-scan in the future using a nice DBus interface, but I think that's a few years away. It does not depend on sane (that's a separate branch...) and if you don't use xsane then the file just gets written and nothing uses it. So, what do you guys think? Richard. From knizek.confy at volny.cz Mon Feb 15 21:19:05 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 15 Feb 2010 22:19:05 +0100 Subject: Building a library of ICC profiles In-Reply-To: <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> References: <62e8012c1002120254x52dc013dm7dbf06860e814057@mail.gmail.com> <15e53e181002120314q5d1790f8nd296df1cf74c70a9@mail.gmail.com> <4c2c37f91002120322n6a3494a7ib9017edd0e44714a@mail.gmail.com> <4c2c37f91002131140w3eb8c218h1e2fced85be786a8@mail.gmail.com> Message-ID: <1266268745.6707.9.camel@athlon> Pascal de Bruijn p??e v So 13. 02. 2010 v 20:40 +0100: > I'm rewriting my article as I type this, it should already be > accessible as a preview: > > http://blog.pcode.nl/?p=551&preview=true > > Any comments before I publish? Any thing not clear? > Pascal - the page is "not found". I guess you would actually have to post it to make it available to public. regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 15 22:09:10 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 16 Feb 2010 01:09:10 +0300 Subject: Adding support for xsane In-Reply-To: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> Message-ID: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> On 2/15/10, Richard Hughes wrote: > Ideally we would talk to easy-scan / gnome-scan in the future using a > nice DBus interface, but I think that's a few years away. Robert Ancell blogged recently that he is going to implement color management after 1.0, and his is now in post 0.9.0 bugfixing mode. So it's probably not that bad :) Alexandre From hughsient at gmail.com Mon Feb 15 22:16:56 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 15 Feb 2010 22:16:56 +0000 Subject: Adding support for xsane In-Reply-To: <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> References: <15e53e181002151234w5c00853ek428029680b57440a@mail.gmail.com> <733f2c731002151409y5f4a5152u58d64f4077ed4796@mail.gmail.com> Message-ID: <15e53e181002151416p37413a9je110eab793646198@mail.gmail.com> On 15 February 2010 22:09, Alexandre Prokoudine wrote: > Robert Ancell blogged recently that he is going to implement color > management after 1.0, and his is now in post 0.9.0 bugfixing mode. So > it's probably not that bad :) Cool. What we need him to do is: * Provide a method to scan a target without applying any icc profiles at all, so we can use it to calibrate the device. * Get the default icc profile assigned by GCM using the udev path or the SANE id, for normal scans. * Tag the resulting scans with the assigned ICC profile Should be no more than an afternoons hacking :-) Richard. From paul at fincc.com Tue Feb 16 00:45:54 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 00:45:54 +0000 Subject: Camera Support Message-ID: <1266281154.2768.8.camel@localhost> Hi I decided to attempt to use a profile with my camera. The camera does not appear on the list of devices, even when it is plugged in. Am I missing something? I can import my profiles but I cannot assign them to a device. The camera is a Nikon D700. Gnome recognises the camera and allows me to open a nautilus viewer on the memory card, open photographs etc. I can see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b0 ProdID=0422 Rev= 1.00 S: Manufacturer=NIKON S: Product=NIKON DSC D700 S: SerialNumber=000002034583 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=usbfs E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms If I run gcm in verbose mode: TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 - uevent add TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 TI:00:40:13 FI:gcm-profile-store.c FN:gcm_profile_store_add_profiles_from_mounted_volume,336 - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 has type gphoto2 So we see the camera connect. Am I missing something? I am running off a copy from the GIT -- Paul Finnigan Finnigan Computer Consultants Ltd. From hughsient at gmail.com Tue Feb 16 09:26:26 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 09:26:26 +0000 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> On 16 February 2010 00:45, Paul Finnigan wrote: > If I run gcm in verbose mode: > > TI:00:40:05 FI:gcm-colorimeter.c ? ? ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:05 ? ? FI:gcm-colorimeter.c ? ?FN:gcm_prefs_uevent_cb,319 > ?- uevent add > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > TI:00:40:13 ? ? FI:gcm-profile-store.c > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > ?- filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > has type gphoto2 > > So we see the camera connect. Am I missing something? Is that all you get when you connect the camera? Could you attach the output from "udevadm monitor" when you plug in the device please. I'm a little surprised it doesn't work, given my D60 works fine. Thanks. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 11:54:27 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 12:54:27 +0100 Subject: Camera Support In-Reply-To: <1266281154.2768.8.camel@localhost> References: <1266281154.2768.8.camel@localhost> Message-ID: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > Hi > > I decided to attempt to use a profile with my camera. The camera does > not appear on the list of devices, even when it is plugged in. Am I > missing something? I can import my profiles but I cannot assign them to > a device. Currently assigning camera profiles in GCM has no real function yet, since the RAW converters don't use this information. > The camera is a Nikon D700. Gnome recognises the camera and allows me to > open a nautilus viewer on the memory card, open photographs etc. I can > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > snip snip > > So we see the camera connect. Am I missing something? > > I am running off a copy from the GIT It works just fine with my EOS 400D as well... Also does your D700 have a recent firmware? Regards, Pascal de Bruijn From paul at fincc.com Tue Feb 16 11:57:31 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 11:57:31 +0000 Subject: Camera Support In-Reply-To: <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <15e53e181002160126y7cec8304n96d1d1de3bf1cde9@mail.gmail.com> Message-ID: <1266321451.6701.12.camel@localhost> Richard On Tue, 2010-02-16 at 09:26 +0000, Richard Hughes wrote: > On 16 February 2010 00:45, Paul Finnigan wrote: > > If I run gcm in verbose mode: > > > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:05 FI:gcm-colorimeter.c FN:gcm_prefs_uevent_cb,319 > > - uevent add > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > TI:00:40:13 FI:gcm-profile-store.c > > FN:gcm_profile_store_add_profiles_from_mounted_volume,336 > > - filesystem mounted on /home/paul/.gvfs/gphoto2 mount on usb%3A001,005 > > has type gphoto2 > > > > So we see the camera connect. Am I missing something? > > Is that all you get when you connect the camera? Could you attach the > output from "udevadm monitor" when you plug in the device please. I'm > a little surprised it doesn't work, given my D60 works fine. Thanks. > > Richard. That is all I get from gcm. I am running Fedora 12 and have compiled gcm from the GIT. I only ever connect my camera to copy files to disc. I never ever read them directly with an application, or not in my normal workflow. That is I only use my Nikon as a (very expensive) memory stick! OK Fedora uses gphoto2 and gvfs. As requested 'udevadm moniotor' when connecting the camera gives: [paul at ewing ~]udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266321215.801858] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) KERNEL[1266321215.802262] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) UDEV [1266321215.813200] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5 (usb) UDEV [1266321215.821229] add /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0 (usb) Nautilus then lets me view photos using: gphoto2://[usb:001,009]/DCIM/100ND700 Thanks -- Paul Finnigan From paul at fincc.com Tue Feb 16 12:19:26 2010 From: paul at fincc.com (Paul Finnigan) Date: Tue, 16 Feb 2010 12:19:26 +0000 Subject: Camera Support In-Reply-To: <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> References: <1266281154.2768.8.camel@localhost> <4c2c37f91002160354x1578c343p5546f589cf6aeb01@mail.gmail.com> Message-ID: <1266322766.6701.21.camel@localhost> Pascal On Tue, 2010-02-16 at 12:54 +0100, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 1:45 AM, Paul Finnigan wrote: > > Hi > > > > I decided to attempt to use a profile with my camera. The camera does > > not appear on the list of devices, even when it is plugged in. Am I > > missing something? I can import my profiles but I cannot assign them to > > a device. > > Currently assigning camera profiles in GCM has no real function yet, > since the RAW converters don't use this information. I knew that, which is why I had not tired it until now. I am looking at the help pages as I had (stupidly) volunteered and wanted to show an input device on the menu. My current scanner a Canon Lide 500 does not work with Sane so I cannot show that. > > The camera is a Nikon D700. Gnome recognises the camera and allows me to > > open a nautilus viewer on the memory card, open photographs etc. I can > > see my camera if I do a lsusb and cat /proc/bus/usb/devices shows: > > > > snip snip > > > > > So we see the camera connect. Am I missing something? > > > > I am running off a copy from the GIT > > It works just fine with my EOS 400D as well... Also does your D700 > have a recent firmware? I would guess not. I have had it over 12 months, and have never had a need to update the firmware. If I need to I will update the firmware. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Tue Feb 16 12:29:45 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 13:29:45 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> Message-ID: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> On Mon, Feb 15, 2010 at 12:36 PM, Pascal de Bruijn wrote: > On Mon, Feb 15, 2010 at 12:34 PM, Richard Hughes wrote: >> On 15 February 2010 01:23, Pascal de Bruijn wrote: >>> It's not fixing it for me now... But I don't think I have the usb-db >>> utility installed... Where should I have gotten it from? >> >> Any modern udev should have it. Use "udevadm monitor" to monitor the >> device events as the device is plugged in. > > Indeed > > $ dpkg -L udev | grep usb-db > /lib/udev/usb-db > > But it's not in my path, I'm not sure whether that matters? I changed the udev-rule to include the full path of usb-db: # color calibration device ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", IMPORT{program}="/lib/udev/usb-db %p" Does this need to be in a particular place in 55-Argyll.rules? I attached the full file. After making the above change, I rebooted my system, and ran the udevadm monitor while plugging in the Huey. The results are attached. Regards, Pascal de Bruijn -------------- next part -------------- pmjdebruijn at biovore:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1266323110.972649] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323110.975186] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323111.064958] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323111.106596] add /module/usbhid (module) KERNEL[1266323111.108080] add /bus/hid/drivers/generic-usb (drivers) UDEV [1266323111.108125] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323111.108145] add /bus/usb/drivers/hiddev (drivers) KERNEL[1266323111.108161] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.108519] add /bus/usb/drivers/hiddev (drivers) UDEV [1266323111.108804] add /module/usbhid (module) UDEV [1266323111.109292] add /bus/usb/drivers/usbhid (drivers) UDEV [1266323111.110702] add /bus/hid/drivers/generic-usb (drivers) KERNEL[1266323117.762463] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) KERNEL[1266323117.762504] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323117.763909] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323117.766370] remove /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.321652] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) KERNEL[1266323121.328367] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) UDEV [1266323121.338002] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2 (usb) UDEV [1266323121.341140] add /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0 (usb) pmjdebruijn at biovore:~$ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG -------------- next part -------------- A non-text attachment was scrubbed... Name: 55-Argyll.rules Type: application/octet-stream Size: 1953 bytes Desc: not available URL: From hughsient at gmail.com Tue Feb 16 21:43:31 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 16 Feb 2010 21:43:31 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> Message-ID: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> On 16 February 2010 12:29, Pascal de Bruijn wrote: > # color calibration device > ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", > IMPORT{program}="/lib/udev/usb-db %p" Hmm, I don't think you need to include the full path this. > Does this need to be in a particular place in 55-Argyll.rules? I > attached the full file. > > After making the above change, I rebooted my system, and ran the > udevadm monitor while plugging in the Huey. The results are attached. Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I assume this is a Huey: 0971 Gretag-Macbeth AG 2005 Huey If it's not a Huey, then we have a problem, and we need to add an entry to usb.ids. See http://www.linux-usb.org/usb-ids.html if this is the case. Richard. From pmjdebruijn at pcode.nl Tue Feb 16 21:56:10 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 22:56:10 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> Message-ID: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: > On 16 February 2010 12:29, Pascal de Bruijn wrote: >> # color calibration device >> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >> IMPORT{program}="/lib/udev/usb-db %p" > > Hmm, I don't think you need to include the full path this. Well the other lines include full paths, it would seem good practice consistency-wise. >> Does this need to be in a particular place in 55-Argyll.rules? I >> attached the full file. >> >> After making the above change, I rebooted my system, and ran the >> udevadm monitor while plugging in the Huey. The results are attached. > > Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like > ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I > assume this is a Huey: > > 0971 ?Gretag-Macbeth AG > ? ? ? ?2005 ?Huey I updated the usb database, and guess what: $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG ID_MODEL_FROM_DATABASE=Huey Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:13:17 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:13:17 +0100 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <4c2c37f91002161413w182c491cu2f8a269bf6bd91c4@mail.gmail.com> On Tue, Feb 16, 2010 at 10:56 PM, Pascal de Bruijn wrote: > On Tue, Feb 16, 2010 at 10:43 PM, Richard Hughes wrote: >> On 16 February 2010 12:29, Pascal de Bruijn wrote: >>> # color calibration device >>> ENV{COLOR_MEASUREMENT_DEVICE}=="*?", ENV{ACL_MANAGE}="1", >>> IMPORT{program}="/lib/udev/usb-db %p" >> >> Hmm, I don't think you need to include the full path this. > > Well the other lines include full paths, it would seem good practice > consistency-wise. > >>> Does this need to be in a particular place in 55-Argyll.rules? I >>> attached the full file. >>> >>> After making the above change, I rebooted my system, and ran the >>> udevadm monitor while plugging in the Huey. The results are attached. >> >> Good, so ID_VENDOR_FROM_DATABASE is being set, but it looks like >> ID_MODEL_FROM_DATABASE isn't -- do you have an up to date usb.ids? I >> assume this is a Huey: >> >> 0971 ?Gretag-Macbeth AG >> ? ? ? ?2005 ?Huey > > I updated the usb database, and guess what: > > $ /lib/udev/usb-db /devices/pci0000:00/0000:00:1d.0/usb6/6-2 > ID_VENDOR_FROM_DATABASE=Gretag-Macbeth AG > ID_MODEL_FROM_DATABASE=Huey Ugh, I just calibrated my screen and it worked like a charm... Please push the udev rule to Graeme. Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 16 22:31:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 16 Feb 2010 23:31:38 +0100 Subject: [PATCH] New USB ID: X-Rite/Gretag-MacBeth ColorMunki Message-ID: <4c2c37f91002161431l7989a672gd240def3bbcf5a23@mail.gmail.com> Hi, The included patch has the USB ID for: http://www.colormunki.com/ The device is a spectrophotometer from X-Rite which recently acquired Gretag-Macbeth. I've tested using udev's usb-db, and the lookup works with my device. Regards, Pascal de Bruijn -------------- next part -------------- A non-text attachment was scrubbed... Name: usb-ids-colormunki.patch Type: text/x-patch Size: 312 bytes Desc: not available URL: From hughsient at gmail.com Wed Feb 17 09:33:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 09:33:21 +0000 Subject: Bug #605259: Colorimeter name in profile description In-Reply-To: <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> References: <4c2c37f91002130243o31efa952s3b1c3847fa6df24@mail.gmail.com> <15e53e181002130609p3e907051k18b750c071972047@mail.gmail.com> <4c2c37f91002141723s1ff90443ha5fc692dd3d2eac3@mail.gmail.com> <15e53e181002150334w1c64d25clf2f7fc6e19d8ce91@mail.gmail.com> <4c2c37f91002150336t46800a68n6c2a6044a2a78cac@mail.gmail.com> <4c2c37f91002160429u2e35099ag379acbfafd72178f@mail.gmail.com> <15e53e181002161343y16a80071ofe8b5aa7739b56d9@mail.gmail.com> <4c2c37f91002161356r775697acj25c71e353b867e08@mail.gmail.com> Message-ID: <15e53e181002170133j3c968710y4dc7996dc31bc5b@mail.gmail.com> On 16 February 2010 21:56, Pascal de Bruijn wrote: > Well the other lines include full paths, it would seem good practice > consistency-wise. I disagree, but it shouldn't hurt as even on 64 bit the early udev boot is in /lib, not /lib64. Richard. From hughsient at gmail.com Wed Feb 17 14:05:27 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 14:05:27 +0000 Subject: Adding printer profiling support Message-ID: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> In a few days time, my nice lovely ColorMunki should be delivered. Before it is, I figured I should get up to speed on how to profile printers, so we know what UI to add to GCM, and so I can get up to speed quickly. So. Does anybody have any hints, tips or suggestions on how to calibrate a printer. Device specific options (e.g. "The ColorMunki works really well with -f234 -g567") are more than welcome, as we already know the colorimeter device type. In particular, we need to support printing to 6x4 inch cards, A4 and letter paper. I would love to integrate this better with CUPS (using the GTK print dialog for instance) than what we can do on the command line. We'll also need scans of the patches sheets that we send out, so we can show the user _how_ to scan in the patches. We'll also probably need a timer for "waiting for the ink to dry" and that sort of thing. Ideas very welcome. Thanks, Richard. From hughsient at gmail.com Wed Feb 17 19:47:58 2010 From: hughsient at gmail.com (Richard Hughes) Date: Wed, 17 Feb 2010 19:47:58 +0000 Subject: Small thumbnails of targets In-Reply-To: <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <4c2c37f91002100917y7b8bc57aw42f72de1fc8bc266@mail.gmail.com> <15e53e181002101138r38bb552eoeae6956077db6d91@mail.gmail.com> <4c2c37f91002110238u35ad2082k2a6a3d178771694d@mail.gmail.com> <15e53e181002110253t24eb81dbx35781c55df27039f@mail.gmail.com> <4c2c37f91002111031n222927f3s83396d7fb313cf54@mail.gmail.com> <15e53e181002120057m7a2ba32fubae63b3f03075e04@mail.gmail.com> <4c2c37f91002170920u66661491u7b4a8dfe21712c9@mail.gmail.com> Message-ID: <15e53e181002171147u290e197fnfe1e857f62b6723a@mail.gmail.com> On 17 February 2010 17:20, Pascal de Bruijn wrote: > J?rg Rosenkranz privately submitted an image of the LaserSoftDCPro > target to me. The attached patch should make it available for GCM. Applied, thanks. Richard. From pedro at pedrocr.net Thu Feb 18 04:50:09 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Wed, 17 Feb 2010 20:50:09 -0800 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: > In a few days time, my nice lovely ColorMunki should be delivered. > Before it is, I figured I should get up to speed on how to profile > printers, so we know what UI to add to GCM, and so I can get up to > speed quickly. > > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Here is my experience with the Munki from my notes. I've used it successfully to both profile a Dell U2410 LCD screen and an Epson R2880. The LCD profiling should work already but I ended up using the tools directly because g-c-m was failing to interact correctly with the argyll tools when they asked to change the position of the device. I think this has been fixed but haven't checked. Anyway for the printing profiling my steps were: 1 - Generate a set of color patches $argyll-targen -f 900 -v -d2 -c -A.8 This gave good results in the end. I did a first round of profiling with 450 patches and that was used as BestPreviousProfile. For the first round it would be instead: $argyll-targen -f 450 -v -d2 In general the number of patches to create is a judgment call. I don't know how we can present this option to the user. Maybe doing the calculation in reverse and asking him how many sheets he is willing to print and scan and then giving him an idea of how good a profile that generates. To then actually generate the files to print: $ printtarg -t -v -iCM -pLetter "Letter" should obviously be changed to whatever paper the user wants to use. The -iCM generates normally sized patches for the Munki, which will require many sheets of paper to fit the 900 patches. See bellow for a discussion of the hack I did to avoid this. 2. Print out the patches I printed the resulting tiff files with PhotoPrint. I believe it uses Gutenprint directly to drive the printer and is the only solution I know right now that can actually apply the ICC profile when printing later. The important thing here is to set the Gutenprint setting "Color Correction" to "Uncorrected", and then any of the image settings for the setup being used (type of paper, resolution, dithering, etc). 3. Read back the patches $chartread Munki will need to first be set to the self calibrate position, then to the profiling position and then run through each of the patch lines in turn while pressing its button. chartread asks for each of the lines and will ask for them again if there is any error. The interface needs to expose this. The last version allows you to reread a patch line at will. I wonder if it would be possible to have some kind of idea of how good the reads were and advise the user to reread one of the lines if it is found to not be too good. 4. Generate the profile $ colprof -v -D"" -qm -S -cmt -dpp This runs by itself without problems. The specific flags are arguable of course. I'm curious as to how changing -q (quality) to high or ultra changes the profile. Some considerations: - Some decent automatic naming would be nice - Selecting the source profile would be nice too (defaulting to sRGB) and possibly allowing the user to later generate the same profile with another profile (e.g. AdobeRGB) as source might be useful. - All the colprof settings can be changed without running the process from the beginning again. I wonder if g-c-m should have the notion of "Profiling runs" from which several actual profiles can be created. This would solve the sRGB/AdobeRGB selection as well. - Colprof outputs a final result with the mean and maximum error of the profile. It would be great to give this result to the user in plain English. Telling him the profile is "Poor/Fair/Good/Excellent" or even a result out of 100. The generated profile works in PhotoPrint. I assume it would also work to transform an image before sending it to the general CUPS pipeline. In theory the generated profile is only valid for the specific set of settings used for the printer. In practice using the same profile on even a different but similar paper is probably better than none at all. And using it at a different resolution on the same paper may very well be decent as well. I have no idea. > In particular, we need to support printing to 6x4 inch cards, A4 and > letter paper. I would love to integrate this better with CUPS (using > the GTK print dialog for instance) than what we can do on the command > line. We'll also need scans of the patches sheets that we send out, so > we can show the user _how_ to scan in the patches. We'll also probably > need a timer for "waiting for the ink to dry" and that sort of thing. My only other comment about the process is that using the Munki with default size patches is an incredible waste of paper and ink. In the argyll mailing list someone pointed out some user's hack on dpreview so I built one myself: http://pedrocr.net/MunkiHelper.jpg I'm not in any way suggesting that users should be expected to build one of these but I would like to be able to configure g-c-m to have not only the configuration for the normal Color Munki but also this hack. The only difference is to change the -iCM flag to printtarg to the -ii1, making the patches much smaller (by printing a sheet as if it was for another instrument). I know Pascal disagrees though. I share the sentiment of wanting to make this as simple to the user as possible. However my experience with this is that if we don't allow the user to fiddle with some of the advanced settings, whenever he hits a speed bump the only option is to fall back on argyll command line tools and totally bypass g-c-m. That doesn't seem like much of a solution either. My suggestion would be to have a set of default settings for each of the supported instruments that work in a straightforward way and then an "Advanced..." button to go and customize the settings. Cheers, Pedro From hughsient at gmail.com Thu Feb 18 09:28:41 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 18 Feb 2010 09:28:41 +0000 Subject: gnome-color-management test day Message-ID: <15e53e181002180128p9c9e977g8619a1518f86afd7@mail.gmail.com> Guys, We've got a GNOME Color Management test day happening today: https://fedoraproject.org/wiki/Test_Day:2010-02-18_Color_management It's very Fedora-centric, but I'm guessing as most of the testing and bugs will be common between distros, I guess it makes you more than welcome to join in. I'll be in the #fedora-test-day channel (on freenode) all day, answering questions and fixing bugs. Thanks. Richard. From pmjdebruijn at pcode.nl Thu Feb 18 17:57:20 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 18 Feb 2010 18:57:20 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> Message-ID: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > On Wed, Feb 17, 2010 at 6:05 AM, Richard Hughes wrote: >> In a few days time, my nice lovely ColorMunki should be delivered. >> Before it is, I figured I should get up to speed on how to profile >> printers, so we know what UI to add to GCM, and so I can get up to >> speed quickly. >> >> So. Does anybody have any hints, tips or suggestions on how to >> calibrate a printer. Device specific options (e.g. "The ColorMunki >> works really well with -f234 -g567") are more than welcome, as we >> already know the colorimeter device type. > > Here is my experience with the Munki from my notes. I've used it > successfully to both profile a Dell U2410 LCD screen and an Epson > R2880. The LCD profiling should work already but I ended up using the > tools directly because g-c-m was failing to interact correctly with > the argyll tools when they asked to change the position of the device. > I think this has been fixed but haven't checked. I didn't have any such issues, so I guess this has been fixed for a while. > Anyway for the printing profiling my steps were: > > 1 - Generate a set of color patches > > $argyll-targen -f 900 -v -d2 -c -A.8 The -c option is very advanced, and requires a lot of logic in GCM in determining what the best previous profile actually was... Or it requires the user to select their best previous profile, and if they select the wrong profile (or GCM automatically selects the wrong profile) it all goes horribly wrong... So in the short run using preconditioning (-c) probably will do more harm than good... This could very well be reconsidered when GCM matures. The 900 patch count is probably way too high for default, since we don't want to waste 4 sheets of expensive paper _by default_. Especially since some packages of expensive paper come in per 10 sheets packages. We'd be wasting 40% :) Please remember the ColorMunki vendor software only uses 90 or so patches by default, so having 210/190 (1x A4/Letter) is a huge improvement... Thus far I've had excellent results using only 210 patches with no preconditioning, and it only requires a single sheet of paper. So I'd highly recommend to use this as default. Anything that requires more than a single sheet of paper should probably go in high quality/advanced mode... Also I'd recon we should not really talk about patch counts, but the amount of paper... For for A4 we would use 210/420/630/840/1050 patches, or for Letter 190/380/470/660? > To then actually generate the files to print: > > $ printtarg -t -v -iCM -pLetter printtarg has a -h option, which will generate smaller patches for the ColorMunki, which fits 210 patches onto A4 instead of 90 or so... This option basically shrinks the rows to a third size, so the ColorMunki is exactly as wide as 3 rows with the aperture exactly over the middle row. > 2. Print out the patches > > I printed the resulting tiff files with PhotoPrint. I believe it uses > Gutenprint directly to drive the printer and is the only solution I > know right now that can actually apply the ICC profile when printing > later. The important thing here is to set the Gutenprint setting > "Color Correction" to "Uncorrected", and then any of the image > settings for the setup being used (type of paper, resolution, > dithering, etc). Not everybody uses a gutenprint supported printer... :) It's basically possible to profile any application with any printer driver, as long as the app nor the printer driver do any dynamic transforms... Your case is very optimal... HPIJS for example does not have an uncorrected mode, but the output is static, so it can be profiled. I apply my printer profile in F-Spot, so I also used F-Spot to print my target images... In theory this should not be very relevant. > 3. Read back the patches > > $chartread > > Munki will need to first be set to the self calibrate position, then > to the profiling position and then run through each of the patch lines > in turn while pressing its button. chartread asks for each of the > lines and will ask for them again if there is any error. The interface > needs to expose this. The last version allows you to reread a patch > line at will. I wonder if it would be possible to have some kind of > idea of how good the reads were and advise the user to reread one of > the lines if it is found to not be too good. I don't think argyll does this yet... But it would be cool indeed... > 4. Generate the profile > > $ colprof -v -D"" -qm -S > -cmt -dpp Using -qm for 210 is an excellent default, but when we go into advanced mode with > 500 patches, we should probably use -qh. I've never used the -S -cmt -dpp options, so I highly doubt they are required... We shouldn't pass random arguments unless strongly indicated that we should. Otherwise we should trust Argyll's defaults... > This runs by itself without problems. The specific flags are arguable > of course. I'm curious as to how changing -q (quality) to high or > ultra changes the profile. Some considerations: Graeme highly discourages the ultra mode, in his words: ultra mode exists to prove that nothing above high is required. > - Some decent automatic naming would be nice > - Selecting the source profile would be nice too (defaulting to sRGB) > and possibly allowing the user to later generate the same profile with > another profile (e.g. AdobeRGB) as source might be useful. Huh? printer profiles usually use LAB as Profile Connection Space, this has nothing to do with sRGB/AdobeRGB. The pipeline: Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> printer native RGB/CMYK -> hpijs/gutenprint > - All the colprof settings can be changed without running the process > from the beginning again. I wonder if g-c-m should have the notion of > "Profiling runs" from which several actual profiles can be created. > This would solve the sRGB/AdobeRGB selection as well. I'd probably be against this too (at least for the short run). This will complicate the user interface (and GCM's codebase), and probably won't be used much by most people, so this is not in line with GNOME's goals. In the long run we could re-evaluate this... > - Colprof outputs a final result with the mean and maximum error of > the profile. It would be great to give this result to the user in > plain English. Telling him the profile is "Poor/Fair/Good/Excellent" > or even a result out of 100. That would be nice... I'd stick to Poor/Fair/Good/Excellent, everybody understands that. Though we need to be very careful about how we determine what is what. > The generated profile works in PhotoPrint. I assume it would also work > to transform an image before sending it to the general CUPS pipeline. > In theory the generated profile is only valid for the specific set of > settings used for the printer. In practice using the same profile on > even a different but similar paper is probably better than none at > all. And using it at a different resolution on the same paper may very > well be decent as well. I have no idea. > >> In particular, we need to support printing to 6x4 inch cards, A4 and >> letter paper. I would love to integrate this better with CUPS (using >> the GTK print dialog for instance) than what we can do on the command >> line. We'll also need scans of the patches sheets that we send out, so >> we can show the user _how_ to scan in the patches. We'll also probably >> need a timer for "waiting for the ink to dry" and that sort of thing. >From most sources I gather a minimum od 15 minutes of drying-time should be enough for most cases. > My only other comment about the process is that using the Munki with > default size patches is an incredible waste of paper and ink. In the > argyll mailing list someone pointed out some user's hack on dpreview > so I built one myself: > > http://pedrocr.net/MunkiHelper.jpg Are you actually aware of the -h option for printtarg? Graeme semi-solved this issue long ago... My current workflow is like this # argyll-targen -v -d 2 -g 20 -f 210 test # printtarg -v -i CM -h -t 300 -p A4 test # chartread -v test # colprof -v -A "bla" -M "bla" -D "bla" -C "bla" -a l -q m test Regards, Pascal de Bruijn From knizek.confy at volny.cz Thu Feb 18 18:46:34 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Thu, 18 Feb 2010 19:46:34 +0100 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> Message-ID: <1266518794.18345.36.camel@athlon> Pascal de Bruijn p??e v ?t 18. 02. 2010 v 18:57 +0100: > On Thu, Feb 18, 2010 at 5:50 AM, Pedro C?rte-Real wrote: > > - Selecting the source profile would be nice too (defaulting to sRGB) > > and possibly allowing the user to later generate the same profile with > > another profile (e.g. AdobeRGB) as source might be useful. > > Huh? printer profiles usually use LAB as Profile Connection Space, > this has nothing to do with sRGB/AdobeRGB. > > The pipeline: > Image (in sRGB) -> sRGB profile -> XYZ (-> LAB) -> printer profile -> > printer native RGB/CMYK -> hpijs/gutenprint It looks like Pedro was referring to -S option of colprof: Argyllcms docs quote [1]: -- Where the resulting profile will be used conventionally (ie. using collink -s, or cctiff or most other "dumb" CMMs) it is important to specify that gamut mapping should be computed for the output (B2A) perceptual and saturation tables. This is done by specifying a device profile as the parameter to the colprof -S flag. When you intend to create a "general use" profile, it can be a good technique to specify the source gamut as the opposite type of profile to that being created, i.e. if a printer profile is being created, specify a display profile (e.g. sRGB) as the source gamut. If a display profile is being created, then specify a printer profile as the source (e.g. SWOP). -- Argyllcms docs quote [2]: ... [Note that Shaper/Matrix profiles are always Colorimetric intent, since there is only a single transformation, and it does not have the necessary flexibility to accommodate gamut mapping.] ... So to construct the perceptual and saturation intent mapping tables, a source profile or source gamut needs to be specified, so that a gamut mapping can be constructed. -- [2] http://www.argyllcms.com/doc/Scenarios.html#PP5 [1] http://www.argyllcms.com/doc/iccgamutmapping.html I do not have much experience on this topic... regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Fri Feb 19 10:41:19 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 10:41:19 +0000 Subject: Help update Message-ID: <1266576079.2381.5.camel@localhost> Richard Attached is my first attempt to help. Sorry it has taken me so long but I had a lot of reading to do about Gnome documentation. I have only altered the Introduction and Usage sections. I will set about the other sections if this is acceptable. If anyone wants to tell me where I am going wrong then please do. I admit this little effort has made me realise just what Richard is doing! There is more to gcm than I expected. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Correct-help-Intro-and-Usage.patch Type: text/x-patch Size: 3064 bytes Desc: not available URL: From hughsient at gmail.com Fri Feb 19 11:02:43 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 11:02:43 +0000 Subject: Help update In-Reply-To: <1266576079.2381.5.camel@localhost> References: <1266576079.2381.5.camel@localhost> Message-ID: <15e53e181002190302r1ffa130ay22236854ce8574d3@mail.gmail.com> On 19 February 2010 10:41, Paul Finnigan wrote: > Attached is my first attempt to help. Sorry it has taken me so long but > I had a lot of reading to do about Gnome documentation. Sure, it takes a fair bit to get up to speed. > I have only altered the Introduction and Usage sections. I will set > about the other sections if this is acceptable. I've committed your patch, thanks. One thing to note (any maybe repair in your next patch :-) is the trailing whitespace issue. git doesn't like trailing whitespace (tabs and spaces at the end of the line) and highlights them in red. Could you please make sure future patches don't add more trailing whitespace please? Thanks. > If anyone wants to tell me where I am going wrong then please do. I > admit this little effort has made me realise just what Richard is doing! Heh. Thanks. > There is more to gcm than I expected. Sure, and it's getting bigger every day. To do the printer profiling properly I'm having to deal with print dialogs and rendering to random cairo surfaces. Both things that were not in the original scope for GCM... Anyway, keep up the good work. Thanks. Richard. From paul at fincc.com Fri Feb 19 12:48:30 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 12:48:30 +0000 Subject: Selecting Device Profiles Message-ID: <1266583710.2381.14.camel@localhost> Hi I was just looking at improving the preferences help page and I came across a small UI problem someone else may like to look at. If the device profile is not loaded you can select "Other profile..." this takes you to the profile install routine, via a Gnome file select window. That is good. But once the profile is installed I have to go back to the Color Profile selector and select it. I think what should happen is: 1. If the profile is good for the device it should be selected. 2. If the profile is not good for the device then a message should be issued and the device profile is unaltered. What should never happen is that the "Other profile" selection remains against the device. Another point is that for a new device the profile should be "None" rather than blank. This will keep it consistent with selecting None from the profile list. What does everyone else think? -- Paul Finnigan From hughsient at gmail.com Fri Feb 19 13:05:10 2010 From: hughsient at gmail.com (Richard Hughes) Date: Fri, 19 Feb 2010 13:05:10 +0000 Subject: Selecting Device Profiles In-Reply-To: <1266583710.2381.14.camel@localhost> References: <1266583710.2381.14.camel@localhost> Message-ID: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> On 19 February 2010 12:48, Paul Finnigan wrote: > If the device profile is not loaded you can select "Other profile..." > this takes you to the profile install routine, via a Gnome file select > window. That is good. But once the profile is installed I have to go > back to the Color Profile selector and select it. That's just a bug: commit 5c4731bce32ce55467449d793b6a508b48b09eda Author: Richard Hughes Date: Fri Feb 19 13:03:14 2010 +0000 trivial: Set the profile we chose as 'Other' as the current device default > I think what should happen is: > > 1. If the profile is good for the device it should be selected. Sure, agreed. > 2. If the profile is not good for the device then a message should be > issued and the device profile is unaltered. We need to add that. > What should never happen is that the "Other profile" selection remains > against the device. What happens if the device chosen is unsuitable? Go back to the previous profile, or 'None'? Richard. From paul at fincc.com Fri Feb 19 13:15:29 2010 From: paul at fincc.com (Paul Finnigan) Date: Fri, 19 Feb 2010 13:15:29 +0000 Subject: Selecting Device Profiles In-Reply-To: <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> References: <1266583710.2381.14.camel@localhost> <15e53e181002190505v6073b2e9t599763b6c2a1cb41@mail.gmail.com> Message-ID: <1266585329.2381.16.camel@localhost> Richard On Fri, 2010-02-19 at 13:05 +0000, Richard Hughes wrote: > What happens if the device chosen is unsuitable? Go back to the > previous profile, or 'None'? > > Richard. I would suggest the previous profile. The warning can then say that the profile is unsuitable and the setting has not been altered. -- Paul Finnigan Finnigan Computer Consultants Ltd. From pmjdebruijn at pcode.nl Fri Feb 19 23:03:26 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 00:03:26 +0100 Subject: gcm-git not building (as package) Message-ID: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Hi, There are some trivial problems with gcm-git: cc1: warnings being treated as errors gcm-calibrate.c: In function 'gcm_calibrate_device': gcm-calibrate.c:654: error: unused variable 'dialog' make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Sat Feb 20 00:14:20 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:14:20 +0300 Subject: Small thumbnails of targets In-Reply-To: <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> Message-ID: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> On 2/10/10, Lars Tore Gustavsen wrote: >> This would be a great way to help out gnome-color-manager if you are >> not comfortable with coding. The list of target types I need as >> thumbnails are: >> >> CMP_Digital_Target-3 >> CMP_DT_003 >> ColorChecker >> ColorCheckerDC >> ColorCheckerSG >> Hutchcolor >> i1_RGB_Scan_1.4 Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) Alexandre From alexandre.prokoudine at gmail.com Sat Feb 20 00:10:43 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Sat, 20 Feb 2010 03:10:43 +0300 Subject: Adding printer profiling support In-Reply-To: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> Message-ID: <733f2c731002191610q5bea9bd2l347287afcf42abc9@mail.gmail.com> On 2/17/10, Richard Hughes wrote: > So. Does anybody have any hints, tips or suggestions on how to > calibrate a printer. Device specific options (e.g. "The ColorMunki > works really well with -f234 -g567") are more than welcome, as we > already know the colorimeter device type. Just in case, make sure you've seen GPLin (http://bit.ly/aTmim3). Maybe it has some useful code for you. Alexandre From pedro at pedrocr.net Fri Feb 19 21:01:20 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Fri, 19 Feb 2010 13:01:20 -0800 Subject: Adding printer profiling support In-Reply-To: <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> Message-ID: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> (I'm CC'ing this to the list to keep the discussion there, hope it's ok) On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > Some applications (even commercial ones) don't support LUT display > profiles properly. > > Argyll can generate Matrix+LUT profiles, but then you have the problem > that one app uses the matrix and the other the LUT, this can give odd > inconsistencies... So it's not recommended for defaults... Makes sense. Do you know if I'll be ok with a LUT using GIMP/f-spot/ufraw? I should probably try g-c-m again to see what profile it comes up with. When I did the LUT one with 2000 patches the result seemed to have a fair amount of extra contrast that looked good. Don't know where that came from. > This is true, however, 210 is already a _big_ improvement over 90... Sure. Although I need to test it again as it was too little for me before. But here is Graeme Gill's opinion on number of needed patches (600-1000 for a "well-behaved" printer): http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,22 I guess this one is easy to expose to the user by asking him how many sheets to print. > Please also note, that you're passing all kinds of options with > unknown effects... I just passed the options recommended by argyll itself (the mailing list and the docs). > Please try again with exactly the options I gave... > > Also make sure you have an up to date version of Argyll (1.1.0-final)... Yes, this I did use in the last run but not the previous ones, so that could be the problem with 210 patches. > -q has little do to with actual quality with LUT profiles, it has to > do with detailedness of the generated profiles... Generating a high > detail profiles with low patches seems silly at best. Makes sense, thanks. >> Again the scenarios and the mailing list tell us to use a source >> profile. Milan had an explanation for it. > > Do you have a reference for that? Sure. Here are the docs: http://www.argyllcms.com/doc/Scenarios.html#PP5 And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try different profiles there: http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 It could be that we can actually get away without -S for a decent default. We should probably start a thread in the argyll mailing list about what to use as sensible defaults for profiling printers (and monitors/scanners/cameras too maybe). > We aren't catering to the masses... But even advanced hobby > photographers and professional photographers see color management as a > necessary evil, and most don't want to bother with patch counts and > all kinds of settings, they just want a reasonable match by clicking > on "Next" a couple of times... Yes, I agree completely. My point wasn't that the GUI shouldn't start as a straight-through "get a decent enough profile and be done with it". I was just arguing that the user shouldn't be dumped into learning all these argyll command line options every time he wants to do something even moderately advanced. > Again, the big question would be how often you _really need_ the > advanced settings... Liking to fiddle with them and needing them are > two different things... > > Trying to control to much was a mistake I made in the past as well, > sticking to Argyll's defaults has generally improved my results. I totally agree there. Only settings that are actually needed should be exposed. I don't yet know what those are though considering all the advice to fiddle with different settings I got from the argyll list. Maybe most of that advice can actually be the default and not need changing. >> I think the underlying assumption behind telling users who want >> advanced stuff to go to the argyll tools is that someone that wants >> advanced calibration/color in Linux is also an advanced Linux user. >> Whereas in reality it would be good to be able to support advanced >> photographers/artists that are also non-geek computer users. It's an >> uphill battle right now with GIMP not supporting 16-bit images, f-spot >> not very complete and raw converters still not particularly good. >> We're advancing in all three fronts though and g-c-m is a much needed >> complement. > > Patience is key here... No doubt. I wouldn't be using Linux to do photography work if I wasn't happy to put up with and work around the shortcomings. >> why -g? > > Adds greyscale patches. So why deviate from the argyll standard there? This one didn't get mentioned in my thread. Is it to improve the tone curve for B&W printing? >>> # printtarg -v -i CM -h -t 300 -p A4 test >> >> Does -t 300 help? I was getting some non-sharp edges on my patches >> maybe it was because of this. > > This doesn't particularly matter much, you're not measuring the edges. I wasn't too worried about it although I guessed it could mess up the patch detection and maybe sometimes interfere with a reading, especially when using the smaller patches. Cheers, Pedro From knizek.confy at volny.cz Sat Feb 20 08:15:14 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 09:15:14 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266653714.2961.28.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). > I completely agree to get some hints from argyllcms mailing list users. Also, sooner or later, GCM would need to solve the problem of a general photographer (I do not want to know how things work but still want my pictures nicely printed). A good example is here: http://photo.net/digital-darkroom-forum/00ViCO William Palmer wonders what to do to solve the problem that printed images look fine on direct sun-light, but when hanged on the wall inside, they look "dark". At the end, Andrew Rodney mentions some "advanced profiling solutions", which can compensate for different viewing conditions, but William does not get the point (which is understandable). That is what ArgyllCMS takes care by -c and -d parameters for colprof: -- Since appearance space is used in the gamut mapping (just as it is in collink), the viewing conditions for the source and destination colorspaces should really be specified. The source colorspace is the profile specified with the -s or -S flag, and the destination is the profile being created. The -c and -d options allow specification of their respective, associated viewing conditions. The viewing condition information is used to map the profile PCS (Profile Connection Space, which us either XYZ or L*a*b*) color into appearance space (CIECAM02), which is a better colorspace to do gamut mapping in. The viewing conditions allow the conversion into appearance space to take account of how color will be seen under particular viewing conditions. -- I do also not think that exposing the colprof parameters to a user is a good idea. Nonetheless, how about asking the user - "Will your print be viewed in a dim light environmnet?" "Will it hang in a room well lit by daylight?") And similarly for "-g" paramater of targen: "Do you print black and white photographs and want a higher emphasise on grey neutrality then on colour fidelity?" Using such questions, the user could be navigated to get a good profile for his own use. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Sat Feb 20 08:44:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Sat, 20 Feb 2010 08:44:50 +0000 Subject: gcm-git not building (as package) In-Reply-To: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> References: <4c2c37f91002191503t285d44yc841344fd61889c@mail.gmail.com> Message-ID: <15e53e181002200044j180d4e97kf865fb3054fd2092@mail.gmail.com> On 19 February 2010 23:03, Pascal de Bruijn wrote: > cc1: warnings being treated as errors > gcm-calibrate.c: In function 'gcm_calibrate_device': > gcm-calibrate.c:654: error: unused variable 'dialog' > make[4]: *** [gcm_prefs-gcm-calibrate.o] Error 1 commit 8c711eb8ba43a8bad65d7f45899859b3ed7fdc81 Author: Richard Hughes Date: Sat Feb 20 08:43:38 2010 +0000 trivial: fix compile from git master when compiling without PackageKit Richard. From pmjdebruijn at pcode.nl Sat Feb 20 11:45:23 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Sat, 20 Feb 2010 12:45:23 +0100 Subject: Small thumbnails of targets In-Reply-To: <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> References: <15e53e181002080116i717fc3feg440487365eea83fa@mail.gmail.com> <58497f011002100529q3b6e53f8l55c8cbf9eb89d7f1@mail.gmail.com> <733f2c731002191614ncbdcd4ek7b6040a9082922f9@mail.gmail.com> Message-ID: <4c2c37f91002200345l1a221c69tb8612a35b5c0ff26@mail.gmail.com> On Sat, Feb 20, 2010 at 1:14 AM, Alexandre Prokoudine wrote: > On 2/10/10, Lars Tore Gustavsen wrote: > >>> This would be a great way to help out gnome-color-manager if you are >>> not comfortable with coding. The list of target types I need as >>> thumbnails are: >>> >>> CMP_Digital_Target-3 >>> CMP_DT_003 >>> ColorChecker >>> ColorCheckerDC >>> ColorCheckerSG >>> Hutchcolor >>> i1_RGB_Scan_1.4 > > Which one of them is my LaserSoft's IT8.7/21993 2005:8 conformant target? :) IT8 = IT8, doesn't really matter which vendor... At least it shouldn't it think... Regards, Pascal de Bruijn From knizek.confy at volny.cz Sat Feb 20 16:58:55 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Sat, 20 Feb 2010 17:58:55 +0100 Subject: Adding printer profiling support In-Reply-To: <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> References: <15e53e181002170605xaac6387r53e92520976b417@mail.gmail.com> <62e8012c1002172050y3227df00pd380520452bc486e@mail.gmail.com> <4c2c37f91002180957k789a7e2fl8ddf1994a42bd1f2@mail.gmail.com> <62e8012c1002181809w150abf8fma3d053d0bae08a3a@mail.gmail.com> <4c2c37f91002190336l60ffc013n199d1c147232875f@mail.gmail.com> <62e8012c1002191301j3a321f7at83ae0fb58a7e078f@mail.gmail.com> Message-ID: <1266685135.5298.5.camel@athlon> Pedro C?rte-Real p??e v P? 19. 02. 2010 v 13:01 -0800: > On Fri, Feb 19, 2010 at 3:36 AM, Pascal de Bruijn wrote: > >> Again the scenarios and the mailing list tell us to use a source > >> profile. Milan had an explanation for it. > > > > Do you have a reference for that? > > Sure. Here are the docs: > > http://www.argyllcms.com/doc/Scenarios.html#PP5 > > And Alastair Robinson's (of PhotoPrint fame) opinion on it was to try > different profiles there: > > http://www.freelists.org/post/argyllcms/Printing-using-an-ICC-profile,3 > > It could be that we can actually get away without -S for a decent > default. We should probably start a thread in the argyll mailing list > about what to use as sensible defaults for profiling printers (and > monitors/scanners/cameras too maybe). How about using the RGB working colourspace, which is set in GCM defaults tab, for -S colour space? We can assume that majority of the images would be in that space. Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From paul at fincc.com Mon Feb 22 12:16:11 2010 From: paul at fincc.com (Paul Finnigan) Date: Mon, 22 Feb 2010 12:16:11 +0000 Subject: Updated Help Text Message-ID: <1266840971.2539.8.camel@localhost> Richard I have amended the text around the preferences and advanced preferences sections of the help file. I have included (but not altered) the text you said should go in about gamma. The text is not perfect but I think that it is better than what was there. I cannot alter the section on Calibration as I do not have the hardware to check out the interface yet (gcm is the first software that made me want to buy it!). If anyone has anything to add to the help files but does not want to update them then just let me know. -- Paul Finnigan -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-Help-Preferences-Text.patch Type: text/x-patch Size: 7012 bytes Desc: not available URL: From hughsient at gmail.com Mon Feb 22 12:31:50 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:31:50 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220431j4a0f4c37lce0c558756c98d7e@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > The text is not perfect but I think that it is better than what was > there. Agreed, thanks. I've applied it with minor changes. You also need to set your email address so git formatted patches display the right email (and so lazy me can just use git am). To do this, just set export GIT_AUTHOR_EMAIL=dave at dave.com in ~/.bash_profile for future patches. Thanks! Richard. From hughsient at gmail.com Mon Feb 22 12:38:59 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 12:38:59 +0000 Subject: Updated Help Text In-Reply-To: <1266840971.2539.8.camel@localhost> References: <1266840971.2539.8.camel@localhost> Message-ID: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> On 22 February 2010 12:16, Paul Finnigan wrote: > If anyone has anything to add to the help files but does not want to > update them then just let me know. In particular, we need lots more FAQ entries filled out: * What colorimeter devices are supported * What target types are supported? * Where do I purchase targets from? * How do I get a profile from my display vendor * How do I get a reference image using a digital camera? * ...lots of other details about color management.... If you're scared by docbook and git, then just submit some prose to the mailing list, and one of the other contributors can format it up and submit a patch on your behalf. Thanks, Richard. From alexandre.prokoudine at gmail.com Mon Feb 22 13:43:41 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Mon, 22 Feb 2010 16:43:41 +0300 Subject: Updated Help Text In-Reply-To: <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> References: <1266840971.2539.8.camel@localhost> <15e53e181002220438uf0ecad3r98504bfa0d5d442a@mail.gmail.com> Message-ID: <733f2c731002220543x3c160251v4a546c11e44a7210@mail.gmail.com> On 2/22/10, Richard Hughes wrote: > In particular, we need lots more FAQ entries filled out: > > * What colorimeter devices are supported Committed > * What target types are supported? Committed > * Where do I purchase targets from? Committed Alexandre From hughsient at gmail.com Mon Feb 22 14:46:19 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 14:46:19 +0000 Subject: ColorMunki works Message-ID: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> My ColorMunki arrived this morning, and I've just committed quite a few patches to make it work calibrating the screen. There are still quite a few rough edges we need to fix (hardcode) but it basically works. Now I'm going to move onto adding initial printing support, although this might take a couple of weeks. Richard. From pmjdebruijn at pcode.nl Mon Feb 22 17:22:37 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Mon, 22 Feb 2010 18:22:37 +0100 Subject: ColorMunki works In-Reply-To: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> References: <15e53e181002220646h386c0875x4effc2db4086465d@mail.gmail.com> Message-ID: <4c2c37f91002220922m77984a56o1c441985dbc9d099@mail.gmail.com> On Mon, Feb 22, 2010 at 3:46 PM, Richard Hughes wrote: > My ColorMunki arrived this morning, and I've just committed quite a > few patches to make it work calibrating the screen. There are still > quite a few rough edges we need to fix (hardcode) but it basically > works. Now I'm going to move onto adding initial printing support, > although this might take a couple of weeks. Indeed it does, there are some cosmetic issues though: https://bugzilla.gnome.org/show_bug.cgi?id=605856 I'm looking forward to the printer stuff, especially the CUPS integration, it would severely kick ass if there would be an extra CUPS Color Management tab, on which output color profiles could be specified. Regards, Pascal de Bruijn From knizek.confy at volny.cz Mon Feb 22 20:51:30 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 21:51:30 +0100 Subject: Make default - what is it supposed to do? Message-ID: <1266871890.982.23.camel@athlon> Hello, what is the expected behaviour of "Make Default" button in gcm-prefs? The notification message reads "Save these profiles for all users", but after pressing it I can see the verbose output reading: - running: pkexec /usr/sbin/gcm-install-system-wide --id xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" Content type was incorrect: application/octet-stream It tries to install the monitor profile, however, I also have a webcam profile set. And as far as I can tell, nothing happens. The profile is not copied to /usr/share/color/... or /usr/local/share/color/... locations, I cannot find anything useful in /etc/... or /var/lib/... and starting a session of a different user does not show any profile set in gcm-prefs. Is this is a bug or not-yet-implemented thing? Regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From alexandre.prokoudine at gmail.com Mon Feb 22 21:11:25 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Tue, 23 Feb 2010 00:11:25 +0300 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> On 2/22/10, Milan Kn??ek wrote: > Hello, > > what is the expected behaviour of "Make Default" button in gcm-prefs? http://www.libregraphicsworld.org/articles.php?article_id=11 "To make your preferences available to all users of a system you can use the Make Default button in the bottom of the dialog. What it will do is ask for superuser password and copy all the active display profiles to a system-wide directory (/var/lib/color) where the new filename matches the device-id. So when a new user logs in, if there is no device-profiles entry for the device, the system-wide profile is used." Alexandre From knizek.confy at volny.cz Mon Feb 22 22:07:42 2010 From: knizek.confy at volny.cz (Milan =?UTF-8?Q?Kn=C3=AD=C5=BEek?=) Date: Mon, 22 Feb 2010 23:07:42 +0100 Subject: Make default - what is it supposed to do? In-Reply-To: <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> References: <1266871890.982.23.camel@athlon> <733f2c731002221311r7aca2051x2629011d8b174b71@mail.gmail.com> Message-ID: <1266876462.20402.8.camel@athlon> Alexandre Prokoudine p??e v ?t 23. 02. 2010 v 00:11 +0300: > On 2/22/10, Milan Kn??ek wrote: > > Hello, > > > > what is the expected behaviour of "Make Default" button in gcm-prefs? > > http://www.libregraphicsworld.org/articles.php?article_id=11 > > "To make your preferences available to all users of a system you can > use the Make Default button in the bottom of the dialog. What it will > do is ask for superuser password and copy all the active display > profiles to a system-wide directory (/var/lib/color) where the new > filename matches the device-id. So when a new user logs in, if there > is no device-profiles entry for the device, the system-wide profile is > used." > Then it seems to be a bug - on two computers (same system though - Ubuntu 9.10 amd64) the directory /var/lib/color exists, but it remains empty. Authorisation seems to be okay, I also tried to run with sudo and as root in console - no success, just the error message: Content type was incorrect: application/octet-stream regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) From hughsient at gmail.com Mon Feb 22 23:17:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Mon, 22 Feb 2010 23:17:13 +0000 Subject: Make default - what is it supposed to do? In-Reply-To: <1266871890.982.23.camel@athlon> References: <1266871890.982.23.camel@athlon> Message-ID: <15e53e181002221517t65dc049aqccb1f4580470e478@mail.gmail.com> On 22 February 2010 20:51, Milan Kn??ek wrote: > ?- running: pkexec /usr/sbin/gcm-install-system-wide --id > xrandr_116at01_a01 "/home/mu/.color/icc/xl20_huey_emu_sRGB_6500.icc" > Content type was incorrect: application/octet-stream Looks like your version of shared-mime-info is too old. We can't do the .icc/.icm fallback in this case as gcm-install-system-wide is running as root as we have to be careful of maliciously created profiles. > Is this is a bug or not-yet-implemented thing? The former :-) Richard. From hughsient at gmail.com Tue Feb 23 14:21:39 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 14:21:39 +0000 Subject: Blog post about GCM Message-ID: <15e53e181002230621t76746c6elb9c4dcc2344b59c@mail.gmail.com> I've made a blog post about GCM that some of you might find interesting: http://blogs.gnome.org/hughsie/2010/02/23/gnome-color-manager-and-printer-profiling/ Good job on the documentation file btw, it's coming along nicely now. Richard. From hughsient at gmail.com Tue Feb 23 15:50:21 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 15:50:21 +0000 Subject: Strategic direction Message-ID: <15e53e181002230750r1b8414a2l2503a7079cfd4f2d@mail.gmail.com> Big ideas I think we need to work towards: * Assigning more than one profile to a device[1] (and having one default profile per device) * Having virtual devices that we can't connect, for instance "Bob's Photo Processing Shop" Any one got any more ideas? Richard. [1] The DBus API already supports this, although it only ever returns one profile. From pmjdebruijn at pcode.nl Tue Feb 23 17:44:13 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 18:44:13 +0100 Subject: New print profiling functionality Message-ID: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Hi, I just tried the brand spanking new print profiling functionality... And of course there's something to bitch about... * It only generated 45 patches, while on A4 I can fit 210 ColorMunki patches in double density mode (-h). * Some patches got clipped (because of margins), because the generated image isn't centered (or it is getting stretched for no reason, since the generated image doesn't include margins). * The generated image is pretty low resolution, the text looks like crap, consider (printtarg -T 200 or 300)? * GCM should not report "reading the patches" during self-calibration, we need a seperate dialog for this! Regards, Pascal de Bruijn From hughsient at gmail.com Tue Feb 23 17:51:53 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 17:51:53 +0000 Subject: New print profiling functionality In-Reply-To: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> Message-ID: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> On 23 February 2010 17:44, Pascal de Bruijn wrote: > I just tried the brand spanking new print profiling functionality... > And of course there's something to bitch about... Heh, good. :-) > * It only generated 45 patches, while on A4 I can fit 210 ColorMunki > patches in double density mode (-h). Right, this is something I need help with. How many patches do we use for quick, normal and slow profiling? I'm already using -h for ColorMunki. > * Some patches got clipped (because of margins), because the generated > image isn't centered (or it is getting stretched for no reason, since > the generated image doesn't include margins). Ahh, I'm just blitting it to the cairo surface, without preserving aspect. I guess we need to do that. I'm using gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > * The generated image is pretty low resolution, the text looks like > crap, consider (printtarg -T 200 or 300)? Hmm, it should already be using 300DPI thanks to the -t300 option. > * GCM should not report "reading the patches" during self-calibration, > we need a seperate dialog for this! Sure, I can't get my ColorMunki to self calibrate using chartread (see the Argyll m/l) so I've not tested past this point. Richard. From hughsient at gmail.com Tue Feb 23 20:20:13 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 20:20:13 +0000 Subject: New print profiling functionality In-Reply-To: <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> Message-ID: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> On 23 February 2010 17:51, Richard Hughes wrote: > Ahh, I'm just blitting it to the cairo surface, without preserving > aspect. I guess we need to do that. I'm using > gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. I've done the scaling in cairo now; see below. >> * The generated image is pretty low resolution, the text looks like >> crap, consider (printtarg -T 200 or 300)? > > Hmm, it should already be using 300DPI thanks to the -t300 option. I've just pushed a commit to do the scaling in cairo, rather than GDK, which makes it look much better. Richard. From pmjdebruijn at pcode.nl Tue Feb 23 22:22:30 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:22:30 +0100 Subject: New print profiling functionality In-Reply-To: <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> References: <4c2c37f91002230944k7cdc3f3bgb375fa4789d62d75@mail.gmail.com> <15e53e181002230951p15ab4a20x6fdf4b60c71d5454@mail.gmail.com> <15e53e181002231220h38bb9c4o35098f72c14e837f@mail.gmail.com> Message-ID: <4c2c37f91002231422g6836f6e5s1a7ff1a8db4e8c7f@mail.gmail.com> On Tue, Feb 23, 2010 at 9:20 PM, Richard Hughes wrote: > On 23 February 2010 17:51, Richard Hughes wrote: >> Ahh, I'm just blitting it to the cairo surface, without preserving >> aspect. I guess we need to do that. I'm using >> gdk_pixbuf_new_from_file_at_scale() which is probably a bad plan. > > I've done the scaling in cairo now; see below. > >>> * The generated image is pretty low resolution, the text looks like >>> crap, consider (printtarg -T 200 or 300)? >> >> Hmm, it should already be using 300DPI thanks to the -t300 option. > > I've just pushed a commit to do the scaling in cairo, rather than GDK, > which makes it look much better. Actually, since you're using cairo, which is very vector-aware, right? Wouldn't it make sense to use the EPS output (printtarg -e). Regards, Pascal de Bruijn From pmjdebruijn at pcode.nl Tue Feb 23 22:28:50 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Tue, 23 Feb 2010 23:28:50 +0100 Subject: Printshop calibration/profiling Message-ID: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Hi, Another thing I noticed, is the very cool dialog which also allows you to profile printshops, however I can only get to this dialog whenever I have a printer in GCM, and the spectrophotometer connected, even though I only want to generate a chart to send to my printshop. This is not a huge problem, more of a nuisance... Maybe it's a thought to create a "Printshop" virtual device? Honestly I'm not sure that's a much better solution, since sooner or later we'll end up with 100 by default created virtual devices for all kinds of corner cases... This message is mainly intended to get a discussion going... Regards, Pascal de Bruijn From alexandre.prokoudine at gmail.com Tue Feb 23 22:32:52 2010 From: alexandre.prokoudine at gmail.com (Alexandre Prokoudine) Date: Wed, 24 Feb 2010 01:32:52 +0300 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <733f2c731002231432j6144ec13h1ffd278e038064c0@mail.gmail.com> On 2/24/10, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... This is not a huge problem when you have a printer. Well, I don't have one :) Alexandre From hughsient at gmail.com Tue Feb 23 22:33:36 2010 From: hughsient at gmail.com (Richard Hughes) Date: Tue, 23 Feb 2010 22:33:36 +0000 Subject: Printshop calibration/profiling In-Reply-To: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> References: <4c2c37f91002231428m4d801692id873f873cc69a563@mail.gmail.com> Message-ID: <15e53e181002231433j2138420bg216e2efe3d84ad3c@mail.gmail.com> On 23 February 2010 22:28, Pascal de Bruijn wrote: > Another thing I noticed, is the very cool dialog which also allows you > to profile printshops, however I can only get to this dialog whenever > I have a printer in GCM, and the spectrophotometer connected, even > though I only want to generate a chart to send to my printshop. This > is not a huge problem, more of a nuisance... Sure, agreed. > Maybe it's a thought to create a "Printshop" virtual device? Honestly > I'm not sure that's a much better solution, since sooner or later > we'll end up with 100 by default created virtual devices for all kinds > of corner cases... I do think we need virtual devices. It's bad usability, as you have to enter everything manually, but a useful thing for power users. Richard. From pmjdebruijn at pcode.nl Wed Feb 24 22:06:08 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Wed, 24 Feb 2010 23:06:08 +0100 Subject: Double Density Mode for ColorMunki Message-ID: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Hi, To my dismay I noticed you've dropped the double density mode for the ColorMunki. What would be the problem with this? Maybe I can help? Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 08:43:34 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 08:43:34 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> Message-ID: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> On 24 February 2010 22:06, Pascal de Bruijn wrote: > To my dismay I noticed you've dropped the double density mode for the > ColorMunki. What would be the problem with this? Maybe I can help? I just couldn't get double density to work correctly. Maybe I'm clumsy or something, but the single density was much easier to scan. Perhaps we can just have it as a simple dialog choice? ________________________________ Target Choice ________________________________ Your calibration device can use much smaller sized squares to save on paper and ink, although it will be harder to use the device. Enable double density mode? [Help] [No] [Yes] ________________________________ Richard. From pmjdebruijn at pcode.nl Thu Feb 25 10:58:38 2010 From: pmjdebruijn at pcode.nl (Pascal de Bruijn) Date: Thu, 25 Feb 2010 11:58:38 +0100 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> Message-ID: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> On Thu, Feb 25, 2010 at 9:43 AM, Richard Hughes wrote: > On 24 February 2010 22:06, Pascal de Bruijn wrote: >> To my dismay I noticed you've dropped the double density mode for the >> ColorMunki. What would be the problem with this? Maybe I can help? > > I just couldn't get double density to work correctly. Maybe I'm clumsy > or something, but the single density was much easier to scan. I'm guessing you didn't print it at proper scale... In double density mode, three rows are exactly as wide as the ColorMunki, so the rows themselves can be used as a visual guide. And because the patches are smaller you need to scan a bit slower. > Perhaps we can just have it as a simple dialog choice? No that's silly... Regards, Pascal de Bruijn From hughsient at gmail.com Thu Feb 25 11:36:33 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 11:36:33 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> Message-ID: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> On 25 February 2010 10:58, Pascal de Bruijn wrote: > I'm guessing you didn't print it at proper scale... Well, argyll formats it as a single page tiff file, so I'm pretty sure I did. I've attached a photo to show you the pages. > In double density mode, three rows are exactly as wide as the > ColorMunki, so the rows themselves can be used as a visual guide. And > because the patches are smaller you need to scan a bit slower. Right, maybe I'm just a bit clumsy. >> Perhaps we can just have it as a simple dialog choice? > > No that's silly... Agreed. Richard. -------------- next part -------------- A non-text attachment was scrubbed... Name: double-density.jpg Type: image/jpeg Size: 23813 bytes Desc: not available URL: From hughsient at gmail.com Thu Feb 25 12:07:28 2010 From: hughsient at gmail.com (Richard Hughes) Date: Thu, 25 Feb 2010 12:07:28 +0000 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> Message-ID: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> On 25 February 2010 11:36, Richard Hughes wrote: > Right, maybe I'm just a bit clumsy. I've found I can use the double density scan 99% correctly, if I rotate the page and "push" the colormunki away from me. If I try to scan from left to right then it only works 10% of the time. I'll do you deal. I'll re-instate the double density feature (with extra love) if you write a section in the help file on how to scan in a target, with tips. :-) Deal? Richard. From pedro at pedrocr.net Thu Feb 25 21:10:18 2010 From: pedro at pedrocr.net (=?UTF-8?Q?Pedro_C=C3=B4rte=2DReal?=) Date: Thu, 25 Feb 2010 13:10:18 -0800 Subject: Double Density Mode for ColorMunki In-Reply-To: <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> References: <4c2c37f91002241406l1378e3ccl33c48ec4804d2948@mail.gmail.com> <15e53e181002250043hf05328o1df43f72ca6e0ec2@mail.gmail.com> <4c2c37f91002250258t427577c1ib7373bdd96147c4b@mail.gmail.com> <15e53e181002250336r57389639n322d7c713e91ae26@mail.gmail.com> <15e53e181002250407i1603cbb5s4b5eeec1918106ba@mail.gmail.com> Message-ID: <62e8012c1002251310t6c02124cnd3f62db919b2b5dd@mail.gmail.com> On Thu, Feb 25, 2010 at 4:07 AM, Richard Hughes wrote: > I'll do you deal. I'll re-instate the double density feature (with > extra love) if you write a section in the help file on how to scan in > a target, with tips. :-) If I write a section for the manual on how to build and use the simple guide rules to use the munki with EyeOne targets can we get that mode too? In my experience it makes scanning much simpler than even normal density patches freehand and the guide takes 5 minutes and only basic supplies to build. If someone was selling an after-market solution for this I assume no one would have a problem with it so I don't see why a home-made one isn't fine as well. It would at least be nice if the instrument definitions were setup in config files for each instrument so that even if you don't want to have this in mainline people could hack together their own config files and still take advantage of the g-c-m UI. Pedro