Skip to content

fix: streams above 1080p in the single view (#166) - #220

Draft
compot-dev wants to merge 6 commits into
v2from
fix/large-frames-166
Draft

compot-dev wants to merge 6 commits into
v2from
fix/large-frames-166

Conversation

@compot-dev

@compot-dev compot-dev commented Oct 16, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes #166 (to be confirmed on the reporter's HY300).

Problem. On a Rockchip HY300 (Android 11, OMX.rk.video_decoder.avc/hevc) a 2304×1296 stream connects, the decoder starts and allocates buffers, but never outputs a frame (no "Resolution update" in the log). 1080p from the same camera plays.

Cause (likely). The decoder is always configured at 1280×720 and learns the real size from the stream. With adaptive playback some hardware decoders only allocate for the configured maximum, so a picture above 1080p never comes out.

Change. In the single view the decoder is told the largest picture it supports, via KEY_MAX_WIDTH/KEY_MAX_HEIGHT (the first supported of 3840×2160, 2560×1920, 2560×1440, 2304×1296). The log says Decoder <name>: pictures up to W×H. The grid stays as before: nine decoders with 4K buffers would not fit in memory.

Version 2.17 (2.15 and 2.16 went to the toy drone PRs #215 and #224; 2.14 was the test build hy300-166-test1).

  • Aceline-1: single view and grid still play (1080p, 2560×1920 H.265): single 2560×1920 H.265 at 20 fps (log: pictures up to 3840×2160), 1080p H.264 at 20 fps, grid unchanged, no crash
  • Reporter: 2304×1296 H.264 and H.265 on the HY300

compot-dev added a commit that referenced this pull request Oct 16, 2026
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.

bug with detection video size at 264 and 265

1 participant