Action Sync doesn't attempt to drive a device's clock, but we have a confusing bit of terminology in that the default timebase is the "host clock" (a term I carried over from other areas, which in this context refers less to the actual CPU clock than to the system's timebase that derives from the CPU clock). That term could use renaming. Perhaps something more specific like "Mach time"? The important bit is that this be distinct from other timebases, such as those derived from audio clocks, which we'll want to support in the future.
The README also needs some editorial work to clarify that we're not trying to deal with hardware clocks, but that we are trying to separate out nominal rate so that it can be usefully distinguished from clock drift.
Action Sync doesn't attempt to drive a device's clock, but we have a confusing bit of terminology in that the default timebase is the "host clock" (a term I carried over from other areas, which in this context refers less to the actual CPU clock than to the system's timebase that derives from the CPU clock). That term could use renaming. Perhaps something more specific like "Mach time"? The important bit is that this be distinct from other timebases, such as those derived from audio clocks, which we'll want to support in the future.
The README also needs some editorial work to clarify that we're not trying to deal with hardware clocks, but that we are trying to separate out nominal rate so that it can be usefully distinguished from clock drift.