Re: Actual 1280x1024_??s.vfo working on any system?

New Message Reply Date view Thread view Subject view Author view

Angus Dorbie (dorbie++at++sgi.com)
Tue, 06 Jul 1999 16:48:15 -0700

Brian Cooper wrote:
>
> Simon,
>
> I appreciate getting your assortment of vfo files to try. I also got one from
> Svend Tang-Peterson that allowed me to drive the 24 inch SGI monitor to 92 hz
> at 1280 by 1024 before crapping out. I will pursue getting a monitor with
> better horizontal frequency specs to attain less flicker in stereo mode.
>

You mean line rate right?

It's still not horizontal, it's vertical. Pixel clock is horizontal and
is just analog so isn't really an issue in terms of what the monitor can
sync to.

A better line rate may not be easy and won't be cheap. I saw one monitor
NASA (Ames I think??) brought in to SGI for some tests and was using to
visualize Sojourner data in stereo but it looked like very early
technology, with a big cable wrap bordering the screen. I don't have
contact information I just had a quick look they were working with
another engineer Trina Roy, but you might try contacting them
internally, I hope it wasn't you much as I'd enjoy the irony.

Cheers,Angus.

> You asked what I'm working on. I am using Iris Performer to create the latest
> generation of Rover Control Workstation software to drive the next Mars Rover
> (named Marie Curie) on Mars in 2001. I wrote the previous version using Open
> Inventor and got to drive Sojourner around during the Pathfinder Mission in
> 1997. I can give you more detail on why I'm using stereo for this via email
> if you want.
>
> Simon Mills wrote:
>
> > Which stereo vfo works depends on your monitor or display device. Doing
> > high res stereo demands a high maximum horizontal frequency. For example
> > I (the Simon mentioned below) was trying the wide 24" monitor that came
> > with our Onyx iR2. This has a max horizontal freq. of 96kHz (from the
> > specifications) and the best I managed was a 1280x1024_88s vfo. I'm now
> > using another (non-wide) monitor which can go up to 107 kHz horiz freq.
> > with a 1280x1024_96s vfo. This is better since the flicker is
> > considerably less. I'd really like 1280x1024_120s but that would require
> > a much more expensive projector & monitor.
> >
> > If you use the Video Format Compiler it should produce an info file
> > where you can find amongst other things the required horizontal
> > frequency ("Line analysis/Frequency"). You can then check this against
> > your display specifications to see if it will work.
> >
> > I've attached (gzip'ed tar file) a number of 1280x1024_nns.vfo files for
> > you to try. Hope it helps.
> >
> > P.S. I'm curious to know what you're working on since I think we're
> > working in very similar fields.
> >
> >
> > Regards, Simon
> > ________________________________________________________________________
> >
> > Simon C. Mills
> > Modelling & Simulation Section (TOS-EMM) Tel: +31 (0)71 565 3725
> > European Space Agency (ESA/ESTEC) Fax: +31 (0)71 565 5419
> > Postbus 299, 2200AG Noordwijk e-mail: simon++at++wgs.estec.esa.nl
> > The Netherlands http://www.estec.esa.nl/wmwww/EMM
> > ________________________________________________________________________
> >
> > ------------------------------------------------------------------------
> > Name: vfo.tar.gz
> > vfo.tar.gz Type: Unix Tape Archive (application/x-tar)
> > Encoding: base64
>
> --
> Brian K. Cooper - Jet Propulsion Lab - Pasadena CA - (818)-354-6298
> brian.cooper++at++jpl.nasa.gov
>
> Signature in Stereo (free view, diverge eyes):
> X X
> ZKSCZFYKDXNLORWVZKSCZFYKDXNLORWVZKSCZFYKDXNLORWVZKSCZFYKDXNLORWVZKSCZFYKDXNLORWV
> FWAVBMYQCLXJRGNTFWABMYQCQLXJRGTFWHABMYQJLXJVRGTFHABMYUQCLXVRGTFHOABYUQCLXWVRGTFH
> GRTUFHNBDTZFQATQGRUFHNBDTRZFQTQGRUYFHNBTRZFQETQGUYFHNBQTRZQEHTQGUYFNBXQTZQXEHTQG
> UQPDMMSKSJDOXNCSUQDMSMSKSJDONCVSUDMRSMKSZJDNCNVSDMSRSKSSZJNCFNVSDMSSKLSSJNSCFNVS
> JBAHAWXSALESVWDBJBHALWXSALESWDSBJHAQLWSAPLEWDKSBHAIQLSAMPLWDKSBHDAILSAMPLJWDKSBH
> ZXDEIWQMWXOUWGUKZXEIKWQMWXOUGUMKZEIFKWMWJXOGUQMKEIFKWMIWJXGUWQMKEIFWMKIWXGYUWQMK
> NWIZZTYXXEHTUVRTNWZZTYXXEKHTURTNWZLZTYXEKHTUQRTNZLSZTYXEKHUQGRTNZLSTYAXEHUXQGRTN
> UHOMSMYSZWBYWWYVUHOSMYSZTWBYWWVUHEOSMYSZWBYEWWVUEIOSMYSZWBEWWVUEZIOMYASZBEFWWVUE
> UMTMEBOJVWXKQLIIUMTMEBOJVWXKQLIIUMTMEBOJVWXKQLIIUMTMEBOJVWXKQLIIUMTMEBOJVWXKQLII
>
> -----------------------------------------------------------------------
> List Archives, FAQ, FTP: http://www.sgi.com/software/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com

-- 
For years now, whenever NT has been proven to have some debilitating
weakness we've heard from MS advocates that NT would catch up, there was
just an incredible faith in this OS and Microsoft's ability to somehow
get there. With the recent results of the Linux vs NT serving benchmark
that same attitude can be seen in the Linux community. The Linux folks
aren't too worried, "Sure the single threaded IP stack was slow but
it'll be fixed in the next release.", it's eerily familiar but I have
confidence in the Linux community's ability to remedy problems and I
don't groan in pain as I used to when Microsoft made similar claims.


For advanced 3D graphics Performer + OpenGL based examples and tutors:
http://www.dorbie.com/

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Tue Jul 06 1999 - 16:48:21 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.