VVocal doesn't use ARA. We did that more than 5 years before ARA was available.
However the VVocal API is very similar to ARA in some ways especially the random access part. However ARA implements a bunch of other stuff which is used by Melodyne. Document management and editing, transport control etc. The fact that we already had the basic framework for doing random access audio in SONAR is what made us choose to adopt ARA.
Internally we don't have an adapter for VVocal - it uses its own API which is way simpler than ARA. However all the commands that create region effects etc use the same code for both ARA and VVocal. So it definitely helped to have that in place already.
bvideo
mudgel
bvideo
One very clever and helpful bit was to wrap ARA around VVocal.
How can that be.
VVocal itself was not modified in the release that brought ARA. It wasn't even included. On the other hand, it has a similar high-level architecture, such as an editor and direct access to the audio file, and it produces a new audio file for playback. But someone had to make some kind of software adapter to mate VVocal's older implementation with the ARA api. I thought that was clever and helpful.