As noted on earlier threads launching Finale 2006-2008, also initiates a launch of Vienna Ensemble. Finale is, of course, limited to using plugins made by or "powered by" Native Instruments, so this launch has no practical positive effect.My guess is that Finale is launching VE in an attempt to validate it - - which would explain the fact that it launches VE every time Finale is launched. Under OS 10.5.1, the delay is minimal, but it is a serious problem under OS 10.4.11 as Finale appears to freeze - - but eventually does open if one waits 5-6 minutes (This5-6 delay occurs even when one has previously launched the VE standalone to avoid having to go through the license checking process while Finale is trying to launch - - if the VE standalone has not first been launched, the delay is even longer). In any case it would appear that Finale misinterprets something in the VE Component (MacHD/Library/Audio/Plugins/Components) that it reads as meanng that VE is an NI product. It did not do this with first beta release of VE, not does it do this with the Vienna Instruments sample player, Ozone 3, Pianoteq, Altiverb 6, etc.
While awaiting a fix for this problem one can do the following:
Remove the VE Component from the Components folder (found as I said above, in MacHD /Library/Audio/Plugins/Components) and put it in a new folder on the desktop.
Launch Finale
Then, if you wish to use the VE standalone as a playback object for Finale
Set Finale's MIDI output to an IAC bus
Put the VE Component back in the Components folder
Launch the VE standalone and assign its MIDI inputs to the appropriate IAC bus.
Work in Finale.
Quit Finale
Quit VE
Remove VE Component from the Components folder before relaunching Finale. (It is not necessary to restart the computer.)
This is, obviously, somewhat inconvenient, but it does work and avoids long delays in Finale's Launch.
I hope this helpful to those who have encountered this problem.
Stephen
