Ac_compute_device_uuid's output is based on invalid pci bus info

Hardware
,
1

We have a low priority, mainly cosmetic issue:

Screen(‘GetWindowInfo’, window) prints a message

ac_compute_device_uuid’s output is based on invalid pci bus info

to the Octave console (we do not perceive any other obvious problems or side effects).

In our application we use PredictVisualOnsetForTime in every trial to sync audio and video. PredictVisualOnsetForTime calls Screen(‘GetWindowInfo’, window) and fills the console with these messages rendering it basically unusable for trial related output (timing information etc.).

Would it be safe to replace

wininfo = Screen(‘GetWindowInfo’, window);

by

wininfo = Screen(‘GetWindowInfo’, window, 7);

in PredictVisualOnsetForTime? This avoids the message. Or is there any other workaround?

Thanks a lot! Andreas

PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit Intel (Version 3.0.22 - Build date: May 19 2025).
PTB-INFO: OS support status: Linux 6.8.0-88-lowlatency Supported.

PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM] GPU with DCE-6.0 display engine [2 heads].

PTB-INFO: OpenGL-Renderer is AMD :: OLAND (, LLVM 15.0.7, DRM 2.50, 6.8.0-88-lowlatency) :: 4.5 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1~22.04.3
PTB-INFO: Screen 1 : Window 10 : VBL startline = 1080 : VBL Endline = 1241
PTB-INFO: Measured monitor refresh interval from beamposition = 8.326594 ms [120.097129 Hz].
PTB-INFO: Will try to use OS-Builtin OpenML sync control support for accurate Flip timestamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 8.326640 ms [120.096460 Hz]. (50 valid samples taken, stddev=0.000548 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 8.333472 ms [119.998001 Hz].

2

Yes.

It is a warning that the queried device unique id UUID of the gpu can’t be properly determined from the PCI bus device info,therefore the returned wininfo.GLDeviceUUID will be likely invalid. It would only affect use with the Vulkan display backend, but use of Vulkan backend is pointless anyway, as the gpu is too old and wouldn’t offer any advantages.

Don’t know why that wouldn’t work, but it is inconsequential here, apart from the debug message clutter. I’ll change PredictVisualOnset… to use infoType 7 future releases to avoid the clutter..

3

Great! Thanks a lot for the quick response, Andreas