3 ms·
I'd rather the open source hardware OSSC[0] or OSSC Pro[1]. 0. https://videogameperfection.com/products/open-source-scan-converter/ https://videogameperfection
by snvzz 1y ago
I'd rather the open source hardware OSSC[0] or OSSC Pro[1].
0. https://videogameperfection.com/products/open-source-scan-converter/ https://videogameperfection.com/products/open-source-scan-co...
1. https://videogameperfection.com/products/ossc-pro/ https://videogameperfection.com/products/ossc-pro/
- Arainach 1y agoThis is the same debate as "Home Assistant vs Google Assistant" or "Linux on the Laptop vs Windows/Mac". If you love poking around and tweaking things OSSC is on an absolute sense capable of a few more things at the cost of significantly more pain. I'll stick with Retrotink.
- snvzz 1y agoidk about the pain. IMHO it's pure FUD. Generally speaking, it just works. Literal plug and play. And I'm not saying this randomly. I have had my OSSC for years, and I use it with ample variety of hardware, including PC8801, PC9801, Amiga, MSX, IBM PC clones (8086, 486, Athlon) and the usual console suspects. With adjustment, it works to perfection. For the Amiga (and only the Amiga) I did input pixel perfect timings. It's easy and, on that platform, it makes a difference. These timings seem good on both OCS/ECS and AGA. I can hardly justify it, but I love my OSSC enough that I am planning on a OSSC Pro in the future. That way I will be able to divide my hardware across two rooms.
- nicole_express 1y agoThe OSSC Pro is actually one of my go-to in my workspace setup. Big fan of it, highly recommend. A problem here is that it doesn't have composite input like you'd need for the Apple II. So you'd need a Koryuu or the add-on I think they're selling now, which complicates things a bit. A solvable problem, of course, and maybe I should've included that in my post as well. Probably would have if it was a bit more serious!