Workbench/Prefs/ScreenMode - Revision history

Philippe Ferrucci at 23:36, 12 January 2013

2013-01-12T23:36:58Z

@@ Line 2: / Line 2: @@
 A screenmode will describe how you want a program to display information on your monitor: which monitor to use (if more than one is installed), which screen resolution to use, how many colors to display...
 With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...
@@ Line 16: / Line 18: @@
 == Defining a screenmode ==
-The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/.
+The new default method to define the screenmodes to be used by the graphic subsystem is to define the tooltypes of the monitor icons in Devs:Monitors/.
-== Tooltypes ==
+=== Using the GUI ===
 The monitor driver tooltypes for defining monitor specifications are:
 The minimum horizontal sync rate in Hz which is supported by your monitor. The default value is 31500. The lowest possible value is 15000. Please
 check the manual of your monitor for the correct value (its mostly specified in kHz so you have to multiply it with 1000, 31500 means 31.5 kHz).
-HSYNCMAX
+* HSYNCMAX
 Similar to HSYNCMIN, it specifies the maximum horizontal sync rate in Hz. The default value is 38000 (38 kHz). The value must be greater than HSYNCMIN.
-VSYNCMIN
+* VSYNCMIN
 The minimum vertical sync rate in Hz which is supported by your monitor. The default value is 60. The lowest possible value is 50. Please check the manual of your monitor for the correct value.
-VSYNCMAX
+* VSYNCMAX
 Similar to VSYNCMIN, it specifies the maximum vertical sync rate in Hz. The default value is 75. The value must be greater than VSYNCMIN.
     MODE=1280x1024@60
@@ Line 92: / Line 115: @@
 or 1920x1440@75 (112.5kHz)
-With the old style CRT (Cathode Ray Tube) monitors, a higher refresh rate results in less flicker. A too high refresh rate may however result in lower
+With the old style CRT (Cathode Ray Tube) monitors, a higher refresh rate results in less flicker. A too high refresh rate may however result in lower display quality when you have a cheap monitor cable (or even a monitor switcher inbetween the graphics card and the monitor) or you are running near the upper limit of graphics card or monitor. Most people are happy with about 70 or 75 Hz.
-With the new style digital TFT/LCD monitors, a higher refresh rate will not result in less flicker anymore because the monitor refresh rate differs from
+With the new style digital TFT/LCD monitors, a higher refresh rate will not result in less flicker anymore because the monitor refresh rate differs from the graphics card refresh rate. Here you should probably follow the recommendations from your monitor manual, often any refresh rate between 60 and 75 Hz is accepted.
 On digital TFT/LCD monitors, you should prefer the exact physical resolution of your monitor as default screenmode, then one pixel in your graphics card can be displayed as one pixel on your monitor. Any other resolution will result in interpolated pixels on your monitor which often causes moiree effects or a blurry display. Check the monitor manual for the exact physical resolution. When you want to use lower resolutions on a TFT/LCD, its often a good idea to use something which can be scaled with an integer number, e.g. when you use 640*480 on a 1280*960 monitor, the monitor can display each graphics card pixel with exactly four (2*2) of its own pixels. Using higher resolutions only makes sense for displaying large pictures in fullscreen mode when your picture viewer is unable to scale down the picture.
@@ Line 108: / Line 128: @@
 Example: MODE=1280x1024x24@75-hsync-vsync

Philippe Ferrucci: /* What is a screenmode? */

2013-01-12T22:50:45Z

What is a screenmode?

← Older revision		Revision as of 22:50, 12 January 2013
Line 1:		Line 1:
	== What is a screenmode? ==		== What is a screenmode? ==

	A screenmode will describe how you want a program to display information on your monitor. ~~With~~ ~~this preferences program you are able~~ to ~~select a graphic card~~ if ~~you have~~ more than one in ~~your~~ ~~computer.~~ ~~Then~~ ~~you~~ ~~can~~ ~~set the size of the display~~, how many colors ~~it will~~ display...		A screenmode will describe how you want a program to display information on your monitor: which monitor to use (if more than one is installed), which screen resolution to use, how many colors to display...

			With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...

	The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.		The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.

Philippe Ferrucci: /* History */

2012-12-09T19:01:11Z

History

