Visual representations of color spaces

I copied these diagrams from the program called Color Space ...
Can be downloaded from here: COULEUR.ORG
I think that it draws spectral locus on xyY by just plotting matching x, y and Y values for every interval of monochromatic lights on the spectrum ... just like we draw the locus line in XYZ by plotting matching tristimulus values X, Y and Z.
Because the underlying data for the most saturated colors human can see is CIE XYZ color matching functions, I think that we can draw the line of spectral locus in every model originated from CIE XYZ by just making necessary transformations to the XYZ tristimulus values for the intended model.
3D representation of the entire human gamut is more tricky, I think. I will ask about it, after getting your confirmation about the spectrum locus.

A set of three numbers in xyY or XYZ defines a color. 
How does it look? How can it be reproduced?
A good occasion to go back to the roots.
The CIE color system is essentially based on the work of Hermann Graßmann,
one of the greatest scientists in the 19th century [1].
Mostly his four laws are quoted [2], but it boils down to this [3]:
"The whole set of color stimuli constitutes a linear vector space,
named tristimulus space."
Colors behave like vectors in a three-dimensional space. A color is
characterized by three numbers. A fourth number would be redundant
(linearly dependent). A color is not characterized by just one spectrum. For
one color exists an arbitrary number of different spectra, called metamers.
The explanation of Graßmann's laws via spectra [4] is wrong.
Nobody knows what a color 'really' is. Acccording to the philosopher Kant,
we don't know what any object in the space 'really' is. We have just an
impression by our senses, eventually enhanced by instruments.
Colors are described by comparison with reference colors. For length and
weight we need references as well: the meter, the kilogramm.
Reference colors are (for instance) the three CIE primaries, spectral colors
with well defined wavelengths (it's not important, that the first experiments
were executed with a different set). Let's say R,G,B.
According to Graßmann one needs exactly three 'primaries'. This should
have ended a long dispute: three or four?, but it didn't.
Now we can use these spectral colors as base vectors of a coordinate system.
According to Kant, humans have an a-priori idea of space (without any proof),
where we can position objects. By intuition the axes are orthogonal.
Any other color can be described by a linear combination of the three primaries,
according to Graßmann exactly in a vector space. Color matching means:
find the three weights for the primaries to match a given (numerically unknown)
color.
Unfortunately, one needs for the matching of some colors negative weight factors,
which is possible by the concept of vector space, but somewhat disturbing for
real color mixing.
In RGB we can describe a new vector space by base vectors X,Y,Z, which form
a non-orthogonal coordinate system. All colors have non-negative coordinates X,Y,Z
and this construct has the funny feature, that luminance is identical with Y,
whereas the 'imaginary primaries' X and Z don't have luminance. Mathematically
this is not a problem.
The relation between the two spaces is given by a matrix Cxr and its Inverse:
X=(X,Y,Z)'  (column vectors)
R=(R,G,B)'
X=Cxr R
R=Crx X =Cxr^-1 X
Conventionally we draw XYZ as a cartesian coordinate system (with orthogonal axes),
and R,G,B is the set of non-orthogonal base vectors – the arrangement has been swapped.
There is no natural law, which of the coordinate systems has to be shown as a cartesian.
XYZ is universal. Other RGB-systems with new primaries can be added, either as
working spaces like sRGB, aRGB or pRGB (ProPhotoRGB, which uses two non-physical
primaries, which doesn't surprise, because we got used to entirely non-physical primaries
X,Y,Z),  or device RGB systems like monitor spaces. Each RGB system is related to XYZ
using a matrix, thus we can transform as well from one RGB-system to another.
Now it's possible to render a threedimensional visualization of a color space by appropriate
colors, for instance aRGB. But for a monitor these colors would be clipped almost at the
sRGB boundary.
Of course it's not possible to render pRGB correctly, because the blue and green primary
are outside the human gamut, and the red primary would be too dark. Therefore it's wise,
to use pRGB only for regions or real world colors.
There might be still an objection: the reference system contains only spectral colors.
How are the little saturated colors looking? This had been clarified by Graßmann: the vector
addition of any two colors is valid mathematically and by appearance.
These explanations may also help to end the dispute about the 'basic colors', especially
for painting. Many artists have invented their own system. The answer is simple: basic
colors are like primaries. Their location in the XYZ-space defines, which colors can be
created with positive weight factors or mixing ratios. By the way: one shouldn't worry here
about the difference between additive and subtractive color mixing.
One may have serious doubts, whether Graßmann's laws and the whole CIE colorimetry
is really valid, especially considering numerous optical illusions [5] and all these special
effects in color appearance, like Helmholtz-Kohlrausch and other nonlinearities.
It's perhaps surprising, that CIE colorimetry works so very well for image processing and
device calibration for monitors, printers and cameras.
Finally I would like to mention another scientist, which is not as popular as others,
probably because his work is mathematically difficult: Jozef B.Cohen [6].   
His work has been continued by William Thornton, Michael Brill and James Worthey
(for a further search).
Best regards --Gernot Hoffmann
[1] Hermann Günther Graßmann (Grassmann)
http://en.wikipedia.org/wiki/Hermann_Grassmann
[2]
http://de.wikipedia.org/wiki/Gra%C3%9Fmannsche_Gesetze
[3] Claudio Oleari
http://www.slidefinder.net/o/oleari10/32197498/p3
(6th slide).
[4]
http://en.wikipedia.org/wiki/Grassmann%27s_law_%28optics%29
[5]
http://www.michaelbach.de/ot/index.html
[6]
Jozef B.Cohen
Visual Color and Color Mixture
http://books.google.de/books?id=W8QeI5di7t4C&pg=PR13&lpg=PR13&dq=cohen+color&source=bl&ots =aYGoI0I99g&sig=IJEgdJjk3yDhi-1NvTD4GdyUIXk&hl=de&sa=X&ei=614hVM_dFsrMyAPbzoDwCA&ved=0CGsQ 6AEwCA#v=onepage&q=cohen%20color&f=false

