Given the API to get the GlobalTimecode of a Block doesn't handle the floating
point value of the TrackTimestampScale (attaching a parent track is not common
and even though the value is not directly available unlike a fractional
timestampscale), it allows external code to compute the proper timestamp
when TrackTimestampScale is not 1.0.
Ultimately the whole way of computing the GlobalTimecode of a block should change but that's probably for a v2.0
Given the API to get the GlobalTimecode of a Block doesn't handle the floating point value of the TrackTimestampScale (attaching a parent track is not common and even though the value is not directly available unlike a fractional timestampscale), it allows external code to compute the proper timestamp when TrackTimestampScale is not 1.0.
Ultimately the whole way of computing the GlobalTimecode of a block should change but that's probably for a v2.0