Vienna Symphonic Library Forum
Forum Statistics

196,182 users have contributed to 43,014 threads and 258,396 posts.

In the past 24 hours, we have 0 new thread(s), 8 new post(s) and 168 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Questions about VI player - velocity x-fade ...
  • A
    A
    Thanks Herb,

    I think I forgot to mention something.

    Currently I use the Perf Legato Speed + Porta matrix you created.
    So with this I already have 4 cells 1A for perf leg 1B for portamento and 2A and 2B for the fast legato_me ...

    now I thought that I want to put the other articulations like rep staccato etc. on a new matrix (perf leg is keyswitch C0 and staccato e.g. would be C#0) ... so would the only option to be automatc the velocity x-fade button then?
  • H
    H
    you could add another cells to your legato matrix (3A, 3B, 4A, 4b) for example,
    syncronize the switchpoint of the cell Xfade on/off controller with the cell switch controller, that the on/off switch is at the same value switching from cell 2 to 3.

    best
    Herb
  • A
    A
    Thanks a lot for your reply!
    I think it might be easier to just add a controller to the x-fade button and turn it on and off.

    Just a little suggestion, but wouldn't it be much cooler to assign a different xfade on/off setting for each matrix?

    With this, you could just load in perf legato, then staccato on the next matrix and as soon as you switch the matrices, you have different xfade settings ... or asked differently, wouldn't it be possible to activate a keyswitch and turn on/off the x-fade button?
  • H
    H
    We had to decide, a global on/off function which is controller assignable, or settings inside the patches without the possibily of a midi controller.
    Both options didn't work.

    The global on/off, controller assignable solution, was the more attractive and flexible solution for us.

    best
    Herb
  • A
    A
    Okay, thanks a lot for your answers. I am sure I will get used to use an additional controller :) However I experienced another thing which I am not sure of, but it seems that the Vi player is loosing the assigned controllers everytime I reboot the sequencer. I made sure that the keyboard doesn't loose the assigned controllers. Does anyone experience that? It would be a big pain to load the assigned controllers on every project!
  • H
    H

    All controller settings are saved in a Preset file.
    I recomment to setup a default empty Preset file with all your controller settings.
    Load this file after startup when you create new Presets before adding any Matrices and patches.

    best

    Herb
  • A
    A
    ah okay, i found a workaround in C4 ... you can save the whole VSTi as an fxp file, then everything including the assigned controllers stay. However if I reboot Cubase and load a VI player, the controller data gets lost.
  • D
    D
    last edited
    last edited

    Just load the fxb preset again when you have re-booted.

    FWIW you can save this preset as a startup file which will load automatically every time you open a new instance of VI. Beware that this can totally c*ck up things like the piano.....!

    DG
  • C
    C

    Hi Alex... I agree 100% with you. I have been commenting on this limitaion/problem since the release of the VI. I can't stress how much it bugs me, and limiting it is to me. I assume one of the ideas behind the VI was to have as much playability as possible, yet all this controller on/off stuff really works against that philosophy.

    Here are a few possible solutions:

    1) Have a local On/Off on a patch, cell or matrix level which overwrites the global one (assuming you dont remove the global one completely)

    2) Revaluate the need for making it Global. Perhaps it was not so needed as you thought? You did this earlier regarding the RAM allocation. To begin with two instances with Violins loaded, used twice the ram because of the Ram optimizer. You then reevaluated and improved the VI a lot! What I'm getting at is that perhaps the reasons you made it global dont really apply, and that you could improve it by making it at least at a Matrix level, rather than instance level.  

    3) Add an option of making On and Off two seperate controllers/keys, rather than just one as it is now. This  would make things easier in the sequencer to just hit a key when you need it on, and a key when you need it off. The problem with the current way of doing it is that when you are running the VI on slave computers you can't always see if it's on or off. So having spereate keys would let me hit the "on" key before a section where it has to be on, without worrying about whether or not it was on or off at the beginning.

     -----------------------

    And while I have your attention here is an additions I would like:

    It would be great if I could make a patch monophonic so when I layer it with a legato instrument it stops playing the current pitch, and plays another when I hit a new key.

  • C
    C

    Hmmm.. I see that formatting is fucked up? I had some breaks in there :D

     Anyway, I would like to elaborate.

    Just as you can change parameters like "attack" etc of a patch, it would be nice with a few 'tick' boxes. Here you could tick parameters for a patch like for instance "velocity x-fade" and the "monophonic" parameter I suggested above. Another nice 'tick' would be to turn on/off releases on local level. I dont have to elaborate how limiting it is that this must be done globally ;)

     Just a few things to consider... Thanks for listening [H]