Comparing the mClassic and mCable: Marseille’s Generational Differences in HDMI Processing

If you are staring at two black Marseille products and cannot tell which one fixes your retro console’s blurry image, the answer is the dongle with the switch on it. This comparison comes down to one physical difference and one processing generation: the mClassic is a short HDMI passthrough dongle with a three-position retro mode switch, while the mCable is a full-length HDMI cable with the same company’s processor fused inline. The mClassic, released in 2019, uses a newer ASIC that outputs a 2560×1440 frame at 60 Hz and 3840×2160 at 30 Hz. The mCable Gaming Edition, from 2017, tops out at 1920×1080. Both apply Marseille’s proprietary context-adaptive anti-aliasing, but the dongle’s dedicated retro mode switch adds a low-lag upscale path for 240p and 480p sources that the cable cannot match. The dongle draws all its power from the HDMI port itself. That single fact explains most of the compatibility failures you will read about online.

This is not about image quality alone. It is about which device fits your signal chain. The cable sits between a console and a TV like any other cable, needing no external power because it uses the HDMI port’s 5V line. The dongle does the same, but because it is compact, it is more sensitive to under-spec ports on cheap switches or older displays. When the port cannot supply enough current, you get signal dropouts or a blank screen. The retro mode switch cycles between three states: Blue LED for upscaling plus anti-aliasing, Green LED for anti-aliasing only, and Off for pure passthrough. The cable has the same three LED states, but its maximum output is 1080p. You trade away the 1440p headroom the dongle offers for the convenience of a cable you cannot lose.

Marseille Inc. publishes no official latency figure beyond a vague “<1 ms” claim on both products. Independent testing with a Time Sleuth latency test by RetroRGB’s Bob Neal measured the dongle at sub-1 ms at 480p, 720p, and 1080p in 2019, which matches the manufacturer’s number. The cable’s delay was never independently measured to the same standard, so treat the “<1 ms” as an approximation and check RetroRGB’s archive for the real figure. What the marketing materials do not tell you is that the 1440p output is not a native 1440p render. It is a 1080p active image area upscaled to fill a 1440p frame. This distinction matters when someone claims the device “makes your Switch 4K.” It does not. It upscales a 1080p signal to 1440p, and the anti-aliasing effect is visible on a 4K TV, but the source resolution never changes.

For the retro gamer, the ace is the retro mode switch itself. Feed it a 240p signal from a NES, SNES, or Genesis over composite or component, and the context-adaptive algorithm applies post-process AA and a mild upscale, outputting 1440p at 60 Hz. The cable has no such mode. It passes 240p through to the TV, which then deinterlaces it as 480i, destroying the image. If you own a PS2 or original Xbox and use a GCVideo or OSSC upstream, the dongle accepts the line-doubled 480p signal and upscales it cleanly, as RetroRGB confirmed in 2019. The cable, fed the same 480p signal, upscales to 1080p with visible AA, but you leave vertical resolution on the table. For modern consoles, the 1440p output on a Switch docked at 720p or 1080p is a genuine improvement, as Digital Foundry and My Life in Gaming both verified in 2019 and 2020. The cable’s 1080p cap means a PS5 or Xbox Series X user gains nothing but a slight sharpening filter.

When The Dongle Fails

Here is the failure case. You have the dongle, a Switch dock, and a TV with only one HDMI input that also needs to carry a soundbar. You plug the device into a cheap HDMI switch, and the picture flickers or drops out entirely. That is the under-spec port problem: the unit draws current from the HDMI 5V line, and budget switches often starve that line. The fix is to power it with a USB cable? No, it has no USB port. You must plug it directly into the TV or use a powered HDMI switch. If it is 1am and you have only a passive switch, your only move is to bypass the processor entirely and live with the TV’s internal scaler, which adds 10-15 ms of lag and softens the image. Do not buy a second unit to fix it. Buy a powered switch with a wall wart and move on.

