Comments for Oyranos http://www.oyranos.org Colour Management System Mon, 20 Feb 2012 17:04:24 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on X Color Management 0.4 DRAFT1 by oyranos http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1175 oyranos Mon, 20 Feb 2012 17:04:24 +0000 http://www.oyranos.org/?p=1093#comment-1175 Ah, you are referring with CIE*Lab to the ICC Profile Connection Space (PCS). The CMM will create one transform object from all profiles and options. So we would end with following two conversions: –(input icc profile)–> Representation in intermediate blending space | pass to compositor –(intermediate space profile)–> Output image (monitor device profile) I assume here the compositor will colour convert all content prior to it's own blending to the monitor colour space. Ah, you are referring with CIE*Lab to the ICC Profile Connection Space (PCS). The CMM will create one transform object from all profiles and options. So we would end with following two conversions:
–(input icc profile)–> Representation in intermediate blending space | pass to compositor –(intermediate space profile)–> Output image (monitor device profile)
I assume here the compositor will colour convert all content prior to it’s own blending to the monitor colour space.

]]> Comment on X Color Management 0.4 DRAFT1 by Niels Ole Salscheider http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1174 Niels Ole Salscheider Mon, 20 Feb 2012 15:21:34 +0000 http://www.oyranos.org/?p=1093#comment-1174 > With that a application can convert to a intermediate blending space and let the compositor care about the conversion to each output. I wonder again if we should allow that intermediate blending space to be a device independent space like L*a*b*. Otherwise we would end up with something like "Input Image --(input icc profile)--> Lab --(blending space profile)--> Representation in intermediate blending space --> pass to compositor --(blending space profile)--> Lab --(output device profile)--> Output image" that is less efficient. > With that a application can convert to a intermediate blending space and let the compositor care about the conversion to each output.

I wonder again if we should allow that intermediate blending space to be a device independent space like L*a*b*.
Otherwise we would end up with something like “Input Image –(input icc profile)–> Lab –(blending space profile)–> Representation in intermediate blending space –> pass to compositor –(blending space profile)–> Lab –(output device profile)–> Output image” that is less efficient.

]]> Comment on X Color Management 0.4 DRAFT1 by X Color Management 0.4 DRAFT1 | Oyranos « Management Fair http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1169 X Color Management 0.4 DRAFT1 | Oyranos « Management Fair Sat, 18 Feb 2012 04:07:49 +0000 http://www.oyranos.org/?p=1093#comment-1169 [...] from: X Color Management 0.4 DRAFT1 | Oyranos Comments [...] [...] from: X Color Management 0.4 DRAFT1 | Oyranos Comments [...]

]]> Comment on X Color Management 0.4 DRAFT1 by Anonymous http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1167 Anonymous Fri, 17 Feb 2012 19:42:07 +0000 http://www.oyranos.org/?p=1093#comment-1167 Glad to hear that my fears are unjustified, thanks for the answer! Glad to hear that my fears are unjustified, thanks for the answer!

]]> Comment on X Color Management 0.4 DRAFT1 by oyranos http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1166 oyranos Fri, 17 Feb 2012 18:50:03 +0000 http://www.oyranos.org/?p=1093#comment-1166 Correct, that's why the spec highly recommends to support client side profiles. With that a application can convert to a intermediate blending space and let the compositor care about the conversion to each output. The according _ICC_COLOR_PROFILES atom is in the spec since version 0.3 and will be supported in the next CompICC colour server release. Correct, that’s why the spec highly recommends to support client side profiles. With that a application can convert to a intermediate blending space and let the compositor care about the conversion to each output.

