Difference between revisions of "OSSC potential incompatibilities"

From Classic Console Upscaler wiki
Jump to navigation Jump to search
(<autosumm-new>)
 
Line 1: Line 1:
This page lists consoles which can be incompatible with some displays when used with OSSC. Home computers and more exotic arcade boards are not included since their outputs often deviate from PAL/NTSC spec to a degree that they are not compatible with TVs but with PC monitors only. Capture card compatibility is neither considered since with some exceptions they are the most picky devices when it comes to non-standard refresh rates and line counts.
+
== Incompatibility due to display tolerance ==
 +
 
 +
Below are listed consoles which may be incompatible with certain displays when used with OSSC. Home computers and more exotic arcade boards are not included since their outputs often deviate from PAL/NTSC spec to a degree that they are not generally compatible with TVs but with PC monitors only. Capture card compatibility is neither considered since with some exceptions they are the most picky devices when it comes to non-standard refresh rates and line counts.
 +
 
 +
As a rule of thumb, consoles with linedoubled output with >1 scanlines off 525/625 spec or >0.5Hz off 50/60Hz refresh can be considered potentially incompatible for displays.
  
 
{| class="wikitable"
 
{| class="wikitable"
 
! align="left"|Console
 
! align="left"|Console
! align="left"|Why?
+
! align="left"|Reason
 
! align="left"|Test method
 
! align="left"|Test method
 
|-
 
|-
Line 9: Line 13:
 
|Hsync period is not constant, causing some jitter to output clock. Some displays are sensitive to this and cannot properly lock to the signal (low receiver PLL bandwidth).
 
|Hsync period is not constant, causing some jitter to output clock. Some displays are sensitive to this and cannot properly lock to the signal (low receiver PLL bandwidth).
 
|No known external test method.
 
|No known external test method.
 +
|-
 +
|Neo Geo
 +
|264-line output becomes 528 when linedoubled, not within +-1 lines of 525p@60Hz spec as required by some displays. MVS additionally uses 59.18Hz refresh rate that is too far from 60Hz for some TVs.
 +
|<pre>ModeLine "MVS_240p_x2" 26.81 720 736 798 858  480 489 495 528  -hsync -vsync</pre>
 
|-
 
|-
 
|PSX in 50Hz non-interlaced (288p) mode
 
|PSX in 50Hz non-interlaced (288p) mode
 
|314-line output becomes 628 when linedoubled, not within +-1 lines of 625p@50Hz spec as required by some displays.
 
|314-line output becomes 628 when linedoubled, not within +-1 lines of 625p@50Hz spec as required by some displays.
 
|<pre>ModeLine "PSX_288p_x2" 27.00 720 732 796 864  576 581 587 628  -hsync -vsync</pre>
 
|<pre>ModeLine "PSX_288p_x2" 27.00 720 732 796 864  576 581 587 628  -hsync -vsync</pre>
 +
|-
 +
|PAL Saturn in 60Hz mode
 +
|59.37 Hz vertical refresh rate
 +
|
 +
|}
 +
 +
== Incompatibility due to sync characteristics ==
 +
 +
Below are listed consoles which are incompatible with OSSC's default settings regardless of display. Some are simply fixed by a menu setting, others may need extra hardware.
 +
 +
{| class="wikitable"
 +
! align="left"|Console
 +
! align="left"|Reason/symptom
 +
! align="left"|Fix if any
 +
|-
 +
|Neo Geo MV-1A and MV-1FZ
 +
|Significant hsync period variation during vblank
 +
|H-PLL pre and post coast -> 3, Hsync tolerance -> 10us (or higher)
 
|-
 
|-
 
|Jaguar in 50Hz non-interlaced (288p) mode
 
|Jaguar in 50Hz non-interlaced (288p) mode
 +
|Output uses odd-odd field signaling since boot, OSSC can't lock properly
 +
|AV3 input (different sync processing chain) e.g. with Sync Strike
 +
|-
 +
|PSX SCPH-100 ('''unverified''')
 +
|No sync detected?
 
|
 
|
 +
|-
 +
|RGB modded French N64 ('''unverified''')
 +
|Unstable sync regardless of settings?
 
|
 
|
|-
 
|Neo Geo
 
|264-line output becomes 528 when linedoubled, not within +-1 lines of 525p@60Hz spec as required by some displays. MVS additionally uses 59.18Hz refresh rate that is too far from 60Hz for some TVs.
 
|<pre>ModeLine "MVS_240p_x2" 26.81 720 736 798 858  480 489 495 528  -hsync -vsync</pre>
 
 
|}
 
|}

Revision as of 21:18, 21 December 2016

Incompatibility due to display tolerance

Below are listed consoles which may be incompatible with certain displays when used with OSSC. Home computers and more exotic arcade boards are not included since their outputs often deviate from PAL/NTSC spec to a degree that they are not generally compatible with TVs but with PC monitors only. Capture card compatibility is neither considered since with some exceptions they are the most picky devices when it comes to non-standard refresh rates and line counts.

As a rule of thumb, consoles with linedoubled output with >1 scanlines off 525/625 spec or >0.5Hz off 50/60Hz refresh can be considered potentially incompatible for displays.

Console Reason Test method
NESRGB / SNES in 60Hz mode Hsync period is not constant, causing some jitter to output clock. Some displays are sensitive to this and cannot properly lock to the signal (low receiver PLL bandwidth). No known external test method.
Neo Geo 264-line output becomes 528 when linedoubled, not within +-1 lines of 525p@60Hz spec as required by some displays. MVS additionally uses 59.18Hz refresh rate that is too far from 60Hz for some TVs.
ModeLine "MVS_240p_x2" 26.81 720 736 798 858  480 489 495 528  -hsync -vsync
PSX in 50Hz non-interlaced (288p) mode 314-line output becomes 628 when linedoubled, not within +-1 lines of 625p@50Hz spec as required by some displays.
ModeLine "PSX_288p_x2" 27.00 720 732 796 864  576 581 587 628  -hsync -vsync
PAL Saturn in 60Hz mode 59.37 Hz vertical refresh rate

Incompatibility due to sync characteristics

Below are listed consoles which are incompatible with OSSC's default settings regardless of display. Some are simply fixed by a menu setting, others may need extra hardware.

Console Reason/symptom Fix if any
Neo Geo MV-1A and MV-1FZ Significant hsync period variation during vblank H-PLL pre and post coast -> 3, Hsync tolerance -> 10us (or higher)
Jaguar in 50Hz non-interlaced (288p) mode Output uses odd-odd field signaling since boot, OSSC can't lock properly AV3 input (different sync processing chain) e.g. with Sync Strike
PSX SCPH-100 (unverified) No sync detected?
RGB modded French N64 (unverified) Unstable sync regardless of settings?