The firmware is not user-updatable. It runs a fixed ASIC, so what shipped in 2019 is what you get forever. The cable has the same limitation. That means the 1440p output and retro mode switch are locked in. Any future TV firmware update that breaks the HDMI handshake will require Marseille to release a new hardware revision, not a software patch. The HDMI handshake itself is a mandatory part of the spec. Every scaler must negotiate EDID and HDCP with the display. The dongle supports HDCP 1.4, not 2.2. If your TV enforces HDCP 2.2 on all ports, the device will refuse to handshake and you will see a black screen. The cable, being HDMI 1.4b, has the same limitation. Test your TV’s EDID behavior before you commit to either. No amount of processing quality compensates for a handshake failure.

If you are on a budget and already own an OSSC or RetroTINK 5X, the dongle pairs well. Those scalers output a clean 480p, 720p, or 1080p signal that the unit upscales to 1440p. The OSSC’s line-doubled 480p, tested by RetroRGB in 2019, works flawlessly. The RetroTINK 5X’s 1080p output, tested in 2021, also works. But do not feed it a 4K signal from a modern console. It passes 4K through with no processing at all, which is a useless passthrough. The cable, limited to 1080p, cannot even accept a 1440p or 4K input. If you own a PS5, you are plugging the cable into a 1080p source and letting it apply AA only. That is a waste of a cable. The dongle is the better buy for almost everyone, but only if your signal chain can deliver a clean sub-1080p signal to it. If you are still playing on a stock SNES with composite cables, the retro mode switch is the difference between a playable image and a blurry mess. The cable will not save you.

My Life in Gaming’s 2019 test with a PS2 via HDMI adapter noted that deinterlacing must happen upstream. The dongle does not deinterlace. The cable has the same limitation. Feed either device a 480i signal, and you get a 480i upscale, not a cleaned-up 480p image. The 4:3 content handling also forces a 16:9 stretch on some displays, with no 4:3 passthrough option, a complaint My Life in Gaming documented in 2019. Digital Foundry’s 2020 tests on Xbox 360 and PS3 at 720p confirmed the AA effect and slight sharpening, but they also noted the 1440p output is not a replacement for a proper scaler. For the money, the dongle at its current street price is a reasonable stopgap. The cable’s 1080p cap makes it a hard pass for anyone with a modern console. The best use case for the cable is a 1080p TV with a Wii U or Switch docked, where Digital Foundry confirmed the AA effect in 2017. That is a narrow window, and the dongle covers it better with its 1440p output.

The retro mode switch is a three-position slider on the dongle’s edge. It is the single feature that separates this device from the cable. Position one, Blue LED, applies the full context-adaptive anti-aliasing algorithm plus the upscale to 1440p. Position two, Green LED, applies anti-aliasing only, leaving the resolution at the source’s native output. Position three, Off, is a pure passthrough. For a 240p source like a NES, the Blue mode is the one you want. It treats the 240p signal as a game signal, not as 480i video, and outputs a clean 1440p frame with visible AA smoothing. The cable has no such switch. Its Blue mode always upscales to 1080p, and its Green mode applies AA only, but it cannot distinguish 240p from 480i. A NES through the cable looks like a deinterlaced mess.

The 1440p output claim from Marseille is real but narrow. The dongle outputs a 1440p frame at 60 Hz, but the active image area is 1080p, upscaled to fill the 1440p frame. Independent testing by RetroRGB in 2019 confirmed the 1440p output works with the OSSC and RetroTINK 5X. My Life in Gaming saw the AA effect on a Switch docked at 720p and 1080p, a Wii at 480p, and a GameCube at 480p via GCVideo. Digital Foundry’s 2020 tests on Xbox 360 and PS3 at 720p showed the same. But the device cannot create detail that was never captured. It is a post-process AA filter that smooths jagged edges, not a magic resolution booster. Feed it a 720p signal, and you get a 1440p output with visible AA, but the underlying resolution is still 720p. The same applies to the cable at 1080p. Both products are honest about this in their spec sheets, but marketing copy often obscures the distinction.

The Power Problem

