Replies: 1 comment 2 replies
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I think this is the (rather surprising) issue. Weirdly, the MS2109 was able to work with whatever my Denon is outputting, at least enough to display a picture. The MS2130 seems a lot more temperamental. I just tried a direct feed from an Apple TV into the MS2130, and it worked! So yes, this does seem to be an issue with the Denon output and the MS2130 specifically. I'll look into getting a splitter to address this issue. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
|
I suspect a problem with HDCP. MS2109/MS2130 may have a built-in HDCP key. These are only 1.4HDMI grabbers, so if the manufacturer has provided them, it will work for this older HDMI protocol. However, the MS2109 firmware cannot be read so easily and is quite monolithic on the market, while in the case of MS2130 we have different firmware, but I have not come across one that would have a key. |
Beta Was this translation helpful? Give feedback.
-
EDIT: Root cause seems to be the Denon reciever, see here
As the title says, I've tried 4 different copies of the same MS2130 grabber, and all of them produce a black screen when fed from my Denon receiver.
I've tried a MS2109 as well, and that was able to produce an image from the same source, but it would often freeze after turning the receiver off and on again, so I jumped to the MS2130 in hopes it would resolve the issue.
Needless to say, I've got a whole batch of grabbers (I bought multiple to try and ensure I didn't get a dud) that all produce a black picture.
All grabbers are tested on Linux. I tested on my HyperHDR install, which is a Debian Bookworm install, and the video preview shows black. I also tested on an ArchLinux laptop using OBS and MPV, and none of my tests are able to produce anything other than black.
When I connect the grabber, or turn the HyperHDR instance off and on again, my TV signal blinks a few times so that the Denon receiver appears to negotiate signals properly, so there's at the very least some kind of handshake that's going on.
Has anyone else experienced this? I don't think it's an issue that's isolated to HyperHDR, but seeing as this community uses them a lot, I figured someone might have encountered something.
Final note: I tried a firmware flash with one of them, per the instructions, and it behaved the same before and after. I can try flashing all of them, but I figured I'd hold off until I asked this question.
MS Tools output:
HyperHDR log:
HyperHDR screenshot:
Beta Was this translation helpful? Give feedback.
All reactions