I picked up another power supply for testing and the problem persisted so I’ve eliminated that anyways.
I’ve test multiple other 240p component video sources (SNES, N64, PS1, Genesis) and they all worked fine. I just don’t have another 480p component source to test.
However, I just thought to test 480i video sources to see what I could find there. Somewhat unsurprisingly, when I set the Wii to 480i I still saw the horizontal lines, but what was interesting was I was able to replicate the same horizontal lines from the N64 when running a game that outputs 480i (which is somewhat rare but luckily I have games that do so).
So, this tells me that there’s a high probability that the issue lies with the OSSC (or its power supply) on 480i and 480p component video sources. Which means it’s likely the power supply, the HDMI mod I did, or some other component of the OSSC. Would you agree based on these tests?
Oh the other thing I forgot to mention is that I tested bypassing the OSSC (ie. by plugging the Wii component cables directly into the TV (Samsung UN50MU6300F) and a monitor (Dell 2407WFPb)) and I didn’t see any scrolling horizontal lines. At first I assumed this proved the OSSC (or its power supply) was the culprit, but I then had the thought that maybe the TV and monitor are both performing some sort of post processing that removes the noise from the signal? Is that possible?
They’re straight
My Wii doesn’t have any display outputs mods like an HDMI mod, though it has been modded for homebrew if that’s relevant.
Unfortunately I don’t have another compatible PSU I can try, nor do I have another 480p component output that I can try to eliminate the Wii as being the culprit. I have tried different component cables which made no difference so it isn’t those anyways.
If you think those things are the most likely causes, I can certainly look into trying to test those things?
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
__gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
wordpress_apbct_antibot | session | No description |
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |