Vienna Symphonic Library Forum
Forum Statistics

196,468 users have contributed to 43,018 threads and 258,412 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Vienna Ensemble - preview infos
  • R
    R

     OK - it is official --This is a VERY nice update (upgrade)[<:o)].  Switching and Power panning looks very promising.  Looking forward to this.

    Rob 
  • J
    J
    It has been suggested that Logic is currently able to exceed 32 bit memory limits by treating each exs instance as a seperate app in terms of memory allocation. Therefore each EXS plug-in could load up to the 32 bit memory limits. I suspect when Herb mentions Vienna Ensemble being 32 bit (in the Mac domain) for the near future will mean the 3GB limits will contiue even after Logics Leopard version surfaces. I hope VSL can get round the additioal programming to create a 64 bit version as soon as....! Julian
  • P
    P

    Beautiful!
  • G
    G

    And what about an FX-Teleport-like technology integration into this wonderful tool?!

    Or it's already there?! [:P]

    Many thanks.

    Luigi Pulcini.
  • T
    T
    Absolutely breathtaking!
  • C
    C

    beta. beta, beta... when? :)
  • D
    D

    Sod that, I just want news. How can VSL announce something and then go quiet. It's disgraceful. Shouldn't be allowed.[8o|]

    DG
  • T
    T
    The instrument switching is such a huge time saver and workflow enhancer. Just great. This is a major upgrade to the way we will work with VSL. Can't wait. TH
  • G
    G
    Really really cool! ...and just in my price range! Thanks herb!
  • C
    C

    So Herb - is today the day? :)
  • S
    S
    Hi I was wondering, if you have your DAW on one machine and then put VE on another and connect by ethernet, do you still need midioverLan to connect to the VE? Also do I still need a audio card out of the VE machine and then and audio in on the DAW? Or will it be able to send the audio back and forth like the Muse receptor? Thanks, Simon
  • D
    D
    last edited
    last edited

    Good questions.

    I guess that you will still need MOL and an audio card on the slave, unless you use FXT. If it did audio and MIDI over LAN, cross-platform I would have thought that VSL would have been trumpeting that fact by now. However, I have been known to be wrong.

    BTW Does Receptor actually send audio? It never used to.

    DG
  • S
    S
    Yeah, it uses a protocol called uniwire. I was hoping VE had maybe written something like that. Any vienna people like to shed some light on the subject?
  • D
    D

    Isn't uniwire MIDI and GUI info only?

    DG
  • P
    P

    So if you're using this stand alone, you'll still need a MIDI yoke right?  Are there any 64-bit MIDI yokes out there right now?  Does MIDI over LAN work in 64-bit?
  • J
    J
    Well, the old VSL Performance Tool already used virtual MIDI ports, so I'd imagine it will be simple for VSL to pipe MIDI into the VE from other Windows apps (OS X has virtual MIDI built-in). But even with a 3rd party virtual MIDI app, it wouldn't have to be 32-bit. It's only the memory-intensive VE itself that needs to be 64-bit - even your sequencer could be 32-bit, since 32 and 64-bit process coexist happily on XP x64. At least that's how I understand it working...
  • D
    D
    last edited
    last edited

    Actually nothing has to be 64bit (apart from drivers), providing that you can run multiple copies. Of course this doesn't work with all audio cards.

    DG
  • C
    C

    hehe... something tells me a few issues have popped up :)
  • D
    D

    Yeah. Less than three weeks to go and still nothing to test. [:(]

    DG
  • J
    J
    last edited
    last edited

    @DG said:

    Actually nothing has to be 64bit (apart from drivers), providing that you can run multiple copies. Of course this doesn't work with all audio cards.

     

    DG

    I have a feeling this won't work, DG, as it sounds as though the VE uses a client-server model, like the VI on OS X. So multiple standalones of the VE would not launch multiple servers... I'm not sure about this, of course, but from what I understand, they've made the new VI (2.0) VST/AU use host-based memory (as it already did on Windows), and the VE use "vsl-server"-based memory. The idea being that you can access double the RAM on 32-bit systems (well, OS X anyway, since xp standard can only ever access 3GB) by maxing out the hosts memory with VI instances, and maxing out the VE server as well. On 32-bit OS X, that would give you 3.x GB in the host and 3.x GB in the vsl-server (or whatever they call it). And what's cool about the new model (again, if I'm understanding it correctly), is that you could load VE instances **as VSTs** and still be loading up memory external to your host. This way, with a mix of VI and VE instances (all VSTs), you'd get your 7-ish GB of RAM loaded, and still be running all the audio from within your host app! But what I really don't understand is where the VE Standalone loads its memory. Is it another separate process, like the old VI Standalone, or does it also load to the vsl-server??? Of course, the real point is to just go 64-bit asap, and solve the problem in one go.... But we OS X folks are going to have to wait on that. Thanks, Apple... --- J.