Do you mean 480p input, not 480p output, I am confused?O-T-T wrote: ↑19 Jan 2024, 08:00So for my needs (see my previous post) what I need is a 480p output (the max I can use if I want the least motion blur possible) @ 240hz and RetroTINK can do that. Is it correct? Note that I'd like to get 4:4:4 chroma, since basically all CRT masks/shaders for RetroArch need it, otherwise artifacts of every kind should be expected.
If you mean output, it's a non-sequitur. 480p is too low resolution for CRT filters. 4:2:0 is at the high resolution level, not the original console resolution level, so 2560x1440 would mean 1280x1440 chrome, despite just being 480p scaled, and 480p is what Blur Busters Law follows (doesn't matter if original or scaled pixels, so why stay 480p).
You have to think in the "correct frame of reference", the theoretical 4:2:2 (which is not yet a feature of Retrotink 4K), is at the high output resolution level, not the original resolution level, only if you were doing filters. Now, if you use 4:4:4 you could do a different resolution like, say, 2560x720 which would be fine for aperturegrille, since the vertical resolution doesn't matter for aperturegrille masks. As long as the OLEDs could scale. So then you don't need the 4:2:2 in that case (at least in theory). But this is as of, yet, untested.
Yes.
The proper way to use Retrotink 4K is low-resolution input, high-resolution output (preferably native).
Evaluate this carefully; This may or may not be the Right Tool for Right Job for you, so I'm saying there's possibly caveats/risks, e.g. like needing to lower refresh rate to 120Hz (e.g. 2560x1440 120Hz would work, as it's the same bandwidth as 4K 60Hz).
If the emulation module is good and RA is configured well, it can be practically perfect. It's just that there's some framepacing optimization issues with RetroArch and some emulator modules.
That's what Retrotink 4K already is, it can do input=output resolution too.
If you were wanting higher resolution output (even without scaling), it'll likely have to be a more expensive device, even if narrowscoped to avoid scaling. That's not the compute/bandwidth problem, it's somewhere else.
No need. He already has the idea but you will have to wait a similar time interval between Retrotink5X and Retrotink4K, for such a device to happen. If you want to wait that long... Maybe ask him directly yourself on the Retrotink4K discord?