OSSC Pro Input profile detection issue

[dead_screem]

Input resolution for NTSC SNES gets misdetected for Scaler as “Gen 1920×240” if im set to 1080p output and if I have FULL aspect set, if I have it set to 4:3 the input gets detected as “Gen 1280×240”. If I set 480p output, input detection is fine. Its as if the output resolution is affecting input resolution detection. This also happens for NTSC PS1, and its 480i output. getting detected as either “Gen 1920x480i” or “Gen 12800x480i” depending on the output aspect setting. the Ps1’s 240p initially gets misdetected as “Gen 1920×240″/”Gen 1280×240” but if I switch the output to 480p then adjust the “Gen 704×240” timings then change back to 1080p output itll get detected correctly as “Gen 704×240” with 1080p output. But no matter what I do I can’t ever get snes 240p or PS1 480 detected correctly. There are similar problems with A-LM mode input profile resolution detection.

[marqs]

Horizontal sampling rate in these generic modes is indeed selected based on output resolution. Typically it results to most balanced image which little/no further processing need in horizontal direction. 704×240 is not any more ‘correct’ with SNES/PS1 than the other ones. If you want 1:1 sampling with console output, there are the console-specific presets which let you  do that.

For scaler mode it would be possible to add an option where smallest / highest generic sampling rate preset is always used, leading to selected scaling algo having a bigger impact in horizontal up/downscaling.

[dead_screem]

For scaler mode it would be possible to add an option where smallest / highest generic sampling rate preset is always used, leading to selected scaling algo having a bigger impact in horizontal up/downscaling.

I don’t understand what you mean.

 

It just makes no sense to do it this way. If I adjust everything for 1080p I then have to redo it all for 720p or 1440p or any other resolution. And moreso, I know what my timing values are for 704×240/704x480i. You can’t even do math to go from 480p timing values to 720p or 1080p, and even if you could, it needlessly overcomplicates it to use. And it’s already overcomplicated enough as it is having to manually adjust timings, instead of a simple auto detected/adjusted based on the input signals actual porches.

This is really making me want to throw it in the closet and reuse my OSSC, as overcomplicated as that thing is.

[marqs]

For scaler mode it would be possible to add an option where smallest / highest generic sampling rate preset is always used, leading to selected scaling algo having a bigger impact in horizontal up/downscaling.
I don’t understand what you mean.

Many input mode groups have a couple generic sampling presets with different rates. A “generic sampling rate preference” option could be introduced with values “auto, min, max”. With min/max, sampling rate would not be automatically selected based on output resolution and aspect, but a preset with lowest/highest of each mode would be used instead.

This is really making me want to throw it in the closet and reuse my OSSC, as overcomplicated as that thing is.

Keep in mind that a lot of people want all kinds of advanced features and feed in sources with higher-than-usual horizontal bandwidth (“super resolutions”). For most parts scaler mode should be easy to use as you just need to select output resolution, aspect and framelock. Anything else you do there like size/position adjustments is already beyond what is possible with most TVs/monitors (without using service menus) and could be called complicated, but they all serve a purpose as there is no one-fits-for-all solution.

[Author]

Posts