The according _ICC_COLOR_PROFILES atom is in the spec since version 0.3 and will be supported in the next CompICC colour server release.

]]> Comment on X Color Management 0.4 DRAFT1 by Anonymous http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/#comment-1165 Anonymous Fri, 17 Feb 2012 18:37:59 +0000 http://www.oyranos.org/?p=1093#comment-1165 That sounds like a really bad idea. What happens when a window covers more than one screen? What happens when I work with duplicate monitors? IMHO the only sane place for color correction is the system compositor. That sounds like a really bad idea. What happens when a window covers more than one screen? What happens when I work with duplicate monitors?
IMHO the only sane place for color correction is the system compositor.

]]> Comment on Linux Printing by Joe Simon http://www.oyranos.org/2012/02/linux-printing/#comment-1161 Joe Simon Thu, 16 Feb 2012 18:05:13 +0000 http://www.oyranos.org/?p=1028#comment-1161 Hi. It is difficult to say at this point. There needs to be some more testing with the library - it would be nice to see if we could first use libCmpx on a few other apps that use a print dialog (Krita, for example). In addition, PDF rendering capability is not quite ready at the moment. However, this is where I am focusing most of my work right now. Hi.

It is difficult to say at this point.

There needs to be some more testing with the library – it would be nice to see if we could first use libCmpx on a few other apps that use a print dialog (Krita, for example).

In addition, PDF rendering capability is not quite ready at the moment. However, this is where I am focusing most of my work right now.

]]> Comment on Linux Printing by Fragender http://www.oyranos.org/2012/02/linux-printing/#comment-1160 Fragender Thu, 16 Feb 2012 11:45:11 +0000 http://www.oyranos.org/?p=1028#comment-1160 Will this be supported in the next KDE (4.9?) release? Will this be supported in the next KDE (4.9?) release?

]]> Comment on Linux Printing by oyranos http://www.oyranos.org/2012/02/linux-printing/#comment-1157 oyranos Wed, 15 Feb 2012 17:30:06 +0000 http://www.oyranos.org/?p=1028#comment-1157 My experiments in creating UML diagrams in dia where from a graphical point of view never satisfying. But that was already some time ago. As I am a graphics guy, I used Inkscape for all diagrams in this post. They are completely freestyle, so "common sense" might fit best. My experiments in creating UML diagrams in dia where from a graphical point of view never satisfying. But that was already some time ago. As I am a graphics guy, I used Inkscape for all diagrams in this post. They are completely freestyle, so “common sense” might fit best.

]]> Comment on Linux Printing by isemenov http://www.oyranos.org/2012/02/linux-printing/#comment-1156 isemenov Wed, 15 Feb 2012 17:12:26 +0000 http://www.oyranos.org/?p=1028#comment-1156 Awesome news! Is that UML or some "common sense" state diagram? If it's real UML, kudos to the project - Open Source devs often seem to be avoiding the real development tools for no reason. Also, if it's UML, it looks like it has it been produced with some kind of TeX package, based on TikZ - the arrows indicate that ;) so it's really nice to know TeX can do UML. Awesome news!

