Vienna Symphonic Library Forum
Forum Statistics

181,975 users have contributed to 42,197 threads and 254,642 posts.

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

  • Thoughts about Multitimbral Instruments in VEpro 64

    i think it would be nice to have the option to switch off multitimbral functionality in VEpro in the preferences or on a per channel basis. this would mean that the incoming midi would always passed through on midi channel 1 to the instrument, ignoring the channel of the incoming midi. at least in the 64bit version of VEpro, using multitimbral instruments doesnĀ“t make much sense, as the memory-hit of the user-interfaces can be ignored. so the way one would prefer to work in order to unclutter things and donĀ“t have to deal with additional inputs in VEpro is to open a new instance of an instrument for every sound needed. right now there are three 64bit instruments for the mac. stylus, omnisphere (beta) and trillian (beta). by loading a new instance of one of these you also have an additional step to assign the right channel in omnisphere. in stylus you donĀ“t even have this option. here you have to take the respective part to load the loop you want. (there are only 8 parts, meaning if you already used 8 omnispheres in VE pro using channel 1-8 you donĀ“t even have the chance to assign midi to a later added stylus. everything would be much easier and more intuitive for new users if weĀ“d be able to switch off multimbrality as mentioned. another option would be another midichannel button. so the existing one would reflect incoming midichannel, the new one would reflect the throughput channel to the instrument (default=1). or you do it as in logic. on loading an instrument you choose between a stereo and a multitimbral instrument. iĀ“d prefer a "M"-button next to the midichannelbutton. Highlighted means multitimbral on and midi is passed through on the same channel. and defaulted itĀ“s off and midi is passed through on channel 1. thanks ;-)

  • I thimk you can do that now, just change the channel in VE Pro from "all" to 1.

  • iĀ“m ot sure what you mean? thereĀ“s no "all"- setting. in case you mean "omni" thatĀ“s something different. as it is, the incoming midichannel is throughpassed to the instrument so you have to additionally adjust the instrument in order to recieve midi on that channel which isnĀ“t straight forward and depending on the instrument may force to learn the instruments indepth settings for no reason. tell me if iĀ“m wrong...

  • You're correct, it is Omni although it says 'all' in the display. If you change from "all" (or omni) to, say, 1, all midi coming in on that plugin midi in will be routed to channel 1 of the instrument you have loaded. I really don't think however that learning a multimbral intrumrent's routing is much of achallenge.

  • sorry, but i think you didnĀ“t get the point. please read my initial post post carefully. setting midichannel to "1" means only incoming midi from channel "1" would be accepted and would be throughput to channel "1" of the instrument. now you setup another track in logic to send midi to another VEpro instrument. you will do that on channel 2. now you set up this next instrument on VEpre to midichannel 2 and it will recieve midi from channel 2 but only throughpass midi to the new instrument on channel 2. so you have to setup the new instrument to recieve on channel 2 only. itĀ“s not too hard to set up (for me) but it may lead to confusions for other people. too many steps that donĀ“t make sense. in stylus for example youĀ“re forced to load a loop in the slot that is corresponding to the midichannel youĀ“re sending from logic. no problem for me, but it could be much easier...


  • I think I understand you now although I think what you're asking is fairly redundant. Another workaround, is to use a separate instance of VE Pro for each instrument. Also, if you can use a VST3 instance, you can have up to 32 midi ports, all of which could be set to "omni".

  • it is fairly redundant yes, itĀ“s just a "thought" (read the title) which could make things somewhat easier and help setting up VEpro more to the way many people will use it (at least in the 64 bit version). using an instance of VEpro for each instrument wouldnĀ“t at all make things more comfortable and if you read my signature, youĀ“ll see that iĀ“m using logic, so vst3 is also no option. now please let this thread be what it is, a suggestion. if you donĀ“t need this, donĀ“t care. but thanks anyway for bumping this up all the time.