RE: [info-performer] Re: Onyx4, multiple compositors.

Date view Thread view Subject view Author view

From: Gordon Tomlinson (gordon++at++gordon-tomlinson.com)
Date: 07/22/2004 18:30:44


Hi

If your expecting prompt answers on a user forum then your most likely
In for a shock I would suggest that you contact SGI directly or get the
Rep that is selling/sold you the Iron to get back to you with an answer
to your question.

You cannot expect prompt answers on a user forum like this, you
Might want it ;) but you probably will not get it ;)

Use you support contract with SGI, I have always found them very
Good and quick, when I was working with SGI Iron..

Best Regards
 
Gordon
 ___________________________________

Gordon Tomlinson

Email gordon++at++gordon-tomlinson.com
IM gordon++at++thesmeghead.com
AIM englishsmeghead
YIM theenglishsmeghead

-----Original Message-----
From: owner-info-performer++at++performer.engr.sgi.com
[mailto:owner-info-performer++at++performer.engr.sgi.com] On Behalf Of Bernie
Kirby
Sent: 23 July 2004 00:06
To: info-performer++at++sgi.com
Subject: [info-performer] Re: Onyx4, multiple compositors.

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.

----------------------------------------------------------------------- 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 -----------------------------------------------------------------------


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Jul 22 2004 - 18:34:01 PDT