Component mode needs different Brightness and Saturation defaults for proper conversion output on the Framemeister. In this case, Brightness = 36 and Saturation = 25. This is especially important for Saturation because the default of 32 is WAY overblown. Brightness can be more subjective, but definitely needs to be in the early to mid 30s. Only prob is if say, you are looking to play a PAL only game on say, SNES there is built in 50Hz detection in the import protection on later games that doorslams you out of playing if your console is 60hz. So it’s not as easy as it sounds. PAL to NTSC conversion is affordable if you don't care about image quality. These days, analogue video processors and scalers like the ones you're asking for are either affordable and crap or quality and expensive (and sometimes unobtainable because the rest of the world has moved on to HDMI and globally-standard HD formats). The GBS-8200 also has a component input, but nothing I have uses component, so we won’t be testing that. Controlling the GBS Control The GBS Control mod replaces the GBS’ CPU with an ESP8266 wireless module running custom firmware. The GBS-8200 uses a Tvia TrueView 5725 upscaler chip which is on paper quite competent, so this is potentially a very good and affordable solution.

The PICTURE mode is suitable for progressive sources. If used on interlaced sources, it will simply duplicate fields for every pair of frames, alternating between doubling odd and even fields. This method of de-interlacing is terrible for anything with motion but perfectly suitable for displaying static images, which is where the name of the mode stems from. The GBS-8200 series of upscalers is, to put it bluntly, mediocre at best. Their main advantage has been their low price, and ability to accept a wide range of signals. This has given them some respect among arcade operators, but their picture quality won’t impress enthusiasts. But never count out the enthusiast community: because with a cheap microcontroller, this has been given new life. Why upscale?

Contents

Fudoh wrote:It's not the processing, believe me. If you connect your FM to a (PC-)CRT, it behaves just like the image on a native 15khz CRT. Retrogamingcables only sells specifically designed cables. It also worked perfectly fine for the last 2 years. What bugs me is that the issue also appears with my PS2 when I run it in 576i via RGB, while PS1 and Saturn work perfectly fine. It doesn't seem connected to the RGB cable So i decided to flash the firmware from 0.81a to0.82a that all went well but no mention of how it wipes out all remote control keys/buttons/programmed

The XRGB-Mini aka Framemeister from Micomsoft in my opinion is a an awesome bit of kit and now the king of 240p processing with no noticable lag.

Navigation menu

Now this doesn't seem to make a visually difference to my eyes, but I thought it was worth reporting for anyone wanting to use their XRGB as an HDMI switch. original Wii titles however might only see marginal improvement, but would still probably look better through HDMI rather than component, digital foundry seems to suggest that you should always set the Wii U to the native output of the game you're playing. so for instance if you're playing a Wii U game, you should probably set video output to 720p as that's the internal resolution of most titles made for Wii U. I realize most devices won’t be as much trouble to configure and set up, however I felt the need to mention what I went through, just so you’ll know what to expect. I hope to eventually find a device that sits between the OSSC and display that works like a VP50, just without the hassle. Hence, only the V_SCALER value varies between both presets. The GAME mode - which happens to be the default - is suitable for 240p sources. The VIDEO mode is best suited to 480i/480p sources. Failing to set V_SCALER to 5 in the latter case will result in highly inaccurate vertical scaling. Similarly, failing to set V_SCALER to 6 for 240p sources will result in uneven scaling (especially noticeable if scanlines are enabled). Bear this in mind if you choose to disable AUTO_SCALER.