Home  |  About  | Last |  Submit  |  Contact
AllQuests.com



Previous Question:  
**A Funny Plasma Owner Story**
 Plasma Flat Panel DisplaysNext Question:  Sprich mit dem Communityteam - 4a :)  Das Spiel
Question Custom Resolution Tool for Intel Graphics Easier Overscan Correction ( AVS Forum Home Theater Computers )
Updated: 2008-05-18 12:29:17 (1319)
Custom Resolution Tool for Intel Graphics Easier Overscan Correction

DTD Calculator:
Clever Technology Making Custom Resolutions for Intel Graphics Easier

For those of you who have or are considering Intel integrated graphics solutions, you may or may not have observed that the standard tool for coping with custom resolutions-- EnTech's Powerstrip-- doesn't work properly with Intel graphics. Why that is is somewhat irrelevant to the discussion here. The important thing is that the Powerstrip situation doesn't appear to be changing anytime soon, and Intel hasn't published any information which implies there is something in the works at their end.

This situation comes at a very annoying time, since the Intel Graphics are becoming a better and better solution for a home theater PC with new DVI and HDMI solutions and better video processing capabilities.

Intel graphics have the capability of specifying custom timings using the VESA standard Detailed Timing Descriptor (DTD), but it's a register hack and the method is cryptic (see http://softwarecommunity.intel.com/W...aphics/239.htm for more than you've ever wanted to know on the matter). A better method is desirable: something graphical as Powerstrip provides, and as Nvidia and ATI provide as well. Not sure it will ever be easy to understand, but it should at least be easier to get the work done. That's where a freeware program called DTDCalculator (developed out of the kindness of their heart by the nice guys at Clever Technologies in the UK) comes in.

DTDCalculator's primary goal is to take a very manual, math-intensive process and make it human. And I think it succeeds.

1) You can download the software installer from my personal site at
http://members.cox.net/archibael/setupdtd100.exe
Clever Technologies is also hosting:
http://www.clevertec.co.uk/productsfree.htm#dtdcalc

2) Install the SW and start it up. Note that you need to be running the application with Administrative privileges in order to write to the registry under Vista with UAC enabled.

3) Get one or more DTDs from some source and write them to the registry

There are several starting places:

a) One of the most accurate (for your particular monitor) would be by grabbing the EDID data from the Intel Graphics Tray Information button (choose "Save to File" and the raw EDID will pop up). Use the instructions from the DTD Wiki I referenced above to find the proper DTDs, paste one into the DTD field of the Reverse Calculation screen and hit the button there.

b) Another option is to find a Linux Modeline out there which someone has used for your monitor, and to input the parameters into the left panel, thus autogenerating the proper DTD for use with Intel graphics.

c) Another is to use a standard (provided), Consumer Electronics Association resolution by selecting one of the choices under "Standard Timings" in the Calculations tab.

In each case, the DTD Calculator tool will show the DTD across the bottom of the window, and will show the exact timing parameters in the left panel. Once you've inserted or selected a basic DTD, proceed to the Registry Hack section. You may or may not have DTDs on this screen (depending on if you've hacked them before or not), but if you want more resolutions than are listed shown there, click the More button. A blank DTD will be generated, ready to be stuffed into the registry. Since we've already got one selected, click "Get Calculated". This will take the current DTD and put it in memory as something you want to send to the registry as a selectable resolution. Repeat for as many as you'd like (up to five). When done, click "Write DTDs to Registry". Reboot, and the new resolutions you inserted should be selectable using the normal methods (Intel Graphics Tray or Windows Display Properties Settings).

Just as a note: if you write to the registry a resolution which matches, in description, one which the Intel graphics drivers are already providing ("1920x1080 interlaced @ 60Hz"), when the reboot occurs only one of the two will be selectable. Which is it? Is it the one you're using to do your overscan correction, or is the driver default one? There's no way to tell! So before putting your DTD in the Registry Hack screen, "tag" it by giving it a very obviously non-standard resolution. Changing the Horizontal Active pixels by 1 or 2 in the left panel is probably your best bet. That way you'll be able to distinguish between "1920x1080i @ 60Hz" and your custom "1922x1080i @ 60Hz". Don't be too worried about the exact resolution you select being "right"; this is just temporary, anyway. Your final overscan-free DTD will be something drastically different from the original and it's unlikely you will ever confuse 1920x1080 with 1898x1070. This method has the added bonus of fooling the drivers into being able to display resolutions your vendor (typically laptop) has (for whatever reason) specifically disabled in their BIOS.

4) Overscan Correction

At this point, especially if you've chosen 1080i or 720p, your TV probably has some level of overscan, meaning that the edges of your desktop or other content is beyond the edges of your screen, and you can't access taskbars or the minimize or close buttons. Highly annoying! Fortunately, that's the primary function of DTD Calculator: eliminating this pesky overscan. Open DTD Calculator, go to Registry Hack again, find the DTD which matches the resolution you are currently in and click Create Modeline to load the current DTD into memory.

Proceed to the Tuning tab, and click Ruler. Superimposed translucently on your desktop is a window you can use to find the right dimensions for your screen. Stretch it to fit to the edges of your screen (use the up/down left/right buttons to do fine tuning if your mouse hand is as jittery as mine) and when you're done click the Apply button. The new, non-overscanned screen size will be computed as a new DTD (you may notice the parameters have now changed.... or you may not, if you don't ordinarily memorize resolution timing parameters).

5) Fine tuning

You've sized the desktop appropriately, now, to fit your screen, but is the image where you'd expect it to be? Or is it shifted left, right... in some way askew? You can use the buttons on the tuning screen to ensure the image moves to the right spot on screen, and you can watch the little image move around the big black box.

6) Finalize
When you're done, and the resolution is as you like it, go back to the Registry Hack tab, choose one of the five available DTD "slots" in the registry, and click "Get Calculated" to change it to what you currently have developed. Click "Write DTDs to Registry" again to rewrite the new resolution to the registry, and then reboot. The new DTD will show up now under the regular resolutions. It's likely something really weird like 1820x996 or 1198x712, but it will be there and it should provide you with an overscanless screen to the limits that your monitor can provide. Voila!

7) There are other ways you can use the DTD Calculator-- a pure way of calculating a Modeline from the EDID (or vice versa). It's an excellent tool and I urge anyone who comes up with a useful application for it aside from what I've outlined here to post your experiences.

Afterword

Again, I ask you to be fairly kind in any suggestions or requests for new features. It's not my software (though it makes my life easier) and it is in fact provided by some folks who just thought it would be a nice favor to do for the community. They didn't write the Intel drivers, and while I and they will probably try to help with any weirdnesses as much as can be done, the bottom line is: if there is a driver problem, go to Intel.

This software is provided with no guarantees, express or otherwise. (At least, I think I saw lawyerspeak like that on some software once. Maybe it will do the trick.)

I reiterate my special thanks to AVS's very own Wo0zy and to his cadre of folks. Without them this software would have been solely in my head, and my Brain-to-IA32 compiler SUCKS. They went above and beyond on this, adding functionalities I hadn't thought of. I cannot say enough good things about them.

Answers: Custom Resolution Tool for Intel Graphics Easier Overscan Correction ( AVS Forum Home Theater Computers )
Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi w00tw00t111,

Not sure what's happened.

Can you post the new DTD so we can have a look at it?

Also, post a screenshot of the "Registry Hack" tab and the "Calculation" tab (with the new resolution loaded). It'll save me asking lots of questions.

Once you had set the 1278x720 resolution did you "load DTD's from Registry" before using the "Ruler" tuning tool?

Cheers,

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Wo0zy
Hi w00tw00t111,

Not sure what's happened.

Can you post the new DTD so we can have a look at it?

Also, post a screenshot of the "Registry Hack" tab and the "Calculation" tab (with the new resolution loaded). It'll save me asking lots of questions.

Once you had set the 1278x720 resolution did you "load DTD's from Registry" before using the "Ruler" tuning tool?

Cheers,

Wo0zy
Hey Wo0zy

The DTD for the 1182x658 is:
01 1D 9E D4 41 92 5C 20 A0 28 45 08 D9 29 11 00 00 1A

