First I’d like to say congratulations on the Dorico 5 release! There is a lot of great things going on with this release!
So, with the impending doom of VST2, I’m slowly transitioning as much as I can to an all VST3 setup (at least as far as Dorico is concerned).
I’ve run into an issue that after a few bars Dorico seems to stop providing information that VST3 plugins can use to build smarter instruments (and some, like Groove Agent, or HALion’s ‘arp engines’ probably NEED to work properly).
Oddly enough, VST2 plugins I’ve tested are working fine in this respect.
To easily illustrate the issue…
I’m looking at two instances of Bidule 0.9784 (and I can snoop this info in similar ways with HALion, and other plugins). One is VST2, the other is VST3.
A ‘sync extractor’ bidule allows me to see/use various bits of information a host sends. The main ones of interest to me at present are:
Playing (1 if transport is going, 0 if stopped)
Tempo (can be used to make better articulation choices)
Bar count (fudge in style or various swaps for soli sections and more)
ASIO Sample count (use to trigger samples or even ‘track’ long audio files at very precise times).
In the VST2 instance of Bidule everything is as expected. The sample count scrolls as expected. The play pin shows a value of 1. Bars count. Etc. Everything works as expected throughout the duration of the entire score.
VST3? It’s a bit different. It’s good for 3 to 4 bars, then poof! No more data! The plugin thinks the transport has stopped!
First three bars it’s looking good…both instances identical:
Somewhere around bar 4…VST3 instance goes poof! It drops all the pins and goes to 0, or default values.
Note: If I run this same scenario in Cubase 12, both the VST2 and VST3 instances of Bidule work as expected. Transport, Tempo, Time Signature, Bar, Sample, Etc…all the pins are correct throughout the entire project.