# I Have a Problem with HDMI Capture #### AKA I am cursed with a blood-red dark tint across all my capture and I cannot figure out why There are gremlins inside my capture setup. I need help. Last month, I wrote a big ol' piece about [[I Have a Problem with Elgato|my lengthy support process with Elgato]] and their 4K X capture card. > Why? Why doesn't this new card have parity with the old one? What is tripping the signal? Is it a flaw on Elgato's part or my own wonky setup? I was not satisfied living in the unknown. Then after the launch of the Nintendo Switch 2, [[Elgato has a Switch 2 Problem|Elgato was having issues]] with the console and [[I Have a Problem with Elgato and Switch 2|so was I]]. > My Elgato HD60 X was not receiving any signal. I swapped in my 4K X and it was getting a signal, but it was dark with a blood-red tint. The Switch 2 was set to 4K60. The blood-red tint has come for my entire capture apparatus and I cannot figure out the problem. I have tried multiple HDMI 2.1 cables, HDMI 2.1 capture cards, UBS-C 3.2 Gen 2 cables, consoles, and computers. I have dismantled my entire capture chain to the point of it just being `Console > Card > Computer` and sometimes completing the chain to the TV, if that test requires it. I am getting this effect with [the Switch 2](https://youtube.com/watch?v=z0kpUVgUuRs). <div class=iframe-container> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/z0kpUVgUuRs?si=AKErSMxA67atLF-w" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div> I am getting this effect with the [RetroTINK-4K and a PS2](https://youtube.com/watch?v=7e-7xdkjzZ4). <div class=iframe-container> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/7e-7xdkjzZ4?si=w-AnwUff6l7qT-PL" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div> Here it is with an [AVerMedia GC553262 Live Gamer Ultra 2.1](https://youtube.com/watch?v=ekctkOnmDyA). <div class=iframe-container> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/ekctkOnmDyA?si=s2qyvLJ8ixtGYU-p" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div> It happens with a PS5 Pro; in OBS, in Elgato capture software, and in QuickTime. It happens on a M1 iMac, a M2 Ultra Mac Studio, a 2017 Intel MacBook Pro, and a 2017 Dell Inspiron Windows laptop. ![[250611_Capture Issue_4KX Color Issue in Elgato Software.png]] ![[250617_Capture Issue_PS5 Pro Menu_1.png]] ![[250617_Capture Issue_Switch 2 Red.png]] ![[250618_Intel MacBook Red.png]] ![[250618_Windows OBS AVer Test.png]] It is happening everywhere. Don't worry, [one time](https://youtube.com/watch?v=OGoH22A5q9Q) I got it to let me play *Mario Kart World* in 4K60 with HDR, while capturing a tone mapped 4K60 footage.[^1] The next boot up brought the red back. I still don't know how. It was so many steps ago. <div class=iframe-container> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/OGoH22A5q9Q?si=aCIKfxgPEr77YWuA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div> I need help. I have asked friends with [[How Many HDMI Cables does Try have in his Setup|complicated setups]]. I have asked Google [Gemini](https://g.co/gemini/share/0d1e7ac2bc89)—[twice](https://g.co/gemini/share/19de6cbdcb4c). I've posted in at least one Discord help forum area. I am tapped out, so I am turning to the open web and the power of the Internet. Please help me solve this problem. Here's what I have done. ## The Facts  Let's start with facts; with irrefutable evidence; what I know to be true. Let's start with original capture apparatus diagram and relevant settings throughout that chain. Here is the smaller, streamlined version from my [[I Have a Problem with Elgato]] piece. ![[250325_Capture Setup Canvas.png]] And here is the official, full diagram. ![[250611_Console Wiring Diagram.png]] And now here are the settings inside these drop-down callouts.[^2] > [!PS]- PlayStation 5 Pro Display Settings > - Resolution - 2160p > - Enhance Image Quality for PS4 Games - On > - VRR - Automatic > - Apply to Unsupported Games - On > - 120 Hz Output - Automatic > - ALLM - Automatic > - Video Transfer Rate - -1[^3] > - HDR - Always On[^4] > - Deep Color Output - Automatic > - RGB Range - Automatic > [!status]- Monoprice Blackbird HDMI 2.1 Splitter EDID > I *thought* the DIP switches were set to "000" which is basically the full bandwidth, but I feel like I recall being surprised they were set to "111" which is "Copy the EDID of the display connected to OUT 1." I realize knowing exactly which setting was chose on this piece of gear would be *far* more helpful than guessing. Here's the [manual](https://downloads.monoprice.com/files/manuals/44086_Manual_241217.pdf) for reference. > [!Kiefer]- RT4K settings > I tested the issue with my PS2, so I was using the latest Wobbling Pixels PS2 Profile over component. It was outputting 4K60 SDR footage over HDMI 2.0. > [!game]- Nintendo Switch 2 Display Settings > - HDR Output - On > - Resolution - Automatic > - RGB Range - Automatic > - Screen Burn-In Reduction - On > - Match TV Power State - Off > - 120 Hz Output - On > - Auto Low-Latency Mode (ALLM) - On > - HDR Output - Compatible Software Only > [!art]- Elgato HD60 X Settings > - Firmware Version - 22.04.26 (MCU: 22.04.08) > - Audio Input - HDMI Audio > - HDMI Color Range - Bypass (same as input) > - Input EDID Mode - Merged > - HDR Tonemapping - On > [!art]- Elgato 4K X Settings > I no longer have the 4K X for testing, but these were my settings and I did have the red issue with that card as well. I [[I Have a Problem with Elgato and Switch 2|originally pegged the issue to the card]]. I was wrong. > - Firmware Version - MCU 24.12.10 > - Audio Input - HDMI Audio > - HDMI Color Range - Bypass (same as input) > - Input EDID Mode - Display or Merged (I flip flopped in testing) > - HDR tonemapping - On > [!art]- AVer Live Gamer Ultra 2.1 (GC553262) Settings > - Multichannel - Enable > - HDCP, Video and Audio Source Device - PS4/PS5 (Default) > - HDCP Detection - On > - Automatic VRR - Off > - USB Transmission Speed - 10Gbps > - Fireware Version - 1.0.8.1 (DB2059#1002 / 24.4.16.9 / 1.33) > - HDMI Compatibility > - Monitor Size - 55 inch, W 122 cm, H 68 cm > - HDMI Version - 2.1 (120Hz) > - Extended Resolution In Use > - Prefer Resolution - 3840x2160P@60HZ > - Extended resolution > - 3840x2160P@60HZ > - 2560x1440P@60Hz > - 1920x1080P@120Hz > - 2560x1440P@120HZ > - VRR(Variable Refresh Rate) > [!log]- OBS settings > This callout would be far too long if I listed out every setting. This will just detail the "Video Capture Card" setting for the HDMI 2.1 capture card/s. For my recording settings, I followed this [video](https://youtube.com/watch?v=q_Oxvcx-0_Y) from LAS_Curry to a tee. > > One more thing, I have had this bug for a while where the cards do not show picture unless I open their "Properties" and toggle on then off "Use Preset." This happens every time I open OBS. I know it is not the problem because the red tint appears in other recording software, but still, it irks me. > > - Device - Live Gamer Ultra 2.1-Video > - Resolution - Either 3840x2160 or 2560x1440, depended on recording scenario > - Simple FPS Values - Blank, there is no option under the menu. > - And now there is when I make the window taller? Previously, was blank. Perhaps this is why the image never loaded and I had to toggle the preset use. Real time blogger troubleshooting. ## Dismantling the Apparatus Troubleshooting 101 dictates that you either work backwards from the most recent addition until the problem is gone or start from scratch and build back up until the problem is introduced. This issue started when I integrated the Nintendo Switch 2 into my set-up, so I assumed it was the culprit. I know I quoted part of [[Elgato has a Switch 2 Problem|this]] at the top, but here it is again, for context. > When I went to boot up *Mario Kart World*, I noticed that the recording gear was not receiving a signal anymore. I double checked all the cables and switches. I tested the PS5 Pro; that worked fine. My Elgato HD60 X was not receiving any signal. I swapped in my 4K X and it was getting a signal, but it was dark with a blood-red tint. The Switch 2 was set to 4K60. Right in that blog post, you can see the inconsistency of the issue at the start. > Can I update myself before I even press "publish?" I just walked out to my office to get a screenshot of the blood-red capture. The 4K X picture came through clean...My HD60 X still is getting no signal...Update 6/13/25: The blood moon capture returned." It was maddening from the get go. So I broke the entire HDMI chain down. I unplugged everything and made a straight forward, as intended chain of `Console > Card > TV & Computer`. My first test of this was the PS5 Pro to the AVer card to my iMac and LG C1. The test showed crystal clear signal. Next, I reintroduced my [Monoprice Blackbird HDMI 2.1 splitter](https://amzn.to/44wnK6R) because my original vision was to integrate the Switch 2 into that device as well and I wanted to rule it out. The chain was now `PS5 Pro > Blackbird Splitter > Live Gamer Ultra 2.1 > LG C1 & iMac` . That test also produced clean signal. Then I plugged in the Nintendo Switch 2 Dock, sans console. The red tint appeared. As Zelda would say, "[witness the blood moon's rise](https://youtube.com/watch?v=4KZsT_ZPXiI&t=30)." Troubleshooting 101 would know dictate that the issue is the Switch 2 *dock*. Remember, the console itself was not in said dock. This led me down a merry chase of HDMI CEC and trying to disable it on from the Switch 2 dock. I went with the [electrical tape option](https://bonigopalan.medium.com/how-i-solved-hdmi-arc-problem-between-a-set-top-box-tv-and-sonos-arc-using-scissors-54e3d0f23ca6). This was 100% repeatable. If I unplugged the dock, the signal was clear. Plug it back in and the color issue returned. Google Gemini concluded that this was some failure in the EDID handshake between the Switch 2, splitter, and the capture card. It recommended that I swap the splitter for a HDMI 2.1 switch. The issue prevailed in that scenario. Then the following morning, when I started up the troubleshooting process once again, the red tint was there waiting for me with the Switch 2 dock *not* plugged. It was like a blood-red HDMI version of the entity from *It Follows*. This smear was seemingly infecting my entire chain. I stripped the chain down to its bare necessities; `PS5 Pro > Live Gamer Ultra 2.1 > iMac`. The red curse was still there. I tried swapping out my longer USB-C 3.2 Gen 2 cable for the packed in cable. No luck there. I changed the HDMI 2.1 cables. No success. At this point, I had to assume it was my iMac, right? It was the [[I Have a Problem with Elgato|bottleneck for my Elgato 4K X]]. When I tested the 4K X with my dad's M2 Ultra Mac Studio, I was able to capture 4K120 without the computer breaking a sweat. There had been an update to macOS since then, maybe the issue was introduced with macOS Sequoia 15.5 (24F74). So I went down the computer testing rabbit hole. I tried the M2 Ultra Mac Studio. Red tint present. That wasn't too surprising if I was assuming macOS to have introduced a bug: Our Macs were running the same software. I tried my 2017 13'' MacBook Pro with a 3.1 GHz Dual-Core Intel Core i5 and 8 GB of LPDDR3 RAM. That is running macOS Ventura 13.7.6. The red shade was there too. Okay. Maybe it is the Mac overall. Wouldn't be my first time facing a Mac compatibility issue. I dug out my wife's old Dell Inspiron laptop. You already know it was there too. Troubleshooting 101 would say that operating system is not the problem. The only variable left is the capture card, right? But why? Like I said, I was successful in getting the Elgato 4K X to work with the Mac Studio a couple months ago. Plug and play as advertised. Ever since the Switch 2 entered the set up is when I started having this red issue. I had never seen it before June 2025. ## What Now? I don't fully know. Writing this post is a big factor. I think I will share it and a condensed version on the AVerMedia and Elgato subreddits. I might record a YouTube video for more exposure. I (obviously) cannot figure out this issue. Why do I want it solved so bad? My Elgato HD60 X still works and does not have this red issue. The HD60 X pass-thru is far more limited than the other cards. I cannot play at 1440p120, which is fairly common on PS5 Pro and now the Switch 2. I don't even want to/cannot record at that spec. I want to play at it though. The entire apparatus was designed to make playing and recording seamless. With one button press I could record, but also not have to unplug anything to just play a game of *Fortnite* with some friends or try the Framerate test in *Nintendo Switch 2: Welcome Tour* at their highest resolution and framerate. Until then, I have cleaned up my studio (so many HDMI cables were strewn about). I plugged everything back in, slightly different this time. Plugging the Switch 2 into the HDMI switcher last night gave me the option for 1440p. This morning, it is grayed out again. 🙃 Maybe my TV is sending a wonky EDID signal over the cables where it is fine on the display and not on my capture? Please help me figure this out. My email is [email protected]. Comment on one of the reddit posts. Hit me up. I'm open to ideas, tests, etc. as long as I have the means and gear. <div class=iframe-container> <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/zGwszApFEcY?si=kp-xSSpHq1BSF4ER" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> </div> [^1]: Ignore the lack of sound. I forget to set it up in OBS. [^2]: I never tested my Xbox Series X throughout this whole thing. 😅 [^3]: This is set to -1 to support my Elgato 4K60S+ card. [^4]: Since the start of the current console generation, I've been [[Xbox Series X Backward Compatibility – Xbox Wire|infatuated]] with the Auto HDR movement. Recently, I've changed my tune to "On with Supported Games," but this is a log of my settings at the start of this troubleshooting journey.