mirror of
https://github.com/marqs85/ossc
synced 2026-11-01 20:57:10 +03:00
Peter YooandClaude Fable 5.1
88577e1467
While an input is locked, single-shot deviations of the frontend measurements (line count, field period beyond PCNT_TOLERANCE, hsync width beyond HSYNC_WIDTH_TOLERANCE, activity flag or the validity check) make get_status() re-program the mode or drop sync. A NeXT SoG source produced such glitches (868 -> 814 -> 868 lines) every few minutes, each one a visible blink. With this option on, a deviation is acted upon only once it has been seen on three consecutive status reads; the first two deviating reads are replaced by the previous stable values. That is 30 ms in the normal case and up to about 105 ms if the vsync wait in get_status() times out on every read. Counting deviating reads (rather than requiring identical readings) guarantees that a real mode change or sync loss is always accepted on the third read. The counter is cleared whenever the input is not locked or the option is off. Default Off (stock behaviour). Stored as profile item id 69. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WiXHy7Jhh5yTdsBaenucgw