Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
system_tools:rtg [2019/11/29 06:14]
muaddib [Creating new screen modes]
system_tools:rtg [2020/06/06 09:54] (current)
muaddib [3) Test desired screen modes]
Line 5: Line 5:
 ===== Overview ===== ===== Overview =====
  
-''​Jason Mac Mullan''​ kindly develops and maintains the ''​SAGA RTG Driver''​ to be used with the ''​Digital Video Out''​ of the ''​Vampire''​ boards. The driver is still in a beta stage.+''​Jason Mac Mullan''​ kindly develops and maintains the ''​SAGA RTG driver''​ to be used with the ''​Digital Video Out''​ of the ''​Vampire''​ boards. The driver is still in a beta stage.
  
 ---- ----
Line 19: Line 19:
     * The original ''​Picasso96.lha''​ archive is hosted here legally, for preservation reasons. Its contents remain unchanged from the [[http://​aminet.net/​package/​driver/​video/​Picasso96|original]],​ conforming to the license. You can update ''​LIBS:​Picasso96/​rtg.library''​ yourself from other sources, for stability improvements.     * The original ''​Picasso96.lha''​ archive is hosted here legally, for preservation reasons. Its contents remain unchanged from the [[http://​aminet.net/​package/​driver/​video/​Picasso96|original]],​ conforming to the license. You can update ''​LIBS:​Picasso96/​rtg.library''​ yourself from other sources, for stability improvements.
  
-==== 1.2) Install the SAGA RTG Driver ​====+==== 1.2) Install the SAGA RTG driver ​====
  
-  - Download the latest [[saga:​updates|SAGADriver ​package]].+  - Download the latest [[saga:​updates|SAGA Drivers ​package]].
   - Use the provided installer and follow the instructions carefully.   - Use the provided installer and follow the instructions carefully.
  
Line 56: Line 56:
 **Remark:** **Remark:**
  
-The ''​SYS:​Prefs/​Picasso96Mode''​ tool will automatically hide (disable) all the resolutions that need more memory than the memory allocated by the ''​SAGA RTG Driver''​.+The ''​SYS:​Prefs/​Picasso96Mode''​ tool will automatically hide (disable) all the resolutions that need more memory than the memory allocated by the ''​SAGA RTG driver''​.
  
 ---- ----
Line 64: Line 64:
   * You can test RTG screen modes from the ''​ScreenMode Preferences''​ of AmigaOS.   * You can test RTG screen modes from the ''​ScreenMode Preferences''​ of AmigaOS.
   * You should use resolutions and refresh rates that work best with your monitor or TV.   * You should use resolutions and refresh rates that work best with your monitor or TV.
-  * We recommend using 1280×720 ​or 960×540 ​for the best AmigaOS experience. +  * We recommend using 1280x720 ​or 960x540 ​for the best AmigaOS experience. 
-  * If you have a Vampire Standalone, make sure you test 720x576@50Hz and 720x480@60Hz,​ to ensure that your monitor or TV works well with them. The Vampire outputs non-RTG ​screens using these two screen modes. (The former in PAL mode and the latter in NTSC mode.)+  * If you have a Vampire Standalone, make sure you test 720x576@50Hz and 720x480@60Hz,​ to ensure that your monitor or TV works well with them. The Vampire ​Standalone ​outputs non-RTG screen modes to Digital Video in these two resolutions. (The former in PAL mode and the latter in NTSC mode.)
  
 ---- ----
Line 71: Line 71:
 ===== Creating new screen modes ===== ===== Creating new screen modes =====
  
-The SAGADriver ​package already installs some commonly-used screen modes. But if the provided screen modes are not sufficient for your needs, you can create your own:+The SAGA Drivers ​package already installs some commonly-used screen modes. But if the provided screen modes are not sufficient for your needs, you can create your own:
  
   - Open a Shell window (''​newcli''​).   - Open a Shell window (''​newcli''​).
   - Run ''​umc <​width>​ <​height>​ <​refresh_rate>​ <​nowiki>​--</​nowiki>​rbt''​ to get the appropriate mode settings.   - Run ''​umc <​width>​ <​height>​ <​refresh_rate>​ <​nowiki>​--</​nowiki>​rbt''​ to get the appropriate mode settings.
     * For example, if you want a 720x576@50Hz screen, run ''​umc 720 576 50 <​nowiki>​--</​nowiki>​rbt''​.     * For example, if you want a 720x576@50Hz screen, run ''​umc 720 576 50 <​nowiki>​--</​nowiki>​rbt''​.
