Redesigned OLED menu. Better UI, easier development.

[PSHarold]

Main features:

• Easier development and cleaner codes. You can now dynamically create menu items, thus supporting showing preset names rather than 1234567. (16 presets max, use WebUI for more)
• Translations. Menu items that need to be translated use xbm images instead of C/C++ strings. Run generate_translations.py to update translations. Menu items can have varying font sizes.
• Long text will automatically scroll.
• Better UI. A unified status bar for navigation and pagination.
• Two new menu items for checking WiFI info and clearing connection (reset to AP mode).
• Shows a screensaver after 3 minutes of inactivity.
• OLEDMenuConfig.h contains some options. Be careful with these options as you can easily run out of BSS.
• OSD menu
  • Brightness
  • Constrast
  • Hue: Not in use.
  • Volume: Not in use.
  • Horizontal Shift
  • Vertical Shift
  • Horizontal Scaling
  • Vertical Scaling

Generate translations for menu items:

1. Open generate_translations.py and locate menu_items.
2. Translate all items in the list by adding "key: value" to the dictionaries, where key is the language code (can be any string) and value is the translated string in the target language.
3. Run python generate_translations.py -font size1@path_to_font1 size2@path_to_font2 ... LANG, where size1, size2, ... are the sizes specified in menu_items. path_to_font1, path_to_font2,... are paths to font files. LANG is the language code used as keys in menu_items For example: python generate_translations.py --font 12@/Users/xxx/Library/Fonts/MesloLGLNerdFontMono-Regular.ttf 16@/Users/xxx/Library/Fonts/MesloLGLNerdFontMono-Regular.ttf will update English strings (en-US is default and can be omitted) python generate_translations.py --font 12@some-font.ttf 16@some-other-chinese-font.ttf zh-CN will translate the strings into Simplified Chinese and use 2 different fonts.

Misc:

• Move some struct definitions to header files.

Need testing.

[ramapcsx2]

@Aleksandr-S12 Hey, your work is really cool, the right spirit! :)

Please understand that this project currently has no dedicated developer with enough time on their hands. Your OSD is neat, but it requires extra chips and extra soldering effort, so quite a lot is involved on the hardware side, in addition to new software stuff. So I think your OSD as it is is not a good fit, mainly because of the extra hardware... It is simply unlikely that people go out and buy the extra stuff, "only" to get an OSD.

Another thing: Have you checked out the TiVo OSD? It has some very rudimentary OSD functions in it.

[Aleksandr-S12]

You are doing a very good job! Thanks to your GBS-C project, we can enjoy retro games on old consoles!

You're right! People do not need unnecessary difficulties with installing additional parts. Unfortunately, in the TiVo OSD menu there is no way to replace the standard icons with your own, and there is also no way to set the text. I think it's pointless.

Have you tried working with the on-screen menu of the MTV 230? I hope Google translator translate correctly!

[ramapcsx2]

Sorry for the offtopic here, nyan :)

Yea, I've checked out the MTV 230 also. It had some setup with the tiny analog switcher IC that is on the output of the TiVo. I don't remember exactly, but I think there were problems with this setup, so I didn't work on it more.

The TiVo OSD is very restricted, yea. I guess nothing really fits the bill here :p I think that adding extra chips should come with big benefits, so if instead of the STV9426, you could use another ESP (maybe ESP32?), that could have multiple other uses, making it more worthwhile. But in this day and age, a whole extra chip just to get an OSD is kind of meh :p

[R2MGaming]

Completed the OSD migration to the new GPS control firmware. Here you can download the source code + instructions https://drive.google.com/file/d/1A3cEvOVxRw7vXp-hBSo_EXhc9TweQ5E0/view?usp=sharing

You're getting a follow from me for this since you did this kind of stuff, for the GBSC project improvement. Maybe you could actually adopt the repo from Rama since you replaced the SMD chip (which I don't know which one it is on the GBS board) with the STV9426 chip to accept a universal remote for controls. If it's possible, you could find many other ways to improve on the GBS 8200 boards (including the HDMI variants) by adding in a composite and S-Video transcoder that could actually make composite and S-Video input crystal clear like the OSSC with a Koryuu transcoder, and IF there is an improved ASIC chip that is the same size as, and has the same pins as the original ASIC, or even better, an FPGA chip that is the same size as and has the surface mounted pins protruding out from all sides of the FPGA or have an FPGA to ASIC adapter made, THIS could actually improve a lot of features missing from or lost with the GBSC project like 16:9 1080p, and if something like this were to work (call me crazy), then perhaps it could also work with 4K with 4:3, 16:9, and 16:10 with aspect ratio switch buttons too. Plus IF certain adapters for certain chips were made to accommodate for the base ones on all GBS boards before adding mods, and if 4K 60 were to be possible along with a way to remove video noise, and random screen tearing or screen tearing static going from the bottom or top of the screen and vice versa without needing to add copper tape to anything on there, it would let me give the GBSC one last chance to use.

EDIT: I've actually learned that it's the ESP8266 doing all the work instead of the current GBS 8200 board chipset. Unless the 8266 got replaced with the 32, it probably could work better instead of the ESP8266.

EDIT 2: Since I am NOW giving the GBS Control one more chance for 1080p 16:9 before I save money for a PixelFX Morph 4K since it's cheaper than the RetroTINK 4K, I've found another workaround by going through my TV's hidden menu to change the overscan on the GBSC to make it all fit on all corners of my TV. I've also duplicated the same Capture Card source from my OBS software to also fit the borders of the device too.

[Nuck-TH]

Please educate yourself about what FPGA is. You already been told to stop this topic, because it is absolutely not how it works.

[R2MGaming]

Please educate yourself about what FPGA is. You already been told to stop this topic, because it is absolutely not how it works.

It's Field Programmable Gate Array which you can re-program stuff about this, and I've already edited my comments saying that I found a workaround to this stuff so the FPGA thing is meaningless. At this moment, I'd rather find out if a device that CAN allow you to have a zoom function to calibrate the output's aspect ratio instead of using my TV to do this stuff exists or not.

[ramapcsx2]

Everyone is allowed to be a beginner, but this topic has derailed too much. I'm closing :)