VE interaction with Finale still a serious problem in latest version of VE

[stevesong]

 A bug I described in earlier postings consisting of an unwanted interaction of Finale 2008 and VE is still present in the new version of VE.

The interaction is as follows:

When Finale is launched it initiates a launch of the VE plugin.

That Finale launches VE serves no purpose - - as current versions of Finale can only instantiate plugins made by or "powered by" Native Instruments.

This bug was not present in the first (Beta) release of VE.

Although the first time I launched Finale (running under OS 10.4.11) the delay caused by the launch of the VE plugin was minimal, on subsequent launches, it became very extended - - taking several minutes for Finale to open (prior to attempting to lauch Finale I had opened the VE standalone to avoid having the license checking process interfere with the launch). During these minutes, Activity Monitor reported that Finale was "not responding"  but it eventually did launch successfully.

Unhappily, this problem has made it necessary for me to uninstall this latest version of VE from the OS 10.4.11 startup disk - - as I had to uninstall the previous version (for the same reason). Fortunately, under OS 10.5.1, although launching Finale still initiates a useless launch of the VE plugin, the delay in Finale's launch is minimal (if I have opened the VE standalone prior to launching Finale).

I hope that this bug will be addressed soon!

[cm]

just an idea (not knowing details about finale) ... can't you set preferences in finale which plugins to launch and which not?

maybe you also could delete the (VI-)component on your system (if not needed by another application).

if both does not work maybe you could move the component to a location where finale does not look during launch but allows usage by an other app?

christian

[stevesong]

 Christian:

Thanks very much for responding and for suggesting possible workarounds.

Finale does have a preference setting supposedly directing to look for components and plugins in specific folders - - however, although I selected folders other than the Library folders where the VE files are normally kept, it appears to find them as launch of VE still takes place whenever  Finale is launched. No doubt this is because Finale automatically looks for NI plugins and components in the Library folder regardless of the preference settings.

Any idea where I might put the VE component so that it can be detected by Logic and DP, but not by Finale?

At the moment, I really have been forced to give up on the current version of VE when running OS 10.4.11 as the delay in launching Finale is several minutes - - even though I have previously launched the VE standalone to avoid having to go through the license checking process at the same time as launching Finale - - but, unhappily, this also makes it impossible to use VE with Logic or DP or as a standalone when using this startup disk.

When running under OS 10.5.1, the delay is minimal (as long as I've already launched the standalone before launching Finale) so, in that case, I can keep VE.

Obviously this is a bug in VE as launching Finale does not initiate launch of any other plugin. For example, if NI plugins have been instantiated in a particular file then those plugins launch only when that specific file is opened.

Something seems to have changed in VE since the initial Beta release that is causing this behavior. As I noted earlier, this anomalous behavior did not occur when that release was installed. I hope this helps you trace the source of the problem. 

I am aslo wondering if the latest version of VE might be more processor efficient than the previous version. with the preious version, running under OS 10.5.1, with Finale 2008 playing a VE template with 13 Level 1 matrices instantiated + 2 legato instruments + 1 instance of Altiverb produced intermittent processor overloads. Running the same matrices instantiated in Logic 8 as VI instances + 4 legato instruments + Altiverb + Ozone 3 and using Finale 2008 as the MIDI source (running on the same computer), there have been no processor overloads. Activity Monitor shows significantly higher processor use when VE is the playback object than it does when the Logic 8 file is the playback object. (I realize that it is not trivial that Finale 2008 is a processor hog - - using 80-90% of one processor merely for MIDI playback and that performance is also affected by the fact that Finale 2008 is not multi-processor aware.)

Again many thanks for your help. 

Stephen 

[cm]

steve, a member of the VSL team agreed to create a respective setup for testing (i'd assume we'd have to clean the macPro first from various betas ...).

i had initially a similar problem on a machine with premiere and VST, but after re-ordering VST locations and preferences it's solved.

christian

[stevesong]

 Christian:

Thanks very much to you and members of the VSL team for taking the time and making the effort to work on this problem.

Stephen

[michael.matthews]

Hi This still is a problem for me with the latest VE release. In fact, it seems to be worse, because now Finale is freezing upon opening when it tries to launch VE. Michael

[stevesong]

Michael:

If my experience is any guide, and you are running OS 10.4.x,  wait five minutes or so and Finale will probably still launch - - it only appears, rather convincingly, to freeze.  If you run OS 10.5.1, the delay is minimal. For this reason I have uninstalled VE from my usual startup disk (which runs OS 10.4.11). My OS 10.5.1 disk is a clone (made by SuperDuper) of my usual startup disk. I always install major software updates on it before installing them on the main startup drive.

[michael.matthews]

Thanks, Steve. Michael