From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,FROM_WORDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f8311a3a7edd715 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2000-12-12 12:00:23 PST Path: supernews.google.com!sn-xit-02!supernews.com!newsfeed.mesh.ad.jp!hermes.visi.com!news-out.visi.com!nntp.flash.net!news.flash.net!not-for-mail From: "Ken Garlington" Newsgroups: comp.lang.ada References: <915jl7$jt5$1@nnrp1.deja.com> Subject: Re: Using "delay until" in real-time X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: Date: Tue, 12 Dec 2000 20:00:19 GMT NNTP-Posting-Host: 216.215.75.194 X-Complaints-To: abuse@flash.net X-Trace: news.flash.net 976651219 216.215.75.194 (Tue, 12 Dec 2000 14:00:19 CST) NNTP-Posting-Date: Tue, 12 Dec 2000 14:00:19 CST Organization: FlashNet Communications, http://www.flash.net Xref: supernews.google.com comp.lang.ada:3004 Date: 2000-12-12T20:00:19+00:00 List-Id: "Ted Dennison" wrote in message news:915jl7$jt5$1@nnrp1.deja.com... : Since this problem should happen to anyone using "delay until" with an : iteration rate divisible by 3, and 60, 30, and 15Hz are common rates in : the industry, I can't be the first person to stumble on this problem. : How does everyone else handle it? For our systems, we usually pick a base iteration rate that can be accurately represented (64Hz is popular, although I've also seen 50Hz and 80Hz).