Dual monitor management

Hi,
I just hooked up my new Mac Pro to two monitors. It's working fine, but have a couple of questions.
When I launch a full screen app (say, World of Warcraft) it blanks out my secondary monitor. Is there any way to prevent this, so I can still watch my IMs or use my web browser? I know I can run WoW in windowed mode, but I'd prefer not to.
Also, I'm still using my and PC for things, and find myself hooking it up to my second monitor now and then. Is there any way (Applescript?) to gather any windows that may have been on my second monitor when it was disconnected and stick them back on my primary display?
Thanks.

Hi diffkid,
Blanking out the secondary monitor is the default setting in World of Warcraft as it allows the game to access more of the video memory.
One way that I have seen Mac users circumvent this is by having the dock on the secondary screen (ie. by put the dock to the right while playing). This will allow them to still have access to other applications will playing the game on the left display.
As for gathering windows, I just use the "gather windows" button in the display preferences. It's not the quickest solution, but I keep the display preferences in my menu bar which makes it a little easier.
Hope that helps.

Similar Messages

Dual-monitor color management?

So I've got a dual-monitor setup running OS 10.7 on a Mac Pro, and color management in Bridge CS5.1 on my second screen is a mess. Both monitors have been individually calibrated with a Pantone Huey Pro (not perfect, but generally pretty consistent across screens).
Viewing an image in Bridge on my first screen, I have no problem. But the same image, when viewed on my second screen, appears heavily oversaturated. When I open the image in Photoshop or Preview, the color is accurate and is consistent across both screens. The below image illustrates the problem: the colors shown correctly in Photoshop (foreground) and incorrectly in Bridge (background). The Creative Suite color settings in Bridge show the settings as "synchronized" with the "North American General Purpose 2" default.
I'm sort of out of my depth here when it comes to color management. Do I have something set wrong? Is this a Lion-related bug? Any help would be appreciated.

The way I have it set up is this: I have two synchronized windows, one on each of my two displays. In one I have a content panel, metadata, collections, etc. In the second window I just have a preview panel, supplying me with a full-screen (almost) preview of any thumbnail I select from the content panel in the other window.
Content (assuming thumbnails as well) panel preview on one display and the Preview panel preview on the other display are both being generated by one application and that is Bridge. Like I said above, I don't think, in fact I'm almost certain this is impossible for Bridge to pull off because of the dual matrices (mathematical formulas) written into each custom display profile that occupy the same video chip to calculate and control hue/saturation appearance in color managed images. Think of the complexity involved. Now Adobe is known for creating workflow miracles with their programming but I doubt they'ld be able to pull that off with Bridge.
Photoshop can pull this off having one image on one display and dragging to the other where it makes the adjustment on the fly. I've seen the quick shift that occurs doing this. But I don't think Bridge can do this because of it's caching structure. I hope an Adobe employee chimes in to correct me.
Now this dovetails into your mentioning forcing a display into the sRGB space during calibration and profiling of each display. This is not what happens doing a hardware calibration. I'm assuming you pick your target Luminance (120 cd/m2 +/-), Gamma (2.2. gamma-usually native) and Color Temp (6500K). It doesn't matter if you did anyway, but what the hardware calibrator does is measure each display's RGB colorant and density range and write the data into the final profile that allows applications like Colorsync Utility to display a 3D gamut model and color managed applications like Photoshop to show colors as intended.
Your display may be close to sRGB but never exact to it because sRGB is a synthetic (made up) color space. Your display has physical anomalies that must be measured and written into the profile to properly display the intended appearance of color referencing the CIELAB color space which is based on human vision. Everything about computerized color in a color managed workflow is based on mapping color to display properly according to gamut size. A computer is a dumb machine and has to be told everything using math. You actually do have to draw it a map to follow.
Bridge's Preview pane looking different may be either referencing the other display profile or is stuck referencing the other and what's happening is the equivalent of Assigning one of the display profiles to the Preview like you can do to an image in Photoshop. Try it. Take your image and convert to one of your display profiles and assign the other display profile to it. Check if you see a slight shift. If Bridge's main Preview pane is stuck showing pixels mapped to (synthetic) sRGB then the same assigning of the display profile effect takes place.
And/or the thumbnails aren't color managed and the Preview pane is and maybe a bit of the above is compounding things. If you aren't confused now can you imagine trying to mathematically write the thumbnail previews on one display and the main Preview on the other both controlled by one application on top of caching and managing a large image database?
Keep the Preview pane and Content pane on one display. Edit your images in Photoshop/ACR/Lightroom on the primary display.
The Color Settings where you select North American Prepress...Web...General Purpose...etc. only applies to how images are handled and previewed that don't have an embedded profile. Are your jpeg images embedded with a profile? If so then this is not the issue. This doesn't apply to Raw captures because their previews are generated by the default Adobe Camera Raw settings.
Omke, no more Version Cue? That's welcome news!

