Our separate monitoring laptop looks frozen when the log folder is busy. The cell controls keep working. I switched on detailed trace to understand a read problem and may have added a display problem instead. I'd like to time the read and write separately before somebody orders a faster laptop to solve an argument.
Time the display update too, then exercise controlled read and write delays offline; a slow folder may be relevant, but you still need to see what the screen is actually waiting for.
Developer found file writes inside the display update path. The revised offline version hands recording to a bounded queue and shows reading age separately from recording gaps. Slow-read, slow-write and full-queue cases behave properly. Normal workshop launch and exported-file review are still to do.