Similar Messages

  • Lightroom's 4 color "spaces"

    I’m working on designing an advanced photography course. This course makes use of Lightroom and Photoshop in the photographic workflow.
    I’m learning and researching myself as I go along, and I feel I have reached a ceiling on what I can work out from the sources at my disposal thus far.
    So I am turning here for help.
    I am trying to clarify how tones and colours are affected from the actual scene through to the printed page. This might seem like overkill to some. However, there is a lot of misunderstanding and confusion, not to mention heated discussions amongst photographers about these issues. I’m experimenting with metering and colour / tone targets and my calculations are only meaningful if I understand how tones and colours are affected at every stage of the workflow.
    Here’s how I understand it:
    There are 4 (sort of) Colour “spaces” in Develop where a real-time dynamic preview of an image is rendered
    1.       The “viewing space” (ProPhotoRGB Chromaticity co-ordinates, sRGB gamma)
    2.       The “computational space” (ProPhotoRGB chromaticity co-ordinates, linear gamma – “MelissaRGB”)
    (Martin Evening’s Lightroom 3 book published by Adobe press - Appendix B, section on color space page 628-632)
    Below that, things get a little fuzzy. According to Jeff Schewe (Real World Camera RAW for CS5, page 32) there is a sort of
    3.            “Native Camera Space” and of course there is the
    4.            RAW data in the file on disk.
    So to generate the dynamically rendered preview, the image goes through the four “layers” as follows (from bottom to top). This is almost certainly flawed, but one has to start somewhere when trying to work things out :-)
    1. The RAW file is read from disk. Colorimetric interpretation is performed using a camera profile (e.g. Adobe Standard for whatever camera it is you are using). This process puts the image data into “Native camera space” (“Plotted” onto CIE XYZ with D50 white point)
    2. In “Native camera space, the scene white balance (as selected by user, guessed by Lightroom or reported by camera) as well as additional camera calibration panel matrix tweaks “informs” the colorimetric conversion into Lightroom’s “computational space” e.g. Melissa RGB. The colorimetric definition of camera RGB primaries and white is re-DEFINED. The demosaicing as well as chromatic aberration corrections are performed in “native camera space”
    3. Almost all image processing calculations occur computationally in the  “MelissaRGB Lightroom computational space”
    4. What is displayed on the screen, however, has an sRGB tone curve applied. This represents the “viewing” space. The histogram is generated from this and the RGB colour percentage readouts are generated from this as well. In addition, some slider controls from user input are weighted back through the tone curve into the computational space below.
    Could someone from Adobe kindly help me to clarify the steps? Eric are you reading this? :-)
    Thanks in advance

    Sandy - Thanks for the link. The spreadsheets you posted on your site is quite helpful.
    Jao – I think what you said goes to the heart of what I am trying to achieve here: “Photograph a grey target at the exact same exposure with the exact same lighting but with different cameras and you'll end up with different values in the raw files” Which is why I encourage photographers to experiment with their cameras in order to understand exactly how the camera will respond in the heat of a real shoot. Set up a scene; take a picture, open in Lightroom. What is clipped and why? Use a reflective spot meter. Repeat. Use a hand held incident meter. Repeat. How much can you reliably recover? Are you happy with what your meter considers the mid-point (and what you set your exposure for on the camera) or do you need to compensate? Just how much latitude do you have between what your camera histogram shows as a blown out highlight and what Lightroom shows as a blown out highlight. This relates to tone. I could go on with more examples, but by now, I am (hopefully) making more sense.
    I’m merely trying to clarify that which is already public in order to form a coherent mental picture. And by mental picture I do not mean an accurate representation of the minutiae and maths involved. Think of a subway map. It represents a bird’s eye view of a transportation system in a logical fashion, yet it bears almost no resemblance to the cartographical reality of the physical topography. I really don’t care where the tunnels go, how they were dug, how they are maintained or where they twist and turn. What I AM looking for is a logical (not physical) map. This map tells me where the different lines begin and end, and where I can change from one line to the other. The most important quality of the map as a whole is that it provides context. You can tell, at a glance, how different lines interact with each other and even how it links to other entities such as bus stations or public landmarks.
    As many have rightfully pointed out, I should not have to care about the maths/secret sauce/internal calculations. And I don’t. In addition, I am a very happy Lightroom user and I am very comfortable using it. I know what a user needs to know to get his picture from A to B. There is no shortage of information on how to accomplish that.
    It might help if I illustrate what I am trying to do below:
    Please excuse the low resolution, the maximum height allowed for upload is 600 pixels. The picture below goes on the bottom left of the "layer" picture above.
    Even though there are certainly many mistakes in my diagram, this is a helpful visualisation. I derived this diagram from publicly available information. As the subway map, this is a logical (not physical) representation that provides context in a visual form. With a little help from people like Eric I am sure I can correct and expand it. The net result is an enhanced understanding of Lightroom and ACR and where it fits into the photographic process, both in terms of tone and colour.
    I am not posting the entire chart here since I am not even certain that a 4 “layered” representation is an appropriate logical representation. I posted the spine of the chart with the 4 “layers” and one part that elaborates on the colorimetric interpretation between the two bottom layers. Comments and corrections are welcomed. And I am convinced that this can be accomplished without divulging anything confidential.

  • HSB Color Space Question - How Many Colors Are There In Photoshop

    Hello guys, I have a sort of basic question that I have been trying to figure out for a few days.
    I am trying to find out how many colors there are in the Color Picker  when the Hue radio button is selected.
    I know there are 256^3 RGB (#Hex) colors, and I am trying to find some relationship when I am coloring with HSB color space in Photoshop.
    It just confuses me because the Hue slider goes from 0-359 and the S and B goes from 0-99...
    So how many HSB colors in Photoshop are there?  Am I missing out on some colors by using HSB color space in Photoshop as oposed to using RGB?
    Are there the exact same amount?  Are there more and there are duplicates in HSB space mode?
    Thank you all for all your help, much appreciated
    Travis

    misterfowly wrote:
    I know there are 256^3 RGB (#Hex) colors, and I am trying to find some relationship when I am coloring with HSB color space in Photoshop.
    It just confuses me because the Hue slider goes from 0-359 and the S and B goes from 0-99...
    So how many HSB colors in Photoshop are there?  Am I missing out on some colors by using HSB color space in Photoshop as oposed to using RGB?
    The deficiency of such mathematical models is that they do not take into account noise and human perception. In an 24 bit RGB space (8 bits per channel) there may be 16 million colors, but this assumes that there are 256 discrete levels in each color channel. You could increase the number of colors by using a 48 bit space. In practice, noise will reduce the number of discrete levels, and this will vary with the camera and ISO used in that camera. For example, consider the Nikon D5000 as evaluated by DXO. At  base ISO the camera can resolve only 21.8 bits of color information and this decreases to 15.6 bits at an effective ISO of 2079 (camera ISO setting of 3200).
    http://www.dxomark.com/index.php/eng/Image-Quality-Database/Nikon/D5000
    Then you have to consider how many of these colors can actually be differentiated by the human visual system. If you can't see a difference, it really doesn't matter.These differences are difficult to quantitate. One such effort uses MacAdam ellipses shown in this Wikipedia article on a CIE 1931 xy plot. How many of these ellipses are contained in the CIE xy space? The DXO site has similar ellipses for real world camera images.
    http://en.wikipedia.org/wiki/MacAdam_ellipse
    See this RIT FAQ for a more sober real world analysis. The actual number of colors is in the millions, but likely not 16 million.
    http://www.cis.rit.edu/mcsl/outreach/faq.php?catnum=1#219
    In a real world situation, I would not be overly concerned about differences between the RGB and HSB spaces, but one could increase precision by using a 48 bit space.

  • New ICC v4 sRGB Color Space May Prevent Clipping Converting From ProPhoto RGB

    Just discovered and tried out this new sRGB color space downloaded from this page:
    http://www.color.org/srgbprofiles.xalter
    Here's a cropped demo with histograms of a raw image I've been working on in ProPhotoRGB in ACR 3.7 and CS2:
    http://www.flickr.com/photos/26078880@N02/2874068887/sizes/o/
    Please disregard the PRMG name in the demo. I got confused as to which was which on that site and thought that this version of sRGB was a PRMG=(Perceptual Reference Medium Gamut) profile. It's called sRGB_v4_ICC_preference.icc.
    Note the different color shifts using the Perceptual intent and unchecking Black Point Compensation=(BPC). Neat little features embedded in this profile, but not sure about how it renders certain colors close to clipping in the shadows. That site doesn't recommend mixed use of ICC v4 with v2 color spaces and output device profiles but I did it anyway just to see what it does.
    Who knows this may be the equivalent of handing scissors to children, but I'm just one of those curious children and thought I'ld share anyway.

    I'll try to respond to a few items above.
    The digital values in a Pro Photo RGB file should generally be the same as for a ROMM RGB file. The exception is that all possible Pro Photo RGB values are "legal" but not all ROMM RGB values are "legal." ISO 22028-2 restricts the legal ROMM values to those with PCS LAB values between 0 and 100 L* and -128 to +128 a* and b*.
    There is no enforcement if you use the illegal values in a ROMM file but as some of these values do not represent possible colors this is not advisable. I think it is good practice to try to stay mostly inside the ICC v4 PRM gamut with Pro Photo/ROMM images. You can check this using the gamut warning profile on the ICC site.
    If you have a Pro Photo RGB image you should just assign the ROMM profile to it. Converting to ROMM RGB should not change anything in the ideal sense but there is the possibility to introduce rounding errors and mismatch black points.
    The main difference between the Pro Photo RGB profile and the ROMM RGB profile is the former includes black scaling to zero (as is common with v2 color space and display profiles) and the latter does not (as is required with v4 profiles).
    In the duck picture, the reason for the difference is the ROMM profile black is at L*=3 so this is where the lowest blacks land when converting MRC to v2 sRGB (which has the sRGB blacks scaled to L*=0). In this case leaving BPC off is analogous to turning on "Simulate Black Ink" in Photoshop Proof Setup.
    All the ACR color space choices are v2 profiles with black scaling. If you want a v4 profile embedded you have to assign it (if you have a corresponding v4 profile) or convert to it.
    Both the sRGB and PRM gamuts fit within the ROMM RGB legal encoding range, but if you use a v2 profile with black scaling you should always turn on BPC when combining with a v4 profile. Otherwise the v4 profile will think the v2 profile represents a device with an infinite dynamic range. When BPC is on the Color Engine scales the black point of the source profile to the black point of the destination profile.
    The sRGB gamut extends outside the PRM gamut in some places, and the PRM gamut extends outside the sRGB gamut in other places. If you convert using a colorimetric intent in either direction some of the gamut will be clipped. The purpose of the sRGB v4 perceptual transforms is to minimize clipping in both directions.
    I can't do this justice here but basically scene-referred images are encodings of the scene colors and output-referred images are encodings of the picture colors on some medium for which the picture colors have been optimized. You can make a scene-referred image by setting the ACR sliders (except the white balance sliders) to zero and the curves tab to linear. You make an output-referred image when you adjust the sliders to non-zero values to make a nice picture as viewed on some medium. For example you might adjust the sliders differently to get the best results printing colorimetrically on glossy photo paper vs. on plain office paper.
    Often an important part of the transform to output-referred includes a midtone contrast and saturation boost. While there will likely be some highlight and may be some shadow compression, it is misleading to think of this transform only as a compression to some output medium dynamic range. In some cases the output medium dynamic range is larger than that of the scene.
    Usually the transform to output-referred is more complicated than a simple gamma function.
    Regardless of the image state (scene-referred or output-referred) the sRGB, Adobe RGB, or Pro Photo RGB nonlinearities will be applied to create the image data that you open into Photoshop.
    We are working in the ICC to prepare more information for posting on this topic.

  • What color space as base in a brand guide?

    What color space forms the base of a color brand guide? How do you start in terms of color spesifications? When I look at most guides it seems that Pantone is always the base, then CMYK, then RGB and Hex? Is RGB and Hex always gonna be a dithered version of the CMYK values or is it best practise to hand pick each one to make them look as close to the CMYK as possible? Is Pantone always mentioned first in the list because that's where the designer started?
    Also, is best practise to mimmick the CMYK and Pantone colors so that the RGB and hex values look like them? Seems to me that most brand guides / visual manuals are made firstly for print, then they add the screen based color spaces.
    In the enclosed example I also observe that the complete values are not always listed, in many cases the Y and K is missing in the CMYK values, does that mean it doesn't contain any black, or is it simply meaning zero? It rarerly occurs with the other color spaces.

    For web, email and screen in general it should always be sRGB. Then you can be fairly certain that it will display correctly (more or less) in any scenario. sRGB wil also work for print (inkjet), it's just that many colors that can be printed are out of sRGB gamut, so it's a restriction that doesn't need to be there. sRGB is a small color space that can't reproduce very saturated colors - they're just clipped. So it's better to start with a larger space like Adobe RGB or even ProPhoto.
    For editing purposes you want a large color space simply to have headroom and not hit the wall at every move. The final destination may well be a smaller space, like a printer profile. The software then converts to that destination profile as it goes to the printer. You can soft proof to the printer profile to get an impression of how the final result will look.
    You can print directly from InDesign, but the typical InDesign workflow is to export a finished PDF. That is where you specify a final destination profile for the whole document, whether a certain CMYK profile for offset press, or an RGB profile for screen. So you have your master InDesign file, and output PDFs for each destination. The InDesign file can contain placed RGB images in any color space, while text and graphic elements are CMYK. Then everything is converted in one go at export.
    You should always go through the PDF Export dialog carefully. Use the presets, but don't automatically accept defaults. For specific purposes, ask here or in the InDesign forum, where they deal with this all the time.
    For screen, under "Output" use convert to destination, sRGB, include profile. Under "Compression", things aren't as obvious as they used to be (downsample to 96 or 100 ppi), because of the new retina displays that can benefit from a higher resolution. I hold my judgement on this one.

  • Color Space and Bit Depth - What Makes Sense?

    I'm constantly confused about which color space and bit depth to choose for various things.
    Examples:
    - Does it make any sense to choose sRGB and 16-bits? (I thought sRGB was 8-bit by nature, no?)
    - Likewise for AdobeRGB - are the upper 8-bits empty if you use 16-bits?
    - What is the relationship between Nikon AdobeWide RGB, and AdobeRGB? - if a software supports one, will it support the other?
    - ProPhoto/8-bits - is there ever a reason?...
    I could go on, but I think you get the idea...
    Any help?
    Rob

    So, it does not really make sense to use ProPhoto/8 for output (or for anything else I guess(?)), even if its supported, since it is optimized for an extended gamut, and if your output device does not encompass the gamut, then you've lost something since your bits will be spread thinner in the "most important" colors.
    Correct, you do not want to do prophotoRGB 8bit anything. It is very easy to get posterization with it. Coincidentally, if you print from Lightroom and let the driver manage and do not check 16-bit output, Lightroom outputs prophotoRGB 8bits to the driver. This is rather annoying as it is very easy to get posterizaed prints this way.
    It seems that AdobeRGB has been optimized more for "important" colors and so if you have to scrunch down into an 8-bit jpeg, then its the best choice if supported - same would hold true for an 8-bit tif I would think (?)
    Correct on both counts. If there is color management and you go 8 bits adobeRGB is a good choice. This is only really true for print targets though as adobeRGB encompasses more of a typical CMYK gamut than sRGB. For display targets such as the web you will be better off always using sRGB as 99% of displays are closer to that and so you don't gain anything. Also, 80% of web browsers is still not color managed.
    On a theoretical note: I still don't understand why if image data is 12 or 14 bits and the image format uses 16 bits, why there has to be a boundary drawn around the gamut representation. But for practical purposes, maybe it doesn't really matter.
    Do realitze hat the original image in 12 to 14 bits is in linear gamma as that is how the sensor reacts to light. However formats for display are always gamma corrected for efficiency, because the human eye reacts non-linearly to light and because typical displays have a gamma powerlaw response of brightness/darkness. Lightroom internally uses a 16-bit linear space. This is more bits than the 12 or 14 bits simply to avoid aliasing errors and other numeric errors. Similarly the working space is chosen larger than the gamut cameras can capture in order to have some overhead that allows for flexibility and avoids blowing out in intermediary stages of the processing pipeline. You have to choose something and so prophotoRGB, one of the widest RGB spaces out there is used. This is explained quite well here.
    - Is there any reason not to standardize 8-bit tif or jpg files on AdobeRGB and leave sRGB for the rare cases when legacy support is more important than color integrity?
    Actually legacy issues are rampant. Even now, color management is very spotty, even in shops oriented towards professionals. Also, arguably the largest destination for digital file output, the web, is almost not color managed. sRGB remains king unfortunately. It could be so much better if everybody used Safari or Firefox, but that clearly is not the case yet.
    - And standardize 16 bit formats on the widest gamut supported by whatever you're doing with it? - ProPhoto for editing, and maybe whatever gamut is recommended by other software or hardware vendors for special purposes...
    Yes, if you go 16 bits, there is no point not doing prophotoRGB.
    Personally, all my web photos are presented through Flash, which supports AdobeRGB even if the browser proper does not. So I don't have legacy browsers to worry about myself.
    Flash only supports non-sRGB images if you have enabled it yourself. NONE of the included flash templates in Lightroom for example enable it.
    that IE was the last browser to be upgraded for colorspace support (ie9)
    AFAIK (I don't do windows, so I have not tested IE9 myself), IE 9 still is not color managed. The only thing it does is when it encounters a jpeg with a ICC profile different than sRGB is translate it to sRGB and send that to the monitor without using the monitor profile. That is not color management at all. It is rather useless and completely contrary to what Microsoft themselves said many years ago well behaved browsers should do. It is also contrary to all of Windows 7 included utilities for image display. Really weird! Wide gamut displays are becoming more and more prevalent and this is backwards. Even if IE9 does this halfassed color transform, you can still not standardize on adobeRGB as it will take years for IE versions to really switch over. Many people still use IE6 and only recently has my website's access switched over to mostly IE8. Don't hold your breath for this.
    Amazingly, in 2010, the only correctly color managed browser on windows is still Safari as Firefox doesn't support v4 icc monitor profiles and IE9 doesn't color manage at all except for translating between spaces to sRGB which is not very useful. Chrome can be made to color manage on windows apparently with a command line switch. On Macs the situation is better since Safari, Chrome (only correctly on 10.6) and Firefox (only with v2 ICC monitor profiles) all color manage. However, on mobile platforms, not a single browser color manages!

  • Safari and Preview have color space recognition bugs

    I found that both Safari and Preview have problems when viewing photos taken by a Canon DC. By default, the Canon cameras use sRGB for their digital still images. But Preview cannot recognize it and would report "ColorSync profile" as "-" in "Tools/Get Info". I guess that Generic RGB profile is applied in such a condition. If the file is opened by iPhoto or Photoshop, the color space information is recognized correctly. And if sRGB profile is manually assigned to the image using ColorSync Utility, Preview/Safari will give the same vivid color representation as iPhoto/PS do.
    The image below can be used to do the experiment.
    http://dpreview-img.fotki.com/gallery/canoneos5dsamples/originals/img9742.jpg
      Mac OS X (10.4.10)  

    See
    http://www.macintouch.com/readerreports/safari3/index.html
    http://www.macintouch.com/readerreports/safari/topic2922.html and http://www.macintouch.com/readerreports/macosx10_4tiger/topic3051.html#16may2007
    Also, search MIT for color. There's been a lot of traffic about profile calibration the past few weeks.

  • Color space conversions to/from XYZ broken?

    I have just started writing a plug-in in which I need to convert data from an RGB space to XYZ and back again. For this I am using the sPSColorSpace->Convert16 function.
    Unfortunately, it seems that the conversions to and from XYZ are not performed correctly. I do not know exactly what *is* calculated, but XYZ it's not. One of the giveaways is that the result of the conversion depends on the color space of the RGB data, including the gamma. Instead, the XYZ values should be uniquely defined, independent of the source RGB space.
    I have since created a work-around, by using the sPSColorSpace->Convert16 function to convert RGB values to Lab, and converting those to XYZ and back again with my own code. In this way, everything works as expected. However, it's unsatisfactory for two reasons: (1) a basic SDK function seems to be broken, and (2) my workaround is very slow, introducing 4(!) redundant nonlinear transforms per pixel.
    Does anyone have similar or contrary experiences? And, assuming I haven't messed up, how should one go about notifying Adobe about this? Thanks in advance!
    Simon

    >XYZ is a device independent color space, not a transformation of RGB (like HSB).
    That is exactly what I meant. Sorry for expressing myself poorly.
    The test I did was as follows. I applied my filter as a smart filter to an RGB smart object. I then *converted* (not assigned) the RGB object to another color space using a relative colorimetric conversion. Because my filter operates in the XYZ space, the (visual) output should be unaffected by the color space conversion. Unfortunately, the output changed.
    When I changed my filter to use Convert16 to convert to Lab (instead of XYZ) and back, and manually performed the Lab<->XYZ conversion, the (visual) output was indeed independent of the source color space.
    My conclusion is that XYZ as calculated by the Convert16 function *is* a 'transformation of RGB', but, you are correct, it shouldn't be. The conversion does not properly account for the source RGB space.
    Simon

  • File Info - Color Space: Uncalibrated

    In File | File Info there is lots of interesting data about the camera, lens etc. There is also one field that says 'Color Space: Uncalibrated'.
    Should this be calibrated? Is it important, will it make any difference to my pictures if it is calibrated, and how does one go about calibrating it (presumably the camera)?
    FWIW the camera is always used on a copy stand, so same lights etc every time, so calibration might be a good thing.
    Thanks - Brian

    Ansel most likely would have loved Photoshop. He  was far from representative photography and manipulated extensively.  His ideas were around the concept of bringing out the subject matter, if that required suppression of certain aspects to do so. If all that is required is to be unobtrusive as possible, then previsualization would be unnecessary. His mantra was to make a photograph, not take a photograph, which he found distasteful; to "take". One can only make them consistently by using all that your tools can offer.
    I also attempt to get it done in ACR so far as possible, because some steps do look better in ACR than in PS, such as b&w conversion. Wait, not better, different. ACR allows fine tuning across a wider color palette than PS, but dramatizing is better accomplished in PS conversion, albeit with a noisier image likely. Finally, the one tool in PS for which I find no equivalent or better in ACR is Shadow/Highlight, which sometimes I do run as a Smart Object. What you give up as a Smart Object is a number of other tools become greyed out.
    I do use the plan mode as well, D.
    BTW, as I was walking down my street, a car pulled out of the driveway with "Fosse" on the license plate, preceded by initials neither of which was a D. I thought for a moment "wouldn't it be funny if we lived just down the street from each other all these years?"

  • Color Spaces CIE and Adobe RGB

    Looking at monitor specs, usually, the color space of the monitor is given in terms of a target color space, like 96% Adobe RGB. Some give several, but along comes Dell, u2412, and they supply one: 82% CIE.
    I know what CIE is, but making a guesstimate from the Dell spec requires more than what I presently know about such matters.
    So, what are the expectations? Is that a meaningful spec for comparison sake? IOW, how much does Adobe RGB enclose CIE 1976?
    TIA
    Lawrence

    I went back to here:
    http://forums.adobe.com/thread/916368?start=0&tstart=0
    and ran some of those checks with the various presentations. Also, embarrassingly, I did know about the site but failed to go back when I looked for any test results for the 2412.
    sic transit Gloria!
    I also generated  a step tablet in PS, as well as doing several calibration reruns. I did a calibration in "Standard"ode and one in "Custom" where I had access to RGB controls.
    TFT Central did the same and claimed that the Custom was more troublesome and didn't yield any significant improvement. I beg to differ!
    Also, they made available the results of the Standard and Custom as an ICC profile for users and I defy anyone to tell me there is no significant difference. Between my two calibrations and TFT's, I have 4 flavors from which to choose. Wow! I'm impressed (NOT!)
    At any rate I settled on using my custom version as it shows the most neutral gray. It also showed the smaller dE both average and max deviation, 0.34 and 1.2 respectively, the only one exceeding 1.0. It also was close to the factory default than the others.
    What a way to run a railroad!
    The other fussbudget item is X-Rite. I doesn't like calibrating LCD. It manages to skip over steps along the way, and if I hadn't the experience and expectations step to step with my crt, I would probably be returning the Dell at this time. The differences from the data pov between my Custom and Average should be barely visible, but in fact, it is visually significant. Normal conclusions would hold the monitor at fault.
    Off to contact X-Rite.
    Lawrence

  • ATI oss color space compressed in the dark shades of gray

    With the arrival von linux 3.13 to [core] I switched from catalyst to the open source drivers, as they finally provide a sufficient performance. My only problem now is that the colorspace is compressed for gray values below 16 (that means every shade of gray having values of 0 to 16 look just black). That's only the case for my HDMI-output connected to my TV, which worked without problems with the catalyst drivers. Also, only the dark grays are compressed, the near-white grays show up correct.
    In the wiki I found a xrandr-command "--set "Broadcast RGB" "Full"", which can be used with chips from Intel. Is there something similar for the open source ati drivers?

    That's just outputting the options "load detection", "dither", "audio", "underscan vborder", "underscan hborder", "underscan" and "coherent" for both my monitor and TV - are these really all? Here's the full output:
    $ xrandr -q --verbose
    Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
    DisplayPort-0 connected 2560x1440+0+0 (0x59) normal (normal left inverted right x axis y axis) 597mm x 336mm
    Identifier: 0x55
    Timestamp: 2366135
    Subpixel: horizontal rgb
    Gamma: 1.0:1.0:1.0
    Brightness: 1.0
    Clones:
    CRTC: 0
    CRTCs: 0 1 2 3 4 5
    Transform: 1.000000 0.000000 0.000000
    0.000000 1.000000 0.000000
    0.000000 0.000000 1.000000
    filter:
    EDID:
    00ffffffffffff0010ac57a04c543930
    34140104b53c22783a8e05ad4f33b026
    0d5054a54b008100b300d100714fa940
    818001010101565e00a0a0a029503020
    350055502100001a000000ff00473630
    365430434f3039544c0a000000fc0044
    454c4c2055323731310a2020000000fd
    0031561d711e000a202020202020012d
    02031df1509005040302071601061112
    1513141f20230d7f07830f0000023a80
    1871382d40582c250055502100001e01
    1d8018711c1620582c25005550210000
    9e011d007251d01e206e285500555021
    00001e8c0ad08a20e02d10103e960055
    50210000180000000000000000000000
    0000000000000000000000000000004b
    dither: off
    supported: off, on
    audio: auto
    supported: off, on, auto
    underscan vborder: 0
    range: (0, 128)
    underscan hborder: 0
    range: (0, 128)
    underscan: off
    supported: off, on, auto
    coherent: 1
    range: (0, 1)
    2560x1440 (0x59) 241.5MHz +HSync -VSync *current +preferred
    h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 88.8KHz
    v: height 1440 start 1443 end 1448 total 1481 clock 60.0Hz
    1920x1200 (0x5a) 193.2MHz -HSync +VSync
    h: width 1920 start 2056 end 2256 total 2592 skew 0 clock 74.6KHz
    v: height 1200 start 1203 end 1209 total 1245 clock 59.9Hz
    1920x1080 (0x5b) 148.5MHz +HSync +VSync
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
    v: height 1080 start 1082 end 1087 total 1125 clock 60.0Hz
    1920x1080 (0x5c) 148.5MHz +HSync +VSync
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz
    1920x1080 (0x5d) 148.5MHz +HSync +VSync
    h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
    1920x1080 (0x5e) 148.4MHz +HSync +VSync
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.4KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 59.9Hz
    1920x1080i (0x5f) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.8KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 60.1Hz
    1920x1080i (0x60) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.1KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 50.0Hz
    1920x1080 (0x61) 74.2MHz +HSync +VSync
    h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
    1920x1080i (0x62) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.7KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 60.0Hz
    1920x1080 (0x63) 74.2MHz +HSync +VSync
    h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
    1600x1200 (0x64) 162.0MHz +HSync +VSync
    h: width 1600 start 1664 end 1856 total 2160 skew 0 clock 75.0KHz
    v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz
    1680x1050 (0x65) 146.2MHz -HSync +VSync
    h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.3KHz
    v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz
    1280x1024 (0x66) 135.0MHz +HSync +VSync
    h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 80.0KHz
    v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz
    1280x1024 (0x67) 108.0MHz +HSync +VSync
    h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
    v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
    1280x800 (0x68) 83.5MHz +HSync -VSync
    h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.7KHz
    v: height 800 start 803 end 809 total 831 clock 59.8Hz
    1152x864 (0x69) 108.0MHz +HSync +VSync
    h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
    v: height 864 start 865 end 868 total 900 clock 75.0Hz
    1280x720 (0x6a) 74.2MHz +HSync +VSync
    h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
    v: height 720 start 725 end 730 total 750 clock 60.0Hz
    1280x720 (0x6b) 74.2MHz +HSync +VSync
    h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
    v: height 720 start 725 end 730 total 750 clock 50.0Hz
    1280x720 (0x6c) 74.2MHz +HSync +VSync
    h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
    v: height 720 start 725 end 730 total 750 clock 59.9Hz
    1440x576i (0x6d) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1464 end 1590 total 1728 skew 0 clock 15.6KHz
    v: height 576 start 580 end 586 total 625 clock 50.1Hz
    1024x768 (0x6e) 78.8MHz +HSync +VSync
    h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.1KHz
    v: height 768 start 769 end 772 total 800 clock 75.1Hz
    1024x768 (0x6f) 65.0MHz -HSync -VSync
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
    v: height 768 start 771 end 777 total 806 clock 60.0Hz
    1440x480i (0x70) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.8KHz
    v: height 480 start 488 end 494 total 525 clock 60.1Hz
    1440x480i (0x71) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.7KHz
    v: height 480 start 488 end 494 total 525 clock 60.1Hz
    800x600 (0x72) 49.5MHz +HSync +VSync
    h: width 800 start 816 end 896 total 1056 skew 0 clock 46.9KHz
    v: height 600 start 601 end 604 total 625 clock 75.0Hz
    800x600 (0x73) 40.0MHz +HSync +VSync
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
    v: height 600 start 601 end 605 total 628 clock 60.3Hz
    720x576 (0x74) 27.0MHz -HSync -VSync
    h: width 720 start 732 end 796 total 864 skew 0 clock 31.2KHz
    v: height 576 start 581 end 586 total 625 clock 50.0Hz
    720x480 (0x75) 27.0MHz -HSync -VSync
    h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
    v: height 480 start 489 end 495 total 525 clock 60.0Hz
    720x480 (0x76) 27.0MHz -HSync -VSync
    h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
    v: height 480 start 489 end 495 total 525 clock 59.9Hz
    640x480 (0x77) 31.5MHz -HSync -VSync
    h: width 640 start 656 end 720 total 840 skew 0 clock 37.5KHz
    v: height 480 start 481 end 484 total 500 clock 75.0Hz
    640x480 (0x78) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 60.0Hz
    640x480 (0x79) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 59.9Hz
    720x400 (0x7a) 28.3MHz -HSync +VSync
    h: width 720 start 738 end 846 total 900 skew 0 clock 31.5KHz
    v: height 400 start 412 end 414 total 449 clock 70.1Hz
    HDMI-0 connected (normal left inverted right x axis y axis)
    Identifier: 0x56
    Timestamp: 2366135
    Subpixel: horizontal rgb
    Clones:
    CRTCs: 0 1 2 3 4 5
    Transform: 1.000000 0.000000 0.000000
    0.000000 1.000000 0.000000
    0.000000 0.000000 1.000000
    filter:
    EDID:
    00ffffffffffff0034a9a6a001010101
    00140103800000780adaffa3584aa229
    17494b00000001010101010101010101
    010101010101023a80d072382d40102c
    4580ba882100001e023a801871382d40
    582c4500ba882100001e000000fc0050
    616e61736f6e69632d54560a000000fd
    00173d0f440f000a20202020202001d1
    02032672509f90140520130412031102
    16071506012309070168030c001000b8
    260fe3051f01011d80d0721c1620102c
    2580ba882100009e011d8018711c1620
    582c2500ba882100009e011d00bc52d0
    1e20b8285540ba882100001e011d0072
    51d01e206e285500ba882100001e0000
    000000000000000000000000000000c1
    dither: off
    supported: off, on
    audio: auto
    supported: off, on, auto
    underscan vborder: 0
    range: (0, 128)
    underscan hborder: 0
    range: (0, 128)
    underscan: off
    supported: off, on, auto
    coherent: 1
    range: (0, 1)
    1920x1080 (0x5d) 148.5MHz +HSync +VSync +preferred
    h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
    1920x1080 (0x5c) 148.5MHz +HSync +VSync
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz
    1920x1080 (0x5e) 148.4MHz +HSync +VSync
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.4KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 59.9Hz
    1920x1080i (0x5f) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.8KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 60.1Hz
    1920x1080i (0x60) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.1KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 50.0Hz
    1920x1080 (0x61) 74.2MHz +HSync +VSync
    h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
    1920x1080i (0x62) 74.2MHz +HSync +VSync Interlace
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.7KHz
    v: height 1080 start 1084 end 1094 total 1125 clock 60.0Hz
    1920x1080 (0x63) 74.2MHz +HSync +VSync
    h: width 1920 start 2558 end 2602 total 2750 skew 0 clock 27.0KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 24.0Hz
    1280x720 (0x6a) 74.2MHz +HSync +VSync
    h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
    v: height 720 start 725 end 730 total 750 clock 60.0Hz
    1280x720 (0x6b) 74.2MHz +HSync +VSync
    h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
    v: height 720 start 725 end 730 total 750 clock 50.0Hz
    1280x720 (0x6c) 74.2MHz +HSync +VSync
    h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.0KHz
    v: height 720 start 725 end 730 total 750 clock 59.9Hz
    1440x576i (0x6d) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1464 end 1590 total 1728 skew 0 clock 15.6KHz
    v: height 576 start 580 end 586 total 625 clock 50.1Hz
    1440x480i (0x70) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.8KHz
    v: height 480 start 488 end 494 total 525 clock 60.1Hz
    1440x480i (0x71) 27.0MHz -HSync -VSync Interlace
    h: width 1440 start 1478 end 1602 total 1716 skew 0 clock 15.7KHz
    v: height 480 start 488 end 494 total 525 clock 60.1Hz
    720x576 (0x74) 27.0MHz -HSync -VSync
    h: width 720 start 732 end 796 total 864 skew 0 clock 31.2KHz
    v: height 576 start 581 end 586 total 625 clock 50.0Hz
    720x480 (0x75) 27.0MHz -HSync -VSync
    h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
    v: height 480 start 489 end 495 total 525 clock 60.0Hz
    720x480 (0x76) 27.0MHz -HSync -VSync
    h: width 720 start 736 end 798 total 858 skew 0 clock 31.5KHz
    v: height 480 start 489 end 495 total 525 clock 59.9Hz
    640x480 (0x78) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 60.0Hz
    640x480 (0x79) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 59.9Hz
    DVI-0 disconnected (normal left inverted right x axis y axis)
    Identifier: 0x57
    Timestamp: 2366135
    Subpixel: horizontal rgb
    Clones:
    CRTCs: 0 1 2 3 4 5
    Transform: 1.000000 0.000000 0.000000
    0.000000 1.000000 0.000000
    0.000000 0.000000 1.000000
    filter:
    load detection: 1
    range: (0, 1)
    dither: off
    supported: off, on
    audio: auto
    supported: off, on, auto
    underscan vborder: 0
    range: (0, 128)
    underscan hborder: 0
    range: (0, 128)
    underscan: off
    supported: off, on, auto
    coherent: 1
    range: (0, 1)
    Just to emphasize this further: color space compression is not a problem on my monitor, but only on the TV. Setable options don't differ as you can see in the output above. Also, Xorg.0.log shows that the TV on HDMI-0 supports the RGB 4:4:4 encoding (just like the monitor does). Here's the full Xorg.0.log:
    [ 2358.417]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 2358.417] X Protocol Version 11, Revision 0
    [ 2358.417] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 2358.417] Current Operating System: Linux arch 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64
    [ 2358.417] Kernel command line: root=PARTUUID=97f3bf97-014d-4333-8092-e190efc8bd3f rootfstype=ext4 ro add_efi_memmap initrd=\EFI\arch\initramfs-arch.img
    [ 2358.417] Build Date: 09 January 2014 08:47:24AM
    [ 2358.417]
    [ 2358.417] Current version of pixman: 0.32.4
    [ 2358.417] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2358.417] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2358.417] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 3 16:25:06 2014
    [ 2358.417] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2358.417] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 2358.417] (==) No Layout section. Using the first Screen section.
    [ 2358.417] (==) No screen section available. Using defaults.
    [ 2358.417] (**) |-->Screen "Default Screen Section" (0)
    [ 2358.417] (**) | |-->Monitor "<default monitor>"
    [ 2358.417] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2358.417] (==) Automatically adding devices
    [ 2358.417] (==) Automatically enabling devices
    [ 2358.417] (==) Automatically adding GPU devices
    [ 2358.417] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2358.417] Entry deleted from font path.
    [ 2358.417] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2358.417] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2358.417] Entry deleted from font path.
    [ 2358.417] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2358.417] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 2358.417] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2358.417] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2358.417] (II) Loader magic: 0x804c80
    [ 2358.417] (II) Module ABI versions:
    [ 2358.417] X.Org ANSI C Emulation: 0.4
    [ 2358.417] X.Org Video Driver: 15.0
    [ 2358.417] X.Org XInput driver : 20.0
    [ 2358.417] X.Org Server Extension : 8.0
    [ 2358.417] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 2358.418] (--) PCI:*(0:1:0:0) 1002:683f:1787:200b rev 0, Mem @ 0xe0000000/268435456, 0xf7e00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
    [ 2358.418] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 2358.418] Initializing built-in extension Generic Event Extension
    [ 2358.418] Initializing built-in extension SHAPE
    [ 2358.418] Initializing built-in extension MIT-SHM
    [ 2358.418] Initializing built-in extension XInputExtension
    [ 2358.418] Initializing built-in extension XTEST
    [ 2358.418] Initializing built-in extension BIG-REQUESTS
    [ 2358.418] Initializing built-in extension SYNC
    [ 2358.418] Initializing built-in extension XKEYBOARD
    [ 2358.418] Initializing built-in extension XC-MISC
    [ 2358.418] Initializing built-in extension SECURITY
    [ 2358.418] Initializing built-in extension XINERAMA
    [ 2358.418] Initializing built-in extension XFIXES
    [ 2358.418] Initializing built-in extension RENDER
    [ 2358.418] Initializing built-in extension RANDR
    [ 2358.418] Initializing built-in extension COMPOSITE
    [ 2358.418] Initializing built-in extension DAMAGE
    [ 2358.418] Initializing built-in extension MIT-SCREEN-SAVER
    [ 2358.418] Initializing built-in extension DOUBLE-BUFFER
    [ 2358.418] Initializing built-in extension RECORD
    [ 2358.418] Initializing built-in extension DPMS
    [ 2358.418] Initializing built-in extension Present
    [ 2358.418] Initializing built-in extension DRI3
    [ 2358.418] Initializing built-in extension X-Resource
    [ 2358.418] Initializing built-in extension XVideo
    [ 2358.418] Initializing built-in extension XVideo-MotionCompensation
    [ 2358.418] Initializing built-in extension XFree86-VidModeExtension
    [ 2358.418] Initializing built-in extension XFree86-DGA
    [ 2358.418] Initializing built-in extension XFree86-DRI
    [ 2358.419] Initializing built-in extension DRI2
    [ 2358.419] (II) "glx" will be loaded by default.
    [ 2358.419] (II) LoadModule: "dri2"
    [ 2358.419] (II) Module "dri2" already built-in
    [ 2358.419] (II) LoadModule: "glamoregl"
    [ 2358.419] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 2358.420] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 2358.420] compiled for 1.15.0, module version = 0.6.0
    [ 2358.420] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2358.420] (II) LoadModule: "glx"
    [ 2358.420] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2358.420] (II) Module glx: vendor="X.Org Foundation"
    [ 2358.420] compiled for 1.15.0, module version = 1.0.0
    [ 2358.420] ABI class: X.Org Server Extension, version 8.0
    [ 2358.420] (==) AIGLX enabled
    [ 2358.420] Loading extension GLX
    [ 2358.420] (==) Matched ati as autoconfigured driver 0
    [ 2358.420] (==) Matched ati as autoconfigured driver 1
    [ 2358.420] (==) Matched modesetting as autoconfigured driver 2
    [ 2358.420] (==) Matched fbdev as autoconfigured driver 3
    [ 2358.420] (==) Matched vesa as autoconfigured driver 4
    [ 2358.420] (==) Assigned the driver to the xf86ConfigLayout
    [ 2358.420] (II) LoadModule: "ati"
    [ 2358.420] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
    [ 2358.420] (II) Module ati: vendor="X.Org Foundation"
    [ 2358.420] compiled for 1.15.0, module version = 7.3.0
    [ 2358.420] Module class: X.Org Video Driver
    [ 2358.420] ABI class: X.Org Video Driver, version 15.0
    [ 2358.420] (II) LoadModule: "radeon"
    [ 2358.420] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
    [ 2358.420] (II) Module radeon: vendor="X.Org Foundation"
    [ 2358.420] compiled for 1.15.0, module version = 7.3.0
    [ 2358.420] Module class: X.Org Video Driver
    [ 2358.420] ABI class: X.Org Video Driver, version 15.0
    [ 2358.420] (II) LoadModule: "modesetting"
    [ 2358.420] (WW) Warning, couldn't open module modesetting
    [ 2358.420] (II) UnloadModule: "modesetting"
    [ 2358.420] (II) Unloading modesetting
    [ 2358.420] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 2358.420] (II) LoadModule: "fbdev"
    [ 2358.420] (WW) Warning, couldn't open module fbdev
    [ 2358.420] (II) UnloadModule: "fbdev"
    [ 2358.420] (II) Unloading fbdev
    [ 2358.420] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 2358.420] (II) LoadModule: "vesa"
    [ 2358.420] (WW) Warning, couldn't open module vesa
    [ 2358.420] (II) UnloadModule: "vesa"
    [ 2358.420] (II) Unloading vesa
    [ 2358.420] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 2358.420] (II) RADEON: Driver for ATI Radeon chipsets:
    ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
    ATI Radeon Mobility X300 (M24) 3152 (PCIE),
    ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
    ATI Radeon X600 (RV380) 3E50 (PCIE),
    ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
    ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
    ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
    ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
    ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
    ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
    ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
    ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
    ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
    ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
    ATI Radeon IGP330M/340M/350M (U2) 4337,
    ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
    ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
    ATI Radeon X800PRO (R420) JI (AGP),
    ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
    ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
    ATI Radeon Mobility 9800 (M18) JN (AGP),
    ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
    ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
    ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
    ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
    ATI Radeon Mobility M7 LW (AGP),
    ATI Mobility FireGL 7800 M7 LX (AGP),
    ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
    ATI FireGL Mobility 9000 (M9) Ld (AGP),
    ATI Radeon Mobility 9000 (M9) Lf (AGP),
    ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
    ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
    ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
    ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
    ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
    ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
    ATI Radeon Mobility 9600 (M10) NQ (AGP),
    ATI Radeon Mobility 9600 (M11) NR (AGP),
    ATI Radeon Mobility 9600 (M10) NS (AGP),
    ATI FireGL Mobility T2 (M10) NT (AGP),
    ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
    ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
    ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
    ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
    ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
    ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
    ATI Radeon Mobility X300 (M22) 5460 (PCIE),
    ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
    ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
    ATI Radeon X800PRO (R423) UI (PCIE),
    ATI Radeon X800LE (R423) UJ (PCIE),
    ATI Radeon X800SE (R423) UK (PCIE),
    ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
    ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
    ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
    ATI FireGL unknown (R423) UR (PCIE),
    ATI FireGL unknown (R423) UT (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility Radeon X700 XL (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
    ATI Radeon Mobility 9100 IGP (U3) 5835,
    ATI Radeon XPRESS 200 5954 (PCIE),
    ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
    ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
    ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
    ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
    ATI Radeon XPRESS 200M 5975 (PCIE),
    ATI Radeon XPRESS 200 5A41 (PCIE),
    ATI Radeon XPRESS 200M 5A42 (PCIE),
    ATI Radeon XPRESS 200 5A61 (PCIE),
    ATI Radeon XPRESS 200M 5A62 (PCIE),
    ATI Radeon X300 (RV370) 5B60 (PCIE),
    ATI Radeon X600 (RV370) 5B62 (PCIE),
    ATI Radeon X550 (RV370) 5B63 (PCIE),
    ATI FireGL V3100 (RV370) 5B64 (PCIE),
    ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
    ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
    ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
    ATI Mobility Radeon X800 XT (M28) (PCIE),
    ATI Mobility FireGL V5100 (M28) (PCIE),
    ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
    ATI Radeon X850 XT PE (R480) (PCIE),
    ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
    ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
    ATI Radeon X850 XT (R480) (PCIE),
    ATI Radeon X800XT (R423) 5D57 (PCIE),
    ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
    ATI Radeon X700 PRO (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
    ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
    ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
    ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
    ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
    ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
    ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
    ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
    ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
    ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
    ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
    ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
    ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
    ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
    ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
    ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
    ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
    ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
    ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
    ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
    ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
    ATI Mobility Radeon X1700, ATI Radeon X2300HD,
    ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
    ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
    ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
    ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
    ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
    ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
    ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
    ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
    ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
    ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
    ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
    ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
    ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
    ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
    ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
    ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
    AMD FireStream 9250, ATI FirePro V8700 (FireGL),
    ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
    ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
    ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
    ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
    ATI Mobility Radeon HD 4670, ATI FirePro M5750,
    ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
    ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
    ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
    ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
    ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
    ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
    ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
    ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
    ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
    ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
    ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
    ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
    ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
    ATI Mobility Radeon HD 3850 X2, ATI RV670,
    ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
    ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
    ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
    ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
    ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
    ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
    ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
    ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
    ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
    ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
    ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
    ATI FireGL V3600, ATI Radeon HD 2600 LE,
    ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
    ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
    ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
    ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
    ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
    ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
    ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
    ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
    ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
    ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
    SUMO, SUMO, SUMO2, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
    ATI Radeon 4100, ATI Mobility Radeon HD 4200,
    ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
    AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
    AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
    AMD Radeon HD 6300 Series Graphics,
    AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
    AMD Firestream 9350, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
    ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
    ATI Mobility Radeon HD 5800 Series,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
    ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
    ATI Mobility Radeon Graphics, CEDAR,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
    ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
    CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
    BARTS, BARTS, Mobility Radeon HD 6000 Series,
    Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
    AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
    AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI,
    TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
    TAHITI, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
    PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
    VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
    VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
    VERDE, VERDE, VERDE, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
    OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, HAINAN, HAINAN, HAINAN,
    HAINAN, HAINAN, HAINAN, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE,
    BONAIRE, BONAIRE, BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI,
    KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
    KABINI, KABINI, KABINI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
    HAWAII, HAWAII, HAWAII, HAWAII
    [ 2358.423] (++) using VT number 7
    [ 2358.423] (II) [KMS] Kernel modesetting enabled.
    [ 2358.423] (II) RADEON(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 2358.423] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
    [ 2358.423] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 2358.423] (==) RADEON(0): Default visual is TrueColor
    [ 2358.423] (==) RADEON(0): RGB weight 888
    [ 2358.423] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
    [ 2358.423] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x683f)
    [ 2358.423] (II) Loading sub module "dri2"
    [ 2358.423] (II) LoadModule: "dri2"
    [ 2358.423] (II) Module "dri2" already built-in
    [ 2358.423] (II) Loading sub module "glamoregl"
    [ 2358.423] (II) LoadModule: "glamoregl"
    [ 2358.423] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 2358.423] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 2358.423] compiled for 1.15.0, module version = 0.6.0
    [ 2358.423] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2358.423] (II) glamor: OpenGL accelerated X.org driver based.
    [ 2358.452] (II) glamor: EGL version 1.4 (DRI2):
    [ 2358.462] (II) RADEON(0): glamor detected, initialising EGL layer.
    [ 2358.462] (II) RADEON(0): KMS Color Tiling: enabled
    [ 2358.462] (II) RADEON(0): KMS Color Tiling 2D: enabled
    [ 2358.462] (II) RADEON(0): KMS Pageflipping: enabled
    [ 2358.462] (II) RADEON(0): SwapBuffers wait for vsync: enabled
    [ 2358.509] (II) RADEON(0): Output DisplayPort-0 has no monitor section
    [ 2358.572] (II) RADEON(0): Output HDMI-0 has no monitor section
    [ 2358.593] (II) RADEON(0): Output DVI-0 has no monitor section
    [ 2358.644] (II) RADEON(0): EDID for output DisplayPort-0
    [ 2358.644] (II) RADEON(0): Manufacturer: DEL Model: a057 Serial#: 809063500
    [ 2358.644] (II) RADEON(0): Year: 2010 Week: 52
    [ 2358.644] (II) RADEON(0): EDID Version: 1.4
    [ 2358.644] (II) RADEON(0): Digital Display Input
    [ 2358.644] (II) RADEON(0): 10 bits per channel
    [ 2358.644] (II) RADEON(0): Digital interface is DisplayPort
    [ 2358.644] (II) RADEON(0): Max Image Size [cm]: horiz.: 60 vert.: 34
    [ 2358.644] (II) RADEON(0): Gamma: 2.20
    [ 2358.644] (II) RADEON(0): DPMS capabilities: Off
    [ 2358.644] (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
    [ 2358.644] (II) RADEON(0): First detailed timing is preferred mode
    [ 2358.644] (II) RADEON(0): Preferred mode is native pixel format and refresh rate
    [ 2358.644] (II) RADEON(0): redX: 0.678 redY: 0.309 greenX: 0.202 greenY: 0.689
    [ 2358.644] (II) RADEON(0): blueX: 0.148 blueY: 0.051 whiteX: 0.313 whiteY: 0.329
    [ 2358.644] (II) RADEON(0): Supported established timings:
    [ 2358.644] (II) RADEON(0): 720x400@70Hz
    [ 2358.644] (II) RADEON(0): 640x480@60Hz
    [ 2358.644] (II) RADEON(0): 640x480@75Hz
    [ 2358.644] (II) RADEON(0): 800x600@60Hz
    [ 2358.644] (II) RADEON(0): 800x600@75Hz
    [ 2358.644] (II) RADEON(0): 1024x768@60Hz
    [ 2358.644] (II) RADEON(0): 1024x768@75Hz
    [ 2358.644] (II) RADEON(0): 1280x1024@75Hz
    [ 2358.644] (II) RADEON(0): Manufacturer's mask: 0
    [ 2358.644] (II) RADEON(0): Supported standard timings:
    [ 2358.644] (II) RADEON(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 2358.644] (II) RADEON(0): #1: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 2358.644] (II) RADEON(0): #2: hsize: 1920 vsize 1200 refresh: 60 vid: 209
    [ 2358.644] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 2358.644] (II) RADEON(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 2358.644] (II) RADEON(0): #5: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 2358.644] (II) RADEON(0): Supported detailed timing:
    [ 2358.644] (II) RADEON(0): clock: 241.5 MHz Image Size: 597 x 336 mm
    [ 2358.644] (II) RADEON(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0
    [ 2358.644] (II) RADEON(0): v_active: 1440 v_sync: 1443 v_sync_end 1448 v_blanking: 1481 v_border: 0
    [ 2358.644] (II) RADEON(0): Serial No: G606T0CO09TL
    [ 2358.644] (II) RADEON(0): Monitor name: DELL U2711
    [ 2358.644] (II) RADEON(0): Ranges: V min: 49 V max: 86 Hz, H min: 29 H max: 113 kHz, PixClock max 305 MHz
    [ 2358.644] (II) RADEON(0): Supported detailed timing:
    [ 2358.644] (II) RADEON(0): clock: 148.5 MHz Image Size: 597 x 336 mm
    [ 2358.644] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2358.644] (II) RADEON(0): v_active: 1080 v_sync: 1082 v_sync_end 1087 v_blanking: 1125 v_border: 0
    [ 2358.644] (II) RADEON(0): Supported detailed timing:
    [ 2358.644] (II) RADEON(0): clock: 74.2 MHz Image Size: 597 x 336 mm
    [ 2358.644] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2358.644] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 2358.644] (II) RADEON(0): Supported detailed timing:
    [ 2358.644] (II) RADEON(0): clock: 74.2 MHz Image Size: 597 x 336 mm
    [ 2358.644] (II) RADEON(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 2358.644] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2358.644] (II) RADEON(0): Supported detailed timing:
    [ 2358.644] (II) RADEON(0): clock: 27.0 MHz Image Size: 597 x 336 mm
    [ 2358.644] (II) RADEON(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 2358.644] (II) RADEON(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 2358.644] (II) RADEON(0): Number of EDID sections to follow: 1
    [ 2358.644] (II) RADEON(0): EDID (in hex):
    [ 2358.644] (II) RADEON(0): 00ffffffffffff0010ac57a04c543930
    [ 2358.644] (II) RADEON(0): 34140104b53c22783a8e05ad4f33b026
    [ 2358.644] (II) RADEON(0): 0d5054a54b008100b300d100714fa940
    [ 2358.644] (II) RADEON(0): 818001010101565e00a0a0a029503020
    [ 2358.644] (II) RADEON(0): 350055502100001a000000ff00473630
    [ 2358.644] (II) RADEON(0): 365430434f3039544c0a000000fc0044
    [ 2358.644] (II) RADEON(0): 454c4c2055323731310a2020000000fd
    [ 2358.644] (II) RADEON(0): 0031561d711e000a202020202020012d
    [ 2358.644] (II) RADEON(0): 02031df1509005040302071601061112
    [ 2358.644] (II) RADEON(0): 1513141f20230d7f07830f0000023a80
    [ 2358.644] (II) RADEON(0): 1871382d40582c250055502100001e01
    [ 2358.644] (II) RADEON(0): 1d8018711c1620582c25005550210000
    [ 2358.644] (II) RADEON(0): 9e011d007251d01e206e285500555021
    [ 2358.644] (II) RADEON(0): 00001e8c0ad08a20e02d10103e960055
    [ 2358.644] (II) RADEON(0): 50210000180000000000000000000000
    [ 2358.644] (II) RADEON(0): 0000000000000000000000000000004b
    [ 2358.644] (II) RADEON(0): Printing probed modes for output DisplayPort-0
    [ 2358.644] (II) RADEON(0): Modeline "2560x1440"x60.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync (67.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1440x576i"x50.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1440x480i"x60.0 27.03 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.8 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "1440x480i"x59.9 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 2358.644] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 2358.706] (II) RADEON(0): EDID for output HDMI-0
    [ 2358.706] (II) RADEON(0): Manufacturer: MEI Model: a0a6 Serial#: 16843009
    [ 2358.706] (II) RADEON(0): Year: 2010 Week: 0
    [ 2358.706] (II) RADEON(0): EDID Version: 1.3
    [ 2358.706] (II) RADEON(0): Digital Display Input
    [ 2358.706] (II) RADEON(0): Indeterminate output size
    [ 2358.706] (II) RADEON(0): Gamma: 2.20
    [ 2358.706] (II) RADEON(0): No DPMS capabilities specified
    [ 2358.706] (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 2358.706] (II) RADEON(0): First detailed timing is preferred mode
    [ 2358.706] (II) RADEON(0): redX: 0.640 redY: 0.345 greenX: 0.291 greenY: 0.635
    [ 2358.706] (II) RADEON(0): blueX: 0.163 blueY: 0.093 whiteX: 0.288 whiteY: 0.296
    [ 2358.706] (II) RADEON(0): Manufacturer's mask: 0
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.706] (II) RADEON(0): clock: 148.5 MHz Image Size: 698 x 392 mm
    [ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 2358.706] (II) RADEON(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.706] (II) RADEON(0): clock: 148.5 MHz Image Size: 698 x 392 mm
    [ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2358.706] (II) RADEON(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2358.706] (II) RADEON(0): Monitor name: Panasonic-TV
    [ 2358.706] (II) RADEON(0): Ranges: V min: 23 V max: 61 Hz, H min: 15 H max: 68 kHz, PixClock max 155 MHz
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
    [ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 2358.706] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
    [ 2358.706] (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2358.706] (II) RADEON(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.706] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
    [ 2358.706] (II) RADEON(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 2358.706] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2358.706] (II) RADEON(0): Supported detailed timing:
    [ 2358.707] (II) RADEON(0): clock: 74.2 MHz Image Size: 698 x 392 mm
    [ 2358.707] (II) RADEON(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 2358.707] (II) RADEON(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2358.707] (II) RADEON(0): Number of EDID sections to follow: 1
    [ 2358.707] (II) RADEON(0): EDID (in hex):
    [ 2358.707] (II) RADEON(0): 00ffffffffffff0034a9a6a001010101
    [ 2358.707] (II) RADEON(0): 00140103800000780adaffa3584aa229
    [ 2358.707] (II) RADEON(0): 17494b00000001010101010101010101
    [ 2358.707] (II) RADEON(0): 010101010101023a80d072382d40102c
    [ 2358.707] (II) RADEON(0): 4580ba882100001e023a801871382d40
    [ 2358.707] (II) RADEON(0): 582c4500ba882100001e000000fc0050
    [ 2358.707] (II) RADEON(0): 616e61736f6e69632d54560a000000fd
    [ 2358.707] (II) RADEON(0): 00173d0f440f000a20202020202001d1
    [ 2358.707] (II) RADEON(0): 02032672509f90140520130412031102
    [ 2358.707] (II) RADEON(0): 16071506012309070168030c001000b8
    [ 2358.707] (II) RADEON(0): 260fe3051f01011d80d0721c1620102c
    [ 2358.707] (II) RADEON(0): 2580ba882100009e011d8018711c1620
    [ 2358.707] (II) RADEON(0): 582c2500ba882100009e011d00bc52d0
    [ 2358.707] (II) RADEON(0): 1e20b8285540ba882100001e011d0072
    [ 2358.707] (II) RADEON(0): 51d01e206e285500ba882100001e0000
    [ 2358.707] (II) RADEON(0): 000000000000000000000000000000c1
    [ 2358.707] (II) RADEON(0): Printing probed modes for output HDMI-0
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1440x576i"x50.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1440x480i"x60.0 27.03 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.8 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "1440x480i"x59.9 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 2358.707] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 2358.726] (II) RADEON(0): EDID for output DVI-0
    [ 2358.726] (II) RADEON(0): Output DisplayPort-0 connected
    [ 2358.726] (II) RADEON(0): Output HDMI-0 connected
    [ 2358.726] (II) RADEON(0): Output DVI-0 disconnected
    [ 2358.726] (II) RADEON(0): Using exact sizes for initial modes
    [ 2358.726] (II) RADEON(0): Output DisplayPort-0 using initial mode 1920x1080
    [ 2358.726] (II) RADEON(0): Output HDMI-0 using initial mode 1920x1080
    [ 2358.726] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 2358.726] (II) RADEON(0): mem size init: gart size :3fbde000 vram size: s:40000000 visible:3f1b0000
    [ 2358.726] (==) RADEON(0): DPI set to (96, 96)
    [ 2358.726] (II) Loading sub module "fb"
    [ 2358.726] (II) LoadModule: "fb"
    [ 2358.726] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 2358.727] (II) Module fb: vendor="X.Org Foundation"
    [ 2358.727] compiled for 1.15.0, module version = 1.0.0
    [ 2358.727] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2358.727] (II) Loading sub module "ramdac"
    [ 2358.727] (II) LoadModule: "ramdac"
    [ 2358.727] (II) Module "ramdac" already built-in
    [ 2358.727] (--) Depth 24 pixmap format is 32 bpp
    [ 2358.727] (II) RADEON(0): [DRI2] Setup complete
    [ 2358.727] (II) RADEON(0): [DRI2] DRI driver: radeonsi
    [ 2358.727] (II) RADEON(0): [DRI2] VDPAU driver: radeonsi
    [ 2358.727] (II) RADEON(0): Front buffer size: 8160K
    [ 2358.727] (II) RADEON(0): VRAM usage limit set to 923097K
    [ 2358.727] (==) RADEON(0): Backing store enabled
    [ 2358.727] (II) RADEON(0): Direct rendering enabled
    [ 2358.792] (II) RADEON(0): Use GLAMOR acceleration.
    [ 2358.792] (II) RADEON(0): Acceleration enabled
    [ 2358.792] (==) RADEON(0): DPMS enabled
    [ 2358.792] (==) RADEON(0): Silken mouse enabled
    [ 2358.792] (II) RADEON(0): Set up textured video (glamor)
    [ 2358.792] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.
    [ 2358.792] (II) RADEON(0): [XvMC] Extension initialized.
    [ 2358.792] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 2358.792] (--) RandR disabled
    [ 2358.796] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 2358.796] (II) AIGLX: enabled GLX_ARB_create_context
    [ 2358.796] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 2358.796] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 2358.796] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 2358.796] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 2358.796] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 2358.796] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 2358.796] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 2358.797] (II) AIGLX: Loaded and initialized radeonsi
    [ 2358.797] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 2358.833] (II) RADEON(0): Setting screen physical size to 508 x 285
    [ 2358.860] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 2358.860] (**) Power Button: Applying InputClass "system-keyboard"
    [ 2358.860] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2358.860] (**) Power Button: Applying InputClass "keyboard"
    [ 2358.860] (II) LoadModule: "evdev"
    [ 2358.860] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 2358.860] (II) Module evdev: vendor="X.Org Foundation"
    [ 2358.860] compiled for 1.15.0, module version = 2.8.2
    [ 2358.860] Module class: X.Org XInput Driver
    [ 2358.860] ABI class: X.Org XInput driver, version 20.0
    [ 2358.860] (II) Using input driver 'evdev' for 'Power Button'
    [ 2358.860] (**) Power Button: always reports core events
    [ 2358.860] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 2358.860] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2358.860] (--) evdev: Power Button: Found keys
    [ 2358.860] (II) evdev: Power Button: Configuring as keyboard
    [ 2358.860] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
    [ 2358.860] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 2358.860] (**) Option "xkb_rules" "evdev"
    [ 2358.860] (**) Option "xkb_model" "pc104"
    [ 2358.860] (**) Option "xkb_layout" "de"
    [ 2358.860] (**) Option "xkb_variant" "nodeadkeys"
    [ 2358.875] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [ 2358.875] (**) Power Button: Applying InputClass "system-keyboard"
    [ 2358.875] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2358.875] (**) Power Button: Applying InputClass "keyboard"
    [ 2358.875] (II) Using input driver 'evdev' for 'Power Button'
    [ 2358.875] (**) Power Button: always reports core events
    [ 2358.875] (**) evdev: Power Button: Device: "/dev/input/event0"
    [ 2358.875] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2358.875] (--) evdev: Power Button: Found keys
    [ 2358.875] (II) evdev: Power Button: Configuring as keyboard
    [ 2358.875] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
    [ 2358.875] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 2358.875] (**) Option "xkb_rules" "evdev"
    [ 2358.875] (**) Option "xkb_model" "pc104"
    [ 2358.875] (**) Option "xkb_layout" "de"
    [ 2358.875] (**) Option "xkb_variant" "nodeadkeys"
    [ 2358.875] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 2358.875] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event27)
    [ 2358.875] (II) No input driver specified, ignoring this device.
    [ 2358.875] (II) This device may have been added with another device file.
    [ 2358.875] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event26)
    [ 2358.875] (II) No input driver specified, ignoring this device.
    [ 2358.875] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event25)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event24)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event23)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event22)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event18)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event17)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event16)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.876] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event15)
    [ 2358.876] (II) No input driver specified, ignoring this device.
    [ 2358.876] (II) This device may have been added with another device file.
    [ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
    [ 2358.877] (II) No input driver specified, ignoring this device.
    [ 2358.877] (II) This device may have been added with another device file.
    [ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event13)
    [ 2358.877] (II) No input driver specified, ignoring this device.
    [ 2358.877] (II) This device may have been added with another device file.
    [ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event12)
    [ 2358.877] (II) No input driver specified, ignoring this device.
    [ 2358.877] (II) This device may have been added with another device file.
    [ 2358.877] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
    [ 2358.877] (II) No input driver specified, ignoring this device.
    [ 2358.877] (II) This device may have been added with another device file.
    [ 2358.877] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event19)
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "system-keyboard"
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "keyboard"
    [ 2358.877] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Nano Transceiver v2.0'
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
    [ 2358.877] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event19"
    [ 2358.877] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Vendor 0x45e Product 0x745
    [ 2358.877] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found keys
    [ 2358.877] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
    [ 2358.877] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.1/4-1.2.1.2/4-1.2.1.2:1.0/input/input19/event19"
    [ 2358.877] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 8)
    [ 2358.877] (**) Option "xkb_rules" "evdev"
    [ 2358.877] (**) Option "xkb_model" "pc104"
    [ 2358.877] (**) Option "xkb_layout" "de"
    [ 2358.877] (**) Option "xkb_variant" "nodeadkeys"
    [ 2358.877] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event20)
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "system-keyboard"
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev pointer catchall"
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "evdev keyboard catchall"
    [ 2358.877] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "keyboard"
    [ 2358.877] (II) Using input driver 'evdev' for 'Microsoft Microsoft® Nano Transceiver v2.0'
    [ 2358.878] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
    [ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Device: "/dev/input/event20"
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Vendor 0x45e Product 0x745
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found 9 mouse buttons
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found scroll wheel(s)
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found relative axes
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found x and y relative axes
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found absolute axes
    [ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Forcing absolute x/y axes to exist.
    [ 2358.878] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found keys
    [ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as mouse
    [ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
    [ 2358.878] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Adding scrollwheel support
    [ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: YAxisMapping: buttons 4 and 5
    [ 2358.878] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 2358.878] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.1/4-1.2.1.2/4-1.2.1.2:1.1/input/input20/event20"
    [ 2358.878] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 9)
    [ 2358.878] (**) Option "xkb_rules" "evdev"
    [ 2358.878] (**) Option "xkb_model" "pc104"
    [

  • Can you show slideshow within Lightroom 4.4 in Adobe RGB color space?

    Can you show slideshow within Lightroom 4.4 (not export out from LR) in Adobe RGB color space provided that you are using a wide gamut monitor which is capable and hardware calibrated & profiled to show such color space?
    If this is possible, what is required to do so in Windows 8 and i7-4770 & HD Graphics 4600 platform or does LR take care of it automatically?
    This is very basic question, however, I could not find a clear answer/info from LR documentation, so wish that someone can advice.

    Those settings are probably stored in a plist somewhere in ~/Library/Preferences. If you can locate the appropriate file, you should be able to copy it to all the network user folders.

  • Image in PDF error - Expected end of color space

    Hi friends,
    I am displaying a PDF file in an webdynpro application. The contents are coming from the output of a RFC. The pdf file contains an image. While I am running the Webdynpro application the image is not coming. An error popup <b>"Expected end of color space"</b> is generated. But the texts of pdf file is coming properly.
    Please help.
    With regards,
    Sekhar

    Hi Sekar
    We are facing the same issue.  Have you managed to resolve this issue ?
    Please advise
    Regards
    Vivek

  • Asking the Bridge Team:  Bridge "working color space" setting when one does not have the Suite?

    Common sense tells me there is really no such thing as a
    "working color space" in Bridge, because
    Bridge is not an image editor, just a browser
    Therefore, this may turn out to be a purely academic question; but that doesn't keep my curiosity from forcing me to ask it anyway. ;)
    Is there a way to set the Bridge
    "color settings" when one does not have the suite?
    The only Adobe program I keep up to date is Photoshop, so I've never had the suite. My version of Photoshop is 11 (CS4) and I run updated
    (not upgraded) versions of Adobe Acrobat 7.x, Illustrator 10.x and InDesign 2.x. Consequently, the Synchronize color settings command is not available to me.
    It seems to me that Bridge is behaving like a proper color-managed browser (e.g. Firefox with color management enabled), in that it displays tagged image files correctly and assumes sRGB for untagged image files. This normally works fine.
    But what if I wanted Bridge to assume my
    Photoshop color working space for untagged images
    so that it behaves the same as Photoshop? I'm just curious, as I deal with a minuscule, practically negligible amount of untagged files.
    My reason for bringing it up now is that I don't recall this being explicitly mentioned in forum replies when users inquire about color settings in Bridge. A recent post regarding Version Cue in the Photoshop Macintosh forum got me thinking about this. Just wanting to make sure that I'm right in my assumption that
    there is really no such thing as a
    "working color space" in Bridge, because Bridge is not an image editor, just a browser.
    Thanks in advance.

    Hi Ramón,
    Thanks for sharing the outcome of your tests. However, I may have found a bug/exception to Bridge's colour management policy!
    It appears that CMYK EPS photoshop files are not colour managed in Adobe Bridge, even if they contain an embedded ICC profile.
    I've tried every combination in the EPS 'Save As' dialogue box, so it doesn't seem to be an issue with file encoding. Also, Bridge doesn't rely on the low-res preview that is held within the EPS itself.
    My guess is that Bridge is previewing the CMYK EPS with a Bridge-generated RGB image, but it's being displayed as monitor RGB (assigned) rather than colour managed (converted to monitor RGB). For most users the difference will be barely perceptible, but the problem became very noticeable when using Bridge to preview Newsprint CMYK images on a wide-gamut monitor (images that should have appeared muted really leapt off the screen!).
    How do I report this to the Colour Police at Adobe?!?

  • Rendering Chroma 4:2:2 with color space 0-255

    Hello Everyone.
    Just as a warning I'm fairly new to video editing, so I will probably not say this right. I have a screen recording that I used FRAPS to collect, and then I packaged it into an .AVI container w/ a lararith codec , and a 24bit RGB color scheme in video dub. I have then opened and edited that video in Premiere Pro and want to export it. The problem that I'm having is screen recording has a LOT of color between 0-16 and 235-255, so any broadcast color space I use makes the video look awful. I was wondering if anyone knows how I can render out with a 0-255 color space and a decent chroma subsampling (my guess is 4:2:2).
    Thank you everyone for your help.

    No, you are asking the right question, and I understand your problem. I just can't recreate it.
    I just took a really wild Quicktime video I downloaded from Videoblocks.com that isn't anywhere close to being broadcast safe, and I exported it to a Windows Media file.
    The first picture is a screenshot from the video. (it is a set of lower thirds in one video - I am just supposed to use one at a time of course.
    The second picture is the Reference monitor from frame 12;24
    I exported the sequence to a Windows Media file and then imported it, putting it right on top of the other video on the sequence so I could make sure to be on the exact same frame. The third picture is the reference monitor from the WMV file on the sequence.  As you can see, there is not much difference. Some, but you have to look closely.
    So, my question to you, since I do not use FRAPS, is what are your sequence setting? Did you just drop a clip on the New button to create a new sequence with the exact right settings? And, are you making the mistake of using the renders to help you export?
    The problem is that I don't understand your source material. I guess I could download FRAPS from somewhere and give it a try? I am just a bit busy with other things today.

Maybe you are looking for

  • Haven't been able to receive any email today

    Is the network having trouble today? I haven't been able to receive any email on my iPhone today at all. It just says "checking mail" with the spinning wheel. I can access the internet, phone, and voicemail functions, but no mail. I have regular mac

  • HP laptop won't turn on. I get 5 sleep icon flashes...that's it.

    I have a HP NV55C laptop. It's been working just fine when suddenly while I was watching something on it the laptop turned off and won't power back up. All I get is 5 flashes from the light bulb icon. I've plugged it into different outlets, unplugged

  • Ipod shows empty.

    Ipod shows empty, but space is still shown used. And everytime I connect my iPod, iTunes stops working. Please help.

  • Advance Table - Add Row button and coloumn issue

    Hi all, I have created Advanced Table wth four coloumns. for two columns item style as messagtextinput and the rest are same as DATE. But when the page is rendering the table columns shows as messagestyletext , which means messagetextinput style item

  • How to copy a LSMW

    Hello I've a problem copying a LSMW. I've distinct projects (each one with a subproject) and I want to copy all the subprojects under one unicque project, so anybody can tell me how to copy one subproject from one LSMW to another? Thanks in advance.