Dual monitors, ICC profiles, color management...problems

Problem:
An image displayed in Safari and then pulled off the web into Photoshop shifts colors noticeably. This is esp. apparent in a side-by-side comparison on the same monitor with the Safari window open next to the Photoshop file window…they look very different.
Possible clues?
When I drag an image in Photoshop from one monitor to the other it shifts color after I release the mouse. In my two-monitor setup one is a large LCD (that's the "main" one) and the other is a MacBook Pro laptop. Even though they both have ICC profiles the laptop is slightly more saturated than the LCD…and Photoshop seems to mirror this but exaggerate it. For example: I pull the same image pulled off the web into two separate Photoshop files and then I display one on each screen: the one on the laptop will be /much/ more saturated than the one on the LCD.
In the end, if I have 4 windows open of the exact same image (2 on each screen: one in Photoshop and one in Safari) I am looking at 4 differently colored images - with the Photoshop images appearing even more exaggeratedly different than anything.
Obviously I understand that the two monitors will never look identical, but Photoshop seems to be imposing some extra color management on my files that makes it impossible to use with my previously very helpful dual-monitor setup.
Specs:
- Dual monitor setup: both are calibrated using an i1Display 2 from x-rite and have their own different profiles (this is new as of this week)
- Mac OS 10.6.6 (w/all current updates)
- Photoshop CS3 10.0.1 (w/all current updates) :: Edit>Color Settings : set to North America General Purpose 2
Help?

Just read this entire thread and wanted to leave a few comments and qualifications, first a couple of FACTS for all to consider.
1) I am not "new" to color management - in fact I am quite experienced in color management at a commercial level since the days of film back when getting "accurate color" was actually difficult. At this point it should be easy if the involved software is working correctly and impossible if it is not.
2) I have the top of the line color management solution provided by one of the top players in the color management market and am using it properly as verified by their technicians.
3) I am running 10.6 on my main computers. Mac Pro, 2 27inch iMac sandy bridge quad cores, and am using mac cinema displays (new ones) on all of them.
Now the rant - I have been trying to run down this or a similar and related issue for over a year. If you happen to be experiencing the same issue as I am, which I will summarize as trying to get 2 displays to display anywhere near the same color (even identical monitors) do not bother upgrading to CS5 as I am using CS5 as well as a bunch of other tools (Aperture, LR, etc, etc) - this is BROKEN and all I can get from any of the vendors involved is finger pointing from one to the other. Each of them wants to blame the other vendor for not doing something correctly but NONE of them can actually give me any details as to what exactly is the problem.
At this point in time I am holding the color management vendor I use to create the profiles responsible - the reason that I am doing that has nothing to do with what exactly the technical problem is. It s purely because they claim that the product is compatible with OS 10.6 and they claim that their software does EXACTLY what I want = mach two monitors. Now we all know that different monitors have slightly different gamuts but at the end of the day if two identical colors fall within the gamut of both monitors they should display the same. They don't. I have worked with my color management vendor for 6 months on this, they agree that it is not working properly, they blame apple but they cannot tell me exactly what the issue is.
If a company advertises and sells a product they claim to be compatible with a particular brand and version of hardware and software and they claim that it will manage color consistency across multiple monitors (even on differing machines) then I believe they are ultimately accountable for ensuring it actually works and resolving the issue - whatever it is, if it fails to function properly.
RB

Bug - Color Management Photoshop 11 and OS X 10.6 Dual Monitors

