Vienna Symphonic Library Forum
Forum Statistics

182,210 users have contributed to 42,211 threads and 254,710 posts.

In the past 24 hours, we have 4 new thread(s), 30 new post(s) and 51 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Vienna Ensemble bugs

  • Vienna Ensemble bugs

    F
    F

    A couple of things I've found so far:

    Selecting several instruments in the left-hand list (by shift-clicking on each one), and clicking 'Remove' leads to a list of anonymous things in the left-hand list where there ought to be the remaining instruments and buses.  (I suspect a data structure got scribbled on by the remove code.)

    The on-screen keyboard in each instrument seems entirely unresponsive when VE is invoked as a VST, which makes configuring keyswitches a tad impossible.  (Works fine when invoked standalone.)

    (Set-up: Cubase SX3, XP x64, EMU 0404 sound card; ask about what else you need to know.)

    By the way, it might be worth creating a sticky thread for bug reports.

  • P
    P
    For reports to be meaningful, your video card, how much RAM, potentially the mother board if you know it. I don't work with Cubase, I use Logic on the Mac and have VI on PCs converted from GigaStudio. I moved to the Mac 2 years ago from SX3 and I'm not aware one way or the other if it's been optimized for XP64 and whether or not you have updated drivers from E-MU for XP64. Was your system specifically built for XP64? You really need to fill in these gaps so we know how to evaluate the applicability of your bug reports. When you don't give more specifics, it makes users unduly over cautious and fearful about downloading and using VE.
  • S
    S
    There is a bug with Waves on Ensemble....When inserting waves plug-ins they come up as "wave-shell", instead of actual plug-in name.....This is fine and all is well until you shut down the session....When you relaunch it, Ensemble doen't remember which Waves plug-ins it was using, since they came up as :"Wave-Shell"....try it....(i'm on a pc with RME Hammerfall)....Great work guys........IT is configuring a 64 bit system for me, so I will be able to have a go at the 8 gig RAM tommorrow. Other than that no probs so far.. SvK
  • F
    F
    last edited
    last edited

    @Peter Alexander said:

    When you don't give more specifics, it makes users unduly over cautious and fearful about downloading and using VE.

    Well, I hope I haven't given the impression that my PC is on fire as a result of installing VE, because it isn't.  So far, things are generally going okay; I'm migrating a current project from about 25 VI instances to four VE instances (woodwinds, brass, strings, other) and adding in a Kontakt 2 instance in the process (so I can get the use of some Horizon libraries again, hooray!).

    My system is a Dell Dimension E520 with a Q6600 CPU (2.4GHz Quad core), 4GB of DDR2 533MHz RAM, 500GB SATA drive with OS and apps, 250GB SATA drive with samples, NVidia NV285 card with dual 1280x1024 monitors, XP Pro x64 SP2, EMU 0404 with 2.0 preview drivers and PatchMix for x64, Cubase SX3 (final release, LAA 32-bit app), Kontakt 2.2.3 (not LAA, despite running LaaTiDo on all relevant DLLs and EXEs), Behringer BCF2000 and BCR2000 control surfaces, M-Audio 88-key keyboard (surfaces and keyboard all connected via USB, not MIDI); the system was indeed built for x64.

  • M
    M

    The bug that followed after fcw selected multiple vi instances in VE and tried to remove them was replicated by myself on VE running as a "vst" in cubase studio 4.1, on Vista ultimate, on a AMD 2GHz dual-core, 2g ram system. VE crashed, but luckily did not take cubase along with it, which i think is one reason why it is convenient to have VE running in a rewire-like mode... I should add that in my case, i had 9 VI instances loaded in VE and tried to remove three selected VI instances.