The question of whether to plug a Marseille mClassic into a PlayStation 5 or Xbox Series X is really a question about what kind of image processing you trust. The debate comes down to a hard technical ceiling: the dongle accepts an HDMI signal up to 1080p and outputs a 1440p frame with a 1080p active image area, or 4K only at 30Hz or below, per Marseille's own specification. Your console, meanwhile, natively outputs 3840×2160 at up to 120Hz over HDMI 2.1. The dongle is not going to make a native 4K signal sharper. It cannot even accept one without passing it through untouched. It is a tool built for 720p and 1080p sources, and your current-gen console is not one of those unless you force a resolution change in the system menu.

What the mClassic Actually Does at the Hardware Level

Inside the Dongle: Single-Frame Processing

The mClassic is a small HDMI dongle powered by the HDMI port itself, drawing 1.5W via a Micro-USB connection that you must also attach for stable operation. Inside is the Marseille VTV-1224A processor, a chip that applies a proprietary form of post-process AA called context-adaptive anti-aliasing. This is a single-frame analysis technique: it looks at the pixels it has, estimates edges, and smooths them. It is not temporal. It does not use motion vectors, and it has no access to the game's rendering buffer. When you feed it a 1080p signal, it upscales that to a 1440p frame, but the active image area remains 1080p. The extra pixels are interpolated from the single frame it received. At 60Hz, the maximum output is 2560×1440 with 4:4:4 or 4:2:2 chroma subsampling depending on the source. At 30Hz or below, it can output 3840×2160, but that 4K signal uses 4:2:0 chroma subsampling, and it is still upscaled from the same 1080p analysis, not a native render.

Why Console Scalers Win

This matters because the PS5 and Xbox Series X have their own built-in scaler, and that scaler runs at a different tier of sophistication. The consoles use temporal upscaling methods: FSR upscaling on the system level, and on PS5 titles that support it, PSSR motion vector-based reconstruction, which is a cousin of DLSS temporal upscaling. These techniques look at multiple frames, track where objects move, and reconstruct missing detail from that motion data. The mClassic cannot do any of this. Its spatial processing is mathematically incapable of generating information that was never in the frame, and that is the entire point of temporal upscaling. A single-frame post-process algorithm will smooth edges, but it will never recover the fine detail that a temporal solution reconstructs from motion.

mClassic Current-Gen Console Dongle Limitations

The Downscale-Upscale Trap

Here is the practical problem. The consoles do not output 1080p by default. They output 4K. If you want the dongle to process the signal, you must go into the console's video settings and force a 1080p output. That means the console downscales its native 4K render to 1080p, sends that to the dongle, and the dongle upscales it back to a 1440p frame. The result: you are throwing away resolution twice and then asking a spatial scaler to approximate what you discarded. Independent testing, including the work done by My Life in Gaming and Digital Foundry, has consistently shown that the unit provides no measurable improvement on current-gen titles when the console is set to its native resolution. The failure case is obvious. A gamer who buys the dongle expecting a sharper image on a 4K screen will see a softer one. The 1440p output is upscaled to 4K by the TV's own scaler, and the TV's scaler adds lag and blur on top of the dongle's processing.

Backward Compatibility: The One Partial Win

The one scenario where the device does something visible is with backward-compatible titles that run at 720p or 1080p internally. On Xbox Series X, the Heutchy Method provides integer-like scaling on supported titles, multiplying the original resolution by two to four times, and that system-level scaler is so effective that the mClassic adds nothing on top. On PS5, PS4 titles that render at 1080p get the dongle's edge smoothing, but the effect is subtle and often introduces ringing halos around sprites, a sharpness artifact that was not present on the original hardware. The 1440p output claim gap is real: Marseille markets 1440p output, but it is a 1440p frame holding a 1080p image upscaled, not a native 1440p render. The gap is a full resolution tier, and it exists because the scaler does not generate new pixel data.

PS5 Upscaling vs External Scaler: Why Temporal Beats Spatial

Motion Vectors vs Static Edges

PS5 upscaling vs external scaler is not a fair fight. The PS5's own system-level scaling is already doing more than any external box can. The PS5 outputs up to 4K at 120Hz over HDMI 2.1, and its built-in scaler, when forced to output 1080p for a 1080p screen, uses a temporal reconstruction that analyses multiple frames. The dongle's context-adaptive anti-aliasing is a post-process AA technique, meaning it operates on the finished frame. It cannot see the motion vectors. It cannot consult the depth buffer, and it has no concept of what the next frame will look like. The result is that on a moving image, which is all of gaming, the dongle's smoothing produces a static edge that flickers where a temporal solution would have reconstructed a stable edge.

The VRR and Lag Penalty

