UI Audit: New Recorder modal — codec/audio/container sections feel stub-like #150
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The new-recorder modal "Master recording" section has three tabs (Video, Audio, Container) but most fields are static placeholders that don't actually do anything:
These all render as
<Field label="…" value="…" select />which is a presentational stub component — they don't bind to recorder state and the values they show don't get saved.What actually saves
Of the modal's fields, only these write to the recorder row:
namesource_typesource_config(URL for SRT/RTMP, empty for SDI)device_index,node_id(SDI/Deltacast)generate_proxyrecording_codecrecording_containerproject_idEverything else on the Audio/Container/Resolution tabs is decoration.
Recommended fix
Two options:
A. Drop the stubs. Remove the Audio tab, Resolution dropdown, Color space, Bit depth. They're not connected, they suggest features that don't exist, and they take vertical space.
B. Wire them up. Map to existing recorder columns (
recording_audio_codec,recording_audio_channels,recording_resolution, etc. — these columns already exist in the DB).B is probably right since the backend supports it. The Field stub needs to be replaced with a real bound
<select>.Also
Proxycollapsible section showing tagsH.264 / 2 Mbps / MP4? Either expose the proxy fields (the DB hasproxy_codec,proxy_video_bitrate, etc.) or hide the section.Discovered during full web-ui audit 2026-05-28.