TicketGUID:{04A5FF4D-85D7-11D6-A52C-00508BE22D04}
Dear ATI
Thanks for the tips in the Mac FAQ. I tried all the relevant ones:
1. i tried rebooting with just the basic Mac OS 9.2.2 and ATI extensions.
2. i removed the ATI ROM Extender and zapped my PRAM.
3. i moved the ATI Radeon 7000 card to another slot.
Nothing made any difference to the problem I reported: the driver's
off-by-one table lookup for gamma correction.
The problem I'm reporting is subtle, not evident to the naked eye. It
is only revealed by my test programs. However, that fault greatly
reduces the usefulness of the Radeon 7000me for my research and
hundreds of colleagues who have similar needs and are watching to see
how I fare.
http://psychtoolbox.org/mac.html#drivers
I've pasted below the printout from my test program. Note the
comparison of what I actually read from the CLUT and what I expected
to read. Most of the errors are very small, but there shouldn't be
any.
To make progress on this, I think we'll need to consult one of your
engineers who knows the C code of the Radeon driver.
Thanks for your help.
Sincerely yours
Denis Pelli
Professor of Psychology and Neural Science at NYU
http://psych.nyu.edu/pelli/
Apple Developer
http://psychtoolbox.org/
gammatest
*** Screen 0 *************************************************************
ATY,mach64_3DUPro (.Display_ATImach64_3DR3 version 1.0.1f8) in slot F1
8 bit dacs. 1024x768 85 Hz. (50,56,60,65,67,70,72,75,85 Hz avail)
Prefs: BlankingDuration 0.008 s.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 8 bits.
GetGamma 8 bits. GetClut == predicted.
UseHighGammaBits 0. pixelSize 8. randomize 1. SetGamma 8 bits.
GetGamma 8 bits. GetClut == predicted.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 10 bits.
SetGamma error -17.
Screen driver supports gamma tables with precisions: 8 bits.
*** Screen 1 *************************************************************
ATY,RV100ad_A (.Display_DualHead version 1.0f26) in slot C1
10 bit dacs. 832x624 74 Hz. (56,60,65,67,70,72,75,85,90,100,120 Hz avail)
Supports: cscGetClutBehavior cscGetTimingRanges
Prefs: DacBits 10, DipPriorityAfterSetClut, MinimumSetClutPriority 2.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 8 bits.
GetGamma 8 bits. GetClut != predicted. Max error 1.
0: GetClut:[ 0 254 164] vs. expected:[ 0 255 165]
1: GetClut:[ 0 253 235] vs. expected:[ 1 254 236]
2: GetClut:[ 1 252 35] vs. expected:[ 2 253 36]
3: GetClut:[ 2 251 252] vs. expected:[ 3 252 253]
. . .
252: GetClut:[ 251 2 38] vs. expected:[ 252 3 39]
253: GetClut:[ 252 1 213] vs. expected:[ 253 2 214]
254: GetClut:[ 253 0 238] vs. expected:[ 254 1 239]
255: GetClut:[ 254 0 24] vs. expected:[ 255 0 25]
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 10 bits.
GetGamma 10 bits. GetClut != predicted. Max error 6.
0: GetClut:[ 0 1018 609] vs. expected:[ 0 1023 614]
1: GetClut:[ 0 1014 926] vs. expected:[ 4 1019 931]
2: GetClut:[ 3 1010 673] vs. expected:[ 8 1015 678]
3: GetClut:[ 7 1006 942] vs. expected:[ 12 1011 947]
. . .
252: GetClut:[ 1006 7 171] vs. expected:[ 1011 12 176]
253: GetClut:[ 1010 3 452] vs. expected:[ 1015 8 457]
254: GetClut:[ 1014 0 986] vs. expected:[ 1019 4 991]
255: GetClut:[ 1018 0 215] vs. expected:[ 1023 0 220]
Errors encountered at all tested gamma table resolutions: 8 10 bits.
**************************************************************************
ยป
Dear ATI
Thanks for the tips in the Mac FAQ. I tried all the relevant ones:
1. i tried rebooting with just the basic Mac OS 9.2.2 and ATI extensions.
2. i removed the ATI ROM Extender and zapped my PRAM.
3. i moved the ATI Radeon 7000 card to another slot.
Nothing made any difference to the problem I reported: the driver's
off-by-one table lookup for gamma correction.
The problem I'm reporting is subtle, not evident to the naked eye. It
is only revealed by my test programs. However, that fault greatly
reduces the usefulness of the Radeon 7000me for my research and
hundreds of colleagues who have similar needs and are watching to see
how I fare.
http://psychtoolbox.org/mac.html#drivers
I've pasted below the printout from my test program. Note the
comparison of what I actually read from the CLUT and what I expected
to read. Most of the errors are very small, but there shouldn't be
any.
To make progress on this, I think we'll need to consult one of your
engineers who knows the C code of the Radeon driver.
Thanks for your help.
Sincerely yours
Denis Pelli
Professor of Psychology and Neural Science at NYU
http://psych.nyu.edu/pelli/
Apple Developer
http://psychtoolbox.org/
gammatest
*** Screen 0 *************************************************************
ATY,mach64_3DUPro (.Display_ATImach64_3DR3 version 1.0.1f8) in slot F1
8 bit dacs. 1024x768 85 Hz. (50,56,60,65,67,70,72,75,85 Hz avail)
Prefs: BlankingDuration 0.008 s.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 8 bits.
GetGamma 8 bits. GetClut == predicted.
UseHighGammaBits 0. pixelSize 8. randomize 1. SetGamma 8 bits.
GetGamma 8 bits. GetClut == predicted.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 10 bits.
SetGamma error -17.
Screen driver supports gamma tables with precisions: 8 bits.
*** Screen 1 *************************************************************
ATY,RV100ad_A (.Display_DualHead version 1.0f26) in slot C1
10 bit dacs. 832x624 74 Hz. (56,60,65,67,70,72,75,85,90,100,120 Hz avail)
Supports: cscGetClutBehavior cscGetTimingRanges
Prefs: DacBits 10, DipPriorityAfterSetClut, MinimumSetClutPriority 2.
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 8 bits.
GetGamma 8 bits. GetClut != predicted. Max error 1.
0: GetClut:[ 0 254 164] vs. expected:[ 0 255 165]
1: GetClut:[ 0 253 235] vs. expected:[ 1 254 236]
2: GetClut:[ 1 252 35] vs. expected:[ 2 253 36]
3: GetClut:[ 2 251 252] vs. expected:[ 3 252 253]
. . .
252: GetClut:[ 251 2 38] vs. expected:[ 252 3 39]
253: GetClut:[ 252 1 213] vs. expected:[ 253 2 214]
254: GetClut:[ 253 0 238] vs. expected:[ 254 1 239]
255: GetClut:[ 254 0 24] vs. expected:[ 255 0 25]
UseHighGammaBits 0. pixelSize 8. randomize 0. SetGamma 10 bits.
GetGamma 10 bits. GetClut != predicted. Max error 6.
0: GetClut:[ 0 1018 609] vs. expected:[ 0 1023 614]
1: GetClut:[ 0 1014 926] vs. expected:[ 4 1019 931]
2: GetClut:[ 3 1010 673] vs. expected:[ 8 1015 678]
3: GetClut:[ 7 1006 942] vs. expected:[ 12 1011 947]
. . .
252: GetClut:[ 1006 7 171] vs. expected:[ 1011 12 176]
253: GetClut:[ 1010 3 452] vs. expected:[ 1015 8 457]
254: GetClut:[ 1014 0 986] vs. expected:[ 1019 4 991]
255: GetClut:[ 1018 0 215] vs. expected:[ 1023 0 220]
Errors encountered at all tested gamma table resolutions: 8 10 bits.
**************************************************************************
ยป
>Dear Denis Pelli,
>
>Thank you for contacting ATI Customer Service Canada.
>
>------------------------------------------------------------------------------
>Your email has been assigned:
>TicketGUID:{04A5FF4D-85D7-11D6-A52C-00508BE22D04}
>
>Please include the above identifier in all future correspondence
>relating to this ticket. Note: The TicketGUID identifier must appear
>in the message body, not in the subject line.
>--------------------------------------------------------------------------------
>
>Based on our experience, the issue(s) you describe are usually due
>to system configuration errors. We believe that the
>troubleshooting steps listed below may help to resolve this issue.
>
>You may also consider using the new SEARCH ATI function on our web
>site. It can be found at:
>
>http://www.ati.com/search/index.html
>
>
>Regards,
>
>Customer Service Canada
>ATI Technologies, Inc.
>http://www.ati.com
>
>===================================================================
>
>Common Troubleshooting steps for Installation issues (Not all steps
>will apply depending on the operating system you are using):
>
>---------------------------------------------------------------------------------------
>
>Booting MacOS with only ATI Extensions loaded (MacOS 9.x or lower):
>
>If the system has random lock-ups, or applications quit
>unexpectedly, it could be caused by incompatible or conflicting
>extensions. The Extensions Manager can help temporarily remove
>suspect Extensions
>
>Steps to follow:
>
>1. Open the Extensions Manager (Apple menu > Control Panels)
>2. From the "Selected Set", choose the "Mac OS x Base" (where 'x' is
>the OS version installed)
>3. Click the "Duplicate Set" button and provide a name for the test set
>4. Enable all ATI extensions (note: all QuickTime extensions should
>be enabled by default, if there are not, please enable them.)
>5. Restart the computer
>
>Confirming an extension conflict, you will need to determine the
>conflicting extensions and correct the conflict. You may wish to
>contact the manufacturer of the extension to see if an update is
>available.
>
>NOTE: If the system experiences a hang at boot the best option would
>be to hold down the SHIFT key when you hear the Startup Chime on
>restart. Hold down the SHIFT key until "Extensions Off" appears on
>your screen. This will disable everything - the CD drive is not
>accessible at this point
>
>---------------------------------------------------------------------------------------
>
>Disable Graphics Acceleration:
>
>If you are experiencing graphics corruption in a 2D application you
>may wish to try disabling the ATI Graphics Acceleration as a test.
>To do this click on the ATI logo in the top-right hand corner of the
>screen. Remove the checkmark from Graphics Acceleration.
>
>---------------------------------------------------------------------------------------
>
>For PCI cards:
>
>Try moving the ATI display adapter to another PCI slot (be sure to
>shut down and UNPLUG the computer first).
>Try trashing the ATI ROM Xtender (This ONLY relates to the Radeon
>Mac Edition). Once the ATI ROM Xtender has been trashed, restart and
>ZAP the PRAM.
>
>---------------------------------------------------------------------------------------
>
>Re-Install Drivers:
>
>If these issues started occurring AFTER updating your ATI display
>driver, you may consider reverting back to the previous driver build
>until a newer build is released.
>Please ensure that you exit ALL applications prior to installing drivers.
>
> Radeon Mac Edition
>
> http://www.ati.com/support/products/mac/radeon/radeonmaceditiondrivers.html
>
> Xclaim VR 128 / Rage Orion / Nexus 128
> http://www.ati.com/support/products/mac/rage128/rage128macdrivers.html
>
> Nexus GA
> http://www.ati.com/support/products/mac/rage/nexusgadrivers.html
>
> Xclaim 3D Plus
> http://www.ati.com/support/products/mac/rage/xclaim3dplusdrivers.html
>
> Xclaim VR
> http://www.ati.com/support/products/mac/rage/xclaimvrdrivers.html
>
> Xclaim 3D
> http://www.ati.com/support/products/mac/rage/xclaim3ddrivers.html
>
> Xclaim GA
> http://www.ati.com/support/products/mac/mach64/xclaimgadrivers.html
>
>
>Power on the system.
>
>1. Use the ATI Install CD to uninstall the current display drivers
>2. Remove both the ATI Displays and Monitors preferences from the
>Preferences folder [located in the System folder]
>3. Remove any remaining ATI extensions from the Extensions folder
>4. Restart the system
>5. Boot with no extensions (hold down SHIFT when the startup chime is heard)
>6. Install the required version of QuickTime (
>http://www.apple.com/quicktime/download/ )
>7. Install the required version of OpenGL support (
>http://www.apple.com/opengl )
>8. Now install the appropriate ATI display drivers from one of the links above
>
>---------------------------------------------------------------------------------------
>
>Xclaim Video Player troubleshooting:
>
>When launching the XCLAIM Video Player, the input source for sound
>may spontaneously change from "Sound In" to another setting.
>
>To resolve this issue, remove the XCLAIM Video Player preferences:
>1. Quit the XCLAIM Video Player
>2. From the System Folder, open the Preferences folder
>3. Locate the XCLAIM VP preferences and remove them
>4. Set the Input Source to the correct audio input setting in the
>Sound control panel
>5. Launch the XCLAIM Video Player
>6. The Input Source should now maintain its setting
>
>
>When launching the XCLAIM Video Player the following message may appear,
> "XCLAIM Video Player cannot locate ATI Video Digitizer".
>
>NOTE: This message can appear when using any ATI XCLAIM VR series adapter.
>
>1. Using the Finder, ensure that the XCLAIM Video Player is not already open.
>2. Ensure that the Desktop Video is off via the Desktop Video
>control strip module.
>3. Verify a monitor is connected to the ATI Xclaim VR product
>4. Confirm the ATI Video Digitizer extension is listed in the
>Extensions folder
>5. Update QuickTime to 3.02 or greater
>6. If running Mac OS X you will need to restart your computer in Mac
>OS 9.1 before running Xclaim Video Player
>
>---------------------------------------------------------------------------------------
>
>Mac2TV Troubleshooting:
>
>Enabling/Disabling TV OUT (Mac2TV) via the ATI DISPLAYS Control
>Panel in MacOS 9.x or lower
>
>To enable TV OUT:
>1. Attach a TV or VCR to the TV OUT connector on the ATI card
>2. Open the ATI Displays control panel
>3. Select an ATI display which supports the Mac2TV feature.
>4. Click on the Mac2TV icon and then check the ON option under VIDEO OUTPUT
>
>To disable TV OUT:
>1. Open the ATI Displays control panel
>2. Select an ATI display which supports the Mac2TV feature
>3. Click on the Mac2TV icon and then check the OFF option under VIDEO OUTPUT
>
>Enabling Mac2TV television output under Mac OS X using the Displays
>control panel:
>
>1. Connect a TV or VCR to the Mac2TV output connector on your ATI
>graphics card BEFORE starting up the computer.
>2. Also connect a monitor to the graphics card being used for TV Output.
>3. Start up computer into Mac OS X.
>4. Open the System Preferences and select "Displays".
>5. Select a simulscan resolution to enable Mac2TV on that display.
>
>NOTE!: When TV OUT (Mac2TV) is initially turned on, your monitor
>display will be turned off. Monitors which do not support the 60 Hz
>vertical refresh rate required by video equipment may be damaged
>when Mac2TV is enabled. Turning off your monitor display is a safety
>feature, protecting your monitor from any potential damage.
>
>
>Mac2TV cannot be enabled on RADEON Mac Edition:
>This issue affects PCI versions of RADEON Mac Edition running ATI
>software version 1.1.0 under Mac OS 9.0. If the system has more than
>one display, then Mac2TV controls may not be available and Mac2TV
>cannot be enabled.
>
>RADEON Installer version 1.1.1 does NOT require RADEON Mac Edition
>to be the startup screen for Mac2TV to be enabled.
>http://www.ati.com/support/products/mac/radeon/radeonmaceditiondrivers.html
>
>---------------------------------------------------------------------------------------
>
>Radeon Mac Edition does not fit in PCI slot
>
>When attempting to install the RADEON MAC EDITION PCI into a
>PowerMac 7200/7500/8500/9500, the lower nut on the card's VGA
>connector may catch on the outer case. This will prevent the RADEON
>MAC EDITION PCI from correctly seating in the PCI slot.
>
>To use the RADEON MAC EDITION PCI in these systems, the lower nut on
>the VGA connector must be removed. Once removed, the card should fit
>properly into any of these PowerMac systems.
>
>---------------------------------------------------------------------------------------
>
>General Advice on Mac Application Troubleshooting
>
>Once you have determined that your application issue is NOT display
>related, you may want to try the following trouble-shooting steps
>listed below.
>
>---------------------------------------------------------------------------------------
>
>Trash application preferences
>
>Most applications keep a preferences file in the Preferences Folder.
>Sometimes this file can become bloated and corrupt, resulting in
>unpredictable behavior.
>
>Trashing the preferences may help to resolve an issue, but will
>destroy any custom settings you may have saved for that application.
>
>If you are prepared to take this step, proceed as follows:
>
>1. On the hard drive, open System Folder
>2. Open the Preferences Folder (in the System Folder)
>3. Locate the application's preference file and drag it to the trash
>4. Restart and Zap the PRAM
>5. Increase the RAM assigned to the application
>6. Applications in Mac OS receive a fixed amount of memory when they
>are launched.
>
>The application you are trying to run may not be getting enough
>memory assigned to it.
>
>Instructions on how to increase the amount of memory assigned to an
>application are available on the ATI Support website.
>
>---------------------------------------------------------------------------------------
>
>Reinstall the application
>
>If the application has an uninstall feature, this should be used first.
>Then reinstall the application from scratch to see if the issue is resolved.
>Contact the vendor of the application
>Most reputable software companies offer some form of technical support.
>
>You might consider contacting the software company for help.