The flicker on a PS2 game played through a modern TV is not a dying console or a bad cable. The console outputs 480i, an interlaced signal. Your LCD, OLED, or plasma panel is progressive-scan by design. Every display sold in the last two decades paints a full frame at once, so it has to do something with the two fields your PS2 sends 60 times a second. What it does with those fields is the entire story of why deinterlacing methods PS2 480i flicker exists as a problem you have to solve, and why the cheapest fix actively ruins the image. The ways to handle those fields are bob, weave, and motion-adaptive deinterlacing. Only one makes a game like Jak and Daxter look like it did on a CRT.

Bob Deinterlacing

Bob deinterlacing is the simplest method. The scaler or TV takes field one, which holds every other horizontal line of the image, and displays it as a full frame. A frame later it takes field two, the lines that were skipped, and displays that as the next full frame. The image is complete, the motion is smooth, and there is zero lag because nothing is stored. But the fields are offset by one line vertically, so static content appears to bounce up and down at 30 Hz. That is the flicker you are seeing on a PS2 menu screen. The text is not blurry. It is vibrating.

Bob deinterlacing trades resolution for motion clarity. It is the default on the OSSC because that device has no framebuffer to hold a full frame. Bob is the reason a game like Gran Turismo 4 looks like it is being viewed through a strobe light when the car stops moving.

Weave Deinterlacing

Weave takes the opposite approach. It stores field one in memory, waits for field two, and combines them into a single full-resolution frame. On a static image, the result is flawless. Every line of the original 480i signal is present. The moment anything moves, weave produces combing artifacts, those horizontal zigzag lines that tear across a moving character's face. A car driving across the screen becomes a set of offset slices.

Weave exists because video content, film and television shot at 24 or 30 frames per second, has very little motion between fields, so the artifact is rare. A PS2 game rendering at 60 fields per second has motion constantly. Weave is a disaster for gameplay. No serious scaler uses weave as the default for 480i, but cheap HDMI converters from Sham Shui Po do, because the converter chip was designed for a DVD player, not a console.

Motion-Adaptive Deinterlacing

Motion-adaptive deinterlacing fixes both problems. The scaler analyses the image per-pixel, decides which parts are static and which are moving, and applies weave to the static areas and bob to the moving ones. The result is a full-resolution frame that does not flicker and does not comb. This is the technique that makes the RetroTINK 5X-Pro the reference for PS2 gaming.

It is not magic. It needs a framebuffer to hold field one while it waits for field two, and it needs processing power to run the motion analysis. The OSSC, a line multiplier with no framebuffer, cannot do it. The GBS-Control, the community-developed firmware that turns an inexpensive VGA scaler board into something usable, attempts it. The claimed-vs-real gap here is well documented on the RetroRGB forums and the GBS-Control Discord: the motion-adaptive deinterlacing works, but on fast-moving red objects, a character's scarf or a car's tail light, it exhibits chroma artifacts, a false colour smear that looks like a bleeding edge. The cause is the GBS-8200 board's limited memory bandwidth, not the firmware. The processor inside cannot analyse and reconstruct the chroma channel fast enough, so it takes a shortcut that shows up on saturated red.

Testing The Difference Yourself

Use a test pattern with static horizontal lines at 1-pixel intervals. Run it through an OSSC in bob deinterlacing mode and the lines will appear to move up and down at 30 Hz, because each field is a line apart. Run the same pattern through a RetroTINK 5X in motion-adaptive mode and the lines hold still, because the scaler recognised them as static and weaved them.

The 5X's motion-adaptive implementation adds about a quarter of a frame of latency. That is imperceptible, and it is the price of doing the analysis. The OSSC's bob deinterlacing adds less than a frame, effectively zero, but the flicker is constant. The 5X also offers a bob mode if you want the zero-lag feel for a game that is always moving. For anything with a HUD, static text, or a menu, motion-adaptive is the one you want.

The GBS-Control Trade-off

The GBS-Control's problem is not that its motion-adaptive mode is bad. It is that it is inconsistent. On a game like Final Fantasy XII, slow-moving with a static menu, it looks as good as the RetroTINK. On Burnout 3, the red car smears. The community has measured the fix: you can lower the deinterlacing quality setting in the firmware to reduce the artifact, but then you are back to bob-level flicker. There is no free lunch on that board.

The RetroTINK 5X-Pro, by contrast, has a dedicated framebuffer and enough FPGA logic to do the chroma processing correctly. The 5X costs more, but for a PS2 library that is 70 percent 480i, the difference is the difference between playing the game and fighting the image.

Line Multiplier Or Framebuffer Scaler

Choosing a scaler for a PS2 means choosing between a line multiplier and a framebuffer scaler. The OSSC is a line multiplier. It takes the 480i signal, bob-deinterlaces it, and doubles the lines to 480p or higher. The image is sharp, the lag is microseconds, but the flicker is always there. The RetroTINK 5X-Pro is a framebuffer scaler. It captures the full frame, performs motion-adaptive deinterlacing, and outputs a clean progressive signal. It also has composite and S-Video inputs, which the OSSC lacks, so you can plug a Super Famicom or N64 into it without a separate converter.

The GBS-Control sits in between. It is cheap and competent for 240p, but its motion-adaptive mode is not reliable enough for a 480i-heavy PS2 library. The OSSC Pro, the successor to the OSSC, adds a framebuffer and adaptive line multiplication, but it still does not match the 5X's deinterlacing because it follows a different design philosophy.

