Vienna Symphonic Library Forum
Forum Statistics

201,372 users have contributed to 43,244 threads and 259,256 posts.

In the past 24 hours, we have 5 new thread(s), 15 new post(s) and 57 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE PRO Compatibility List - YOUR input is much appreciated!
  • civilization 3C
    civilization 3C

    BFD2 has been godawful here. By itself, with absolutely nothing else in the network, I can get it to work if I set BFD2 to load with that preset as if a default. But loading new kit pieces, WILL crash VEP; or, with 'load nothing' as a preference, loading a preset or kit will fail to load most of it, and 'loading new kit pieces WILL crash...'. Generally I'm working around it, Cubase on the slave machine, BFD or BFD2 as a regular plugin.
  • O
    O
    On a Mac, BFD2 seems to work fine except for two issues:

    1) No tempo sync when in a VE Server. It doesn't read tempo from the host. (Tried DP 7)

    2) The mono audio outputs from BFD2 don't work. VE Pro sees the "correct" number of outputs from BFD (8 stereo and 16 mono = 16 stereo) but only the 8 stereo work. The 16 mono (as VE sees them as 8 additional stereo outs) have no audio coming from them.
  • civilization 3C
    civilization 3C

    'On a Mac', well I'm using a macpro octocore under OSX.6.2 with these issues. I think I will compile some crash reports per this 'loading causes crash in every case' and submit. With 'load preferred preset at startup' it's ok, but typically I pick a kit according to the demands of the piece's other orchestration, so this is a real problem for me.
  • B
    B
    I just tried VE Pro with EastWest's PLAY and it seems to work, I am very surprised (in a good way obviously) since the compatibility list says it doesn't. PLAY version 1.2.05, VE Pro version 4.0 build 4881, Cubase x64 5.1.1, Windows 7 x64 on Core i7 12GB. Apparently great news (?)... but why does http://vsl.co.at/en/211/497/1685/1693/1742/1369.htm explicitly say it doesn't work?
  • D
    D
    last edited
    last edited

    @BenjaminCS said:

    I just tried VE Pro with EastWest's PLAY and it seems to work, I am very surprised (in a good way obviously) since the compatibility list says it doesn't. PLAY version 1.2.05, VE Pro version 4.0 build 4881, Cubase x64 5.1.1, Windows 7 x64 on Core i7 12GB. Apparently great news (?)... but why does http://vsl.co.at/en/211/497/1685/1693/1742/1369.htm explicitly say it doesn't work?
     

    Because it works with some versions of the software (on Windows) and not others. there is guarantee that ti will work with future versions. this is why I J-Bridge PLAY, so that I don't have to worry about future updates of VE Pro not working with PLAY.

    DG
  • L
    L
    Has anyone had good results with Korg Legacy Analog? I find that the Korg instruments usually Hang-up the VEPro engine after hitting a few notes (audio stops). The Korg Legacy collection is listed as supported plugins, but I can't seem to make it work on VEPro (build 4881) on either a Mac or Windows. Thanks, Kevin L
  • K
    K

    I've played a bit with Korg Analog on both Mac and Windows, and I couldn't reproduce this behavior. Could you perhaps give some exact steps on how to get it to behave like this? 
  • L
    L
    Hi Karel, Thanks for replying to my note. I'd really like this to work well, so I'm glad you are paying attention.

    There isn't really much I need to do to have this happen. Happens consistently and relatively quickly for me in both PC (Windows 7) and MacOS (10.6.3, running on 3.2g 8-core).

    This is what happens on my Mac (VEP v. 4.0, build 4881), no sound card, using audio line-outs, USB Midi interface (digidesign midi io), CME Vx7 Keyboard:

  • 1.) launch Vienna ensemble pro
  • 2.) instantiate MonoPoly on some channel (will get the same behavior with any plugin in the collection)
  • 3.) select patch A045 ("Soft Synth Horn").
  • 4.) Play something (I was just stabbing chords. using sustain pedal too).
  • 5.) (varies, ~ 10-30 seconds) after some playing, Notes will hold in sustain. no new Midi info accepted (eg. sustain off, retriggering notes). Meters are still active, CPU is hovering around 20-25% (and updating while notes are hung). Turning off audio engine (power button in top left of VEP interface) is the only way to reset notes, and get MIDI to be accepted again. I can instantiate other plugs on other channels while the Korg plugin is hung. This happens more often when I use the sustain while playing.

    I can not reproduce the same behavior on the standalone Korg applications.

    Hope this helps, Is there anything you wish for me to try?

    Regards,
    Kevin L
  • K
    K

    Can you reproduce this in another host application like Logic?
  • L
    L
    Hi again, Karel,

    I have tried reproducing this problem in MainStage, and could not reproduce it. I will also try ProTools and Logic tonight.

    I haven't tried another host yet on the PC.

    Thanks,
    Kevin
  • L
    L
    Hi Karel,

    Sorry - I could not reproduce that behavior in ProTools, Logic, or MainStage (on the Mac), nor in the standalone Korg apps. These 'hangs' happen consistently in VEPro with Korg Apps.

    Regards,
    Kevin
  • K
    K

    Ok, I've managed to reproduce this now. Will see what can be done about this. Thanks.
  • L
    L
    Great! Thanks for your efforts.

    I don't know if this is the same problem - but I did see freezes with AAS Ultra Analog (not on your compatibility list) too. Same type of behavior. It would be really cool if the same bug fix will fix both problems!

    Regards,
    Kevin L
  • C
    C

    LASS/Kontakt3.5/Cubase 5.1.1.(VSL aleady know about this)

    Repro:

    1.create metaframe project with kontakt and LASS

    2.Make a new Cubase project (48KHZ or 96)and connect to VSL Ensemble,(decoupled)

    3. Save cubase project,

    4.Close Cubase

    5.restart Cubase project

    LASS has corrupted Legato script with hanging notes. Happens on all ensemble Pro releases.
  • M
    M

    I can verify that this happens exactly as described on my system as well
  • C
    C

    Thanks for confirming, this really needs sorting out.
  • O
    O
    Just chiming in.. I have also had those issues with LASS.
  • A
    A
    Windows xp 64 / cubase 4 Hi there. Interestingly, the older version of Ensemble Pro does open and work greatly with Play... It works as follows: when I open Play vst on Ensemble PRO it says 'vst not found'. but actually it creates an empty channel named play_1. THEN, I open another channel with play (that PRO names 'play_2') and tadaan, it opens it and I am able to load whatever I want! If I remove the play_1, the entire software crashes. So I keep it as it is, like a good-luck charm! I have tried the newest version, it does not work. I mean, it opens play but..just as a picture, I can't press any button nor load any instrument. And after a while, it crashes. Hope it helps.
  • K
    K

    EW will release an update for Play in the (hopefully) near future that addresses the compatibility problem with VE Pro. The fact that it happens to work for some versions is a mere coincidence.
  • F
    F

    Play2 works to some extent in Vista64 although when we load it into VSL Pro Server (64bit) it says its missing a component and loads a grey screen. However on loading a previsouly saved VSL metaframe it loads up fine. I know this is work in progress between VSL and EW and its very encouraging.

    Kontakt 4 and GPlayer both work fine.