Retro AV |OT| RGB, CRTs, Upscalers, and more


Except that you have to know the resolutions and have the ability to run the test suite with a rom cart. I don’t have ability to run the test suite on my PS1 and even though he posted his findings of PS2 it looks wrong for some reason.

I’m looking forward to dialing in my Genesis and N64 tonight.

I hope some day to have it set up for GameCube, & Wii.


Yeah, exactly. I kinda assumed so, but you need to be able and run the Test Suite on every system you want to configure (I have the same issue, as in, the only console I can actually go through that way is the Mega Drive).


No Xbox here. I didn’t consider that image quality may be as much game dependent as the system it’s running on.

I’ll have to check out that FBX video for Wii settings. It’s pretty much all I use the OSSC for at the moment.


I’m not familiar with the fs320 but I did look it up for you. It’s a standard def TV which is good but it does have some digital processing which you should be able to turn off. It’s newer then an fv310 because it has a memory card slot on it but I have no idea how it looks. I know the FS100/120 models are significantly worse then the FV300/310 (I know this from experience.


Thanks Socks. Figured you would be of help on this!

So it’s an FS model, but it’s newer than the better FV models… odd. I might just have to go take a look. I have the ability to do the 240p TS on my GameCube, though I need to actually download it and set it up. Could use s-video with that. Ugh, really don’t feel like breaking down anything from my setup right now, though. I might just pass unless I can find some first-hand info from an enthusiast somewhere…


Unfortunately I’m having trouble coming up with anything. I’ve seen several posts that suggest the fs320 is the newer model of the fs120.

I did find this.


Where do you get the labels he has on his N64 carts?


No idea. I’m a CIB nazi


Man, I’m just not sure it’s worth hauling that huge 32 incher at this time. I would have to re-arrange my entire setup in a major way to use it so it would just be sitting in my basement for quite a while, maybe years. If it was the FV310 or a 27 inch FV300, I’d jump but I don’t think I’m going to be able to swing it right now. Maybe if they give it to me for free…


HA! We diverge. You poor bastard. I think it’s a fools errand even though I have most of my GB/NES CIB because no box will ever live up to my standards in my head. I had to let that one go.


For the fv310 it’s absolutely worth it. I prefer it over my BVM.

When I first got into retro gaming I was just grabbing whatever garbage I could find for cheap and it looked like ass having loose carts everywhere. Now I’m very particular about what I grab and it must be CIB. I’d rather just play it on an everdrive if I’m going to lose the box/manual experience


There are a lot of problems with this approach. For example on some systems the horizontal resolution varies; it can change game by game or even within the same game. So you’ll dial it in perfectly for 320 wide output on Genesis and then the game could switch to 256 wide, and you’d have to change the settings / profile constantly.

But even if you’re OK with doing that, if you try to line up each hardware pixel to n screen pixels you’ll still end up with an incorrect PAR and the wrong aspect ratio. This applies for any system where the PAR is not 1:1 (most of them).

The best way to set this up is just to take exactly as many samples per line as you are outputting pixels horizontally. Ironically, this is exactly what the default setting does for 240p on the OSSC; you’ll get the best possible image at the correct aspect ratio.

You can’t do that for 480i/480p but the upsample2x does a really nice job just oversampling the line to compensate.


I think PS2 and Wii have different internal resolutions based on the game. I tried the settings FBX gave for FFX and I would rather just play the HD port.

Everything I have goes in a box and the boxes I have for those games are also in boxes and even if I had CIB I end up putting the manual in the box that I keep separate from the games. This is the wrong thread for this chat. We should discuss it more here.


Yeah, I just saw @poptart’s post and makes a good point.


PS2 varies the rate put out on the scan; 512 or 640 wide for 480 content plus many games don’t use all that:

I’d strongly recommend leaving most of the OSSC’s advanced settings at the default when outputting 480 (aside from the upsample2x) to not disturb the aspect ratio that the game is intended to have on PS2.

I posted above about the Wii but the rendered resolution is recommended to be 640 (but could be lower) which is very often scaled horizontally in a somewhat blurry way before being output. The amount of pixels on the output phase is always 720 but the internal resolution is lower.

For FFX specifically the HD port is extremely well done so yeah I’d recommend that, especially with transfarring to the Vita version.


The thing is, the timing needs to be adjusted or you get audio and visual drops. I think you are right but once I used FBX’s method the OSSC behaved in a new way. Before I would just run the audio from my GSSCARTSW to some speakers but now with SNES the timing is fixed and I no longer get any audio drops. No flickering pixels or any nonsense. I’ve never seen the SNES look better on any HD display using any method.

I used that 320/256 approach for a while with the framemeister. I don’t own a lot of Genesis 320x games so I would try to make a mental note to switch it over. With the Framemeister I had 20 profiles so it wasn’t a big deal to have 3 genesis specific ones (320/256 for 1080p and 1 for 720p)

The thing is, there is timing issues that I think need to be dialed in, in the advanced menus because on my tv 480p x2 and 480i x4 will often desync. The last adjustment he did with the checkerboard is probably the only adjustment necessary to keep your tv and your ossc in sync.

If you are using a 4K TV you can take advantage of some of the TV’s pixel and width features to correct for aspect ratio going wonky. I think you are right in that probably should use the output res instead of the internal if your tv isn’t as full featured in that department.

Default the V. Active even when putting in 480 content is 240. Shouldn’t you adjust that to 480?

FBX really opened up the OSSC to me this weekend and now I want to master it. The world after CRTs is going to happen and if I could get something to look “good enough” on a fixed pixel display I will. As of right now, I can honestly say that the settings for my snes on my 4K are so good that I don’t feel like I need to play it on a CRT anymore. This is probably my first time ever thinking that.


Again not sure what’s up with your TV’s sync handling. :slight_smile:

I don’t think most TV’s aspect ratio correction is really good enough to dial in the exact aspect ratio you’d want, and in doing so you would always blur pixels horizontally anyway so you might as well just output at the right aspect ratio to begin with.


The 1st option when you get to your advance setting is defaulted to 180. If you adjust that to get the timing correct. I think my 4Ks in general are less forgiving with variance in the HDMI spec. (sony’s even more so)

If the image does sync sometimes you get audio drops which means the tv kept the visual but dropped the audio. Figuring out what timing is necessary is probably key to resolving this incompatibility. If you go to their forums there are tons of tvs that don’t play nice. The makers of the OSSC should be working to fix this via firmware not having users trying to hack the settings to get it optimally operational.


Quick and very ‘visual’ mini-explanation of clock/pitch and phase controls for analog-input on LCD screens. Could be of some help for the non-tech people like myself, while tinkering with the OSSC’s Advanced timing tweaker.


I have to wonder what exactly is causing the incompatibility. Is it the non-standard resolutions, or is it the framerates? A combination of both maybe? I have to wonder how much of that is addressable in the firmware itself.