← Older revision		Revision as of 19:01, 9 December 2012
Line 7:		Line 7:
	== History ==		== History ==

	The first tool in AmigaOS to define screnmodes is called Picasso96Mode. While this program is still released with the system, the prefered way is now to use the ScreenMode preferences program we discuss here.		The first tool that existed in AmigaOS to define screnmodes is called Picasso96Mode. While this program is still released with the system, the prefered way is now to use the ScreenMode preferences program we discuss here.

	Anyway, if you are an experienced user you might want to read the [[Workbench/Prefs/Picasso96Mode\|Picasso96Mode]] documentation.		Anyway, if you are an experienced user you might want to read the [[Workbench/Prefs/Picasso96Mode\|Picasso96Mode]] documentation.
	Note that this old method still works. However, Picasso96Mode will not recognize the modes created with ScreenMode.		Note that this old method still works. However, Picasso96Mode will not recognize the modes created with ScreenMode.

	== Defining a screenmode ==		== Defining a screenmode ==

Philippe Ferrucci at 19:00, 9 December 2012

2012-12-09T19:00:35Z

← Older revision		Revision as of 19:00, 9 December 2012
Line 1:		Line 1:
	= What is a screenmode? ==		== What is a screenmode? ==

	A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...		A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...

Philippe Ferrucci at 18:29, 9 December 2012

2012-12-09T18:29:09Z

← Older revision		Revision as of 18:29, 9 December 2012
Line 19:		Line 19:
	there are no resolution settings for the gfxboard.		there are no resolution settings for the gfxboard.

			== Tooltypes ==
	Picasso96Mode adds a SETTINGSFILE tooltype to the monitor driver icon which points to the modes stored in a binary file. The settings file screenmodes are added before the tooltype screenmodes, the tooltype screenmodes dont overwrite existing similar modes. So when you want to switch to the new method completely, dont forget to remove the SETTINGSFILE tooltype.

	You should first tell Picasso96 about the supported frequency ranges of your monitor, then define screenmodes, then save and reboot (the tooltypes are read during Picasso96 startup only).

	Caution, don't store monitor driver backups in Devs:Monitors/.
	Most existing monitor driver icons contain the BOARDTYPE tooltype which overrides the filename and specifies which card driver shall be used, it would be "random" which driver is found and used first, so if they conflict the correct driver tooltypes could not be able to redefine the modes already specified with the wrong tooltypes from
	the backup. You can exclude file names on the commandline of the LoadMonDrvs command call in Startup-Sequence but thats not recommended, please store your monitor driver backups in SYS:Storage/Monitors/.

	If you try to define a screenmode which would be out of the specified monitor frequency ranges, Picasso96 will reject that screenmode.

	If you try to define a screenmode which would be out of the capabilities of your graphics card, Picasso96 will either try to adjust it (by e.g. switching to DoubleScan mode or lowering the vertical sync rate if possible) or reject it (e.g. it will not accept 24bit/32bit modes on old graphics cards which dont support that).

	The monitor driver tooltypes for defining monitor specifications are:		The monitor driver tooltypes for defining monitor specifications are:

Philippe Ferrucci at 18:26, 9 December 2012

2012-12-09T18:26:14Z

← Older revision		Revision as of 18:26, 9 December 2012
Line 1:		Line 1:
	== What is a screenmode? ==		= What is a screenmode? ==

	A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...		A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...

	The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.		The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.

			== History ==

			The first tool in AmigaOS to define screnmodes is called Picasso96Mode. While this program is still released with the system, the prefered way is now to use the ScreenMode preferences program we discuss here.

			Anyway, if you are an experienced user you might want to read the [[Workbench/Prefs/Picasso96Mode\|Picasso96Mode]] documentation.
			Note that this old method still works. However, Picasso96Mode will not recognize the modes created with ScreenMode.

	== Defining a screenmode ==		== Defining a screenmode ==

			The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/.

	- "FAKENATIVE=<Yes\|No>" tooltype to disable the fakenative modes on the AOne (and only the AOne). The tooltype is ignored when		- "FAKENATIVE=<Yes\|No>" tooltype to disable the fakenative modes on the AOne (and only the AOne). The tooltype is ignored when
	there are no resolution settings for the gfxboard.		there are no resolution settings for the gfxboard.


	The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.

	Picasso96Mode adds a SETTINGSFILE tooltype to the monitor driver icon which points to the modes stored in a binary file. The settings file screenmodes are added before the tooltype screenmodes, the tooltype screenmodes dont overwrite existing similar modes. So when you want to switch to the new method completely, dont forget to remove the SETTINGSFILE tooltype.		Picasso96Mode adds a SETTINGSFILE tooltype to the monitor driver icon which points to the modes stored in a binary file. The settings file screenmodes are added before the tooltype screenmodes, the tooltype screenmodes dont overwrite existing similar modes. So when you want to switch to the new method completely, dont forget to remove the SETTINGSFILE tooltype.

