# Error message for using Bits# **URL:** \ **Category:** Uncategorized\ **Created:** [February 6, 2013, 2:18am UTC](https://psychtoolbox.discourse.group/t/error-message-for-using-bits/534 "2013-02-06T02:18:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Allen\_Ingling](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@Allen\_Ingling](https://psychtoolbox.discourse.group/u/Allen_Ingling)\ **Post date:** [February 6, 2013, 2:18am UTC](https://psychtoolbox.discourse.group/t/error-message-for-using-bits/534/1 "2013-02-06T02:18:51Z")
Hi, We recently purchased a Bits# and got the following error message when testing with a simple code for palatte animation. We never met this problem with our previous Bits++. Can anyone let us know what is wrong and how to fix it? Thanks! I posted a similar message two days ago with a different yahoo account. I worry the previous message is not received. Hope you are not bothered by the duplicated messages. -Min PTB-INFO: This is Psychtoolbox-3 for Apple OS X, under Matlab 64-Bit (Version 3.0.10 - Build date: Oct 7 2012). PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information. PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions. PTB-INFO: Broken Apple OS/X 10.7 or later detected: Using CoreVideo timestamping instead of precise vbl-irq timestamping. PTB-INFO: You are using a multi-display setup (2 active displays): PTB-INFO: Please read 'help MultiDisplaySetups' for specific information on the Do's, Dont's, PTB-INFO: and possible causes of trouble and how to diagnose and resolve them. PTB-INFO: According to the operating system, some of your connected displays do not seem to PTB-INFO: be switched into mirror mode. For a discussion of mirror mode vs. non-mirror mode, PTB-INFO: please read 'help MirrorMode'. PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon HD 6770M OpenGL Engine :: 2.1 ATI-1.0.29 PTB-INFO: Renderer has 512 MB of VRAM and a maximum 494 MB of texture memory. PTB-INFO: VBL startline = 768 , VBL Endline = -1 PTB-INFO: Beamposition queries unsupported on this system. Will try to use kernel-level vbl interrupts as fallback. PTB-INFO: Measured monitor refresh interval from VBLsync = 11.763242 ms [85.010580 Hz]. (50 valid samples taken, stddev=0.003011 ms.) PTB-INFO: Reported monitor refresh interval from operating system = 11.764704 ms [85.000015 Hz]. PTB-INFO: Small deviations between reported values are normal and no reason to worry. PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 1027 ... PTB-INFO: Will use 8 bits per color component framebuffer for stimulus drawing. PTB-INFO: Will use 8 bits per color component framebuffer for stimulus post-processing (if any). LoadIdentityClut: Info: Could not use GPU low-level setup for setup of pixel passthrough. Will use fallback method. LoadIdentityClut: Info: If you have an AMD/ATI GPU, you may get this working by loading the PsychtoolboxKernelDriver LoadIdentityClut: Info: on OS/X or using a Linux system properly setup with PsychLinuxConfiguration. Building a fragment shader:Reading shader from file /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine\_FormattingShader.frag.txt ... PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! ---
**Author:** ![Allen\_Ingling](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@Allen\_Ingling](https://psychtoolbox.discourse.group/u/Allen_Ingling)\ **Post date:** [February 18, 2013, 3:28am UTC](https://psychtoolbox.discourse.group/t/error-message-for-using-bits/534/2 "2013-02-18T03:28:00Z")
Hi Mario, Thanks for your suggestion! I tried your Bits++ demos, BitsPlusImagingTest and MinimumMotionExp. Neither of them worked. When running BitsPlusImagingTest, I saw a yellow square on the upper left quadrant. It never changed with the keystrokes. A single line of pixels on the upper left corner of the monitor did change with the keystrokes. When running MinimumMotionExp at the Bits++ mode, I saw grayscale static windmill. But the code worked well when I didn't use the Bits++ mode. Below are the messages for running these two demos. I noticed that both messages mentioned PsychtoolboxKernelDriver. Do you think I should install it? Thanks! > \>\> BitsPlusImagingTest PTB-INFO: This is Psychtoolbox-3 for Apple OS X, under Matlab 64-Bit (Version 3.0.10 - Build date: Oct 7 2012). PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information. PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions. PTB-INFO: Broken Apple OS/X 10.7 or later detected: Using CoreVideo timestamping instead of precise vbl-irq timestamping. PTB-INFO: You are using a multi-display setup (2 active displays): PTB-INFO: Please read 'help MultiDisplaySetups' for specific information on the Do's, Dont's, PTB-INFO: and possible causes of trouble and how to diagnose and resolve them. PTB-INFO: According to the operating system, some of your connected displays do not seem to PTB-INFO: be switched into mirror mode. For a discussion of mirror mode vs. non-mirror mode, PTB-INFO: please read 'help MirrorMode'. PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon HD 6770M OpenGL Engine :: 2.1 ATI-1.0.29 PTB-INFO: Renderer has 512 MB of VRAM and a maximum 494 MB of texture memory. PTB-INFO: VBL startline = 768 , VBL Endline = -1 PTB-INFO: Beamposition queries unsupported on this system. Will try to use kernel-level vbl interrupts as fallback. PTB-INFO: Measured monitor refresh interval from VBLsync = 11.763313 ms [85.010061 Hz]. (50 valid samples taken, stddev=0.004460 ms.) PTB-INFO: Reported monitor refresh interval from operating system = 11.764704 ms [85.000015 Hz]. PTB-INFO: Small deviations between reported values are normal and no reason to worry. PTB-INFO: Support for fast OffscreenWindows enabled. LoadIdentityClut: Info: Could not use GPU low-level setup for setup of pixel passthrough. Will use fallback method. LoadIdentityClut: Info: If you have an AMD/ATI GPU, you may get this working by loading the PsychtoolboxKernelDriver LoadIdentityClut: Info: on OS/X or using a Linux system properly setup with PsychLinuxConfiguration. Setting to value 0 -- Press any key to continue. Setting to value 0.0526316 -- Press any key to continue. Setting to value 0.105263 -- Press any key to continue. Setting to value 0.157895 -- Press any key to continue. Setting to value 0.210526 -- Press any key to continue. Setting to value 0.263158 -- Press any key to continue. Setting to value 0.315789 -- Press any key to continue. Setting to value 0.368421 -- Press any key to continue. Setting to value 0.421053 -- Press any key to continue. Setting to value 0.473684 -- Press any key to continue. Setting to value 0.526316 -- Press any key to continue. Setting to value 0.578947 -- Press any key to continue. Setting to value 0.631579 -- Press any key to continue. Setting to value 0.684211 -- Press any key to continue. Setting to value 0.736842 -- Press any key to continue. Setting to value 0.789474 -- Press any key to continue. Setting to value 0.842105 -- Press any key to continue. Setting to value 0.894737 -- Press any key to continue. Setting to value 0.947368 -- Press any key to continue. Setting to value 1 -- Press any key to continue. INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline INFO: a total of 2 times out of a total of 24 flips during this session. INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system) INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]); INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips. ============================ Minimum Motion Windmill ============================================== ==A fast, precise, versatile and eternally fascinating photometric technique for the computer age== Do you want to use the Bits++ box or DataPixx/ViewPixx for stimulation [y/n]? y Using CRS Bits++ in Bits++ CLUT mode or DataPixx/ViewPixx in L48 mode. For default gamma compensation (gamma = 2.7), just hit enter at the following prompt: File with Nx3 InvGammaTablevariable listing the video outputs (0 to65536) producing r,g,b intensities ~ row index; will add .mat extension) Or, for default gamma compensation (gamma = 2.7), just hit enter: Number of settings per condition: 5 Name of subject (only internal use!): File name prefix for storing new data (relative to data subdirectory, will add .mat and .txt extensions): aaa ADAPTRGB = 0.5000 0.3100 0.2400 condition-dependent parameters in this script: innerdiameter, outerdiam, whichluminance (r:1, b:2, both:3); values, 1 row per condition are conditionset = 11 15 3 0 2 3 Spatial dimensions displayed and quoted assume that monitor screen width = viewing distance; if not, modify constants in script. Move trackball or mouse leftward if motion is clockwise, rightward if anticlockwise, to find the balance point. Hit escape to save and quit early; to register a setting, press any other keyboard key or a mouse button. Setting is acknowledged by a beep Press any key to continue... Do you want to use the DataPixx box instead of Bits++ box for stimulation [y/n]? n PTB-INFO: This is Psychtoolbox-3 for Apple OS X, under Matlab 64-Bit (Version 3.0.10 - Build date: Oct 7 2012). PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information. PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions. PTB-INFO: Broken Apple OS/X 10.7 or later detected: Using CoreVideo timestamping instead of precise vbl-irq timestamping. PTB-INFO: You are using a multi-display setup (2 active displays): PTB-INFO: Please read 'help MultiDisplaySetups' for specific information on the Do's, Dont's, PTB-INFO: and possible causes of trouble and how to diagnose and resolve them. PTB-INFO: According to the operating system, some of your connected displays do not seem to PTB-INFO: be switched into mirror mode. For a discussion of mirror mode vs. non-mirror mode, PTB-INFO: please read 'help MirrorMode'. PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon HD 6770M OpenGL Engine :: 2.1 ATI-1.0.29 PTB-INFO: Renderer has 512 MB of VRAM and a maximum 494 MB of texture memory. PTB-INFO: VBL startline = 768 , VBL Endline = -1 PTB-INFO: Beamposition queries unsupported on this system. Will try to use kernel-level vbl interrupts as fallback. PTB-INFO: Measured monitor refresh interval from VBLsync = 11.763561 ms [85.008270 Hz]. (50 valid samples taken, stddev=0.010067 ms.) PTB-INFO: Reported monitor refresh interval from operating system = 11.764704 ms [85.000015 Hz]. PTB-INFO: Small deviations between reported values are normal and no reason to worry. PTB-INFO: Support for fast OffscreenWindows enabled. LoadIdentityClut: Info: Could not use GPU low-level setup for setup of pixel passthrough. Will use fallback method. LoadIdentityClut: Info: If you have an AMD/ATI GPU, you may get this working by loading the PsychtoolboxKernelDriver LoadIdentityClut: Info: on OS/X or using a Linux system properly setup with PsychLinuxConfiguration. driftratehz = 2 ASSUMEDREFRESHRATE = 85.0083 Warning: Drift period is not a multiple of monitor refresh interval: rounding > \> In MinimumMotionExp at 209 Stipulated drift rate: 2.000000 Hz, actual 1.976937 Hz Trial 1 of 10 Outer Radius: 7.5degrees, Mean spatial frequency in cpd: 0.44074 Trial 2 of 10 Outer Radius: 1degrees, Mean spatial frequency in cpd: 5.7296 Trial 3 of 10 Outer Radius: 7.5degrees, Mean spatial frequency in cpd: 0.44074 Trial 4 of 10 Outer Radius: 1degrees, Mean spatial frequency in cpd: 5.7296 Trial 5 of 10 Outer Radius: 7.5degrees, Mean spatial frequency in cpd: 0.44074 Trial 6 of 10 Outer Radius: 1degrees, Mean spatial frequency in cpd: 5.7296 Trial 7 of 10 Outer Radius: 7.5degrees, Mean spatial frequency in cpd: 0.44074 Trial 8 of 10 Outer Radius: 1degrees, Mean spatial frequency in cpd: 5.7296 Trial 9 of 10 Outer Radius: 7.5degrees, Mean spatial frequency in cpd: 0.44074 Trial 10 of 10 Outer Radius: 1degrees, Mean spatial frequency in cpd: 5.7296 INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline INFO: a total of 2 times out of a total of 8642 flips during this session. INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system) INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]); INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips. > \>\> > > --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "Mario" \ wrote: > \> > \> > \> > \> Do our Bits+ Bits++ mode demos, e.g., MinimumMotionExp, work? > \> > \> This line... > \> > \> \> Building a fragment shader:Reading shader from file /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine\_FormattingShader.frag.txt ... > \> > \> ... looks suspicious. I don't know why it would show up in code meant to drive a Bits#, so i assume something is wrong with your script. > \> > \> Post the most minimal script that fails for you, so we can see what you're doing. > \> > \> -mario > \> > \> > \> > \> --- In [psychtoolbox@yahoogroups.com](mailto:psychtoolbox@yahoogroups.com), "ptbmin" wrote: > \> \> > \> \> Hi, > \> \> > \> \> We recently purchased a Bits# and got the following error message when testing with a simple code for palatte animation. We never met this problem with our previous Bits++. Can anyone let us know what is wrong and how to fix it? Thanks! > \> \> > \> \> I posted a similar message two days ago with a different yahoo account. I worry the previous message is not received. Hope you are not bothered by the duplicated messages. > \> \> > \> \> -Min > \> \> > \> \> > \> \> > \> \> PTB-INFO: This is Psychtoolbox-3 for Apple OS X, under Matlab 64-Bit (Version 3.0.10 - Build date: Oct 7 2012). > \> \> PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information. > \> \> PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with > \> \> PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions. > \> \> > \> \> PTB-INFO: Broken Apple OS/X 10.7 or later detected: Using CoreVideo timestamping instead of precise vbl-irq timestamping. > \> \> > \> \> > \> \> PTB-INFO: You are using a multi-display setup (2 active displays): > \> \> PTB-INFO: Please read 'help MultiDisplaySetups' for specific information on the Do's, Dont's, > \> \> PTB-INFO: and possible causes of trouble and how to diagnose and resolve them. > \> \> > \> \> PTB-INFO: According to the operating system, some of your connected displays do not seem to > \> \> PTB-INFO: be switched into mirror mode. For a discussion of mirror mode vs. non-mirror mode, > \> \> PTB-INFO: please read 'help MirrorMode'. > \> \> > \> \> > \> \> PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon HD 6770M OpenGL Engine :: 2.1 ATI-1.0.29 > \> \> PTB-INFO: Renderer has 512 MB of VRAM and a maximum 494 MB of texture memory. > \> \> PTB-INFO: VBL startline = 768 , VBL Endline = -1 > \> \> PTB-INFO: Beamposition queries unsupported on this system. Will try to use kernel-level vbl interrupts as fallback. > \> \> PTB-INFO: Measured monitor refresh interval from VBLsync = 11.763242 ms [85.010580 Hz]. (50 valid samples taken, stddev=0.003011 ms.) > \> \> PTB-INFO: Reported monitor refresh interval from operating system = 11.764704 ms [85.000015 Hz]. > \> \> PTB-INFO: Small deviations between reported values are normal and no reason to worry. > \> \> PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 1027 ... > \> \> PTB-INFO: Will use 8 bits per color component framebuffer for stimulus drawing. > \> \> PTB-INFO: Will use 8 bits per color component framebuffer for stimulus post-processing (if any). > \> \> LoadIdentityClut: Info: Could not use GPU low-level setup for setup of pixel passthrough. Will use fallback method. > \> \> LoadIdentityClut: Info: If you have an AMD/ATI GPU, you may get this working by loading the PsychtoolboxKernelDriver > \> \> LoadIdentityClut: Info: on OS/X or using a Linux system properly setup with PsychLinuxConfiguration. > \> \> Building a fragment shader:Reading shader from file /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine\_FormattingShader.frag.txt ... > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> > \> ---
**Author:** ![Allen\_Ingling](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@Allen\_Ingling](https://psychtoolbox.discourse.group/u/Allen_Ingling)\ **Post date:** [February 22, 2013, 8:59am UTC](https://psychtoolbox.discourse.group/t/error-message-for-using-bits/534/3 "2013-02-22T08:59:50Z")
Hi Mario, You are right! A guy from the CRS support and also the Bits# manual suggest to add a line PsychImaging('AddTask', 'General', 'EnableCLUTMapping'); before open the screen. Indeed, using 'General' rather than 'AllViews' avoided those error messages, but still left one suspicious message: Building a fragment shader:Reading shader from file /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine\_FormattingShader.frag.txt ... When that AddTask line was removed from the script, this message didn't appear. However, in both cases (with or without the AddTask line) I could see a line of dancing pixels along the top of the screen, an indication of failure to recognize the T-Lock code. I am guessing the unintended temporal dithering by Mountain Lion caused the problem. Min > \> Regarding your code, this line > \> > \> \> PsychImaging('AddTask', 'AllViews', 'EnableCLUTMapping'); > \> > \> doesn't belong there and likely causes the error messages. It is meant to allow CLUT mapping if you don't have a BitsXXX / or DataPixx/ViewPixx device. I'll add a fix to future ptb's so that such a command will be silently ignored in Bits++/Monot++ etc. mode, but for now specifying it will wreak havoc. > \> > \> However, it is still not clear to me why the MinimumMotionExp doesn't work out of the box for you, assuming your Bits# is switched to Bits++ mode. > \> > \> -mario > \> > \> > \> \> %-------------------------------------------------- > \> \> clear all;clc; > \> \> KbName('UnifyKeyNames'); > \> \> oldEnableFlag = Screen('Preference', 'TextAntiAliasing', 0); > \> \> dur = 10; % how long we show the demo > \> \> > \> \> try > \> \> AssertOpenGL; > \> \> ncolors = 253; > \> \> screens = Screen('Screens'); > \> \> screenNumber = max(screens); > \> \> bkgcol = ncolors/2; > \> \> > \> \> %--- Starting to communicate with Bits# --- > \> \> s1 = serial('/dev/tty.usbmodemfa121'); > \> \> fopen(s1); > \> \> fprintf(s1,['$BitsPlusPlus' 13]); > \> \> fclose(s1); > \> \> > \> \> %--- Bits++ configuration --- > \> \> PsychImaging('PrepareConfiguration'); > \> \> PsychImaging('AddTask', 'General', 'EnableBits++Bits++Output'); > \> \> PsychImaging('AddTask', 'AllViews', 'EnableCLUTMapping'); > \> \> > \> \> [w, screenRect] = PsychImaging('OpenWindow', screenNumber, ncolors/2); > \> \> fixpos = CenterRect([0 0 1 1],screenRect); > \> \> oldclut = Screen('ReadNormalizedGammaTable',screenNumber); > \> \> > \> \> img = zeros(100,100); > \> \> tex = Screen('MakeTexture', w, img); > \> \> > \> \> newcmap = gray(ncolors); > \> \> newclut=zeros(256,3);newclut(1:ncolors,:) = newcmap; > \> \> newclut(254:256,:) = [1 1 1;0 0 0;0 0 0]; % a lookup table for 100% contrast, though it is not calibrated. > \> \> > \> \> newcmap=.5\*ones(ncolors,3); > \> \> newclut2=zeros(256,3);newclut2(1:ncolors,:) = newcmap; > \> \> newclut2(254:256,:) = [1 1 1;0 0 0;0 0 0]; % a lookup table for 0% contrast. > \> \> > \> \> Screen('FillRect',w,bkgcol); > \> \> Screen('DrawArc',w,255,CenterRect([0 0 12 12],screenRect),0,360); > \> \> Screen('LoadNormalizedGammaTable',w,newclut,2); > \> \> Screen('Flip',w); > \> \> > \> \> DrawFormattedText(w, 'Press a key to start', 'center','center'); > \> \> Screen('Flip',w); > \> \> KbWait; > \> \> > \> \> % Animation loop: > \> \> t0 = GetSecs; > \> \> Tpress = t0; > \> \> whichclut = 1; > \> \> while((GetSecs-t0) \< dur) > \> \> Screen('DrawTexture',w,tex); > \> \> Screen('DrawArc', w, 255, CenterRect([0 0 12 12], screenRect), 0, 360); > \> \> if whichclut == 1 > \> \> Screen('DrawText', w, 'Contrast = 0%', 150, 150, 255); > \> \> else > \> \> Screen('DrawText', w, 'Contrast = 100%', 150, 150, 255); > \> \> end > \> \> if whichclut == 1 > \> \> Screen('LoadNormalizedGammaTable',w,newclut2,2); > \> \> else > \> \> Screen('LoadNormalizedGammaTable',w,newclut,2); > \> \> end > \> \> Screen('Flip',w); > \> \> [keyIsDown, secs, keyCode, deltaSecs] = KbCheck; > \> \> if keyIsDown && GetSecs-Tpress \> .2 > \> \> if keyCode(KbName('q')) % press q to quit the programn > \> \> error('quit!'); > \> \> else > \> \> whichclut = 3-whichclut; % otherwise the lookup table is altered. > \> \> end > \> \> Tpress = GetSecs; > \> \> end > \> \> end; > \> \> > \> \> Screen('FillRect',w, bkgcol); > \> \> Screen('Flip', w); > \> \> Screen('LoadNormalizedGammaTable',w,oldclut); > \> \> Screen('Preference', 'TextAntiAliasing', oldEnableFlag); > \> \> Screen('CloseAll'); > \> \> > \> \> %--- Stop communication with Bits# --- > \> \> delete(s1); > \> \> clear s1; > \> \> catch ME > \> \> Screen('FillRect',w, bkgcol); > \> \> Screen('Flip', w); > \> \> Screen('LoadNormalizedGammaTable',w,oldclut); > \> \> Screen('Preference', 'TextAntiAliasing', oldEnableFlag); > \> \> Screen('CloseAll'); > \> \> %--- Stop communication with Bits# --- > \> \> delete(s1); > \> \> clear s1; > \> \> psychrethrow(psychlasterror); > \> \> end > \> \> > \> \> %--------------------------------------------------// > \> \> > \> \> > \> \> However, the same error messages still occurred. > \> \> > \> \> PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: ATI Radeon HD 6770M OpenGL Engine :: 2.1 ATI-1.0.29 > \> \> PTB-INFO: Renderer has 512 MB of VRAM and a maximum 494 MB of texture memory. > \> \> PTB-INFO: VBL startline = 768 , VBL Endline = -1 > \> \> PTB-INFO: Beamposition queries unsupported on this system. Will try to use kernel-level vbl interrupts as fallback. > \> \> PTB-INFO: Measured monitor refresh interval from VBLsync = 11.754849 ms [85.071279 Hz]. (50 valid samples taken, stddev=0.060949 ms.) > \> \> PTB-INFO: Reported monitor refresh interval from operating system = 11.764704 ms [85.000015 Hz]. > \> \> PTB-INFO: Small deviations between reported values are normal and no reason to worry. > \> \> PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 1027 ... > \> \> PTB-INFO: Will use 8 bits per color component framebuffer for stimulus drawing. > \> \> PTB-INFO: Will use 8 bits per color component framebuffer for stimulus post-processing (if any). > \> \> LoadIdentityClut: Info: Could not use GPU low-level setup for setup of pixel passthrough. Will use fallback method. > \> \> LoadIdentityClut: Info: If you have an AMD/ATI GPU, you may get this working by loading the PsychtoolboxKernelDriver > \> \> LoadIdentityClut: Info: on OS/X or using a Linux system properly setup with PsychLinuxConfiguration. > \> \> Building a fragment shader:Reading shader from file /Applications/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine\_FormattingShader.frag.txt ... > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> PTB-ERROR: Failed in processing of Hookchain 'LeftFinalizerBlitChain' : Slot 1: Id='Builtin:RenderClutBits++' --\> Aborting chain processing. Set verbosity to 5 for extended debug output. > \> \> PTB-ERROR: Bits++ CLUT encoding failed. No suitable CLUT set in Screen('LoadNormalizedGammaTable'). Skipped! > \> \> > \> \> > \> \> > \> \> I also double checked the config.xml file located in the Firmware folder which could be seen at the 'USB mass storage' mode. The lines 7 and 8 were already modified following the instruction on page 24 of the manual. And the value of TARGET\_EDID was also changed from "AUTO" to the model of our monitor "SONY GDM-F520.edid". And you see, line 13 (\ ) suggests the working mode is set to BitsPlusPlus. > \> \> > \> \> \ > \> \> \ > \> \> #DeviceType Is Either "VISAGE" Or "BITS#" > \> \> \ > \> \> #if DeviceType Is "VISAGE" Then Other Enables Are Ignored > \> \> #for Bits sharp normally USB\_CDC is ON only > \> \> \ > \> \> \ > \> \> \ > \> \> #set only one video mode enabled at a time > \> \> \ > \> \> \ > \> \> \ > \> \> #set only one stereo decode mode enabled at a time > \> \> \ > \> \> \ > \> \> \ > \> \> #enable temporal dithering for LCD displays only > \> \> \ > \> \> \ > \> \> #Sampling Mode = "1kHz" or "User" > \> \> \ > \> \> #User Defined Sampling Rate For Returned Data > \> \> #N Samples Per Frame > \> \> \ > \> \> #channels enabled will be returned over USB or logged to file > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> #configure connected response box > \> \> #\ > \> \> #\ > \> \> #\ > \> \> #\ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> \ > \> \> > \> \> > \> \> Now it seems the Bits# was connected to the iMac and installed following the instruction in the manual. Do you have any idea for further testing? I noticed another Bits# user was complaining that his Bits# did not work on his Mac mini with Mountain Lion operating system. Mine is an iMac with Mountain Lion, too. The graphic card is an ATI Radeon HD 6770M. > \> \> > \>