The HDMI port power requirement is the dongle’s Achilles’ heel. It draws all its current from the HDMI 5V line. On under-spec ports, found on cheap switches or older TVs, the signal drops out intermittently. RetroRGB’s testing in 2019 noted this failure mode explicitly. My Life in Gaming encountered it when pairing the unit with a passive switch. The cable has the same power draw, but its longer form factor means the processor sits closer to the console, reducing the chance of a marginal port. If you experience dropouts with either device, the fix is a powered HDMI switch or a direct connection to the TV. Do not waste time on a different cable. The problem is the port’s current delivery, not the cable’s shielding.

The mCable Gaming Edition, model MC-GE-001, launched in 2017. It is a full-length HDMI cable with the Marseille processor embedded in the middle, and it outputs a maximum of 1920×1080 at 60 Hz. Its input resolution range is 480p to 1080p. It handles 720p sources from a Wii U or Switch docked with visible AA, as Digital Foundry confirmed in 2017. The cable supports HDMI 1.4b and HDCP 1.4, which means it will not handshake with newer HDCP 2.2-only displays. The anti-aliasing method is the same proprietary contextual post-process AA as the dongle, but Marseille claims the dongle’s newer ASIC delivers a stronger AA effect. RetroRGB’s side-by-side testing in 2019 did not fully quantify that claim. Treat it as an approximation and check RetroRGB’s 2019 review for the side-by-side comparison.

The cable’s latency is listed as “<1 ms” by Marseille, but no independent Time Sleuth test measured it to the same standard as the dongle’s sub-1 ms result. My Life in Gaming’s 2017 tests showed the AA effect visible on 480p, 720p, and 1080p sources, but they did not publish a latency figure. Digital Foundry’s 2017 tests on a Wii U at 720p confirmed the 1080p upscale and AA smoothing. Again, no latency number. The 1080p cap is the cable’s fatal flaw in 2025. It cannot output 1440p or 4K. It is useless for a PS5 or Xbox Series X user who wants to upscale a 720p or 1080p game. The fixed ASIC means no firmware updates. What you bought in 2017 is what you get today. If you find a new-old-stock unit at a steep discount, it is a decent 1080p AA solution for a Wii U or Switch, but only if you accept the 1080p ceiling.

Input lag is where the comparison gets concrete. Marseille claims “<1 ms” of added latency for both devices. The only independent measurement comes from RetroRGB’s Bob Neal, who used a Time Sleuth latency test in 2019 and measured the dongle at sub-1 ms for 480p, 720p, and 1080p inputs. That is real and reproducible. The cable was never measured with the same rigor. My Life in Gaming’s 2017 tests focused on image quality, not latency. So the dongle’s sub-1 ms figure is verified. The cable’s “<1 ms” is an approximation. Do not trust either claim without checking RetroRGB’s 2019 article, which publishes the complete methodology and raw results. The context-adaptive algorithm introduces a small processing delay from its analysis window, but it is so small that no human can perceive it. The Time Sleuth confirms it is not a marketing fantasy.

The practical implication is that both devices are effectively lagless. The dongle’s 1440p output adds a second layer of scaling on your TV, which can add 10-15 ms of display lag if you do not enable Game Mode. The cable, limited to 1080p, avoids that extra scaling on a 1080p TV but forces it on a 4K TV, where the set’s internal scaler adds 30-40 ms. The dongle’s 1440p output on a 4K TV is closer to the native resolution, so the TV’s scaler does less work. That is a real advantage. Neither device can fix a TV that adds lag in its own processing. Game Mode is mandatory. If you are using a modern OLED, the 1440p output combined with Game Mode is the best you can get without a dedicated scaler. The cable’s 1080p cap means you are relying on the TV’s scaler for any resolution above 1080p. That is a losing game.

