The “perfect” timing window in Festival is +/-5ms from gem position (10ms total afaik). Harmonix has always been exceptional with their beatmatching code. There are physical limits to the black magic of latency compensation, however. If your input has to travel over the wire before the game can see it, then it’s unavoidable without heavy compensation
IBM PC design philosophy was the furthest thing possible from “open architecture”.
The PC only became “open” when the industry basically strongarmed it open. Prior to clean-room BIOS cloning, IBM did pursue legal redress against early clones.
The Nintendo black boxes were still mock-ups to a significant degree. They often depicted situations nearly impossible (or actually impossible) to achieve in-game, the graphics often exceeded NES color limits, and often the pixel art itself was completely wrong (check out Mario on the Donkey Kong or Mario Bros boxes).
It’s worth noting that this is not actually explicit in the standard so much as it is just a natural consequence of not including the half-line. Since the raster is continually moving across and down, including during all retraces (until the actual blanking pulses reset them), the presence of the half-line means that the horizontal retrace doesn’t reset at the end of the half line, it just continues scanning horizontally while the vblank pulse resets the vertical deflection to the top of the screen. Similarly, all scan lines are actually very slightly tilted down on all CRTs unless there is compensation for it. The vertical deflection is consistently moving across the length of the horizontal trace.
Edit: if you have a set that is miscalibrated or worn out, you can end up actually seeing the retrace lines during what should be blanking
We're not talking about DOS here. This is AmigaOS, a fully preemptively multitasked OS from day one. No memory protection, but unless your code is running on bare metal like demos and games, there are other tasks running.
Top parent of this thread is talking about a package for AmigaOS being run on a bespoke emulator (as the Unusable Amiga Emulator of the 90s wasn’t really a thing that could be used for that)
AmigaOS does indeed enable the extra half line when any visible viewports are interlaced. Fortunately that just works because the individual “non-interlaced” fields are still legible when shifted back and forth by a half line.
Forgot to add this earlier. Later versions of AmigaOS that support non-15kHz rates will promote all screens to the lowest screen mode that can suppprt all visible screen resolutions. So, if you drag a NTSC:High Res Interlaced (640x400@60i) screen down in front of a Multiscan:Productivity (640x400@70p) screen, then the front screen will also display in Prpductivity mode.
Piles of evidence that humans tend to treat AI as infallible, just like the police did here. They didn't use this as a point for further investigation, they saw the match and said "let's go get her" without so much as looking at the damaged vehicle for paint transfer, which should be remedial-level police instruction.
Modern AI was and is a mistake. It's only going to get worst before it gets better.
Unfortunately, our current government in the US is hard AI-pilled (oh, sorry, "super-intelligence-pilled"). They use it every day to present propaganda to the public via social media.
Ban AI use in all branches of government, and in policing. At least until there are ethical standards put in place that are very heavily punished when violated.
Also, state and federal level politicians should be prohibited from using social media in anything other than a purely personal basis without mention of political office or without speaking on the topic of politics. Want to post cool pictures of your family? Go for it. Speaking to your constituency? Must be strongly vetted for ethical violations, and punishable by immediate removal from office and a 10-year blacklist.
reply