Vienna Symphonic Library Forum
Forum Statistics

200,496 users have contributed to 43,199 threads and 259,094 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Seems as if Vienna Instr. is the ONLY VI working nicely in Vienna Ensemble Pro

  • Seems as if Vienna Instr. is the ONLY VI working nicely in Vienna Ensemble Pro

    M
    M

    It is more or less like the header says. Unfortunately.

    I've got problems with 

    BPM, MachFive2, Kontakt 4, Korg M3 Plug-In, Omnisphere, StylusRMX, Yellowtools, SampleTank2XL.

    After opening and loading files via the OS X file system a couple of times once a Plug prompts for it,

    I cannot use the OS X Browser dialogs anymore. I cannot click on any directories or navigate to the locations I wish to navigate to.

    BPM will crash VE Pro 10 times per day (I know, I should not use it)

    MachFive2 is behaving better but crashes VEPro a lot too.

    Korg M3 Plug-In will crash VEPro every time a new session is opened with an M3 Instance

    K4 can only have its interface resized once. Then I am stuck with that size until I reboot VEPRO

    The spectrasonics Plugs will not start playback the same time when hitting play in the DAW. I have checked it via measuring the sample

    delay. Sometimes 200 SAmples other times 2000 and many a time in between. I might add that 2000 samples is an eternity when talking timing.

    SampleTank2XL WILL crash VEPro as soon as you load large patches.

    Now, the M3 Plugs IS very buggy so I might think that the cause belongs Korgs. However, the other plugs are NOT showing those behaviors

    as Audio Units in

    Logic Pro, Plogue Bidule & Protools HD | LE

    The Vienna Instrument seems to be the only one which does NOT crash VEPro.

    The advertisement states that VEPro supports 99.9% of all VIs..... 

    Well, those mentioned above are among the most important and them inserted into VEPRO are NOT something I would rely on when having a client in the studio. I think those problems are VEPro related. Otherwise, Logic Pro should display the same behavior with those exact Audio Units.

    K4 - One time in the middle of a session running on the VEPro server, I decided to add some outputs to K4. I do that all the time in Logic and PT. After saving the defaults I have to reboot the session. So I saved it and as I tried to open it again VEPRo would just crash every the time.  I had spent 3 hours on that playback and had a talent sitting there waiting to lay down his words. Only an XML editor and some knowledge about XML Tags helped interchange those DATA which had been wrongly written in the metaFrame file. I created a new metaframe with Kontakt and copied that XML Data into the session that would not open. After that I had it up again.... Might add that BPM caused that EXACT problem one day before. So I have an XML editor alias sitting next to the mframe file folder. BPM and Co. might have a few quirks here and there but since I started to make music i n1996 I have NOT once experienced Logic nor Protools NOT being able to open a seesion that I worked on. I had VEPRO for 1 day and then those problems came....  

    I love the idea and smoothness of VEPro especially when using the Vienne PRo Instrument (Incredible) kudos to the programmers.

    However, and this is a humongous however, I think you need to take a VERY close look at VEPro before you go about advertising it as 99.9% AU VI Compatible on OS X. I have bought it now and will be using the Strings but had I known that it would be incompatible with the MAJOR VIs then I would have probably waited before purchasing.

    Dont get me wrong - VEPRO is one of THE most innovative apps I have ever seen on a Mac alongside BPM and a few other great ones but we need to get it more stable than a cold-war nuclear powerplant [:O]
  • P
    P

    I'm going to come at this from a different angle but I support the thrust of MC's post.

    My angle is this: A lot of us who have started using VEP are not that interested in VIP or for that matter Orchestral composing in general. We may have to do the odd string arrangment but that's not the reason we bought into VEP.

    We bought it because it's a AU plug host.

    That may not be the primary use that the programers had in mind but you are now seeing more and more of us turning up on your forum and asking about compatibility with our favourite plugs.

    But do you want us customers? That's the question at hand.

    Is VEP primarily just for Orchestral composers or are you going to to put your resources into keeping this app working with the major VI's?

    I have been heavily advertising VEP amongst friends and clients as the greatest plug host (and I think MC also was influenced by my praise of the product)

    If VEP is not going to work with VI's that work well in other apps then I feel I can't recommend it without serious reservations.

    I will also confirm that Spectrasonics plug "Stylus" has eratic behavior with the latest VEP build.

    Upon opening a session the plug will not audition loops in time. If I quit VEP and restart it then it will be ok.

    It could be a PT thing or it could be that I am running a PPC as my master. (which I know is not supported)
  • K
    K

    M.C., could you submit crash reports to ? Also, could you tell me some exact steps to reproduce the problems you're experiencing? Thanks.
  • K
    K

    Note that Pro Tools LE does not have any form of plugin latency compensation, so unless you're using 0 buffers of latency in the VE Pro Server Interface RTAS, you'll get uncompensated delay on its output.