How to Capture Handheld Consoles, Analogue Pocket Dock, and Nintendo Switch for Retro Streams

To capture handheld consoles, you are chaining an HDMI output from a dock or console into a capture card. The entire game is won or lost in the signal handshake before the video ever reaches your editing timeline. The Analogue Pocket Dock, MiSTer FPGA, and Nintendo Switch all output over HDMI, but each one lies about its signal in a different way. A capture card that swallows the lie records garbage. Know the exact chain for each: what setting to enable, what cable to use, and what to do when the screen blinks black instead of showing your gameplay. The failure cases are real. An EDID mismatch with the OSSC Pro's HDMI input has ended more than one stream.

Fix The Scaling Before You Record

The Analogue Pocket Dock outputs a claimed 1080p signal over HDMI, at whatever resolution the core renders internally. The trap is that the default scaling is not integer. A Game Boy image stretched to 1080p produces uneven pixel widths. On a capture, that reads as shimmering horizontal lines and wobbling sprites. Fix it in the Dock's video menu. Enable integer scaling, which forces a clean multiplication for each core, centred with black borders. The capture card records the borders as part of the frame. That is correct. Integer scaling is the only way to get a stable, artifact-free image from the Pocket's FPGA cores.

Build The Capture Chain

Run the Dock's HDMI out directly into an Elgato HD60 S or an AVerMedia card. Do not loop through a scaler unless you need to add scanlines. The Pocket's output is already digital and the HD60 S accepts it at 1080p60. Set the capture card's EDID to expect 1080p, not 'auto'. The Dock can occasionally handshake at 720p if the display negotiates first. On the HD60 S, open the Elgato software, go to device settings, and force the resolution. The result is a 1080p60 capture with 4:2:0 chroma subsampling. That is fine for gameplay footage. No one is reading fine text in a shmup.

Test With The GB Interface Core

If you are using the GB Interface core for original Game Boy and Game Boy Color games, the same integer scaling rule applies. The GB Interface outputs at the core's native resolution. Without integer scaling, the pixels smear. Load the 240p test suite from a flash cart, play the scrolling pattern, and check the capture for jagged horizontal lines. If you see them, the Dock is not integer scaling. Re-enable it. This is a configuration default, not a hardware fault. The Dock is capable of a perfect capture, but only after you flip that one menu toggle.

Choose Your Output Path

The MiSTer FPGA is a different animal. The DE10-Nano board outputs native video over a VGA-style connector or a direct HDMI add-on. Its capture chain depends entirely on which output you chose. The cleanest path for streaming is the MiSTer's direct video over HDMI. It bypasses the analogue converter and hands the capture card a digital signal. If you built your MiSTer with the analogue I/O board, you are stuck with VGA. You need an OSSC Pro or a RetroTINK 5X-Pro in between to convert that to HDMI. The OSSC Pro accepts the MiSTer's native 240p over VGA, line-doubles it to 480p, and outputs that to the capture card. The lag is microseconds. The OSSC Pro has no framebuffer in this mode. The capture card sees a 480p signal, and you record that, not 1080p.

Dial In The Direct HDMI Settings

For a direct HDMI MiSTer, the signal is already digital. Feed it straight into an Elgato HD60 X at up to 1440p. The MiSTer's HDMI output supports integer scaling per core. Enable it in the MiSTer.ini file with the 'video_info' and 'fb_terminal' settings. The 240p test suite, run from the MiSTer's menu core, shows you the exact pixel spacing. If the capture shows uneven lines, the core is not scaling to a clean multiple. Adjust the core's aspect ratio settings. The MiSTer's HDMI output respects HDCP if a game uses it, which almost none do. But the capture card will negotiate a white screen if HDCP is active. Disable it in the MiSTer core settings or use a card that strips it. The Elgato HD60 S does not.

Colour Fidelity And The Bottleneck

