Make 240p and 288p line triple separate options
- This topic has 3 replies, 3 voices, and was last updated December 4, 2016 at 10:48 PM by .
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › Make 240p and 288p line triple separate options
On my current setup 240p line triple works great, but 288p line triple doesn’t work at all. Rather than a combined option for 240p and 288p line triple, could these be split into separate options?
I’ll put that on the list. That’s probably something to implement when new lineX features get added, so that the options would be something like following:
240p linemult [lineX2, lineX3, lineX4, lineX5] 288p linemult [lineX2, lineX3, lineX4]
While at it could we have manually selectable lineX1 mode also?
Not sure if there’s *usually* need for it but Amiga’s DBLNTSC mode puts out 744x467p @ 59Hz and 29.02kHz which is misdetected by the OSSC (it says 494p on info screen and 640×384 under advanced timing settings). As end result lineX2 mode is force enabled even though it makes no sense for this 467p mode. I can set up all the advanced timing settings properly to get perfect picture, except that lineX2 is on and as end result aspect ratio is totally wrong.
So if one could override lineX* mode under advanced timing settings then situation like these could be handled manually. Not sure if there’s any point to make OSSC detect these Amiga modes properly though I have to say that
-J
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › Make 240p and 288p line triple separate options
On my current setup 240p line triple works great, but 288p line triple doesn’t work at all. Rather than a combined option for 240p and 288p line triple, could these be split into separate options?
I’ll put that on the list. That’s probably something to implement when new lineX features get added, so that the options would be something like following:
240p linemult [lineX2, lineX3, lineX4, lineX5]
288p linemult [lineX2, lineX3, lineX4]
Cool thanks.
While at it could we have manually selectable lineX1 mode also?
Not sure if there’s *usually* need for it but Amiga’s DBLNTSC mode puts out 744x467p @ 59Hz and 29.02kHz which is misdetected by the OSSC (it says 494p on info screen and 640×384 under advanced timing settings). As end result lineX2 mode is force enabled even though it makes no sense for this 467p mode. I can set up all the advanced timing settings properly to get perfect picture, except that lineX2 is on and as end result aspect ratio is totally wrong.
So if one could override lineX* mode under advanced timing settings then situation like these could be handled manually. Not sure if there’s any point to make OSSC detect these Amiga modes properly though I have to say that
-J
| 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 |