CMCDv2: ltc is reported in the wrong format

[costela]

Have you read the FAQ and checked for duplicate open issues?

If the problem is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?
Yes

Are you using the demo app or your own custom app?
Reproducible both on demo and custom app.

If custom app, can you reproduce the issue using our demo app?
Yes

What browser and OS are you using?
Firefox and Chrome

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Tizen, Web0S

What are the manifest and license server URIs?

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

What did you do?

Start any stream with CMCDv2 enabled:

{
  "cmcd": {
    "enabled": true,
    "version": 2
  }
}

What did you expect to happen?
ltc should be an integer millisecond value of the playhead distance to the current time, as specified in the current WIP CMCDv2 spec.

What actually happened?

ltc is a full millisecond timestamp for the first few requests (e.g. 1738664450585) and then becomes a non-rounded number, potentially non-integer (e.g.: 12272.13541), both non-conformant with the spec.

Are you planning to send a PR to fix it?
Yes 🔧