Workarounds And The Hardware Limit

The GBS-Control is a community-developed replacement for the GBS-8200 board, a cheap VGA scaler originally designed for arcade cabinets. The firmware is open source and actively maintained. But the claimed-vs-real gap on its motion-adaptive deinterlacing is the chroma artifact on fast-moving red objects. The RetroRGB wiki has a page on this exact issue, documenting the memory bandwidth limits of the board's FPGA.

If you already own a GBS-Control, the workaround is to use bob mode for action games and accept the flicker, or to switch to a game like Persona 4 where the camera does not move much. If you are buying new, the RetroTINK 5X-Pro is the reliable choice. Its motion-adaptive deinterlacing is clean, and its latency is half a frame.

When You Do Not Need Motion-Adaptive

If your PS2 library is all 240p, which is the case for many early titles like TimeSplitters, the OSSC is perfect. It passes 240p through without deinterlacing, doubling the lines directly, and the result is razor-sharp. The RetroTINK 5X also handles 240p perfectly, but you are paying extra for the 480i capability. If you play PAL GameCube games, many of which run at 480i, you need motion-adaptive deinterlacing even more, because PAL at 576i has even more lines to flicker. The OSSC cannot fix that. A framebuffer scaler can.

The Generic Converter Trap

The failure case is what happens when you try to save money and buy a generic HDMI converter. It will see your PS2's 480i signal, misdetect it as 480i video, and apply a weave deinterlace. The result is combing on every moving object, a multi-frame lag, and a signal that looks like it is being broadcast through static. The chip is designed for DVD players, not games, and it treats the 240p signal from your Super Famicom as 480i, destroying the scanline effect and adding artifacts. This is the most common mistake in retro gaming. It is why the Hong Kong apartment gamer with one 4K OLED for everything ends up putting the console in a drawer. The fix is not a better cable or a different TV setting. It is a scaler with the right deinterlacing method.

CRTs And Modern Displays

If you are playing on a CRT, a PVM-20L5 or a consumer Trinitron, none of this matters. The CRT is an interlaced display, it paints fields in sequence, and the PS2's 480i signal looks exactly as intended. But CRTs are heavy, rare, and failing. On a modern display, the rule is simple: for PS2, GameCube, or Xbox games that run at 480i, you need motion-adaptive deinterlacing. Bob deinterlacing is a compromise you accept only if you cannot afford anything else. Weave is never acceptable for games. The GBS-Control is a budget option that gets you most of the way, but what it misses, the chroma artifact on red, is enough to break the illusion. The RetroTINK 5X-Pro is the reference because it does not have that problem.

Which Scaler To Choose

If you have a PS2 or GameCube with a 480i-heavy library and a modern TV, buy a RetroTINK 5X-Pro, or a RetroTINK 4K if your budget stretches. The 5X maxes at 1440p, the 4K outputs 4K with HDR, and both do motion-adaptive deinterlacing at about a quarter frame of lag. The OSSC is only suitable for 240p. The GBS-Control is only suitable if you are willing to debug firmware and put up with the red smear.

Do not buy a generic converter. Do not rely on your TV's deinterlacing, which is designed for film and adds lag even in Game Mode. The RetroTINK 5X has a menu system, profile saving, and accepts composite, S-Video, component, and RGB SCART. The RetroTINK 4K adds black frame insertion and HDR CRT emulation. Both receive firmware updates that improve deinterlacing quality, so the version number matters. Check the firmware before you update, because a slow lock means a blank screen for several seconds every time a PS1 game switches from a 240p menu to 480i gameplay.

Who Each Scaler Is For

This subject suits the gamer who wants to play, not tinker. If you enjoy building a GBS-Control, soldering wires, and flashing firmware, the RetroTINK is not your device. If you want to plug in a console, switch on a scaler, and play for an hour without touching a menu, the RetroTINK 5X-Pro is the only choice. The GBS-Control is for the tinkerer who accepts the chroma artifact as a quirk. The OSSC is for the 240p purist who will never play a 480i game. The RetroTINK 4K is for the collector with a 4K OLED.

If you are the Hong Kong apartment gamer with limited space, one display, and a shelf of consoles, the RetroTINK 5X-Pro is the one that works for all of them. The mClassic claims 1440p output and zero lag, but independent testing with a Time Sleuth shows measurable lag and a 1080p active image, so skip it for this use case.

Firmware Changes Everything

The deinterlacing landscape changes with firmware. The RetroTINK 5X added a new bob mode that reduces flicker on static content by alternating the phase, but it is still bob. The RetroTINK 4K added a weave mode for test purposes, but it is not recommended for games. The OSSC firmware is the reference for its bob implementation, and it has not changed because the hardware cannot do more. The GBS-Control updates frequently, so check the Discord for the latest release. The point is that you cannot read a review from years ago and expect it to apply. The hardware is fixed. The firmware is not.

The Hardware Limit Nobody Talks About

One thing the guides will not tell you: the claimed-vs-real gap on the GBS-Control is not a firmware bug that will be fixed. It is a hardware limit. The GBS-8200 board uses a single 16-bit memory bus, and the FPGA cannot read and write the framebuffer fast enough to do full chroma processing at 60 fields per second. The community has overclocked the memory, but the artifact persists. If you see a video titled "GBS-Control is perfect now," watch for the red test pattern. If it is not there, the creator is hiding it.

Deinterlacing Methods for Retro Gaming: Bob, Weave, and Motion-Adaptive