@impeteimpete wrote: Sun Feb 06, 2022 9:28 amHi folks,ZincT wrote: Sat Feb 05, 2022 7:59 pmJamminFool wrote: Sat Feb 05, 2022 7:48 pm It's certainly a tricky one to solve; I don't envy Pete.
Is there any way to find out which version of JUCE is being used? "Help - About" mentions JUCE but not which version.
For what its worth, the reason I had problems with MIDI event timing were several:
- JUCE: Ambiguity in the documentation as to how MIDI time stamps were supposed to be used for each audio block; if interested, these need to be numbered from zero for every audio block emitted (so they're always relative to the start of the block)
- JUCE: the AUv3 implementation should have emitted absolute MIDI event times to the AU subsystem; but it was sending the "zero based" relative time I noted above; note that the VST implementation in JUCE handled this the right way. I think the reason they had the bug in the AU adaptor, is down to the ambiguity I mentioned above. I actually found this issue (and fix) independently of the JUCE team a couple of days back; it turns out they'd fixed it at the end of December (in a version we'd not merged-in)
We don't merge-in JUCE updates very often, as I'm cautious not to destabilise Wotja; I have patched JUCE quite extensively to (say) support tvOS and work-around various issues with plug-in scanning and what have you, and I have to be very careful not to break all my fixes!
Finally - Wotja 22.1.2 (sent this morning to Beta testers!) has a version of JUCE 6.1.5 - so completely up-to-date. The primary reason for my updating from JUCE 6.1.4 was to get some Accessibility fixes.
Best wishes, Pete
That is encouraging news! Thanks!