The Reg Hack image before manipulating with the ruler:
[img=http://img244.imageshack.us/img244/2402/reghackua7.jpg]

The Reg Hack image after manipulating with the ruler:


The Calculation image after manipulating with the ruler:



What I did after first saving the DTD you provided and rebooting was as follows:
1. Set my monitors resolution to the 1278x720 resolution
2. Opened DTD calculator
3. Went to Registry Hack, which at the time didn't have anything on the left hand side.
4. Clicked "Create Modeline"
5. The fields on the left were populated with the correct data (for the 1278x720 res)
6. Clicked "Tuning"
7. Clicked "Ruler"
8. Dragged each side to where the Outer Diameter of the Red was butting up against the edges of my monitors screen.
9. Clicked "Apply"
10. Clicked "Registry Hack"
11. Clicked "Get Calculated" (Made sure the original DTD and the 'edited' DTD were different; they were)
12. Clicked "Write DTD's To Registry" and Rebooted
13. Upon rebooting I'm presented with the 1182x658 resolution, the overscan is better, but still not nearly correct. If I go back into DTD calculator and perform the exact same steps described above and write/reboot; all of my custom resolutions are erased and upon logging into windows my resoluiton is set to 800x600.

Hopefully this helps

Thanks again for your continued help! I really appreciate it!!

w00tw00t111

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

This tool seems to be exactly what i need, except...

When I run it and go to the "Registry Hack" tab, the bottom of the screen says in red text "Intel Graphics Registry Key Not Found" and the "Write DTDs to Registry" button is always disabled. Seems pretty obvious (after reading all about how this tool works) that the required registry entries inserted by the Intel driver are not present. I've tried numerous things over the last few days to overcome this, but, am worried I'm just missing something silly. I can provide full details of system if required, but, for now, I'll just list the ones that seem most prevalent, and hope some one can point out some boneheaded thing I've done (or not done). Thanks in advance for all the work and help.

OS: Vista Home (same results when 'Run as Administrator')
Chipset: Intel 915GM
Driver: Mobile Intel(R) 915GM/GMS/910GML Express Chipset Family (Microsoft Corporation - XDDM)
Driver Provider: Intel Corporation
Driver Version: 6.14.10.4656

plac3bo

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by w00tw00t111
Hey Wo0zy

The DTD for the 1182x658 is:
01 1D 9E D4 41 92 5C 20 A0 28 45 08 D9 29 11 00 00 1A

The Reg Hack image before manipulating with the ruler:
[img=http://img244.imageshack.us/img244/2402/reghackua7.jpg]

The Reg Hack image after manipulating with the ruler:


The Calculation image after manipulating with the ruler:



What I did after first saving the DTD you provided and rebooting was as follows:
1. Set my monitors resolution to the 1278x720 resolution
2. Opened DTD calculator
3. Went to Registry Hack, which at the time didn't have anything on the left hand side.
4. Clicked "Create Modeline"
5. The fields on the left were populated with the correct data (for the 1278x720 res)
6. Clicked "Tuning"
7. Clicked "Ruler"
8. Dragged each side to where the Outer Diameter of the Red was butting up against the edges of my monitors screen.
9. Clicked "Apply"
10. Clicked "Registry Hack"
11. Clicked "Get Calculated" (Made sure the original DTD and the 'edited' DTD were different; they were)
12. Clicked "Write DTD's To Registry" and Rebooted
13. Upon rebooting I'm presented with the 1182x658 resolution, the overscan is better, but still not nearly correct. If I go back into DTD calculator and perform the exact same steps described above and write/reboot; all of my custom resolutions are erased and upon logging into windows my resoluiton is set to 800x600.

Hopefully this helps

Thanks again for your continued help! I really appreciate it!!
Hi w00tw00t111,

Thanks for the info. It sounds like you did everything you should mate.

When you say erased do you mean that you still have 1 enabled DTD but it is all zeros are that the "No of DTD's"=0? (if you see what I mean).

If the number of DTD's is set to zero try clicking the "more" button again to enable one then go to the "Calculation" tab and in the "Standard timings" dropdown box select 1280x720p @60 this should populate the boxes on the left again. Go to "tuning" and using the first tool (not ruler), move the left border right by one and the right border left by one. This should create 1278x720 resolution based on the standard EIA/CEA timing.

Next, go back to "Registry Hack" and click "Get Calculated" (just like you did before) and then "Write DTD's to Registry". Once done reboot and see if we get that one in the Graphics Tray.

If not, we need to do a little digging. Search the registry for "TotalDTDCount" (there should be a few of these. Look for the ones under "CurrentControlSet"). What values are they set to (obviously they should be 1)? Just below each of these TotalDTDCount keys you should see DTD_1 to DTD_5. Can you see your DTD in any of these keys?

If not, I would suggest removing the Intel drivers and then re-installing them. This will add a new set of reg keys which DTD Calc will look for.

I've not seen this problem before so your help in identifying what's happened could prove useful (hopefully to both of us ).

Cheers,

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by plac3bo
This tool seems to be exactly what i need, except...

When I run it and go to the "Registry Hack" tab, the bottom of the screen says in red text "Intel Graphics Registry Key Not Found" and the "Write DTDs to Registry" button is always disabled. Seems pretty obvious (after reading all about how this tool works) that the required registry entries inserted by the Intel driver are not present. I've tried numerous things over the last few days to overcome this, but, am worried I'm just missing something silly. I can provide full details of system if required, but, for now, I'll just list the ones that seem most prevalent, and hope some one can point out some boneheaded thing I've done (or not done). Thanks in advance for all the work and help.

OS: Vista Home (same results when 'Run as Administrator')
Chipset: Intel 915GM
Driver: Mobile Intel(R) 915GM/GMS/910GML Express Chipset Family (Microsoft Corporation - XDDM)
Driver Provider: Intel Corporation
Driver Version: 6.14.10.4656
I suspect this is because it's Vista, but using an XP driver (915 doesn't support Vista because it couldn't meet WDDM certification requirements; this is controversial in itself, but let's not go there). The DTDCalcuator is probably looking in the Vista driver registry locations, and the DTDs are likely in the XP driver registry locations. I can't think of a great way to gracefully cope with this (but since I'm not the coder, that may not matter), but you can manually stuff the registry once you've used the tool to find the right settings.

You should search the registry for TotalDTDCount and/or DTD_1. TotalDTDCount should be filled in with the number of new resolutions you'd like to have available, and DTD_x, where x = 1, 2, 3, 4, or 5, is where you should stuff the settings (with a "37 01" tacked onto the end).

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thanks to Wo0zy for stepping up on supporting this stuff while I was missing in action.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Thanks to Wo0zy for stepping up on supporting this stuff while I was missing in action.
Trying. Everyone deserves a vacation but don't make it TOO long mate .

plac3bo,

Archi's great spot is no doubt the answer. I can expand on the DTD Calc situation by explaining exactly what the logic is when looking for registry entries. Obviously your solution lays with Archi's suggestion but if you could take the time to compare your registry keys with the information I'm about to give and let us know where your setup differs it would probably help us to help others in your position.

When DTD Calculator checks for the presence of Intel Graphics drivers and reads DTD's from the registry it only looks in one key

HKLM\System\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}

Under this key you may have multiple 4 digit number keys (0000,0001,0002, etc). DTD Calc finds the highest 4 digit number key that contains a "TotalDTDCount" entry. If that fails it then checks inside each of the 4 digit keys for one that has a sub-key called "Settings" and looks for the "TotalDTDCount" in there. If multiples are found it again uses the entry found in the highest 4 digit key. Under that key there will be entries for DTD_1 through DTD_5 and it is these values that get returned in the DTD Calc "Registry Hack" tab. Obviously if the TotalDTDCount value=1 then only the entry under DTD_1 is returned (and so on).

I need to check with paul but I think the presence (or lack of) the "Settings" sub-key is a difference between the way the Vista and XP drivers write information.

If none of the above finds a relevant key this is when you get the "Intel Registry Key Not Found" message.

When writing new DTD's to the Registry, DTD Calc writes to all of the following

HKLM\System\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\nnnn

HKLM\System\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\nnnn\Settings

HKLM\System\CurrentControlSet\Control\Video\ANYSUBKEY\nnnn

HKLM\System\CurrentControlSet\Services\ialm\Device*

Where nnnn is any 4 digital number key, ANYSUBKEY means that it goes through every sub-key at that level and "Device*" means that the sub-key starts with the word "Device" and only writes DTD's (and TotalDTDCount) if the TotalDTDCount value is already present.

It's not the most straightforward thing to explain (Paul had to hammer a cork into one of my ears before it stuck) but when you're looking at the Registry it does make sense .

Your feedback would be appreciated.

Cheers,

Wo0zy.

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hey w0ozy. Thanks for the advice. I tried just what you said, and got the same result as last time. So, this time (after it reverted to 800x600 and none of my custome resolutions showing up in the Display Properties) I took notice of the DTD calculator. When I opened up Registry Hack, there was 1 DTD showing, but as you guessed it was all 0's. I clicked "Read from registry" and nothing happened.

I then opened up RegEdit and searched for TotalDTDCount. I found only found one instance of it under the key:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}\0000\Settings\TotalDTDCount

I checked for the DTD 1 to DTD 5 and sure enough they were there.

DTD 1 had all 0's
DTD2 had: 01 1D 80 D0 72 1C 16 20 10 2C 1A 80 00 00 00 00 00 86 37 01
DTD3 had: 01 1D 00 BC 52 D0 1E 20 B8 28 25 40 00 00 00 00 00 04 37 01
DTD 4 had: 01 1D 00 72 51 D0 1E 20 6E 28 25 00 00 00 00 00 00 06 37 01
DTD 5 had all 0's

So, I'm not sure what any of that means but hopefully it'll give you a hint of what we're dealing with.

Thanks!!

w00tw00t111

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thank you both for the quick response.

I've looked at my Registry and have:
Code:
HKLM\System\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}
+- 0000\
|   +- Settings
+- 0001\
    +- Settings
None of those (0000, 0000\Settings, 0001, 0001\Settings) contained a TotalDTDCount entry or DTD* entries.

I then manually added the TotalDTDCount (value=0) to all four keys (seperately, not together, and each time deleting the others before proceeding). I was able to run the DTD Calculator hack program and it now lets me write my custom DTD to the registry, however, the custom entries are not selectable after I reboot and do not appear in the List of All Modes dialog.

Is it possible the driver I am using doesn't support custom resolutions and if so, is there an alternative driver I can use?

Any insight is greatly appreciated.

plac3bo

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Try http://downloadcenter.intel.com/Deta...12536&lang=eng

(6.14.10.4764)

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by w00tw00t111
Hey w0ozy. Thanks for the advice. I tried just what you said, and got the same result as last time. So, this time (after it reverted to 800x600 and none of my custome resolutions showing up in the Display Properties) I took notice of the DTD calculator. When I opened up Registry Hack, there was 1 DTD showing, but as you guessed it was all 0's. I clicked "Read from registry" and nothing happened.

I then opened up RegEdit and searched for TotalDTDCount. I found only found one instance of it under the key:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}\0000\Settings\TotalDTDCount

I checked for the DTD 1 to DTD 5 and sure enough they were there.

DTD 1 had all 0's
DTD2 had: 01 1D 80 D0 72 1C 16 20 10 2C 1A 80 00 00 00 00 00 86 37 01
DTD3 had: 01 1D 00 BC 52 D0 1E 20 B8 28 25 40 00 00 00 00 00 04 37 01
DTD 4 had: 01 1D 00 72 51 D0 1E 20 6E 28 25 00 00 00 00 00 00 06 37 01
DTD 5 had all 0's

So, I'm not sure what any of that means but hopefully it'll give you a hint of what we're dealing with.

Thanks!!
Looks like we're getting somewhere.

