Vienna Symphonic Library Forum
Forum Statistics

194,181 users have contributed to 42,912 threads and 257,928 posts.

In the past 24 hours, we have 1 new thread(s), 13 new post(s) and 88 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Multitimbral Audio Units in VEpro - strange behaviours - midi lost...

  • Multitimbral Audio Units in VEpro - strange behaviours - midi lost...

    C
    C
    so my initial problems with stylus and omnisphere turns to be a general problem with multimbral audio units and persists with the new update. i´m using Logic 9.01 (same with L8 though), OS 10.6.1, MacIntel Octo. I can´t get multiple multitimbral AU´s to run properly in one 32bit instance of VEpro. I setup a multiinstrument in logic and a32 bit VEpro and insert one omnisphere midichannel 1. runs fine. I add a second omnisphere midi channel 2. it doesn´t work initially however, it might work if i change the channel to 2 on the second omnispheres mixer page. then i add a third instance of omnisphere with channel 3. it works instantly without having to change anything in omnisphere 3. i add more omnispheres and they work or don´t work with or without the mixertweak in omnisphere. no pattern, just a matter of luck. when ever i save and reload the project, only omisphere 1+3 are instantly playing back. the midi notes i play on the other channels stay in the pipe for like 1-2 minutes and then eventually play back. i have similar but more rare issues with addictive drums and stylus, no specific pattern here. addictive drums runs or not. (mostly it does run) there must be some issue with the internal midirouting. i see the incoming midi on the respective channel in VEpro exactly when i play it. i also hear what stylus or addictive drum are playing if they play on their internal playfunction. however there is a huge mididelay of several minutes when they´re triggered from the sequencer. for the time beeing i will use one 32bit instance dedicated to one omnisphere used in real multimode set up with inputs etc, and start another for other tasks, but this isn´t the way, i´d like to work forever and is quite iconvenient. also i think core distribution is better when using one instance of omnisphere per sound, please tell me if i´m wrong on this. the workflow definitly is better and i´d like to have only one 64bit server instance for my vienna instruments and one 32bit server hosting any kind of AU´s as needed to lighten ram footprint of logic. so if somebody want´s to reproduce, just try to setup a 32bit VEpro in logic with 5 omnispheres playing one sound each. if you can do, save it and do a complete system retart (or at least quit the host and everything VSL related including the VSL-Daemon) then reload everything. If you can make it work even after reload, then I have a problem (or my system...)
  • F
    F

    cueblast,

    I tried to reproduce this setup and I ended up with the same issues. In my case, Omni 1, 2 & 3 played back instantly. Omni 4 & 5 - as mentioned - with a huge "mididelay", let's say 1minute after stopping the sequencer...

    It's such a great piece of software but there are still A LOT of issues which make it quiet unreliable.

    Mac Pro 2 x 2,93 GHz - 16GB RAM

    OS 10.6.1

    Logic 9.0.1
  • C
    C
    cool, thanks for testing this. should be enough reason for the viennas to dive into the issue. might aswell be a problem of spectrasonics or AU-specs, but i´m VSL will find a way to deal with it :-) BTW since the VEpro update, i´m not able to write into Omnispheres searchfield. haven´t tried it with other textfields, parameters or other synths, but i´m sure it was possible before the update....
  • K
    K
    We'll look into this. Thanks for reporting.
  • N
    N

    Look forward to a fix Karel.

    Cheers.

    Nick
  • N
    N

    Thanks a lot VSL. Version 4604 seems to have fixed this problem. [:D]

    Nick
  • N
    N

    Sorry. I was a tad too hasty there. Just tried it with a bigger template and the problem persists.
  • F
    F

    ...even with smaller templates...
  • A
    A
    The problem is probably a Logic issue. By default in the Clicks & Ports layer of the Environment, Logic cables the Sum from the Physical Input (through some monitors) to the Sequencer Input. You need to delete that cable and draw a cable from the MIDI ports your controller(s) use to the Sequencer Input. SHAMELESS SELF+-PROMOTION ALERT: I will have a tutorial on this, pictures and text, in my upcoming book, "Going Pro With Logic Pro 9." In the meantime, upon request I will send people a template with it created if they email me: jay@jayasher.com.
  • N
    N

    Thanks Jay. I tried your suggestion but unfortunately the problem still occurs.

    Nick
  • C
    C
    hi. after 3 month+ and several updates of VEpro, logic, spectrasonics etc. i´m just trying again and get the same issues. still sometimes on certain mulititimbral instruments i see the incoming midi in VEpro, i hear the internal prelisten audio (stylus in this case) but VEpro doesn´t throughput the midi to the instrument. i think the huge midi delay has gone though... edit: sorry, my fault (and a bit of a designflaw from stylus) - solved ! (the parts in stylus mixer don´t have a channelswitch (like omnisphere) so if you want a stylus play on channel4 you must choose the groove in part 4 obviously...)