Color match two monitors

How can I adjust two displays for correct color matching? I have an HP w1907, which is my main computer monitor, and a Samsung SyncMaster P2370HD. The Samsung is connected to a Matrox MX02 Mini for external monitoring as well as to the pc for desktop extension. Each monitor has its proprietary adjustment tool, but very limited.
Do I need a hardware dedvice like the Spyder3 or Huey?

aldeco wrote:
Do I need a hardware dedvice like the Spyder3 or Huey?
It would be most advisable!
Except I think EyeOne gets better reviews than those two.

Similar Messages

Synchronizing Color Profiles of two monitors

How do i synchronize the color profile on my macbook pro with another monitor?

They are just different. Some monitors have a "control panel" (accessed by buttons on the monitor) that adjusts the color "tone" (don't know the technical term). I'm pretty sure Samsung monitors have this feature. Maybe the two monitors are set up differently.
You can also adjust the color using ColorSync feature of Mac OS X. Open System Preferences to the Displays pane. A control window opens on each display. Click on the Color tab. From there, you can calibrate the display so that they match as close as possible.
So first, adjust the color from the display, if that's possible. Then use System Preferences to get the two matched as closely as possible.

I have been having a issue with getting the colors on my monitor to match the colors fro my print lab. I now have the monitor calibrated to match the prints but when I open elements it doesn't use the same colors. If i have it use the calibrated profile b

I have been having a issue with getting the colors on my monitor to match the colors fro my print lab. I now have the monitor calibrated to match the prints but when I open elements it doesn't use the same colors. If i have it use the calibrated profile by changing the color management settings, the color picker no longer shows true white or black. How do I get elements 12 to honor the new calibrated settings?

Ok so I've done what you said and this is what it's come back ....
I don't know that these are the errors , but they're the things which don't look right ...
Throughout the shut down there is a recurring line ;
It says ;
Com.apple.launchd 1 0x100600e70.anonymous.unmount 301 PID still valid
Then there are 2 more which I think are related ;
Com.apple.securityd 29 PID job has I overstayed its welcome , forcing removal.
Then the same with fseventd 48 and diskarbitrationd 13
Oh and on Launchd1 : System : stray anonymous job at shut down : PID 301 PPID13 PGID 13 unmount...
Then the last process says "about to call: reboot (RB_AUTOBOOT).
Continuing...
And stops ...
Hope this means something to you ... Thanks again for your help so far :-)

3d Acceleration on two monitors with nvidia?

Is there any way to get two monitors that are running on the same pc and kernel BOTH be 3d accelerated in X?
Like two instances of X or two instances of the WM...or...something? I have an nvidia card for both of my monitors and would like both accelerated...
Is this possible? Can I use the "nvidia" (as opposed to "nv") driver for both?
I'm unclear on this issue, any help would be appreciated.