-    * You can request any mode from 320×200@200Hz up to 1920×1080@28Hz. ​ However, there are some limitations,​ which you can ensure by reviewing the output of ''​umc'':​+    * You can request any mode from 320x200@200Hz up to 1920x1080@28Hz. ​ However, there are some limitations,​ which you can ensure by reviewing the output of ''​umc'':​
       * Higher resolutions and refresh rates require higher clock rates.       * Higher resolutions and refresh rates require higher clock rates.
       * The clock rate should be at least 25MHz, which is the minimum allowed value for Digital Video.       * The clock rate should be at least 25MHz, which is the minimum allowed value for Digital Video.
Line 85: Line 85:
       * The ''<​nowiki>​--</​nowiki>​rbt''​ parameter is strongly recommended,​ because it will apply a special formula to reduce the blanking time and deliver the same resolution & refresh rate with a **lower** clock rate.  In this way, you can save some bus bandwidth, and also create high resolutions & refresh rates that would otherwise be unreachable due to the upper limit of the clock rate.       * The ''<​nowiki>​--</​nowiki>​rbt''​ parameter is strongly recommended,​ because it will apply a special formula to reduce the blanking time and deliver the same resolution & refresh rate with a **lower** clock rate.  In this way, you can save some bus bandwidth, and also create high resolutions & refresh rates that would otherwise be unreachable due to the upper limit of the clock rate.
       * If your monitor or TV does not work with "​rbt"​ modes, you can try omitting the ''<​nowiki>​--</​nowiki>​rbt''​ parameter. ​ For example, if ''<​nowiki>​--</​nowiki>​rbt''​ slightly reduces the desired horizontal/​vertical frequencies,​ and the reduced values fall slightly below the minimum specifications of your monitor or TV, then you should omit it.  Or, if you are creating a low resolution & refresh rate, and ''<​nowiki>​--</​nowiki>​rbt''​ causes the clock rate to fall below the lower limit, then you should omit it.  In these cases, even omitting ''<​nowiki>​--</​nowiki>​rbt''​ might be insufficient,​ and you might need to add the ''<​nowiki>​--</​nowiki>​margin=<​percentage>''​ parameter. (For example: ''<​nowiki>​--</​nowiki>​margin=20''​)       * If your monitor or TV does not work with "​rbt"​ modes, you can try omitting the ''<​nowiki>​--</​nowiki>​rbt''​ parameter. ​ For example, if ''<​nowiki>​--</​nowiki>​rbt''​ slightly reduces the desired horizontal/​vertical frequencies,​ and the reduced values fall slightly below the minimum specifications of your monitor or TV, then you should omit it.  Or, if you are creating a low resolution & refresh rate, and ''<​nowiki>​--</​nowiki>​rbt''​ causes the clock rate to fall below the lower limit, then you should omit it.  In these cases, even omitting ''<​nowiki>​--</​nowiki>​rbt''​ might be insufficient,​ and you might need to add the ''<​nowiki>​--</​nowiki>​margin=<​percentage>''​ parameter. (For example: ''<​nowiki>​--</​nowiki>​margin=20''​)
