Making color management "just work" using colord
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Hughes, Richard
The colord project intends to make color management just work. In this presentation I will quickly introduce why color management is required, and also the problems introducing an integrated color management workflow. We will compare and contrast the frameworks commonly used in OSX and Windows 7. By discussing the integration points, we will be talking to application developers and platform maintainers in order to shape the future development of colord and the front-ends such as GNOME Color Manager. We will also spend some time exploring the intricacies of an open source color management framework best suitable for display, scanning and printing, and how we can start to provide this functionality. I’ll cover how key projects have already been modified to work with colord, and what application authors still have to do. There will be time left for questions and discussion. It is expected the audience will be moderately technically skilled, and possess a basic understanding of color management.
 Okay, so what are your views on colourful... Colourful... Colourful... So... Good morning. I'm Richard Hughes. I work for Red Hat in the SIP team. I live in London and I've been doing this colour stuff for about a year. I also maintain package kit, no package kit, no power manager, no power manager, no power D and I'm a customer for loads of other projects such as UK and Geneva and stuff. It's been an epic source for the world but I'm pretty new to this whole colour stuff. So in the presentation I'm going to explain to you basic principles like gamut, what an ITC program is, what's important, go through a typical workflow, go through what is required for colour D and key design to be able to promote, go through actually how it works, impact implementation, talk about the session component, in this case the car manager, I've also mentioned the key user. And then we'll go through, so really quickly we can have a lot to talk about. And to answer some of the questions. So these are the questions to the end. Of course hopefully any questions will be answered on the next few slides. So let's get going. So actually colour is really hard. Colour is really just a radio waves which we can process as carolies. You might think the colour is a processing of an object, but actually it depends on the lighting, it might depend on your colour line, it might depend on how many different things, the screen looking at, working on your photo. So actually colours are quite a complicated thing. You really need to make much simpler before you actually mix up the work. So when we did the colour we did it with very different devices. Now just your camera, you can take a photo which can capture millions and millions of colours, more colours than you can take a photo in the brain of the model. Now if we can display them on the screen, we might put them on our digital black panel or a cnt display, which is a big cake of showing a few hundred thousand colours. So if we want to do less, we have to work out how to map colours from a device of loads of colours to a device of a lot less of loads. And then we might print more of our photo out, so you might print out a photo of some kids, some other kids, which might be different again because instead of using light red and blue, we may use a pink, so cyan, magenta, yellow, black. And we have to manage to colour them. There's no way in the world we can make these devices all the same, so the blue of the camera is going to be much bluer than the blue of the printer. But we can tell you some ways to do it right, and also maybe try and make it a little more efficient. Or without that risk of using loads of options and light, but we'll just use them. So to do this, we have to map the colour spaces. So on the left hand side you can see an example of a S-R-G-V. Now the weakness of all shapes is actually what your rights can see. So that's the limit of our human vision system. And the light-shaping area is the colours that they can create. So that's what you made. It's a good approximation of a 10-year-old monitor, the C-R-T-M-O-N-T-A. And it's currently used by most of the toolkits, and now it's confused by most of the internet. As you can see, we can see that loads of colours we can see. We can't express a lot of deep greens, we can't express lots of balloons or wets. So actually it's kind of showing a savage now. Monitor's just showing me more colours. We don't really want to be able to strip ourselves to this very small set. So the limit example shows you what a doggie engine looks like. A doggie engine being a spot to call entity space, which is used by designers because it can express so many more colours. Because it's a well-known space, if you know it don't be, then you can export web-tales in as well. So it's big, because they're more balloons, many more greens, but they're more reds. Now the shape triangle is actually a lot of shape, and it's actually a 3-metre hole. It's a bit more complicated to just try and look. There's a couple of little strokes that come up well. And the last space is a little pro-photo, actually. Now this is a massive space. You can even encode colours, but you can't actually see. It's kind of quite wasteful, but it doesn't mean you can't actually make any more colours. So you might think, you're so okay, this space is bigger, is it not better? Or if they're encode pixels with a bit of pixel, on this small S1GV space, we might have 30 or 40 skin tones, which are really big key colours. Using pro-photo, I should say, because of the larger range, you've got a much closer quantisation. You actually might only have 4 or 5 skin tones. So unless you've got the 16 bit of pixel, it's not great. You can see that each colour space has its advantages and weaknesses, and it's not going to be anything like the same just use this one, just use that one. So this is an example of things that start picking in the winter. Although it has slightly less highlight on the camera, suppose we're rubbing on a frosty floor. It is great, the red is quite clear, the south red looks like a bit more gel-oak. The white is crisp, the black looks sharp. And I think it's important that it's 1960s, well, not that time. Now, all the Nova Springs are very high-confiniture, they come across really low, and it's two years old, my little son. And so the background is kind of dim now, and so it's kind of a bit darker, and the colour looks a bit much now, because it's not as if you could explain. So I printed it on my nice, shiny HD printer, and it came on the right side, so the blacks are pretending to be this money-brown colour. The white, the paper white, isn't white, it's kind of like a light-shaded blue, and the red's a completely different red, it's a much more extra-sour, even if you look. This is a total failure for the user, but the user is printing and registering a photo, and it has very few resemblance to the image. So what can we do? We can't obviously make a printer, but if you like that ink, then it actually has a little coverage. We can't make a print white side for the actual paintbrush itself. What we can show you is just what it's going to look like. So it could be able to make colour-correcting images so they look extra, so they look a bit more representative to the photo. Or could we tell the user what it's going to look like and it's going to look like a print printing kit we've used to tell reference to show the user the actual words of the look-like that they're trying to print. So how do we fix this? We use something called the Nicency Procurement. Now, the Nicency Procurement, we use the finally blob of the user, which characterises either a colour space, like this RGB, a DBRGB, that kind of thing, or it can characterize a device. So you can tell the Nicency Procurement on the display, my print is up, scanner, my camera. And you can have a profile per device. We get this thing from 8 and you can't manage quite the work. It's kind of a digital environment. So for example, for Pixar and Dreamworks, this is what they do. They have the look of the photos and say this is always going to be a problem in the experience. There was an inclination from that to play this job. Now, we have what you think, close to that in nice X, in Windows, or anywhere near in Linux. There's kind of something that we should try to aspire to. Now, with profiles, you might have seen some people might have already downloaded them from the website. Manicaptors try to really help things and provide sort of pre-cured, generic profiles. So if you go to the line of websites for a T61 backup display, you can download the Nicency Procurement. Which is great, you can have a great comment or display. But actually, that's probably the average of 3 of the 4 monitors of production line in some way, in the battery two years ago. But actually, there's a personal experience from something that's snatched to T61. You can buy T61 panels from Taiwan, you can buy it from China, you can get it shiny and you can get it glossy. Try to over-cord all of that to one G-Magnet profile. Kind of misleading thinking you've got color managers to let them actually have it. So really, you've got to be very self-cubrocheted because, I've noticed, the layers get dimmer as they get on top. So, 3 of the raw display is something like an 8th for the bright 20-40. Now, they also get more of that, which is kind of changing your colors as well. It's kind of biodegradable to artists to show them what they're kind of looking like before and after. Now, I like ZX, did this right. It's sort of 3-release to go. They use a system called ColorSync. Most applications for ColorSync nearly on the right side of the color system. They're actually very hard to not be color-matched to other cells. Which is kind of one of these things. Drawbacks in the profile of the screen is actually very difficult to say, because they can leave my image alone. I guess, we'd be able to leave this complaint with the same background, so it generally works really well. Now, whether from the system, first of all, in this color thing, whether it's color model, where there needs to be some vSync profiles obstructed in hours that are only this specific stuff, so you can plug in various blocks of IP. And it kind of worked on this stage. Windows 7 is much better. Many more programs support the system. Many more better-sounding programs that have conveyed our Windows color system in them. That said, most drivers in Windows 7 don't do color management, so you fall back to SRG. So really, the situation by-set is 9 out of 10. Windows 7 is 6 out of 10. And then, at the moment, 1 of the insurance. So what can we do to fix this? Well, this thing of color-d, I can't do that. This thing of color-d, now, color-d is really just a color-d. It doesn't really do much for the store. It really just deals with mapping programs to devices. So I can say to color-d, give me all the color-d parts of my system or give me color-d more of my print-serf or print-serf was the paper. Or I can make the system and give me the list of all color-d parts in the system. So it's really just a high-level kind of framework that can help you to do the wrong thing. It provides a very high-level D by St. Wi. So being D-Rust, I can find that color-d in the store, or the API. But it's very high-level, so you can really make applications that inspire you. And it provides a D by St. Wi. So you can say, do you use an overriding system? I think St. Wi is a little too......cover the screen and associate a specific profile with a specific display. You sort of have a thing of a screen based on the picture and say, the profile is available. You map it to the client. It's pretty usually the message on the screen. And what do people kind of question? You know, there it being a system doing that all one-night for done in a session. I can't explain that. It did really work very well for two scenarios. First, the cups has to be a system statement. So we have a process to sort to 100 feet of......a shot with a card stick. And also things like the GDM script. Those are actually usually locked in. You need to be able to set profiles and work with a protocol. So it's kind of simple, really. I think it's... I hope it's 100 frames. The bottom line is that I know this is a system statement. It's not part of the session statement. So you can see here, it's not the same option. It's not support. It's sort of a new dose to get into the initial panel. It's not going to be cups. Or rather, cups is talking to it. So, the difference is cups is......cups are recommended for the person who is certain to be able to get a top level. Cups are going to create coloration of ice in the company. And have any profiles already in the future. So, the link in coloration. Coloration works. Color sensors, which I'll just give you an example to give you. Which basically means that the rate of fire in the moment makes for giving color. Or a more respect for the risk of catching. Coloration is a direction profile. Coloring of conflict. So you can set things like the overrides. Or you can set a rate of overrides. So it's not the problem in the matter. It also has two depthfaces. The first one is color wargifts. It's the nothing from the profile device. The second one is the depthfaces. And the other one is the storage. Which actually has the kind of assistive virtual profiles and assistive virtual devices. Which kind of seems a bit characteristic. But basically means you can have things like a printer that you know what you're talking about. So if you have a printer that you can put in your photos online. And you can send it to your field like for the shot. So you can set the color bar. So this will bring the sous-tendent. So you can create a print line, and you can actually revise it. And the current classic feature, I'm not sure if it's a family-grown idea. It's a product that's changing. And I think that one of the main components is it talks to the assistive system and the permission of the product. It actually goes into direct access to cells. And the parcel of the product is the top level sort of primary representant in the system. And the top level is the session. The session for the GSM session. The known through the system. I'm just blocking it. Now let's talk to the apps. The reason we're talking to the apps is because the system deals with the access to the apps that the accession is. And it also sets the option on the GSM. And our gamera is supposed to display the operation. We have to do this in the session. The GSM session also loads protocols on the home directory. It does that itself on the price. The reason and reasons. First being price of the product is very low. Second, probably the SELIME. The idea of the assistive demodulating of the root rather than the SELIME directly is a plan for the accession for us to learn. And the third reason being if you're having a cryptopendor actually, you can not even use the number. So the financial data protocols can be used in a bit. And not in the session. Two other things. GSM practices the control center which is the pain plan. Which lets you assign over a rate of protocols to devices. GSM view is kind of like, kind of like, you guys have to use, but not really users. So we can see, all the customer profiles having the same amount of data while having this color space is not going to be a question color search. Now, the printing architecture is kind of complicated. All the time I rewrote the get to roster to interface the quick-comedy now. That's another lot of string. The romantic integration which was the post-stretch also goes to color-de-now. So for a document to be printed, I've got a document being printed from glossy paint, and I'm going to make a protocol here. More for a question and use for the output device. Kind of works. It's a bit of a time-out, but it's kind of complicated. We need to know how it works. So, it's really about loading information really quickly. So just to cover some key points. It's a system dealer. It's a dealer interface. It's system activated. You have to have your color-de-now devices, and you have to do some work to use color-de-now devices. So, for a dedicated device, it's a few very many good stuff. It uses policy care. So, some stuff you might want to use is not to be able to delete the devices but be able to query them. So, you can control what you can possibly do. So, we have one single interface for map-ins, one single interface for virtual devices. And I guess the key things to take out of this is the kind of the things that work with CNA, the color-de-now framework, more than the color-de-now device engine. Others like the ASU maps to other ASU maps, they can do a really good job of taking pixels, and then sort of converting these into color-transform. Now, color-de-now can drive to the near-hat. That's the job of some of the templates that's in that in the virtual-earned stack. There is a high-level sharing between user and the community. So, I talked about choosing the broke-levels of the printers. I'm going to go to the virtual-earned stack for a 3D panel. I would query a lot of color-de-now to get the broke-levels of the printers. Using that, we can have broken-up the match-down to pull back to any virtual-earned stack for any resolution. But the use is on the calibration level of the protocol. It just helps any protocol, any non-strictly protocol, and it's kind of crude in letting us through the documentation. It's already more happily using the color-same, so no blocks in real life. But unlike Apple, we don't actually limit those to three dimensions. This is just a strange box of color-de-now. There's no reason to put it up in front of the mutation, and it had a lot of pecs in our objects. It must be this way, with that, so we're not limited to sort of the unobtrusional logic. Another thing that's determined the content is, basically, the user is almost live. So even if you have a big protocol where it's loaded from the DVD file to the load-game protocol itself, it's kind of the internal protocol. And the user then profiles to fly Steven. Even the protocol doesn't affect the personal plate. The protocol's much better than the original protocol. Similarly, for the slates, you have a protocol that's all to generate from the EDIC in the past four months. That's going to be worse than one that's actually used in the theory or the one on the key to that calibration device. So anything that's all that's been added and done as a protocol heuristic is a soft protocol. All that's because Trump's finding the new part of the partnership protocol. Now, what does it say is that it's fixed? And really, what the protocol limit is, is that the language is what he must have been saying. Luckily, that's kind of gross on them. So the fact is that we want to get the attributes, the flexibility, the features, especially when you're using cool, big, hot color to anything that's up to your HP. Then it can work. So if you're backing all of those together, you need to want to find devices and protocols in a different way. So for a protocol that's more of an eager protocol as a file and has a checksum, I usually have checksum part by the self so it saves time collecting it. But protocol is a kind of trick what you should say. That's protocol with properties, methods, procedures, back and forth. Devices is a bit harder. It's kind of color management specific because a scanner displays, do you have a scanner? You've got two scanners, the same like in the model. It doesn't have a lot of inflection of that to put years later. So it's very easy to do variation. It's a scanner, but I'm not sure how I can use it. It's a great account. It's usually twice model name and vendor name as the key. You can not use it. But for display, there's a significant variation between two different vertical slabs. Are they made of batteries? They might have been more modern than they are. I'm not sure I'm pulling back to anything compared to the channel. That's all it tells us. So, because it's a DOS interface we get loads of stuff free. It's actually really easy to say this is the property, this is the property of the protocol. And so for advice, we can say the device has a protocol. It's a real protocol for the device with different mapping and associations. It's a protocol that we can enter. So here, the X on our main is used in the session to sort of be personal. I mean, there's a lot of stuff on the interface that we could have worked on. So, that brings to the point that it's just a slang, a lot of serial number. Maybe if we explore this this would work with broken device. Rebroken device is first, the name, simple in the session, and then the images, and second, we're doing anything over at the CIS layer, the second is the client. The protocol is definitely the same protocol as the other. The property is not really a protocol. So, I kind of published it. It creates a multiplier for this. First, you use the line of liners to have some kind of screener in three months. So, from this we can tell when the device was modified compared to where it created because that's based on three months that we can screen the snake. It's an approach that we've looked into in that scenario. It's similar with the lot of kit methods to break. So, we can add protocol devices. We can get protocol based on the sort of quality of the biography. We can make a protocol default. So, we can prefer protocol with protocol. And kind of more interesting about color of the object is the candidate methods. This is one of the core methods that say quality of the system. It can start off with color of the core device. Like in the sessions, it's trying to protocol the object. A protocol device will just set the protocol on an effect on the object. And that will help us to think we set the same things like the ECGT, the Econome, Table or any other printing that is an input protocol that we can't still present in the process. And then if the application that's been protocoled in, I know X is precious to it. So, whatever total or automatically time you are, doesn't force any of it itself. It's usually good when it's input. Either a protocol is set or it's that way before. Again, it can similarly be for a literacy constraint for instance, you can ask users to enter their own passwords. They do protocol in there. Or you can ask the root password for their trying to remove the profile. Or any local active users can do anything. SSA users can. If someone has physical access to a computer, there's more to the things that can be changed to the color of the monitor. So, I talked about calibration. And basically it comes down to what you can calibrate. For a scan device, scan device, it might be a case of thinking of proto or a scan device. It's a target. The target is basically very accurately a piece of card. Then there's a color swatch on it. And you start scanning it and take a photo. And then compare what you get as the tip output from the scanner or the studio level. Again, it's very tricky. Because with each target, it's a sticky, it would be exact sort of, exact color coordinate. So, we'll color them in that sheet. And basically, those things are sort of a way to see what happens in the RLC mode's correct protocol. It's a little bit harder to calibrate the display to need something like a calibration tool or a computer to have a pathway. They're about 50 dollars. You basically stick on the screen and RLC has a special screen that follows. We measure and it's a little bit less display to make sure that the protocol is correct. Now, there's two ways to calibrate the monitor. One is kind of easy and you go to one of the calibration services online. Now, while printing out samples of MMI and MMI to see if they can be longer than ICC protocol, that costs about 20, 30 dollars. It's quite a bit worth doing in the UF card to calibrate the total series of MMI's. Roughly, if you're a print shop, then you have six sets of 8 with six types of paper, but the cheap piece is by the $600 tool versus the monitor, which actually allows you to scan the printed samples themselves, get your first sample from the MMI source and actually continue exactly what the real type of characteristics of the test is. These are just three dialogues from the camera manager. They're kind of soft and you might have to do it online. There's no screen design guys who want to read work through the four positives. They're using this how a far-rear calibration process can be. There's no straightness inside, so it can change shape. The other kind of get better. Now, this all sounds kind of cool and I guess a lot of people think you understand the last thing that's crossed up. The standard is GPU built-in kind of like so. The library that we're coming to is Geo-type library. The LG we all need to gloss right away. Of course, a lot of people might want to use this with right-wing software. This is for the interface. You can actually take it to the interface with no people's analysis in words, which is kind of okay to use with right-wing software. But ideally, it's pretty old-fashioned. So, this is how you use Color D on the command line. The idea is most users don't know Color D exists on the user. The color engine of the command line only needs to be set up without the confuses and needs to be fixed up scripts or what do you remember, maybe it's a set or something. There are loads of commands to just get to places which is kind of condensed to be on the slide. It still shows information that you can get out from Color D. It's just that the first sort of lock of commands that you do. The device you're programing for, the device that's serial or the protocol set file on the main. So, it's just a very simple wrap-up allowing it to interface with the proper tool. I have a question about the previous slide. Now I don't have time. Go on. So, I'm used to using that for the last question. There's some translation needed. Oh, yeah. I don't know where I think we have all the questions. I'm used to it. Do you have any questions at the end? Yeah, that's fine. So, you're at the end. So, you're at the end of the demo. So, there's a few more commands. So, realistically, most people are not using applications and drivers that they're using Color D. As it all happens, I'm seeing this without knowing what's going on. So, if there's some new color, I'm going to use this color D to get primary. So, see if my request is sync. Turn to the point where we have some devices. If you're going to do a GLA and you're going to do a GX sync version of the GLA and some more good stuff, which is sort of that. Um, it's very useful. For something like the RStudio game or something, we need to export second state in RStudio, and we want to export photo data in the RGP color space. We don't want immigrants in any sort of random place on the process. So, this is a standard color based in the color space. I'm currently at the time, and I'm doing a color map. So, this is what we're doing with the dependency tool. We're going to use the sort of georgia dependency to use the model bus. It's a good thing because scope of the device that the program has created, so that it comes crashes, but we want to be focused and destroy things that the program has created. Now, no color major is really small front end because we do much talk, and we can match it to the color so it really just creates calls to create files to each other. First profile based on the ID class and coordinates. Then, first profile, which profile added, but basically this bit, and it's the best color of the work to match it, and it's the best for the privacy rules. So, profile added, we check the ID, the ID, the private, the data, to see which one is right there. We can use that if there's screens three months that way. We can also do the bus edit so we can load things like gantt.org or state buses. It's kind of like we understand anything about what a bus is. It's just a simple, easy matching just to get an extensive look at that. So here's some screenshots of no color major. It's just the interesting effects and showing the device on the top part and the effect on the bottom. So, the color rate button comes up in the sense to if there was a period work interface, I can change the profile to that. What you basically do is add color mix. Similarly, in gcbure, in more color mix, this is actually comparing and contrasting to profiles. So if you want more screenshots, just click on color mix to do the more color combinations. And you get information like profile, color count is like 3, whole, if you're at a table, you can say you're on a stand-in, show the image, click on that, it's for a certain beat. So, to recap very quickly, some of the most information you might have now, I talked about working spaces, color gamuts, ICC profiles, I haven't discussed how to combine which work flow, but key concepts and design choices are making color D. Then, as we use color D, be it from R9, blindings or digital emails, we talked about no color mixture. And also this KD version is how it's working. I hope to get this review with KD version for the next week. I'd like to make a thank you guys for supporting me with all this, because I just work on staff and I'm a bit more aware of it. So thanks very much for listening and I'll answer your questions. Thank you. We're looking at the fact that we're one question, dating. No, you answered it. Any questions? Okay, so I just want to make sure I understand this question with us and for us to develop and create a new one to graduate, and to add to the research into this. I've got a piece of this kind of information, and it's a specific one, especially with the best one. And I don't care whether I use it to use color, or to add to the stuff, I just want to be able to use it. I would have to use the wrong to use colors. I think that we're going to be using the bus, and it's really important to be able to use it. I will talk to you in a minute. Well, one of the benefits of this is that it can have all the languages and connectives. It's completely desktop-utual. It's a bit new to work in normal languages. It's a bit nice to be able to do that. But it's easy to read. What do you use, I expect? Color, color, color, color. Color, color, color. Color, color, color. Color, color, color. Color, color, color. Color, color, color. Color, color, color. We're going to have all the all the different options that we're working on for a while. That will be a big thing for people with color. I'm talking on the first page to get some interaction into the first two as well, and then I'm going to say hopefully this is not important to us. It's on very more than we do. Thank you.
 Okay, so what are your views on colourful...  Colourful...  Colourful...  So...  Good morning. I'm Richard Hughes. I work for Red Hat in the SIP team.  I live in London and I've been doing this colour stuff for about a year.  I also maintain package kit, no package kit, no power manager, no power manager,  no power D and I'm a customer for loads of other projects such as UK and Geneva and stuff.  It's been an epic source for the world but I'm pretty new to this whole colour stuff.  So in the presentation I'm going to explain to you basic principles like gamut,  what an ITC program is, what's important, go through a typical workflow,  go through what is required for colour D and key design to be able to promote,  go through actually how it works, impact implementation,  talk about the session component, in this case the car manager,  I've also mentioned the key user.  And then we'll go through, so really quickly we can have a lot to talk about.  And to answer some of the questions.  So these are the questions to the end.  Of course hopefully any questions will be answered on the next few slides.  So let's get going.  So actually colour is really hard.  Colour is really just a radio waves which we can process as carolies.  You might think the colour is a processing of an object,  but actually it depends on the lighting,  it might depend on your colour line, it might depend on how many different things,  the screen looking at, working on your photo.  So actually colours are quite a complicated thing.  You really need to make much simpler before you actually mix up the work.  So when we did the colour we did it with very different devices.  Now just your camera, you can take a photo which can capture millions and millions of colours,  more colours than you can take a photo in the brain of the model.  Now if we can display them on the screen,  we might put them on our digital black panel or a cnt display,  which is a big cake of showing a few hundred thousand colours.  So if we want to do less, we have to work out how to map colours from a device of loads of colours  to a device of a lot less of loads.  And then we might print more of our photo out,  so you might print out a photo of some kids, some other kids,  which might be different again because instead of using light red and blue,  we may use a pink, so cyan, magenta, yellow, black.  And we have to manage to colour them.  There's no way in the world we can make these devices all the same,  so the blue of the camera is going to be much bluer than the blue of the printer.  But we can tell you some ways to do it right,  and also maybe try and make it a little more efficient.  Or without that risk of using loads of options and light,  but we'll just use them.  So to do this, we have to map the colour spaces.  So on the left hand side you can see an example of a S-R-G-V.  Now the weakness of all shapes is actually what your rights can see.  So that's the limit of our human vision system.  And the light-shaping area is the colours that they can create.  So that's what you made.  It's a good approximation of a 10-year-old monitor, the C-R-T-M-O-N-T-A.  And it's currently used by most of the toolkits,  and now it's confused by most of the internet.  As you can see, we can see that loads of colours we can see.  We can't express a lot of deep greens,  we can't express lots of balloons or wets.  So actually it's kind of showing a savage now.  Monitor's just showing me more colours.  We don't really want to be able to strip ourselves to this very small set.  So the limit example shows you what a doggie engine looks like.  A doggie engine being a spot to call entity space,  which is used by designers because it can express so many more colours.  Because it's a well-known space,  if you know it don't be, then you can export web-tales in as well.  So it's big, because they're more balloons,  many more greens, but they're more reds.  Now the shape triangle is actually a lot of shape,  and it's actually a 3-metre hole.  It's a bit more complicated to just try and look.  There's a couple of little strokes that come up well.  And the last space is a little pro-photo, actually.  Now this is a massive space.  You can even encode colours, but you can't actually see.  It's kind of quite wasteful,  but it doesn't mean you can't actually make any more colours.  So you might think, you're so okay,  this space is bigger, is it not better?  Or if they're encode pixels with a bit of pixel,  on this small S1GV space,  we might have 30 or 40 skin tones,  which are really big key colours.  Using pro-photo, I should say,  because of the larger range, you've got a much closer quantisation.  You actually might only have 4 or 5 skin tones.  So unless you've got the 16 bit of pixel, it's not great.  You can see that each colour space has its advantages and weaknesses,  and it's not going to be anything like the same just use this one, just use that one.  So this is an example of things that start picking in the winter.  Although it has slightly less highlight on the camera,  suppose we're rubbing on a frosty floor.  It is great, the red is quite clear,  the south red looks like a bit more gel-oak.  The white is crisp, the black looks sharp.  And I think it's important that it's 1960s, well, not that time.  Now, all the Nova Springs are very high-confiniture,  they come across really low,  and it's two years old, my little son.  And so the background is kind of dim now,  and so it's kind of a bit darker,  and the colour looks a bit much now,  because it's not as if you could explain.  So I printed it on my nice, shiny HD printer,  and it came on the right side,  so the blacks are pretending to be this money-brown colour.  The white, the paper white, isn't white,  it's kind of like a light-shaded blue,  and the red's a completely different red,  it's a much more extra-sour, even if you look.  This is a total failure for the user,  but the user is printing and registering a photo,  and it has very few resemblance to the image.  So what can we do?  We can't obviously make a printer,  but if you like that ink, then it actually has a little coverage.  We can't make a print white side  for the actual paintbrush itself.  What we can show you is just what it's going to look like.  So it could be able to make colour-correcting images  so they look extra, so they look a bit more representative to the photo.  Or could we tell the user what it's going to look like  and it's going to look like a print printing kit we've used  to tell reference to show the user  the actual words of the look-like that they're trying to print.  So how do we fix this?  We use something called the Nicency Procurement.  Now, the Nicency Procurement,  we use the finally blob of the user,  which characterises either a colour space,  like this RGB, a DBRGB, that kind of thing,  or it can characterize a device.  So you can tell the Nicency Procurement on the display,  my print is up, scanner, my camera.  And you can have a profile per device.  We get this thing from 8 and you can't manage quite the work.  It's kind of a digital environment.  So for example, for Pixar and Dreamworks,  this is what they do.  They have the look of the photos  and say this is always going to be a problem in the experience.  There was an inclination from that to play this job.  Now, we have what you think,  close to that in nice X, in Windows,  or anywhere near in Linux.  There's kind of something that we should try to aspire to.  Now, with profiles, you might have seen  some people might have already downloaded them from the website.  Manicaptors try to really help things  and provide sort of pre-cured, generic profiles.  So if you go to the line of websites  for a T61 backup display,  you can download the Nicency Procurement.  Which is great, you can have a great comment or display.  But actually, that's probably the average of 3 of the 4 monitors  of production line in some way,  in the battery two years ago.  But actually, there's a personal experience  from something that's snatched to T61.  You can buy T61 panels from Taiwan,  you can buy it from China,  you can get it shiny and you can get it glossy.  Try to over-cord all of that to one G-Magnet profile.  Kind of misleading thinking you've got color managers  to let them actually have it.  So really, you've got to be very self-cubrocheted  because, I've noticed, the layers get dimmer as they get on top.  So, 3 of the raw display is something like an 8th  for the bright 20-40.  Now, they also get more of that,  which is kind of changing your colors as well.  It's kind of biodegradable to artists  to show them what they're kind of looking like before and after.  Now, I like ZX, did this right.  It's sort of 3-release to go.  They use a system called ColorSync.  Most applications for ColorSync  nearly on the right side of the color system.  They're actually very hard to not be color-matched to other cells.  Which is kind of one of these things.  Drawbacks in the profile of the screen  is actually very difficult to say,  because they can leave my image alone.  I guess, we'd be able to leave this complaint  with the same background, so it generally works really well.  Now, whether from the system, first of all,  in this color thing, whether it's color model,  where there needs to be some vSync profiles  obstructed in hours that are only this specific stuff,  so you can plug in various blocks of IP.  And it kind of worked on this stage.  Windows 7 is much better.  Many more programs support the system.  Many more better-sounding programs  that have conveyed our Windows color system in them.  That said, most drivers in Windows 7  don't do color management, so you fall back to SRG.  So really, the situation by-set is 9 out of 10.  Windows 7 is 6 out of 10.  And then, at the moment, 1 of the insurance.  So what can we do to fix this?  Well, this thing of color-d,  I can't do that.  This thing of color-d,  now, color-d is really just a color-d.  It doesn't really do much for the store.  It really just deals with mapping programs to devices.  So I can say to color-d,  give me all the color-d parts of my system  or give me color-d more of my print-serf  or print-serf was the paper.  Or I can make the system  and give me the list of all color-d parts  in the system.  So it's really just a high-level kind of  framework that can help you  to do the wrong thing.  It provides a very high-level D by St. Wi.  So being D-Rust, I can find that color-d  in the store, or the API.  But it's very high-level,  so you can really make applications  that inspire you.  And it provides a D by St. Wi.  So you can say, do you use an overriding system?  I think St. Wi is a little too... ...cover the screen  and associate a specific profile  with a specific display.  You sort of have a thing of a screen  based on the picture and say,  the profile is available.  You map it to the client.  It's pretty usually the message on the screen.  And what do people kind of question?  You know, there it being a system  doing that all one-night for done in a session.  I can't explain that.  It did really work very well for two scenarios.  First, the cups has to be a system statement.  So we have a process to sort to 100 feet of... ...a shot with a card stick.  And also things like the GDM script.  Those are actually usually locked in.  You need to be able to set profiles  and work with a protocol.  So it's kind of simple, really.  I think it's...  I hope it's 100 frames.  The bottom line is that I know this is a system statement.  It's not part of the session statement.  So you can see here, it's not the same option.  It's not support.  It's sort of a new dose to get into the initial panel.  It's not going to be cups.  Or rather, cups is talking to it.  So, the difference is cups is... ...cups are recommended for the person who is certain  to be able to get a top level.  Cups are going to create coloration of ice in the company.  And have any profiles already in the future.  So, the link in coloration.  Coloration works.  Color sensors, which I'll just give you an example to give you.  Which basically means that the rate of fire  in the moment makes for giving color.  Or a more respect for the risk of catching.  Coloration is a direction profile.  Coloring of conflict.  So you can set things like the overrides.  Or you can set a rate of overrides.  So it's not the problem in the matter.  It also has two depthfaces.  The first one is color wargifts.  It's the nothing from the profile device.  The second one is the depthfaces.  And the other one is the storage.  Which actually has the kind of assistive virtual profiles  and assistive virtual devices.  Which kind of seems a bit characteristic.  But basically means you can have things like  a printer that you know what you're talking about.  So if you have a printer that you can put in your photos online.  And you can send it to your field like for the shot.  So you can set the color bar.  So this will bring the sous-tendent.  So you can create a print line,  and you can actually revise it.  And the current classic feature,  I'm not sure if it's a family-grown idea.  It's a product that's changing.  And I think that one of the main components  is it talks to the assistive system  and the permission of the product.  It actually goes into direct access to cells.  And the parcel of the product  is the top level sort of primary representant  in the system.  And the top level is the session.  The session for the GSM session.  The known through the system.  I'm just blocking it.  Now let's talk to the apps.  The reason we're talking to the apps  is because the system deals with the access  to the apps that the accession is.  And it also sets the option on the GSM.  And our gamera is supposed to display  the operation.  We have to do this in the session.  The GSM session also loads  protocols on the home directory.  It does that itself on the price.  The reason and reasons.  First being price of the product is very low.  Second, probably the SELIME.  The idea of the assistive demodulating of the root  rather than the SELIME directly is a plan  for the accession for us to learn.  And the third reason being if you're  having a cryptopendor actually,  you can not even use the number.  So the financial data protocols  can be used in a bit.  And not in the session.  Two other things.  GSM practices the control center  which is the pain plan.  Which lets you assign over a rate of protocols  to devices.  GSM view is kind of like,  kind of like, you guys have to use,  but not really users.  So we can see,  all the customer profiles  having the same amount of data  while having this color space  is not going to be a question color search.  Now, the printing architecture  is kind of complicated.  All the time I rewrote the  get to roster to interface  the quick-comedy now.  That's another lot of string.  The romantic integration  which was the post-stretch  also goes to color-de-now.  So for a document to be printed,  I've got a document being printed  from glossy paint,  and I'm going to make a protocol here.  More for a question and use for the output device.  Kind of works.  It's a bit of a time-out,  but it's kind of complicated.  We need to know how it works.  So, it's really about  loading information really quickly.  So just to cover some key points.  It's a system dealer.  It's a dealer interface.  It's system activated.  You have to have your color-de-now devices,  and you have to do some work  to use color-de-now devices.  So, for a dedicated device,  it's a few very many good stuff.  It uses policy care.  So, some stuff you might want to use  is not to be able to delete the devices  but be able to query them.  So, you can control what you can possibly do.  So, we have one single interface for map-ins,  one single interface for virtual devices.  And I guess the key things  to take out of this is the kind of  the things that work with CNA,  the color-de-now framework,  more than the color-de-now device engine.  Others like the ASU maps to other ASU maps,  they can do a really good job of taking pixels,  and then sort of converting  these into color-transform.  Now, color-de-now can drive to the near-hat.  That's the job of some of the templates  that's in that in the virtual-earned stack.  There is a high-level sharing  between user and the community.  So, I talked about choosing  the broke-levels of the printers.  I'm going to go to the virtual-earned stack  for a 3D panel.  I would query a lot of color-de-now  to get the broke-levels of the printers.  Using that, we can have  broken-up the match-down  to pull back to any  virtual-earned stack for any resolution.  But the use is on the calibration  level of the protocol.  It just helps any protocol,  any non-strictly protocol,  and it's kind of crude  in letting us through  the documentation.  It's already more happily using the color-same,  so no blocks in real life.  But unlike Apple, we don't actually limit  those to three dimensions.  This is just a strange box of color-de-now.  There's no reason to put it up  in front of the mutation,  and it had a lot of pecs in our objects.  It must be this way, with that,  so we're not limited to  sort of the unobtrusional logic.  Another thing that's determined  the content is, basically,  the user is almost live.  So even if you have a big  protocol where  it's loaded from the DVD file  to the load-game protocol itself,  it's kind of the internal protocol.  And the user then profiles  to fly Steven. Even the protocol  doesn't affect the personal plate.  The protocol's  much better than the original protocol.  Similarly, for the slates,  you have a protocol that's  all to generate from the  EDIC in the past four months.  That's going to be worse than one  that's actually used in the theory  or the one on the key to that calibration device.  So anything that's all that's been added  and done as a protocol heuristic  is a soft protocol.  All that's because Trump's finding the new  part of the partnership protocol.  Now, what does it say  is that it's fixed?  And really, what the protocol limit  is, is that the language  is what he must have been saying.  Luckily, that's kind of gross on them.  So the fact is that we want to get  the attributes, the  flexibility, the  features, especially when you're  using cool, big, hot color  to anything that's up to your HP.  Then it can work.  So if you're backing  all of those together,  you need to want to find devices and protocols  in a different way. So for a protocol  that's more of an eager protocol as a file  and has a checksum,  I usually have checksum part by the self  so it saves time collecting it.  But protocol is a kind of trick what you should say.  That's  protocol with properties,  methods, procedures, back and forth.  Devices  is a bit harder.  It's kind of color management specific  because a scanner  displays, do you have a scanner?  You've got two scanners, the same like in the model.  It doesn't have a lot of inflection  of that to put years later.  So it's very easy to do variation.  It's a scanner,  but I'm not sure how I can use it.  It's a great account.  It's usually twice  model name and vendor name as the key.  You can not use it.  But for display, there's a significant  variation between two different  vertical slabs.  Are they made of batteries?  They might have been more modern than they are.  I'm not sure  I'm pulling back to  anything compared to the  channel.  That's all it tells us.  So, because it's a DOS interface  we get loads of stuff  free. It's actually really easy to say  this is the property,  this is the property of the protocol.  And so for advice, we can say  the device has a protocol.  It's a real protocol for the device  with different mapping and associations.  It's a protocol that we can enter.  So here, the X on our main  is used in the session to  sort of be personal.  I mean, there's a lot of stuff  on the interface  that we could have worked on.  So, that brings to the point  that it's just a slang, a lot of serial  number. Maybe if we explore this  this would work with broken device.  Rebroken device is  first, the name, simple in the session,  and then the images, and second,  we're doing anything over at the  CIS layer, the second  is the client.  The protocol is definitely the  same protocol as the other. The  property is not really a protocol.  So, I kind of  published it.  It creates a multiplier for this.  First, you use the line of liners  to have some kind of screener in three months.  So, from this we can tell  when the device was  modified compared to where it created  because that's based on  three months that we can  screen the snake. It's an  approach that we've looked into in that scenario.  It's similar with the  lot of kit methods to break.  So, we can add protocol devices.  We can get protocol based on  the sort of quality of the biography.  We can  make a protocol default.  So, we can  prefer protocol with protocol.  And kind of more interesting about  color of the object is the  candidate methods. This is one of  the core methods that say quality of the  system. It can start off with color of the  core device. Like in the  sessions, it's trying to protocol the  object. A protocol device will just  set the protocol on an effect on the object.  And that will help us to think we set  the same things like the ECGT, the  Econome, Table or any other printing  that is an input protocol that  we can't still present in the  process. And then if the application  that's been protocoled in, I know  X is precious to it. So, whatever  total or automatically time you  are, doesn't force any of it itself.  It's usually good when it's input.  Either a protocol is set or it's  that way before.  Again, it can similarly be  for a literacy constraint for instance,  you can ask users to enter their own  passwords. They do protocol in there.  Or you can ask the root password for  their trying to remove the profile.  Or any local active users  can do anything.  SSA users can.  If someone has  physical access to a computer, there's  more to the things that can be changed to  the color of the monitor.  So, I talked about  calibration.  And basically it comes down to what  you can calibrate. For a scan  device,  scan device, it might be a case of  thinking of proto or a scan  device. It's a target.  The target is basically very accurately  a piece of card.  Then there's a color swatch on it.  And you start scanning it and take a photo.  And then  compare what you get as the tip  output from the scanner  or the studio level.  Again, it's very tricky. Because with each  target, it's a sticky, it would be exact  sort of, exact color coordinate.  So, we'll color them in that sheet.  And basically, those things are sort of  a way to see what happens in the  RLC mode's correct protocol.  It's a little bit harder to calibrate  the display to need something  like a calibration tool  or a computer to have a pathway.  They're about 50 dollars.  You basically stick on the screen  and RLC has a special screen  that follows. We measure and  it's a little bit less display to  make sure that the protocol  is correct.  Now, there's two ways to calibrate  the monitor. One is kind of easy  and you go to  one of the calibration services online.  Now, while printing out  samples of MMI and MMI  to see if they can be longer than  ICC protocol, that costs about  20, 30 dollars. It's quite a bit  worth doing in the UF card to  calibrate the total series of MMI's.  Roughly, if you're a print shop,  then you have six sets of 8 with six  types of paper, but the cheap piece  is by the $600 tool  versus the monitor, which actually  allows you to  scan the printed samples themselves,  get your first sample from the MMI source  and actually continue  exactly what the real type of  characteristics of the test is.  These are just three dialogues  from the camera manager. They're kind of  soft and you might have to do it online.  There's no screen design guys  who want to read work through the four  positives. They're using this how a  far-rear calibration process can be.  There's no straightness inside, so it can change  shape. The other kind of get better.  Now, this all sounds kind of cool  and I guess a lot of people think you  understand the last thing that's crossed up.  The standard is GPU built-in  kind of like so. The library  that we're coming to  is Geo-type  library. The LG  we all need to gloss right away.  Of course, a lot of people  might want to use this with  right-wing software.  This is for the interface.  You can actually take it to the interface  with no people's analysis in words,  which is kind of okay to use with right-wing software.  But ideally, it's  pretty old-fashioned.  So,  this is how you use Color D  on the command line. The idea is  most users don't  know Color D exists on the user.  The color engine of the command line  only needs to be set up  without the confuses and needs to be  fixed up scripts or what do you  remember, maybe it's a set or something.  There are loads of commands to just get to places  which is kind of condensed  to be on the slide. It still shows information  that you can get out from Color D.  It's just that the first sort of lock  of commands that you do. The device  you're programing for, the device that's  serial or the protocol set file on the main.  So, it's just a very simple wrap-up  allowing it to interface  with the proper tool.  I have a question about the previous slide.  Now I don't have time.  Go on.  So, I'm used to using that for the last question.  There's some translation needed.  Oh, yeah.  I don't know where I think we have all the questions.  I'm used to it.  Do you have any questions at the end?  Yeah, that's fine.  So, you're at the end.  So, you're at the end of the demo.  So, there's a few more commands.  So, realistically, most people  are not using applications and drivers  that they're using Color D.  As it all happens, I'm seeing this  without knowing what's going on.  So, if there's some new color,  I'm going to use this color D  to get primary.  So, see if my request is sync.  Turn to the point where we have some devices.  If you're going to do a GLA  and you're going to do a GX sync version  of the GLA and some more good stuff,  which is sort of that.  Um,  it's very useful.  For something like the RStudio game  or something, we need to export  second state in RStudio,  and we want to export photo data  in the RGP color space.  We don't want immigrants in any sort  of random place on the process.  So, this is a standard  color based in the color space.  I'm currently at the time,  and I'm doing a color map.  So, this is what we're doing  with the dependency tool.  We're going to use  the sort of georgia dependency  to use the model bus.  It's a good thing because  scope of the device that the program  has created, so that it comes  crashes, but we want to be focused  and destroy things  that the program has created.  Now, no color major is really  small front end because we do much talk,  and we can match it to the color  so it really just creates  calls to create files to each other.  First profile based on the ID  class and coordinates.  Then, first profile,  which profile added,  but basically this bit,  and it's the best color of the work  to match it, and it's the best  for the privacy rules.  So, profile added, we check the  ID, the ID, the private, the data,  to see which one is right there.  We can use that if there's screens  three months that way.  We can also do the bus edit so we can load things  like gantt.org or state buses.  It's kind of like we understand anything  about what a bus is.  It's just a simple, easy matching  just to get an extensive look at that.  So here's some screenshots of  no color major. It's just the interesting  effects and showing the device  on the top part and the effect on the bottom.  So, the color rate button  comes up in the sense to  if there was  a period work interface,  I can change the profile to that.  What you basically do is add color mix.  Similarly, in gcbure,  in more color mix, this is actually  comparing and contrasting to profiles.  So if you want more screenshots,  just click on color mix to do the  more color combinations.  And you get information like profile,  color count is like 3,  whole, if you're at a table,  you can say you're on a stand-in, show the image,  click on that, it's for a certain beat.  So, to recap very quickly,  some of the most information you might have now,  I talked about working spaces,  color gamuts,  ICC profiles,  I haven't discussed how to combine  which work flow, but key concepts  and design choices are making color D.  Then, as we use color D,  be it from R9, blindings or  digital emails, we talked about no color  mixture. And also this  KD version is how it's working.  I hope to get this review with KD  version for the next week.  I'd like to make a thank you guys  for supporting me with all this,  because I just work on staff  and I'm a bit more aware of it.  So thanks very much for listening  and I'll answer your questions.  Thank you.  We're looking at the fact  that we're one question, dating.  No, you answered it.  Any questions?  Okay, so I just want to make sure  I understand this question with us  and for us to develop and create  a new one to graduate,  and to add to the research into this.  I've got a piece of this kind of  information, and it's a specific  one, especially with  the best one.  And I don't care  whether I use it  to use color, or to add  to the stuff, I just want to be  able to use it. I would have to use the wrong  to use colors.  I think that we're going to be using  the bus, and it's really  important to be able to use it.  I will talk to you in a minute.  Well, one of the benefits of this  is that it can have  all the languages and connectives.  It's completely desktop-utual.  It's a bit new to work in normal  languages. It's a bit nice to be able to do that.  But it's easy to read.  What do you use, I expect?  Color, color, color, color.  Color, color, color.  Color, color, color.  Color, color, color.  Color, color, color.  Color, color, color.  Color, color, color.  We're going to have all the  all the different options that we're  working on for a while. That will be a big  thing for people with color.  I'm talking on the first page to  get some interaction  into the first two as well, and then  I'm going to say hopefully this is not  important to us.  It's on very more  than we do.  Thank you.
