[gmpi] Re: New Reqs 3.8 - Events

  • From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Sun, 21 Dec 2003 16:56:45 -0800

That all sounds fine, so long as there's a clear rule for hosts to initialize to zero, for example when the outermost graph is constructed. So GMPI never even claims to handle counter rollover correctly, so plugs and hosts can just ignore rollover. Actually this is one of the best argument for 64 bit timestamps I've seen yet, since of course lots and lots of hosts will run for more than 6 hours at a stretch.

-- Chris G.

On Sun, Dec 21, 2003 at 03:58:33 +1300, Jeff McClintock wrote:
 My rough calculations indicate a 32bit counter will rollover after about 6
 hours.   A 64bit counter will run for over 3000 years before rolling over.

 I'm going to ignore rollover, safe in the knowledge that I will be dead
 before my software crashes.... A little dialog box will pop-up "Ha ha,
 Master clock expired - so sue me!".

(calculation assumes signed integers (1 bit for sign) at 96kHz sample Rate)

I make it much longer than that (assuming 1Mhz clock and unsigned integers):

2^64 / 10^6 / 60 / 60 / 24 / 365.25 = 584542 years

- Steve

---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.

Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: