Vienna Symphonic Library Forum
Forum Statistics

178,856 users have contributed to 42,064 threads and 253,923 posts.

In the past 24 hours, we have 3 new thread(s), 7 new post(s) and 56 new user(s).

  • Spectrasonics instruments and multitimbral performance

    I am running the Spectrasonics instruments under VE Pro which seems to create a limitation as to how many parts I can play at once.   I think I've found that each an every one of the Spectrasonics instruments have a maximum of 8 parts.  This creates a bigger issue: when all three instruments are loaded into the VE Pro 32bit server, I can only use a total of 8 parts - period.  That means if I put in 4 parts into Omnisphere, I can only put 2 into Trillian and two more into Stylus.  It sounds like a lot but I was wondering if there was any way around this limitation - any ideas?  Even if I load another AU channel, there doesn't seem to be a way to not have all the Spectrasonics instruments see the other MIDI channels.  Am O missing something terribly obvious?  Thanks.


  • last edited
    last edited

    @Another User said:

    That means if I put in 4 parts into Omnisphere, I can only put 2 into Trillian and two more into Stylus.

    Yes, this is a limitation of how Spectrasonics developed their plugs. In fact, it's the ONLY limitation that I have found... so you "simply" have to work around it and use multiple instances (or in the case of VST3 or RTAS, use multiple "ports") of VEPro, since the Spectrasonics plgs are forced to use midi 1-8.

    That's just "how it is".


  • Thanks for the explanation - I was hoping this wasn't the case.  How many instances of VE Pro do you think I can open?  I'm running these at 32 bit (not sure if Spectrasonics supports 64 bit) on a brand new 2.66GHz Mac Mini server with 8 GBs of memory.  I run one other instance of VE Pro at 64 bit to take advantage of my Vienna Instruments and the other VE Pro (at 32 bit) handles my Spectrasonics instruments.  Thanks


  • The conventional wisdom is more instances of a plugin = more resources used -- BUT in the case of VEPro server connections at the host, some say it is negligible. Same for instances on the slave -- if you look at resources used for 1 instance with 8 plugins vs. 8 instances with 1 plugin per, the total CPU utilization is supposed to be very close. AND when you consider muti-core and multi-threaded CPUs, some may claim that the "more instances" is actually a more efficient way to work.

    You may as well try this on your own combination of host and server(s) - and please report back.

    PS -- you can run the Sepctrasonics plugs (latest versions) in your 64-bit server. See Spectrasonics site for clarification.


  • I use Omnisphere and Stylus in 64bit works great,as suggested,you should open a seperate VEPro instance for each Spectrasonics library,I dont think theres a limit to the amount of instances you can open,your system will dictate that limit for you. (Just remember to assign the right amount of threads per instance.)leaving the rest for your Sequencer and a thread or two for your OS. Dean.

  • last edited
    last edited

    @jeremyroberts said:

    Yes, this is a limitation of how Spectrasonics developed their plugs. In fact, it's the ONLY limitation that I have found... so you "simply" have to work around it and use multiple instances (or in the case of VST3 or RTAS, use multiple "ports") of VEPro, since the Spectrasonics plgs are forced to use midi 1-8.

    I don't think this is quite true. For RMX it is, but Omnisphere and Trillian allow the use of midi channels 9-16. I have a project up right now that uses 2 Spectrasonics AU plugs per instance. Just instantiate RMX first.

  • last edited
    last edited

    @esteso said:

    For RMX it is, but Omnisphere and Trillian allow the use of midi channels 9-16. I have a project up right now that uses 2 Spectrasonics AU plugs per instance. Just instantiate RMX first.

    You are so right and I am so mistaken! you can simply pull down the midi channel assignments in the mixer page. Silly me.