Gerhard Empl (100535.3606++at++CompuServe.COM)
18 Apr 96 20:44:01 EDT
(1) the texture "leaks out" (is applied to) other polygons as well
unless it is loaded as last one (thats a problem we can live with but
might be the reason for others).
(2) the frame rate drops down from 50 to 25 (or 60 to 30) when
applying the video. We then set the texture loading to be done only
once via performer and loaded the frame at the end of the drawing loop
via vl. Surprisingly this call only took a very short time, so the
Sirius board seems to synchronize itself with the video input blocking
the raster engine during that period.
here another formulation of our problems:
Problem 1:
Hardware: Onyx RE2 / 4 RM5 / Sirius Option
Library: Performer 2.0
Display: 50 Hz
Problem: We need to get a rendered scene with a live video-input at
50hz framerate.
What we do have now:
We got a stable framerate of 50 hz, but as soon as we
turn on the live video-input and drain it to the RM, the
framerate drops to appr. 25 hz.
We use SIR_TEX_PACK_RGB_5 packing for the tex drain.
What we tried:
We tried to draw only the Live-Video Texture --> still
appr. 25 hz framerate.
We tried interleaved and non-interleaved --> no effect
We tried PFTEX_LIST_APPLY and PFTEX_BASE_AUTO_SUBLOAD
We tried to reduce the texture size from 1024*1024 to
512*512 --> the machine crashed.
Question: Is there a way of getting Live-Video- input to texture memory with
a 50 frames/sec?
It seems to us that the video-transfer blocks the rendering
completely, because the sirius option has to wait until it gets a
complete frame.
We could also live with a quality penalty of the live input, but our
framerate has to be stable 50 hz.
Problem 2:
Hardware: Onyx RE2 / 4 RM5 / Sirius Option
Library: Performer 2.0
Display: 50 Hz
Problem: How do we get a texture on a loaded graphic e.g: .obj ?
Problem 3:
Hardware: Onyx RE2 / 4 RM5 / Sirius Option
Library: Performer 2.0
Display: 50 Hz
Problem: As soon as our Live-video-texture gets into view, it
sometimes happens that the video-input is drained to the wrong textures.
It seems that the sirius board sometimes writes into the wrong texture
memory adress.
Thank you very much for your help,
Gerhard Empl, R2
E-Mail: 100535.3606++at++compuserve.com
E-mail from: Gerhard Empl, 19-Apr-1996
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:44 PDT