The dongle is a context-adaptive anti-aliasing processor. It analyzes each frame’s content and applies post-process AA selectively, smoothing edges without blurring the entire image. This is different from a scaler like the OSSC, which is a line multiplier with no framebuffer, or the RetroTINK 5X, which uses a framebuffer and can output 1440p or 4K. The algorithm is proprietary to Marseille Inc. and runs on a fixed ASIC with no user-updatable firmware. The cable uses the same algorithm but on an older ASIC, which is why Marseille claims the dongle has a stronger AA effect. RetroRGB’s 2019 tests showed the AA effect is visible on a Switch at 720p and 1080p docked, a Wii at 480p, a GameCube at 480p via GCVideo, and a Dreamcast at 480p via HDMI adapter. Digital Foundry’s 2020 tests on Xbox 360 and PS3 at 720p confirmed the same, with a slight sharpening filter that some users like and others find artificial.

The processing is not a replacement for a proper scaler like the RetroTINK 5X or OSSC Pro. It cannot deinterlace 480i. That must happen upstream, as My Life in Gaming noted in 2019. It cannot handle 4K input. It passes 4K through with no processing at all, confirmed by RetroRGB in 2019. It forces a 16:9 aspect ratio on some displays, with no 4:3 passthrough option, a complaint documented by My Life in Gaming. The cable has the same limitations, but its 1080p cap means it cannot even output 1440p. The dongle’s advantage is real but narrow. The context-adaptive algorithm is the star, not the upscale. Feed the dongle a clean 480p signal from an OSSC, and you get a 1440p output with visible AA. That is a significant improvement over the cable’s 1080p cap. Feed it a blurry 480i signal, and you get a blurry 1440p output. The unit does not perform motion-adaptive deinterlacing.

Specification	mClassic	mCable Gaming Edition
Manufacturer	Marseille Inc.	Marseille Inc.
Form factor	HDMI dongle (no cable)	Inline HDMI cable with integrated processor
Input resolution	480p to 1080p	480p to 1080p
Output (60 Hz)	2560×1440 (1440p)	1920×1080 (1080p)
Output (30 Hz and below)	3840×2160 (4K)	1920×1080 (1080p)
4K input behavior	Passthrough, no processing	Not supported (1080p max input)
Processing modes	Blue (upscale + AA), Green (AA only), Off (passthrough)	Blue (upscale + AA), Green (AA only), Off (passthrough)
Retro mode switch	Yes (three-position slider)	No
Anti-aliasing method	Marseille contextual post-process AA	Marseille contextual post-process AA
AA intensity	Stronger (newer ASIC, manufacturer claim)	Weaker (older ASIC, manufacturer claim)
Latency (manufacturer)	<1 ms	<1 ms
Latency (independent)	Sub-1 ms (RetroRGB, 2019, Time Sleuth)	Not independently measured
HDMI version	HDMI 1.4b (implied)	HDMI 1.4b
HDCP compliance	HDCP 1.4	HDCP 1.4
Firmware update	No (fixed ASIC)	No (fixed ASIC)

Does the mClassic work with a PS5 or Xbox Series X? No, because those consoles output 4K, and the dongle passes 4K through with no processing. You would need to set the console to 1080p output, which defeats the purpose. The device cannot upscale 4K to anything useful.

Can the mCable fix a blurry NES image? No, the cable lacks a retro mode switch and treats 240p as 480i, so it applies a destructive deinterlace. The dongle’s retro mode switch is the only one of the two that handles 240p correctly. Even then, you need a clean 240p signal from a good source.

Is the mClassic’s 1440p output native? No, it is a 1080p active image area upscaled to fill a 1440p frame. RetroRGB and Digital Foundry confirmed the output works and the AA is visible, but the source resolution never changes. Treat any claim of “4K upscaling” as marketing, not reality.

Why does my mClassic lose signal on a switch? The dongle draws power from the HDMI port’s 5V line. Under-spec ports on cheap switches cannot supply enough current. Use a powered HDMI switch or plug the unit directly into the TV. If the problem persists, test with a different port before buying a new device.

The mClassic’s sub-1 ms latency was measured by RetroRGB’s Time Sleuth test in 2019. The mCable’s “<1 ms” claim was never independently verified. If you are choosing between them, buy the dongle for its verified 1440p output and retro mode switch. Skip the cable unless you find it at a steep discount for a 720p-only Wii U setup.