Custom Resolution Tool for Intel Graphics: Easier Overscan Correction - Page 5

This horizontal offset over VGA can be fixed by adjusting the projector's "Horizontal" setting. I have my Z4 set to +55 or there abouts. On the projector's remote, press Menu, scroll to "Picture Adj." and change the "Horizontal" setting.


If it is a 1:1 pixel mapping issue via VGA then you can fix this in the projector settings also. Adjust the "Total Dots" setting. If you have just one vertical band then you may only need to adjust total dots by 1. But if you have multiple bands then you should see them spread out and disappear as you adjust total dots in the right direction. One setting will produce no bands and this is 1:1 pixel mapping. (It's easier to see if you tile a 2x2 pixel checkerboard pattern on your desktop.)

Note that the "Horizontal" and "Total Dots" settings are only available for the VGA input, not the HDMI input.

Also, if you haven't already, turn the projector's "Oversscan" setting to zero for the VGA input. And fiddle with the "Fine Sync" setting to see if that inproves your VGA picture.

Somehow using DTD2 which maps to 1080i @60Hz produces a flickery image and leads me nowhere... Using DTD1 (1080i @50Hz) brings me back to where I was after eliminating the overscan -> 1824 x 1026 (25Hz)...

You could try driving a generic 1365x768, but as I said it's uncertain it will show up on screen.

Sure willing to try in case it produces a better result, can you please explain how? Do I just pick a DTD close enough (e.g. DTD6) and modify "H Active Pixels" and ""V Active Lines" in the tool respectively to 1365 and 768 without touching anything else as the new DTD?

Thanks - I'll raise a new post on the 17-sec stutter as it at this stage it could be anything. I'll also update the post with a response from Intel regading Sound over G33!

On related note, is there anyway to have the PC changes it timings to automatically suit the media being played?

Eg I have some scripts running that change the frequency from 50hz (my default) to 24hz (maybe now 60hz) and back again when running PowerDVD HD for the playback of HD-DVD / Blue-ray (I can also assign keys to manual swap between 24, 50, and 60hz).

I've noticed the our PS3 will Automatically change its output based on the format of the disk being played, but is their any utility that will read a media's frame rate and change the PC's resolution/frequence to a predefined setting?

Thanks,
Nathan

Thanks - I use reschange to manualy change the refresh (I have three shortcuts each with just "-refresh=24 or 50 or 60" in it and it works perfectly). I've also made up an autohotkey script that detects when PowerDVD starts up / closes down and changes the refresh rate to suit - I've outlined the process here for anyone who is interested http://yabb.jriver.com/interact/index.php?topic=43879.0

Hi there

This seems great but every time I try to write anything to the registry it gives the following message

"An unhandled error occured and could NOT be logged"

"Click OK to continue"

"Requested registry access is not allowed"

I click the ok button and it just returns to DTD calculator.

Sorry to be a pain! I tried the links to your site and they didn't work, you see I thought I would just hack the registry manually..



Thanks in advance for your time

David

Hi David,

Are you using Vista?

Cheers,

Wo0zy

Hi there,
Yes I'm using Vista Home Premium

David

Try "Run as Administrator"

Hi David,

jmone is on to my next suggestion

Right-click on the DTD Calc shortcut and select "Run as Administrator". That should sort out the problem for you. The problem is the result of another Vista "security enhancement".

Good luck.

Wo0zy.

hi all,
I would just like to express my thanks to archibael and the folks who put this together. I have a 47" Westinghouse display and a desktop using the Jetway mini-itx J9F2 with the 945GM chipset through hdmi and a celeron m 440.

My moniter displays 1:1 at 1080p very well - but everything on the jetway was shifted left about an inch, or 40 pixels or so. I created a 1918x1080 resolution based on the stock settings, moved it over in the tuning panel, and voila - worked like a charm.

I will check tomorrow if the sound still works.

Anyway to modify the stock 1080p settings rather than use a wonky 1918x1080 setting? I want the 2 pixels i paid for!

Plus - shame on intel for making us learn all this stuff when everyone else builds a simple solution to take care of the problem!

This software saved me from having to return the board - thanks again!
cf

BRILIIANT!!!
It works a treat, that has been p*&&^ng me off for a couple of weeks.
I have a Panasonic TH-37PX70 plasma screen. Set my resolution to a very odd 1215 x 684 and happy days. I can now use my plasma for media center and surfing, thank god for that!

Its a shame that Intel don't do something, especially seeing as they have this on their site too!!!
Shame on MS Vista security enhancements too!

Thanks should go out to everyone that has been involved with this

Cheers

David

Hey everyone. I was receiving help in this thread http://www.avsforum.com/avs-vb/showthread.php?t=968533 with my new htpc. I tried w0ozy's suggestions and seem to still be having a problem.

I used:
01 1D 00 72 51 D0 1E 20 6E 28 55 00 D9 29 11 00 00 1A

Changed the resollution to 1278x720 and wrote it to the registry/rebooted.
Upon rebooting I changed my resolution to the 1278x720, but as expected the overscan was really bad. So, I opened up DTD calculator went to "Tuning" and opened the ruler. I then dragged all 4 sides of the rectangle to where the outer edge of the line was creating a border around my monitor. I clicked "apply". The new res. was something to the effect of 1168x660. I wrote that to the registry and rebooted. Upon rebooting, the screen had slightly less overscan, but still quite noticeable i.e. I could barely see the blue of the tool bar where as before, I couldn't see any of the tool bar. So, I opened the DTD calculator went to tuning -> ruler and did the same thing again. I then wrote the new values to the registry and rebooted.

Upon rebooting windows opens with 800x600 and all of my custom resolutions are not in the graphics properties. I went through this same process 3 times, and each time it did the exact same thing.

Any ideas?

Thank you!

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!!

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

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

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}\
nnn

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

HKLM\\System\\CurrentControlSet\\Control\\Video\\ANYSUBKEY\
nnn

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.

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\\{ 4D36E968-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!!

Thank you both for the quick response.

I've looked at my Registry and have:
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.

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

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.