[Chimera-users] To get CHIMERA to work: "with stereo viz on new samsung "3D" LCD and quadro card"

Greg Couch gregc at cgl.ucsf.edu
Fri Mar 7 19:12:58 PST 2014


Chimera does stereo similarly to VMD-L.  VMD's QuadBuffer stereo is 
Chimera's sequential stereo. And chimera can generate various other 
stereo formats too.

So specially for case 1, Linux (Ubuntu) with "quadro card" -- you need 
to carefully read the NVIDIA README Appendix B, 
http://us.download.nvidia.com/XFree86/Linux-x86_64/331.49/README/xconfigoptions.html, 
and configure stereo in the X server correctly.  In your case, you would 
want Stereo 12 -- the HDMI 3D mode.  Note that is only available for 
NVIDIA Kepler and later GPUs, so a Quadro K600 or newer is required.

For case 2, MacPro/Mavericks with "a quadro card" -- it might 
accidentally work, but it's not worth the hassle.  The MacPro Quadro 
cards are pre-Kepler, and none of the Apple graphics drivers support 3D 
TVs, but sometimes the 3D TV can be tricked/forced into 3D mode if the 
video signal is just right.  If you are successful in getting it 
working, we'd like to hear about it, but this is not a good solution.

So what do we recommend?  For 3D TVs, the best price/performance is a 
Windows 8 system with a recent AMD Radeon (not FirePro) graphics card.  
Connect it to a recent 3D TV, switch Chimera's camera to sequential 
stereo mode, and it just works.  Couldn't be simpler.  NVIDIA GeForce 
graphics cards could work, but it appears that their graphics drivers 
only work with NVIDIA's 3D Vision setups.  That restriction might be 
gone by now, but you would need to test it to know for sure.  To make 
Windows more palpable, install the cygwin.com UNIX environment and its 
sshd server, so you can scp/rsync files to it. :-)

We also recommend recent AMD FirePro or NVIDIA Quadro graphics cards 
with Windows or Linux.  This has worked for many years and the drivers 
have been updated to work 3D TVs.  With the NVIDIA graphics driver, 
there are two places where stereo can be configured -- for Chimera, it 
is the stereo in the 3D graphics settings that are important, not the 3D 
Stereoscopic settings.

    HTH,

    Greg

