-
|
Hello and greetings to the kind people supporting this excellent product. I am having a strange issue and am looking for help... I set up my ambilight using HyperHDR yesterday and had everything functioning perfectly. My setup uses a RPi 4B, EzCoo Splitter and MS2019 grabber connected to a Roku Ultra displaying 4K HDR. HyperHDR is running on the RPi controlling my LED's wirelessly via WLED. I used the setup most of the day yesterday and shut it off last night when going to bed (I turned it off from WLED to stop the "rainbow" test signal from displaying all night). Today, I turned everything back on and I can only get the "rainbow" test signal. HyperHDR says "no signal" when trying to show the live capture. I've tried rebooting everything, as well as rebooting individual components in case this is a power sequence issue or something. I also have an MS2130 (not sure which firmware but I only see yuv modes on USB3.0). I swapped out the grabber, updated the LUT, and was able to get a signal, but it had a horrible "blue cast" to the image to the point that my LED's were mostly blue all the time. I suspect this is a firmware issue, but I have no idea how to use the Chinese software to downgrade the firmware, as I don't read Chinese. Next I tried another MS2019 and changed the LUT back (in case the first one went bad). This made no difference, still no signal being received by HyperHDR. I'm at a loss and have no idea how to troubleshoot this. If someone would be kind enough to help me, I would sincerely appreciate it. Is there perhaps a trick to the order of rebooting the TV, Roku, RPi, WLED and Ezcoo? I'm racking my brain but can't seem to find a solution. Alternatively, if there is a way to solve the "blue cast" on the MS2130, I'm open to doing that too. Any help would be sincerely appreciated. Logs are pasted below for reference... I do notice this entry multiple times: Warm regards, 2024-03-25T22:19:43.451Z [CORE] TTY is not attached to the log output |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Rather than delete my post, I wanted to share that I believe I have found the source of the issue... I did not have the "scaler" enabled on the Ezcoo splitter on HDMI Output 2. I enabled it and everything appears to work fine now. Now I am curious if that might be the cause of the "blue cast" on the MS2130 also. I will do some testing and report back. Please let me know if the scaler was likely the culprit in either case. Many thanks in advance :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I got it working again with the MS2109 for now and returned the MS2130 grabber to Amazon. Honestly, the color rendering and performance has been very good for me on the MS2109, especially as I am using HyperHDR to control WLED over WiFi. I am not sure that in my case going from USB2.0 to USB3.0 would make a huge difference, but I would welcome your thoughts/advice. Do you think it is worth upgrading to the MS2130? If so, where do you recommend buying the device from? Many thanks for all your hard work! |
Beta Was this translation helpful? Give feedback.
Rather than delete my post, I wanted to share that I believe I have found the source of the issue...
I did not have the "scaler" enabled on the Ezcoo splitter on HDMI Output 2. I enabled it and everything appears to work fine now. Now I am curious if that might be the cause of the "blue cast" on the MS2130 also. I will do some testing and report back.
Please let me know if the scaler was likely the culprit in either case.
Many thanks in advance :)