NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › OSSC v1.xx series beta firmware
Tagged: OSSC 1.6 mod
Somehow it works now. Didn’t change anything.
I have fixed this. It was bad soldering on resistor pad.
@marqs fw 1.11a broken every JAMMA PCB sync.
I couldn’t get image as well on jamma. It syncs and stays synced but no image only solid black screen.
@Raph_friend it’s likely caused by ADC PLL BW option introduced in 1.11. Its default value (high) is tailored for lowest jitter but unfortunately it has reduced compatibility for some displays. Try changing it to lower bandwidth – I’ve already changed default to medium locally, but that won’t go into effect until next firmware (and then only on fresh boards or if existing profile is reset).
What’s happening is that it’s not detecting any sync from JAMMA PCBs.
Did you get it working with CPS2 or MVS (MV1C for example)?
Edit: After a few tweaks, I managed to get my PCBs working again.
Thanks!
Hello everyone, I’m from Brazil, I made the mod for version 1.8, and there’s something I noticed, on TVs with HDR compatibility, apparently the burn in effect when using 2x or 4x bob, stopped happening, has anyone else noticed? Could this be the solution for the burn in caused by bob? At least on my TV after that, it went back to normal, before the burn in happened very quickly if I left the image paused for a few minutes, I did a test yesterday with HDR enabled, I left the image paused for more than 20 minutes and nothing happened, it went back to normal.
Updated my v1.7 after performing the modifications, my U10 chip was not one of the ones listed but the update applied successfully.
It’s possible that your TV is automatically dimming or slightly shifting the picture to prevent burn in. Most OLEDs do this in HDR mode.
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 |