Consider what happens on a 4K OLED with VRR. The PS5 can output a 4K signal with VRR enabled, and the screen handles the refresh rate. Insert the mClassic into that chain. You force the console down to 1080p. You disable VRR because the dongle is HDMI 1.4b and does not support the feature. Then the dongle's 1440p output goes to the TV, which has to scale it to the panel's native resolution. The TV's scaler adds its own lag, typically 10 to 15 milliseconds at 1080p and up to 40 milliseconds at 4K even with Game Mode enabled, according to testing of Samsung and LG panels. The mClassic adds 1 to 2 milliseconds of its own processing, measured with a Time Sleuth. That is irrelevant when the display chain is already adding an order of magnitude more. The built-in scaler on the PS5 and Xbox Series X, by contrast, adds no measurable lag beyond the display chain, a fact confirmed by Digital Foundry's 2020 testing.

Xbox Series X Anti-Aliasing mClassic: Does It Improve the Image?

Modern Titles: No Signal, No Effect

Xbox Series X anti-aliasing testing reveals a clear answer: no, not for modern titles. The Series X uses the Heutchy Method for backward compatibility, a per-title resolution multiplier that can double or quadruple the original resolution on select games. This is a system-level process that outperforms any external scaler because it has access to the game's internal rendering data. When a title is Heutchy-enhanced, it renders at a higher internal resolution and then scales it to 4K using the console's built-in scaler. The mClassic, inserted between the console and the TV, only sees the final output, which is already 4K. Since the dongle cannot accept a 4K signal without passing it through untouched, it does nothing at all. The processing chip only engages when the input is 1080p or lower.

Older Titles: Edge Smoothing at a Cost

For Xbox 360 titles that do not receive the Heutchy treatment, the console outputs them at their native 720p or 1080p, and here the mClassic does apply its edge smoothing. The visible result is a reduction in aliasing on 3D geometry. It comes at the cost of sharpness. The console's built-in scaler, which is a simple bilinear or bicubic filter, produces a sharper image when the source is 720p because it is upscaling to 4K directly. The mClassic takes that 720p signal, upscales it to 1440p, and then the TV has to scale that to 4K. The double upscaling softens the image. Digital Foundry's 2019 review noted this exact behaviour: edge smoothing is visible on 720p sources, but the loss of fine detail from the intermediate scaling step is noticeable on a large 4K screen. If you want better anti-aliasing on an Xbox Series X, look at display-side motion blur guides and VRR setup, not a scanline generator or an external dongle.

Marseille mClassic 4K Output Claim: What the Spec Sheet Really Says

The HDMI 1.4b Bottleneck

The Marseille 4K output claim is technically true and practically misleading. The dongle can output 3840×2160, but only at a maximum refresh rate of 30Hz, and only with 4:2:0 chroma subsampling. At 60Hz, the maximum output is 2560×1440 with 4:4:4 or 4:2:2 chroma subsampling. This is not a limitation of the chip. It is a limitation of the HDMI 1.4b interface the dongle uses. HDMI 1.4b has a maximum bandwidth of 10.2 Gbps, which is not enough for 4K at 60Hz with full chroma. The PS5 and Xbox Series X use HDMI 2.1, which has a bandwidth of 48 Gbps, enough for 4K at 120Hz with full 4:4:4. The mClassic is a bottleneck. No firmware update can change that.

Handshake Failures and Black Screens

For a modern gamer, the 4K output claim is irrelevant because a 30Hz signal is unplayable for most titles. Racing games, shooters, and action titles all require 60 frames per second or higher to feel responsive. Forcing a 4K output at 30Hz means the dongle is not doing any processing anyway. It is passing the signal through with a 4:2:0 subsampling conversion, which reduces colour detail. The HDMI handshake between the dongle and the screen must also negotiate EDID and HDCP, and this negotiation adds a fixed minimum time to every signal change. If the screen does not recognise the dongle's EDID immediately, the picture blinks black for several seconds. This is a known failure mode. It is why some users report the mClassic causing a black screen every few minutes; the handshake loop re-negotiates continuously because the dongle's EDID says 1440p but the screen wants 4K, and neither side wants to concede.

Who Should Use the mClassic and Who Should Not

The Retro Gamer: A Genuine Use Case

The mClassic suits one type of user: the retro enthusiast with a 720p or 1080p source that cannot be improved by any other means. If you own a PlayStation 3, an Xbox 360, a Nintendo Switch in docked mode, or an original PlayStation 3, the dongle provides a mild but genuine improvement in edge smoothness on 3D titles. It is plug-and-play, consumes no extra power beyond the HDMI port, and adds only 1 to 2 milliseconds of latency, which is imperceptible. It is a reasonable purchase for that use case. It will not ruin the image the way a cheap converter from Sham Shui Po will, because that converter treats 240p as 480i and discards half the vertical resolution.

The Modern Gamer: Leave It in the Box

