Here’s a comparison between 288p GC (perfect picture, no issues) and N64 (picture slightly blurry, mostly horizontal ghost image/blur towards the right border of the screen; sync? issues).
Both are using Generic 4:3 Line2x mode.
N64
Prof.9 288p
313p 540858 (or 840859)
AV1: RGBS 313p
15.62lHz 49.92Hz
GC
Prof.9 288p
312p* 539415
AV1: RGBS 312p
15.62kHz 50.08Hz
OSSC on-time (warmup) doesn’t seem to affect GC, but heavily affects N64 with flickering going down from every couple of frames to something like every couple of dozen seconds.
Edit:
Considering that this gets better over time, I’m wondering if there’s an issue with my OSSC. I usually associate such behaviour (issues improving or getting worse over run-time) with temperature or soldering issues. (To be fair, I don’t have that much confidence in the connectors because they have no strain relief, i.e. they are not anchored to the case, but all mechanical energy is directly transferred to the solder joints)
I noticed that the issue is worst right after turning everything on. I’ve left the N64 running for a while and then turned on the OSSC and it was pretty bad right after turning it on. I also noticed that the sync info is slightly different, depending on when I push the button on the remote – it’s either Prof.9, 288p, 313p, 540858 or Prof.9, 288p, 313p, 540859.
I don’t have an option to output a test image so I cannot try to adjust sync. The effect I get is very similar to turning up H-PLL Pre-Coast (or rather it makes it much worse).
Huh, okay – it works fine without the receiver. Well, I only get the sound from the TV, obviously, but the image seems to be stable.
Component video without OSSC directly on the receiver works, that’s what I meant with that.
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 |