Well, it is always possible to write a script that would run them one after another and run the script at the login. Just a thought...

One after another doesn't work normally, why would this work in a script?

Edit:  Correction ... it does work if you open with app explicitly.  Opening by double clicking the mframe file does not work (even when the file is associated with the appropriate app.

dbudde, are you using Automator? I am curious to know how you are telling it to select the application once it is launched and File / Open from within that application. The closest I can get to opening the metaframe within the application is "Watch me do," and that has been tricky because the desktop topography changes. 

Perhaps you are using AppleScript. 

I don't have a working script yet.  But I can make it work manually in the finder by double clicking the first mframe file.  Then select the second mframe file and right click and slect 'open with' and select the appropriate app.  For whatever reason 'open' or double click doesn't work for the second file.

I tried to get these same commands to work in Automator, but it won't work.  I also tried with various amounts of delay between opening the first and second file.  Nothing works when trying to script this.  There must be a bug somewhere in the app association mechanism either in VE Pro or in OS X.  I don't know.

Boy, have we been traveling parallel universes. In Automator, I was throwing every command I could find at this, including Pause and Hide Applications. I brought it to the point where the mouse would click the second VE instance (the server window after it was launched, to set up a File / Open menu). Onscreen it looked right, but I still got an error. 

In a bug-free world, we'd just drag both metaframes into Login Items and go make music. 

My apologies for interrupting the flow of consciousnes but - Back to re-visiting the original topic of this thread:

Does VE Pro only recognize 8 instances in localhost mode (on the same machine as the DAW host software) or only 8 instances total (on localhost and x number of slaves)?

Jack

I believe the answer is eight instances per server.

That's my assumption too. If it was limited to eight instances per network, this thread would be about twenty pages by now....

Thanks gentlemen.

I can live with that. Sorry that it's a limitation for your work flows.

.

The current limit is 8 instances per server. We are looking at raising this limit in an update.

@MS said:

The current limit is 8 instances per server. We are looking at raising this limit in an update.

Thanks Martin! I think you will make many people very happy if you change this [:D]

Best regards,

Peter

FANTASTIC!!!!

I gave up yesterday. But I was in Automator.  I wouldn't take too much time with it, though, because it's the kind of thing that can be handled in an update. 

All we really need is a fix where the "Open With" setting works. Presently, if you double-click on a second metaframe file that is set to "Open With" the 32-bit server, nothing happens if the 64-bit is already running. And vice versa -- if the 32-bit is running and you double click on a metaframe set to open the 64-bit server, nothing happens. 

VSL, could you acknowledge that, and will a fix be coming? Thanks. 

Once the bug is fixed, we should be able to drag the two metaframe files into Login Items and load on start-up without any scripts. 

You cannot duplicate the server, it does not allow you to run two of the same server architectures at the same time (You will get a warning message).

Actually, I forgot about the other bug. As both dbudde and I noted, when both metaframes are dragged into Login Items, Syncrosoft generates an error message, and neither program opens. I don't know if this is linked to the double-click error where a second metaframe won't launch in Finder after the first metaframe has loaded.  

It occurs to me that the synchrosoft error on login items might get resolved when the update to the elicenser is released for Snow Leopard.

Just a quick word of caution for those wanting to use more than 8 instances of VE Pro who can use the VST3 version of the plugin (I know this won't apply to the majority of you on this thread who seem to be using Logic).  Obviously using 8 VST2 VEPs are going to chew through more CPU cycles and affect ASIO performance than a single VST3 instance (which can cater for multiple midi ports).  So as a quick test I created 3 new Cubase projects to see how much this was affected;

the first with 8 VST2 VEPs loaded, each with a single empty Kontakt 3.5 instantiated

the second with 8 empty Kontakt 3.5s loaded into Cubases VST Inst rack as per normal

the third with a single VST3 VEP with 8 empty Kontakt 3.5s loaded within

Then I measured the %CPU and %ASIO performance (VST Performance meter within Cubase) and found the following at buffer settings of 32, 64 and 128 samples

(sorry about the table formatting)