-      * You will be able to achieve a refresh rate of 60Hz for all resolutions up to and including 1280x720. ​ If you want to create a resolution higher than that, then, a refresh rate of 50Hz (or above) will exceed the upper limit of the clock rate, even with the help of the ''<​nowiki>​--</​nowiki>​rbt''​ parameter. ​ You will be forced to reduce the refresh rate down from 50Hz.  Here are the maximum refresh rates you can achieve for a couple of example resolutions:​+      * With the limitations above, you will be able to achieve a refresh rate of 60Hz for all resolutions up to and including 1280x720. ​ If you want to create a resolution higher than that, then, a refresh rate of 50Hz (or above) will exceed the upper limit of the clock rate, even with the help of the ''<​nowiki>​--</​nowiki>​rbt''​ parameter. ​ You will be forced to reduce the refresh rate down from 50Hz.  Here are the maximum refresh rates you can achieve for a couple of example resolutions:​
         * 1600x900: ≤40Hz         * 1600x900: ≤40Hz
         * 1920x1080: ≤28Hz         * 1920x1080: ≤28Hz
 +      * Vampire 500 V2+ and Vampire 600 V2 boards have not been designed to handle clock rates higher than 40MHz reliably. ​ This threshold will reduce the maximum reliable refresh rate for each resolution. ​ Here are a couple of examples:
 +        * 800x600 or 960x540: ≤ 60Hz
 +        * 1280x720: ≤ 38Hz
 +        * 1600x900: ≤25Hz
   - Run ''​SYS:​Prefs/​Picasso96Mode''​.   - Run ''​SYS:​Prefs/​Picasso96Mode''​.
   - Create a new resolution.   - Create a new resolution.
Line 108: Line 112:
 -> If you have a Vampire Standalone, the line size is independent of the memory burst, but it must still be aligned to 8 bytes. In other words, the horizontal resolution multiplied by the color depth (in bytes) must be a multiple of 8. -> If you have a Vampire Standalone, the line size is independent of the memory burst, but it must still be aligned to 8 bytes. In other words, the horizontal resolution multiplied by the color depth (in bytes) must be a multiple of 8.
 </​callout>​ </​callout>​
 +
 +----
 +
 +===== Display power management =====
 +
 +The RTG driver is compatible with the VESA Display Power Management Signaling (DPMS) standard. In particular, the "​On"​ and "​Off"​ states are supported, but the "​Stand-by"​ and "​Suspend"​ states are not.
 +
 +You can use ''​[[.vcontrol|VControl DPMS]]''​ to turn on/off the monitor or TV that is connected to the Vampire via Digital Video Out.
 +
 +Also, you can use [[http://​aminet.net/​package/​util/​blank/​DPMSManager|DPMSManager]] or a similar program to automate display power management. Note that the "​Stand-by"​ and "​Suspend"​ modes triggered by such programs will be interpreted as "​Off"​.
 +
 +----
 +
 +===== Disabling RTG =====
 +
 +If you are stuck with a non-working RTG screen mode (maybe because you accidentally saved a bad configuration,​ or you connected an incompatible monitor), you can disable RTG by holding down the <​key>​Shift</​key>​ key while booting. ​ The RTG driver will skip loading the RTG screen modes, and AmigaOS will boot into a default High Res 4-color screen mode.  (This is the same screen mode used in the Amiga Early Startup Control.) ​ Then you can switch to a more appropriate screen mode using the ''​ScreenMode Preferences''​ of AmigaOS.
  
 ---- ----
Line 115: Line 135:
 {{:​more-info.png?​nolink&​48|}} {{:​more-info.png?​nolink&​48|}}
  
-  * Technical information:​ [[saga:​video|SAGA Video Core]] +  * Technical information:​ [[saga:​video|Isabel: ​SAGA Video Core]] 
-  * SAGA RTG Driver ​sources: [[https://​github.com/​ezrec/​saga-drivers/​tree/​master/​saga.card|saga.card]]+  * SAGA RTG driver ​sources: [[https://​github.com/​ezrec/​saga-drivers/​tree/​master/​saga.card|saga.card]]
     * Covered under the ''​MIT License''​.     * Covered under the ''​MIT License''​.
-  * Forum: [[http://​www.apollo-core.com/​knowledge.php?​note=938|SAGA RTG Driver News]]+  * Forum: [[http://​www.apollo-core.com/​knowledge.php?​note=938|SAGA RTG driver news]]
   * Video: [[https://​youtu.be/​SqApemA9iM8|Vampire RTG Mode Introduction]]   * Video: [[https://​youtu.be/​SqApemA9iM8|Vampire RTG Mode Introduction]]
   * Video: [[https://​youtu.be/​kH62uNQaXBU|How to make your own resolution]]   * Video: [[https://​youtu.be/​kH62uNQaXBU|How to make your own resolution]]
Last modified: le 2019/11/29 06:14