Skip to content

fix(image): H264 loop keyframe after reset; v1.7.4#28

Merged
joaner merged 3 commits into
ioai-tech:mainfrom
joaner:fix/h264-loop-keyframe
Jul 14, 2026
Merged

fix(image): H264 loop keyframe after reset; v1.7.4#28
joaner merged 3 commits into
ioai-tech:mainfrom
joaner:fix/h264-loop-keyframe

Conversation

@joaner

@joaner joaner commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • After H264 decoder reset (seek/loop), wait for an IDR before feeding VCL chunks, and keep recent SPS/PPS so bare IDRs can reconfigure.
  • Align loop rewind with seek: notify time subscribers before distributing backfill messages.
  • Demote MCAP initialize console.log diagnostics to console.debug so default console stays quiet.
  • Bump to v1.7.4 and refresh npm lockfile.

Test plan

  • Open an H264 MCAP (e.g. compressed video topic), enable Loop, play through the end and back to start — console should not show A key frame is required after configure() or flush()
  • Image panel recovers from the next keyframe after loop
  • Manual seek mid-GOP still repairs / resumes without the keyframe error
  • Loading an MCAP no longer prints initialize info at default log level (visible only with Verbose / Debug)

joaner added 3 commits July 14, 2026 09:32
Prevent WebCodecs "key frame required" errors when looping by waiting
for an IDR after decoder reset and notifying rewind before backfill.
Also demote MCAP initialize diagnostics to console.debug.
@joaner joaner changed the title fix(image): H264 loop keyframe after reset fix(image): H264 loop keyframe after reset; v1.7.4 Jul 14, 2026
@joaner joaner merged commit a86dec2 into ioai-tech:main Jul 14, 2026
2 checks passed
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