Vienna Symphonic Library Forum
Forum Statistics

183,305 users have contributed to 42,291 threads and 255,041 posts.

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

  • Perhaps I'm not using the right terminology. On my slave I have both a VE3 "standalone" instance with the most used samples. It outputs through an RME ADAT card. Then, sometimes, I'm also running the VE3 service, for loading additional instruments. It outputs through gigabit ethernet. The two are totally independent.

    Dom 


  • I noticed that Vienna Instruments uses less CPU on my rig (Logic 8 + G5 + Tiger) than Vienna Ensemble. As for the power panning whatever used for it sounds artificial. "Placing" an instrument group in a hall requires interaction between the [b]off axis[/b] recorded direct signal (not the case with Vienna) and the reverb from [b]off center[/b] source. For the latter you need at least IRs for several locations on the stage in the same room working simultaneously.

  • I forgot to mention, I'm on a single Mac Pro quad-core, so having a network of machines with VE is a moot point for me.  Also, I don't use panning at all, I do stage placement via Altiverb.

    I think I may have just talked myself out of using VE. ;) I don't have any problems with the VI interface other than that silly "Show Window" button that comes up when I double click the Vienna Instruments AU on any given track.  I'd seriously pay money to get rid of that thing.  Why is it that no other AUs do that?  Is it some kind of wrapper, maybe?  Is Vienna on Mac just really a VST with some kind of AU wrapper around it, hence the extra step?


  • last edited
    last edited

    @MDesigner said:

    I forgot to mention, I'm on a single Mac Pro quad-core, so having a network of machines with VE is a moot point for me.  Also, I don't use panning at all, I do stage placement via Altiverb.

    I think I may have just talked myself out of using VE. 😉 I don't have any problems with the VI interface other than that silly "Show Window" button that comes up when I double click the Vienna Instruments AU on any given track.  I'd seriously pay money to get rid of that thing.  Why is it that no other AUs do that?  Is it some kind of wrapper, maybe?  Is Vienna on Mac just really a VST with some kind of AU wrapper around it, hence the extra step?

    I think that the window is caused because VI (and VE) uses its own memory space. When VI becomes 64bit, you'll thank VSL for this, because it will allow you to use all your RAM, even if your sequencer is still 32bit.

    DG


  • Ahh, I see.  Makes sense.

    I guess I might appreciate it down the road.  But at the moment, it feels like a small bump in my workflow.. mildly disturbing but not horrible. :)


  • last edited
    last edited

    @MDesigner said:

    Ahh, I see.  Makes sense.

    I guess I might appreciate it down the road.  But at the moment, it feels like a small bump in my workflow.. mildly disturbing but not horrible. 😊

    If you want to appreciate it now, then in real terms it means that you can use 3GB or so in your sequencer, 2.5Gb in VI and another 2.5 in VE. Without all this "behind the scenes" you would only be able to use the 3GB, without using standalones.

    DG

  • I use a Vienna Ensemble via IAC.
    Big advantage is that Logic does not produce an audio midi error sync when you edit the VE while Logic is playing

    Best

    Cyril

    MacBook Pro M3 MAX 128 GB 8TB - 2 x 48" screen --- Logic Pro --- Mir Pro 3D --- Most of the VI libs, a few Synch... libs --- Quite a few Kontakt libs --- CS80 fanatic
  •  Hi Guys

     I'm glad I found two people that are using VI and/or VE with Logic. I am running Logic Pro 8 on an Intel Mac and I have VSL special edition and also VE 2.0. I cannot for the life of me get Logic to put output through the VSL or VE. When I play my keyboard in Logic it picks up the VSL or VE patch, and the MIDI In meter reads correctly, but can't get the exising midi tracks to ouput through the VSL or VE. Any suggestions greatly appreciated. I have a TASCAM US-122 External Audio. Thanks.

    Carmen


  • Did you use the demo song in VSL download area as a template ? If you want to send your logic song to cb(dot)pub(at)numericable(dot)com I have a look at it Best Cyril

    MacBook Pro M3 MAX 128 GB 8TB - 2 x 48" screen --- Logic Pro --- Mir Pro 3D --- Most of the VI libs, a few Synch... libs --- Quite a few Kontakt libs --- CS80 fanatic
  • last edited
    last edited

    @cgassi said:

    can't get the exising midi tracks to ouput through the VSL or VE
    Hi Carmen - did you try copying the existing MIDI data onto the VE/VI track? If you already did that and heard nothing, you could try changing the MIDI channel of the VI('s) inside VE.


  •  Thanks for suggestions. I was finally able to get the existing MIDI tracks to address the VSL standalone. I'm sure there are advnatages to using Vienna Ensemble. Is it logical that with more instruments available in the mixer, the MIDI tracks in Logic should be able to point to the channels assigned to the instruments in Vienna Ensemble and use less CPU and memory?

    Carmen


  •  Thanks again, I posted my results and a couple of more questions.

    Carmen


  • My experience with VSL is very new

    I use VE in standalone and I use IAC to send midi from Logic to the VE
    This solution avoids to have core audio overload messages when you look or edit the VE while Logic is playing
    I have made a VE for my Appassionata where I load ALL the articulations of the Appassionata
    From Logic I switch articulation via program changes

    I do the same for my Brass, Winds and Percussions but with QSLO Platinum and Kontakt 2
    Using K2 it was recommended to have Multi (= VE) instead of instruments (= VI) you get better performance and if you load twice the same instrument the samples are loaded only once (VSL can answer better on this one)

    Best

    Cyril

    MacBook Pro M3 MAX 128 GB 8TB - 2 x 48" screen --- Logic Pro --- Mir Pro 3D --- Most of the VI libs, a few Synch... libs --- Quite a few Kontakt libs --- CS80 fanatic