Philippe Ferrucci: /* Defining a screenmode */

2012-12-09T18:18:51Z

Defining a screenmode

← Older revision		Revision as of 18:18, 9 December 2012
Line 6:		Line 6:

	== Defining a screenmode ==		== Defining a screenmode ==

			- "FAKENATIVE=<Yes\|No>" tooltype to disable the fakenative modes on the AOne (and only the AOne). The tooltype is ignored when
			there are no resolution settings for the gfxboard.


	The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.		The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.

Philippe Ferrucci: /* What is a screenmode? */

2012-12-09T18:02:37Z

What is a screenmode?

← Older revision		Revision as of 18:02, 9 December 2012
Line 1:		Line 1:
	== What is a screenmode? ==		== What is a screenmode? ==

	A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can the size of the display, how many colors it will display.		A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can set the size of the display, how many colors it will display...

	The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.		The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.

Philippe Ferrucci at 18:00, 9 December 2012

2012-12-09T18:00:40Z

← Older revision		Revision as of 18:00, 9 December 2012
Line 1:		Line 1:
	~~How~~ to ~~define~~ a ~~monitor~~ screenmode		== What is a screenmode? ==

			A screenmode will describe how you want a program to display information on your monitor. With this preferences program you are able to select a graphic card if you have more than one in your computer. Then you can the size of the display, how many colors it will display.

			The ScreeMode program also displays several information about the screenmodes. One of them is the ModeID which defines a screenmode by a unique identifier.

			== Defining a screenmode ==

	The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.		The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.

Philippe Ferrucci: Created page with "How to define a monitor screenmode The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors..."

2012-12-09T15:07:47Z

Created page with "How to define a monitor screenmode The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors..."

New page

How to define a monitor screenmode

The new default method to define the screenmodes to be used by Picasso96 is to edit the tooltypes of the P96 monitor icons in Devs:Monitors/. The old method, using Picasso96Mode, does still work, however, Picasso96Mode will not recognize the modes created with the new method. Picasso96Mode offers more control of details but is a bit complicated for the normal user.

Picasso96Mode adds a SETTINGSFILE tooltype to the monitor driver icon which points to the modes stored in a binary file. The settings file screenmodes are added before the tooltype screenmodes, the tooltype screenmodes dont overwrite existing similar modes. So when you want to switch to the new method completely, dont forget to remove the SETTINGSFILE tooltype.

You should first tell Picasso96 about the supported frequency ranges of your monitor, then define screenmodes, then save and reboot (the tooltypes are read during Picasso96 startup only).

Caution, don't store monitor driver backups in Devs:Monitors/.
Most existing monitor driver icons contain the BOARDTYPE tooltype which overrides the filename and specifies which card driver shall be used, it would be "random" which driver is found and used first, so if they conflict the correct driver tooltypes could not be able to redefine the modes already specified with the wrong tooltypes from
the backup. You can exclude file names on the commandline of the LoadMonDrvs command call in Startup-Sequence but thats not recommended, please store your monitor driver backups in SYS:Storage/Monitors/.

If you try to define a screenmode which would be out of the specified monitor frequency ranges, Picasso96 will reject that screenmode.

If you try to define a screenmode which would be out of the capabilities of your graphics card, Picasso96 will either try to adjust it (by e.g. switching to DoubleScan mode or lowering the vertical sync rate if possible) or reject it (e.g. it will not accept 24bit/32bit modes on old graphics cards which dont support that).

The monitor driver tooltypes for defining monitor specifications are:

HSYNCMIN
--------
The minimum horizontal sync rate in Hz which is supported by your monitor. The default value is 31500. The lowest possible value is 15000. Please
check the manual of your monitor for the correct value (its mostly specified in kHz so you have to multiply it with 1000, 31500 means 31.5 kHz).

HSYNCMAX
--------
Similar to HSYNCMIN, it specifies the maximum horizontal sync rate in Hz. The default value is 38000 (38 kHz). The value must be greater than HSYNCMIN.

VSYNCMIN
--------
The minimum vertical sync rate in Hz which is supported by your monitor. The default value is 60. The lowest possible value is 50. Please check the manual of your monitor for the correct value.

VSYNCMAX
--------
Similar to VSYNCMIN, it specifies the maximum vertical sync rate in Hz. The default value is 75. The value must be greater than VSYNCMIN.

The monitor driver tooltype for defining screenmodes is:

MODE
----
With this tooltype you specify at least the width and height in pixels and the vertical sync frequency in Hz of a screenmode. Example:

