Does the OSSC dislike PS2 FATs?

[xeos]

Do I need specific settings for using a PS2 FAT with the OSSC?

I have an OSSC that I purchased used a year ago, off ebay. I've not used it a whole lot but when I have it's been with a ps2 slim and it's worked great, never a problem. Well that slim's bit the dust and so I dug out a dusty ps2 fat, and the OSSC is having sync issues with it - after being on a minute or less I start getting a drop in the video and the red light flashes on the OSSC. it seems to come and go but at it's worst it's every few seconds. If I reset the OSSC it doesn't help.

It's not the specific FAT or the specific yprpb cable - I have 2 fats that do this, and the same cable works fine with my ps2 slim. This happens for sure with 480i, I haven't tried 480p. I'm running firmware 86a. and have been for a while.

one thing I notice is that the OSSC will sometimes say the refresh rate is only 59.90hz instead of 59.94hz. Is that to be expected for the ps2??

[Dochartaigh]

I have 3x fat PS2's with HDD's I run on occasion (including some like ~30 hour long games) with the OSSC. Have original Sony YPbPr/Component cables, Retro Access RGBS SCART cable, and HD Retrovision YPbPr cables for them. None give me dropouts like you describe.

Long shot, but some resistors are different between the PS1 and PS2 cables (and some cable manufacturers didn't know at some point), so I'm wondering if it's a difference between the fat and slim PS2's and something in your cable... (others can hopefully chime in about this, outta my comfort zone)

[NoAffinity]

When you say "reset the ossc" do you mean reset it to default settings? If you havent tried this, do so. It may be soemthing inherent to your profiles that isnt jibing with the ps2 signal.

If you have done that, well as suggested, it might be worth investing in. Of course official ps2 (or ps3) component cables are your best bet but even cheapy cables off amazon will at least give a point of comparison.

Lastly, have you tried component output going direct to a screen with component input? I ask because my ps2 doesnt do well with the ps3 cable I have. I have to wriggle it around in the socket until I get it just right to be making full connection on all necessary pins...and that is not simply fully inserted. Otherwise I may be missing either audio channel, any color channel, or various combinations of then including no audio or no video.

Sent from my SM-G955U using Tapatalk

[ZellSF]

Neither of my SCPH-50004s have any problems.

It's possible (if unlikely) that your display doesn't like some aspect of the OSSC's PS2 output. Try another display?

[xeos]

When you say "reset the ossc" do you mean reset it to default settings? If you havent tried this, do so. It may be soemthing inherent to your profiles that isnt jibing with the ps2 signal.

just power cycling.

Lastly, have you tried component output going direct to a screen with component input? I ask because my ps2 doesnt do well with the ps3 cable I have. I have to wriggle it around in the socket until I get it just right to be making full connection on all necessary pins...and that is not simply fully inserted. Otherwise I may be missing either audio channel, any color channel, or various combinations of then including no audio or no video.

it's a cheap cable, for sure, but I've tried wiggling the heck out of it, without any change. it works fine plugged directly into the tv. only the OSSC has issues.

[xeos]

Neither of my SCPH-50004s have any problems.

It's possible (if unlikely) that your display doesn't like some aspect of the OSSC's PS2 output. Try another display?

The OSSC knows it's losing sync - the red light next to the display panel flashes, so I don't think it's the TV.

Also, before I switch to the PS2 on the OSSC it shows that nice internally generated test screen, and that test screen looks fine, no dropouts ever.

I'm a little worried it's the OSSC starting to fail - there's some odd visual snow on the screen now that I've never seen before. it's very hard to capture, but here's a bad picture of it:

https://photos.app.goo.gl/AbTYncyNH8h9BTgb8

this doesn't happen on the internally generated test screen you see on OSSC power on. Only once it's trying to display the ps2. And as I said before, it thinks the ps2 is refreshing at 59.90hz instead of the ntsc standard 59.94hz...

flashing the ossc seems like a good next step, but I'm a little concerned if it's dying that I'll just brick it. At least now it's sort of usable.

[NoAffinity]

The snow is likely a result of the source. Try reducing gain until it goes away. If you can do that, there is probably more granular tweaking that can be done with each individual color channels gain to get a great picture with color balance and no interference.

With ps2 displaying via ossc, go to Settings opt and reset settings. You dont have to save it, but it will temporarily reset the profile to default settings (highest compatibility).

Sent from my SM-G955U using Tapatalk

[bobrocks95]

I've seen incredibly similar snow before on an original Xbox where the Y/green component cable wasn't plugged in all the way. I would assume it's ground related? If the cables are really loose plugged into the OSSC, most component cables allow the connectors to be tightened. May or may not be your issue.

[neorichieb1971]

About 12 years ago a guy brought a PS2 fat to work and it was hacked.

I wanted him to try my component cable on his machine so I tried it and it flat out didn't work at all.

After a bit of investigation it turns out the type of mod that was done somehow disconnected everything except composite video.

Has the unit been modded in anyway?

[Fudoh]

After a bit of investigation it turns out the type of mod that was done somehow disconnected everything except composite video.

his system had a RGB video fix. By default macrovision protected DVDs disabled the RGB output. This could be re-enabled via a mod, but it disabled component video instead. This was done to most modded PS2 systems in Europe back in the day, since component was nowhere to be found, but all CRTs had RGB Scart instead and the PS2 was a popular DVD player after all.

[Guspaz]

What firmware version are you running on the OSSC? There have been changes to the sync processing or default settings in various firmware revisions, the latest version is v0.88. It also sounds like you haven't tried a factory reset to defaults, you should try that.

[xeos]

Has the unit been modded in anyway?

nope. recall also I have 2 ps2 fats that do this.

[xeos]

What firmware version are you running on the OSSC? There have been changes to the sync processing or default settings in various firmware revisions, the latest version is v0.88. It also sounds like you haven't tried a factory reset to defaults, you should try that.

Agreed. I'm running firmware 86a (a testing version that implemented a LED lag testing method at my suggestion; this same firmware has worked fine for 6+ months tho with the slim). My only hesitance to flashing newer is that I'm worried the OSSC is failing for a 2nd reason: it's starting to be inconstant about responding to the remote. Sometimes requiring the remote to be about 1 inch from the receiver, sometimes working from a full 4 feet away. new batteries, too.

[maxtherabbit]

I have also noticed occasional signal drops on my fat ps2 using the OSSC on latest firmware. I don't recall ever seeing them on old versions before .8something. I had assumed it was because the ps2 is my only 480i source but the truth is I don't know what is causing it

[xeos]

Does anybody else notice what refresh rate the OSSC thinks the Sony ps2 console is running at (fat or slim, either way)? Mine always says 59.90 which seems weird. It should be 59.94.

[thchardcore]

I had random dropouts on the firmware from about a year ago.

I solved this initially by changing output to DVI (instead of HDMI) since I am using a converter to output to a PC CRT. I was using the Tendac converter, but swapped to the Porta as the issue would still come and go.

However, on the latest firmware with the Porta (potty), I am using HDMI output without any issues for quite some time.

I heard changing thedefault VIC id may help with this issue, using 2 as the most common setting.

[RocketBelt]

For PS2, try setting 'Allow upsample2x' to on, and 'Autodetect input' to current input.

I found a game that drops sync at predictable events (Sega Rally 2006 Arcade mode). Problem went away after applying the settings above. Allow upsample2x makes the biggest difference. Adding Autodetect input seems to make it re-sync quicker.