Having trouble with 3X on PS2

NewHome Forums OSSC & OSSC Pro OSSC – Discussion and support Having trouble with 3X on PS2

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #39398
    ATS
    Participant

    2X and 4X appear to work fine, but I actually got a bit of burn in from 2X yesterday which I was thankfully able to fix with a test pattern on youtube. For whatever reason I can’t get 3X to work on my PS2, I just get a black screen despite the OSSC having the working green light. I want to use it since it doesn’t use bob. 5X says it’s unsupported but I’m not worried about that one.
    I don’t have any issue using 2X, 3X, 4x, and 5X on the Genesis, Snes, and N64.

    My TV is an [LG] webOS TV UK6090PUA 4K Smart Ultra HDR. Bit of a mouthfull.

    These are my timings for the PS2:

    H. samplerate
    858.00
    H. s.rate adj
    858.00

    H. synclen
    62

    H. backporch
    57

    H. active
    720

    V. synclen
    3

    V. backporch
    15

    V. active
    240

    Sampling phase
    180 deg

    #39405
    nmalinoski
    Participant

    What, specifically, is giving you trouble? System menu? PS1 games? PS2 games?

    You mention bob deinterlacing, which tells me you’re likely working with PS2 games running in 480i. If that’s the case, you’re looking at 1440i with line3x, which is a very atypical video mode, and it doesn’t surprise me that your display doesn’t like it. You’ll need a scaler that supports that mode in between your OSSC and display if you want to use that.

    If you still don’t want to use bob deinterlacing, consider using passthrough for 480i and letting your TV do deinterlacing and scaling.

    #39406
    ATS
    Participant

    The system menu and PS2 games. It cuts back to my TV’s screensaver since it can’t display the picture. The only real reason I wanted to scale it is for recording a bigger picture when I use my capture device without having to blow it up on the computer after it’s been recorded since it records it natively at a very small resolution. Originally I was running 2X through an mclassic and that actually looked pretty decent and would’ve done what I wanted, but I got burn in cause of the bob technique. It’s not that I can’t just change the channel or turn off the TV when I’m not playing, but it happened very fast. Took maybe 10-15 minutes. I decided I’ll just forego the mclassic for now since it only works on 2X and I don’t want to worry about the bob issue, 3X seems like a big enough picture for recording purposes.

    • This reply was modified 3 months ago by ATS.
    #39430
    ATS
    Participant

    Is there any chance using a scart cable from the PS2 to the OSSC would fix the issue instead of using component?

    #39455
    nmalinoski
    Participant

    The nice thing about a SCART cable on the PS2 is that you can use it for both YPbPr and RGB output to an OSSC, and, especially if you want to use RGB, you can enable automatic input switching, which will automatically handle the RGBS->RGsB format change when switching to 480p+ video modes; however, no, that will not change anything regarding issues with interlaced video.

    If prescaling is an absolute requirement, you can look into either adding an additional scaler, like an Extron DSC 301 HD directly after your PS2 (will also support 480i line3x; tradeoff will be 3-second recoveries from HDMI blackouts and a frame of lag) or using something like a Framemeister (or an OSSC Pro, whenever that comes out) instead of an OSSC.

    #39477
    Jarrah White
    Participant

    Speaking purely as a guy who cleans and converts VHS to digital for a living, I’d personally just use the passthrough mode with the majority of PS2 games. The reason the 2X, 3X and 4X modes look so good on Sega Mega Drive, SNES and N64 is because the majority of the games output at 240p or 288p. Because the signals are progressive, that means the OSSC has all the lines that make up the frame right from the word go. The PS2 on the other hand primarily outputs at 480i or 576i – interlaced video signals. What that means is the console alternates between showing the odd and even numbered lines that make up the frame separately. In progressive video, 30 frames per second is just that. But in interlaced, 30 frames per second is actually 60 half-frames per second. Not half as in chopped in half, but half the lines that make up the frame. That means with 480i or 576i content, at any given time the OSSC only has half the image to work with. Linedoubling such content means half the vertical resolution is lost.

    For that reason, I would NEVER linedouble an interlaced signal unless it was a re-release of an old 288p game that was converted to 576i. The PS2 has a few games like that, such as the Sonic the Hedgehog collections. Deinterlacing such games in the normal field combination method generally results in combing artifacts where there shouldn’t be any, whereas linedoubling 288p games that were converted to 576i surprisingly retains the original visual intention. But for the vast majority of games that were rendered at 576i to begin with, you’re better off letting your TV or some other device do the deinterlacing. Even a cheap scaler will produce a more accurate deinterlace of such content than the OSSC or RetroTINK.

    • This reply was modified 2 months, 4 weeks ago by Jarrah White.
    • This reply was modified 2 months, 4 weeks ago by Jarrah White.
    #39516
    ATS
    Participant

    I actually find that the passthru mode looks very good using the OSSC and generally looks better than most other methods I’ve used with the PS2, the only reason I was really trying to upscale it was so I’d have a bigger picture to capture for my computer rather than manually blowing up the picture in a program after I recorded footage.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.