I need to know if it's just me, or others are seeing this.
Color management doesn't seem to work properly on dual monitors (MBP + Dell 2408) with Photoshop 11/CS4 and 10.6.
Each of my monitors is independently calibrated and all other apps work fine. For reference Lightroom 2.4/Preview 5.0/FireFox 3.5.2 all render properly across both monitors. Under 10.5 Preview 4.X did not render properly across two monitors, I was so happy in 10.6 it finally did, but PS is WAY more important so I'm kinda bummed.
Anyway, this seems to only happen on the 2nd monitor. If I move the menu bar (Prefs/Displays/Arrangement) to the external monitor making it primary monitor then it works for that monitor, but no longer for the laptop display. Photoshop render images on the 2nd monitor way washed out, but normally on the primary.
Photoshop 11.0.1 worked fine for me on dual monitors under 10.5.

So if you've read the links above regarding the "default monitor" issue, people have suggested that a potential workaround is to go to System Preferences>Displays>Arrangement>drag the menu bar from the first diplay to the second
Essentially you make your secondary monitor the default display.
For me what this does to PS is that it now displays the matching colors to Lr in the secondary display (which is now the default display with the menu bar at the top), BUT! when I drag the PS window back into my MacBook display it appears OVERLY saturated...
Strangely Lr appears the same in both windows, AND MORE IMPORTANTLY with the same colors, saturation, brightness, just as it did before I made my Dell 2405FPW the default display. Basically, Lr hasn't shifted in color from display to display or even from display to display after making the secondary monitor my new default display. It has retained the same integrity of colors through all these changes.
Which begs the question, if Lr can't handle dual displays and always uses the color profile of the display it begins in (starts running in), then why does it never shift in color and still look exactly the same after I've made my Dell 2405FPW my primary display?
And actually, if you look really really carefully, Lr DOES produce a color shift between displays as you drag it from one screen to the next. It's extremely fast and happens pretty much as you get 0.5 to 1 inch of the window into the secondary display. It's subtle on my monitor too, which leads me to believe that it performs this color correction properly, quickly, and seamlessly.
What if, my Photoshop 10.0 (old version of CS3) is not registering and understanding the secondary display's color profile correctly? What if it really is PS's fault because everything else looks right? Maybe the issue I'm having is different from what others are experiencing, after all we're in 10.6 now and most of these issues were reported in 10.4 and 10.5? I should probably upgrade my PS CS3 and see what happens?
jb, what version of PS do you have?

HP Zbook dual monitors issue - Intel HD Graphics Family ! in Device Manager

I have upgraded to Windows 10 x64 last week and I was using dual monitors. I discovered one of the monitor has stopped working and when I chekced in the device manager, one of the 2 display adaptors has got an exclaimation mark beside it and says: Windows has stopped this device because it has reported problems. (Code 43) I have tried uninstall and installing it to no avail. Anyone has the same issue? Is this a driver issue? Thank you.

it's as below: 17th July 2015 10.18.15.4256:

Dual monitor setup - need laptop on the left

Hi All
I'm running a dual monitor setup - specifically a HP G72 laptop and a widescreen monitor. I use the monitor as the default and sometimes I want to use the Laptop as a secondary screen for watching TV etc. My desktop is Enlightenment, I just changed to it from Gnome. My issue is that I want the laptop to be on the left of the monitor - that's how it is physically positioned - but when I switch the Laptop screen on all my applications shift over to the laptop screen. I've written 2 scripts, attached to hotkeys, one to turn the laptop off and the other to turn the laptop on. The script to turn the laptop on is as follows:
xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
--output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --left-of LVDS1
This works fine, applications stay where they should be, except that the physical position is incorrect; VGA1 should be to the right of LVDS1 like this:
xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
--output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --right-of LVDS1
However, when I use the second script all of the applications shift to the laptop but at least the physical position is correct. The issue appears to be something to do with laptops, almost as though when it's a laptop the default monitor is forced to be on the left. Has anybody got any suggestions how to get around this issue?
Thanks
Richard

