Skip to content

a port feed is conformed to the size the compile declares for it, else its like target, else the clock - #19

Merged
imbcmdth merged 2 commits into
mainfrom
fix/port-feed-size
Oct 20, 2026
Merged

imbcmdth merged 2 commits into
mainfrom
fix/port-feed-size

Conversation

@imbcmdth

Copy link
Copy Markdown
Owner

A held input fed on a port (a run-time lateral) was conformed to the size of the input it follows (accepts.like), else the clock input's: blitz's compose_av declares its held inputs with pixel formats only, so beside foundmeat's 16x16 synthetic clock a 1080p main feed reached the module at 16x16 and was drawn as a blur under a crisp overlay. Seen live on 2026-10-20; the rule dates from the live-inputs work in 0.29.0 and applied on both memory paths.

  • cli: a run-time lateral whose body selects an input's own first picture with a numeric shape STRUCT gives that stream's hint in -bound a width and height ({"input":"inputs","streams":[{"rate":null,"width":1920,"height":1080}]}); every other binding is unchanged. Test in test_laterals.py.
  • sidecar: conformed() takes the declared size first, then like, then the clock; the pixel format from the port's accepts, else the followed input's; colour from the followed input. The k-th stream of a port-served input pairs with the k-th port of its param's list (written down in NODE-CLI.md). Unit cases for each rule; a gpu_frames case with a 16x16 clock and a 640x360 feed declared 640x360 on host memory and on the GPU; the gpu-box test module gains a w=own variant.

Proof with blitz 0.4.1 unchanged, a 16x16 clock and a 1080p H.264 feed on a port, output 1920x1080, each frame against the source still: 42.7 dB on Windows (D3D12) and on the box (Vulkan decode, nvenc), the decoded feed itself 42.9; 0.32.3 gives 14.7 dB and matches a 16x16 blur at 28.2. A lateral body that does not declare its picture size keeps the old rule (known_gaps.md).

🤖 Generated with Claude Code

imbcmdth and others added 2 commits October 19, 2026 21:47
…r it

A hold input fed on a port was conformed to the size of the input it
follows (accepts.like) or, failing that, the clock input's. blitz's
compose_av follows nothing, so a 1080p feed beside a 16x16 clock reached
it at 16x16. A stream of a port-served input in -bound may now carry
width and height. Where it does, the host tells the node that size at
init and conforms the feed to it; like and then the clock are the
fallbacks as before. The pixel format still comes from the port's
accepts, else from the input it follows.

gpu-box gains w=own, a port-fed w with no like whose output takes w's
size, and the tests run it on both memories with a 640x360 feed against
a 16x16 clock.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A run-time lateral whose body selects an input's own first picture, with
a shape giving width and height, now passes that size on to the node
input it feeds on a port, so the sidecar conforms the feed to it. A body
that declares no size passes none, and the feed is conformed as before.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@imbcmdth
imbcmdth merged commit 13af234 into main Oct 20, 2026
2 checks passed
@imbcmdth
imbcmdth deleted the fix/port-feed-size branch October 20, 2026 05:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant