=== Pitfall #2: Screen lag ===
Once you connect the CPC to a modern monitor, you may experience a phenomenon, that some games just don't feel right. It's like you are too slow - or that the collision detection seems to be off. Of course, some games are just crappy in that regard, or you might just get old ;-). But it's at least as likely, that your set-up has a significant screen lag. Screen lag means, that there is a significant delay between the moment that your CPC sends a signal to the monitor and the moment that this signal is shown on screen. Old school monitors don't have a significant screen lag. The CPC updates its screen 50 times per second, and any update will be visible almost instantly on a CTM644, GT65 or any other old school monitor with a tube. the reason for this is, that these monitors work analogue. They display the signals they receive immediately. As soon as there are any digital devices involved, this changes. Digital devices have some kind of chips that take the analogue signal and transform them into digital signals. This transformation requires some time and depending on the logic that is built in, this time is almost neglectable - or can be so significant, that it harms your gaming experience. A lag of 1 or 2 frames often does not do any harm, but any lag above one or two frames can be recognisable, at least in fast paced games which you are familiar with. You will see bullets still quite a distance away from you, but in the computer, the bullets have already hit you. You simply can no longer react fast enough, so this might be even [https://www.youtube.com/watch?v=7VOsOuQ5mhM&t=12s THE most important aspect of your set-up].
(Note: Screen lag of course is not limited to games, but primarily there it can become a problem. If you want to measure the screen-lag of your set-up, there is a pretty easy way to do so, you just need your CPC, a mobile phone that can shoot videos at 120 or 240fps and a computer, to watch that video frame per frame. See: [[Testing your Screen-Lag with a CPC]])
[https://www.youtube.com/watch?v=2CnsQBGAuos The new star on the horizon.] An open source project, that combines a Raspberry Pi with some custom logic, to convert signals from home computers and home consoles to HDMI. For almost every computer there is a more or less different version of the board. You can build the RGB2HDMI yourself or buy a finished version, e.g. on sellmyretro.com . It's features are even beyond those of the OSSC and Framemeister. Its total price is somewhere between the GBS and the OSSC, depending on where you buy it. And its tiny. Its biggest disadvantage is, that you need a different version of the board per console or home computer (well - some computers share a similar signal, so e.g. for the BBC you can also use the CPC version, but e.g. an Amiga or an Amstrad Plus each need another converter version). Screen lag has not been measured yet for it, but it seems to be very low.
== Links ==
CPC Wiki
* [[LCD And Plasma TV Solution]] (Composite Video)
* [[Power Supply for CPC and CPC plus]]
External
* [https://github.com/ramapcsx2/gbs-control GBS Control for GBS8200]
* [https://www.youtube.com/watch?v=7VOsOuQ5mhM Screen Lag - explanation and comparison video]