On the Shmups Forum, the collective wisdom is that the MiSTer's HDMI output is the reference for 1080p capture. It avoids the analogue conversion entirely. If you see chroma subsampling artifacts, colour bleeding on red text, check the MiSTer's video mode. It defaults to 4:2:2 for some cores. Force 4:4:4 in the video_mode setting if your capture card supports it. The HD60 S only accepts 4:2:0, so you are stuck with that. The HD60 X handles 4:4:4. Choose your card based on what you are willing to lose. The MiSTer's output is clean. The card's subsampling is the bottleneck.

The Basic Capture Chain

The Nintendo Switch, whether the standard HAC-001 or the OLED HEG-001, outputs a maximum of 1080p60 over HDMI 1.4b. It is capped there for all retro titles running through the Switch Online service or emulation. The Switch does not apply HDCP to gameplay footage, only to the Netflix and YouTube apps. A capture card records the game feed without a handshake failure. Plug the Switch's HDMI out directly into an Elgato HD60 S, set the capture to 1080p60, and you are done. The Switch's chroma subsampling is RGB Limited (16-235) or YCbCr 4:4:4. The HD60 S downsamples that to 4:2:0 for recording. The result is a slightly crushed black level if you do not adjust your OBS colour range to match. Set the HD60 S to 'Partial' and the OBS source to 'Partial' as well.

Solve The Lag Problem

Capture latency on the Switch with an Elgato HD60 X over USB 3.0 is 2 to 3 frames at 60 Hz, which is 33 to 50 milliseconds. That is too slow for rhythm games where you are playing on the same screen. For those, split the signal. Run the Switch's HDMI into a powered splitter, one output to your TV, the other to the capture card. The splitter adds no perceptible lag to the TV path. The capture card's delay becomes irrelevant because you are not playing through the preview. If you are using an AVerMedia GC553G2, the latency is the same 2 to 3 frames. The splitter is not optional for a lag-free play experience. Do not trust the mClassic to fix this. The Marseille Inc. mClassic upscaler adds about half a frame of lag and can introduce a 1440p signal that the HD60 S will reject. Leave it out of the Switch capture chain unless you are feeding it into a RetroTINK 4K first.

Scaling Beyond 1080p

For Switch retro titles, the 1080p cap means you cannot get integer scaling to 4K without an external scaler. The RetroTINK 4K accepts the Switch's 1080p60 input and upscales to 2160p60 with proper integer scaling. The OSSC Pro also accepts the Switch's HDMI input and line-multiplies to 1080p or 1440p, but it does not add integer scaling because the Switch's output is already a fixed resolution. Your choice is simple. Record at the Switch's native 1080p and accept the pixel grid, or add a RetroTINK 4K to the chain and pay for the privilege of slightly larger pixels. Most streamers skip the scaler and record at 1080p. The capture card's 4:2:0 subsampling blurs the difference anyway.

The Game Boy Interface (GB Interface) is a homebrew replacement for the Game Boy Player on the GameCube. It outputs a clean digital signal that is a nightmare for capture. When you run GB Interface via Swiss, it can output 240p over component or RGB. The upscaler you choose after that determines the capture quality. The RetroTINK 5X-Pro accepts the GB Interface's 240p over component, applies integer scaling to 1080p, and adds the CRT simulation filters that make Game Boy games look like a PVM-20L5. The capture card records the 1080p output, a clean scale with no deinterlacing artifacts because the signal is progressive.

The OSSC Pro handles GB Interface over RGB SCART, line-doubling 240p to 480p, then to 960p, and finally to 1920p if you want a 1080p output. The lag is zero in line-doubling mode. The capture card sees the final resolution. If you are using an Elgato HD60 S, that is 1080p60. The OSSC Pro's output is clean. The trap with GB Interface is that it defaults to a 60 fps signal. Some games run at 50 fps on PAL consoles. The scaler must handle the frame rate conversion. The RetroTINK 5X-Pro does this with motion-adaptive deinterlacing for interlaced content. For progressive 240p, it simply scales. The Shmups Forum recommends the RetroTINK 5X for this case. The OSSC Pro's line-doubling does not add a framebuffer, so a 50 fps game on a 60 fps capture will stutter.

For the capture itself, set the GB Interface's output to 240p, not 480i. Let the upscaler handle it. If the capture card records a 1080i file, it is an EDID handshake issue. The card is misreading the scaler's output. Force the Elgato HD60 S to 1080p60 in its settings. The file will be progressive. The GB Interface is a niche choice. It is the only way to get a pixel-perfect Game Boy capture without a modded console. The 240p test suite confirms the signal chain is clean before you start recording.

The HDMI handshake is where every capture chain falls apart. EDID (Extended Display Identification Data) is the metadata a display sends back to the source, telling it what resolutions and refresh rates it supports. When a capture card sits between the source and the display, it impersonates the display. If its EDID is wrong, the source outputs a signal the capture card cannot record. On the Switch, the console sends 1080p60. The Elgato HD60 S reports that it accepts 1080p60. The handshake succeeds in milliseconds. Insert an OSSC Pro's HDMI input into the chain, and the OSSC Pro's EDID may negotiate a 1440p signal from the Switch. The HD60 S cannot capture that. The result is a black screen or a blinking loop. The Switch, OSSC Pro, and capture card keep re-negotiating. The screen goes black every few seconds.

To fix this, force the EDID at the OSSC Pro. Go into its HDMI input settings and set the input to 1080p, not auto. The OSSC Pro's firmware, developed with input from the Shmups Forum, has a per-input EDID override. Set it to '1080p60' and the Switch outputs 1080p. The capture card sees a clean signal. HDCP is the other half. The Switch does not apply HDCP to game footage, but it does for streaming apps. If you try to capture the Switch's Netflix app, the HD60 S records a black screen with a green bar. That is HDCP protection. The Elgato HD60 S does not strip HDCP. The AVerMedia GC553G2 does not either. Your only option is to disable HDCP on the source, which you cannot do on the Switch. Avoid the app entirely.

The failure case hits mid-stream. The screen starts blinking. You have 30 seconds to fix it before your viewers leave. The cause is the EDID negotiation, not the cable. Unplug the HDMI cable from the capture card, wait five seconds, and plug it back in. If the blinking continues, power-cycle the scaler or the splitter. The HDMI handshake loop has corrupted the EDID in the chain. This is not a driver issue or a firmware bug. It is the HDMI specification doing exactly what it is designed to do: re-negotiate when the signal does not match the EDID. The RetroTINK 5X-Pro has a setting to lock the EDID to a fixed profile. That prevents the loop. The OSSC Pro has a similar setting. Use it before you start streaming, not after.

Match The Resolutions Exactly

When you capture from a RetroTINK 5X-Pro, the scaler's output resolution and the capture card's input resolution must match exactly. The RetroTINK 5X-Pro outputs up to 1440p. The Elgato HD60 S only accepts 1080p. Set the RetroTINK 5X-Pro to 1080p. Set the capture card to 1080p60. The RetroTINK's menu has an 'output resolution' setting. Choose 1080p, not 'native' or 'auto'. The same applies to the OSSC Pro, which outputs up to 1440p over HDMI. Force the OSSC Pro to 1080p in its output settings. The capture card records a clean signal. Run the 240p test suite through the scaler. Check the capture preview for a full stable image.

Chroma Subsampling And Audio

Chroma subsampling is the hidden variable. The RetroTINK 5X-Pro outputs 4:4:4, a full-resolution colour signal. The Elgato HD60 S captures 4:2:0, which samples colour at half the resolution. The result is a slight softening of colour detail. On most games, you will not see it. If you capture from a MiSTer or an Analogue Pocket, the signal is already 4:4:4. The capture card's 4:2:0 conversion is the only loss. The AVerMedia Live Gamer Ultra 2.1 captures 4:2:0 as well. There is no way around it without a capture card that supports 4:4:4, like the Elgato 4K X. For audio, the scalers embed the audio into the HDMI signal. The capture card records it as part of the video file. If you use the OSSC Pro's analogue audio input, the scaler embeds that into HDMI. Set the capture card's audio input to 'HDMI' in OBS. Do not use the analogue audio ports on the capture card. They go through a separate analogue-to-digital converter that adds noise and delay. The HDMI path is direct. The audio will be in sync with the video.

