.
@Migot said:
I'm using both Finale 2006b and VSE /VI / VE and I would like to say that, Yes launching Finale make VE starting too but doing this in less than 20 second! Finale is not freezing at all...? You may even leave VE Service run behind the scene causing no problem! This on a G5 PPC, 10.4.11 8Gig ram.... Did you update your VI and VE to the last version available? VE Software 2.0.2779 (2007-12-08) VI Software OS X PPC 1.1 (2007-11-24) Have a look there: http://vsl.co.at/en/68/375/377/239.htm So, Hope this will help Sincerely
Thanks for your comments.
I can't explain why my experience is so different from yours except that I'm running Finale 2008a while you are running Finale 2006b. I have the latest versions of VE and VI software. As I've mentioned elsewhere, the delay when running under OS 10.5.1 is minimal - - like the one you describe, but I and some others experience a long 5 - 6 minute delay when launching Finale 2008 when runnning under OS 10.4.11 if the VE component is installed in the Components Folder. I should also add that my startup disk is well maintained - I repair permissions and rebuild the directory with Alsoft's DiskWarrior on a regular basis.
Whether the delay is short or long, it appears that Finale is attempting to validate VE every time it (Finale) is launched. This suggests that there is something in the VE component that Finale interprets as a sign that VE is an NI plugin. If one could identify what this sign is and change it, one might be able to eliminate this behavior. Remember that this did not occur with the first beta release of VE.
In the meantime, I hope that my workaround will be helpful to those whose experience is similar to mine.