It does not suit the modern gamer with a PS5 or Xbox Series X. For that user, the console's built-in scaler is already superior, and the dongle's spatial processing cannot match the temporal upscaling of FSR or PSSR. The failure case is a gamer who buys the dongle expecting a sharper 4K image and gets a softer one, or worse, a black screen from an HDMI handshake loop. The one scenario where the mClassic might be worth trying is a PS5 playing a PS4 title that renders at 1080p. Even then, the improvement is marginal and often introduces ringing halos. The recommended path for a modern gamer is to leave the console at its native 4K output, enable VRR if the screen supports it, and address motion blur on the screen itself. A screen with 120Hz BFI eliminates sample-and-hold blur without visible flicker, and that does more for image clarity than any external scaler ever will.

Comparing the mClassic to the Alternatives You Might Actually Buy

The Scaler Landscape

When assessing the mClassic against its competition, the first thing to understand is that it sits in a different price and capability tier than the devices most retro gamers actually buy. The OSSC is a line multiplier with no framebuffer, which means it adds microseconds of latency, not milliseconds. It requires component or SCART input and will not accept HDMI from a PS5. The RetroTINK 5X outputs up to 1440p, adds a framebuffer for motion-adaptive deinterlacing, and includes composite input, but it costs several times more than the mClassic and is not powered by the HDMI port. The RetroTINK 4K is the ceiling of the market, using a field-programmable gate array to achieve sub-millisecond scaling with HDR CRT emulation and black frame insertion. It costs more than a used console. The GBS-Control is a community-built alternative that turns a cheap VGA scaler into a competent lag-free upscaler, but it requires soldering and configuration.

Where the mClassic Fits

The mClassic is the only option in its price range that is truly plug-and-play. It is also the only one that cannot accept a 4K signal. Every other modern scaler handles 4K input, even if it only outputs 1440p. The dongle's HDMI version is 1.4b, which is a generation behind, and its maximum output resolution at 60Hz is 1440p, not 4K. If your screen is 4K and you feed the dongle a 1080p signal, the TV's scaler must handle the final upscale to the panel's native resolution, and that scaler adds lag. The power draw of 1.5W is low, but the Micro-USB connection is a point of failure; an under-spec HDMI port on a TV or a worn cable can cause signal dropouts. The HDMI handshake with newer TVs, which have their own EDID quirks, can also cause issues that require a firmware update from Marseille. No firmware update can change the hardware's bandwidth limit.

Latency, Motion Blur, and What Actually Makes a Modern Image Look Good

The Temporal Advantage

The reason the mClassic fails to impress on current-gen consoles is not a flaw in its design. It is a fundamental mismatch between its single-frame spatial processing and the temporal, motion-vector-driven methods the consoles use. The PS5's PSSR motion vector approach and the Xbox's FSR upscaling both reconstruct detail from multiple frames, which means they can recover information that is not present in any single frame. The dongle's context-adaptive anti-aliasing, by contrast, analyses one frame at a time and estimates edges. This is why a temporal solution produces a stable image on moving objects, while the mClassic produces a shimmering edge that flickers. The difference is most visible on fast-moving games, where the dongle's smoothing creates a ghosting effect that was not present in the original render.

Fix the Screen, Not the Signal

For the modern gamer, the real bottleneck is display-side. A 4K OLED with VRR support will display a native 4K signal at 120Hz with no added lag, but only if the console is set to output that signal natively. Inserting an mClassic forces the console down to 1080p, disables VRR, and adds a scaling step that the TV's processor handles poorly. The result is a softer image with more input lag, the exact opposite of what a competitive gamer wants. The research is clear: the dongle adds 1 to 2 milliseconds of processing latency, but the TV's scaler adds 10 to 40 milliseconds depending on the panel. The built-in scaler on the PS5 and Xbox Series X adds no measurable lag beyond the display chain. Invest in a screen with low input lag and a 120Hz BFI mode, not an external dongle that was designed for a different era of gaming.

The Verdict on the mClassic for Current-Gen Consoles

For a PlayStation 5 or Xbox Series X owner, the mClassic is a solution in search of a problem. The consoles' built-in scalers are superior. The dongle cannot accept a 4K signal. The only way to make it work is to force the console down to 1080p, which defeats the purpose of owning a 4K console. The unit's 1440p output is a marketing claim that does not survive contact with a 4K screen, because the active image area is 1080p upscaled. Independent testing with a Time Sleuth confirms the latency is negligible, but the image quality loss from downscaling and re-upscaling is not. The dongle is not a failure. It is a tool, but it is a tool for a different job.

The mClassic suits the retro gamer who wants to play a PlayStation 3, Xbox 360, or Nintendo Switch docked on a modern screen and needs a simple, low-cost way to reduce aliasing. It suits the Hong Kong apartment dweller with a Super Famicom who needs a clean image on a 4K OLED and cannot justify the cost of a RetroTINK 4K. It does not suit the modern gamer who wants better anti-aliasing on a PS5 or Xbox Series X, because that gamer needs display-side motion blur guides and VRR setup, not scanline generators.

mClassic vs PlayStation 5 and Xbox Series X Built-in Upscaling for Current-Gen Consoles