Hacker News new | past | comments | ask | show | jobs | submit login

https://arstechnica.com/gaming/2022/05/how-to-play-multiplay...

ArsTechnica’s article includes more detail in how exactly they got this to work - it’s pretty great/disgusting.




It's not very difficult. Just buy a video scalar and slice the screen into quarters. I have a pile of these devices at work. The delay is one frame (or one field in interlaced modes). They are really straightforward devices generally built out of an FPGA or CPLD and some RAM/RAMDACs and old analog ones are cheap.


You might not even need a scaler. Most signage displays have built-in video wall mode that can extract any integer fraction tile out of the raw data, and some models even let you chain the displays so you don't need a splitter or matrix.


You'd have to do some buffering, but I guess you could "just" (this is way easier with digital tech) buffer scanlines, send the first half of it to one screen, the second have to another at half speed, and replay the line for the next scanline? What's nice is you don't have to buffer a full frame to do this, so there wouldn't be a frame of lag.


That doesn't work for a four way split. The top of the screen could have almost zero delay, but the bottom of the screen would need half a frame of delay.

But you can keep the delay to a maximum of about half a frame (and an average of just over a quarter frame across the whole display). It requires driving the two bottom displays out of sync to the two top displays by half a screen.

You could do more with a small software modification on the n64, make it interleave the top two and bottom two images as alternating scanlines. That way while it's outputting the repeats for the top two, the n64 is scanning out the next line for the bottom two.


> but the bottom of the screen would need half a frame of delay.

You mean the two bottom players would have a delay, right? They already have a half-screen delay.


No, the bottom of all four output displays would have an extra ~8ms of delay on top of any native delay. It's unavoidable (unless you can use seriously non-standard timings) as each players output display takes ~16ms to scan from top to bottom, while the n64 takes ~8ms to scan from the top to bottom of each player's view.

You can avoid (additional) unequal treatment by adjusting the timings of the bottom two players so their TVs start scanning out the top line right after the n64 scans out it's middle line.


I wish they'd change the link to this as it contains more technical details.

Edit: nevermind, shame that you can't flag your own comments for moderator attention. I know I can email but I feel like it's not important enough to warrant one.


It’s too late now, but for future reference, if you can still edit your comment, and no one has replied, you can delete them




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: