Pixelcount offset problem with 2 devices in lead/follow + 0.5sec delay

@wizard , if I may, Significant feature release: Sync multiple Pixelblazes if it is still the up to date doc (it may not as it’s now 2.5 years old), please please link it in the official docs on the website. It is not findable, and it’s only after losing many hours with google and gemini that gemini found me this link I was unable to find.

Next, it’s really not helping me with my mapper question. It says “As for mapping, there are two approaches we’ve been playing with. The simpler of the two is to add “phantom pixels” that will compress the respective maps into where you’d like them relative to each other. For example:”
but I don’t get it. Why a few phantom pixels and how do they work, when I’d expect writing a mapper on each device, with a simple x or y offset?
the rest is about nodeid which is not relevant to my use case.