Gamma: 1.8 or 2.2, etc.

I have a Mac G5 (1995), OS 10.5.8, Radeon 9600 and a LaCie electron b 22 CRT, with PS CS4, processing camera raw and adobe RGB. I need a monitor calibrator (am using an old Spyder, but unhappy with it), and will get an LCD when the LaCie croaks. My questions are:
1) Can I use the same calibrator brand/system for both CRT and LCD monitors? (The LCD would likely be a NEC PA 271 or similar). If "yes" for certain calibration systems, do you have a preference? At one time, Monaco Optix XR Pro was recommended for the LaCie crt, but x-rite bought out that competition. Other recommended (a few years ago) for the LaCie are x-rite's i1D2 and Coloreyes Display Pro 3.10. But the latter's website (ColorManagement.com) does not inspire confidence. LaCie's Blue Eye Pro is just a rebranded x-rite(?). And the sensor should be a DTP-94, right?
NEC offers its own well-regarded customized calibration system--Spectraview II--but that probably wouldn't work with the old LaCie.
2) I have seen both 1.8 and 2.2 as the preferred gamma for Mac systems. Does this setting depend on operating system and hardware? For my current set-up, is 1.8 the correct number? What about for Lightroom 3 on a Mac?
3) Is ColorMunki any good for printer calibration (Epson R2400), to be done by a rank amateur?
Thank you for your help!

Many of the older monitor calibrators were optimized for the general gamut of monitors of the period - sRGB or thereabouts and often don't perform well with wide gamut LCDs. You should be fine with the new models. The X-Rite seems to be the preferred device. If I were buying one today, that's what I would buy.
"I have seen both 1.8 and 2.2 as the preferred gamma for Mac systems. Does this setting depend on operating system and hardware? For my current set-up, is 1.8 the correct number? What about for Lightroom 3 on a Mac?"
It's been a long time since gamma 1.8 was recommended and even then it was usually for the wrong reasons. That really stems from a time before hardware calibration and profile aware applications where gamma 1.8 gave a closer match with black and white laser printers and with the default CMYK setups prior to Ps 5.0.
The native gamma of most monitors is in the 2.2-2.4 range, so calibrating to the 2.2 standard generally results in less of a correction being applied in the video card lookup tables, lessoning the potential for on screen posterization from too much a tweak to 8 bit monitor data. In addition, the most popular working color spaces are already gamma 2.2 or a derivative thereof and keeping your monitor at 2.2 helps when viewing non color managed web images.
So, the bottom line is that you should use gamma 2.2 whether on a Mac or PC, old or new. Colormunki is fine for your printer profiles.

Similar Messages

Greek entries in Contacts

I have several contacts entered in Greek on my contacts app.They all appear at the bottom of the list of contacts I would like them to appear either on their own alphabetized list or within the english alphabet. Is there a way to add a Greek alphabet section? Thanks!

Well Linc, I disagree with you. From the way Contacts behaves it has no such capability whatsoever. There is no Alpha, Beta, Gamma, etc tabs that organize entries like A, B, C. Yet the OS includes a mirriad of languages for one to choose from when typing, but Contacts has no accommodation for any of them but english, it seems. The reason it works the way it does is the way binary code inteprets letters. Contacts doesn't know what to do with these lettters just as it can't deal with numbers or symbols and just throws them at the bottom of the list in binary order. I have not dabbled with Cyrillic, Arab, African, or Pictographic languages all of which are even more distant than Greek to latin/english, but I'm sure its even more if not completely impossible to use Contacts for most of those. What I was hoping for was some switch somewhere in contacts that allows for incluson of foreign language tabs. If I had the answer, I would not be posting, would I?
To answer your next to last comment directly, it is possible to envelope Greek into the English tabs by assigning Alpha to A Beta to V, Gamma to G, Delta to D etc. Alternatively there could be a seperate tab system, which would be the cleaner way to do it but neither solution seems to be available.

Colors differ in PhotoShop and Windows Viewer

Dear members
I got a problem.. when I adjust/ photoshop a picture in PhotoShop cs3 I save it.
Then when I open it in the Windows Viewer.. the colors are different from PhotoShop. Some are lighter other darker.
When I send this to print. The colors of the Windows Viewer match the result. And the colors of PhotoShop doesn't.
I've got my screen also calibrated.
Does anyone know where the problem is?

Dave,
Really there was no offense taken. It's only that these problems are a bit more complicated than simply calibrating the monitor. Learning to understand these things takes time. For me it took many long mountain bike rides and hikes in the Santa Monica Mountains where I could clear my head enough for the light bulb of understanding to turn on.
I might have reacted a but harshly too. Really, we're all here to learn and share information and hopefully not get too confused.
Assie,
"'Trust what you see in Ps and don't worry about Viewer as it's just an approximation'
"I think this is with my system different. When i see a picture in viewer and i let it printed professionally. The colors on the printed picture are the same of the viewer.. and not the same with those in PS. "
Good, your back in the thread. In order to help you we need to know a couple of things. What is your RGB working space? What monitor do you have and how has it been calibrated - gamma, white point, luminence, calibration device, etc?
With the images you are having printed professionally, what is the data flow for the printing? What type of printer is being used and what is the lab's color management setup? Are you sending them tagged files and if so, what profile is being embedded?
Really the best way to wade through all this is one baby step at a time. First make sure that your screen is calibrated properly (this means hardware colorimeter) and your ambient lighting is correct for the luminence of your screen. Prints need to be viewed under a standardized light source. Inkjets love the lighting from Solux (solux.net). If you are going to display prints under other types of light, then it's best to make custom profiles that factor in the light source as part of the profile.
Once you have your monitor properly calibrated, you can be reasonbly sure that what you see in Ps is what is in your file. For any kind of output, you need to customize the data for the output device. Normally this is done with output profiles, and usually better results come from custom profiles. You have to know what's happening to your data at every step of the way to determine where things are going awry if you get prints that are not meeting your expectations, so tackle one thing at a time and don't move on to the next until your'e sure the last step has been done correctly or it will be difficult to pinpoint what to change.

Upscaled dv for anamorphic and want to know about adjusting gamma etc.

