VBL endline beamposition queries and audio timestamping issues

PsychtoolboxVersion: 3.0.19 - Flavor: Manual Install, 19-Jan-2026
OS Name: Microsoft Windows 11 Enterprise
Version: 10.0.22631
Processor: Intel(R) Core(™) Ultra 7 165H, 3800 Mhz, 16 Core(s), 22 Logical Processor(s)
MATLAB: 9.13.0.2698988 R2022b Update 10
Speakers: 2-SoundWire Speakers
Speaker driver version: 10.0.22621.1

Hi there,
I’m trying to run the Stop Signal Task on MATLAB with new laptops and I’m getting these errors:

PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: NVIDIA RTX 1000 Ada Generation Laptop GPU/PCIe/SSE2 :: 4.6.0 NVIDIA 581.95

PTB-INFO: VBL startline = 1200 , VBL Endline = -1

PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping as fallback.

PTB-INFO: Timestamps returned by Screen(‘Flip’) will be therefore less robust and accurate.

PTB-INFO: Measured monitor refresh interval from VBLsync = 16.654572 ms [60.043572 Hz]. (50 valid samples taken, stddev=0.138633 ms.)

PTB-INFO: Reported monitor refresh interval from operating system = 16.666667 ms [60.000000 Hz].

PTB-INFO: Small deviations between reported values are normal and no reason to worry.

PTB-INFO: WINDOWS DWM DESKTOP COMPOSITOR IS ACTIVE. On this Windows-10 or later system, Psychtoolbox can no longer reliably detect if

PTB-INFO: this will cause trouble for timing and integrity of visual stimuli or not. You might be just fine, or you could be in trouble.

PTB-INFO: Use external measurement equipment and independent procedures to verify reliability of timing if you care about proper timing.

PTB-INFO:

PTB-INFO: Using PortAudio V19.7.0-devel, revision unknown

PTB-INFO: New audio device 2 with handle 0 opened as PortAudio stream:

PTB-INFO: For 1 channels Playback: Audio subsystem is MME, Audio device name is Microsoft Sound Mapper - Output

PTB-INFO: Real samplerate 22254.000000 Hz. Input latency 0.000000 msecs, Output latency 100.656062 msecs.

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

PTB-WARNING:PsychPortAudio(‘Stop’): Audio device with handle 0 had broken audio timestamping - and therefore timing - during this run. Don’t trust the timing!

INFO: PTB’s Screen(‘Flip’, 10) command seems to have missed the requested stimulus presentation deadline

INFO: a total of 10 times out of a total of 519 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.

Any help would be greatly appreciated.

Thanks,
Bree

Hm. Seems like there are 2 problems, graphics and audio. Regarding the graphics problem, is this the latest NVIDIA driver available for your system? Because, very recently, I had vsync problems with a desktop system, where Windows had auto-installed an outdated version 576.88, which was no good. My problem was fixed once I updated to 591.44 (and shortly after to 591.74).

This thread has been superseded by VBL endline beamposition queries and audio timestamping issues 2