It occurs to me that where I still wind up with a subtle glitch, a lag or time offset, is always at the end of an animation loop, where the 5-6 video streams all have to start over at the same time. This is a problem I’ve now successfully resolved save for a short subset of problematic nodes with 5 or 6 sizable video hotspots synchronized.
When, however, only 3-4 video clips have to start over at the end of a loop, there is no glitch, and no loss of synchronization. This gives me an idea:
It occurs to me that if the loops were staggered, with some starting/ending at a different time than the rest, this might fix the issue. I imagine 3 out of 6 could start at the moment the node is opened, in a 4-second loop. There’d also be - for the other three areas - three two-second clips that play only once, no loop, followed by another three in a four-second loop offset by two seconds. So in effect the only time there’d be 6 clips starting would be the time the node is initially loaded, every time there’s a loop point after that it’d only affect 3 video clips.
I can understand how to do this conceptually but am finding it difficult to actually write working code for it, using the available DAGON command reference and documentation.
I wrote what I thought would work, then spent a couple of hours debugging it trying to make this crazy idea actually run. It’s still not working. Can anyone give me guidance on how to code this?
[EDIT: After some 30-odd attempts to rewrite the code I’m now finally making progress, I hope. It’s partially working at this point but a few adjustments still need to be made. Still not quite right though… and I’m running out of ideas at this point.]
[EDIT #2 - I’m stumped. I will probably just wait until Dagonity is released and try that next, if it really is as user-friendly as Agustin says it is.]
[EDIT #3 - I just tried something on a hunch - which was taking one of the more problematic nodes and recording the screen with a 60 fps camera, then playing it back at 10 fps in the hopes of getting a better look at the glitchy out-of-sync behavior.
I realized two things:
-there was actually an extra lag, at the time when the videos looped, not much but 1-4 extra lagging frames, out of 60, every time the video hit a loop point.
-the extent of the problem seemed to correlate strongly with video surface area. The largest video hotspot size, a 1024x1024 pixel video clip, was clearly causing more lag than any of the others.
A hypothesis: If every video clip has the exact same, smallish surface area, the video clips will all have the exact same miniscule amount of lag and thus will not only not go out of sync gradually over time, but will not have discernible momentary visual glitches.
I am now testing this hypothesis.]