Is that UML or some “common sense” state diagram? If it’s real UML, kudos to the project – Open Source devs often seem to be avoiding the real development tools for no reason. Also, if it’s UML, it looks like it has it been produced with some kind of TeX package, based on TikZ – the arrows indicate that ;) so it’s really nice to know TeX can do UML.

]]> Comment on Colour Management in openSUSE-12.1 by Latino » Blog Archive » Dedicado a Suse Linux un distro muy sencillo http://www.oyranos.org/2011/11/colour-management-in-opensuse-12-1/#comment-744 Latino » Blog Archive » Dedicado a Suse Linux un distro muy sencillo Mon, 09 Jan 2012 21:11:02 +0000 http://www.oyranos.org/?p=715#comment-744 [...] Ligeramente camuflado por la novedad que supone GNOME 3, KDE sigue siendo la joya de la corona de openSUSE 12.1, y son dos las características que se presentan en primicia: KolorManager y mirall. El primero lo encontraréis en los repositorios y como su nombre indica es un módulo para la gestión del color(una vez instalado aparecerá en Preferencias del sistema). Podéis encontrar más información acerca de Kolor Manager en este enlace. [...] [...] Ligeramente camuflado por la novedad que supone GNOME 3, KDE sigue siendo la joya de la corona de openSUSE 12.1, y son dos las características que se presentan en primicia: KolorManager y mirall. El primero lo encontraréis en los repositorios y como su nombre indica es un módulo para la gestión del color(una vez instalado aparecerá en Preferencias del sistema). Podéis encontrar más información acerca de Kolor Manager en este enlace. [...]

]]> Comment on About by The release of OpenSUSE 12.1 - Acsyndicate | Acsyndicate http://www.oyranos.org/about/#comment-682 The release of OpenSUSE 12.1 - Acsyndicate | Acsyndicate Tue, 03 Jan 2012 01:42:00 +0000 http://www.oyranos.org/?page_id=133#comment-682 [...] especially for systems with multi-monitor setups. One will also find a new color management tool: Oyranos color management [...] [...] especially for systems with multi-monitor setups. One will also find a new color management tool: Oyranos color management [...]

]]> Comment on Firefox-8.0 Colour Management by oyranos http://www.oyranos.org/2011/12/firefox-8-0-colour-management/#comment-669 oyranos Fri, 30 Dec 2011 18:33:22 +0000 http://www.oyranos.org/?p=922#comment-669 On openSUSE-12.1 you can install MozillaFirefox version 9.0 from my private repository http://software.opensuse.org/download.html?project=home:bekun:branches:openSUSE:12.1:Update&package=MozillaFirefox On openSUSE-12.1 you can install MozillaFirefox version 9.0 from my private repository
http://software.opensuse.org/download.html?project=home:bekun:branches:openSUSE:12.1:Update&package=MozillaFirefox

]]> Comment on Oyranos Colour Management LiveCD III by oyranos http://www.oyranos.org/2011/12/oyranos-colour-management-livecd-iii/#comment-537 oyranos Fri, 16 Dec 2011 07:18:54 +0000 http://www.oyranos.org/?p=877#comment-537 How about putting that topic on OpenICC together with a small suggestion about key name + possible values? Then the GCM and KolorManager projects can implement it and display to users. For a GSoC project that might be overkill. How about putting that topic on OpenICC together with a small suggestion about key name + possible values? Then the GCM and KolorManager projects can implement it and display to users. For a GSoC project that might be overkill.

]]> Comment on Oyranos Colour Management LiveCD III by Florian Höch http://www.oyranos.org/2011/12/oyranos-colour-management-livecd-iii/#comment-531 Florian Höch Thu, 15 Dec 2011 23:33:30 +0000 http://www.oyranos.org/?p=877#comment-531 <blockquote>I had hoped that I would be prompted to calibrate the display on startup, but this ws not the case</blockquote> Yes, this would be nice yet-to-be-implemented functionality. Imho, when a measurement device gets plugged in, the system could ask (via a dialog or preferably a small, not modal popup) if it should launch the calibration software, with the usual option to "not ask again". This also would mean there needs to be a place where users can set the preferred calibration software, and some system (udev?) needs to detect the instrument and act accordingly. Maybe an idea for the next GSoC?

I had hoped that I would be prompted to calibrate the display on startup, but this ws not the case

