Firmware 0.81
- This topic has 6 replies, 7 voices, and was last updated May 3, 2018 at 11:23 PM by .
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › Firmware 0.81
Firmware 0.81 is now available:
* multiplication-based scanline method added
* hybrid scanline option added
* 640×400 preset mode added
* option for linking input to profile added
* LCD backlight timeout option added
* H.mask range increased
* Infoscreen display updated
* fixed applying of some power-on default values
* fixed optimized mode mask and position inaccuracies
* pre-ADC video gain setting added
That’s a number of updates, and we’re now at the point where pretty much all the remaining code space (on -aud version) has been utilized with all the low-hanging fruits of size optimization as well used. It’ll be quiet for a while on the firmware front as some larger-scale solutions need to be experimented with to solve the issue.
YEEEES!!!
Huge thank you.
Thank you for the updated firmware and features.
Will you be updating the online Junker manual explaining the new features for the uninitiated amongst us?
Ted.
Can you please explain the scanline updates? Big thanks for the added improvements!
Awesome, can’t wait to try it out tomorrow.
Huge thanks to marqs, borti, paul and everyone else involved in this major update. ^_-
* hybrid scanline option added
* fixed optimized mode mask and position inaccuracies
Very pleased about these two additions. I’ve been using hybrid scanlines in the beta version of this FW and I really like them. They look even better than standard scanlines imo.
Position inaccuracy was something I didn’t know was being fixed until I saw this today. Really pleased with that! Finally my Super Famicom doesn’t have a single pixel cut off on the left side. Looks perfect now.
* pre-ADC video gain setting added
I’m curious for more info about this. I read the separate thread in the requests forum about this feature, and I understand it’s to compensate for the 1-chip’s blown-out colours, but using various colour test patterns and adjusting this setting, I find the default of 8 actually looks the best. Are certain models less bright than others? Or is the OSSC set to compensate for this by default? Or am I just crazy?
Edit: oh also super stoked about the display timeout feature. That’s bugged me for forever
I just flashed my OSSC to this latest firmware and now although I am getting an image fine. I cannot seem to get any more audio out from the TV like I used to from the RGB AV1 port. Any advice on what to change in the OSSC settings? I tried all the usual make sure the cables are not half hanging loose etc..
EDIT:
Got it sorted. Flashed with the wrong bin file. Needed the 0.81-aud.bin file and it’s sorted.
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 |