This is due to your window manager treating the two monitors as a larger 'desktop' area - that combined with your specification of the pos=0x0 you are telling it to do this.
If you have only the VGA output on, the top left corner of the VGA monitor is 0x0. If you open a window, and it is placed 10 pixels in and down from the top left, it is at coordinates 10x10 in the x session. Then you turn on the laptop monitor and specify that the top left corner of the laptop monitor should now bo considered 0x0 - but nothing is done to move the windows, so the window with coordinates 10x10 is now near the top left of the laptop monitor.
I see 3 possible ways of acheiving what you want:
1) swap the "pos" parameters in your xrandr commands so that the monitor on the left is always at 0x0 and the one on the right is always at 1920x0 (or whatever). This will leave a large area of available X desktop that is not visible - I don't know how your window manager will treat this. It might try to map windows on the laptop screen space even though that screen is not on. I know openbox is easy to configure where it tries to place windows.
2) Keep the VGA monitor always at 0x0, but place the laptop monitor at a negative offset when you want it on. I don't actually know if X allows negative coordinates like that, but it's worth a shot.
3) Configure your window manager, or use a different window manager, so that it is aware of the two screens and treats them reasonably (e.g. moves windows when the desktop area is changed).
Last edited by Trilby (2014-07-12 12:15:42)

Dual monitor setup - primary monitor blank upon startup

