Good to know. Because I’m having a lot of fun working with this, l want to encourage you guys (who I believe have written Sugarcube itself…?) to dig into this problem:
Loops are crucial if you are trying to design sound for an experience where time is a variable. I can’t necessarily rely on tracks that have a set time. But I can use loops.
For example, imagine I have a track 50.5 seconds long. But a user might be on the page for as long as 90 seconds, or as short as 45 seconds. The last 5.5 seconds of my track is a standalone loop. Ideally in Twine, I would be able to specify that section of the track that I want to loop (45secs - 50.5secs). Failing that, I could trigger a second track, which is just the loop, at the precise moment that the first track ends. Either way, the last 5.5 seconds loops until the user moves on from the page. However, none of this is possible without continuous and seamless loop functionality.
It would be worth flagging this up in the Sugarcube documentation as well, as we’ve built a fairly complex sound design for this project around the assumption that
loop meant “continuous and seamless.” I don’t think that the current definition:
“Set the selected tracks to repeat playback upon ending normally”
clearly implies a gap between repeats. My tracks begin and end with sound, so I would imagine continuous sound when track repeats.
I’m happy to discuss any of this further.
Many thanks, Ben