-
+
SYNCHRONIZATION: Non-linear motion
- what happens when get_transport_position() returns a value that
isn't even close to where we expect to be?
- for apps with everything in memory, just chase (jump + resync)
- for apps requiring disk i/o:
- jump takes time (disk I/O takes time)
- might need to jump again before disk I/O is complete
- easier if we know the jump points ahead of time (e.g. looping)
- general problem is extremely hard to solve
- present in VST as well
- may be no really good solution