Jim Helman (jimh++at++surreal)
Mon, 20 Nov 95 13:22:06 -0800
Of these two, the shared memory approach is probably preferable in
terms of throughput and consistent latencies. One has a lot more
real-time control over processing when X isn't involved.
> I have been working with the Polhemus Fastrak in my Performer
> application. I set up the Fastrak so that it outputs a continuous
> stream of binary data and I sproc a lightweight process from the APP
> to process this stream and place that data in buffers that can be
> accessed by the APP. If this sounds like something you want to do, it
> can be no different from writing a device driver for a non-Performer
> application.
This is a good approach. Ideally, you'd like to sync the Polhemus to
video so that its frame rate doesn't beat with the rendering frame rate
and cause variations in latency.
rgds,
-jim helman
jimh++at++surreal.asd.sgi.com
415/933-1151
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:03 PDT