# leopard compatibility

**URL:** <https://psychtoolbox.discourse.group/t/leopard-compatibility/1895>\
**Category:** Uncategorized\
**Created:** [October 23, 2007, 6:04pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895 "2007-10-23T18:04:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rl867](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@rl867](https://psychtoolbox.discourse.group/u/rl867)\
**Post date:** [October 23, 2007, 6:04pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/1 "2007-10-23T18:04:09Z")

</div>

Hello,  
  
Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
compatible with Psychophysics Toolbox? Do any of the changes change   
things in a way that could cause problems?  
  
Thanks,  
Rob  
  
--   
[http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [October 24, 2007, 4:16pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/2 "2007-10-24T16:16:42Z")

</div>

Given that Leopard isn't available yet, no one can know.  
  
But from the technical specs that are available at the moment,  
i wouldn't expect any incompatibilities by design.  
  
Of course its always possible that Leopord contains some  
new bugs along with all the new features and these bugs  
could interfere, but that wouldn't be by design.  
  
I hope that there will be a few significant improvements,  
especially in the areas of anti-aliasing and fast creation  
of high-precision/HDR stimuli. Tiger lacks a few useful  
functions there which are available on Linux and Windows  
since over a year. Timing behaviour is also an area where  
i would expect some further improvements, given the  
redesigned scheduler (now optimized for multi-cores),  
although the quality of timing of Tiger was already lightyears  
ahead of the beautiful products from Redmond.  
  
-mario  
  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Robert Levy \<levy@...\> wrote:  
> \>  
> \> Hello,  
> \>   
> \> Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
> \> compatible with Psychophysics Toolbox? Do any of the changes change   
> \> things in a way that could cause problems?  
> \>   
> \> Thanks,  
> \> Rob  
> \>   
> \> --   
> \> [http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)  
> \>

---

<div class="post-metadata">

**Author:** ![aseitz](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@aseitz](https://psychtoolbox.discourse.group/u/aseitz)\
**Post date:** [October 28, 2007, 3:06am UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/3 "2007-10-28T03:06:33Z")

</div>

OK, I just installed Leopard (on my macbook pro) and so far psychtoolbox seems to be   
running well. I am not sure if I would recommend upgrading experimental machines to   
Leopard quite yet, but at least it seems fine for code development.  
  
If anyone wants me to test something specific let me know (so far I have tested dotdemo   
as well as some of my own experimental programs).  
  
Best,  
  
-Aaron  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@...\> wrote:  
> \>  
> \> Given that Leopard isn't available yet, no one can know.  
> \>   
> \> But from the technical specs that are available at the moment,  
> \> i wouldn't expect any incompatibilities by design.  
> \>   
> \> Of course its always possible that Leopord contains some  
> \> new bugs along with all the new features and these bugs  
> \> could interfere, but that wouldn't be by design.  
> \>   
> \> I hope that there will be a few significant improvements,  
> \> especially in the areas of anti-aliasing and fast creation  
> \> of high-precision/HDR stimuli. Tiger lacks a few useful  
> \> functions there which are available on Linux and Windows  
> \> since over a year. Timing behaviour is also an area where  
> \> i would expect some further improvements, given the  
> \> redesigned scheduler (now optimized for multi-cores),  
> \> although the quality of timing of Tiger was already lightyears  
> \> ahead of the beautiful products from Redmond.  
> \>   
> \> -mario  
> \>   
> \>   
> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Robert Levy \<levy@\> wrote:  
> \> \>  
> \> \> Hello,  
> \> \>   
> \> \> Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
> \> \> compatible with Psychophysics Toolbox? Do any of the changes change   
> \> \> things in a way that could cause problems?  
> \> \>   
> \> \> Thanks,  
> \> \> Rob  
> \> \>   
> \> \> --   
> \> \> [http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)  
> \> \>  
> \>

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [October 29, 2007, 5:38pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/4 "2007-10-29T17:38:51Z")

</div>

Oops, typo: Also post the full output of DotDemo.m please.  
-mario  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@...\> wrote:  
> \>  
> \> Good to know.  
> \>   
> \> Can you run "BitsPlusImagingPipelineTest" and post its output?  
> \> And also post the Radeon X1600 or with NVidia Geforce8600M?  
> \>   
> \> thanks,  
> \> -mario  
> \>   
> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "aseitz" \<aseitz@\> wrote:  
> \> \>  
> \> \> OK, I just installed Leopard (on my macbook pro) and so far psychtoolbox seems to   
> be   
> \> \> running well. I am not sure if I would recommend upgrading experimental machines   
> to   
> \> \> Leopard quite yet, but at least it seems fine for code development.  
> \> \>   
> \> \> If anyone wants me to test something specific let me know (so far I have tested   
> dotdemo   
> \> \> as well as some of my own experimental programs).  
> \> \>   
> \> \> Best,  
> \> \>   
> \> \> -Aaron  
> \> \>   
> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \> \>  
> \> \> \> Given that Leopard isn't available yet, no one can know.  
> \> \> \>   
> \> \> \> But from the technical specs that are available at the moment,  
> \> \> \> i wouldn't expect any incompatibilities by design.  
> \> \> \>   
> \> \> \> Of course its always possible that Leopord contains some  
> \> \> \> new bugs along with all the new features and these bugs  
> \> \> \> could interfere, but that wouldn't be by design.  
> \> \> \>   
> \> \> \> I hope that there will be a few significant improvements,  
> \> \> \> especially in the areas of anti-aliasing and fast creation  
> \> \> \> of high-precision/HDR stimuli. Tiger lacks a few useful  
> \> \> \> functions there which are available on Linux and Windows  
> \> \> \> since over a year. Timing behaviour is also an area where  
> \> \> \> i would expect some further improvements, given the  
> \> \> \> redesigned scheduler (now optimized for multi-cores),  
> \> \> \> although the quality of timing of Tiger was already lightyears  
> \> \> \> ahead of the beautiful products from Redmond.  
> \> \> \>   
> \> \> \> -mario  
> \> \> \>   
> \> \> \>   
> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Robert Levy \<levy@\> wrote:  
> \> \> \> \>  
> \> \> \> \> Hello,  
> \> \> \> \>   
> \> \> \> \> Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
> \> \> \> \> compatible with Psychophysics Toolbox? Do any of the changes change   
> \> \> \> \> things in a way that could cause problems?  
> \> \> \> \>   
> \> \> \> \> Thanks,  
> \> \> \> \> Rob  
> \> \> \> \>   
> \> \> \> \> --   
> \> \> \> \> [http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)  
> \> \> \> \>  
> \> \> \>  
> \> \>  
> \>

---

<div class="post-metadata">

**Author:** ![aseitz](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@aseitz](https://psychtoolbox.discourse.group/u/aseitz)\
**Post date:** [October 30, 2007, 6:23pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/5 "2007-10-30T18:23:55Z")

</div>

Hi Mario,  
  
My Macbook Pro has the GeForce 8600M GT video card with 256MB of RAM. I am using   
matlab 7.5.0.338 (R2007b) and PsychtoolboxVersion 3.0.8 - Flavor: beta - Corresponds to   
SVN Revision 884.  
  
I have included the outputs from DotDemo and BitsPlusImagingPipelineTest below.  
  
Best,  
  
-Aaron  
  
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
Here is the output from DotDemo.m  
  
doublebuffer =  
 1  
  
  
PTB-INFO: This is the OpenGL-Psychtoolbox version 3.0.8. Type 'PsychtoolboxVersion' for   
more detailed version information.  
PTB-INFO: Psychtoolbox is licensed to you under terms of the GNU General Public License   
(GPL). See file 'License.txt' in the  
PTB-INFO: Psychtoolbox root folder for a copy of the GPL license.  
  
  
  
OpenGL-Extensions are: GL\_ARB\_transpose\_matrix GL\_ARB\_vertex\_program   
GL\_ARB\_vertex\_blend GL\_ARB\_window\_pos GL\_ARB\_shader\_objects GL\_ARB\_vertex\_shader   
GL\_EXT\_multi\_draw\_arrays GL\_EXT\_clip\_volume\_hint GL\_EXT\_rescale\_normal   
GL\_EXT\_draw\_range\_elements GL\_EXT\_fog\_coord GL\_EXT\_gpu\_program\_parameters   
GL\_APPLE\_client\_storage GL\_APPLE\_specular\_vector GL\_APPLE\_transform\_hint   
GL\_APPLE\_packed\_pixels GL\_APPLE\_fence GL\_APPLE\_vertex\_array\_object   
GL\_APPLE\_vertex\_program\_evaluators GL\_APPLE\_element\_array GL\_APPLE\_flush\_render   
GL\_APPLE\_aux\_depth\_stencil GL\_NV\_texgen\_reflection GL\_NV\_light\_max\_exponent   
GL\_IBM\_rasterpos\_clip GL\_SGIS\_generate\_mipmap GL\_ARB\_shading\_language\_100   
GL\_ARB\_imaging GL\_ARB\_point\_parameters GL\_ARB\_texture\_env\_crossbar   
GL\_ARB\_texture\_border\_clamp GL\_ARB\_multitexture GL\_ARB\_texture\_env\_add   
GL\_ARB\_texture\_cube\_map GL\_ARB\_texture\_env\_dot3 GL\_ARB\_multisample   
GL\_ARB\_texture\_env\_combine GL\_ARB\_texture\_compression   
GL\_ARB\_texture\_mirrored\_repeat GL\_ARB\_shadow GL\_ARB\_depth\_texture   
GL\_ARB\_fragment\_program GL\_ARB\_fragment\_program\_shadow GL\_ARB\_fragment\_shader   
GL\_ARB\_occlusion\_query GL\_ARB\_point\_sprite GL\_ARB\_texture\_non\_power\_of\_two   
GL\_ARB\_vertex\_buffer\_object GL\_ARB\_pixel\_buffer\_object GL\_ARB\_draw\_buffers   
GL\_ARB\_shader\_texture\_lod GL\_EXT\_compiled\_vertex\_array GL\_EXT\_framebuffer\_object   
GL\_EXT\_texture\_rectangle GL\_ARB\_texture\_rectangle GL\_EXT\_texture\_env\_add   
GL\_EXT\_blend\_color GL\_EXT\_blend\_minmax GL\_EXT\_blend\_subtract   
GL\_EXT\_texture\_lod\_bias GL\_EXT\_abgr GL\_EXT\_bgra GL\_EXT\_stencil\_wrap   
GL\_EXT\_texture\_filter\_anisotropic GL\_EXT\_secondary\_color GL\_EXT\_blend\_func\_separate   
GL\_EXT\_shadow\_funcs GL\_EXT\_stencil\_two\_side GL\_EXT\_depth\_bounds\_test   
GL\_EXT\_texture\_compression\_s3tc GL\_EXT\_texture\_compression\_dxt1   
GL\_EXT\_texture\_sRGB GL\_EXT\_blend\_equation\_separate GL\_EXT\_texture\_mirror\_clamp   
GL\_EXT\_packed\_depth\_stencil GL\_EXT\_geometry\_shader4 GL\_EXT\_transform\_feedback   
GL\_EXT\_gpu\_shader4 GL\_APPLE\_flush\_buffer\_range GL\_APPLE\_ycbcr\_422   
GL\_APPLE\_vertex\_array\_range GL\_APPLE\_texture\_range GL\_APPLE\_float\_pixels   
GL\_ATI\_texture\_float GL\_ARB\_texture\_float GL\_ARB\_half\_float\_pixel GL\_APPLE\_pixel\_buffer   
GL\_APPLE\_object\_purgeable GL\_NV\_point\_sprite GL\_NV\_register\_combiners   
GL\_NV\_register\_combiners2 GL\_NV\_blend\_square GL\_NV\_texture\_shader   
GL\_NV\_texture\_shader2 GL\_NV\_texture\_shader3 GL\_NV\_fog\_distance GL\_NV\_depth\_clamp   
GL\_NV\_multisample\_filter\_hint GL\_NV\_fragment\_program\_option   
GL\_NV\_fragment\_program2 GL\_NV\_vertex\_program2\_option GL\_NV\_vertex\_program3   
GL\_ATI\_texture\_mirror\_once GL\_ATI\_texture\_env\_combine3 GL\_ATI\_separate\_stencil   
GL\_SGIS\_texture\_edge\_clamp GL\_SGIS\_texture\_lod   
  
  
  
PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: NVIDIA GeForce 8600M GT OpenGL   
Engine :: 2.0 NVIDIA-1.5.16  
PTB-INFO: Renderer has 256 MB of VRAM and a maximum 242 MB of texture memory.  
PTB-Info: VBL startline = 900 , VBL Endline = 900  
PTB-Info: Measured monitor refresh interval from beamposition = 16.742675 ms   
[59.727612 Hz].  
PTB-Info: Will use beamposition query for accurate Flip time stamping.  
PTB-Info: Measured monitor refresh interval from VBLsync = 16.750103 ms [59.701124   
Hz]. (50 valid samples taken, stddev=0.065576 ms.)  
PTB-Info: Small deviations between reported values are normal and no reason to worry.  
  
  
WARNING: PTB's Screen('Flip') command missed the requested stimulus presentation   
deadline  
WARNING: a total of 1 times during this session!  
  
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
  
And here is the output from BitsPlusImagingPipelineTest  
  
Converting test stim to color++ format  
PTB-WARNING: Switching and query of color clamping via glClampColorARB unsupported   
by your graphics hardware.  
PTB-WARNING: Could not disable color value clamping as requested. Unsupported by your   
graphics hardware?  
Building a fragment shader:Reading shader from file   
/Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/Bits++\_Color++\_Formattin  
gShader.frag.txt ...  
  
  
WARNING: PTB's Screen('Flip') command missed the requested stimulus presentation   
deadline  
WARNING: a total of 1 times during this session!  
  
Maximum raw data difference: red= 0.000000 green = 0.000000 blue = 0.000000  
  
  
------------------- Color++ test success! --------------------------------  
-----  
  
Converting test stim to mono++ format  
PTB-WARNING: Switching and query of color clamping via glClampColorARB unsupported   
by your graphics hardware.  
PTB-WARNING: Could not disable color value clamping as requested. Unsupported by your   
graphics hardware?  
Building a fragment shader:Reading shader from file   
/Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/Bits++\_Mono++\_Formattin  
gShader.frag.txt ...  
  
Maximum raw data difference: red= 0.000000 green = 0.000000 blue = 0.000000  
  
  
------------------- Mono++ test success! --------------------------------  
-----  
  
BitsPlusPlus imaging pipeline verified to work correctly. Validation info stored.  
  
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
  
  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@...\> wrote:  
> \>  
> \> Oops, typo: Also post the full output of DotDemo.m please.  
> \> -mario  
> \>   
> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \>  
> \> \> Good to know.  
> \> \>   
> \> \> Can you run "BitsPlusImagingPipelineTest" and post its output?  
> \> \> And also post the Radeon X1600 or with NVidia Geforce8600M?  
> \> \>   
> \> \> thanks,  
> \> \> -mario  
> \> \>   
> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "aseitz" \<aseitz@\> wrote:  
> \> \> \>  
> \> \> \> OK, I just installed Leopard (on my macbook pro) and so far psychtoolbox seems to   
> \> be   
> \> \> \> running well. I am not sure if I would recommend upgrading experimental   
> machines   
> \> to   
> \> \> \> Leopard quite yet, but at least it seems fine for code development.  
> \> \> \>   
> \> \> \> If anyone wants me to test something specific let me know (so far I have tested   
> \> dotdemo   
> \> \> \> as well as some of my own experimental programs).  
> \> \> \>   
> \> \> \> Best,  
> \> \> \>   
> \> \> \> -Aaron  
> \> \> \>   
> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \> \> \>  
> \> \> \> \> Given that Leopard isn't available yet, no one can know.  
> \> \> \> \>   
> \> \> \> \> But from the technical specs that are available at the moment,  
> \> \> \> \> i wouldn't expect any incompatibilities by design.  
> \> \> \> \>   
> \> \> \> \> Of course its always possible that Leopord contains some  
> \> \> \> \> new bugs along with all the new features and these bugs  
> \> \> \> \> could interfere, but that wouldn't be by design.  
> \> \> \> \>   
> \> \> \> \> I hope that there will be a few significant improvements,  
> \> \> \> \> especially in the areas of anti-aliasing and fast creation  
> \> \> \> \> of high-precision/HDR stimuli. Tiger lacks a few useful  
> \> \> \> \> functions there which are available on Linux and Windows  
> \> \> \> \> since over a year. Timing behaviour is also an area where  
> \> \> \> \> i would expect some further improvements, given the  
> \> \> \> \> redesigned scheduler (now optimized for multi-cores),  
> \> \> \> \> although the quality of timing of Tiger was already lightyears  
> \> \> \> \> ahead of the beautiful products from Redmond.  
> \> \> \> \>   
> \> \> \> \> -mario  
> \> \> \> \>   
> \> \> \> \>   
> \> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Robert Levy \<levy@\> wrote:  
> \> \> \> \> \>  
> \> \> \> \> \> Hello,  
> \> \> \> \> \>   
> \> \> \> \> \> Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
> \> \> \> \> \> compatible with Psychophysics Toolbox? Do any of the changes change   
> \> \> \> \> \> things in a way that could cause problems?  
> \> \> \> \> \>   
> \> \> \> \> \> Thanks,  
> \> \> \> \> \> Rob  
> \> \> \> \> \>   
> \> \> \> \> \> --   
> \> \> \> \> \> [http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)  
> \> \> \> \> \>  
> \> \> \> \>  
> \> \> \>  
> \> \>  
> \>

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [October 31, 2007, 6:40pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/6 "2007-10-31T18:40:57Z")

</div>

thanks for doing this. Could you also run StereoDemo(1) and tell  
me if it properly switches into frame sequential stereo mode,  
ie. you see the flickering/alternating stereo stim and the sync  
line drawn at the bottom of your screen?  
  
thanks,  
-mario  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "aseitz" \<aseitz@...\> wrote:  
> \>  
> \> Hi Mario,  
> \>   
> \> My Macbook Pro has the GeForce 8600M GT video card with 256MB of RAM. I am using   
> \> matlab 7.5.0.338 (R2007b) and PsychtoolboxVersion 3.0.8 - Flavor: beta - Corresponds   
> to   
> \> SVN Revision 884.  
> \>   
> \> I have included the outputs from DotDemo and BitsPlusImagingPipelineTest below.  
> \>   
> \> Best,  
> \>   
> \> -Aaron  
> \>   
> \> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> \> Here is the output from DotDemo.m  
> \>   
> \> doublebuffer =  
> \> 1  
> \>   
> \>   
> \> PTB-INFO: This is the OpenGL-Psychtoolbox version 3.0.8. Type 'PsychtoolboxVersion'   
> for   
> \> more detailed version information.  
> \> PTB-INFO: Psychtoolbox is licensed to you under terms of the GNU General Public   
> License   
> \> (GPL). See file 'License.txt' in the  
> \> PTB-INFO: Psychtoolbox root folder for a copy of the GPL license.  
> \>   
> \>   
> \>   
> \> OpenGL-Extensions are: GL\_ARB\_transpose\_matrix GL\_ARB\_vertex\_program   
> \> GL\_ARB\_vertex\_blend GL\_ARB\_window\_pos GL\_ARB\_shader\_objects   
> GL\_ARB\_vertex\_shader   
> \> GL\_EXT\_multi\_draw\_arrays GL\_EXT\_clip\_volume\_hint GL\_EXT\_rescale\_normal   
> \> GL\_EXT\_draw\_range\_elements GL\_EXT\_fog\_coord GL\_EXT\_gpu\_program\_parameters   
> \> GL\_APPLE\_client\_storage GL\_APPLE\_specular\_vector GL\_APPLE\_transform\_hint   
> \> GL\_APPLE\_packed\_pixels GL\_APPLE\_fence GL\_APPLE\_vertex\_array\_object   
> \> GL\_APPLE\_vertex\_program\_evaluators GL\_APPLE\_element\_array GL\_APPLE\_flush\_render   
> \> GL\_APPLE\_aux\_depth\_stencil GL\_NV\_texgen\_reflection GL\_NV\_light\_max\_exponent   
> \> GL\_IBM\_rasterpos\_clip GL\_SGIS\_generate\_mipmap GL\_ARB\_shading\_language\_100   
> \> GL\_ARB\_imaging GL\_ARB\_point\_parameters GL\_ARB\_texture\_env\_crossbar   
> \> GL\_ARB\_texture\_border\_clamp GL\_ARB\_multitexture GL\_ARB\_texture\_env\_add   
> \> GL\_ARB\_texture\_cube\_map GL\_ARB\_texture\_env\_dot3 GL\_ARB\_multisample   
> \> GL\_ARB\_texture\_env\_combine GL\_ARB\_texture\_compression   
> \> GL\_ARB\_texture\_mirrored\_repeat GL\_ARB\_shadow GL\_ARB\_depth\_texture   
> \> GL\_ARB\_fragment\_program GL\_ARB\_fragment\_program\_shadow   
> GL\_ARB\_fragment\_shader   
> \> GL\_ARB\_occlusion\_query GL\_ARB\_point\_sprite GL\_ARB\_texture\_non\_power\_of\_two   
> \> GL\_ARB\_vertex\_buffer\_object GL\_ARB\_pixel\_buffer\_object GL\_ARB\_draw\_buffers   
> \> GL\_ARB\_shader\_texture\_lod GL\_EXT\_compiled\_vertex\_array GL\_EXT\_framebuffer\_object   
> \> GL\_EXT\_texture\_rectangle GL\_ARB\_texture\_rectangle GL\_EXT\_texture\_env\_add   
> \> GL\_EXT\_blend\_color GL\_EXT\_blend\_minmax GL\_EXT\_blend\_subtract   
> \> GL\_EXT\_texture\_lod\_bias GL\_EXT\_abgr GL\_EXT\_bgra GL\_EXT\_stencil\_wrap   
> \> GL\_EXT\_texture\_filter\_anisotropic GL\_EXT\_secondary\_color GL\_EXT\_blend\_func\_separate   
> \> GL\_EXT\_shadow\_funcs GL\_EXT\_stencil\_two\_side GL\_EXT\_depth\_bounds\_test   
> \> GL\_EXT\_texture\_compression\_s3tc GL\_EXT\_texture\_compression\_dxt1   
> \> GL\_EXT\_texture\_sRGB GL\_EXT\_blend\_equation\_separate GL\_EXT\_texture\_mirror\_clamp   
> \> GL\_EXT\_packed\_depth\_stencil GL\_EXT\_geometry\_shader4 GL\_EXT\_transform\_feedback   
> \> GL\_EXT\_gpu\_shader4 GL\_APPLE\_flush\_buffer\_range GL\_APPLE\_ycbcr\_422   
> \> GL\_APPLE\_vertex\_array\_range GL\_APPLE\_texture\_range GL\_APPLE\_float\_pixels   
> \> GL\_ATI\_texture\_float GL\_ARB\_texture\_float GL\_ARB\_half\_float\_pixel   
> GL\_APPLE\_pixel\_buffer   
> \> GL\_APPLE\_object\_purgeable GL\_NV\_point\_sprite GL\_NV\_register\_combiners   
> \> GL\_NV\_register\_combiners2 GL\_NV\_blend\_square GL\_NV\_texture\_shader   
> \> GL\_NV\_texture\_shader2 GL\_NV\_texture\_shader3 GL\_NV\_fog\_distance   
> GL\_NV\_depth\_clamp   
> \> GL\_NV\_multisample\_filter\_hint GL\_NV\_fragment\_program\_option   
> \> GL\_NV\_fragment\_program2 GL\_NV\_vertex\_program2\_option GL\_NV\_vertex\_program3   
> \> GL\_ATI\_texture\_mirror\_once GL\_ATI\_texture\_env\_combine3 GL\_ATI\_separate\_stencil   
> \> GL\_SGIS\_texture\_edge\_clamp GL\_SGIS\_texture\_lod   
> \>   
> \>   
> \>   
> \> PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: NVIDIA GeForce 8600M GT   
> OpenGL   
> \> Engine :: 2.0 NVIDIA-1.5.16  
> \> PTB-INFO: Renderer has 256 MB of VRAM and a maximum 242 MB of texture memory.  
> \> PTB-Info: VBL startline = 900 , VBL Endline = 900  
> \> PTB-Info: Measured monitor refresh interval from beamposition = 16.742675 ms   
> \> [59.727612 Hz].  
> \> PTB-Info: Will use beamposition query for accurate Flip time stamping.  
> \> PTB-Info: Measured monitor refresh interval from VBLsync = 16.750103 ms [59.701124   
> \> Hz]. (50 valid samples taken, stddev=0.065576 ms.)  
> \> PTB-Info: Small deviations between reported values are normal and no reason to worry.  
> \>   
> \>   
> \> WARNING: PTB's Screen('Flip') command missed the requested stimulus presentation   
> \> deadline  
> \> WARNING: a total of 1 times during this session!  
> \>   
> \> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> \>   
> \> And here is the output from BitsPlusImagingPipelineTest  
> \>   
> \> Converting test stim to color++ format  
> \> PTB-WARNING: Switching and query of color clamping via glClampColorARB   
> unsupported   
> \> by your graphics hardware.  
> \> PTB-WARNING: Could not disable color value clamping as requested. Unsupported by   
> your   
> \> graphics hardware?  
> \> Building a fragment shader:Reading shader from file   
> \> /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/Bits++\_Color+  
> +\_Formattin  
> \> gShader.frag.txt ...  
> \>   
> \>   
> \> WARNING: PTB's Screen('Flip') command missed the requested stimulus presentation   
> \> deadline  
> \> WARNING: a total of 1 times during this session!  
> \>   
> \> Maximum raw data difference: red= 0.000000 green = 0.000000 blue = 0.000000  
> \>   
> \>   
> \> ------------------- Color++ test success! --------------------------------  
> \> -----  
> \>   
> \> Converting test stim to mono++ format  
> \> PTB-WARNING: Switching and query of color clamping via glClampColorARB   
> unsupported   
> \> by your graphics hardware.  
> \> PTB-WARNING: Could not disable color value clamping as requested. Unsupported by   
> your   
> \> graphics hardware?  
> \> Building a fragment shader:Reading shader from file   
> \> /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/Bits++\_Mono+  
> +\_Formattin  
> \> gShader.frag.txt ...  
> \>   
> \> Maximum raw data difference: red= 0.000000 green = 0.000000 blue = 0.000000  
> \>   
> \>   
> \> ------------------- Mono++ test success! --------------------------------  
> \> -----  
> \>   
> \> BitsPlusPlus imaging pipeline verified to work correctly. Validation info stored.  
> \>   
> \> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> \>   
> \>   
> \>   
> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \>  
> \> \> Oops, typo: Also post the full output of DotDemo.m please.  
> \> \> -mario  
> \> \>   
> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \> \>  
> \> \> \> Good to know.  
> \> \> \>   
> \> \> \> Can you run "BitsPlusImagingPipelineTest" and post its output?  
> \> \> \> And also post the Radeon X1600 or with NVidia Geforce8600M?  
> \> \> \>   
> \> \> \> thanks,  
> \> \> \> -mario  
> \> \> \>   
> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "aseitz" \<aseitz@\> wrote:  
> \> \> \> \>  
> \> \> \> \> OK, I just installed Leopard (on my macbook pro) and so far psychtoolbox seems   
> to   
> \> \> be   
> \> \> \> \> running well. I am not sure if I would recommend upgrading experimental   
> \> machines   
> \> \> to   
> \> \> \> \> Leopard quite yet, but at least it seems fine for code development.  
> \> \> \> \>   
> \> \> \> \> If anyone wants me to test something specific let me know (so far I have tested   
> \> \> dotdemo   
> \> \> \> \> as well as some of my own experimental programs).  
> \> \> \> \>   
> \> \> \> \> Best,  
> \> \> \> \>   
> \> \> \> \> -Aaron  
> \> \> \> \>   
> \> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario Kleiner" \<mario.kleiner@\> wrote:  
> \> \> \> \> \>  
> \> \> \> \> \> Given that Leopard isn't available yet, no one can know.  
> \> \> \> \> \>   
> \> \> \> \> \> But from the technical specs that are available at the moment,  
> \> \> \> \> \> i wouldn't expect any incompatibilities by design.  
> \> \> \> \> \>   
> \> \> \> \> \> Of course its always possible that Leopord contains some  
> \> \> \> \> \> new bugs along with all the new features and these bugs  
> \> \> \> \> \> could interfere, but that wouldn't be by design.  
> \> \> \> \> \>   
> \> \> \> \> \> I hope that there will be a few significant improvements,  
> \> \> \> \> \> especially in the areas of anti-aliasing and fast creation  
> \> \> \> \> \> of high-precision/HDR stimuli. Tiger lacks a few useful  
> \> \> \> \> \> functions there which are available on Linux and Windows  
> \> \> \> \> \> since over a year. Timing behaviour is also an area where  
> \> \> \> \> \> i would expect some further improvements, given the  
> \> \> \> \> \> redesigned scheduler (now optimized for multi-cores),  
> \> \> \> \> \> although the quality of timing of Tiger was already lightyears  
> \> \> \> \> \> ahead of the beautiful products from Redmond.  
> \> \> \> \> \>   
> \> \> \> \> \> -mario  
> \> \> \> \> \>   
> \> \> \> \> \>   
> \> \> \> \> \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), Robert Levy \<levy@\> wrote:  
> \> \> \> \> \> \>  
> \> \> \> \> \> \> Hello,  
> \> \> \> \> \> \>   
> \> \> \> \> \> \> Does anyone know whether MacOS-X 10.5 (leopard) will be immediately   
> \> \> \> \> \> \> compatible with Psychophysics Toolbox? Do any of the changes change   
> \> \> \> \> \> \> things in a way that could cause problems?  
> \> \> \> \> \> \>   
> \> \> \> \> \> \> Thanks,  
> \> \> \> \> \> \> Rob  
> \> \> \> \> \> \>   
> \> \> \> \> \> \> --   
> \> \> \> \> \> \> [http://www.nmr.mgh.harvard.edu/~levy/](http://www.nmr.mgh.harvard.edu/~levy/)  
> \> \> \> \> \> \>  
> \> \> \> \> \>  
> \> \> \> \>  
> \> \> \>  
> \> \>  
> \>

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [November 2, 2007, 8:43pm UTC](https://psychtoolbox.discourse.group/t/leopard-compatibility/1895/7 "2007-11-02T20:43:44Z")

</div>

Apparently they work with the NVidia Geforce8600M inside the new  
MacBookPro's - both on Tiger 10.4.10 and Leopard, and also with  
the NVidia Quadro. However that doesn't guarantee they work with  
anything else. Support is completely driver dependent, so its  
up to NVidia/ATI/Intel which cards support it with which OS release.  
  
We'll see. On OS/X lack of beampos queries is not that much  
of a problem, you only lose a little bit of accuracy: PTB uses  
timestamped hardware interrupts (vbl interrupts) on OS/X to  
get pretty ok timestamps if it can't use beampos queries.  
  
Order of accuracy/robustness:  
  
1. Beampositin queries are best - as good as +/- 20 microsecs jitter  
on some hardware/OS.  
  
2. VBL interrupts on OS/X can be as good as +/-100 microsecs, but  
they are always submillisecond accurate at least.  
  
3. Standard timestamps are sub-millisecond on OS/X and Linux  
most of the time, but its not guaranteed. On Windoze, they are  
(nearly) guaranteed to be worse than 1 msec - pick an arbitrarily  
high number as upper bound for the worst case.  
  
-mario  
  

> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Peter Meilstrup" \<peter.meilstrup@...\> wrote:  
> \>  
> \> Does this mean the beamposition queries on Intel are working now? Will it  
> \> also work on ATI graphics hardware? This will eliminate one of my hewadaches  
> \> if so.  
> \>   
> \> On 10/30/07, aseitz \<aseitz@...\> wrote:  
> \> \>  
> \> \>  
> \> \> PTB-Info: Measured monitor refresh interval from beamposition = 16.742675ms  
> \> \> [59.727612 Hz].  
> \> \> PTB-Info: Will use beamposition query for accurate Flip time stamping.  
> \> \> PTB-Info: Measured monitor refresh interval from VBLsync = 16.750103 ms [  
> \> \> 59.701124  
> \> \> Hz]. (50 valid samples taken, stddev=0.065576 ms.)  
> \> \> PTB-Info: Small deviations between reported values are normal and no  
> \> \> reason to worry.  
> \> \>  
> \> \>  
> \>