On 03/07/2014 10:09 AM, Peter Engelhardt wrote:
> Dear Chimera,
>
> Sorry - Specification -  We naturally meant:
>
> CHIMERA to WORK with "stereo viz on new samsung "3D" LCD and quadro card"
> aqs.htm
>> Dear Chimera,
>>
>> We recently got a mail on instruction to install correct parameters 
>> to get VMD-L to work:
>>
>> "vmd-l: help with stereo viz on new samsung "3D" LCD and quadro card"
>>
>> Now we ask, do you have any suggestions to get "Samsung "3D" LCD and 
>> quadro card" and to get CHIMERA work not only for:
>>
>> 1. Linux (Ubuntu) with "quadro card"
>>
>> but also and on:
>>
>> 2. MacPro/Mavericks with "a quadro card"
>>
>> We thank you in advance
>>
>> Cheers
>> Peter et al.
>>
>> Quoting John Stone <johns at ks.uiuc.edu>:
>>
>> [Hide Quoted Text]
>> Carlos,
>>   Ah, I had missed the startup message you included when I read
>> your first note.  All of the VMD stereo modes other than "QuadBuffered"
>> are implemented by rendering code within VMD itself, and they do not
>> depend on the graphics driver or any special hardware capabilities. 
>> aqs.htm
>> So, the fact that you are able to use the "SideBySide" or other modes
>> just indicates that your TV can work with the VMD-supplied mode, but
>> that's separate from the issue of having the Quadro's stereo sync and
>> other features working.
>>
>> The VMD "QuadBuffered" stereo mode relies entirely on the GPU and
>> its driver for stereoscopic display.  This is the best mode to use
>> if you want the IR or RF stereo emitter to remain in proper sync with
>> the displayed images, but it requires that the GPU drivers and windowing
>> system be configured correctly, and that the GPU and driver will 
>> actually
>> support the target display.  If you're running on Linux, then the thing
>> to do is to check the contents of /var/log/Xorg.0.log and look for
>> the word "Stereo".  Here's an example of the kinds of output you're 
>> looking
>> for, as seen on a couple of our machines:
>>   (**) NVIDIA(1): Option "Stereo" "10"
>>   (**) NVIDIA(1): Option "ForceStereoFlipping" "true"
>>
>> Here's a machine that has stereo enabled:
>> (II) Setting vga for screen 0.
>> (II) Setting vga for screen 1.
>> (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
>> (==) NVIDIA(0): RGB weight 888
>> (==) NVIDIA(0): Default visual is TrueColor
>> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
>> (**) NVIDIA(0): Option "MetaModes" "2560x1600 +0+0"
>> (**) Feb 17 16:21:29 NVIDIA(0): Enabling 2D acceleration
>> (II) Feb 17 16:21:29 NVIDIA(0): Display (Samsung SyncMaster (DFP-0)) 
>> does not support NVIDIA
>> (II) Feb 17 16:21:29 NVIDIA(0):     3D Vision stereo.
>> (II) Feb 17 16:21:29 NVIDIA(0): NVIDIA GPU Quadro 7000 (GF110GL) at 
>> PCI:8:0:0 (GPU-0)
>> (--) Feb 17 16:21:29 NVIDIA(0): Memory: 6291456 kBytes
>> (--) Feb 17 16:21:29 NVIDIA(0): VideoBIOS: 70.10.4a.00.01
>> (II) Feb 17 16:21:29 NVIDIA(0): Detected PCI Express Link width: 16X
>> (--) Feb 17 16:21:29 NVIDIA(0): Valid display device(s) on Quadro 
>> 7000 at PCI:8:0:0
>> (--) Feb 17 16:21:29 NVIDIA(0):     CRT-0
>> (--) Feb 17 16:21:29 NVIDIA(0):     CRT-1
>> (--) Feb 17 16:21:29 NVIDIA(0):     Samsung SyncMaster (DFP-0) (boot, 
>> connected)
>> (--) Feb 17 16:21:29 NVIDIA(0):     DFP-1
>> (--) Feb 17 16:21:29 NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
>> (--) Feb 17 16:21:29 NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
>> (--) Feb 17 16:21:29 NVIDIA(0): Samsung SyncMaster (DFP-0): Internal 
>> Dual Link TMDS
>> (--) Feb 17 16:21:29 NVIDIA(0): Samsung SyncMaster (DFP-0): 330.0 MHz 
>> maximum pixel clock
>> (--) Feb 17 16:21:29 NVIDIA(0): DFP-1: Internal Single Link TMDS
>> (--) Feb 17 16:21:29 NVIDIA(0): DFP-1: 330.0 MHz maximum pixel clock
>> (**) Feb 17 16:21:29 NVIDIA(0): Using HorizSync/VertRefresh ranges 
>> from the EDID for display
>> (**) Feb 17 16:21:29 NVIDIA(0):     device Samsung SyncMaster (DFP-0) 
>> (Using EDID frequencies
>> (**) Feb 17 16:21:29 NVIDIA(0):     has been enabled on all display 
>> devices.)
>> (II) Feb 17 16:21:29 NVIDIA(0): Validated MetaModes:
>> (II) Feb 17 16:21:29 NVIDIA(0):     "2560x1600+0+0"
>> (II) Feb 17 16:21:29 NVIDIA(0): Virtual screen size determined to be 
>> 2560 x 1600
>> (--) Feb 17 16:21:29 NVIDIA(0): DPI set to (101, 101); computed from 
>> "UseEdidDpi" X config
>> (--) Feb 17 16:21:29 NVIDIA(0):     option
>> (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
>> (==) NVIDIA(1): RGB weight 888
>> (==) NVIDIA(1): Default visual is TrueColor
>> (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
>> (**) NVIDIA(1): Option "Stereo" "10"
>> (**) NVIDIA(1): Option "ForceStereoFlipping" "true"
>> (**) Feb 17 16:21:29 NVIDIA(1): USB IR emitter stereo requested
>> (WW) Feb 17 16:21:29 NVIDIA(1): For stereo to work with Xinerama, 
>> stereo X configuration
>> (WW) Feb 17 16:21:29 NVIDIA(1):     option should be enabled on all X 
>> screens in the X server.
>> (WW) Feb 17 16:21:29 NVIDIA(1):     Stereo is disabled on one (or 
>> more) X screens, while
>> (WW) Feb 17 16:21:29 NVIDIA(1):     Xinerama is enabled. Stereo 
>> visuals will not be
>> (WW) Feb 17 16:21:29 NVIDIA(1):     available.
>> (**) Feb 17 16:21:29 NVIDIA(1): OpenGL stereo forced
>> (**) NVIDIA(1): Option "MetaModes" "nvidia-auto-select +0+0"
>> (**) Feb 17 16:21:29 NVIDIA(1): Enabling 2D acceleration
>> (II) Feb 17 16:21:29 NVIDIA(0): Display (Acer HN274H (DFP-0)) 
>> supports NVIDIA 3D Vision
>> (II) Feb 17 16:21:29 NVIDIA(0):     stereo.
>> (II) Feb 17 16:21:29 NVIDIA(1): NVIDIA GPU Quadro 7000 (GF110GL) at 
>> PCI:9:0:0 (GPU-1)
>> (--) Feb 17 16:21:29 NVIDIA(1): Memory: 6291456 kBytes
>>
>>
>
>> Here's a machine that has stereo disabled currently:
>> (II) Setting vga for screen 0.
>> (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
>> (==) NVIDIA(0): RGB weight 888
>> (==) NVIDIA(0): Default visual is TrueColor
>> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
>> (**) NVIDIA(0): Option "Stereo" "0"
>> (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-3"
>> (**) Feb 17 17:20:19 NVIDIA(0): Stereo disabled by request
>> (**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select 
>> +2560+520, DFP-3: 2560x1600 +0+0; DFP-0: nvidia-auto-select +2560+0, 
>> DFP-3: 2560x1600 +0+0; DFP-0: nvidia-auto-select +0+0, DFP-3: 
>> nvidia-auto-select +1920+0"
>> (**) Feb 17 17:20:19 NVIDIA(0): Enabling 2D acceleration
>> (II) Feb 17 17:20:21 NVIDIA(0): Display (Acer HN274H (DFP-0)) 
>> supports NVIDIA 3D Vision
>> (II) Feb 17 17:20:21 NVIDIA(0):     stereo.
>> (II) Feb 17 17:20:21 NVIDIA(0): Display (HP ZR30w (DFP-3)) does not 
>> support NVIDIA 3D Vision
>> (II) Feb 17 17:20:21 NVIDIA(0):     stereo.
>> (II) Feb 17 17:20:21 NVIDIA(0): NVIDIA GPU Quadro K6000 (GK110BGL) at 
>> PCI:131:0:0 (GPU-0)
>> (--) Feb 17 17:20:21 NVIDIA(0): Memory: 12582912 kBytes
>> (--) Feb 17 17:20:21 NVIDIA(0): VideoBIOS: 80.80.16.00.01
>> (II) Feb 17 17:20:21 NVIDIA(0): Detected PCI Express Link width: 16X
>> (--) Feb 17 17:20:21 NVIDIA(0): Valid display device(s) on Quadro 
>> K6000 at PCI:131:0:0
>> (--) Feb 17 17:20:21 NVIDIA(0):     CRT-0
>> (--) Feb 17 17:20:21 NVIDIA(0):     Acer HN274H (DFP-0) (boot, 
>> connected)
>> (--) Feb 17 17:20:21 NVIDIA(0):     DFP-1
>> (--) Feb 17 17:20:21 NVIDIA(0):     DFP-2
>> (--) Feb 17 17:20:21 NVIDIA(0):     HP ZR30w (DFP-3) (connected)
>> (--) Feb 17 17:20:21 NVIDIA(0):     DFP-4
>> (--) Feb 17 17:20:21 NVIDIA(0):     DFP-5
>> (--) Feb 17 17:20:21 NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
>> (--) Feb 17 17:20:21 NVIDIA(0): Acer HN274H (DFP-0): Internal Dual 
>> Link TMDS
>> (--) Feb 17 17:20:21 NVIDIA(0): Acer HN274H (DFP-0): 330.0 MHz 
>> maximum pixel clo
>>
>
>



More information about the Chimera-users mailing list