If DTD_1 is all 0's and DTD calc says only 1 DTD is enabled that's why you aren't seeing a custom resolution. However, the system only uses entries under "CurrentControlSet" so if you haven't got any DTD keys there I think this is the problem (although I don't know what caused it).

Last question. When you select the standard 1280x720 timing from the calculation tab and then click "Get Calculated" on the "Registry Hack" Tab does this actually change the 0's to the DTD shown across the botton of the application? If it does then DTD Calc is working it just can't find the registry keys it needs to update.

If this is the case I would completely remove the Intel drivers, reboot and then reinstall them. After the install do another registry search for "DTD" and see if it returns entries under

HKLM\System\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}

If it does then DTD Calc should work again.

Cheers,

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hey Wo0zy, thank you for your continued help. I tried what you said,
i.e. try get calculated after the DTD is "erased" and sure enough it will grab the data (meaning like you said DTD seems to be working). So, I uninstalled the intel drivers, and then rebooted and reinstalled the drivers.

I then went into DTD calculator and tried the DTD that's listed up above in a previous post (it's for 1280x720). I "Get Calculated" Write to registry and then reboot. After rebooting I opened up DTD calculator and say "create modeline" and it populates all the other data. I go into ruler and then adjust so that the red lines border the edge of my screen. The resolution comes out to 1182x659 (I changed 659 to 660 so it would be an even number). I "Get calculated" and write to registry, then reboot. Upon rebooting my resolution (under display properties) it's 1182x660. My screen is much larger i.e. the text, icons, etc. and I still have overscan on all 4 sides.

So, essentially what I've described in the previous paragraph is the exact same problem that I've had each time that I try the DTD Calculator. When I open regedit
it defaults to HKLM\SYSTEM\ControlSet001\.... (where the TotalDTD was found before)
If I go to the reg value you provided and then extend it to the folder \0000\Settings I then find under DTD_1 the value that is shown in DTD calculator.

Both values match; which presumably is good but what isn't good is that the resolution still isn't correct and I'm not sure how to correct b/c if I change it to a certain amount it just seems to 'erase' the DTD in both the reg and in DTD Calculator.

Very perplexing.

w00tw00t111

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi!

Trying to figure out my LCD:s DTD but cant figure out which one to use. In much need of help to see if I can get it to work. Would much appreciate assistans.

I have a SAMSUNG LE-40R87BD. It is supposed to have native support of 1360 x 768 @60 hz according to manual. I 'm using G35 Chip (Asus P5E-VM HDMI).

Here is my report from the Intel Diagnostic:

Intel(R) Graphics Media Accelerator Driver Report


Report Date: 02/17/2008
Report Time[hr:mm:ss]: 00:29:07
Driver Version: 7.14.10.1350
Operating System: Windows Vista (TM) Ultimate* , (6.0.6000)
Default Language: Swedish
DirectX* Version: 10.0
Physical Memory: 2038 MB
Minimum Graphics Memory: 8 MB
Maximum Graphics Memory: 358 MB
Graphics Memory in Use: 163 MB
Processor: x86 family 6 Model 15 Stepping 13
Processor Speed: 2208 MHZ
Vendor ID: 8086
Device ID: 2982
Device Revision: 03


* Accelerator Information *

Accelerator in Use: Intel(R) G35 Express Chipset Family
Video BIOS: 1508
Current Graphics Mode: 1184 x 666 True Color (50 Hz)



* Devices Connected to the Graphics Accelerator *


Active Digital Televisions: 1


* Digital-tv *

Monitor Name: Generic PnP Monitor
Display Type: Digital
Gamma Value: 2,40
DDC2 Protocol: Supported
Maximum Image Size: Horizontal: 6,0 inches
Vertical: 3,0 inches
Monitor Supported Modes:
640 x 480 (60 Hz)
1280 x 720 (50 Hz)
1280 x 720 (60 Hz)
Display Power Management Support:
Standby Mode: Not Supported
Suspend Mode: Not Supported
Active Off Mode: Not Supported


* SDVO Encoder Report *

** Encoder 1 **
Vendor ID: Silicon Image
Device ID: 174
Device Revision: 0
Major Version: 1
Minor Version: 2

* Other names and brands are the property of their respective owners.

pettan7514

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi pettan7514,

Did you save the report to a text file before copying from it? If not please do this first. The text file should contain the EDID information which would help us with your problem.

Once we've got it, we can see if 1360x768 is likely to be possible or not.

Cheers,

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi!

Here is the report in text file format.

Thanks Wo0zy for taking time to help!

pettan7514

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

According to http://pixelmapping.wikispaces.com/Samsung+TVs your TV can do 1360x768 over HDMI, but your EDID is not providing any clues as to how to go about it. Are you plugged into HDMI port 1 or port 2? Port 2 might offer a different EDID, and according to the aforementioned website 1360x768 is only supported on Port 2.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I changed from HDMI port 1 to 2 and voila! All of a sudden I can choose 1360 x 768 right out of the box. I havent changed anything, this is standard graphic driver from Intel. Is this supposed to happen? I mean, so many others have problem getting there Native resolution?

pettan7514

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by pettan7514
I changed from HDMI port 1 to 2 and voila! All of a sudden I can choose 1360 x 768 right out of the box. I havent changed anything, this is standard graphic driver from Intel. Is this supposed to happen? I mean, so many others have problem getting there Native resolution?
TBH it totally depends on the TV. Some do 1:1 some don't. Looks like you got lucky.

Archibael,

Great find!! Already added the site to "Favorites"

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thanks a bunch for finding that out for me Archibael. Had almost given up hope :-)

pettan7514

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by pettan7514
I changed from HDMI port 1 to 2 and voila! All of a sudden I can choose 1360 x 768 right out of the box. I havent changed anything, this is standard graphic driver from Intel. Is this supposed to happen? I mean, so many others have problem getting there Native resolution?
There is much to curse about Intel graphics drivers' over-reliance on EDID, but in this case it works well. As Wo0zy points out, it is very dependent on your TV... and in that regime, your selection was a good one.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by pettan7514
Thanks a bunch for finding that out for me Archibael. Had almost given up hope :-)
Very glad to hear positive results, after a disappointing week from a personal perspective.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

First, thanks for the program. My TV's resolutions aren't recognized by the driver at all, the best I could get was 1280x960. DTDcalc let me go to 1080i and then correct the overscan.

