[nmalinoski]

I’m trying a microSD HC card and it says, card not detected. Already formatted the card on fat32, also wrote the image using Win32disk imager. No luck, I guess I need to try a different SDcard.

Can anybody confirm if microSD HC cards work?

You should be able to use SDHC and SDXC cards as of 0.74; if you’re on a firmware earlier than that, you’ll need either a regular SD card (2GB or smaller) or a compatible JTAG programmer to get onto a newer firmware.

If you’re on 0.74 or later, I’m not sure. I’d try a different SD card to start with (if you don’t have one, order one on Amazon; you can get them for $10 or less); and, if that doesn’t work, I’d get in touch with the company you bought yours from.

[nmalinoski]

Though I’m curious as to why you would use a Koryuu on a Dreamcast when component video cables are available?

Only thing I can think of is a desire to play the handful of titles that don’t support RGB output (as in composite-/S-Video-only) without a patch. (That would also preclude use of HD Retrovision’s cables, which appear to require RGB.)

[nmalinoski]

Honestly, that’s just how line-doubled 480i looks on a flat panel. Personally, I think it looks passable with scanlines on, so the OSSC is effectively filling in the missing fields with black instead of doubling the line data.

[nmalinoski]

Which firmware are you on?

[nmalinoski]

Do you know when it will be released?

When it’s ready.

[nmalinoski]

If you get a flicker that looks like a vertical shimmering, that’s because it’s an interlaced signal. This is, unfortunately, the norm for PS2 software.

The RT2X/Pro/SCART are all [relatively] simple line-doublers, so they can’t perform good deinterlacing–the most they can do is duplicate lines (or insert black lines when scanlines are turned on? I don’t have hands-on experience with these devices) to fill in the missing fields every frame in order to bring the video output from 480i/576i up to 480p/576p.

When you put these devices in passthrough mode, it leaves it up to a downstream processor or the display to perform deinterlacing. If that happens to be your display, and your display is in game mode, it wouldn’t surprise me if your display is just doing something similar to the RT2X Pro. In my case, my Samsung LCD looks like it’s filling in black instead of trying to do a bob deinterlace. If you want a good deinterlace, you’ll need to disable game mode on your display and take the tradeoff of added input lag.

[nmalinoski]

If you don’t want to see it, you can hide it with Post Proc > Horizontal Mask.

[nmalinoski]

From what I’ve read, bob-deinterlacing can cause image retention (not quite burn-in) in displays that are susceptible to it.

I’d recommend using passthrough for interlaced sources so that the display can do the deinterlacing.

[nmalinoski]

I’m pretty sure it’s set through Gravatar; I think you’d need an account through Gravatar using the same email address.

[nmalinoski]

Yeah that makes sense. My TV doesn’t allow user control to scale down to pillarbox or zoom out, only to upscale to wide/zoom in/panoramic. I don’t see overscan when I play direct over component to the TV or from the Xbox 360 @480p over HDMI to the TV, so I wonder what is making the TV mishandle the OSSC signal.

Different input types are often handled differently by TVs; so your component input is likely doing different processing to what your HDMI inputs do. For example, I have an older Samsung LCD that will absolutely do 240p correctly over YPbPr component, but not over composite or HDMI (And probably not RGBHV, but I haven’t tested that one).

I also have experience with a Panasonic plasma TV from about a decade and a half ago, which has an HDMI input, but it forces overscan on it; even though it has aspect ratio adjustments, disabling overscan didn’t appear possible. You might be having a similar issue, and I would suggest eventually getting a different display that would allow you to properly display inputs without overscan.

[nmalinoski]

DTV 480p is correct for the Xbox. The rest sounds like configuration issues on the display end.

Now for DTV 480p mode. In 480p passthrough mode, my TV doesn’t resize the image properly, so the picture appears zoomed in but at the correct proportions.

You need to toggle the aspect ratio on the display to a mode that disables overscan, like “1:1”, “native”, or something else.

In 480p line2x mode, if my TV thinks the picture is 1440×960 it shows me the entire picture but stretches it to widescreen.

You need to toggle the aspect ratio on the display to 4:3.

If your display doesn’t let you toggle aspect ratio (rare, but happens), you’ll need to either add a video processor that can control aspect ratio (perhaps by pillarboxing) or use a different display.

[nmalinoski]

Is your CRT boosting sync to TTL on the loop-out? That might cause problems/damage on AV1 of the OSSC.

[nmalinoski]

I bought one of these for my setup; something like that should add some cable relief compared to the solid style adapter shown above.

[nmalinoski]

I post a reply to a thread, and for whatever reason the column denoting the last reply is not updated to mention me. And on at least three occasions in the past month I’ve had to reset my password or got a notification that I had been locked out.

The last-reply column issue pre-exists the updated site.

As for the password resets and account lockouts, I haven’t experienced that; closest thing would be occasionally having to log in again (cookie expiration?), but that’s something else that pre-exists the updated site.

[nmalinoski]

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.

[Author]

Posts