I took my dv ntsc 4:3 (3:2 really shot on dvcam on the dvx100a) timeline and nested it in an anamorphic sequence to render out a quicktime with the 1:85 matte on it and to apply an rgb limiter as when it upscales some of my broadcast safe get hot again in the high end. This output is going to a theatrical presentation. Unfortunately now they are only going to show it with dvcam and want this anamorphic output so it matches another filmmaker's settings and the projectionist doesn't have to get confused (?) so anyway...
Back to my question...when I upscale this to 133.33 to fill the screen in the anamorphic of course things get washed out...I readjusted gamma to 1.05 which is subtle but brings the blacks back...I do have a bunch of monitors but I distrust that on my little 14" broadcast sony crt what is going to project won't be washed out so I'm relying somewhat on a sony flat screen panel with settings to match my smaller crt but by eye...
In any case anyone out there doing this a lot do you find there are general settings you use that would adjust and resaturate color and gamma levels etc. and any other levels I need worry about so the picture won't look so washed out when it's projected? Does readjusting gamma to 1.05 sound right to you or should it be more as a general thing?
I have a color balance set up for highs and mid range but don't know that I need to use them on this file which I output as an uncompressed it seems to not have lost much in the color itself it's mainly the gamma issue...I also want to get this right because it's a pain working with the uncompressed nested sequence and rendering it is extremely time consuming.
...when I output a quicktime earlier using dv ntsc compressor settings "as is" I found I would lose saturation and the picture would get dark if I applied the gamma and instead color corrected just with color balance settings and the rgb limiter.
thank you

What kind of problem are you having? I've used Netbackup for doing Oracle backups quite a bit without a problem. If you can shutdown the instances, just have a script do it before the backup starts. Usually, I do a cold backup on the weekends and then backup of the archive logs during the week to save tape space. Just stick in a little script to do a log switch before the backup starts to make sure you get the current changes. If you're running 24x7, you'll need to look at buying the RMAN module from veritas or roll your own hot backup script.

Safari 4 Color and Gamma STILL Washes Out -- NOT Solved 7/4/2009

OK, just bringing this back to the top:
http://discussions.apple.com/thread.jspa?threadID=2032159&start=0&tstart=0 is listed as 'Solved', but that was totally premature. The alleged fixes range from the usual repair permissions, trash Safari prefs, reboot, etc., but it's all temporary, at best.
A CLEAN install of the OS to a virgin partition, followed by permissions, repair, combo updater, apply all related Safari, repair permissions, delete, shutdown and reboot leaves you with the same issue as soon as you sleep displays, go to screen saver, use FUS, and come back in with Safari 4 already running, you will get the screen wash as further described here:
http://gallery.me.com/frederico/100070
Posted Elsewhere:
Gamma settings within Safari 4 windows since upgrade will "degrade" (read: darken and stratify) when scrolling the window contents, using either scroll wheel, arrow keys, or mouse on scroll bar. Text also becomes progressively fuzzy and its opacity decreases until the entire window is black.
Moving another application window in front, or minimizing and maximizing the errant window, moving or resizing it in any manner, or using the 'Force Repaint' command will restore the appearance immediately. I can capture screenshots of it, but cannot use your included screenshot command, as the mere act of dropping down the report slider forces repaint.
Quitting Safari, rebooting machine, or just logging out will "cure" the problem for a short time, but it returns fairly quickly. I do not believe I have any third party plugins causing the issue; I removed several and the problem still crept back; each user account, including a freshly created test account sees this error.
This can fairly regularly be triggered by sleeping the displays or entering locked screensaver, logging in, and going to several sites such as Daring Fireball, Mac OS X Hints, and anything displaying PNG and Flash combos.
Perhaps related: I updated to 10.5.7 at the same time, and when I restarted, noticed that the gamma profile on my center screen (of five LCDs) was severely washed out. Switching back and forth between any other color profile in Displays and back to my calibrated profile will cure the wash -- until I log out and back in. Each user account, including a freshly created test account sees this error.
Have also clean installed OS X 10.5.4 and updated to a10.5.7 using combo updater; then installed and updated Safari 4. Problem follows Main screen (menubar host) on each of five LCD displays on three ATi video cards on Mac Pro Quad 2008.
Getting ready to restore back to Safari 3 and 10.5.6 from clone; this behavior is becoming tedious.
Screenshots and additional details on request; <Edited by Host>
http://gallery.me.com/frederico/100070
More info and more users seeing the same thing here
http://www.macosxhints.com/article.php?story=2009062403534417
http://www.macosxhints.com/article.php?story=2009062403534417#comments
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 6 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
System Version: Mac OS X 10.5.7 (9J61)
Kernel Version: Darwin 9.7.0
Boot Volume: system
Boot Mode: Normal
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
CMC 22 W:
Resolution: 1680 x 1050 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
ATI Radeon HD 2600 XT:
Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
CMC 19AW:
Resolution: 1440 x 900 @ 60 Hz
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected

Now THAT is interesting. I typically do not have two Safari windows open and active on the same screen; I usually have three or more Safari windows open, but each is on its own screen, using tabs within each.
I think it's fascinating to see that the content is only affected in one window on the same page.
Can you elaborate as to your trigger? Is it FUS? Screensaver? Other?
The suggestion in either this thread or the other to switch the window momentarily to another screen to clear the problem until the next FUS or screensaver event is my current favorite fix. I have hotkeys assigned to move a window from one screen to another, anyway, so when I return to a user session from login to see Safari schizing out, a quick screen-swap toggle clears the issues until I allow a screensaver (but not always) or engage FUS (always) and see the issue return.
Do you have multiple screens? Can you reliably resolve the issue by swapping and returning, rather than being forced to quit Safari?
One thing to note about the screen swap, is that when this issue is occurring, there is a tremendous lag (a solid second or so) before the window is actually moved to the other screen, and a comparable lag when returning. IOW, there is an observable and HUGE processor spike as well as a memory-use spike (seen in Activity Monitor, top, and iStat Menus) as it deals with moving the visual display (be it plain text or graphic or video content) when this bug is active, but the same action two seconds later, or the same action in any other program, nets near-instant screen movement in response to the global hotkey action.
So, whatever it is that is borked between Safari and Core Video is not just an interpretation/ColorSync/disply error; it seems also to be leaking memory and having runaway processor cycles, as well.
There are times when Safari, with less than ten or twenty tabs open starts eating pretty close to 2GB of RAM, and will dominate a single processor to near 100%, *without* any windows actually containing very much in the way of images, and certainly no Flash or even QT.
I know this sounds a bit arrogant and spoiled, but thank God I have 8 cores and 8GB of RAM; I cannot imagine how this bug might feel on a single core machine with less than 2GB of RAM.

Fluctuating gamma on TV connected via S-video adapter

I have a television (generic CRT) connected to my Powerbook G4 through the S-video adapter and an RCA cable.
Periodically (and I think with increasing frequency), it looks like the gamma setting for the TV fluctuates when it is displaying the line in from the Powerbook. It gets darker and darker... and then it gets lighter and lighter... and then it gets darker and darker... etc. It's a slow cycle, but I haven't been able to find any way of breaking it (restarting the computer, reconnecting the cables, re-detecting the displays, turning mirroring on and off) and it appears to happen whether the display is mirrored or part of a multiple display arrangement.
The one correlation I might have seen is between the temperature of the computer and the fluctuation: hotter -> fluctuation is more likely (no faster or more extreme, just more likely to happen). I think. Of course, the Powerbook spends so much time raging hot that it's hard to tell if this is coincidence or actually meaningful.
Has anyone else experienced this or something like it? Since it's sporadic, I have to hope that there is a fix ("always reboot before connecting the TV" would be a fine fix... if it worked), rather than marking it down as dying hardware.
Thanks for any help folks can offer!

