Some OSSC questions: 640x / 320x profiles interchangeable? 288p or 256p?

[bramblepie]

Hi there, I have been admiring from afar but finally jumped in to the messy but wonderful world of the OSSC. Loving it so far (3 days in!).

I’m based in the UK and so all my setup is PAL and most of it 50hz. I’m using the OSSC through to a computer monitor.

Right, on to the questions…

1) I have been making custom profiles for my PS1 collection that I’m playing via a PS2 with scart, do I need two separate profiles for games in 640×256 and games in 320×256? I have found that 320 h.active games look the same in the 640 h.active (but obviously not vice versa). Likewise, do I need two profiles for games that are 512×256 and 256×256 or can I just use the the 512 h.active profile? Just wanted to make sure their isn’t a reason to keep both before I delete a profile.

2) When setting optimal timings am I right to use 256 v.active or should it be 288?

3) Some times when I use horizontal or vertical scanlines they look like a striped jumper with bands of thicker or closer together scanlines, is this because the scanlines of the OSSC are made to work best with NTSC signals or is this a sure sign that something is up with my timings? Also, can scanlines be used to set correct timings?

4) What is the best way to dial in settings for interlaced content? It’s harder to see changes with all the flickering etc.

Cheers and apologies if these are redundant questions (couldn’t find answers on the internet).

[bramblepie]

Just to follow up, learnt that the striped look of my scanlines was due to a mismatch between my h/v resolutions and my monitor’s 1920×1080 pixels. Setting the height of profiles to ‘270’ gets pixel perfect scanlines. Setting the width to 640 gets pixel perfect vertical scanlines (when in wide mode I believe).

Is there any downside to picking 270 as the height rather than 240/256/288? Other than it being a little smaller and maybe not 100% pixel perfect I don’t notice a huuuge difference.

Anyways, enjoying using the OSSC, if anybody wants my PS1 via PS2 optimal timings for 640/320, 512/256, 384 then let me know.

Cheers.

[BuckoA51]

I’m not certain on your first point, but you can certainly often reduce V.Active with PAL games as few use the full 288p area for the graphics.

There’s not much you can really do to improve interlace sources.

[Harrumph]

Yes 270 makes sense as that scales nicely into 1080p in 4x mode.

[bramblepie]

Thank you so much for the replies, appreciate it.

I’ve come to just accept that interlaced and 480p modes don’t need / can’t be edited that much.

I have a semi-related follow up question: what is ‘Line3x (Laced)’? What kind of de-interlacing does it use? To me eyes it’s still pretty jumpy and flickery but has a more pixelated look and doesn’t burn in almost instantly like the ‘Bob’ modes. Also, on my monitor the ‘Line3x (Laced)’ forces widescreen and won’t allow me to squish this into 4:3. Is their a known work around the squish in games via h.scale to be 4:3 in a 16:9 window?

Again, thank you so much for your replies across these forums. They have been uber helpful. Really enjoying the OSSC still. Can’t get over that analog consoles can look so nice on a digital display.

[Harrumph]

Line3x for interlaced content does not de-interlace, the output is still interlaced (1440i with 720 lines per field, PAL is 1728i I suppose). It’s quite uncommon that a display even accepts it.

[bramblepie]

Cheers Harrumph! I guess that makes sense. Yeah, thankfully my monitor shows both ntsc and pal line3x (laced) modes. I do find it odd that there is still shimmering, even on still graphics like menus etc. Doesn’t appear to change when I alter h.active either. Odd. I’ll have to experiment further with squishing it to 4:3 I guess but it looks good to be more wide-screen games.

[Author]

Posts