Hello -
This has been vexing me for some time now. I've seen hints of this issue from other people but never the exact same circumstances and never do I see a definitive answer.
I have a dual monitor arrangement on my 8 core Clovertown (first generation) Mac Pro. After shutting the machine down, when I start it back up, the primary monitor almost always flickers very quickly then goes black while the machine boots, and the secondary monitor kicks on. Note - this never happens on restarts or waking up from sleep mode; just after starting up after completely shutting the machine down.
Exact specs are:
The afore mentioned first-gen 8 core Mac Pro (spring 2007), combined with an ATI 4870 graphics card, with the 24 inch Cinema Display LED serving as primary monitor (the one that's useless upon starting up), and my older 23 inch LCD as secondary display. Also worth noting - I'm aware the ATI 4870 is not officially supported in this generation of Mac Pro, however there were so many reports on the web of it working that I did the swap-out myself, and ended up getting the 24 inch LED since I then had the Mini Displayport on the back of my machine.
The only way I manage to get my machine working after starting back up is to restart it several times - literally up to over a dozen attempts sometimes, before the primary display finally does start functioning and I can begin working as normal.
Because there were many reports of the ATI 4870 working fine with this Mac Pro and word of other flickering monitor problems, I thought I'd ask despite the graphics card not being officially supported. Any ideas on how to remedy this problem so I don't have to keep restarting over and over before both my screens eventually work?
Thank you in advance.

So I have the same issue. I run dual 23" Apple Cinema Displays. For a while now the main monitor has had trouble waking up. I have also been unable to put the Display to sleep from the power button on the display. The other monitor seems to go to sleep fine. So when I get it to sleep and it won't start up, I usually restart and everything is fine. Today I can't get that monitor to come up at all. In addition, I have swapped ports on the video card switching the order of the monitors, no change. I also checked in my System Preferences>Display, and the system is still recognizing two monitors. So I am guessing my issue is related to the Display itself. What can be done at this point?

Dual monitor setup with seperate resolutions

hey guys!
i currentley run thye latest version of archlinux with the cinnamon desktop environment and an nvidia geforce 7300SE graphics card.
im running a dual monitor setup with one 27" 1920x1080 monitor and one 27" 1024X768 monitor
because they have the same physical size they line up perfectley but because the resolution is different programs/mouse cursor movement doesnt, is there any way (without changing the resolutions) to compensate this effect so that in the eyes of linux/cinnamon the monitors line up so that for example dragging a window goes seamlessley between the 2 monitors.
i HAVE found out the panning option in the nvidia x server settings, but that really isnt what i am looking for...
Last edited by RikSolo (2014-08-04 11:25:02)

A magnifier following the window down to the pixel, zooming to the exact size of 540 pixels the 384 pixels window could create an illusion of just that. It would be highly impractical however, not mention all the hacking time. Even if you would manage to get two screen with different sized icons, so that they match visually, the windows and fonts resizing on the fly, wmctrl might help with windows alone, no their themes (buttons, borders thickness etc.), you would still be left with a visually differently sized mouse cursor. Technically such a feat should be possible, but who is going to code it? Nvidia?
Last edited by emeres (2014-08-04 18:48:59)

Monitor Profile incorrect on Dual Monitor Setup

Hello,
I've searched the forums and I can't find an answer to my problem. I've read about dual monitor setups in Windows and how to set the defaults and whatnot, but it doesn't seem to fix my problem.
I am running on an nVidia GeForce 8600M GT, Windows 7 x64, Photoshop CS4 x64. I calibrated my main display (Dell Vostro 1700) as well as the attached monitor (ASUS VK246H) using Datacolor Spyder3Elite. Both monitor profiles seem to load just fine. I've also went into Windows' color manager and set the system defaults for each monitor respectively. The problem I'm having is that if I were to load Photoshop on the 2nd monitor, Photoshop only uses the main display's color profile (Vostro 1700) and not the ASUS VK246H profile. What could be going wrong?
Just to clarify, what I mean by "loading PS on the 2nd monitor" is that when I execute Photoshop.exe, the splash screen and main window shows up on the 2nd monitor, not the main monitor (which is what I want).

function(){return A.apply(null,[this].concat($A(arguments)))}
Chris Cox wrote:
What if the image is in between two monitors?
The piece on each display is corrected for the display it is on.
Is it supposed to work that way? Because it doesn't. Not with Photoshop CS5 x64 at least.
As a test I intentionally misconfigured the profile for my Monitor #1 (left) so that it's REALLY OBVIOUS which profile is being used. When set this way, on Monitor #1 red colors will appear pale orange.
An open document, floating in a window:
If COMPLETELY displayed on Monitor #1, Photoshop will use the Monitor #1 profile.
If even 1 pixel of the edge of the image is moved onto Monitor #2, it will use the Monitor #2 profile on the entire image.
See for yourself:
-Noel

Dual Monitors on Mac Mini Late 2014 not working on Dell S2340Lc

Hey guys,
Got a mac mini and using it mainly for work. Working for an ISP and no one has used macs and I've opted to be the poor sucker that gets to deal with old people that don't know how to mac very goodly.
I have two Dell S2340Lc monitors. I have one connected up via HDMI and that works perfectly fine. I turned off the mac, I plugged in Monitor 2 with a MiniDP/Thunderbolt to HDMI adapter, powered on the mac and whilst it was booting, it had the Apple logo and the loading bar on the Dell display plugged in to the thunderbolt to hdmi adapter and then once it loaded up the log in screen, it went to the HDMI display. I logged in and in the displays section, the monitor plugged in to the thunderbolt to hdmi adapter isn't being detected, however I can plug it in to a Samsung 55 Inch Smart TV and it works just fine. I can set up dual monitors between the TV and the monitor in HDMI, but the Dell S2340Lc will only work with a HDMI cable into the HDMI port on the mac mini and will not work through the thunderbolt to hdmi adapter. On the display it just says that there is no signal coming from the computer.
Just wondering if any of you apple gurus had any ideas as to why this isn't working?
Thanks!

What if you switch monitors?
What happens if yo only have the Thunderbolt>HDMI>Dell monitor connected?
Try resetting the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Call Apple. You get 90 days or free telephone support
Complimentary Support (USA)

Dual Monitors Windows 7 Problems

Ok, this problem is getting really annoying and I think its a problem with windows 7 itself and not my computer.
Basically I have a dual monitor setup with the left hand monitor as my secondary and right hand monitor as my primary. Whenever I have an application with any graphics on it at all such as a progress bar on my left hand monitor moving windows around becomes laggy and juddery, yet this doesn't happen when the graphical app is on my primary monitor!
My system Specs:
ASUS Striker Extreme MOBO
OCZ 850W gameXtreme
Core 2 Duo 2.4GHz CPU
4GB (4x1GB) OCZ DDR2 1066MHz RAM
Nvidia 8800GTX
Sound blaster x-fi Xtreme Gamer (older PCI version)
3 x 80GB HD for system drive in RAID 0
1 x 500GB and 1 x 250GB drives for storage
Monitors are 1680 x 1050 res
Windows 7 Exp Index:
CPU: 5.9
Memory: 5.9
Graphics: 6.8
Gaming Graphics: 6.8
Primary HD: 5.9
What iv tried:
Updating to latest drivers
Upgraded system memory from 2GB to 4GB
Installing 64-bit version
removing sound card and re-installing windows from scratch
upgraded my PSU
Thanks for your help!

(Latest update) This is the best I can do to alleviate the problem, and does reduce its severity immensely, but I found myself still noticing some slight playback glitches in videos on my second monitor which probably also translate to anything else with movement. I have tested with a panning scene in one of my videos and there is a subtle micro-stutter on my second monitor which I can find no way to fix. This doesn't occur if outputting to a single display, one or the other, nor does it occur when playing the video on my primary monitor in a dual-monitor configuration. Note that when I say "primary monitor", I am not referring to the monitor Windows has marked as primary, but my actual monitor rather than TV. In a dual-monitor configuration, this micro-stutter will only occur when playing video on my right monitor (TV), regardless of settings or which ports the monitors are connected to on the GPU. The micro-stutter occurs with no relation to the activity on the other screen, as it can be completely still. I can confirm the micro-stutter does not occur at all with Desktop Window Manager (Aero) disabled. In short, this is a nightmare.
(Note that this micro-stutter is equally replicable in the 182.50 (WDDM1.1-less) driver, meaning there is no way to solve it other than disabling Aero or outputting to a single monitor.)
I think I've solved the problem.. for me, anyway. I've divided this into short answer and "long answer", which is closer to a stream of consciousness in some ways, as I found out about Force10Level9 as I was writing.
The short version:
I've found some registry keys which seem to have fixed the problem for me. I haven't experienced any side effects, but use the tweaks at your own risk!
I don't know exactly what they do. This comes from a lot of.. experimentation. I believe FrameRateMin tells the Desktop Window Manager that it's crucial to try to keep the framerate at or above the value specified (more details below), and Force10Level9 sounds like it forces DWM to use DirectX 9. I'm fairly certain about the former, not as certain about the latter, but together they do wonders.
You can view the fix below. You can then save it as a .reg file and import it into your registry. Restart the Desktop Window Manager service or reboot to see the changes.
Fix: http://pastebin.com/FFDbubw9
Undo: http://pastebin.com/zA8CJY06
(P.S. Just ran a FurMark test between fix applied and no fix. No difference in performance, with an inactive secondary monitor. I also noticed no difference in Physical Memory usage as reported by Task Manager. YMMV, let me know if you have any side effects.)
(P.P.S. The screen fade that happens when you log in/out is just as choppy as before (or if it wasn't choppy for you, that shouldn't have changed). Oh well, how often do we see that thing, anyway? :))
By the way, it appears 10Level9 is Windows 7's emulation platform for running DX10 on DX9 hardware. It's reported to be at least a 0.5x performance hit, so it's surprising that it actually makes Aero run better. If this article is anything to go by, Force10Level9 makes Aero run exactly the same as it does with older WDDM 1.0-only drivers like 182.50: http://www.techarp.com/showarticle.aspx?artno=637&pgno=1
The long version:
Well... I was able to do one more thing.
There is an undocumented registry key which allows you to fine-tune the Desktop Window Manager's scheduling. Unfortunately, all of its values seem to be defunct in the final version of Windows 7 we all use today... except one: FrameRateMin.
From what I gather, the Desktop Window Manager (Aero) carefully monitors the framerate it is able to achieve, and when it can't measure up to its own expectations, it will perform a "step down", or framerate reduction, and maintain this lower framerate for a given period of time (at one time specifiable with a registry value) before trying again at maximum speed.
I presume it does all this to keep things looking "smooth".
The problem is, in most cases, it doesn't help, and actually prolongs the stuttering duration. By "in most cases", I mean in every case it's happened in my personal usage of my Windows 7 computers.
So what helped me was setting this FrameRateMin value to 60. That way, the Desktop Window Manager considers anything under 60fps to be unacceptable and will not remain at a lower framerate for purposes of perceived smoothness. Thus, the stuttering will take up as little time as possible, making it nearly unnoticeable most of the time.
Keep in mind DWM shouldn't be having performance problems to begin with, but apparently in some cases, like with my particular hardware (desktop and laptop) and the latest NVIDIA drivers, it does.
Down to brass tacks. The registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM\Schedule. The value is FrameRateMin, a DWORD representing the minimum framerate DWM will consider as acceptable. I set it to 60, but you can set it to whatever you want.
To repeat, this WILL NOT prevent Aero from ever getting below the framerate you specify; it simply prevents Aero from retaining a lower framerate after a stutter in order to give the illusion of smoothness (an illusion which fails).
I imagine the main reason it fails so spectacularly in my usage is because I watch a lot of videos which play back at 24fps. Such a framerate plays back terribly with a 30Hz refresh rate, which is what Aero would reduce itself to for extended lengths of time. Now, performance hiccups are minimal, but sadly still existent.
So this isn't a solution, but it does help. I am still uncertain of where the problem lies, considering GPU-Z shows graphics card loads to be as low as always when it's happening.
Oh, and I found one more registry value. This one is far more important. :) It solves the problem for me entirely, from what I can tell.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics
add the DWORD value Force10Level9 with a value of 1.
I haven't noticed any side effects, just smooth performance.
Apply these tweaks at your own risk!

