Forum Replies Created
Your video is private.
If your PS2 only has this problem through the OSSC and not when it is directly connected to your TV’s then there must be something wrong with the OSSC or its power supply.
Did you buy it from Videogameperfection?May 13, 2020 at 11:02 AM in reply to: Random noise in image, tried nearly everything, have no idea how to proceed. #37782
With all modes do you mean Line3x and Line4x also have this issue?
I already tried three different power supplies for the SNES
Any of them an original Nintendo power supply?
It doesn’t make sense that it is blurrier with optimized settings. Are you sure you weren’t outputting at Line5x with generic 4:3?
The profile by FBX is only for 320×240 or 640x480i resolution but there are some games which use 640×240 so those games will have missing pixels with his profile.
BTW the reason that the SNES looked much sharper in that FBX tutorial video was because it was outputting at Line2x before he imported the profile.April 29, 2020 at 10:25 AM in reply to: N64 RGB Advanced – OSSC – Best picture in Passthrough #37323
You are using 320×240 optimized and that is not enough pixels for the menu of the N64 Advanced.
Either use Generic 4:3 which is easiest or use 512×240 optimized mode with the settings that FirebrandX used in the 480i mode of his N64 profile. (773 samplerate, 640 H.active).
Optimized modes are set to 240 lines by default so you may lose some part on the top and bottom if PAL games used more lines. Adjust V.active to show more lines.
The OSSC only chooses PC resolutions through AV3. That’s why it detects it as 800×600 instead of 576p.
Yeah your OSSC is defective.
You can lift the pin to fix the diagonal lines but the APU-01 revision also has a lot of noise in the video. You are unable to use reverse LPF due to that because that really amplifies the noise.
It might be better to find another SNES like a 1-CHIP or GPM-01/02 revision.August 11, 2019 at 9:15 AM in reply to: Dreamcast OSSC 480p 2X settings for Retro Access scart cable #27387
You are testing this with the SCART cable directly connected to the OSSC and not with a SCART switch in between right?
Depending on what cable you are using the console and cable could both be at fault. APU-01 is a later revision than RGB-02 so I think it still has the same issue. Though serial SM117 is closer to APU-01(SM119) on that list.
The GPM and 1-CHIP are the best revisions with 1-CHIP being the sharpest.
Try disabling Sync LPF. What kind of cable are you using?
Even less frequently, there’s a chance it will shift it up by *two* pixels, resulting in a backporch of 13 being needed and the top line actually being cut off entirely.
So you mean in this case the top line is not visible with any backporch?
I think this is probably a N64 hardware quirk. Does the vertical position change when you are just switching inputs on the OSSC?
You should look at some video examples to decide what you want to do.
PAL NES Composite vs NESRGB on an OSSC comparison: https://www.youtube.com/watch?v=psd9e8DPGfI
Composite -> RetroTink -> OSSC: https://www.youtube.com/watch?v=WKZLGVMctlk
Hi-Def NES: https://www.youtube.com/watch?v=TI60A3DpI6w
You don’t have to use an installer in the US. Here is a list of recommended Hi-Def NES installers world wide: https://www.game-tech.us/recommended-kit-installers/
The installers from that list will probably also do a NESRGB install if you ask.
Board revisions APU-01 and RGB-01 of the Super Nintendo have those diagonal lines in the image. Check your serial number at https://docs.google.com/spreadsheets/d/1HYLy_TTDop_FzuX6qnxuQI43upg4raXfno582taO744/pubhtml
If you don’t have one of those revisions then it is caused by your RGB cable.
If you cannot lower H.samplerate with 1920×1200 then use 1600×1200 and set your monitor to 4:3.
You need to test without the receiver between the OSSC and the TV.
You said composite video did not show the issue. Did you connect the composite video cable to the component input on the OSSC?
It looks like the TV keeps receiving correct sync because otherwise it would blank out for 2 seconds. It is probably caused by the RGB mod or receiver.