It was indeed Macrovision copy protection. And, if anyone happens to pull this up on a similar search, it's worth noting that not all video players bother to transmit the Macrovision "protection" signal (this occurred to me as a I read this. With DVDs, 'tain't the hardware -- it's in the software!)
Try something more flexible than Apple's DVD Player: VLC.
AlBook G4/1.25GHz, Windtunnel G4/400MHz, and more.. Mac OS X (10.4.10)

Convert RGB to Gray Gamma 1.2 and count number of color pages

I'm working with a printer for theses and dissertations. I receive the PDF files from our graduate students and pass them along. I'm responsible for checking that the document meets the needs of the printer and billing the students appropriately. I'm using Adobe Acrobat X Pro, and am fairly savvy with the pre-flight profiles (creating and running), but I'm not a designer or printer.
Recently, the printer informed me that our students creating PDF files from Word are actually creating what they consider color documents because black is an RGB color from a Word document. I did see in Word that I can use the "High Quality Print" conversion setting to make the text black from the start, but I'm dealing with the final PDF file more often.
They gave me instructions on how to use the "Convert Colors" command to convert the document (or specific pages) to the Gray Gamma 2.2 profile so those pages would be in black and white - see screenshot:
I then submit the document to their web page, where it tells me the count of color pages. I have two problems:
1. For some documents, even after I convert all pages to the profile above, their preflight tool (they use pit stop through their web site, I think ), tells me that some pages are still in color.
2. I can't seem to find a consistent way to count color pages in Acrobat. I've created a pre-flight profile (seee screenshot below), but my results never match theirs (unless it's a raw PDF file and every page is in color). Am I missing an option? I don't really know what spot colors are, so maybe that's an issue?
What I want to be able to do is:
1. Provide consistent instructions to our students on how to fix their documents (perhaps create a pre-flight profile or droplet for them to put their PDF file into).
AND
2. Count the color pages in their document accurately. The printer bills per the page, and there is a differential between color and black and white printing.
Any help would be appreciated.

To detect a "color" page you only need to look at the first two items (CMY plates or more than 0 spot plates). If an object is in RGB it'll separate onto all four plates when printed.
First question - are you sure that the reports coming back from the printer are correct? If they flag a page as color and you don't, what does that page actually contain? Are there any non-printing items (hidden text, items behind something else, etc.) which won't drop an extra plate when physically printed, but which the print shop might be detecting? You're testing the file from the point of view of the paper passing through the machine, they might just be scanning all the objects and ignoring whether they're visible or not. Open one of the questionable pages using the Output Preview tool (on the Tools > Print Production panel) and look at which plates are used.
FYI, spot color is a purpose-mixed ink (not a 'process' color made from CMYK) which appears on its own plate. Usually it's something like a Pantone color, but it might represent something applied by a different part of the production process entirely - lacquer, foil, embossing, etc. With wet ink printing a spot color was literally taken from another bucket and run on a fifth roller, but in digital printing they're usually converted back to process by the printer hardware. The difference is in how accurately that conversion takes place - so they're common for things like company logos. It's unlikely you'll have any in the type of files you're talking about unless a student has picked one by mistake when writing their document in InDesign. Word doesn't like spots and they're not in JPG/PNG/GIF images.

Contrast / Gamma Different in Canvas and Desktop Preview

*The Confusion:*
The contrast of my video differs between the Canvas Window and Desktop Preview.
I assume the two are using different gamma settings. But I can't figure out what's going on, to know what those settings are and how to assess the final display picture.
*Screen Grabs:*
Here's a screen grab of the canvas, with the image at 100%. The screen grab does not show the full frame.
- - - http://epokhecutmedia.com/images/gamma-ts-canvas.png
Here's a full screen grab of image in Desktop Preview.
- - - http://epokhecutmedia.com/images/gamma-ts-preview.png
*What I've done:*
I've gone through every gamma setting I know of and can't match the Canvas and Desktop Preview or make sense of the difference.
Also, If I toggle between Display calibrations of 1.8 and 2.2 using the Display preferences in System Preferences, values in both the Canvas and Desktop Preview shift and still do not match.
*Another seemingly related thing:*
My Canvas window display jumps between different contrasts (possibly gamma values) automatically while I'm working.
For example,
- - - I'll have video frozen. I'll play it and the image with brighten across the mids with playback. However, after freezing it again it keeps the brighter value.
- - - When I'm using filter, such as the 3-Way Color Corrector, when I click to drag a slider, the image with darken across the mids. Sometimes, as I drag, the canvas will erratically jump back and forth between the two values.
*Why this is a problem:*
I can't do basic exposure correction, because I don't know which is the accurate value to work with.
edit by: FordPrefectRevisited, Screen Grabs added

If I may re-open this thread, let me ask the question FordPrefect only alluded to:
Given that I should be using a pro-level HD broadcast monitor to view everything, given that every piece of footage is different in the particulars, and given that the Canvas Window image is almost always different than any other playback system (Finder, QT, VLC Players, etc.), are there general exposure/gamma changes y'all make to account for the visual difference between the Canvas Window and other playback systems? If you're anything like me, you don't start from SCRATCH on every single edit... You have a few go-to filters with a few go-to settings, and then make minor adjustments according to the needs of the footage.
For instance, in order to get the exported image close in exposure to the ideal Canvas Window image, I usually go: Effects - Video Filters - Quicktime - Brightness and Contrast - and then adjust the Brightness to 0.85 and it seems to get close.
You guys have anything like that? Thanks for any help!

Gamma function in formula node

I am running LabView V.6.1 and try to use the gamma function in a formula node.
According to the HELP text ''Formula Node and Expression Node Functions'', the syntax for the Gamma funtion is gamma(x), but this leads to the block diagram error ''Formula node: Undefined variable''.
Other functions (like exp(x), sqrt(x) etc.) work.
Thanks for helping.

Hi,
we ran into this one a little while ago. The help is a little misleading. The Gamma function actually only works with the Expression Nodes, and not the Formula nodes.
Go to the labview help file, and search for "Differences Between the Parser in the Mathematics VIs and the Formula Node "
Also refer to the following link for a bit more information :
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000020540000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_QUESTION_0=%22Square%22+function+in+formula+node&USEARCHCONTEXT_QUESTION_S=0
it's a bit long winded, but be patient - the information is in there.
Hope that helps
S.
// it takes almost no time to rate an answer

Xmonad - Can't start any terminal emulator (xterm,urxvt,etc)

Hi,
I've recently installed Arch Linux in Virtualbox-OSE and also installed xmonad. It took me a while to get it running. It is all working fine and I can start all kinds of applications with MOD+Shift+P, but the only thing I can't do is start a terminal emulator such as xterm or urxvt. Neither with MOD+Shift+P and MOD+Shift+Return. When I do this I see a window flashing and I think it is the program I am trying to start but it is closing right after the startup.
Does anybody recognize this problem or know how to fix it?
Thanks,
Webfp

lifeafter2am wrote:Please post your xmoand.hs file and your xorg log.
my xmonad.hs
import XMonad
import XMonad.Util.Replace
import XMonad.Hooks.EwmhDesktops
main = xmonad $ ewmh defaultConfig
{ terminal = "urxvt"
, modMask = mod4Mask
, borderWidth = 0
xorg log
[ 174.789]
X.Org X Server 1.11.3
Release Date: 2011-12-16
[ 174.790] X Protocol Version 11, Revision 0
[ 174.791] Build Operating System: Linux 3.1.5-1-ARCH i686
[ 174.791] Current Operating System: Linux Laptop-Frank 3.1.8-1-ARCH #1 SMP PREEMPT Sat Jan 7 08:03:08 UTC 2012 i686
[ 174.792] Kernel command line: root=/dev/disk/by-uuid/1b11e5e6-5760-4dbb-9d54-0c982c0a37a4 ro
[ 174.794] Build Date: 17 December 2011 09:38:27AM
[ 174.794]
[ 174.795] Current version of pixman: 0.24.0
[ 174.795] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 174.796] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 174.801] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 11 16:17:09 2012
[ 174.883] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 174.928] (==) No Layout section. Using the first Screen section.
[ 174.928] (==) No screen section available. Using defaults.
[ 174.928] (**) |-->Screen "Default Screen Section" (0)
[ 174.928] (**) | |-->Monitor "<default monitor>"
[ 174.954] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 174.955] (==) Automatically adding devices
[ 174.955] (==) Automatically enabling devices
[ 175.021] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 175.021] Entry deleted from font path.
[ 175.057] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 175.057] Entry deleted from font path.
[ 175.057] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 175.059] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 175.059] Entry deleted from font path.
[ 175.059] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 175.059] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 175.059] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 175.060] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 175.072] (II) Loader magic: 0x8228580
[ 175.073] (II) Module ABI versions:
[ 175.073] X.Org ANSI C Emulation: 0.4
[ 175.073] X.Org Video Driver: 11.0
[ 175.073] X.Org XInput driver : 13.0
[ 175.073] X.Org Server Extension : 6.0
[ 175.078] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
[ 175.079] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 175.079] (II) LoadModule: "extmod"
[ 175.104] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 175.136] (II) Module extmod: vendor="X.Org Foundation"
[ 175.136] compiled for 1.11.3, module version = 1.0.0
[ 175.136] Module class: X.Org Server Extension
[ 175.137] ABI class: X.Org Server Extension, version 6.0
[ 175.137] (II) Loading extension MIT-SCREEN-SAVER
[ 175.137] (II) Loading extension XFree86-VidModeExtension
[ 175.137] (II) Loading extension XFree86-DGA
[ 175.138] (II) Loading extension DPMS
[ 175.138] (II) Loading extension XVideo
[ 175.138] (II) Loading extension XVideo-MotionCompensation
[ 175.138] (II) Loading extension X-Resource
[ 175.139] (II) LoadModule: "dbe"
[ 175.142] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 175.146] (II) Module dbe: vendor="X.Org Foundation"
[ 175.146] compiled for 1.11.3, module version = 1.0.0
[ 175.146] Module class: X.Org Server Extension
[ 175.146] ABI class: X.Org Server Extension, version 6.0
[ 175.146] (II) Loading extension DOUBLE-BUFFER
[ 175.146] (II) LoadModule: "glx"
[ 175.147] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 175.166] (II) Module glx: vendor="X.Org Foundation"
[ 175.166] compiled for 1.11.3, module version = 1.0.0
[ 175.166] ABI class: X.Org Server Extension, version 6.0
[ 175.166] (==) AIGLX enabled
[ 175.166] (II) Loading extension GLX
[ 175.167] (II) LoadModule: "record"
[ 175.169] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 175.172] (II) Module record: vendor="X.Org Foundation"
[ 175.173] compiled for 1.11.3, module version = 1.13.0
[ 175.173] Module class: X.Org Server Extension
[ 175.173] ABI class: X.Org Server Extension, version 6.0
[ 175.173] (II) Loading extension RECORD
[ 175.173] (II) LoadModule: "dri"
[ 175.174] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 175.205] (II) Module dri: vendor="X.Org Foundation"
[ 175.205] compiled for 1.11.3, module version = 1.0.0
[ 175.205] ABI class: X.Org Server Extension, version 6.0
[ 175.205] (II) Loading extension XFree86-DRI
[ 175.205] (II) LoadModule: "dri2"
[ 175.207] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 175.210] (II) Module dri2: vendor="X.Org Foundation"
[ 175.210] compiled for 1.11.3, module version = 1.2.0
[ 175.210] ABI class: X.Org Server Extension, version 6.0
[ 175.210] (II) Loading extension DRI2
[ 175.211] (==) Matched vboxvideo as autoconfigured driver 0
[ 175.211] (==) Matched vesa as autoconfigured driver 1
[ 175.211] (==) Matched fbdev as autoconfigured driver 2
[ 175.211] (==) Assigned the driver to the xf86ConfigLayout
[ 175.211] (II) LoadModule: "vboxvideo"
[ 175.247] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[ 175.265] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 175.266] compiled for 1.5.99.901, module version = 1.0.1
[ 175.266] Module class: X.Org Video Driver
[ 175.266] ABI class: X.Org Video Driver, version 11.0
[ 175.266] (**) Load address of symbol "VBOXVIDEO" is 0xb7396420
[ 175.266] (II) LoadModule: "vesa"
[ 175.268] (WW) Warning, couldn't open module vesa
[ 175.268] (II) UnloadModule: "vesa"
[ 175.269] (II) Unloading vesa
[ 175.269] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 175.269] (II) LoadModule: "fbdev"
[ 175.271] (WW) Warning, couldn't open module fbdev
[ 175.271] (II) UnloadModule: "fbdev"
[ 175.271] (II) Unloading fbdev
[ 175.272] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 175.272] (II) VBoxVideo: guest driver for VirtualBox: vbox
[ 175.273] (--) using VT number 7
[ 175.301] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[ 175.311] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.1.8_OSE
[ 175.341] (II) Loading sub module "ramdac"
[ 175.341] (II) LoadModule: "ramdac"
[ 175.342] (II) Module "ramdac" already built-in
[ 175.342] (II) Loading sub module "fb"
[ 175.342] (II) LoadModule: "fb"
[ 175.344] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 175.361] (II) Module fb: vendor="X.Org Foundation"
[ 175.361] compiled for 1.11.3, module version = 1.0.0
[ 175.362] ABI class: X.Org ANSI C Emulation, version 0.4
[ 175.362] (II) Loading sub module "shadowfb"
[ 175.362] (II) LoadModule: "shadowfb"
[ 175.370] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 175.378] (II) Module shadowfb: vendor="X.Org Foundation"
[ 175.378] compiled for 1.11.3, module version = 1.0.0
[ 175.379] ABI class: X.Org ANSI C Emulation, version 0.4
[ 175.379] (II) Loading sub module "vgahw"
[ 175.379] (II) LoadModule: "vgahw"
[ 175.379] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 175.383] (II) Module vgahw: vendor="X.Org Foundation"
[ 175.383] compiled for 1.11.3, module version = 0.1.0
[ 175.383] ABI class: X.Org Video Driver, version 11.0
[ 175.383] (II) Loading sub module "dri"
[ 175.383] (II) LoadModule: "dri"
[ 175.384] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 175.384] (II) Module dri: vendor="X.Org Foundation"
[ 175.384] compiled for 1.11.3, module version = 1.0.0
[ 175.384] ABI class: X.Org Server Extension, version 6.0
[ 175.384] (II) VBoxVideo(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 175.385] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[ 175.385] (--) VBoxVideo(0): Virtual size is 32000x32000 (pitch 32000)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxInitialMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.385] (II) VBoxVideo(0): Modeline "VBoxInitialMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.385] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-1024x768": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-800x600": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-800x600"x0.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-640x480": 18.8 MHz (scaled from 0.0 MHz), 29.2 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-640x480"x0.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 175.389] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 175.389] (==) VBoxVideo(0): RGB weight 888
[ 175.389] (==) VBoxVideo(0): Default visual is TrueColor
[ 175.389] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[ 175.390] (==) VBoxVideo(0): DPI set to (96, 96)
[ 175.390] (--) Depth 24 pixmap format is 32 bpp
[ 175.820] drmOpenDevice: node name is /dev/dri/card0
[ 175.821] drmOpenDevice: open result is 13, (OK)
[ 175.828] drmOpenDevice: node name is /dev/dri/card0
[ 175.829] drmOpenDevice: open result is 13, (OK)
[ 175.829] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 175.829] drmOpenDevice: node name is /dev/dri/card0
[ 175.829] drmOpenDevice: open result is 13, (OK)
[ 175.829] drmOpenByBusid: drmOpenMinor returns 13
[ 175.829] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 175.830] (II) [drm] DRM interface version 1.4
[ 175.830] (II) [drm] DRM open master succeeded.
[ 175.830] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
[ 175.830] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
[ 175.831] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
[ 175.831] (II) VBoxVideo(0): X context handle = 0x1
[ 175.835] (II) VBoxVideo(0): [drm] installed DRM signal handler
[ 175.836] (II) VBoxVideo(0): visual configurations initialized
[ 175.845] (II) VBoxVideo(0): Requested monitor count: 1
[ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 175.846] (II) VBoxVideo(0): EDID for output VBOX0
[ 175.846] (II) VBoxVideo(0): Manufacturer: VBX Model: 0 Serial#: 50332672
[ 175.846] (II) VBoxVideo(0): Year: 1990 Week: 1
[ 175.846] (II) VBoxVideo(0): EDID Version: 1.3
[ 175.846] (II) VBoxVideo(0): Digital Display Input
[ 175.846] (II) VBoxVideo(0): Indeterminate output size
[ 175.846] (II) VBoxVideo(0): Gamma: 2.20
[ 175.846] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
[ 175.847] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 175.847] (II) VBoxVideo(0): Default color space is primary color space
[ 175.847] (II) VBoxVideo(0): First detailed timing is preferred mode
[ 175.847] (II) VBoxVideo(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 175.847] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 175.847] (II) VBoxVideo(0): Manufacturer's mask: 0
[ 175.847] (II) VBoxVideo(0): Supported detailed timing:
[ 175.847] (II) VBoxVideo(0): clock: 47.8 MHz Image Size: 0 x 0 mm
[ 175.847] (II) VBoxVideo(0): h_active: 1024 h_sync: 1026 h_sync_end 1028 h_blank_end 1030 h_border: 0
[ 175.848] (II) VBoxVideo(0): v_active: 768 v_sync: 770 v_sync_end 772 v_blanking: 774 v_border: 0
[ 175.848] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[ 175.848] (II) VBoxVideo(0): Monitor name: VBOX monitor
[ 175.848] (II) VBoxVideo(0): EDID (in hex):
[ 175.848] (II) VBoxVideo(0): 00ffffffffffff005858000000040003
[ 175.848] (II) VBoxVideo(0): 0100010380000078eeee91a3544c9926
[ 175.848] (II) VBoxVideo(0): 0f505400000001010101010101010101
[ 175.848] (II) VBoxVideo(0): 010101010101af120006400006300202
[ 175.848] (II) VBoxVideo(0): 2200000000000000000000fd0000c800
[ 175.848] (II) VBoxVideo(0): c864000a202020202020000000fc0056
[ 175.849] (II) VBoxVideo(0): 424f58206d6f6e69746f720a00000010
[ 175.849] (II) VBoxVideo(0): 000a20202020202020202020202000fb
[ 175.849] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
[ 175.849] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1024x768 Warning: We only handle separate sync.
[ 175.849] (II) VBoxVideo(0): Using hsync ranges from config file
[ 175.849] (II) VBoxVideo(0): Using vrefresh ranges from config file
[ 175.849] (II) VBoxVideo(0): Printing DDC gathered Modelines:
[ 175.850] (II) VBoxVideo(0): Modeline "1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 -hsync -vsync (46.4 kHz)
[ 175.851] (II) VBoxVideo(0): Printing probed modes for output VBOX0
[ 175.851] (II) VBoxVideo(0): Modeline "1024x768"x60.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.851] (II) VBoxVideo(0): Modeline "800x600"x60.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 175.851] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 175.851] (II) VBoxVideo(0): Output VBOX0 connected
[ 175.852] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 175.852] (II) VBoxVideo(0): Output VBOX0 using initial mode 1024x768
[ 175.852] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 175.852] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 175.856] (==) VBoxVideo(0): DPMS enabled
[ 175.857] (II) VBoxVideo(0): [DRI] installation complete
[ 175.857] (--) RandR disabled
[ 175.857] (II) Initializing built-in extension Generic Event Extension
[ 175.857] (II) Initializing built-in extension SHAPE
[ 175.857] (II) Initializing built-in extension MIT-SHM
[ 175.857] (II) Initializing built-in extension XInputExtension
[ 175.857] (II) Initializing built-in extension XTEST
[ 175.857] (II) Initializing built-in extension BIG-REQUESTS
[ 175.857] (II) Initializing built-in extension SYNC
[ 175.857] (II) Initializing built-in extension XKEYBOARD
[ 175.857] (II) Initializing built-in extension XC-MISC
[ 175.858] (II) Initializing built-in extension SECURITY
[ 175.858] (II) Initializing built-in extension XINERAMA
[ 175.858] (II) Initializing built-in extension XFIXES
[ 175.858] (II) Initializing built-in extension RENDER
[ 175.858] (II) Initializing built-in extension RANDR
[ 175.858] (II) Initializing built-in extension COMPOSITE
[ 175.858] (II) Initializing built-in extension DAMAGE
[ 175.887] (II) AIGLX: Screen 0 is not DRI2 capable
[ 175.887] drmOpenDevice: node name is /dev/dri/card0
[ 175.887] drmOpenDevice: open result is 14, (OK)
[ 175.888] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 175.888] drmOpenDevice: node name is /dev/dri/card0
[ 175.888] drmOpenDevice: open result is 14, (OK)
[ 175.888] drmOpenByBusid: drmOpenMinor returns 14
[ 175.888] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 175.888] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 176.017] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[ 176.017] (II) The file referenced, is *NOT* loaded
[ 176.017] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[ 176.017] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 176.019] (EE) AIGLX: reverting to software rendering
[ 176.437] (II) AIGLX: Loaded and initialized swrast
[ 176.437] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 176.442] (II) VBoxVideo(0): Setting screen physical size to 270 x 203
[ 176.899] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 176.899] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 176.899] (II) LoadModule: "evdev"
[ 176.901] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 176.935] (II) Module evdev: vendor="X.Org Foundation"
[ 176.935] compiled for 1.10.99.902, module version = 2.6.0
[ 176.935] Module class: X.Org XInput Driver
[ 176.935] ABI class: X.Org XInput driver, version 13.0
[ 176.935] (II) Using input driver 'evdev' for 'Power Button'
[ 176.935] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 176.935] (**) Power Button: always reports core events
[ 176.935] (**) Power Button: Device: "/dev/input/event3"
[ 176.936] (--) Power Button: Found keys
[ 176.936] (II) Power Button: Configuring as keyboard
[ 176.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 176.936] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 176.936] (**) Option "xkb_rules" "evdev"
[ 176.936] (**) Option "xkb_model" "evdev"
[ 176.936] (**) Option "xkb_layout" "us"
[ 177.050] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 177.050] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 177.050] (II) Using input driver 'evdev' for 'Sleep Button'
[ 177.050] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.050] (**) Sleep Button: always reports core events
[ 177.051] (**) Sleep Button: Device: "/dev/input/event4"
[ 177.051] (--) Sleep Button: Found keys
[ 177.051] (II) Sleep Button: Configuring as keyboard
[ 177.051] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input4/event4"
[ 177.051] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 177.051] (**) Option "xkb_rules" "evdev"
[ 177.051] (**) Option "xkb_model" "evdev"
[ 177.051] (**) Option "xkb_layout" "us"
[ 177.055] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event1)
[ 177.055] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
[ 177.055] (II) Using input driver 'evdev' for 'VirtualBox USB Tablet'
[ 177.055] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.055] (**) VirtualBox USB Tablet: always reports core events
[ 177.055] (**) VirtualBox USB Tablet: Device: "/dev/input/event1"
[ 177.056] (--) VirtualBox USB Tablet: Found 9 mouse buttons
[ 177.056] (--) VirtualBox USB Tablet: Found scroll wheel(s)
[ 177.056] (--) VirtualBox USB Tablet: Found relative axes
[ 177.056] (--) VirtualBox USB Tablet: Found absolute axes
[ 177.057] (--) VirtualBox USB Tablet: Found x and y absolute axes
[ 177.057] (II) VirtualBox USB Tablet: Configuring as mouse
[ 177.057] (II) VirtualBox USB Tablet: Adding scrollwheel support
[ 177.057] (**) VirtualBox USB Tablet: YAxisMapping: buttons 4 and 5
[ 177.057] (**) VirtualBox USB Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.057] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/input/input1/event1"
[ 177.057] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE, id 8)
[ 177.057] (EE) VirtualBox USB Tablet: failed to initialize for relative axes.
[ 177.058] (II) VirtualBox USB Tablet: initialized for absolute axes.
[ 177.058] (**) VirtualBox USB Tablet: (accel) keeping acceleration scheme 1
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration profile 0
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[ 177.060] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js0)
[ 177.060] (II) No input driver/identifier specified (ignoring)
[ 177.062] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse0)
[ 177.063] (II) No input driver/identifier specified (ignoring)
[ 177.065] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 177.065] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 177.065] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 177.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.066] (**) AT Translated Set 2 keyboard: always reports core events
[ 177.066] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 177.066] (--) AT Translated Set 2 keyboard: Found keys
[ 177.066] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 177.066] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 177.066] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 177.066] (**) Option "xkb_rules" "evdev"
[ 177.067] (**) Option "xkb_model" "evdev"
[ 177.067] (**) Option "xkb_layout" "us"
[ 177.070] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event5)
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 177.070] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[ 177.070] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event5"
[ 177.070] (--) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found relative axes
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[ 177.071] (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[ 177.071] (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.071] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
[ 177.071] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 10)
[ 177.072] (II) ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 177.074] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
[ 177.074] (II) No input driver/identifier specified (ignoring)
[ 177.077] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 177.078] (II) No input driver/identifier specified (ignoring)
[ 177.082] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event2)
[ 177.082] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
[ 177.082] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[ 177.082] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.082] (**) VirtualBox mouse integration: always reports core events
[ 177.082] (**) VirtualBox mouse integration: Device: "/dev/input/event2"
[ 177.083] (--) VirtualBox mouse integration: Found 1 mouse buttons
[ 177.083] (--) VirtualBox mouse integration: Found absolute axes
[ 177.083] (--) VirtualBox mouse integration: Found x and y absolute axes
[ 177.083] (II) VirtualBox mouse integration: Configuring as mouse
[ 177.083] (**) VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[ 177.083] (**) VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.084] (**) Option "config_info" "udev:/sys/devices/virtual/input/input2/event2"
[ 177.084] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: MOUSE, id 11)
[ 177.084] (II) VirtualBox mouse integration: initialized for absolute axes.
[ 177.084] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[ 177.086] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js1)
[ 177.086] (II) No input driver/identifier specified (ignoring)
BTW it was a real hassle to find the content of those files when you do not have a terminal emulator to use.

