Despite our best efforts (#27, for example), there remains a fundamental inconsistency between playback and perform : playback starts from the next set, perform starts from the current set.
This induces several problems. For example, this means that clicking a set on the visualizer will mean that the user can start playing from there, but the playback will skip that index and move to the next one instead. There are many other consequences that can be recorded here for memory.
Another example : when first starting a file, if we jump to an index that isn't the first one, perform mode will skip it, and start from the next. This only happens once (?). (Maybe it's a different bug ?)
Despite our best efforts (#27, for example), there remains a fundamental inconsistency between playback and perform : playback starts from the next set, perform starts from the current set.
This induces several problems. For example, this means that clicking a set on the visualizer will mean that the user can start playing from there, but the playback will skip that index and move to the next one instead. There are many other consequences that can be recorded here for memory.