Defer WebRCS layer format API integration to a stretch goal

This commit is contained in:
Dandaedre 2026-11-13 11:45:13 +01:00
parent 9058801b02
commit 3b7e4250a8
2 changed files with 45 additions and 2 deletions

View File

@ -26,7 +26,9 @@ more later without promising that every device configuration supports them.
The reference image is an editing aid, not an additional hardware layer. Screen
resolution is independent of the application window size, zoom and image size.
Source routing, transitions, playback, masking, rotation, keying, live preview
and device control remain outside scope. Input cropping and virtual layer
and device control remain outside the offline implementation scope. Device writes
are a later stretch goal (step 10), not authorized work on the connected unit.
Input cropping and virtual layer
resolutions are now planned, with support deferred until after the first draft.
Their coordinate spaces must be designed from the start. See the
[resolution and advanced-cropping specification](midra-layout-resolutions.md).
@ -211,7 +213,7 @@ regardless of selection order except when explicitly choosing a reference layer.
- [ ] Commit each completed task; no automatic release publishing.
Session-file save/load can follow if needed; it is not required to demonstrate
precise positioning. No networking work is included in this plan.
precise positioning. Networking is deferred to the separate stretch goal below.
### 9. After the first draft: input and layer resolutions
@ -237,6 +239,41 @@ Gate: the user's 1920 × 1080 source → 1920 × 1000 input → 300 × 250 layer
workflow retains a 300 × 250 selectable box through zoom, content offset and
placement. The WebRCS settings reproduce the same visible result without masking.
### 10. Later stretch goal: apply layer format through the WebRCS REST API
Status: requested for later; do not implement or exercise device connectivity
during the current offline work. The user's currently connected WebRCS controls
a **live Eikos 4K**. Do not probe, connect to or send commands to that unit.
This backlog entry does not authorize future live-device testing or writes.
- [ ] After offline positioning and advanced cropping are validated, research
the supported API for the exact model/firmware using documentation and an
isolated simulator or explicitly designated non-live test device. Verify
endpoint availability, authentication, units and field semantics rather than
assuming an endpoint from the WebRCS UI.
- [ ] Define the smallest supported operation for applying a layer's format:
dimensions and, where needed for the virtual format, crop/aspect settings from
the verified device adapter. Identify any required position correction and
include it explicitly in the proposed change. Do not alter source routing,
transitions or trigger a Take as an implicit side effect.
- [ ] Keep offline mode as the default. Selecting a device or editing, dragging,
pasting, undoing or redoing locally must never automatically send commands.
- [ ] Present a concrete before/after preview with the device identity, firmware,
screen, layer, Program/Preview target and every setting to be changed. Require
an explicit user action to send that reviewed change; do not infer that a
Preview target is harmless or available without verifying device behavior.
- [ ] Detect stale device state before applying; require a refreshed review if
relevant settings changed. Document whether the API can apply the change
atomically. Report partial failures and uncertain outcomes without blind
retries or automatic rollback commands against a live system.
- [ ] Test against mocked transport first, then an explicitly authorized isolated
target. Verify that no writes occur on startup, connection, local edits,
cancellation or errors, and that only reviewed fields are sent.
Gate: a reviewed layer-format change can be applied and checked on a designated
non-live target. Any use on the current live installation requires separate,
explicit authorization at that time. No API calls are part of this planning task.
## Coordinate contract to verify
Proposed internal model: screen origin at its top-left, X increases rightward,

View File

@ -81,6 +81,12 @@ Reference artwork is illustrative, not a loaded image or live video. Source/inpu
formats, custom output resolution, image import, cropping, alignment and persistent
session files are future work. Sessions currently live only in memory.
Applying layer format through the WebRCS REST API is a
[later stretch goal](midra-layout-plan.md#10-later-stretch-goal-apply-layer-format-through-the-webrcs-rest-api).
The currently connected Eikos is live: this work must remain offline, with no
device probing or commands. A future integration must preview changes and require
an explicit send action; local editing must never update the device automatically.
The displayed WebRCS values use the planned center-from-top-left convention.
Actual firmware coordinate limits, crop behavior and decimal acceptance are not
verified yet. Fractional values remain visible rather than silently rounded.