I finally had a chance to do some more exploration.
Currently, I've got two fluxboxes running across my monitors (no xinerama right now). The only thing I don't like is that I still can't get the "nvidia" driver to work for both displays.
Strangely enough, when I try to use the "nvidia" module for both, upon "startx" both monitors go black and ctl + alt + backspace won't kill X, I have to hit the reset button.
Here is the log generated after both monitors going blank. Any help would be very appreciated:
<----------I editted a few lines out here and there in the log, due to the forums truncating the message. I editted in particular the long series of line starting with NV or NVIDIA and then a bunch of resolutionm combos. let me know if there is something particular you want me to post. ---------->
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "speedo"
(WW) Warning, couldn't open module speedo
(II) UnloadModule: "speedo"
(EE) Failed to load module "speedo" (module does not exist, 0)
(II) LoadModule: "freetype"
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 6.8.1, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.6106
Module class: XFree86 Video Driver
(II) LoadModule: "nv"
(II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o
(II) Module nv: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "keyboard"
(II) Loading /usr/X11R6/lib/modules/input/keyboard_drv.o
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) NVIDIA X Driver 1.0-6106 Wed Jun 23 08:14:45 PDT 2004
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, GeForce4 440 Go 64M,
GeForce4 410 Go 16M, Quadro4 500 GoGL, Quadro4 550 XGL, Quadro4 NVS,
GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X,
GeForce4 MX 420 with AGP8X, GeForce4 448 Go, GeForce4 488 Go,
Quadro4 580 XGL, Quadro4 280 NVS, Quadro4 380 XGL,
GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, 0x0313, GeForce FX 5600SE,
0x0316, 0x0317, GeForce FX Go5600, GeForce FX Go5650,
Quadro FX Go700, 0x031D, 0x031E, 0x031F, GeForce FX 5200,
GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200SE,
GeForce FX Go5200, GeForce FX Go5250, GeForce FX Go5200 32M/64M,
0x0329, Quadro NVS 280 PCI, Quadro FX 500, GeForce FX Go5300,
GeForce FX Go5100, 0x032F, GeForce FX 5900 Ultra, GeForce FX 5900,
GeForce FX 5900XT, GeForce FX 5950 Ultra, 0x0334, Quadro FX 3000,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, 0x0345, GeForce FX Go5700, GeForce FX Go5700,
0x0349, 0x034B, Quadro FX Go1000, Quadro FX 1100, 0x034F
(II) Primary Device is: PCI 01:00:0
(WW) NVIDIA: No matching Device section for instance (BusID PCI:2:4:0) found
(--) Chipset NVIDIA GPU found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[6] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[7] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[8] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0x48000000 - 0x4fffffff (0x8000000) MX[B](B)
[11] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[12] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[13] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[14] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[18] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[19] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[20] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[22] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[23] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[24] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[25] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[26] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[27] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[29] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[30] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[31] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
(--) Chipset GeForce2 MX/MX 400 found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[6] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[7] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[8] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0x48000000 - 0x4fffffff (0x8000000) MX[B](B)
[11] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[12] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[13] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[14] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[18] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[19] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[20] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[22] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[23] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[24] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[25] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[26] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[27] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[29] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[30] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[31] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0xff000000 e: 0xffffffff correcting
(II) NonSys
[0] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[1] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[2] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[3] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[4] -1 0 0xf0000000 - 0xf0000000 (0x1) MX[B]
[5] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[6] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[7] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[8] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[9] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[10] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[11] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[12] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[13] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[14] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[15] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[16] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[17] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[18] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[19] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[20] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[22] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[24] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[25] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[26] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[27] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[28] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
[29] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[30] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0x48000000 e: 0x4fffffff correcting
<----------EDIT---------->
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Reloading /usr/X11R6/lib/modules/libfb.a
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Reloading /usr/X11R6/lib/modules/libramdac.a
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? Yes, I do.
(II) LoadModule: "rac"
(II) Loading /usr/X11R6/lib/modules/librac.a
(II) Module rac: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) resource ranges after preInit:
[0] 1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B]
[1] 1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B]
[2] 0 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B]
[3] 0 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B]
[4] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B)
[5] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[6] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[7] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[8] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[9] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[10] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[11] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[12] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[13] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[14] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[15] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[16] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[17] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[18] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[19] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[20] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[21] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[22] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[23] 1 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[24] 1 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[25] 1 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[28] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[29] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[30] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[31] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[32] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[33] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[34] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[35] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[36] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[37] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[38] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[39] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[40] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[41] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[42] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
[43] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[44] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
[45] 1 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[46] 1 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) NVIDIA(0): Setting mode "1280x960"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(EE) NVIDIA(0): Failed to load GLX
(==) RandR enabled
(==) NV(1): Write-combining range (0xe0000000,0x4000000)
(II) NV(1): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) NV(1): Backing store disabled
(==) NV(1): Silken mouse enabled
(WW) NV(1): Option "RenderAccel" is not used
(==) RandR enabled
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Device: "/dev/psaux"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc101"
(**) Keyboard1: XkbModel: "pc101"
(**) Option "XkbLayout" "us"
(**) Keyboard1: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/local/, removing from list!
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
SwitchToMode - scrn: 0 clock: 74250
hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
Checking against clock: 148500 (148500)
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
Checking against clock: 94500 (94500)
hdsp: 1024 hbeg: 1072 hend: 1168 httl: 1376
vdsp: 768 vbeg: 769 vend: 772 vttl: 808 flags: 5
Checking against clock: 56300 (56300)
hdsp: 800 hbeg: 832 hend: 896 httl: 1048
vdsp: 600 vbeg: 601 vend: 604 vttl: 631 flags: 5
Checking against clock: 74250 (74250)
hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) NVIDIA(0): Setting mode "640x480"
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
SwitchToMode - Succeeded
GetModeLine - scrn: 0 clock: 74250
GetModeLine - hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
GetModeLine - scrn: 0 clock: 74250
GetModeLine - hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
SwitchToMode - scrn: 0 clock: 148500
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
Checking against clock: 148500 (148500)
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) NVIDIA(0): Setting mode "1280x960"
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
SwitchToMode - Succeeded
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing.

