search for: timespac

On 15-Feb-08, at 6:44 AM, ogg.k.ogg.k@googlemail.com wrote: > Well, it doesn't quite work because the second part of the gpos is > an offset, > rather than absolute, and the precision we shed on one, we need to > recover > on the other one, to keep the ability to timestamp events at the > correct > granularity. It would have worked if the second part was absolute

...ion to the first one, and the second granule shift to zero). The current system uses the same granule rate for both the base (the high bits) and the offset (the low bits) of the granulepos. Here, a separate granule rate (typically coarser) is applied to the base, allowing the base to span a larger timespace. Since the offset added to that base uses the finer grained granule rate, the precision of the resulting timestamping remains (as long as the time than an offset can span is less or equal to the granularity of the base, but that does leave quite a bit of leeway). In effect, the existing method map...

...second granule shift to zero). > > The current system uses the same granule rate for both the base (the > high bits) and the offset (the low bits) of the granulepos. Here, a > separate granule rate (typically coarser) is applied to the base, > allowing the base to span a larger timespace. Since the offset added to > that base uses the finer grained granule rate, the precision of the > resulting timestamping remains (as long as the time than an offset can > span is less or equal to the granularity of the base, but that does > leave quite a bit of leeway). In effect,...