{"id":475,"date":"2006-08-04T15:06:03","date_gmt":"2006-08-04T07:06:03","guid":{"rendered":"http:\/\/www.nargalzius.com\/blog2\/http:\/www.nargalzius.com\/blog2\/archives\/2006\/08\/2006_08_04_1506.php"},"modified":"2006-08-04T15:06:03","modified_gmt":"2006-08-04T07:06:03","slug":"dual-monitor-advice-tips-and-tricks","status":"publish","type":"post","link":"http:\/\/nargalzius.com\/blog\/archives\/2006\/08\/04\/dual-monitor-advice-tips-and-tricks","title":{"rendered":"Dual monitor advice, tips, and tricks"},"content":{"rendered":"<div align=\"center\">\n<a href=\"http:\/\/static.flickr.com\/63\/206379351_66f97ffa7f_o.jpg\" rel=\"lightbox\" title=\"click on image for more details\"><img decoding=\"async\" src=\"http:\/\/static.flickr.com\/63\/206379351_66f97ffa7f_m.jpg\"><\/a>\n<\/div>\n<p>During my quest to have a color calibrated setup of dual displays, I&#8217;ve come across a bunch of information that will definitely be useful to any newbie plannning to do the same. Most information could be found in different forums if you search hard enough. But it would be useful to just have everything I&#8217;ve discovered written here.<\/p>\n<!--more-->\n<h2>Viewing angles (LCD)<\/h2>\n<p>Mostly (if not entirely) applicable to LCDs, once you go dual, viewing angles will be <em>very important.<\/em> You&#8217;ll be making one of two choices: would you like the monitors side-by side aligned on the same axis, or a bit bent (like a V) with each facing you. The latter is very common, but there&#8217;s a legitimate reason to want to try the first: graphics alignment. Unless your monitors are perfectly perpendicular to the surface, <span class=\"footnote_referrer\"><a role=\"button\" tabindex=\"0\" onclick=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_1');\" onkeypress=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_1');\" ><sup id=\"footnote_plugin_tooltip_475_1_1\" class=\"footnote_plugin_tooltip_text\">1 <\/sup><\/a><span id=\"footnote_plugin_tooltip_text_475_1_1\" class=\"footnote_tooltip\">Normally, your monitor is tilted up a little if you&#8217;re seated higher, or down a little if you&#8217;re seated lower.<\/span><\/span><script type=\"text\/javascript\"> jQuery('#footnote_plugin_tooltip_475_1_1').tooltip({ tip: '#footnote_plugin_tooltip_text_475_1_1', tipClass: 'footnote_tooltip', effect: 'fade', predelay: 0, fadeInSpeed: 200, delay: 400, fadeOutSpeed: 200, position: 'top right', relative: true, offset: [10, 10], });<\/script> doing the latter formation will result in a gap either at the top or bottom of the joint where the two monitors meet. Of course this is a very trivial subject, but this &#8220;misalignment <em>could<\/em> get quite irritating for the more anal people (myself included), which is why I mention it.<\/p>\n<p>This also brings us to another thing you should be wary of: available tilt adjustments of the monitors. If you have full freedom of tiliting up down, sideways then you can always go the second way without compromising your viewing angles. Unfortunately my <a href=\"http:\/\/www.viewsonic.com\/products\/desktopdisplays\/lcddisplays\/xseries\/vx922\/\" title=\"View product info\">VX922<\/a>s, as premium quality as they may be, can only tilt up and down &#8211; hence I am constantly battling with the issue of having these gaps at the joint.<\/p>\n<p>A good solution, if you like to try some carpentry, is to make simple shims to put on the bases to adjust whatever tilt direction is lacking in your monitors. Or of course spend more bucks on <a href=\"http:\/\/www.ergoindemand.com\/about_VESA_standard.htm\" title=\"What is VESA?\">VESA<\/a> compliant panel mounts if you could. <span class=\"footnote_referrer\"><a role=\"button\" tabindex=\"0\" onclick=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_2');\" onkeypress=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_2');\" ><sup id=\"footnote_plugin_tooltip_475_1_2\" class=\"footnote_plugin_tooltip_text\">2 <\/sup><\/a><span id=\"footnote_plugin_tooltip_text_475_1_2\" class=\"footnote_tooltip\">Of course your monitors have to be VESA compliant to begin with.<\/span><\/span><script type=\"text\/javascript\"> jQuery('#footnote_plugin_tooltip_475_1_2').tooltip({ tip: '#footnote_plugin_tooltip_text_475_1_2', tipClass: 'footnote_tooltip', effect: 'fade', predelay: 0, fadeInSpeed: 200, delay: 400, fadeOutSpeed: 200, position: 'top right', relative: true, offset: [10, 10], });<\/script><\/p>\n<h2>Video cards<\/h2>\n<p>This can be an issue depending on how you use your computer. If you&#8217;re into color, then I guess for color accuracy, you&#8217;re better off with two simple video cards with <code>DVI<\/code> outputs. A dual head <code>DVI<\/code> video card is preferable if you&#8217;re sure you can set different color profiles for each &#8220;head\/monitor&#8221; &#8211; I learned the hard way that this isn&#8217;t a generalization one can make with dual-headed cards. More on this later<\/p>\n<p>If you&#8217;re a gamer, and are on a tight budget, then a single card with dual (but different) outputs would be advisable. A lot of the cards nowadays come with dual-heads, one being a <code>DVI<\/code> jack, the other is a <code>D-SUB<\/code> (standard VGA) jack.<\/p>\n<h2>Inputs<\/h2>\n<p>Based on what was mentioned above, your monitors&#8217; supported <em>inputs<\/em> will now matter, whatever interface you have for your monitor, make sure you can connect it somewhere in your card(s) and vice-versa. <code>DVI<\/code> is digital so for color accuracy, it&#8217;s always the better choice. Another plus of digital input is that you don&#8217;t use refresh rates &#8211; ergo staring into an LCD via <code>DVI<\/code> is less likely to strain you in any way.<\/p>\n<p>The only reason I can think of to use a VGA input (<code>D-SUB<\/code>) is simply because you don&#8217;t have <code>DVI<\/code> (in your card or monitor) &#8211; otherwise it&#8217;s better than analog in every concievable way.<\/p>\n<h2>Primary Display<\/h2>\n<p>Most people (myself included) have the (<code>DVI<\/code>\/<code>D-SUB<\/code>) combination, and most of the time, the <code>D-SUB<\/code> is considered as monitor one on first install. Don&#8217;t let this mislead you, <code>D-SUB<\/code> being first listed has nothing to do with it being better than <code>DVI<\/code> in any way &#8211; so find a way to switch that immediately. If you have dual <code>DVI<\/code> inputs, then any would be fine. But for the rest of us, set the monitor hooked to your <code>DVI<\/code> as your primary monitor.<\/p>\n<h2>Calibration<\/h2>\n<p>Here&#8217;s an important bit of information I&#8217;ve found out after calibrating my monitor: Most dual head cards cannot set separate ICC profiles on individual monitors. There are applications that allow you to set them manually, but as far as I know, there isn&#8217;t anything yet that can set them automatically and remember it after a reboot.<\/p>\n<p>With the regular color management utility of windows, sure you can select and individual monitor, you can even select individual refresh rates. Each monitor&#8217;s color profile settings show available profiles for use, but try this: select one for one monitor and set that as the default. Go to the second and select <em>another<\/em> and set as default. Go back to the first&#8230; you&#8217;ll now see that it only remember the <strong>last<\/strong> profile you set as default (which in our case is now the second).<\/p>\n<p>Running the calibration software sets each individual monitor properly (as you have to run it twice with each), but after reboot, they use and load whatever is the default &#8211; meaning only ONE profile. Now you see why I stressed the need to have 2 <em>separate<\/em> video cards &#8211; as you have the option to indeed select individual profiles for each.<\/p>\n<p>Another peeve of mine is the requirement to even <em>use<\/em> these profile loaders&#8230; even if you set a generated calibrated profile in windows, when you reboot, for some reason it doesn&#8217;t apply it. Maybe it&#8217;s just me, but whenever I disable the profile loader in the <code>startup<\/code> folder, the profiles don&#8217;t stick after reboots. This is also applicable for single monitor setups. Unless you have some kind of profile loader there, for some reason it won&#8217;t apply profiles properly.<\/p>\n<p>If someone found a way to solve this problem, please feel free to share your solution.<\/p>\n<h2>Good LCD Settings to use<\/h2>\n<p>Given the problem above, I could now assume that <em>despite<\/em> having separate ICC profiles for each monitor. Reboots will probably end up loading only one of them. So I obviously chose the monitor connected digitally as the &#8220;basis&#8221;<\/p>\n<p>A nifty trick I thought of was this: Since the software that profiles and calibrates your monitors ultimately drastically changes the visual settings based on a hardware <em>colorimeter,<\/em> it means it does all the compensation via software. This means you can set your hardware settings to any [reasonable] value and it will still adjust them properly.<\/p>\n<p>So say you set your monitor totally out of whack color setting (via your LCD&#8217;s hardware settings); in theory, the software can <em>still<\/em> correct your colors while retaining your LCD hardware settings (because it does all the compensation via software).<\/p>\n<p>Therefore, my first valid tip is to ALWAYS set the <em>color preferences<\/em> hardware setting on the LCD to <em>user mode<\/em> the names may vary, but look for the part where you can change the color temperature &#8211; the goal is to <strong>not<\/strong> use the presets. Set your RGB values to have some slack on both sides so you can do + or &#8211; adjustments at the end of it all.<\/p>\n<p>Next is to try to match the two monitors with your eyes for now by just using these RGB values. You don&#8217;t have to get them exactly, but if you could then why not? When you&#8217;re done with that, and assuming you still have enough slack on the <em>secondary<\/em> monitor, calibrate your <strong>primary.<\/strong> <span class=\"footnote_referrer\"><a role=\"button\" tabindex=\"0\" onclick=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_3');\" onkeypress=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_3');\" ><sup id=\"footnote_plugin_tooltip_475_1_3\" class=\"footnote_plugin_tooltip_text\">3 <\/sup><\/a><span id=\"footnote_plugin_tooltip_text_475_1_3\" class=\"footnote_tooltip\">In the case of a single video card with dual heads, you can also calibrate the second monitor, but because of the &#8220;bug&#8221; I mentioned above, it might just be a waste of time.<\/span><\/span><script type=\"text\/javascript\"> jQuery('#footnote_plugin_tooltip_475_1_3').tooltip({ tip: '#footnote_plugin_tooltip_text_475_1_3', tipClass: 'footnote_tooltip', effect: 'fade', predelay: 0, fadeInSpeed: 200, delay: 400, fadeOutSpeed: 200, position: 'top right', relative: true, offset: [10, 10], });<\/script><\/p>\n<p>Now use the newly generated profile as your default profile (I don&#8217;t care how you apply it, just make sure it applies to <strong>both<\/strong> monitors). Now since you did a best-guess matching to begin with, you should now see the second monitor looking <em>close<\/em> to the first. Of course theres an almost sure chance that it will still be off a little bit &#8211; after all, you are useing a <em>different<\/em> monitor&#8217;s profile for your secondary display), so what you do now is go back to your RGB values (which should have slack for more adjustments) and adjust to taste. <span class=\"footnote_referrer\"><a role=\"button\" tabindex=\"0\" onclick=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_4');\" onkeypress=\"footnote_moveToReference_475_1('footnote_plugin_reference_475_1_4');\" ><sup id=\"footnote_plugin_tooltip_475_1_4\" class=\"footnote_plugin_tooltip_text\">4 <\/sup><\/a><span id=\"footnote_plugin_tooltip_text_475_1_4\" class=\"footnote_tooltip\">And now you know why you HAD to use the custom\/user settings and not the presets.<\/span><\/span><script type=\"text\/javascript\"> jQuery('#footnote_plugin_tooltip_475_1_4').tooltip({ tip: '#footnote_plugin_tooltip_text_475_1_4', tipClass: 'footnote_tooltip', effect: 'fade', predelay: 0, fadeInSpeed: 200, delay: 400, fadeOutSpeed: 200, position: 'top right', relative: true, offset: [10, 10], });<\/script><\/p>\n<p>Unfortunately, for the second monitor, we&#8217;ll be relying on our eyes now &#8211; so you just have to trust your judgement and try matching it with your <em>properly calibrated<\/em> <strong>primary<\/strong> screen.<\/p>\n<p>If all goes well, you should end up with a <em>satisfactorily<\/em> (is there such a word?) matched set of dual displays \ud83d\ude42<\/p><div class=\"speaker-mute footnotes_reference_container\"> <div class=\"footnote_container_prepare\"><p><span role=\"button\" tabindex=\"0\" class=\"footnote_reference_container_label pointer\" onclick=\"footnote_expand_collapse_reference_container_475_1();\">Notes<\/span><span role=\"button\" tabindex=\"0\" class=\"footnote_reference_container_collapse_button\" style=\"display: none;\" onclick=\"footnote_expand_collapse_reference_container_475_1();\">[<a id=\"footnote_reference_container_collapse_button_475_1\">+<\/a>]<\/span><\/p><\/div> <div id=\"footnote_references_container_475_1\" style=\"\"><table class=\"footnotes_table footnote-reference-container\"><caption class=\"accessibility\">Notes<\/caption> <tbody> \r\n\r\n<tr class=\"footnotes_plugin_reference_row\"> <th scope=\"row\" class=\"footnote_plugin_index_combi pointer\"  onclick=\"footnote_moveToAnchor_475_1('footnote_plugin_tooltip_475_1_1');\"><a id=\"footnote_plugin_reference_475_1_1\" class=\"footnote_backlink\"><span class=\"footnote_index_arrow\">&#8673;<\/span>1<\/a><\/th> <td class=\"footnote_plugin_text\">Normally, your monitor is tilted up a little if you&#8217;re seated higher, or down a little if you&#8217;re seated lower.<\/td><\/tr>\r\n\r\n<tr class=\"footnotes_plugin_reference_row\"> <th scope=\"row\" class=\"footnote_plugin_index_combi pointer\"  onclick=\"footnote_moveToAnchor_475_1('footnote_plugin_tooltip_475_1_2');\"><a id=\"footnote_plugin_reference_475_1_2\" class=\"footnote_backlink\"><span class=\"footnote_index_arrow\">&#8673;<\/span>2<\/a><\/th> <td class=\"footnote_plugin_text\">Of course your monitors have to be VESA compliant to begin with.<\/td><\/tr>\r\n\r\n<tr class=\"footnotes_plugin_reference_row\"> <th scope=\"row\" class=\"footnote_plugin_index_combi pointer\"  onclick=\"footnote_moveToAnchor_475_1('footnote_plugin_tooltip_475_1_3');\"><a id=\"footnote_plugin_reference_475_1_3\" class=\"footnote_backlink\"><span class=\"footnote_index_arrow\">&#8673;<\/span>3<\/a><\/th> <td class=\"footnote_plugin_text\">In the case of a single video card with dual heads, you can also calibrate the second monitor, but because of the &#8220;bug&#8221; I mentioned above, it might just be a waste of time.<\/td><\/tr>\r\n\r\n<tr class=\"footnotes_plugin_reference_row\"> <th scope=\"row\" class=\"footnote_plugin_index_combi pointer\"  onclick=\"footnote_moveToAnchor_475_1('footnote_plugin_tooltip_475_1_4');\"><a id=\"footnote_plugin_reference_475_1_4\" class=\"footnote_backlink\"><span class=\"footnote_index_arrow\">&#8673;<\/span>4<\/a><\/th> <td class=\"footnote_plugin_text\">And now you know why you HAD to use the custom\/user settings and not the presets.<\/td><\/tr>\r\n\r\n <\/tbody> <\/table> <\/div><\/div><script type=\"text\/javascript\"> function footnote_expand_reference_container_475_1() { jQuery('#footnote_references_container_475_1').show(); jQuery('#footnote_reference_container_collapse_button_475_1').text('\u2212'); } function footnote_collapse_reference_container_475_1() { jQuery('#footnote_references_container_475_1').hide(); jQuery('#footnote_reference_container_collapse_button_475_1').text('+'); } function footnote_expand_collapse_reference_container_475_1() { if (jQuery('#footnote_references_container_475_1').is(':hidden')) { footnote_expand_reference_container_475_1(); } else { footnote_collapse_reference_container_475_1(); } } function footnote_moveToReference_475_1(p_str_TargetID) { footnote_expand_reference_container_475_1(); var l_obj_Target = jQuery('#' + p_str_TargetID); if (l_obj_Target.length) { jQuery( 'html, body' ).delay( 0 ); jQuery('html, body').animate({ scrollTop: l_obj_Target.offset().top - window.innerHeight * 0.2 }, 380); } } function footnote_moveToAnchor_475_1(p_str_TargetID) { footnote_expand_reference_container_475_1(); var l_obj_Target = jQuery('#' + p_str_TargetID); if (l_obj_Target.length) { jQuery( 'html, body' ).delay( 0 ); jQuery('html, body').animate({ scrollTop: l_obj_Target.offset().top - window.innerHeight * 0.2 }, 380); } }<\/script>","protected":false},"excerpt":{"rendered":"<p>During my quest to have a color calibrated setup of dual displays, I&#8217;ve come across a bunch of information that will definitely be useful to any newbie plannning to do the same. Most information could be found in different forums if you search hard enough. But it would be useful to just have everything I&#8217;ve &hellip; <p class=\"link-more\"><a href=\"http:\/\/nargalzius.com\/blog\/archives\/2006\/08\/04\/dual-monitor-advice-tips-and-tricks\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Dual monitor advice, tips, and tricks&#8221;<\/span><\/a><\/p><\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[4,13],"tags":[261,364,782,1255],"class_list":["post-475","post","type-post","status-publish","format-standard","hentry","category-general","category-technology","tag-color-profile","tag-dual-display","tag-monitor","tag-viewsonic"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts\/475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/comments?post=475"}],"version-history":[{"count":0,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/posts\/475\/revisions"}],"wp:attachment":[{"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/media?parent=475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/categories?post=475"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nargalzius.com\/blog\/wp-json\/wp\/v2\/tags?post=475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}