In previous HTPC incarnations, I think it was the ATI drivers which offered something like 1776x1000 (which was close enough for me). I wish the intel drivers would do that. But that's Intel's fault (at least I blame it on them not the program author's. So far, great.

A suggestion: On page one of the thread, under Overscan, mention there will be red bars offscreen for adjustment? I tried for a good while to align the squares with the screen border which obviously doesn't work. The overscan is pretty massive so there is no chance I could see the red borders outlining the edge of the screen.
I also spent several attempts at adjusting things and clicking on "close". When I eventually returned to this pc with the overscan not fixed I found the post that explains why that happens. Still I wish the button was labeled cancel or something.

Do we know why the driver would only offer 1024x768, 1280x1024 and so forth. Clearly these resolutions are not offered by the display.

Not wanting to sound overly critical, but this chipset has been a serious disappointment so far. First the hardware acceleration turns out not to be an actual acceleration for x264 where it is needed most and then I get to spend an evening getting my screen resolution set up. Maybe expectations were too high :-(

MartinK

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by MartinK
First, thanks for the program. My TV's resolutions aren't recognized by the driver at all, the best I could get was 1280x960. DTDcalc let me go to 1080i and then correct the overscan.

In previous HTPC incarnations, I think it was the ATI drivers which offered something like 1776x1000 (which was close enough for me). I wish the intel drivers would do that. But that's Intel's fault (at least I blame it on them not the program author's. So far, great.
Actually, there's a VideoBIOS option for this chipset which does just that: if activated, any time 1920x1080 is found it adds 1776x1000 as well. I don't think it's implemented in too many BIOSes, unfortunately.

Quote:
Do we know why the driver would only offer 1024x768, 1280x1024 and so forth. Clearly these resolutions are not offered by the display.
Those are standards and get offered by default. Is the driver seeing your EDID?

Quote:
Not wanting to sound overly critical, but this chipset has been a serious disappointment so far. First the hardware acceleration turns out not to be an actual acceleration for x264 where it is needed most and then I get to spend an evening getting my screen resolution set up. Maybe expectations were too high :-(
If you expected x264 accel, yeah, your expectations were too high. Expecting resolutions to work properly, however, does not fall into that category, and your annoyance is warranted.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hey, thanks for the quick response.

The driver offered only standard desktop resolutions. I got the EDID as per the instruction from the thread from the diagnostic log. When I fed the EDID into DTD Calculator it came up with three options, one of them 1080i which is what I wanted. So far so good.

Asus P5K-VM HDMI / Monoprice 5way switch / Mitsubishi WD-52525 (I think)

I am unable to correct the overscan however; there is about an inch black on top. The overlay offered by the ruler tool is either not very precise or the TV doesn't respond as expected. I tried to move this upper border up in small increments, eventually it will either be out of sync when I reboot, or to add insult to injury set the border further DOWN.

I don't think this is for me

MartinK

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by MartinK
Hey, thanks for the quick response.

The driver offered only standard desktop resolutions. I got the EDID as per the instruction from the thread from the diagnostic log. When I fed the EDID into DTD Calculator it came up with three options, one of them 1080i which is what I wanted. So far so good.

Asus P5K-VM HDMI / Monoprice 5way switch / Mitsubishi WD-52525 (I think)

I am unable to correct the overscan however; there is about an inch black on top. The overlay offered by the ruler tool is either not very precise or the TV doesn't respond as expected. I tried to move this upper border up in small increments, eventually it will either be out of sync when I reboot, or to add insult to injury set the border further DOWN.

I don't think this is for me
Hi Martin,

The ruler tool is pixel accurate (especially if you use the UP/DOWN/LEFT/RIGHT buttons rather than dragging with the mouse. You can also use the adjustment tool (the blue square with the red border) for fine adjustment as this allows you to see where your active pixels "sit" within the blanking intervals.

Do I take it from your comments about feeding the EDID into DTDCalc that you're using the new version with the "Interpret EDID" Tab?

Just to clarify. You've added the standard 1080i resolution (obtained from your EDID) to the registry as DTD_1. You then reboot and select the new (overscanned) 1080i resolution from the Intel Graphics Tray. Then you launch DTDCalc again, go to the "Reg Hack" Tab and click "Read DTD's from Registry" which loads up your 1080i timing into the DTD_1 slot and then click "Create Modeline". Is this correct so far?

Next you go to the "tuning" tab and use the ruler tool to adjust as needed after which you write the new DTD to the registry.

What is the DTD you end up with after the adjustment?

Also, a quick Google for you TV brings up a few pages which suggest that while it supports 1080i this is done through scaling. 720p (or timings derived from 720p) may give you better results and stop the TV from scaling (which could have something to do with your problem).

Someone claims that the following modeline gave them the best results

ModeLine "666p" 74.56 1200 1288 1424 1680 666 694 697 746 -hsync +vsync

You could try feeding these into DTDCalc and see what happens.

Hope this helps a little. If not Archibael will probably have a few more suggestions and/or a flash of inspiration

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

There are certainly cases where the TV set itself "corrects" for all those annoying blanking pixels it finds driven into it and shifts back despite the work you've done to correct it with DTDCalc or just normal registry entry. This seems to be the behavior of certain models of TV, though I haven't compiled a list.

Wo0zy is certainly correct, though: have your PC do all the scaling work to 720p (or 666p, as the case may be), then feed the TV 1:1 pixels. Though it's not a sure thing, I suspect your PC's graphics will do a better job scaling than your TV will.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Wo0zy: Yes, that's what I did. Unfortunately this is a crummy TV, it doesn't read 720p from HDMI. (I think the speculation was that the electronics can't handle 720p, and it will drop half the lines than upscale to its native resolution of 720p. But I may not reproduce this right, it was made by men wiser than myself )

I ended up ordering an ATI 3450 today. Last time I used an HTPC it was just two clicks to get this right with the ATI drivers and this apparently problematic TV.

Thanks again for the awesome tool though; if it wasn't for that I would have been stuck at 1280x960

MartinK

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I am busy installing an AOpen MP945-VDR Mini PC and I'm having lots of trouble getting my Sony KDE-42XS955 to work via a DVI to HDMI cable.

I have to install Vista (with SP1 integrated) using a normal DVI/LCD monitor, else the user account creation page never shows up on the TV.

If I set the resolution to 1280x720 the TV will sync, but overscan.

When I run DTD it fails to load any timing from the registry.
If I select a standard timing, and modify it to 1216x684, and save it, reboot, nothing still shows up in the resolutions.

If I run PowerStrip it fails to retrieve any timings from the TV.

(I ran both DTD and PowerStrip as admin)

I don't know if this is due to to SP1, or if Vista and my TV and the GMA jsut does not get along well.

Anybody tried DTD on Vista SP1 with a 945GM, specifically a Sony KDE-42XS955 and a AOpen MP945-VDR?

Regards
P.

ptr727

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I am on SP1 but I was using G35...

What I needed to do is use the Intel control panel and save the system information to a file. It does not show this info on screen but the file had the EDID (sp?) blob that I needed to get started with DID calculator. Once I had that I was able to save and load custom resolutions.

(in regards to my earlier posts, ATI 3450 running fine by the way; offered 1776x1000 right on first boot and overscan was spot on)

MartinK

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by ptr727
I am busy installing an AOpen MP945-VDR Mini PC and I'm having lots of trouble getting my Sony KDE-42XS955 to work via a DVI to HDMI cable.

I have to install Vista (with SP1 integrated) using a normal DVI/LCD monitor, else the user account creation page never shows up on the TV.

If I set the resolution to 1280x720 the TV will sync, but overscan.

When I run DTD it fails to load any timing from the registry.
If I select a standard timing, and modify it to 1216x684, and save it, reboot, nothing still shows up in the resolutions.

If I run PowerStrip it fails to retrieve any timings from the TV.

(I ran both DTD and PowerStrip as admin)

I don't know if this is due to to SP1, or if Vista and my TV and the GMA jsut does not get along well.

Anybody tried DTD on Vista SP1 with a 945GM, specifically a Sony KDE-42XS955 and a AOpen MP945-VDR?

Regards
P.
Hi ptr727,

Can't say I have yet but Martin's results suggest it should work (even if he didn't get the results he was looking for).

Which version of the Intel drivers are you using? Also, search the registry for DTD_1 and TotalDTDCOunt. Make sure all relevant TotalDTDCOunts are set to 1 (or more) and check each DTD_1 to see if the values match your new DTD for 1216x684. You can copy the values from one of the keys and paste them into the reverse calculator (remember to remove the 37 01 from the end before calculating).

There is a post on page 5 which explains exactly which keys DTDCalc should write to which should help narrow it down

Let us know what you find.

Martin's suggestion regarding how to obtain the EDID for your TV is correct however, even if the DTD you choose is not correct it should still show up in the Graphics Tray.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Update:
I reinstalled Vista Ultimate with SP1, this time using a LCD monitor from start to finish.
After installing, a new Intel GMA driver was available through WU, this was reportedly published yesterday on WU.
The last time I manually installed the 15.7.3 drivers, this time I let WU install the updated GMA drivers.

For some unexplainable reason these two changes made a difference in the the observed behavior, this time I did get timings from the Intel diagnostic report, and I could create custom resolutions.

I still have DOS/BIOS mode overscan problems (this is great about the ATI HD2600XT card, works perectly in DOS/BIOS mode), but that is not something I can do anything about in software.

My DVI to HDMI converter with TosLink audio injection also does not work with the GMA card, it worked fine with my previous ATI X1300, but I'll take that up with the manufacturer.

Thanks for the support.

Regards
P.

ptr727

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Two quick questions:
1) Should I attempt to use even number resolutions, or are uneven number resolutions ok?
2) When using the ruler tool, how do you recommend to tune using the red border, i.e. red border visible, not visible, no pixels outside border visible, one line of pixels visible outside border visible, etc?

Regards
P.

ptr727

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by ptr727
Two quick questions:
1) Should I attempt to use even number resolutions, or are uneven number resolutions ok?
2) When using the ruler tool, how do you recommend to tune using the red border, i.e. red border visible, not visible, no pixels outside border visible, one line of pixels visible outside border visible, etc?

Regards
P.
Glad to hear you got things working although I can't explain why the WU driver worked and 15.7.3 didn't.

Regarding your questions.

1. Always go for even numbers of pixels. There have been some problems with odd numbers (primarily on the vertical timing). Also, avoid odd numbered "H Start of Sync Pulse" values. While odd numbers mostly work there is unexplained behaviour with Vista UAC and on startup/shutdown. Something to do with handoff to the secure desktop we think. Also Red/Blue reversal has been reported

2. Red border just visible is how if was designed. However, if you use VMC you may have to tweak the Horizontal to slightly larger than the visible area if you get odd screen corruption on the RHS of the image. Alternatively, use the custom resolution for the desktop only and configure VMC to use a standard resolution. If you tell the Wizard you're using a TV instead of a flat panel the VMC interface will compensate for overscan by moving navigation buttons "in" by around 10%.

Hope this helps.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Wo0zy, thanks for the advice.

Another unrelated question;
During Vista SP1 testing (pre-release and RTM) I found, and reported to Microsoft and was told the issue was reported to Intel, that SP1 and the 15.7.3 GMA drivers bluescreens two of my machines with GMA3000 (DG33TL) adapters on suspend/sleep. This does not happen on my machines with GMA950's.

Now that Vista is RTM, and Intel released new drivers through WU, same problem.
I am forced to set my machines to high performance power scheme to prevet them from sleeping.

Anybody else experiencing this?

Regards
P.

ptr727

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Yes. The 14.33 and 15.8 drivers list this in "Issues Resolved"

"BSOD happens when resuming from S4 on WinVista SP1."

Both drivers should be released publicly within the week.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Wo0zy, Archibael,
Just a quick note of thanks. After wasting 2 nights with Powerstrip a couple of months ago, I had given into just dealing with massive overscan and just using MediaPortal to adjust it. Great program, by the way.
Anyway, revisited the issue last week and came across this thread. An hour or so of tweaking last night with your program and I got it. No more overscan!
Awesome work, guys. Thank you.
Jim

mij1525

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by mij1525
Wo0zy, Archibael,
Just a quick note of thanks. After wasting 2 nights with Powerstrip a couple of months ago, I had given into just dealing with massive overscan and just using MediaPortal to adjust it. Great program, by the way.
Anyway, revisited the issue last week and came across this thread. An hour or so of tweaking last night with your program and I got it. No more overscan!
Awesome work, guys. Thank you.
Jim
Hi mij1525,

Thanks for taking the time to give positive feedback. It's appreciated.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Yes. The 14.33 and 15.8 drivers list this in "Issues Resolved"

"BSOD happens when resuming from S4 on WinVista SP1."

Both drivers should be released publicly within the week.
Thank you, are these new drivers, or any Intel Beta drivers available online?

ptr727

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

15.8 should show up this week. It was just released to the internal website last Friday, and the external release usually follows by about a week.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

G35 + Sony KDL-46V2000 = EPIC FAIL

Iíve just built a htpc based on an Asus P5E-VM HDMI and Iím having no luck getting the right resolution for my Sony KDL-46V2000. Iíve connected the htpc via VGA (Iíll worry about HDMI later) and the TVís PC input accepts 1360x768 with 1:1 pixel mapping but thereís no such choice in the display properties (Vista Ultimate 32 bit).

At the moment Iím running 1024x768 which naturally leaves a bunch of black unused space on the sides. I tried adding 1360x768 with Powerstrip but when I changed to this resolution, the graphics card just stuffed the extra pixels onto the same 4:3 space. Itís like the graphics card doesnít realise Iím using a wide screen tv.

Anyway, Iíd like to try the method explained in this thread but I donít know how to get the DTD for my TV. I tried method 3a ("save to file" via the Intel Graphics tray icon) but I just get an incomplete report that does not contain the Raw EDID. I canít find any Linux modeline for my TV and the last option (choosing a standard CEA resolution) went horribly wrong. I tried adding 1280x720p@60Hz but my TV wouldn't accept it and I had lots of problems getting any picture back so I'd rather not try that again.

Does anyone have any other ideas on how I can find a DTD that works with my TV? I specifically chose this motherboard so I wouldn't have to buy a separate graphics card, but right now, I'm seriously considering it.

Here are the resolutions that my Sony KDL-46V2000 accepts via the VGA input (image copied from the manual)


Oddish

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Create a diagnostic report from within the Intel Graphics Tray and post your EDID information. That'll give a starting point.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Maybe someone can help me with this. I have intel media graphics on a compaq presario c508. I am trying to use this utility to get 1920x1080i output to the second monitor port to run to my CRT projector. Here is the problem, the DTD calculator says "inet graphics registry key not found" Any ideas? I know for certian i am using intel GMA. I have vista basic installed. am logged in as admin and am not using the UAC.

Thanks,
Paul

pureroundcircle

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Wo0zy
Another spurious question Are you overclocking your system at all?
This is the other scenario that caused the "Driver" errors for me. Even ensuring that my RAM frequency was "fixed" didn't help.
I'm rubbish at OCing but in this case the system was rock solid until I did anything which "stressed" the graphics. Just a thought.
No Wo0zy. I'm not OC my system (E8400 is running at 3GHz). The bios (5.05) is set to normal mode.
Since I've updated the Display driver to 15.9, my display is back on 1080p60. I need to redo the registry hack for the 1080p48 mode availability

Later then...

John

JohnHWman

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Bizarre. Don't know why the two aren't playing well with one another. That fact that you get several seconds of good picture before it dies just adds to the nuttiness-- it's obvious it's transmitting right or you wouldn't get anything from other monitors, and it's obvious it's receiving right or you wouldn't get 1080p60 from other sources. If the timings were that off, you'd get a distorted picture.

Try

F3 39 80 18 71 38 2D 40 58 2C 45 00 00 00 00 00 00 1E

It's not 60Hz, it's 59.94Hz and might work better.
Archibael, I tried this DTD and while it was more stable than the 60Hz signal it still wouldn't stay on for more that 10 seconds at a time. Clearly the TV is not behaving correctly. When I get a chance I'll throw some other permutations at it and see how it behaves but I'm not optimistic. Thanks for the help.

tgemini13

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Ok,

I've updated the registry using DTD calc after Intel Video Driver 15.9 installation and my 1080p48 mode is back. Now, everytime I reboot my PC (after setting 1080p48 mode), the destop is still reverted to 1080P60 but now VISTA only pop-up a small message saying that my desktop resolution should be set to 720p for optimal watching

So I still need to manually reselect the 1080p48 mode using the Intel display configuration program... Not really convenient

Also, it seem's that I now have heavy stutter on BRD or HD-DVD playback for an unknown reason appart from the fact that I switched from 15.8.2 to 15.9 and updated PowerDVD Ultra from 3319a to last 4102 build... Stutter is present in either 1080p48 or 1080p60 full screen mode (but not in window mode ).

Who is faulty : Intel 15.9 driver or PDVD 4102 build ???

John

JohnHWman

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

4102 build, of course. Intel drivers can do no wrong!

I don't have an answer for why your machine is reverting to p60 and recommending a lower rez, but one possible fix is to set up a ResChange batch file to run at startup.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hello after many hours of reading, I know need some help with configuring my Intel integrated graphics. I have read through all the post and have been marginally successful in resolving my problem with the use of the DTD calculator. My problem that needs resolving is identical to the last persons thread which was not resolved ...the screen in vista is cut off from the left and any adjustments made just moves the right hand side of the screen causing flickering

My HTPC is connected via DVI to HDMI (TV end)
Vista home premium
Last intel drivers
Initially I was lead to believe my screen supported 1366 x 768 but the TV on screen display told me otherwise.

Results from using DTD calculator are here
640 x 480 @ 60 Hz
Block 1 DTD Found (See List)
Block 1 DTD Found (See List)
Display does not support underscan
Display supports basic audio
Display supports YCbCr 4:4:4
Display supports YCbCr 4:2:2
1 native formats in DTDs
Short Video Descriptor:
Resolution Supported - 1280x720p @ 59.94/60Hz 16:9 Native
Short Video Descriptor:
Resolution Supported - 1280x720p @ 50Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1920x1080i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1920x1080i @ 50Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x576p @ 50Hz 16:9 Non-Native
Short Audio Descriptor:
Audio Format - LPCM
2 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz, 32kHz
Bit Depth :24 bit, 20 bit, 16 bit
Speaker Allocation Block :
Speakers Present :
Front Left / Front Right
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)

So using this setting Resolution Supported - 1280x720p @ 59.94/60Hz 16:9 Native as my starting point , I have manged to configure settings so top and bottom of screen are lined up correctly .I have saved those settings which are 1244 x 672 , now when I attempt to rectify the over hang on the left of the screen all that happens is the adjustment are made to the right side of the screen any suggestions ??

Regards Toni

bonesoflondon

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi guys!
I just purchased an LCD TV and would like to run it at 1360*768 from my notebook.
I have an old ACER Travelmate 370 notebook with an Intel 82852/82855 GM/GME graphics card.
My problem is that DTD Calculator says it can't find an Intel graphics card.
I downloaded the latest drivers for this series (from 2006) it didn't help, but now I have a readout from moninfo which I didn't have before. I also tried the development driver linked here previously, the card works fine and I can get close to the desired resolution, but DTD still doesn't recognise my card.

Any idea on how I could trick DTD to write the desired resolution to the registry?

Thanks for your help.

akkerfeld

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Which drivers are you using? 855 didn't support custom resolutions unless you used the IEGD driver.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Intel Corporation 855 Embedded Graphics Controller
5.1.0.838
This is what I'm using right now and I also tried the lates driver from Intel's site.

This is what DTD is saying:

Intel graphics registry key not found

I'm using Win XP Prof SP3

akkerfeld

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Yeah, DTDCalc won't work with that chipset. You'd need to create a custom driver with the IEGD (go to Intel's Download Center and search on "IEGD") in order to get a custom resolution.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I downloaded IEGD 8.0 but when I try to run it it says that another instance of ced is already running...

Thanks anyway I think I should just throw this piece of crap out of the window.

akkerfeld

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi,

a little bit off topic but a lot of knowlegde seems to be here.

thank you for the custom resolution tool. After all I managed to set up my intel g31 to 1280x768@50Hz - never tought such a pain to get a good picture at hdmi (its digital, he.)

But off topic: serious problem at dvi hdmi connection from onboard G31 - 3100 to LCD TV. Everytime the tv is powered off while the htpc is running the intel gma (latest driver) will close the dvi connection, even after the tv is later switched on. I have to restart or hibernate an restore.

Anybody here have a solution ? Its a serious prob because: if an record is in progress and I later switch the tv on (after the htpc is on) there is only blank screen, not so good for an htpc.

thnx
joerg

herrmannj

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by herrmannj
Hi,

a little bit off topic but a lot of knowlegde seems to be here.

thank you for the custom resolution tool. After all I managed to set up my intel g31 to 1280x768@50Hz - never tought such a pain to get a good picture at hdmi (its digital, he.)

But off topic: serious problem at dvi hdmi connection from onboard G31 - 3100 to LCD TV. Everytime the tv is powered off while the htpc is running the intel gma (latest driver) will close the dvi connection, even after the tv is later switched on. I have to restart or hibernate an restore.

Anybody here have a solution ? Its a serious prob because: if an record is in progress and I later switch the tv on (after the htpc is on) there is only blank screen, not so good for an htpc.

thnx
joerg
Hi joerg,

This could be the "persistance problem" which was dealt with over on the G35 thread (see http://www.avsforum.com/avs-vb/showp...postcount=1037 for Dave's suggested fix). Give this a try and see if it helps.

The problem has also been reported as fixed in later drivers. What version are you currently running?

Hope this helps.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi,

thanx, will give it a try. I also saw in the history that it should be fixed in a earlyer driver version - but it still exist

I'm using the latest version 14.33 but I tryed some older version too ithout success.

Will report if your hint fix it.

thnx
joerg

herrmannj

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I see that the driver evrsion mendioned is 15.7.3. I think its a vista driver, I'm using the latest xp version 14.33. Maybe that makes a difference but I will give a shut with stopping Persistence=C:\Windows\system32\igfxpers.exe. wenn I'm at home.

Hopefull that will help.

joerg

herrmannj

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hey, thats do the trick, your my man.

wow, thanx very, very much !

herrmannj

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by herrmannj
Hey, thats do the trick, your my man.

wow, thanx very, very much !
Glad it worked but thank Dave (DPlettner). He found it

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Aloha, found this wonderful site and I am fiddeling with my sytem since days.
Formerly I had my Mitsubishi HC 900 on a computer with a real graphic card and was able to drive it in native mode via Power Strip.
From that time I still have a modeline, which worked like a charme:

"1024x576" 54,164 1024 1064 1200 1344 576 675 681 806 -hsync -vsync

Now I have the projector on one of those fancy intel boards and I am fighting to get it back. I wrote the above numbers into the DTD calculator, but the problem is, that the resulting DTD isn't valid. On of its fields shows 0X, which means, that something must be wrong. But I don't see what.
When I click the interlaced checkbox, the problem is solved, but of course I don't want it to be interlaced.

Any idea?
Thanks in advance!

galteser

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

28 15 00 40 41 40 E6 20 28 88 36 0X 00 00 00 00 00 18

The gap between the end of vertical active lines and the vertical sync pulse (99) is too large to express in standard VESA DTD notation, but dropping it down to the max allowable may shift your image down a lot.

Best you'll be able to get is:

28 15 00 40 41 40 E6 20 28 88 F6 0C 00 00 00 00 00 18

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by galteser
Aloha, found this wonderful site and I am fiddeling with my sytem since days.
Formerly I had my Mitsubishi HC 900 on a computer with a real graphic card and was able to drive it in native mode via Power Strip.
From that time I still have a modeline, which worked like a charme:

"1024x576" 54,164 1024 1064 1200 1344 576 675 681 806 -hsync -vsync

Now I have the projector on one of those fancy intel boards and I am fighting to get it back. I wrote the above numbers into the DTD calculator, but the problem is, that the resulting DTD isn't valid. On of its fields shows 0X, which means, that something must be wrong. But I don't see what.
When I click the interlaced checkbox, the problem is solved, but of course I don't want it to be interlaced.

Any idea?
Thanks in advance!
The error is due to the fact the the V. Sync Offset (the difference between the start of the V. Sync Pulse and the V. Active Pixels) is so large. The largest value you can represent in a DTD is 63 (decimal) or 3F (Hex). Don't ask me to explain or my head will explode

The reason that ticking the "Interlace" option fixes the problem is because doing so effectively halves all Vertical values so your V. Sync Offset changes from 63 (hex) to 31 hex) and bingo.

What this means is that modeline will never work with Intel Grahpics. Sorry

I would suggest perhaps grabbing the EDID for your display (using the Intel Diagnostic report) and using that as a starting point for creating a DTD friendly timing using DTDCalc.

Wo0zy

Edit: Took me sooo long to work it out that Archibael beat me to it

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thanks to the 2 of you.
2 problems with that:
1) When I use the suggested modeline, which probably drags the picture too low, it looks basically ok in DTD calculator. I write it to the registry and it IS in the registry. I can see it there and I can read it out back. Nevetheless I can?t choose 1024x576 neither in the Intel Graphics Media Accelerator driver nor in the usual display settings.
2) Fiddling with the EDID: I have verious EDIDs, the one from the Intel Graphics Media Accelerator driver and the ones Powerstrip saved on my old PC I used my projector with. I checked those out and they contain various resolutions, but NOT the native one. Weird. I talked to Mitsubishi and they told me they will get back to me. Eventually. Is there sth else I can do?

Thanks again.

galteser

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by galteser
Thanks to the 2 of you.
2 problems with that:
1) When I use the suggested modeline, which probably drags the picture too low, it looks basically ok in DTD calculator. I write it to the registry and it IS in the registry. I can see it there and I can read it out back. Nevetheless I can?t choose 1024x576 neither in the Intel Graphics Media Accelerator driver nor in the usual display settings.
2) Fiddling with the EDID: I have verious EDIDs, the one from the Intel Graphics Media Accelerator driver and the ones Powerstrip saved on my old PC I used my projector with. I checked those out and they contain various resolutions, but NOT the native one. Weird. I talked to Mitsubishi and they told me they will get back to me. Eventually. Is there sth else I can do?

