Skip to content

v0.10.39: normalise the timestamps

Latest

Choose a tag to compare

@gnacho gnacho released this 06 Nov 06:10
· 16 commits to main since this release

The sound now survives the trip to the consumer.

Fixed

  • The doorbell stamps its frames with the device clock, milliseconds since an
    epoch well past 32 bits. Converting that straight to 90 kHz wrapped and left
    meaningless presentation timestamps. Video survived because a demuxer can
    resynchronise on start codes, but the audio packets were dropped: a 20 second
    capture through RTSP carried 126 undecodable packets instead of about a
    thousand.
  • Each track is now referenced to its first frame, so it starts at zero and
    grows with the real spacing.

Verified

  • TestTSMuxerNormalisesEpochTimestamps feeds epoch-sized marks and checks the
    first is zero, the second is the real difference, and that audio keeps its own
    origin. TestTSMuxerPTSIsMonotonic and TestTSMuxerNeverRepeatsAPTS updated
    to the new semantics.
  • In the container, a 25 second capture now carries 9,147 audio payloads with
    sound and only 615 of filler silence, where the old one had a single silence
    frame.
  • gofmt, go vet clean, full suite green in 9.1 s.

Not verified

  • Decoding the sound through RTSP with this version: pending deploy.