MODE=1280x1024@60

This will create a screenmode with a width of 1280 pixels, a height of 1024 pixels and a refresh rate (vertical sync rate) of 60 Hz.

When you are unsure about the widths, heights and frequencies to use, consult the manual of your monitor, it often contains a list a supported
screenmodes. Of course its possible to create more modes when your monitor has real multisync capabilities. Some hints:

Typical resolutions and frequencies supported by many monitors are
640x350@85 (37.9kHz)
640x400@85 (37.9kHz)
640x480@60 (31.5kHz)
or 640x480@72 (37.9kHz)
or 640x480@75 (37.5kHz)
or 640x480@85 (43.3kHz)
720x400@85 (37.9kHz)
800x600@56 (35.2kHz)
or 800x600@60 (37.9kHz)
or 800x600@72 (48.1kHz)
or 800x600@75 (46.9kHz)
or 800x600@85 (53.7kHz)
1024x768@60 (48.4kHz)
or 1024x768@70 (56.5kHz)
or 1024x768@75 (60.0kHz)
or 1024x768@85 (68.7kHz)
or 1024x768i@43 (35.5kHz)
1152x864@75 (67.5kHz)
1280x960@60 (60.0kHz)
or 1280x960@85 (85.9kHz)
1280x1024@60 (64.0kHz)
or 1280x1024@75 (80.0kHz)
or 1280x1024@85 (91.1kHz)
1600x1200@60 (75.0kHz)
or 1600x1200@65 (81.3kHz)
or 1600x1200@70 (87.5kHz)
or 1600x1200@75 (93.8kHz)
or 1600x1200@85 (106.3kHz)
1792x1344@60 (83.6kHz)
or 1792x1344@75 (106.3kHz)
1856x1392@60 (86.3kHz)
or 1856x1392@75 (112.5kHz)
1920x1440@60 (90.0kHz)
or 1920x1440@75 (112.5kHz)

With the old style CRT (Cathode Ray Tube) monitors, a higher refresh rate results in less flicker. A too high refresh rate may however result in lower
display quality when you have a cheap monitor cable (or even a monitor switcher inbetween the graphics card and the monitor) or you are running near the upper
limit of graphics card or monitor. Most people are happy with about 70 or 75 Hz.

With the new style digital TFT/LCD monitors, a higher refresh rate will not result in less flicker anymore because the monitor refresh rate differs from
the graphics card refresh rate. Here you should probably follow the recommendations from your monitor manual, often any refresh rate between 60 and 75 Hz is accepted.

On digital TFT/LCD monitors, you should prefer the exact physical resolution of your monitor as default screenmode, then one pixel in your graphics card can be displayed as one pixel on your monitor. Any other resolution will result in interpolated pixels on your monitor which often causes moiree effects or a blurry display. Check the monitor manual for the exact physical resolution. When you want to use lower resolutions on a TFT/LCD, its often a good idea to use something which can be scaled with an integer number, e.g. when you use 640*480 on a 1280*960 monitor, the monitor can display each graphics card pixel with exactly four (2*2) of its own pixels. Using higher resolutions only makes sense for displaying large pictures in fullscreen mode when your picture viewer is unable to scale down the picture.

Back to the explanation of the MODE tooltype, for interlace mode you can specify an "i" behind the refresh rate, e.g. 'MODE=1280x1024@60i'. BTW, doublescan mode is automatically activated when the horizontal frequency of the given mode drops below HSYNCMIN, but its also possible to activate it with a "d" behind the refresh rate. If you add an "r" instead, a mode with reduced blanking (only useful for newer TFTs) is created. Please note that reduced blanking is only supported at 60hz.

By default, each mode will be created in all available color depths. You can add a list of depths separated by commas to a mode specification to create a mode with only the specified depths. Example: MODE=1280x1024x8,16@60 will create the mode with depths of 8bit (256 colors) and 16bit (65536 colors), but not with 15bit (32768 colors), 24bit or 32bit (truecolor).

Adding "-hsync" to a mode specification changes the horizontal sync polarity to negative polarity, "+hsync" changes it to positive polarity. Adding "-vsync" or "+vsync" does the same for the vertical polarity. This may be useful when you have lots of similar screenmodes defined or a second computer attached to your monitor and the monitor is unable to distinguish all modes in his internal settings tables for screen placement etc, then the opposite polarity may help the monitor to distinguish screenmodes. The default polarity setting is undefined (depends on the mode requested).

Example: MODE=1280x1024x24@75-hsync-vsync