Thanks again.
When you say it is in the registry, is every DTD_1 (or whatever "slot" you used) showing the correct DTD and are all "TotalDTDCount" entries set to (at least) 1 depending on the slot you used?

The EDID is normally a useful starting point but the whole point of using Archibael's DTD trick is to force a resolution that isn't included.

Are you using Xp or Vista and (forgive me for asking this), what language is the installation?

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Wo0zy
Are you using Xp or Vista and (forgive me for asking this), what language is the installation?
It is an English Vista Ultimate, for which I downloaded the German language
pack.

Quote:
Originally Posted by Wo0zy
When you say it is in the registry, is every DTD_1 (or whatever "slot" you used) showing the correct DTD and are all "TotalDTDCount" entries set to (at least) 1 depending on the slot you used?
What do you mean by "every"? There is only one? (Or do you mean in the subkeys/sub"directories" 000 and 001?)
There are 2 DTDs in the calculator, the one I used is DTD_1. The DTD_1 in the registry looks the same like the one in the calculator. (But is missed the last 2 blocks in the calculator. And the registry has DTD_1 to DTD_5 nevertheless, where the other entries are not empty either.) "TotalDTDCount" is set to 2.
Somehow you have lost me here ...

galteser

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by galteser
It is an English Vista Ultimate, for which I downloaded the German language
pack.



