320×240 optim. mode for line2x
- This topic has 2 replies, 2 voices, and was last updated May 7, 2017 at 11:59 PM by .
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › 320×240 optim. mode for line2x
For 240p content, linedouble mode’s horizontal scaling is currently limited to 1x (i.e., the equivalent of “Generic 4:3” setting for line3x-5x). It would be great to have the low-active-pixel optimized modes (320×240 and 256×240) available for line2x as well, to enable 2x horizontal (nearest-neighbor) scaling with linedouble.
One specific reason would be to facilitate N64 “de-blur” for line2x in the same manner you can currently do it for 3x and above (i.e. with a H.samplerate of 387). More generally, it seems most 240p consoles with 320 or lower horizontal res show additional noise and/or blur when oversampled by a factor of 2 (even when it’s exactly twice the native sample rate).
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › 320×240 optim. mode for line2x
For 240p content, linedouble mode’s horizontal scaling is currently limited to 1x (i.e., the equivalent of “Generic 4:3” setting for line3x-5x). It would be great to have the low-active-pixel optimized modes (320×240 and 256×240) available for line2x as well, to enable 2x horizontal (nearest-neighbor) scaling with linedouble.
One specific reason would be to facilitate N64 “de-blur” for line2x in the same manner you can currently do it for 3x and above (i.e. with a H.samplerate of 387). More generally, it seems most 240p consoles with 320 or lower horizontal res show additional noise and/or blur when oversampled by a factor of 2 (even when it’s exactly twice the native sample rate).
This has been now implemented and will be included in next fw release.
That’s great news—many thanks for your continued work on this!
| 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 |