Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!usc!elroy.jpl.nasa.gov!jarthur!nntp-server.caltech.edu!laguna.ccsf.caltech.edu!andrey From: andrey@beyond.cs.caltech.edu (Andre T. Yew) Newsgroups: comp.sys.sgi Subject: Summary: flushing the pipeline Message-ID: Date: 30 Aug 90 20:39:28 GMT Sender: news@laguna.ccsf.caltech.edu Distribution: comp Organization: California Institute of Technology Lines: 20 Thanks to all of the people who responded. Most suggestions for flushing the pipeline were generally the same -- give the pipeline something to do which on completion would guarantee that the pipeline is empty. Suggestions ranged from using gsync(), swapbuffer(), finish() ... to readrect() and feedback. I ended up calling finish() first then gsync() (call me paranoid :-). Apparently, that helped my problem, but did not fully solve it. That is, I'm still experiencing some jitter in my recordings periodically and in the same locations, and I doubt it's the recorder's fault. I don't suppose the 'Pipeline has any round-off problems? Oh well, back to the drawing board. Thanks again, everyone. -- Andre Yew andrey@through.cs.caltech.edu (131.215.128.1)