What do you mean by "every"? There is only one? (Or do you mean in the subkeys/sub"directories" 000 and 001?)
There are 2 DTDs in the calculator, the one I used is DTD_1. The DTD_1 in the registry looks the same like the one in the calculator. (But is missed the last 2 blocks in the calculator. And the registry has DTD_1 to DTD_5 nevertheless, where the other entries are not empty either.) "TotalDTDCount" is set to 2.
Somehow you have lost me here ...
http://www.avsforum.com/avs-vb/showp...&postcount=145

Tries to explain what keys are written to and read from by DTDCalc. It would be worth checking against your registry entries however, from your description it sounds right.

The last two bytes (37, 01) are added by DTDCalc. They are required before the Intel driver will use the DTD even though they're not part of the normal DTD structure.

Are you able to add any custom resolutions (even one that you know won't work)? Might be worth trying a sligtly modified standard timing and see if that shows up just to be sure that the drivers aren't blocking your timing for some odd reason. Other than that and maybe a fresh driver installation I'm out of ideas. Sorry.

Archi could well have a few more suggestions though

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Wo0zy

Archi could well have a few more suggestions though

Wo0zy
Yeah, you covered most of what I would have said. I'd open regedit, do a Find on DTD_1 and TotalDTDCount, and make sure every instance of them is populated with the DTD you want (obligatory Aliens paraquote: "It's the only way to be sure").

I don't *think* the BIOS would be refusing something esoteric like 1024x576, but it might be. Try 1022x576 (tweak third hex digit down two and fourth hex digit up two) and see if that shows up. If it does, it's a BIOS thing.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

(Archibael, I just have to try out the option you mentioned in the PM, just saw it right now and the cinema PC is switched on ony now and then, I just want to get the other facts off my chest now, will report about the other idea probably tonight.)

I talked to Mitsubishi by noiw and they told me, that 1024x576 isn't in the EDID, because this is no VESA resolution. I guess this is clear for you anyway, I still don't understand the finer details of this matter (and I'm not sure, if I want to

Quote:
Originally Posted by Wo0zy


http://www.avsforum.com/avs-vb/showp...&postcount=145

Tries to explain what keys are written to and read from by DTDCalc. It would be worth checking against your registry entries however, from your description it sounds right.

The last two bytes (37, 01) are added by DTDCalc. They are required before the Intel driver will use the DTD even though they're not part of the normal DTD structure.
Yes, I checked again and the registry looks fine.

Quote:
Originally Posted by Wo0zy
Are you able to add any custom resolutions (even one that you know won't work)? Might be worth trying a sligtly modified standard timing and see if that shows up just to be sure that the drivers aren't blocking your timing for some odd reason. Other than that and maybe a fresh driver installation I'm out of ideas. Sorry.
I tried the 1022x576 last night Archibael suggested and it shows up in the registry, but Windows doesn't give me the option to choose it after reboot. I have the weird feeling I'm doing something fundamentally wrong.

Will report later about the other idea.

galteser

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi,

I need some help/advice please! I am currently building up a new system, which has a small digital flat panel being driven by the LVDS port on a Intel 945 G/GM chipset. The problem I am having, is that I am not able to get this panel to be driven at a refresh rate of 50Hz, which according to it's specs it can handle. I have downloaded & installed the latest Intel drivers, and created a DTD for a 1024x768 @ 50Hz, using DTDCalculator (really nice piece of software, thanks WoOzy and colleagues).

Also, I created a couple of 'dummy' settings, like 1022x768 @60Hz and 1010x750 @60Hz, to see if they are recognised. I can get any of these settings to apply to a external monitor (over VGA or DVI), but the digital flat panel on the LVDS does not see these possible settings. One thing I have noticed, is that the option "Hide modes that this monitor cannot display" is greyed out, and cannot be selected. Is there a way round this - one of my colleagues, thinks that maybe creating a dedicated .inf file with the EDID that is needed and installing it would allow me to set the digital flat panel's refresh rate to 50Hz.

engineer_muppet

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by engineer_muppet
Hi,

I need some help/advice please! I am currently building up a new system, which has a small digital flat panel being driven by the LVDS port on a Intel 945 G/GM chipset. The problem I am having, is that I am not able to get this panel to be driven at a refresh rate of 50Hz, which according to it's specs it can handle. I have downloaded & installed the latest Intel drivers, and created a DTD for a 1024x768 @ 50Hz, using DTDCalculator (really nice piece of software, thanks WoOzy and colleagues).

Also, I created a couple of 'dummy' settings, like 1022x768 @60Hz and 1010x750 @60Hz, to see if they are recognised. I can get any of these settings to apply to a external monitor (over VGA or DVI), but the digital flat panel on the LVDS does not see these possible settings. One thing I have noticed, is that the option "Hide modes that this monitor cannot display" is greyed out, and cannot be selected. Is there a way round this - one of my colleagues, thinks that maybe creating a dedicated .inf file with the EDID that is needed and installing it would allow me to set the digital flat panel's refresh rate to 50Hz.
Interesting question.

You can certainly add a DTD to the driver setup inf (igdlh.inf for Vista) but I dont think it will help as DTDCalc writes to the same registry area.

If you want to try, just download the .zip version of the drivers. In the "Graphics" folder you'll find the setup information file. If you search through that you'll find the "DTD" and "TotalDTDCount" entries. Just change the TotalDTDCount value to 1 and add your new DTD to the DTD_1 entry (not forgeting the 37 01 at the end).

I have no personal experience of whether Intel treat LVDS any differently. Perhaps when Archibael comes online he might know.

Thanks for the kind words BTW and good luck with the project.

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Sorry, been gone on a road trip last four days or so.

Don't have any idea why LVDS is behaving differently than VGA/DVI. Can you read the EDID of the LVDS-connected flat panel?

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Sorry, been gone on a road trip last four days or so.

Don't have any idea why LVDS is behaving differently than VGA/DVI. Can you read the EDID of the LVDS-connected flat panel?
Hi archibael,

Using moninfo.exe, only the registry stored display information is read for the LVDS panel, and has no problems reading the display information for the VGA/DVI panel.

I have spent some time over the last few days looking into this a bit further, and have been thinking that to get a different refresh rate, the vBIOS may need to be accessed. Is this something that I can do at home/work, or is it something that needs to be done by Intel?

Thanks.

engineer_muppet

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by engineer_muppet
Hi archibael,

Using moninfo.exe, only the registry stored display information is read for the LVDS panel, and has no problems reading the display information for the VGA/DVI panel.

I have spent some time over the last few days looking into this a bit further, and have been thinking that to get a different refresh rate, the vBIOS may need to be accessed. Is this something that I can do at home/work, or is it something that needs to be done by Intel?

Thanks.
The vBIOS has a mode exclusion list which is pretty specific about what is rejected, which is why typically you can get 1022x768 @60Hz to work even when 1024x768 @60Hz is ruled out. Yeah, you could hack your BIOS (I've done it, though seldom have the courage to actually flash my goofy version), but I don't advise that unless all else has failed.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Wo0zy
Let me know how you get on. If Archi is referring you to me I don't hold out a great amount of hope but you never know.
Actually, I was only referring him to you because it sounded like he was having problems getting the DTD written to registry with the tool. Any failure, once it's in the registry, to actually see the resolution show up as selectable is certainly an Intel driver problem.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by oteacher
I've thought on that being the problem, and it may be! OS is Brazilian Portuguese, and Intel recognizes that and install in that language also (see screen capture).
Well if that's the case i rather wait for another version of the intel drivers.... than reinstall Vista (PIA). Or maybe there is some command-line options that changes the setup language?

Thanks

Alexandre
Aha

If that is the problem then directly editing the inf may well work. Got to be worth a try.

Cheers,

Wo0zy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

In that case, disregard that last post Captain. I'm stumped

But if you're happy, I'm happy

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by F4ion1
Tried that DTD and it showed the same way as when I manually created it. The size looks correct but it is too high and too far to the left(I'm beginning to think somebody doesn't want me to have a HD HTPC). I've got the Dell hooked up now with DTD running, trying to see if there is a way I can just export the exact hex of the DTD that it is running then paste that hex on the Macbook and create the DTD. Sounds simple but I can't find anywhere in DTD calculator to read the DTD that is currently showing, don't even know if that's possible.

grrrrrrrrrrrrrrrrrrr
Huh. Yeah, don't think the Dell will have the DTD anywhere except in memory, perhaps... and I don't even know where to tell you to look.

That hex should have worked... don't know why it's not doing so, other than that evil MacBIOS is interfering.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Huh. Yeah, don't think the Dell will have the DTD anywhere except in memory, perhaps... and I don't even know where to tell you to look.

That hex should have worked... don't know why it's not doing so, other than that evil MacBIOS is interfering.
I hear ya. I'll keep messing with it and see what I can come up with.

Thanks a bunch for all the help though.

F4ion1

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Hi F4ion1,

Just out of interest have you tried adjusting around the 1080i timings to see what happens?

Also, avoid odd numbered Vertical Pixel counts. Not that this is the problem with the current test DTD but I noticed in the report you posted that the current timing was 1198 by 665.

One final thing. The two reports also show two different driver builds (1364 and 1253). Again, I don't know why it would have an impact but it might be worth updating the dell drivers just to see if it breaks anything (having created a restore point obviously ).

Cheers,

Wo0zy.

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

To: archibael,

I just received an Asus P5E-VM HDMI from my very nice girlfriend. This will be my first build with an Intel IGP. I've been using an older Radeon with powerstrip to switch between 60Hz (for HDTV) and 48Hz (for DVD's). I understand Powerstrip won't work properly with IGPs. Thus the topic of this thread.

I use XP Pro. My HTPC outputs via DVI to my Optoma HD70 projector. I have no under/overscan issues. Everything is 1:1 pixel perfect without tweaking. I use powerstrip purely for the custom refresh rates.

My question is this: using the applications and techniques you're describing here, will I be able to add a 1280x720, 48Hz timing to the registry and then just switch between them using the built-in windows display properties dialog box (r-clicking the desktop, etc.)? This would be freaking awesome! I don't mind powerstrip, but I'd rather not use it if I can get by without it.

EDIT: I should add, the HD70 projector does NOT report 48Hz to Windows. Powerstrip forces 48Hz, and the projector syncs to it. Don't know if this is important...

Thanks,
Jay

Jay_S

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Yes.

Can you get a copy of the 48Hz timings you used with Powerstrip on the Radeon? You should be able to program them in to DTDCalculator (I like the Modeline format, but if you can't figure out how to convert them post them here and someone'll guide you through it) and have them added to the registry... at which point you can switch to them using the Display Properties dialog or ResChange.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Yes - powerstrip can export modeline info. I've done this to get Ubuntu working properly with the projector. I can't actually start this build until I have a few other components (namely ddr2 ram - should be here early next week). But this is all very exciting.

Thanks for the quick response,
Jay

Jay_S

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

archibael,

Here's the powerstrip dump:

Code:
PowerStrip timing parameters:
1280x720=1280,112,40,216,720,5,5,20,59329,2304

Generic timing details for 1280x720:
HFP=112 HSW=40 HBP=216 kHz=36 VFP=5 VSW=5 VBP=20 Hz=48

VESA detailed timing:
PClk=59.33 H.Active=1280 H.Blank=368 H.Offset=96 HSW=40 V.Active=720 V.Blank=30 V.Offset=5 VSW=5

Linux modeline parameters:
"1280x720" 59.329 1280 1392 1432 1648 720 725 730 750 +hsync +vsync

Jay_S

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by Jay_S
archibael,

Here's the powerstrip dump:

Code:
PowerStrip timing parameters:
1280x720=1280,112,40,216,720,5,5,20,59329,2304

Generic timing details for 1280x720:
HFP=112 HSW=40 HBP=216 kHz=36 VFP=5 VSW=5 VBP=20 Hz=48

VESA detailed timing:
PClk=59.33 H.Active=1280 H.Blank=368 H.Offset=96 HSW=40 V.Active=720 V.Blank=30 V.Offset=5 VSW=5

Linux modeline parameters:
"1280x720" 59.329 1280 1392 1432 1648 720 725 730 750 +hsync +vsync
DTD for 1280x720x48Hz:

2D 17 00 70 51 D0 1E 20 70 28 55 00 00 00 00 00 00 1E

It's a fractional pixel clock, which is somewhat unfriendly. If that doesn't work, try the slightly different:

2c 17 00 70 51 D0 1E 20 70 28 55 00 00 00 00 00 00 1E

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

archibael,

You rock. I can't implement any of this until next Thursday. Apparently UPS 3-day means 3 + 2 (for new year's eve and new year's day).

Thanks again,
Jay

Jay_S

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Let me know how it works out. Folks are seeing stutter at 24Hz on certain monitor and monitor/receiver combinations, so I'd be interested in how you do at 48Hz.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Archibael,

First of all, I'd like to express my sincere gratitude for your post on how to correct overscan, for the first time in literally few months since I got my slick little PC, I can sit back and enjoy a real movie played from the htpc, full screen and using the correct resolution! Thank you so much for taking the time to share your knowledge and give back to the community, thank you, thank you, thank you...

I have started in Vista a few months back, had never ending resolution issues with the Intel drivers available back then, and the best I could do is settling for a very odd resolution with everything showing inside a nice black frame on my TV. I obviously grew irritated by this very quickly (not to mention the risks of burn-in on my Plasma TV), add to that various Vista bugs, misbehaviors and sheer Windows annoyances in Media Center, I decided to ditch Windows altogether and jump into a Linux distro with integrated MythTV, I picked MythDora 4.0 which I installed and started working on... The idea for going Linux was that I'd be more likely to find ways to customize resolution, but also to check out what the MythTV hype is all about...

While the graphics are mouth drooling and the overall look and feel was absolutely fantastic, not to mention the kickass functionality & features, I soon hit a brick wall yet again with resolution issues (but of course many others which are typical noob headbanging issues such as LIRC, etc). To start with, my graphic card was not recognized and simply came up as generic which limits what I could do. After spending a LOT of time googling away and chewing on many forums and newsgroups, I figured that to even hope getting somewhere I had to recompile the kernel, recompile X server and only then be able to install and compile the needed Intel 2.2.0 driver which fixes some issues specific to my H/W. Nevertheless, I embarked into this and after hours and hours, days and days of headscratching and battling to set myself free in the Fedora dependency hell , I had to admit to myself that I have gone to a place which is a out of my league and way beyond my modest and rusty Linux knowledge, though it was both a refreshing and very frustrating experience, I had to... alas... go back to Windows.

My H/W is as follows:

AOpen MiniPC MP965-DR (same as Ryan1!)
Intel T7500 CPU
Graphics GM965 (GMA 3100X)
GMA driver: 7.14.10.1364

My TV is a Pioneer PDP-507XG [www (dot) pioneer (dot) com (dot) sg/storefront/brochure/7GPDP.pdf] The input signals supported through the 2 HDMI ports (3 & 4) which are HDMI 1.1 and HDCP 1.1 compliant are:

24Hz 1080p
50Hz 720p / 1080i / 576p / 576i
60Hz 720p / 1080i / 480p / 480i

The screen resolutions supported are:
HDTV 720p
1280 x 720
1366 x 768
HDTV 1080p
1920 x 1080

This spits out the following EDID:

EDID BYTES:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------
00 | 00 FF FF FF FF FF FF 00 41 2F A6 00 01 01 01 01
10 | 00 10 01 03 80 60 36 78 2A D7 B3 AE 51 50 94 23
20 | 0C 4A 47 00 00 00 01 01 01 01 01 01 01 01 01 01
30 | 01 01 01 01 01 01 01 1D 80 D0 72 1C 16 20 10 2C
40 | 25 80 B8 18 32 00 00 9E 01 1D 80 18 71 1C 16 20
50 | 58 2C 25 00 B8 18 32 00 00 9E 00 00 00 FD 00 17
60 | 3D 0F 2E 08 00 0A 20 20 20 20 20 20 00 00 00 FC
70 | 00 50 44 50 2D 78 78 37 47 0A 20 20 20 20 01 08

It is rather unclear from the documentation what the "native reolution" is for this TV, however, basing on its EDID and following the steps detailed in your wiki and DTD Calculator howto, I started off with DTD 01 1D 80 D0 72 1C 16 20 10 2C 25 80 B8 18 32 00 00 9E and end up with a setting (after fine tuning the overscan) of 1824 x 1026 (25Hz).

I just have two questions I hope you can advise on:

1) Based on the EDID above and the datasheet on the URL I provided, what would you say is the native rez I should be shooting for? At the moment, I really have movies playing FULL SCREEN (i.e. no side bars and no top/bottom bars!), which this looks great for HD video playback, it does look a little odd for SD video, not sure what it is (stretching? cropping? dunno...)

2) In your Wiki, you mention the following:

"Typically, the DTD is in the first Descriptor Block, but it can be in any of the four. You can tell if the data is a DTD or not because the first two bytes will be nonzero. In some cases, there may be more than one DTD listed because the monitor manufacturer has chosen to provide detailed timings for other modes-- possibly because they have an in-line scaler which works best with specific input timings. Consider all of these for your use, but the most important one for our purposes is the one which matches the native resolution of your display. In most cases (as in the example given), that will be the only one provided. If there are more than one, the best way to decide which to use, if you know what your monitor's native resolution is supposed to be, is to do a brief decode of the DTD parameters"

I'm little confused with this statement: If the EDID contains multiple DTDs, how to find the others? i.e. Ok, I can pick up the first one starting byte 54 and worth 18 bytes, but where are the others?


Many thanks again Archibael for your help.
A final word of kudos for WoOzy and the Clever Tech team for pulling our tormented souls out of trouble, respect!

And BTW, sorry for the long post and thanks for reading this far!

Cheers,
Moonray

moonray

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by moonray
Archibael,

24Hz 1080p
50Hz 720p / 1080i / 576p / 576i
60Hz 720p / 1080i / 480p / 480i

The screen resolutions supported are:
HDTV 720p
1280 x 720
1366 x 768
HDTV 1080p
1920 x 1080

This spits out the following EDID:

EDID BYTES:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------
00 | 00 FF FF FF FF FF FF 00 41 2F A6 00 01 01 01 01
10 | 00 10 01 03 80 60 36 78 2A D7 B3 AE 51 50 94 23
20 | 0C 4A 47 00 00 00 01 01 01 01 01 01 01 01 01 01
30 | 01 01 01 01 01 01 01 1D 80 D0 72 1C 16 20 10 2C
40 | 25 80 B8 18 32 00 00 9E 01 1D 80 18 71 1C 16 20
50 | 58 2C 25 00 B8 18 32 00 00 9E 00 00 00 FD 00 17
60 | 3D 0F 2E 08 00 0A 20 20 20 20 20 20 00 00 00 FC
70 | 00 50 44 50 2D 78 78 37 47 0A 20 20 20 20 01 08
There should be a second EDID block over HDMI which will contain more modes of resolution. Is it not showing up when you do Intel Graphics Tray, click Information, and choose Save to Disk?

Quote:
1) Based on the EDID above and the datasheet on the URL I provided, what would you say is the native rez I should be shooting for? At the moment, I really have movies playing FULL SCREEN (i.e. no side bars and no top/bottom bars!), which this looks great for HD video playback, it does look a little odd for SD video, not sure what it is (stretching? cropping? dunno...)
I'd strive for the native 1365x768p with the caveat that even though that is the native resolution, some HDMI receivers won't accept it over that interface (they scale everything which comes in). Barring that, I'd drive 1080p60 or 1080p24 and trust that Pioneer has tweaked their internal scaler to make sure 1080p looks good when scaled to the native.