Making_color_management__just_work__using_colord_0_59.png Making_color_management__just_work__using_colord_60_311.png Making_color_management__just_work__using_colord_312_383.png Making_color_management__just_work__using_colord_384_491.png Making_color_management__just_work__using_colord_492_863.png Making_color_management__just_work__using_colord_864_1871.png Making_color_management__just_work__using_colord_1872_2639.png Making_color_management__just_work__using_colord_2640_4499.png Making_color_management__just_work__using_colord_4500_7619.png Making_color_management__just_work__using_colord_7620_9899.png Making_color_management__just_work__using_colord_9900_12623.png Making_color_management__just_work__using_colord_12624_12755.png Making_color_management__just_work__using_colord_12756_12803.png Making_color_management__just_work__using_colord_12804_14795.png Making_color_management__just_work__using_colord_14796_17243.png Making_color_management__just_work__using_colord_17244_22391.png Making_color_management__just_work__using_colord_22392_23363.png Making_color_management__just_work__using_colord_23364_25067.png Making_color_management__just_work__using_colord_25068_26399.png Making_color_management__just_work__using_colord_26400_27647.png Making_color_management__just_work__using_colord_27648_28247.png Making_color_management__just_work__using_colord_28248_30143.png Making_color_management__just_work__using_colord_30144_32243.png Making_color_management__just_work__using_colord_32244_34439.png Making_color_management__just_work__using_colord_34440_37763.png Making_color_management__just_work__using_colord_37764_38699.png Making_color_management__just_work__using_colord_38700_39467.png Making_color_management__just_work__using_colord_39468_39947.png Making_color_management__just_work__using_colord_39948_40439.png Making_color_management__just_work__using_colord_40440_41195.png Making_color_management__just_work__using_colord_41196_41819.png Making_color_management__just_work__using_colord_41820_42347.png Making_color_management__just_work__using_colord_42348_43571.png Making_color_management__just_work__using_colord_43572_44123.png Making_color_management__just_work__using_colord_44124_44723.png Making_color_management__just_work__using_colord_44724_45491.png Making_color_management__just_work__using_colord_45492_45803.png Making_color_management__just_work__using_colord_45804_46079.png Making_color_management__just_work__using_colord_46080_46259.png Making_color_management__just_work__using_colord_46260_46307.png Making_color_management__just_work__using_colord_46308_46355.png Making_color_management__just_work__using_colord_46356_46403.png Making_color_management__just_work__using_colord_46404_46619.png Making_color_management__just_work__using_colord_46620_46667.png Making_color_management__just_work__using_colord_46668_48839.png Making_color_management__just_work__using_colord_48840_48887.png