Generally, I think the points in https://github.com/w3c/webcodecs/issues/122#issuecomment-833788313 make a lot of sense. As I understand we could always add an alternative attribute with values represented by `DOMHighResTimestamp`. With that in mind, I support you using a different type (here unsigned microseconds). @dbaron also made the point (in email thread) that the timestamps you are defining are within the time of the video or audio stream/file, and is independent of the playback rate as that doesn't change the timestamp but just causes it to advance at a different rate Both David and I agree that if that is understood correctly, it is pretty reasonable that it is a different type, differently-defined. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/612#issuecomment-834203258
Received on Friday, 7 May 2021 09:20:55 UTC