Yes, this would be nice yet-to-be-implemented functionality. Imho, when a measurement device gets plugged in, the system could ask (via a dialog or preferably a small, not modal popup) if it should launch the calibration software, with the usual option to “not ask again”. This also would mean there needs to be a place where users can set the preferred calibration software, and some system (udev?) needs to detect the instrument and act accordingly. Maybe an idea for the next GSoC?

]]> Comment on Oyranos Colour Management LiveCD III by oyranos http://www.oyranos.org/2011/12/oyranos-colour-management-livecd-iii/#comment-529 oyranos Thu, 15 Dec 2011 08:59:51 +0000 http://www.oyranos.org/?p=877#comment-529 For writing to a existing partition I launched the dolphin file manager available from the dock. I was prompted by a root password dialog and typed in the system password, which is "linux" for this CD. For writing to a existing partition I launched the dolphin file manager available from the dock. I was prompted by a root password dialog and typed in the system password, which is “linux” for this CD.

]]> Comment on Oyranos Colour Management LiveCD III by oyranos http://www.oyranos.org/2011/12/oyranos-colour-management-livecd-iii/#comment-521 oyranos Wed, 14 Dec 2011 15:01:42 +0000 http://www.oyranos.org/?p=877#comment-521 Thanks for your feedback. The CD is meant for average users and colour geeks. So prompting for a specialised procedure like profiling is not in scope. Could you extract the EDID from the root window or output property? If that is available, then Oyranos CMS can create a ICC profile from EDID on the fly, which is together with a launched Compiz/CompICC the base for instant colour management of the display. The small icon in the systray should be colourd to show CompICC is running. To see the profile associated with monitor, you can use several methods. One is the Color Management panels device tab in KDE system settings panel. An other method is to call oyranos-monitor -lc. The -c option is needed to see the actual device profile and not the document profile, with the later normally being sRGB. To see the profile in ICC Examin use: $ oyranos-monitor -c -f icc | iccexamin -i Running ICC Examin on Ubuntu 9.04 and 10.10 seems fine with the developer script: http://www.oyranos.org/wiki/index.php?title=Oyranos/git Will test with a newer ubuntu version. Thanks for the hint. The LiveCD is a stock openSUSE-12.1 with some additional packages and patches applied and brings all advantages and some pain. Hope you can solve to write to disk. Thanks for the suggestions. I will place a README file and think I can disable the german locale preselection. Once we update to the actual dispcalGUI, the explanation for profile upload would make sense. (edited) Thanks for your feedback.

The CD is meant for average users and colour geeks. So prompting for a specialised procedure like profiling is not in scope.

Could you extract the EDID from the root window or output property? If that is available, then Oyranos CMS can create a ICC profile from EDID on the fly, which is together with a launched Compiz/CompICC the base for instant colour management of the display. The small icon in the systray should be colourd to show CompICC is running. To see the profile associated with monitor, you can use several methods. One is the Color Management panels device tab in KDE system settings panel. An other method is to call oyranos-monitor -lc. The -c option is needed to see the actual device profile and not the document profile, with the later normally being sRGB. To see the profile in ICC Examin use:
$ oyranos-monitor -c -f icc | iccexamin -i

Running ICC Examin on Ubuntu 9.04 and 10.10 seems fine with the developer script: http://www.oyranos.org/wiki/index.php?title=Oyranos/git
Will test with a newer ubuntu version. Thanks for the hint.

The LiveCD is a stock openSUSE-12.1 with some additional packages and patches applied and brings all advantages and some pain. Hope you can solve to write to disk.

Thanks for the suggestions. I will place a README file and think I can disable the german locale preselection. Once we update to the actual dispcalGUI, the explanation for profile upload would make sense.
(edited)

]]> Comment on Oyranos Colour Management LiveCD III by Chris Lilley http://www.oyranos.org/2011/12/oyranos-colour-management-livecd-iii/#comment-519 Chris Lilley Wed, 14 Dec 2011 14:25:39 +0000 http://www.oyranos.org/?p=877#comment-519 I gave this CD a whirl. First impressions were not, however, encouraging. Despite the claim that it "starts into a instantly colour managed desktop" the bileous gren background was an instant giveaway tha colour management was not happening. Apparently my wide gamut display was being treated as sRGB. There was no documentation of how the system assigned a monitor profile, and although a search found a number of ICC profiles none seemed to relate to my display. I had hoped that I would be prompted to calibrate the display on startup, but this ws not the case (and my colorimeter was apparently not detected). Maybe then it reads the EDID and chooses from some dfatabase of profiles? If so , its not clear where tha database is. The display widget had no information about a system monitor profile. I was able to load ICC Examin and look at some of the provided sample profiles (which is good as had previously failed to compile it on ubuntu) and visualise the gamut in 3D (with a lot of flickering and screen blackouts, presumably a video driver issue). I was able to look at the provided sample images, the raster ones opened in CinePaint and the vector one in Inkscape. The livecd would not let me read or write to the internal drives aand claimed that tan external drive had an unsupported filesystem (ntfs) so i was unable to copy sample images, icc profiles or screenshots of gamut visualisations. I will try again to see if it can write to a fat32 SD card. Concrete suggestions for improvement: - provide a readme or better, some html documentation to get people started - explain where the monitor profile comes from, how it is set, how to contribute profiles for your hardware, and how to check it is installed and working correctly - explain how to start Argyll with the display gui front end - put the installed programs on the KDE menu (some were but not all) - allow the user to select English UI for ICC Examin and CinePaint :) I gave this CD a whirl. First impressions were not, however, encouraging. Despite the claim that it “starts into a instantly colour managed desktop” the bileous gren background was an instant giveaway tha colour management was not happening. Apparently my wide gamut display was being treated as sRGB. There was no documentation of how the system assigned a monitor profile, and although a search found a number of ICC profiles none seemed to relate to my display.

