Comments (8)
I tested SNES specifically (as well as Genesis) to make sure Macrovision coasting wasn't required anymore.
So it's probably an issue with your sync signal and/or any processing done on it.
Can you describe your setup please? Especially important is any resistors in the sync line and if you use an LM1881, it's power supply (3.3 or 5 volts).
from gbs-control.
If you use direct console csync or Composite / Luma, the SOG slicer level is now important again (not so much / at all with an LM1881).
It can be changed by 'wsog x', where 'x' can be 0 (lowest) to 31 (highest). The default is 10.
from gbs-control.
My cable is wired to SNES csync through a 330 Ohm resistor.
By the way, what resistance do you measure on your GBS between sync and ground?
from gbs-control.
I measure 1k on a "2014" GBS and 500Ohm on a "2017" model.
Both have a single 1K resistor to ground installed, so no idea what's going on there.
Your SNES csync is probably too strong with those components.
I always recommend adding an additional 100Ohm to ground on the sync input, to more closely mimic a TV setup.
from gbs-control.
Yeah, it seems that the sync termination on the GBS is questionable, though it was designed for arcade hardware. The 330 Ohm serial resistor, which is recommended for SCART cables, is calibrated to bring TTL-level sync to ~1V peak-to-peak when the input is terminated to ground through 75 Ohms. I noticed that my SNES actually outputs ~3V peak-to-peak csync, though. I also modified my Genesis to output csync from the CXA1145 instead being driven directly from the VDP, so I have no serial resistor in the cable. I'll have to play around with different input/cable resistors tomorrow evening to find something that works for both consoles.
from gbs-control.
If you have an oscope: You want to aim for 0.3 to 1.0Vpp with the cables all connected.
Without oscope, you should install the recommended resistor: 100 Ohms to ground on the GBS sync input.
For a regular Genesis, csync is quite tricky to get right. Those require 470 Ohm in series, then a 10uF capacitor, then the ~ 75 Ohm to ground on the GBS (due to that extra 100 Ohm resistor).
But your Genesis is modified, so just the 100 Ohms will do.
There is another set of important parameters on S5_35 and S5_37. They handle sync pulse width margins.
Due to several sync input possibilities, this hpw can have a huge range.
I just found out that Genesis consoles can reach up to "200" on their weak and slow sloped csync lines.
A regular console would be more like "120".
I'll experiment with automatic settings for that.
It will have to be continuous, I think, because the console can switch the hpw. Genesis in 256px mode is such an example: Completely different pulse width than 320px mode..
In any case, if you install the 100 Ohm resistor and follow the cable diagrams for each console (or buy good premade cables), then the electrical side is fine.
from gbs-control.
OK, my SNES and Genesis both sync with 75 Ohm csync termination on the GBS.
from gbs-control.
Great, that's a relief. I think I have a good grasp on the SP now.
The correct termination resistance should also improve the signal integrity a little, as it helps avoiding reflections / ghost signals.
from gbs-control.
Related Issues (20)
- Sega Dreamcast desync with vga box at 960p, 1024p works fine 720p, 1080p
- Clarification about the power supply bypass capacitors HOT 6
- Jumpy image with SNES and Yoshi's island HOT 3
- How do I flash new firmware onto the GBS-C using Windows 11 HOT 2
- Connecting an old PC to the VGA port on a GBS-control sometimes results in garbled video HOT 1
- Someone to help Adding Amstrad CPC resolution ?
- Output old french TV standard
- Red & Green horizontal lines in just one quadrant of the the display signal. HOT 2
- RGBI/CGA color quantization? HOT 1
- Sync/Clock Issue
- Motion-adaptive de-interlacing not functioning on VGA input sources
- OLED screen - Line Filter toggle HOT 12
- Video Tearing/Artifacts HOT 22
- Cannot compile :c HOT 4
- [FR] Screenshot?
- Deinterlacing not working on Commodore 128
- Getting an error message when compiling: Compilation error: call of overloaded 'getParam(int)' is ambiguous HOT 1
- [Question] Can I Limit Which Resolutions Get Upscaled? HOT 7
- Gbs board not responding help!!
- Shaky image playing Yoshi`s Island and scart cable sync on luma on SNES
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gbs-control.