V0.4.0加入锁定二维码
This commit is contained in:
+12
-54
@@ -1,58 +1,16 @@
|
||||
# Roadmap
|
||||
# QFT Roadmap
|
||||
|
||||
## V0.1 — 单 QR 无网络链路(当前)
|
||||
## v0.4 physical validation
|
||||
|
||||
- Windows 选择文件
|
||||
- 单 QR 动画
|
||||
- Android CameraX 连续识别
|
||||
- CRC32
|
||||
- SHA-256
|
||||
- 重复帧去重
|
||||
- 多轮补洞
|
||||
- 保存 Downloads/QFT
|
||||
1. Use **450 B / single QR** as the baseline and measure real-phone distinct new-frame/s at Windows 30 / 45 / 60 FPS.
|
||||
2. Record lock acquisition time, locked ROI area, camera FPS, successful decode/s, distinct new-frame/s and reacquire time per device.
|
||||
3. Only after real-device data exists, test nearby DATA payloads (e.g. 390 / 450 / 510 B) and keep the value with the highest *effective* file throughput rather than the highest theoretical bytes/frame.
|
||||
4. Add optional Windows FPS presets chosen from observed Android effective new-frame/s; the optical transport itself remains strictly one-way.
|
||||
5. Tune focus/exposure behavior across LCD/OLED and 60/120 Hz panels.
|
||||
|
||||
目标不是速度,而是证明:**飞行模式下可稳定完整恢复真实文件**。
|
||||
## Later
|
||||
|
||||
## V0.2 — 扫码稳定性
|
||||
|
||||
- 自动曝光/对焦锁定
|
||||
- 只分析中央 ROI
|
||||
- 720p/1080p 自适应
|
||||
- 帧序号抖动统计
|
||||
- 自动 FPS 调节
|
||||
- QR 版本/纠错级别动态选择
|
||||
- Android 前台常亮、屏幕方向锁定
|
||||
|
||||
## V0.3 — 多 QR
|
||||
|
||||
- Windows 2x2 -> 3x3 网格
|
||||
- Android 一帧多码检测
|
||||
- 每个位置独立 lane
|
||||
- lane interleave,避免同一丢帧损失连续数据
|
||||
|
||||
## V0.4 — Fountain / RaptorQ
|
||||
|
||||
- source block / symbol
|
||||
- 无需等待指定 seq
|
||||
- 达到恢复阈值即可完成
|
||||
- 发送端持续产生 repair symbols
|
||||
- 删除“整文件循环重播”的尾部等待
|
||||
|
||||
## V0.5 — QFT Visual Code
|
||||
|
||||
- 固定四角定位
|
||||
- 自定义二值网格
|
||||
- BCH/LDPC 内层纠错
|
||||
- SIMD 二值化与采样
|
||||
- 60/120 FPS
|
||||
- 标定显示器刷新率与相机 rolling shutter
|
||||
|
||||
## V0.6 — Android -> Windows
|
||||
|
||||
这个方向因 PC 可能无摄像头,使用 App P2P:
|
||||
|
||||
- 同 LAN
|
||||
- 临时热点
|
||||
- Wi-Fi Direct(可用平台)
|
||||
- QUIC
|
||||
- 不经过外网/云端
|
||||
- Fountain/RaptorQ to reduce whole-playlist replay cost without a reverse ACK channel.
|
||||
- Native SIMD/custom visual decoder if ZXing remains the dominant bottleneck.
|
||||
- Optional custom QFT Visual Code after the single-QR baseline is measured.
|
||||
- iOS/macOS/Linux clients.
|
||||
|
||||
Reference in New Issue
Block a user