'PTB - ERROR: SYNCHRONIZATION FAILURE !'
12 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
I am trying to run some scripts via Psychtoolbox-3 that we routinely use in the lab, but each time, I get the error: 'PTB - ERROR: SYNCHRONIZATION FAILURE!'. In the past, we used to turn off the sync tests to get the scripts to run, because we couldn't get them to disappear in Windows 10 with our setup. We just bought a new computer with the setup below, and are still getting the sync error.
The computer is running MatLab 64-Bit (version 3.0.16) with a Nvi 14 (Radeon RX 5500/5500M /Pro 5500M) graphics card on GNU/Linux X11 (Ubuntu 20.04), and the monitor is a Lacie electron blue 22' (though we have also tried with a Mitsubishi diamondpro 2070sb). The screen resolution is at 1024x768 and the refresh rate is set to 120hz. I pasted the generated MatLab output below:
PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.16 - Build date: Apr 25 2020).
PTB-INFO: OS support status: Linux 5.4.0-42-lowlatency Supported.
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: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] GPU with DCE-10.0 display engine [6 heads].
PTB-WARNING: Querying rasterbeam-position doesn't work on your setup! (Returns a constant value 0)
PTB-WARNING: This can happen if Psychtoolbox gets the mapping of connected displays to graphics card
PTB-WARNING: outputs wrong. See 'help DisplayOutputMappings' for tips on how to resolve this problem.
PTB-WARNING: However, this probably doesn't really matter on your setup for most purposes, as i can use OpenML
PTB-WARNING: timestamping instead, which is even more precise. Only few applications need beampos queries in this case.
PTB-WARNING: Couldn't even collect one single valid flip interval sample! Sanity range checks failed!
PTB-WARNING: Could be a system bug, or a temporary timing problem. Retrying the procedure might help if
PTB-WARNING: the latter is the culprit.
PTB-WARNING: Couldn't collect valid flip interval samples! Fatal VBL sync failure!
PTB-WARNING: Either synchronization of doublebuffer swapping to the vertical retrace signal of your display is broken,
PTB-WARNING: or the mechanism for detection of swap completion is broken. In any case, this is an operating system or gfx-driver bug!
WARNING: VBL Calibration run No. 1 failed. Retrying...
PTB-WARNING: Couldn't even collect one single valid flip interval sample! Sanity range checks failed!
PTB-WARNING: Could be a system bug, or a temporary timing problem. Retrying the procedure might help if
PTB-WARNING: the latter is the culprit.
PTB-WARNING: Couldn't collect valid flip interval samples! Fatal VBL sync failure!
PTB-WARNING: Either synchronization of doublebuffer swapping to the vertical retrace signal of your display is broken,
PTB-WARNING: or the mechanism for detection of swap completion is broken. In any case, this is an operating system or gfx-driver bug!
WARNING: VBL Calibration run No. 2 failed. Retrying...
WARNING: Will enable VBL busywait-workaround before trying final VBL Calibration run No. 3.
WARNING: This will hopefully work-around graphics driver bugs of the GPU sync-to-retrace mechanism. Cross your fingers!
PTB-WARNING: Couldn't even collect one single valid flip interval sample! Sanity range checks failed!
PTB-WARNING: Could be a system bug, or a temporary timing problem. Retrying the procedure might help if
PTB-WARNING: the latter is the culprit.
PTB-WARNING: Couldn't collect valid flip interval samples! Fatal VBL sync failure!
PTB-WARNING: Either synchronization of doublebuffer swapping to the vertical retrace signal of your display is broken,
PTB-WARNING: or the mechanism for detection of swap completion is broken. In any case, this is an operating system or gfx-driver bug!
PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: Radeon RX 5500 XT :: 4.6.14736 Compatibility Profile Context 20.20
PTB-INFO: VBL startline = 768 , VBL Endline = -1
PTB-INFO: Will try to use OS-Builtin OpenML sync control support for accurate Flip timestamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=1000000000.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 8.347036 ms [119.803001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
WARNING: Couldn't compute a reliable estimate of monitor refresh interval! Trouble with VBL syncing?!?
WARNING: Mismatch between measured monitor refresh interval and interval reported by operating system.
This indicates massive problems with VBL sync.
----- ! PTB - ERROR: SYNCHRONIZATION FAILURE ! -----
One or more internal checks (see Warnings above) indicate that synchronization
of Psychtoolbox to the vertical retrace (VBL) is not working on your setup.
This will seriously impair proper stimulus presentation and stimulus presentation timing!
Please read 'help SyncTrouble' for information about how to solve or work-around the problem.
You can force Psychtoolbox to continue, despite the severe problems, by adding the command
Screen('Preference', 'SkipSyncTests', 1); at the top of your script, if you really know what you are doing.
Error using Screen
See error message printed above.
Error in klein_baseline_demo (line 101)
w =Screen('OpenWindow',ScreenNumber, gray);
Help would be greatly appreciated. Thank you!
0 Kommentare
Antworten (0)
Siehe auch
Kategorien
Mehr zu Timing and presenting 2D and 3D stimuli finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!