Quote:
2) In your Wiki, you mention the following:

"Typically, the DTD is in the first Descriptor Block, but it can be in any of the four. You can tell if the data is a DTD or not because the first two bytes will be nonzero. In some cases, there may be more than one DTD listed because the monitor manufacturer has chosen to provide detailed timings for other modes-- possibly because they have an in-line scaler which works best with specific input timings. Consider all of these for your use, but the most important one for our purposes is the one which matches the native resolution of your display. In most cases (as in the example given), that will be the only one provided. If there are more than one, the best way to decide which to use, if you know what your monitor's native resolution is supposed to be, is to do a brief decode of the DTD parameters"

I'm little confused with this statement: If the EDID contains multiple DTDs, how to find the others? i.e. Ok, I can pick up the first one starting byte 54 and worth 18 bytes, but where are the others?
Immediately thereafter. So in this case your DTDs (from the first EDID block only) are

01 1D 80 D0 72 1C 16 20 10 2C 25 80 B8 18 32 00 00 9E
01 1D 80 18 71 1C 16 20 58 2C 25 00 B8 18 32 00 00 9E

Which are 1080i at 50Hz and 60Hz respectively.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

I really need to use the DTDCalculator, but every time I try to start it I get an application error "The application failed to initialize properly (0xc0000135)" Any one have any ideas?

