Hi, Yes. That’s our contingency plan. The ideal, however, is that we want to trigger audio timings using the project’s in-built reading speed variable. (The subject of my first post on this forum).
Essentially, the story learns how fast you read at on-board, and then reveals the text in sentences and paragraphs at that speed (calculated as “words per second”). Part of the idea of the variable was to use it as a way of triggering sound cues, whose timing would be unique to each reader’s reading speed. (This approach is working out really well on desktops, but not so well on mobile devices).
We could definitely create an average estimate of “pre-wait silence,” but the ideal would be to incorporate the more personalised audio timings based on the “words per second” variable.