From: Tom Flynn (flynnt++at++gmail.com)
Date: 07/22/2004 17:36:36
On Fri, 23 Jul 2004 09:05:48 +1000 (AEST), Bernie Kirby
<bernie++at++ecr.mu.oz.au> wrote:
>
> The silence is deafening.
huh? what? I can't hear you :)
seriously though, i've had my reply window open for like the past
four days trying to remember and answer some of your questions...have
a little patience :)
when you post a question to a mailing list, someone in the community
might repond, someone at sgi might respond, perhaps no one will
respond. you might argue that sgi should be paying closer attention
to the list, but i'm willing to bet that the pf engineers are trying
to answer as many questions on the list as they can while trying to
get their work done for the next pf release. if they happen to miss
you're question, there's no need to take it so personally.
if you need a deterministic response, sgi support should probably be
called. that way a bug that can be tracked will be filed, assigned,
and worked on by an engineer.
hope that helps,
tom
> 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.
>
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
> SIGGRAPH 2004 Friends of Performer BOF:
> Tuesday, August 10, 6pm - 8pm Wilshire Grand Hotel, Sierra Ballroom
> -----------------------------------------------------------------------
>
>
This archive was generated by hypermail 2b29 : Thu Jul 22 2004 - 17:38:47 PDT