Interface/Gamma issue - Display profiling

If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in some application-windows. Never happend in Tiger so I figure it's a Leopard issue.*
If you use Gamma 1.8, the Apple default, Photoshops windows (in my case) look perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know the boxes are there).
All the other settings you can choose while profiling - like temperature, luminance, chromatic adaption, profile-type etc. don't influence windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 (like a CRT) OR do you use L* and live with the boxes OR have you profiled your display properly/with L* but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.

*So here's what I think happens (+ my idea to solve the grey-boxes issue):*
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be new, that's why there were no issues with Tiger) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
*After that the grey boxes dissapear and everything is back to normal.* There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (Just a theory, hopefully not...)
*Problem 1:*
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me.
*Problem 2:*
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
*I hope Apple comes up with a real solution soon, this seems like too much of a hack - considering the delicate nature of colour management.*
*If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.*
This is pretty much mirrored on the Adobe forums btw.

H264(Youtube/Vimeo Preset) export looks flat and desaturated- H264 Gamma?

All my h264 output both quickitme and mp4 looks flat and desaturated after export compared to to the program window.This happends with both cs5.5 and cs6.
I know there is some h264 bug with Quicktime but its flat on Youtube also( in Safari) I thought this gamma issue has been sorted out?
How can I output my files to youtube so it looks the same as my Program monitor on youtube? I know all screens are different and you need a color calibrated montior( I have that) but why the shift?
It just does not seem that anyone has an answer. x264 does not work... anything else? QUickitme x does not have the ability to do the "opacity fix"
How will i get that my output on my client screen will not be so flat. ( I know it wont be exactly the same (as TVs in a showroom) but the difference between the video inside premier and outside is VAST!
I dont want to "fix" it by addinga contrast and saturation layer and them on a Windows machine maybe its then overly contrasty?
I'm on 17" MAcbook PRo Using anexternal calibrated NEC Monitor.
Did I miss a major answer on the web somewhere?

So what do you guys do? Just add an extra layer of process ( I have added a fast color correction Adjustment layer and clipping the black at 10 and the highlights at 245 and putting the saturation at 120. Its a thumbsuck though...
How on earth do people who colour grade on Davinc or Lustre etc output there stuff to Vimeo.(Yes I know it goes to film or TV , but what about thier showreel?) It also uses H264? Is there ANY codec I can use to upload to Youtube that will look like my program monitor?
It is facinating how these companies provide all these wonderful tools and in the final polished output you cannot get it too look llike it looked inside the product! Baffling!
If I had a Windows machine would I have this problem?

IPhoto prints and gamma

For quite a while now, my prints from iPhoto (cameras Canon 30D and Sony Cybershot) have all been coming out much darker and duller than the appear on my Cinema Display. I've been poking about and have learned about Apple displays using 1.8 gamma rather than the 2.2 of a PC. To my dismay, I also learned that prints ordered through iPhoto are printed by Kodak Gallery (formerly Ofoto?) and they are not automatically adjusted to match the gamma of Apple displays. This would explain the dark results. Is everything I've stated here actually true? Is any of it true? Why would Apple partner with a printing service that would not adjust for Apple's beautiful displays? Do I have to switch my monitor to 2.2 in order to see how my prints will actually turn out when I order them through Apple? And why were the first prints / photo books that I ordered (back a few versions of iPhoto earlier) so much better / brighter / truer to my display?

Michael:
It seems that a gamma of 2.2 is more prevalent in the world than 1.8 because most digital printers are PC driven of sorts. Nature of the beast I guess.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

/etc/modprobe.d/nouveau_blacklist.conf NOT being honored [SOLVED]

Topic says it all:
$ cat /etc/modprobe.d/nouveau_blacklist_ck.conf
blacklist nouveau
$ lsmod | grep nouv
nouveau 709777 0
ttm 54808 1 nouveau
drm_kms_helper 25753 1 nouveau
drm 185576 3 nouveau,ttm,drm_kms_helper
i2c_algo_bit 5199 1 nouveau
mxm_wmi 1425 1 nouveau
video 11133 1 nouveau
i2c_core 19495 6 nouveau,drm_kms_helper,drm,i2c_algo_bit,nvidia,i2c_i801
button 4406 1 nouveau
Last edited by graysky (2011-11-24 13:37:34)

Hold on guys.... the problem seems to be xorg. If I boot runlevel 3, no nouveau. As soon as I start X:
$ grep -i nouveau /var/log/Xorg.0.log
[ 60.195] (==) Matched nouveau as autoconfigured driver 0
[ 60.195] (II) LoadModule: "nouveau"
[ 60.196] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 60.198] (II) Module nouveau: vendor="X.Org Foundation"
[ 60.241] (II) NOUVEAU driver
[ 60.241] (II) NOUVEAU driver for NVIDIA chipset families :
But it is the nvidia modules that I am using:
$ grep -i nvidia /var/log/Xorg.0.log
[ 60.192] (II) Module glx: vendor="NVIDIA Corporation"
[ 60.192] (II) NVIDIA GLX Module 290.10 Wed Nov 16 18:01:24 PST 2011
[ 60.195] (==) Matched nvidia as autoconfigured driver 2
[ 60.212] (II) LoadModule: "nvidia"
[ 60.212] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 60.219] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 60.241] (II) NOUVEAU driver for NVIDIA chipset families :
[ 60.242] (II) NVIDIA dlloader X Driver 290.10 Wed Nov 16 17:41:10 PST 2011
[ 60.242] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 60.422] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 60.423] (II) NVIDIA(0): Creating default Display subsection in Screen section
[ 60.423] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 60.423] (==) NVIDIA(0): RGB weight 888
[ 60.423] (==) NVIDIA(0): Default visual is TrueColor
[ 60.423] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 60.423] (**) NVIDIA(0): Enabling 2D acceleration
[ 61.535] (II) NVIDIA(GPU-0): Display (Ancor Communications Inc ASUS MS228 (DFP-2)) does not
[ 61.535] (II) NVIDIA(GPU-0): support NVIDIA 3D Vision stereo.
[ 61.536] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 61.536] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 61.536] (--) NVIDIA(0): VideoBIOS: 70.06.1f.00.21
[ 61.536] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 61.536] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 61.536] (--) NVIDIA(0): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 61.536] (--) NVIDIA(0): Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.536] (--) NVIDIA(0): Ancor Communications Inc ASUS MS228 (DFP-2): 330.0 MHz maximum
[ 61.536] (--) NVIDIA(0): pixel clock
[ 61.536] (--) NVIDIA(0): Ancor Communications Inc ASUS MS228 (DFP-2): Internal Dual
[ 61.536] (--) NVIDIA(0): Link TMDS
[ 61.574] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been
[ 61.574] (**) NVIDIA(0): enabled on all display devices.
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1280x720" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1280x720".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1280x720" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1280x720".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid HorizSync range
[ 61.574] (WW) NVIDIA(0): (30.000-83.000 kHz) would exclude this mode's HorizSync
[ 61.574] (WW) NVIDIA(0): (28.1 kHz); ignoring HorizSync check for mode
[ 61.574] (WW) NVIDIA(0): "1920x1080".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1920x1080".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1440x576" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1440x576".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1440x576" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1440x576".
[ 61.574] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.574] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.574] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.574] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.574] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.574] (WW) NVIDIA(0): "1920x1080".
[ 61.575] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.575] (WW) NVIDIA(0): contradicts itself: mode "1280x720" is specified in the
[ 61.575] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.575] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.575] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.575] (WW) NVIDIA(0): "1280x720".
[ 61.575] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.575] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.575] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.575] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.575] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.576] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.576] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.576] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.576] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.576] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.576] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.576] (WW) NVIDIA(0): contradicts itself: mode "720x576" is specified in the
[ 61.576] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.576] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.576] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode "720x576".
[ 61.577] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.577] (WW) NVIDIA(0): contradicts itself: mode "1280x720" is specified in the
[ 61.577] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.577] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.577] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.577] (WW) NVIDIA(0): "1280x720".
[ 61.577] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.577] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.577] (WW) NVIDIA(0): EDID; however, the EDID's valid HorizSync range
[ 61.577] (WW) NVIDIA(0): (30.000-83.000 kHz) would exclude this mode's HorizSync
[ 61.577] (WW) NVIDIA(0): (28.1 kHz); ignoring HorizSync check for mode
[ 61.577] (WW) NVIDIA(0): "1920x1080".
[ 61.577] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.577] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.577] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.577] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.577] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.577] (WW) NVIDIA(0): "1920x1080".
[ 61.578] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.578] (WW) NVIDIA(0): contradicts itself: mode "1440x576" is specified in the
[ 61.578] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.578] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.578] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.578] (WW) NVIDIA(0): "1440x576".
[ 61.578] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.578] (WW) NVIDIA(0): contradicts itself: mode "1440x576" is specified in the
[ 61.578] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.578] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.578] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.578] (WW) NVIDIA(0): "1440x576".
[ 61.578] (WW) NVIDIA(0): The EDID for Ancor Communications Inc ASUS MS228 (DFP-2)
[ 61.578] (WW) NVIDIA(0): contradicts itself: mode "1920x1080" is specified in the
[ 61.578] (WW) NVIDIA(0): EDID; however, the EDID's valid VertRefresh range
[ 61.578] (WW) NVIDIA(0): (55.000-75.000 Hz) would exclude this mode's VertRefresh
[ 61.578] (WW) NVIDIA(0): (50.0 Hz); ignoring VertRefresh check for mode
[ 61.578] (WW) NVIDIA(0): "1920x1080".
[ 61.598] (II) NVIDIA(0): Assigned Display Device: DFP-2
[ 61.598] (==) NVIDIA(0):
[ 61.598] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 61.598] (==) NVIDIA(0): will be used as the requested mode.
[ 61.598] (==) NVIDIA(0):
[ 61.598] (II) NVIDIA(0): Validated modes:
[ 61.598] (II) NVIDIA(0): "nvidia-auto-select"
[ 61.598] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 61.620] (--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
[ 61.620] (--) NVIDIA(0): option
[ 61.620] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 61.620] (II) NVIDIA: access.
[ 61.623] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 61.623] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 61.623] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 61.623] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 61.623] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 61.623] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 61.623] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 61.623] (II) NVIDIA(0): Config Options in the README.
[ 61.626] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 61.711] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 61.711] (==) NVIDIA(0): Backing store disabled
[ 61.711] (==) NVIDIA(0): Silken mouse enabled
[ 61.711] (==) NVIDIA(0): DPMS enabled
[ 61.711] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[ 61.711] (WW) NVIDIA(0): such display device could be found, or all display devices
[ 61.711] (WW) NVIDIA(0): by that name are currently unavailable.
[ 61.711] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[ 61.711] (WW) NVIDIA(0): display device could be found, or all display devices by
[ 61.711] (WW) NVIDIA(0): that name are currently unavailable.
[ 61.712] (II) NVIDIA(0): [DRI2] Setup complete
[ 61.712] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 61.787] (II) config/udev: Adding input device HDA NVidia HDMI/DP (/dev/input/event10)
[ 61.787] (II) config/udev: Adding input device HDA NVidia HDMI/DP (/dev/input/event7)
[ 61.788] (II) config/udev: Adding input device HDA NVidia HDMI/DP (/dev/input/event8)
[ 61.788] (II) config/udev: Adding input device HDA NVidia HDMI/DP (/dev/input/event9)

