Hi @marqs, I am wondering if there is any need for me to mod my OSSC rev. 1.6 to install the latest firmware 1.xx. It might be risky, and I don’t want to solder without a strong reason. The main motivation is to minimize the number of converters and make an ultimate device that supports both game consoles and a VCR player. I know that OSSC is not too good when it comes to VCR compatibility, but maybe some sync bugs were addressed and fixed in 1.xx (as I read in what has changed).
An old thread about VCR compatibility: https://videogameperfection.com/forums/topic/vcr-compatibility/
So far, I have 2 significant issues:
1) OSSC loses sync and drops audio/video frequently when getting input from the VCR. If newer firmware has some solution, it’s nice to know.
2) VCR has European SCART output, but not RGB, so I use a SCART to S-video/RCAs adapter and an OSSC add-on board like this to get a proper signal: https://videogameperfection.com/forums/topic/ossc-av-s-video-transcoder-add-on-worthy-upgrade-or-scam/. Since it’s a popular solution, maybe someone else had the same issue. Unfortunately, the colors of S-video output are not bright enough compared to CVBS (which shouldn’t be the case, I expected to see an image with better quality). Is it an issue with the add-on board itself or something related to Lumacode, which can be accessed only in 1.xx firmware? I’ll try to connect the add-on board with OSSC using component cables, not SCART, maybe it will help.
Thank you in advance.
Update: I tried my setup on RetroScaler2x, it has similar issues with sync, but at least getting the image from S-video works properly, and the colors are correct. If OSSC is still not compatible with VCRs, I’ll leave it as it is (so far I am happy with 1.6 and 0.90 firmware features) and will have to deal with an additional S-video to HDMI converter for VCR.
| 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 |