Rapier

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Do you have .NET Framework 2.0? Pretty sure I saw that error back in the day when I had first tried to install it.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Quote:
Originally Posted by archibael
Do you have .NET Framework 2.0? Pretty sure I saw that error back in the day when I had first tried to install it.
Yep. Definitely a .Net Framework error. If you already have 2.0 installed run Windows Update and make sure you have all the latest patches.

Cheers,

Wo0zy.

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Just as a general update. The new version of DTD Calc should be ready during January.

It will include the updated modeline.txt with the new timings kindly supplied by Archibael (thanks) and a new tab for deciphering EDID and E-EDID information.

As well as extracting all DTD's from both blocks, the new tab will also report other EDID version 3 data block information including
Short Audio Descriptors (SADs),
Short Video Descriptors (SVDs),
Speaker Allocation Data
and one or two other bits of useful information (hopefully)

This should prove useful for determining the "REPORTED" capabilities of a screen or receiver without having to manually decode the information.

I'll also be in touch with Archibael regarding and update to the "How To" guide so that it includes a couple of "workarounds" to problems that have been discovered recently.

Happy New Year!!

Wo0zy.

Wo0zy

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

that got it. With the wiki link dead I'm still at loss on how to use the tool

Rapier

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Try http://softwarecommunity.intel.com/W...aphics/239.htm . It's not as visually stimulating as the original Wiki, but it provides the same information.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thanks for the help, I think I've got it figured out.

Rapier

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Help! I am struggling with the new G35 graphics chipset. My old pc connected to my TV through an aging nVidia card and worked flawlessly through a dvi>HDMI connection.

The new PC uses the G35 onboard graphics and connects directly through HDMI at both ends. 50% of the time when the PC restarts everything works perfectly. The other 50% of the time the TV displays a message "over range" and the image becomes stretched leaving the far right side forced off the edge of the screen (roughly from notification area).

By going into intel graphics properties if I change resolutions several times then eventually I can get a non-stretched, normal image. On both occasions the tv reports 1360 x 768 as the resolution size - just 50% of the time accompanied by "over range".

After reading through some of these posts I found that the EDID info is important so I've just copied this information from the report that is produced from the intel utility. I did this for both and it was identical. I've attached the two files to this message.

Thanks for any help you guys can offer.

garethuk

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

EDIDs are looking identical in each case, so that's not the problem.

Hrm. Have you used the DTD Calculator to set your resolutions, or is 1360x768 something that came up "naturally" with the drivers?

If the latter, try using DTD Calculator with

1b 21 50 a0 51 00 1e 30 48 88 35 00 c5 8f 21 00 00 1c

If you've already tried that DTD and it's causing you the problem, I'd tweak the 1st digit up and down one and try again:

1a 21 50 a0 51 00 1e 30 48 88 35 00 c5 8f 21 00 00 1c
1c 21 50 a0 51 00 1e 30 48 88 35 00 c5 8f 21 00 00 1c

Sounds like the Intel drivers are sending the right resolution but your TV isn't always syncing to it, which could just be a clocking mismatch (hence my suggestion to tweak the pixel clock parameter up and down in the above).

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thanks so much for your reply. It worked perfectly - I had to tweak it to get it to display as I already had one with that name. I changed it to 1366 x 768 and all is working fine.

When I next do a driver update will I need to do this again or does it stay in registry?

Thanks once again!

garethuk

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Results differ. Some people have it remain, and for some they have to re-apply.

You could always add it to the Modeline.txt file and then it will always be there for DTDCalculator to apply.

archibael

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

Thank you so much for your advice! You have solved me a bunch of hassle with the other half.

garethuk

Custom Resolution Tool for Intel Graphics Easier Overscan Correction

This is just a note that when I used the default 1280x720@60 setting, the image was offset to the left and the left half of the start button was cropped. Ironically enough, the intel graphic drivers offset to the right. I have a g965 chipset and a sanyo z4 (1280x720) lcd projector through vga.
I hadn't read of others with similar issues, maybe they just all knew how to fix it right off, so I wanted to post so others might be helped.
My settings are as follows and it fits on the screen correctly.
74.250 1280 1352 1440 1648 720 725 730 750 (notice the only change is the 1352)
01 1D 00 70 51 D0 1E 20 48 58 55 00 00 00 00 00 00 1E
The only issue that I'm having, now, is there is a vertical band of bold and fuzzy, when looking at text. I'm guessing that this is what people are calling vertical banding, but I'm not sure. It's entirely possible that I need to adjust some other parameters and it may not be perfect 1:1 pixel mapping, but it isn't jacked over to the side.
JJ

doubleJ

 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Previous Question:  
**A Funny Plasma Owner Story**
 AVS Forum  Plasma Flat Panel DisplaysNext Question:  Sprich mit dem Communityteam - 4a :)  Codemasters forum  Das Spiel

- Source: Custom Resolution Tool for Intel Graphics Easier Overscan Correction AVS Forum Home Theater Computers
- Previous Question: **A Funny Plasma Owner Story** AVS Forum Plasma Flat Panel Displays
- Next Question: Sprich mit dem Communityteam - 4a :) Codemasters forum Das Spiel