From: Bernie Kirby (bernie++at++ecr.mu.oz.au)
Date: 07/22/2004 16:05:48
The silence is deafening.
So, I presume that it can't be done. Might as well send the machine back then.
--- > Compositor confusion. > > Does anyone have a performer3.1.1 app that uses > multiple compositors? > > We have an onyx4 with 3 compositors, but as yet, we've not been > able to effectively get a single performer app to 'drive' the > multiple compositors. > > One setup is this: > 2 cards each driving the 3 compositors with a 2x1 vert subdivision. > that is, 6 cards in total - 6 screens. > Using the example compositor.C code, and modifying it to use just the > first two pipes with the 2x1 vert subdivision, it works fine. > Extending this we tried creating 3 pfCompositors and added the pipes 0,1 > to the first one, 2,3 to the second and 4,5 to the third.... added channels as > needed, called setScreen as appropriate. Doesn't work. Only the first compositor > composits, and the others seem to just use the first pipe specified (maybe the > others - can't see them) and aren't being composited. > > This leads to questions: > > How do you tell a pfCompositor which actual compositor to use? > What are the 'rules' for addressing each compositor? > If I wanted to (for example) just run a graphics program on > (say) the third compositor using just it's two cards, how can I > stop performer opening a window on all the 'other' essentially unused pipes? > > Also, returning to the basic compositor.C example, we tried to just use > 2 pipes again, but called setScreen to point to some of the other screens > on another compositor. Again, didn't work. > > Other questions: > What is a software compositor? (see example perfly C code > pfCompositorMode(compositor, PFCOMP_SOFTWARE, 1); ) > > What are the PFCOMP_TYPEs PFCOMP_NxM_VERT and PFCOMP_NxM_HORIZ ? again, > used in perfly code, but not in man page. > > What does pfCompositorAddCompositor do? It's mentioned in the > man page, but there's no description. > > > Other problems: > Calling: > pfCompositorMode(comp, PFLOAD_BALANCE, PF_OFF /* or PF_ON */); > > Gives this message: > PF Warning: pfCompositor::setMode(), compState is NULL > and subsequently, a core dump. > > -- Two wrongs don't make a right ... but two wrights make an aeroplane.
This archive was generated by hypermail 2b29 : Thu Jul 22 2004 - 16:07:23 PDT