Vienna Symphonic Library Forum
Forum Statistics

196,686 users have contributed to 43,023 threads and 258,420 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Having a problem with a EW Brass patch on a slave in VEPro

  • Having a problem with a EW Brass patch on a slave in VEPro

    J
    J

    Hi all. Didn't have much luck with EW; said they would loiok into this.... I was hoping someone could chime in here, and possibly check something for me.

    I use Cubase (W7), and as part of my large template, I have sevaral EW Hollywood Brass Diamond instruments loaded in VE Pro in a PC slave. 6FH Leg Slur (x2), 2FH Leg Slur (x2), both marc patches and the stac patch. Main and vint mics loaded on all.

    When I open the project and go to play the 6FH Leg Slur, only the very beginning of the note (or maybe it's the leg transition?) is available. Once that note is hit one time, then I can play the full note with no problem. Here is an audio ex:

    http://www.jeffreyhayat.com/JHayat_HBDtest.mp3

    That's me hitting the key 2x. The first, as you can tell, the note does not play properly (I am holding the key, not releasing it quickly), and then when you hear the note play correctly, that's me hitting the key a second time.

    Now, I see this with Kontakt as well. Kontakt has bgd loading, and not all of the notes in an instrument are immediately available. But, even tho it may take a few moments, they eventually do become available. Not so with the 6FH Leg Slur patch - the notes never become fully available unless they are keyed. And from that point on, I have no  problems whatsoever.

    Here is some more info:

    This only happens when that slave has a lot of other instruments loaded in several other VE Pro instances, thereby requiring more RAM usage. So, if this were tested by simply loading 6FH Leg Slur in VE Pro on a slave where the RAM udage were relly low, this problem won't show. I don't know what the tolerence is, but my RAM usage with everything loaded is 7 GB (I have a total of 8 on that machine).

    This does not happen with 2FH Leg Slur (which alomost doesn't make sense), nor does it happen with the stac and marc patches.

    This only happens when two mic positions are loaded.

    One other user said he expereinces the same thing with Hollywood Strings

    Has anyone seen anything like this, and/or does anyone have any ideas as to what might be goin on?

    Thanks in advance.

  • J
    J

    bump  :) :)
  • PaulP
    VSL Team
    PaulP

    Hi Jeff, 

    May I ask: What does the East West support team say to this? 

    They have many VE PRO licenses to check, and I feel that they are the right people to talk about such specific behavior. 

    Best, 

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • C
    C
    last edited
    last edited

    Hi Jeff

    @Jeff Hayat said:

    f this were tested by simply loading 6FH Leg Slur in VE Pro on a slave where the RAM usage were really low, this problem won't show.

    So there's nothing wrong with the horns patch per se. Excuse this simplistic guess, but since your template works OK on your master (2GB spare RAM) but not OK on your slave (1GB spare RAM), doesn't that indicate that you need a little more RAM in your slave? EW orchestral patches use a hell of a lot of samples and can be a strain on system resources, especially when using dynamic cross-fading and multiple mic positions.
  • J
    J

    Hi, thanks for the replies.

    "May I ask: What does the East West support team say to this? "


    Oh, how annoying! We will look into this.

    "So there's nothing wrong with the horns patch per se."

    No - I don't think it's the patch itself; I think it's the way PLAY handles ceryain patches inside VEP.

    "doesn't that indicate that you need a little more RAM in your slave?"

    Tried more RAM - I temporarily added another 4 GB to that slave, to see if that was the issue. So I had approx 5GB (or close to it) free.
  • C
    C

    Just wondered - does your slave PC have the same kind of processor speed as your main machine?
  • J
    J

    Yes - same MB: Asus P6T, and same CPU: Intel Core i7 960  3.20Ghz
  • C
    C

    Thanks Jeff. Unfortunately I can't replicate your set-up for test purposes, but from what you've said I think you've effectively isolated the problem to EW Play, which I suppose finds the onus of processing incoming MIDI data from an external source (as on your slave) slightly more taxing than operating inside your sequencer.  There must be a more scientific explanation, please excuse my non-technical waffle!

    For others to chime in, could you maybe give a breakdown of the various sample players you're running inside the multiple instances of VE Pro on your slave?

    >Once that note is hit one time, then I can play the full note with no problem.

    I occasionally experience this using Vienna Instruments (both in VE and standalone) and the only consolation is that it always works on the second attempt!
  • J
    J

    For others to chime in, could you maybe give a breakdown of the various sample players you're running inside the multiple instances of VE Pro on your slave?

    Only PLAY and Kontakt, but not in the same instance.

    I occasionally experience this using Vienna Instruments (both in VE and standalone) and the only consolation is that it always works on the second attempt!

    Really.... hmmmmmm
  • C
    C

    In my experience, PLAY is always the most prone to wobble because of the huge sample count of some the EW Hollywood series library patches. Good luck with finding a fix - in the meantime, If I were in your position I'd use fewer mic positions or 'lite' patches for work in progress.
  • M
    M

    Old thread, but if anyone is still wondering, this same issue happened to me just recently.  

    In my case, I was using EastWest PLAY in VE Pro slave with Cubase.  But I was using Cubase expression maps, which didnt play nicely with the legato patches of Play and was constantly triggering legato transitions before the sample.

    Removing Expression maps for all legato patches and reloading solved the issue.