Open Bone008 opened 6 years ago
This is hopefully made less crucial by this change: 01e91de73cb83190c8e1dfe92737f9576736357b
Now the cursor position is not updated when music playback is started from the "transfer" dialog, which makes it much less CPU intensive since we are no longer polling waveOutGetPosition
constantly. The thread can still hang in theory, but should hopefully not happen on any reasonable modern system.
Leaving this open in case this theory does not survive practical tests.
Since the playback thread has control over the cursor position during playback, hickups in playback are never caught up. This makes the "Start internal music with sequence" feature virtually useless for shows and full rehearsals, because there is no guarantee that the music will stay in sync.
Contributing factor is possibly the CPU-intensive visualization, so #17 could help as well.