There’s been some previous discussion of this here on the forum – I seem to recall @FredGUnn having a similar problem, and perhaps he can remember the details and maybe even point us to the original discussion.
Hmm, I remember something about that, but that particular issue wasn’t mine, as I don’t have any instances in my default setup with over 16 instruments requiring another port. I have each VEP instance on port 1 and all works fine.
I was never able to determine what was really going on there, I’m afraid. I hate to speak ill of our wonderful customers, but to some degree that thread feels a bit like the blind leading the blind. There’s no reason I can think of why you should not be able to access ports beyond the first. Perhaps something to ask John about – he’s got VE Pro, and I haven’t.
far be it from me, but 2 separate instances with VE pro limited to 10 tracks each works fine. So I suspect there IS a snafu somewhere. But it’s an easy work around and totally worth it to access the new Live stage feature !
In the thread you linked above I gave clear enough instructions what one should do in order to get more ports activated. VE Pro is flexible enough to cover almost every situation.
First of all, before starting with creation of a VE Pro template, the most important thing is to come up with clear structure, by knowing well enough the specifications of the Virtual Instruments and their players. For example Kontakt, Halion and UVI Falcon allow loading of multiple instruments into a single instance, while Spitfire player, Sine, Synchron and VI Pro allow only single instrument per instance. Two different building strategies could be applied depending on the player.
I would recommend a VE Pro instance per instrument Group - Woodwinds, Brass, Percussion, Keys, Strings… This keep the order clear enough and well structured.