OSX Print dialogue's Color Matching "Automatic" option - what's it actually doing?

I'm trying to understand OSX's colour management options clearer. It seems that the Print dialogue's default option for Color Matching is set to "Automatic". Is this as good as no colour management, because a specific profile isn't selected or is it actually using a default profile?
To stop the OSX driver from colour correcting my file and leave it to the printer manufacturer's driver you should set it to the other option (eg. eg. “Vendor Matching” (10.5) and “In Printer” (10.6) - or depends on what printer you have chosen) and then save a preset. Not everyone thinks to do this so that's why I'm interested in knowing exactly what the "Automatic" option is doing.
Your help is most appreciated!
Cheers,
Cojcolds

I understood your note to say that when "Color Matching" is set to ColorSync: Automatic the images in the file will first be converted through the monitor profile (in my case I'm currently using the "canned" LCD Display profile), then through the printer's profile (I have a desktop Fuji Xerox DocuPrint C1110B), correct?
Correct. Let's say you're using the working RGB color space of Adobe RGB in Photoshop. At all times, that color is being translated to the monitor color space by ColorSync for the rendition that is actually displayed. The file itself remains Adobe RGB, but that's not your monitor's profile, so it needs to be continuously converted for display.
When you print the image, the first thing ColorSync does is convert the color space from Adobe RGB to your monitor profile (all with temporary data, not to the original). Now the image is in the color space you were viewing, which is where is needs to be since the idea is for the print to match the monitor color you are looking at. But the printer is not a monitor, so the monitor profile color space the data is currently in is not correct for printing. So it goes through a second conversion from the monitor color space to the printer profile's color space. That is what finally gets sent to the printer.
This is where any automatic color correction must be off. You've already told ColorSync to use the proper profiles to achieve a print that will match the monitor as closely as possible. This assumes of course you have accurate profiles for both your monitor, and the printer with the paper being used.
As a further test, I then ColorSync to the AdobeRGB(1998) profile and made a new ps file. The RGB values in the distilled PDF were still the same as the Word doc.
That's what throws people off. An RGB value isn't a specific color. It's a representation of where that RGB value falls in relation to *L*A*B. So a fully saturated red of 255,0,0 will look different in a short color space as opposed to a larger space. Here's an example (see image below). I have two different profiles overlapping each other. The red point circled in green is the most saturated red that can be attained in relation to *L*A*B in that smaller color space. The point circled in yellow is that larger space's most saturated red. In both cases (the confusing aspect), both will assign 255,0,0 to that point, but one would obviously be a richer red than the other. Think of it this way. 255,0,0 is the maximum color space that particular color space (profile) can handle within *L*A*B. It's not necessarily the maximum red we can see in the visible color spectrum.
So, your converted files look the same because ColorSync is generating the color based on your monitor profile for display. Since that's always the same, the color will look the same, regardless of the input RGB profile. At least as long as you don't use a really small RGB space as an assigned color space and squeeze it down to some noticeably dull color.
I'm a trainer for Fuji Xerox and am writing a course for our Mac users on Colour Management (in particular for our high-end production RIPs (Fiery/Creo/FreeFlow) with serious colour management being applied).
Fun! I've been doing prepress work as as in-home business for quite a few years now, but worked in a couple of different high end print shops for many years. Last thing I used on that end was a Scitex Brisque RIP. As I'm sure you know, Creo bought out Scitex. I'm sure RIPs have changed a lot since I last looked at one.
I only discovered the other day that the Mac OS has the "Color Matching" option and wondered if the OS was in any way bending the colour values before our RIPs have a chance to properly manage the colours. So far it looks like the setting is not having any impact.
It all depends on where your settings are on both the Mac and at the RIP. Too long of an explanation to go into here I think.
As a further note, I even tried setting ColorSync to the "Generic CMYK" profile and the distilled PDF still showed the correct RGB values. So, maybe the print to PDF option is ignoring the Color Matching settings or something else is at play but this setting is still a mystery to me...
ColorSync will only apply matching profiles on the fly. So something would already have to by CMYK before it would apply the Generic CMYK profile. Which no one in their right mind would ever use. It's the flattest, ugliest CMYK profile you will ever see.

Need help on matching two 23" ACDs

I currently have two 23" ACDs connected to one ATI Radeon 4870 in my Mac Pro. My problem is the brightness and color on the displays vary greatly to the point that it is easily noticable by the naked eye. Is there anyway to calibrate the two monitors to match each other using only one video card. I have a HueyPro, but it wants me to adjust contrast on the monitors so I'm assuming it was built for a PC monitor. Any help is greatly appreciated.

No way. It's genuine cryptography and there is no way to derive the original serial number from an install's activation key. You can only deactivate all installs and then reactivate them based on a list. Otherwise you can simply try to find a free activation from one of your serial numbers...
Mylenium

Calibrating two monitors

Hi, I have a Mac Pro 2 x 2.8 intel and I am running a Dell WFP 3008 and a Dell WFP 2407 dual display, can anyone let me know how I calibrate both monitors, I use a gretag macbeth eye one calibration device.
Thanks.
Jason

Calibrating two monitors of different models, or worse, different brands, is really difficult. The colors and/or contrast don't match well, even after calibrating both and creating separate profiles. I used to have two monitors, a Sony F400 19" CRT, and a Dell/Sony 17" CRT. The F400 had truer colors, while the Dell/Sony always looked warmer (redder), and a bit ore contrasty. I used a GretagMacbeth Eye One Display (first version). I now use Color Munki and a single Dell 2408WFP, so I'm not sure if this still hold true if I had monitors of different model or brand.

How to synchronize colors with two different video cameras

I own Sony FX1 and HC9 video cameras. The color between the two video cameras can be pretty noticeable, and I tend to flip between the two cameras a lot during editing. Ideally I would get them to match up better before I start filming, but despite my attempts, I still can see a noticeable difference between them in post-production. I know I can use the color corrector filter to adjust the colors, but is there a more effective way to adjust the colors of the two video so they match better? I have used that eyedropper on the "visual" screen of the color corrector to adjust the white balance. Is there something similar where I could for example click the eyedropper on the blue of one video and it would change the blue of the video from the second camera to match?

You don't really have the controls for that in FCE. You can't fine tune the color with real precision for color matching in FCE. There is a match hue function with the eyedropper, but without separate shadows, mids, and highlight color controls there is only so much you can do.

I would like to change the colour of bars in a chart without losing the underlying default texture associated with my chosen theme. None of the 3D textured fills offered in "Chart Colors" match the textured fill of the theme. Any suggestions?

I would like to change the colour of bars in a chart without losing the underlying default texture associated with my chosen theme. None of the 3D textured fills offered in "Chart Colors" match the textured fill of the theme. Any suggestions?

Thanks Gary, but no, that does not work. First of all, I can't select each bar individually. When I click on one bar, all three bars are selected.
When I use "inspector > graphic" I have 5 fill options: none, color, gradient, image, tinted image. The default selection for the theme I'm using is image. What I would like to use for my charts is the same image that this theme uses for table headers. It has the same texture as the chart, but a different colour. Using anything but image or tinted image removes the texture from the fill.
I have found I can do one of two things. I can select tinted image from the fill selections in "inspector > graphic" or I can select 2D Image Fills from "inspector > chart > chart colors". The first choice does not allow me to match the table header colour because it only allows me to apply a tint to the existing colour and adjust its opacity. The existing colour has too much influence on the fill, so I can't find an RGB adjustment that will match the table header colour. The image selections from "inspector > chart > chart colors" do not quite match the colour or the texture. Again, I can try to tint the image, but I still can't get it to match and the texture is not the same anyway.
The image I want to use obviously exists in the software as it is an attribute of the theme, but for some reason is inaccessible. The other angle I have tried is to edit the theme, but I can't figure out how to do that either.

LR3 Print Module: printing to profile - unable to change Color Matching

Hi
I use LR3 in 32 bit mode (there is no 64bit driver for HP DesignJet 130n).
I always print to profiles. In LR2 I had to make sure that in the PrintSettings the option Color Matching was set to "Vendor Machine", because although I saved this setting, LR never remembered.
Now with LR3 the option is again set to"Color Sync" but this time it cannot be changed.
Any suggestion?
Thanks
Bruno

Bob,
My problem is exactly what you say: you must find the appropriate place in the printer interface where you can disable all color management performed by the printer driver.
In OS X (10.5.) I know only of two places where I can handle Color Management: "Print Settings" and "Profile" in the LR3 Print Module.
By default LR3 sets the Print Settings "Color Matching" to "Vendor Machine" if I choose "Managed by the Printer" for the Profile.
By default LR3 sets the Print Settings "Color Matching" to "ColorSync" if I choose a custom printer/paper profile.
Where/what is "the appropriate place in the printer interface where you can disable all color management performed by the printer driver" ?

Ps CS5 e Ps CS6 in Mavericks: (Two monitor)

Hello. Sorry for my bad English!!!
This is my great problem: After installation of Maverick on my MacPro Early 2008, when i launch Photoshop (CS5 or CS6 version) in my secondary monitor don't appear the palette of the struments by my works, but is only on surface by primary monitor!!! ...and my image is on the deep. It's impossible to work on this mode!!!
If i register the "Works Area" after reimposted palette of the tools ( Level, History, Color...ecc.ecc.) when i restart Photoshop ...the windows by second monitor is on the primary monitor!!!!
What's appened???
Tanckyou to all!!!
Alfredo Manicardi - [email protected] - www.scattinaturali.com

Tank
Messaggio originale----
Da: [email protected]
Data: 14-nov-2013 0.24
A: "Alfredo Manicardi"<[email protected]>
Ogg: Ps CS5 e Ps CS6 in Mavericks: (Two monitor)
    Re: Ps CS5 e Ps CS6 in Mavericks: (Two monitor)
    created by bwl2010 in Photoshop General Discussion - View the full discussion
I had the same problem and it was driving me nuts. Thanks to conradchavez.com Blog.
Multiple displays: If you put panels (including the Tools panel) on a secondary display and then switch applications, those panels may snap back to the primary display when you switch back. To avoid this, open System Preferences, click Mission Control, and turn off Displays Have Separate Spaces. Mavericks ships with that option on, so if you want to position Adobe application panels and windows on multiple displays you should turn off that option.
You will have to log out before it works. It worked for me.
Tankyou very mutch!!!!
Now is all perfectly funzionally!!!!
Ri- Tankyou!!!
Alfredo Manicardi
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5840183#5840183
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5840183#5840183
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5840183#5840183. In the Actions box on the right, click the Stop Email Notifications link.
           Start a new discussion in Photoshop General Discussion at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

VISTA color management and monitor calibration

Elements 7.0
VISTA Home Premium SP1
Nvidia 8600
Samsung SyncMaster 213T
Canon XSi
Multiple printers
Since getting new system with Vista, I haven't been able to get a print that looks like my screen. I tried Costco today and everything was much darker than I expected, but the reds were much richer. I read a lot about calibrating my monitor, but it is possible that there is more do it than that? Learning to adjust skin tone etc. in Photoshop, only to have the prints look bad is pretty frustrating.
Is the other option to invest in a quality printer, or go to a real lab instead of Costco?
Please use small words, since I'm not a professional.
Regards,
Michael

Michael, color management is certainly a difficult issue to perfect. My monitor is color calibrated but it doesn't guarantee that the prints will match. With the same image, I get different results from different printers and labs. I get the best results from labs in the local camera/photo shops, and the pricing for enlargements is still on par with like Snapfish or Kodak.
Check this setting in PSE: Edit>Color Settings...>Always Optimize for Printing. I would suggest color calibrating your monitor, then try different labs until you find the best results.

Problems with color matching when printing...

Hi, I work for a small family business in the P.O.P. industry. We currently have myself and one other designer, we both take illustrator files that have come from the graphic design firm that we contract with and get them ready to print on our Vutek QS3200. However ever since acquiring the printer we have begun to run into problems with the colors when printing. When the files are exported off of my computer, I use either .tif or .pdf files, they print as they should, the colors seem to match the proof and everything goes smoothly. However when the other designer exports a file, he tends to do mainly pdfs, the colors tend to be extremely different from where we want them. Also we will get very strange results, such as yesterday he kept getting a faint yellow 1/2" border around his prints. After I believe 3+ hours of him trying, I was given the original CD and instructed to try. After 15-20 minutes of making the changes that we needed to make (adding a new price point) and ripping, mine printed perfectly.
We both use Macs, both have CS3 Design standard, only differences between the computers are mine is newer and a bit faster, and I'm running OS 10.5.6 and he has 10.4. He has also at some point loaded various color profiles, whereas my CS package is just whatever the default is when I loaded it. When we were being trained he grabbed the color profile off of the Colorburst RIP server and loaded onto his computer, plus I believe he has a couple for freelancing purposes on there as well. My thought is that these profiles are somehow corrupting the files that are going through that computer, but I honestly am lost with it at the moment. He believes the problem lies within the fact that he does not have the newer OS, I honestly cannot see that as having any effect on this at all. I was wondering if anyone has run into any similar problems, or if anyone might have any advice on this issue? I would really like to be able to solve this, as I was hired to do mainly structural design for the P.O.P. and I'm having to put in a lot of overtime to get my work done along with the additional work that I'm having to do.
Thanks for your time

I've got a few years experience calibrating large format printers. First, the Yellow sounds like a file problem. I used to work with two workstations, one PC ( RIP station ), and one Mac ( file prep station ). I tend to agree with you in that the OS is probably not the problem. But, any Colorburst profiles should remain in the RIP, not in the originator application. My workflow consisted of creating EPS files that were based on established color settings in their given applications ( i.e., Illustrator, Photoshop ) which were interpreted by the RIP which had it's own calibrated profile ( perhaps more than one based on how many different substrates were being used ). Your partner may be complicating things by incorporating a RIP profile prematurely. If there are deviations big enough to be noticed, there has to be something in the application color settings that is causing some type of corruption. This could lead back to the operating system, but I would think it lies somewhere in Bridge or the application color settings. Start there. You should seriously consider implementing a calibration system if you do not have one already. Another slight possibility is the driver's ability to interpret files coming out of Leopard vs. files coming out of Tiger. It may benefit you both to be in the same operating system dynamics, using the same driver versions and RIP profiles. At the very least, match everything that is currently working successfully and put them on both machines. If there is still a noticeable problem in color matching, then something is seriously wrong and you should call in a prepress profiling expert. Hope this helps.

Color matching with multicam clips

Hello,
I'm trying to figure out how I can color match between my multicam clips in FCPX. I'm kind of a newbie, but I'm trying... :-)
If I double click on a multicam clip that I just created, I see all the clips expanded on the timeline. At that point, I can sync, edit, etc. If I color match there, it's very easy, and it works well. The problem is that I can't figure out how to save all my edits and then "un-expand" the mulitcam clip so it's just the one layered clip (same as if you just drag the multicam clip down from the events list).
I suppose I could just leave it expanded - but it would be easier to work with if it was just the one multicam clip, instead of all the clips inside it expanded out. So - how do I do it? Am I making sense? If the color matching applied to the actual event, it would be easy - and I could just create a new multicam clip and start a new project. However, it doesn't work that way and only applies the color matching to the clip in the timeline (as it should....).
Thanks for any help you might have.
Johnny

Hi Tom,
I've got a similar problem to the one you helped on this thread.
I'm trying to colour correct one of the multicam clips in the angle editor.
When I click colour match and hover over the other clip part of this multi cam clip nothing happens and the 'apply match' button remains greyed out.
I can colour match the individual cuts back in normal time line but of course I don't want to waste time doing it to every single clip/cut.
Why won't it let me colour correct in angle editor?
The mouse icon turns into a mini monitor when I hover over the clip i want to match to.
Any ideas?

Three Monitor Save, Two Monitor Hang- CS6

I have three monitors running from my Dell M6600 at work. I save a Premiere Project with any panel open on the third monitor. Then take my computer home where I only have two monitors and open the project file, Premiere hangs. It will never launch the application fully. It opens to the point where it would normally load project data, and then hangs.
As a workarround I have begun making sure I save the project with all panels on two screens. However, if I forget then the only solution I have is to go to work to open the project. (Or get a third monitor at home...)
I would love to be able to edit the project XML and remove or reset the panel layout. Anyone else experiencing this issue? or know how to "hack/workaround" the project file?

Jim Simon wrote:
I don't think that's correct. Each project loads with the last saved window arrangement, named or not. So he'll need to rearrange the windows before saving at work (or get that third monitor at home).
I'm just going by the help file:
http://helpx.adobe.com/premiere-pro/using/workspaces.html
"If a project saved with a custom workspace is opened on another system, the application looks for a workspace with a matching name. If it can’t find a match (or the monitor configuration doesn’t match), it uses the current local workspace."
But like I said, I haven't tested it out myself.

Color match two monitors

Similar Messages

Maybe you are looking for