The 240p-as-480i Misdetection

The most common failure is the 240p-as-480i misdetection. A scaler or a capture card sees a 240p signal and treats it as 480i. The deinterlacing algorithm discards half the vertical resolution and adds combing artifacts. The Elgato HD60 S is a video device, not a game scaler. It does this to 240p game footage. Never feed 240p directly into a capture card. Always use a scaler like the RetroTINK 5X-Pro or OSSC Pro, which output 480p or higher. If you are using a generic HDMI converter from Sham Shui Po, the one that costs 50 HKD, it will treat 240p as 480i. Your capture will look like a striped mess. The chip is designed for DVD players, not game consoles. Throw it away.

The HDMI Handshake Loop

The second failure is the HDMI handshake loop. The trigger is often a capture card with a flaky EDID, like the older Elgato HD60. The card reports a 1080i EDID. The scaler outputs 1080p. The negotiation fails. The screen blinks black every few seconds. Fix it by updating the capture card's firmware, which changes the EDID. Elgato has published a table of supported EDIDs for each card model. Check that. If the firmware is up to date and the blinking continues, the scaler's EDID override is your only option.

Dropped Frames

The third failure is the capture card dropping frames. This is a USB bandwidth issue, not a capture fault. The Elgato HD60 S uses USB 3.0. Plug it into a USB 2.0 port or a hub, and it will drop frames. Use a dedicated USB 3.0 port on your PC. Disable the camera preview in OBS, which can steal bandwidth. The AVerMedia GC553G2 has the same requirement. The Shmups Forum has a sticky thread on this. The card's USB interface matters more than the card's chipset. If you are on a laptop with limited USB ports, use a powered USB 3.0 hub, not the one built into your monitor.

Why does my Switch capture show a black screen on Netflix?

The Switch applies HDCP to streaming apps but not to gameplay. The Elgato HD60 S does not strip HDCP, so it records a black screen. You cannot disable HDCP on the Switch. You cannot capture those apps.

Can I use a capture card with the Analogue Pocket Dock without a scaler?

Yes. The Dock outputs 1080p over HDMI, and the Elgato HD60 S accepts that directly. Enable integer scaling in the Dock's menu first to avoid uneven pixel sizes.

What is the best upscaler for capturing a MiSTer FPGA?

The OSSC Pro is the reference for MiSTer. It accepts the native VGA output and line-doubles to 1080p without a framebuffer. The RetroTINK 5X-Pro is better if you need composite or S-Video inputs.

Why does my capture card record a 1080i file when I feed it 1080p?

This is an EDID handshake issue. The capture card is misreading the scaler's output. Force the scaler to output 1080p and force the capture card to accept 1080p60.

How much lag does a capture card add to my play display?

Elgato HD60 X adds 2 to 3 frames at 60 Hz, which is 33 to 50 ms. Split the signal to a TV and capture separately to avoid playing through the preview.

Can I use the mClassic to upscale my Switch for capture?

The mClassic can output 1440p. Most capture cards only accept 1080p. Use it only if you have a RetroTINK 4K in the chain to accept the 1440p signal.

What is the 240p test suite and why do I need it?

It is a homebrew ROM that tests lag, geometry, and colour accuracy on your display and capture chain. Run it before recording to verify the signal is clean.

This subject suits the retro gaming hobbyist who already owns a MiSTer FPGA or an Analogue Pocket and wants to share their gameplay on Twitch or YouTube. It suits the capture enthusiast who has a RetroTINK 5X-Pro and wants to understand the EDID handshake. It suits the competitive shmup player who needs zero lag on their play display and is willing to split the signal and capture separately.

It does not suit the Switch owner who just wants to record a few rounds of Mario Kart without adjusting a single setting. Plug in an Elgato HD60 S and use the default software. It does not suit the person who wants to buy a pre-modded console as a plug-and-play gift. This assumes you already have the hardware and are willing to navigate menus. It does not suit anyone looking for driver-level integer scaling on a PC emulator. That is the domain of dgVoodoo2 and DXVK, not the HDMI capture chain.