Dual Monitors with GPU and Motherboard not working

Hey guys, just wondering if anyone else could help me out.
So, I decided to hook up an old monitor of mine to my rig today and, lo and behold, the monitor isn't being detected by my computer.
I've already got a monitor running through my GPU (NVidia GTX 960) via DVI.
Currently tried connecting my second (old) monitor to my motherboard with DVI as well, but it isn't being detected.
I went into my bios and forced my integrated graphics on, but when I checked in the device manager, it said my VGA graphics adapter "Cannot start (Error Code 10)"
Also tried updating VGA graphics adapter drivers, but I had the latest drivers already.
I'm not sure if that's related to the issue, but I thought it'd be worth mentioning.
(What's also worth mentioning is that I'm a complete casual when it comes to computer building and such, lol)
Motherboard is a Gigabyte F2A88XM-HD3, supports VGA, DVI and HDMI.
Monitor that I'm trying to connect supports both DVI and VGA.

A lot of the 960's don't have 2 DVI's. However most have an additional HDMI and DisplayPort. I recommend you get an adapter from amazon or something. Just make sure that it will convert HDMI or DP to DVI. Usually amazon products have a good amount
of questions already answered by buyers.
Interesting that they'd go that route, I guess I just assumed since my 760 has two.
I've set up dual monitors using one DVI and one HDMI before, but I ran into issues with screen sizing. Despite having two identical monitors set at the same resolution the mouse would not transmit over to the second monitor at the same height as it was on
the first, so I had to buy an adapter like Joshua suggested.