Quicktime X and After Effects CS4 - Unwanted Color / Gamma shift

Hello,
Upon the import of ANY video footage file into After Effects CS4, there is an immediate color (I am guessing a gamma shift) difference between how the video appears in Quicktime (both X and the older player) and how it appear in the After Effects composition window.
Footage appears to be darker in AE and lighter in quicktime, both before and after export. The gamma/color then appears roughly the same when being compressed via h.264 and uploaded to the web (the same in Safari, much darker via Firefox).
My main concern is simply getting AE's color to match Quicktime's so that I can have as close of a match between the color I think I have created in AE, and the actual color that appears in my final output to the web.
I have tried using all of the fixes to be found relating to gamma shifts via .h264, prores, etc. but nobody seems to have this problem with every codec, even animation. I have tried assigning color profiles in AE, matching quicktime legacy formats, etc. All of the options available in AE to no avail.
My monitor is calibrated fine, I am using Perian, All of the latest software updates. Any advice much appreciated!

Hi, thanks for the link. While helpful I am still having problems!
I tried using the method described with Automator to assign a color profile to a test Animation file, created from scratch in AE and rendered out as an Animation with no color management (previously it made no difference to the quicktime gamma shift as to if I had assigned a working color space or not within AE).
Automator only gives three color profile options, HD, SD, or PAL. I tried using HD as this is the size of video I normally work in (although I am also working in PAL), and ran Automator. I also tried using PAL and got identical results. It took about 30 seconds to finish and the result indeed looked much better in QT, and opened up in AE looking identical to a copy of the same .mov file with no color correction.
However, there is *still some change in the image quality as it appears in QT from how it (and the original) appears in AE*.
Original created / displayed in AE: What I am trying to maintain
Rendered out, Automator color profile HD assigned, and opened in QT: Gamma looks good but colors slightly more saturated than original in AE.
Rendered out with no color profile: Original problem with large gamma shift making everything bleached/washed out.
I have a screen shot I can show you to illustrate this here:
http://www.yousendit.com/download/THE0ek9xa0RxRTNIRGc9PQ
While the difference is subtle you can look at the RGB numbers and see the middle example is indeed more saturated.
Perhaps I need to use another color profile when working with the animation codec for animations created from scratch in AE to avoid this saturation shift, other than HD or PAL? Would you know of how to do this?
Also, would you know of how to change this, and perhaps a way of changing qucktime's interpretation rules for all animation files per se, so that I do not need to go through every .mov with the animation codec and assign profiles to them?
Many thanks for your time and sorry for being so long winded!

Gamma: 1.8 or 2.2, etc.

Similar Messages

Maybe you are looking for