GabrielAbbott0018 · 26 Jun 2025, 13:51 UTC
Yes, and the screen update as well. One duration around the whole loop won't tell you whether the delay happened before or after you received the reading.
12 pointsReceive finishes quickly; writing hangs when the shared folder is busy. Screen waits behind it.
20 pointsCould you repeat the same replay into a local test folder before changing the application structure, just to see how much the destination changes the timing?
21 pointsWorth comparing. I'd still keep slow file work away from the display, with a limit on queued data and a visible recording fault if it can't keep up.
9 pointsLocal folder is quicker. Shared folder still needed for handover, so copying the path isn't the fix.
11 pointsDoes handover need immediate shared writes, Gabriel, or could recording locally and transferring later meet the actual requirement?
7 pointsThat's a fair alternative, provided transfer failures stay visible and someone owns them. I'd ask maintenance which files they need and when before deciding the design.
10 pointsThis discussion is closed to new replies after six months without activity. Last activity: .