serialviz VS gbs-control

For my simple app, one-line calls to ESBuild in package.json seem good enough. I run everything using 'npm run dev' or 'npm run build'. See [1].

I suppose it wouldn't scale if the app got too big and complicated.

[1] https://github.com/skybrian/serialviz/blob/main/package.json

Nice! Looks like the protocol between the Pico and the Windows software is quite simple. Porting it to another OS shouldn't too hard.

Here's an unusual approach to portability for this kind of software: since Chrome supports Web Serial, a web app could do the UI and then it would be portable across operating systems (though still Chromium specific) with no software to install (assuming you already have Chrome or Edge).

Along those lines, I wrote a little web app that plots CSV data from a microcontroller board (which happens to be a Pico). There's not a lot to it, but I like it better than the Arduino plotter and it might be useful as an example:

https://github.com/skybrian/serialviz

I built a ESP8266 controlled GBS8200 as main scan converter. https://github.com/ramapcsx2/gbs-control You can get a GBS8200 for about 24$ + shipping and an ESP8266 doesn't cost much. And also it just needs basic solder skills. Not really complicated to build. Then you have a great VGA output. And that you can convert to HDMI with a cheap VGA-HDMI adapter. I personally use an old Eizo 5:4 VGA Monitor because of the aspect ratio but sometimes I do actually connect it to HDMI to record things in OBS.

Try searching for GBS-CONTROL. You should probably start looking here: https://github.com/ramapcsx2/gbs-control

Some games also require you to move the sync signal over to the next pin, some games require sync signal to both pins at once. It can take some fiddling for a few games but I've always gotten it working eventually. It could help to also go ahead and upgrade the board with GBS control. I have my Rush setup that way and it's pretty handy being able to adjust the picture wirelessly with my phone.

In my opinion GBS-Control. https://github.com/ramapcsx2/gbs-control

Try some of the other URLs after connecting to the local wifi. https://github.com/ramapcsx2/gbs-control/wiki/Software-Setup

Arcade "CGA" isn't real CGA, it's just analog 15 kHz RGB. You'd have to use something like this to convert the CGA from your computer into analog RGB if you want to feed it into one of those GBS-8200 boards. They're not very good unless you modify them anyway. I use an OSSC to convert analog RGB to HDMI, but that's more expensive.

After a bit of research, I almost pre-ordered a RAD2X HDMI cable, but that would likely be around $85 after shipping, and wouldn't get here for a while. Also, it only works with the Saturn, while I was hoping to find a solution that will work with other retro consoles. Luckily, I came across this video by Voultar showing how to build a GBS-Control.

If you know how to wield a soldering iron then a GBS-8200 plus gbs-control firmware does a good job too for a much lower price, but that does get pretty technical.

- Sometimes the web UI won't have 1280x960 checked, even if it's outputting a 960p signal. I don't know if this is connected to the vertical shift bug, or if .

Again I'd have to dig into the GBS-C source code to find out why mode changing behaves oddly. There will be a lot of learning to do, understand the software state and chip registers and how they correlate to profile settings and input/output behavior. I suppose I could file a bug at https://github.com/ramapcsx2/gbs-control/issues, but somehow I feel reluctant to do so, partly because I didn't fully understand the setup and don't know if many of these bugs wouldn't happen on a VGA CRT, partly just learned helplessness and not knowing if my bug report is detailed enough or will be ignored or attacked, partly because I'd prefer to chat with the developers in Discord/Matrix outside of a higher-stakes formal bug report or a forum I've never posted at before.