Vienna Symphonic Library Forum
Forum Statistics

182,828 users have contributed to 42,261 threads and 254,932 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VelX unusual response in DS

  • VelX unusual response in DS

    J
    J
    Hi, VelX is responding whenever it feels like in DS. I have all VelX assigned to the same knob in my controller. Sometimes it works on a note, then later it won't on the same note. I'm not sure if it's related to DS, but this had not happened to me before with SE. On another note, sometimes when left unattended the filter in all the instruments in Vienna Ensemble will close all the way to 1. Any reason why? VI player and Vienna Ensemble. Mac Pro 3,1 10.6.8 8 GB Ram Thanks, Juan
  • Cyril BlancC
    Cyril BlancC

    VelX ? DS ?

    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
  • P
    P

    Velocity Crossfade. Dimension Strings. 

    "... sometimes when left unattended the filter in all the instruments in Vienna Ensemble will close all the way to 1. Any reason why?"

    Just a possibility. Sometimes an errant keyboard controller can spit out MIDI values even when you don't touch it. When the hardware contacts get dirty, for example, even a vibration in the room can trigger a message, in this case, sending a CC (# assigned to filter) / 1 command. That closes the filter.

    If you have Logic, cable a monitor to the MIDI path in Environment, and you can check to see if a MIDI message was sent. Also, you might change the MIDI receiving number on the filter to see if it continues. If I am right -- if it is a specific errant CC message (which in this case happens to be assigned to Filter) -- the problem will stop. (That's not a fix, I know. But you may be able to pinpoint the problem.)

    As for the VelX, well, that too feels like a controller. You say "knob" so you are continuously controlling the crossfade.You could reassign the DS patch to Xfade by Note Velocity and see if that works. If so, it's virtually guaranteed to be a MIDI message problem. 
  • J
    J
    Thank you, that could be it. Another question, is it programmed to be that way, or is it a glitch that the VelX checkbox automatically disables itself once the fader is halfway below the middle then turns itself back one when halfway above?
  • D
    D

    Aha. You have set it to a controller without meaning to. Check what controller you have set it to and then disable it or set it to a different controller number.

    DG
  • P
    P

    In MIDI there are two kinds of controllers. One is continuous, like CC1, usually the mod wheel. It goes from 1 to 127. 

    The other kind is called... um, I don't know. But it works like an on - off switch, like CC # 64, usually the sustain. And those controllers usually send a data byte that is 1 or 128 (or 0 or 127. I can never keep that straight.) There is no in-between. So it's a binary, yes - no, on - off thing. 

    If you use a continuous controller to work the sustain pedal, all numbers 63 and below will be interpreted as off, and anything higher will be on. If you use a pedal switch to work the sustain pedal, it'll just send 0 or 127. 

    As DG suggests, you probably have VelX (which is meant to be continuous) assigned to a knob that is just sending 0 or 127. That's why it resets to 0.

    Did you ever track down the offending vehicle?

    Yesterday I had to disassemble my MIDI keyboard and clean the contacts on my mod wheel. It was sending erratic messages whenever I moved it, causing the faders on VSL to jump every which way. 

    In any event, this is not a VSL setting or bug. 

    Cheers.