veyepar: Improving Graphics Interactivity

Author(s):	Keith Packard
Location	C3
Date	jan Thu 24	Days Raw Files
Start	10:40	First Raw Start	10:08
Duration	0:45:0	Offset	0:31:08
End	11:25	Last Raw End	11:38
Chapters	00:00 0:28:37 0:45:20
Total cuts_time	45 min.

https://2019.linux.conf.au/schedule/presentation/134/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Improving_Graphics_Interactivity_Its_All_in_the_Timing.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Interactive applications, which includes everything from real time games through flight simulators and virtual reality environments, place strong real-time requirements on the whole computing environment to ensure that the correct data are presented to the user at the correct time. This requires two things; the first is that the time when the information will be displayed be known to the application so that the correct contents can be computed, and second that the frame actually be displayed at that time. These two pieces of information are managed inconsistently through the graphics stack, making it difficult for applications to provide a smooth animation experience to users. And because of the many APIs which lie between the application rendering using OpenGL or Vulkan and the underlying hardware, a failure to correctly handle things at any point along the chain will result in stuttering results. Fixing this requires changes throughout the system, from making the kernel provide better control and information about the queuing and presentation of images through changes in composited window systems to ensure that images are displayed at the target time, and that the actual time of presentation is reported back to applications and finally additions to rendering APIs like Vulkan to expose control over image presentation times and feedback about when images ended up being visible to the user. This presentation will first demonstrate the effects of poor display timing support inherent in the current graphics stack, talk about the different solutions required at each level of the system and finally show the working system. markdown
Comment:	production notes