mirror of
https://github.com/YusufB5/ASCILINE.git
synced 2026-06-23 22:48:06 +02:00
Clarify Adaptive Frame Codec opt-in validity
Updated Adaptive Frame Codec section to clarify opt-in validity range.
This commit is contained in:
parent
524d66be72
commit
3e9243fd51
1 changed files with 1 additions and 2 deletions
|
|
@ -35,7 +35,7 @@ No autoplay restrictions. To the browser, it's just text on a canvas.
|
|||
2. **Frontend (Vanilla JS)**: Receives binary frames via WebSockets, manages a jitter buffer, and renders to a Canvas grid.
|
||||
3. **Communication**: Optimized WebSocket protocol with a custom `INIT` handshake for dynamic resolution/FPS adjustment.
|
||||
|
||||
## 🗜️ Adaptive Frame Codec (opt-in, backward compatible)
|
||||
## 🗜️ Adaptive Frame Codec (opt-in,valid for mod [2-5])
|
||||
|
||||
The original binary protocol re-sends the full grid every frame. An opt-in
|
||||
adaptive codec picks the smallest of three encodings per frame and tags it in a
|
||||
|
|
@ -58,7 +58,6 @@ the tested one.
|
|||
| content | vs. legacy |
|
||||
| :------ | :--------- |
|
||||
| static screen / slideshow | **0.3%** (≈375×) |
|
||||
| pixel mode | 11.6% (≈8.6×) |
|
||||
| high-motion / full-frame change | 63% (never worse than legacy) |
|
||||
|
||||
An optional `--quality {lossless,high,balanced,low}` enables lossy *temporal
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue