It seems that the timeInSamples given by Live is wrong when the tempo changes (tested with vst2).
When getting timeInSamples in processBlock(), I expect it to increase by numSamples, whether the tempo changes or not.
But the tempo changes seem to make some timeInSamples jumps.
Am I missing something, or is it most likely an ableton bug?
As someone who just implemented variable tempo in their DAW (which is a nightmare) this is really fascinating to see.
I feel confident saying this is probably a Live bug, perhaps with the time->tempo mapping algorithm they’re using giving back the wrong time (maybe they’re going time->tempo->time->samples?).
Wow, that’s interesting. This definitely looks like an Ableton bug. JUCE’s timeInSamples comes pretty much straight from VST2’s audioMasterGetTime opcode and JUCE does not do anything special with this number - it just passes it on to you.
Ableton has a new bug reporting system. Can you let me know exactly which Live version (i.e. x.x.x) you encountered this bug. Which OS were you using? 32-bit or 64-bit?
Yes, I had reported it back then in February 2018. They had estimated this being a bug on their side and put in their backlog. No news since then.
You should report it again in my opinion, especially as it also concerns vst3 now.