I have a dual monitor setup. When I paste develop settings from one image to another, Lightroom switches the active window.

Strange problem. Lightroom 5.5. Windows 8.1. Dual monitor setup.
I'm processing a large batch of photos. I have Monitor #1 set as my main develop window, with Monitor #2 set only to display a larger version of the image I'm working with. If I copy the develop settings off of one image and try to paste them onto another image, Lightroom will switch from Monitor #1 to Monitor #2 as the main develop window, and will not display anything on Monitor #1.
If I then try to paste develop settings onto another image on Monitor #2, LR will then display a larger version of the image I'm working with on Monitor #1.
To work the way I want to, I have to continually drag my develop window back to Monitor #1 every time I try to paste develop settings onto a new image. How can I make this stop?

I just tried what I think you’re saying you’re doing and I don’t have the problem with LR 5.5 on Windows 7 SP 2.
Does the same thing happen whether you use the key shortcuts vs the Settings / Copy/Paste options on the menu?
I ask this because if you’re using the keyboard shortcuts, maybe you have some display-manager program that has bound itself to the Ctrl-Shift-V (paste settings) to the function of move-to-other-monitor which would do at least part of what you describe.
You can also test this theory by doing a Ctrl-Shift-V with an application other than LR as the active window and see if it moves. I suppose Ctrl-Shift-C might also play into it so try both of these hot-key combinations with a program that isn’t LR.
If none of this sheds any light on the situation, then give a more detailed description of the low-level functions you’re doing to accomplish the copy-paste of settings, so someone else could replicate the steps exactly.
Specific detailed steps, like:
left-click on source photo’s thumbnail in the filmstrip
press Ctrl-Shift-C to copy the settings
click Check-None
enable the white-balance and calibration checkboxes
click Ok
left-click on destination photo's thumbnail in the filmstrip
click on Settings / Paste Settings in LR’s menus to paste the settings to the selected photo

