Skip to content

fix: duration was exposed in microseconds but is expected to be in seconds#14

Merged
juliendargelos merged 2 commits into
plutotcool:mainfrom
benjaminrobinet:fix/duration-in-seconds
Apr 23, 2026
Merged

fix: duration was exposed in microseconds but is expected to be in seconds#14
juliendargelos merged 2 commits into
plutotcool:mainfrom
benjaminrobinet:fix/duration-in-seconds

Conversation

@benjaminrobinet
Copy link
Copy Markdown
Contributor

Summary

  • Video.duration is documented as seconds but TrackDecoder.duration was returning the raw microsecond value from the manifest, breaking seek(time) whose time is in seconds.
  • The manifest keeps FSVTrack.duration in microseconds (matching WebCodecs conventions and chunk.timestamp); conversion to seconds now happens at the public duration getter boundary.
  • The .seek() was expecting to receive a time in seconds

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

@benjaminrobinet is attempting to deploy a commit to the plutotcool Team on Vercel.

A member of the Team first needs to authorize it.

@juliendargelos juliendargelos merged commit 606e513 into plutotcool:main Apr 23, 2026
3 of 4 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.

2 participants