I had hoped that I would be prompted to calibrate the display on startup, but this ws not the case (and my colorimeter was apparently not detected). Maybe then it reads the EDID and chooses from some dfatabase of profiles? If so , its not clear where tha database is. The display widget had no information about a system monitor profile.

I was able to load ICC Examin and look at some of the provided sample profiles (which is good as had previously failed to compile it on ubuntu) and visualise the gamut in 3D (with a lot of flickering and screen blackouts, presumably a video driver issue).

I was able to look at the provided sample images, the raster ones opened in CinePaint and the vector one in Inkscape.

The livecd would not let me read or write to the internal drives aand claimed that tan external drive had an unsupported filesystem (ntfs) so i was unable to copy sample images, icc profiles or screenshots of gamut visualisations. I will try again to see if it can write to a fat32 SD card.

Concrete suggestions for improvement:
- provide a readme or better, some html documentation to get people started
- explain where the monitor profile comes from, how it is set, how to contribute profiles for your hardware, and how to check it is installed and working correctly
- explain how to start Argyll with the display gui front end
- put the installed programs on the KDE menu (some were but not all)
- allow the user to select English UI for ICC Examin and CinePaint :)

]]> Comment on An other Open Source Colorimeter by Chris Lilley http://www.oyranos.org/2011/11/an-other-open-source-colorimeter/#comment-518 Chris Lilley Wed, 14 Dec 2011 14:06:05 +0000 http://www.oyranos.org/?p=823#comment-518 Richard, thanks for the rapid response. I saw that graph, I was looking though for the actual data not just a raster image of a graph. Perhaps it could be added to the git repo? With wide-gamut ccfl, 'white' (blue with orange filter) led, rgb led and normal ccfl backlights all in comon use, support for multiple ccmx matrices is a very welcome feature, great to see that. There seems to be more than one device called colormunki: the ColorMunki Display which Amazon US sells for USD 139 and the ColorMunki Photo which Amazon US sells for USD 449. The former seems to be a colorimetyer, similar to the i1Display which I have, and the latter seems to be a spectrophotometer (sice it can do printer profiling). Anyway I have preordered a ColorHug, and further discussion is probably better on the dedicated list for it which have joined. Richard, thanks for the rapid response.

I saw that graph, I was looking though for the actual data not just a raster image of a graph. Perhaps it could be added to the git repo?

With wide-gamut ccfl, ‘white’ (blue with orange filter) led, rgb led and normal ccfl backlights all in comon use, support for multiple ccmx matrices is a very welcome feature, great to see that.

There seems to be more than one device called colormunki: the ColorMunki Display which Amazon US sells for USD 139 and the ColorMunki Photo which Amazon US sells for USD 449. The former seems to be a colorimetyer, similar to the i1Display which I have, and the latter seems to be a spectrophotometer (sice it can do printer profiling).

Anyway I have preordered a ColorHug, and further discussion is probably better on the dedicated list for it which have joined.

]]> Comment on An other Open Source Colorimeter by Richard Hughes http://www.oyranos.org/2011/11/an-other-open-source-colorimeter/#comment-517 Richard Hughes Wed, 14 Dec 2011 12:16:06 +0000 http://www.oyranos.org/?p=823#comment-517 I'm not going to argue with you, it's a waste of my time. I’m not going to argue with you, it’s a waste of my time.

]]>