MythTV Program Guide Slow/No Composite Effects On Dual Monitor

Hello all,
I am not entirely sure where this would belong, so I put it here.
I am running Arch64 with an NVidia 8600GTS and dual monitors as seperate X screens. The second monitor is actually a TV not a monitor, and is using the S-Video output on the video card, but I'm not sure that that's relevant at all.
On my primary monitor the program guide in MythTV runs fairly decent, however on the TV it runs unbearably slow. Pushing up on the remote a time or two will take a minute or so to happen. I have it set to the least demanding level possible.
I originally thought that this was just a MythTV issue but I noticed that XCompmgr and Compiz-Fusion effects do not work at all on the TV either, so I think these issues are related.
Also, I do not currently have a composite window manager installed, I am using Gnome with Metacity.
Here is a copy of my xorg.conf:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder62) Tue Jan 6 09:44:34 PST 2009
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder62) Tue Jan 6 09:43:54 PST 2009
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "ServerLayout"
# Serial Mouse not detected
# USB Mouse not detected
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
# Load "synaptics"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AutoAddDevices" "False"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -hsync +vsync
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -hsync +vsync
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -hsync +vsync
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -hsync +vsync
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -hsync +vsync
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -hsync +vsync
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -hsync +vsync
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 55.0
VertRefresh 43.0 - 72.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "All"
BoardName "All"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 16
Option "TwinView" "0"
Option "metamodes" "DFP: 1680x1050 +0+0; DFP: 800x600 +0+0; DFP: 640x480 +0+0"
SubSection "Display"
Depth 16
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 16
Option "TVStandard" "NTSC-M"
Option "TVOutFormat" "SVIDEO"
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 16
EndSubSection
EndSection
It's a bit of a mess at the moment. Last time I reinstalled I was having trouble with the keyboard and mouse not working in Gnome, so I've been hesitant to mess with it too much.
On my previous install my xorg.conf looked like this:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder58) Wed Oct 1 15:13:37 PDT 2008
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jul 17 18:39:00 PDT 2008
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
# RgbPath "/usr/lib/X11/rgb"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
# Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GTS"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
# Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "RenderAccel" "True"
Option "NoRenderExtension" "False"
Option "AllowGLXWithComposite" "True"
Option "XvmcUsesTextures" "True"
Option "LoadKernelModule" "True"
Option "DamageEvents" "True"
# Option "LogoPath" "/home/theavataroftime/Pictures"
Option "NoLogo" "True"
Option "TwinView" "0"
Option "metamodes" "DFP: 1680x1050 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "RenderAccel" "True"
Option "NoRenderExtension" "False"
Option "AllowGLXWithComposite" "True"
Option "XvmcUsesTextures" "True"
Option "LoadKernelModule" "True"
Option "DamageEvents" "True"
Option "LogoPath" "/home/theavataroftime/Pictures"
Option "NoLogo" "True"
Option "TVStandard" "NTSC-M"
Option "TVOutFormat" "SVIDEO"
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection
I had the same issues with composite managers and that MythTV guide using this xorg.conf too.
Has anyone had any similar issues? I am at a total loss here, so any help is greatly appreciated. Thank you.

No one else has had troubles with the program guide or composite effects on dual monitors?

Dual Monitor/View problem......

I am having a problem running my dual monitors with my MSI gf4 ti 4200 128mb card...... i re-installed my drivers (i tried 30.00's and 30.82's) and they work fine, but once i reboot or change the resolution it'll show 4 monitors in my device manager instead of 2, and my resolution cannot change from 840x480x32 (used to be only 840x480x8 )....atleast i have 32 bit now.... but i think its cause the other 2 useless monitors are using up the resources for this settings, because when they arent installed it will let me go higher in resolution...... any experts here know anything about a fix or solution for all those monitors using "EXTEND MONITOR ONTO DESKTOP" without having 4 monitors showing? thx in advance,
RaZoR
ps.... i tried uninstalling the monitors but they just keep reappearing.....any MSI tech's know what i should do??

set "first display" - monitor. !

Dual monitor management

Similar Messages

Maybe you are looking for