Vienna Symphonic Library Forum
Forum Statistics

182,187 users have contributed to 42,209 threads and 254,691 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Question regarding ram optimize/learn function in VI's

  • Question regarding ram optimize/learn function in VI's

    S
    S
    I experimented recently with this function and it's a really great and clever idea. I am just wondering though, in regard to velocity.
    Lets say I have a instrument part that uses a staccato patch, and, say for illustration sake, that there are only 12 notes as it's basis for the particular part it plays.
    If there are 3 velocity levels for each sampled sound, that means there are really 12 x 3 possibilities for each different pitch used by that instrument.

    So, when you play through it using the "learn" function so it tags the samples you use for the part, and then you shed the unwanted samples at the end of the play through, will it leave you with just 12 different tagged sounds, or will you still have the different velocity levels for each pitch attached also? - ie, will you end up with 36 sounds that you can still use that are kept in the ram, or just the 12 sounds and one sample only, of each of the velocities associated with that particular sample ?
    It's just that if you are happy with the 12 pitches, but you decided to use a different velocity during playback later, will you have to reload the patch and do the learn function again, or does it keep every velocity layer associated with that particular sample, which means you can still make adjustments with velocity without having to reload the samples.

    Thanks if someone can make this clear to me.

    best,

    Steve.
  • W
    W
    Optimize gets rid of every note that is not in the recorded velocities. And if you edit or replay it, changing the velocities, there will be missing notes until you reset or "learn" the new ones.
  • C
    C
    This is such a valuable function but what surprises me is that you can't just reload a single patch by dragging a single articulation into the matrix again.

    This would often be much easier than performing full a reset on a whole, large matrix. Also, a full reset isn't always possible if you are pushing the limits of your available RAM.

    Any thoughts on a software tweak from our beloved VI programmers?

    Hey, while I'm spouting, here's another idea on the subject. What if you could reset individual cells with a special click/key combination? You could then save a fully optimised version of an instrument, perhaps with just the perfomance legato patch fully loaded for playing your first line in and the other cells just containing only the relevant patch information.

    Then as you work on your piece you could reload only the desired articulations, as and when you need them, without having to go looking for them in the browser. So it would no longer be necessary to preload massive matrices with everything in them.

    Any thoughts?

    Colin
  • W
    W
    If you change the line you can "learn" just the new notes without using a full reset.
  • P
    P
    "Optimize gets rid of every note that is not in the recorded velocities."

    This is not true if "velocity xfade" is on. In that case, all velocities will be preserved, even if they are not played. This keeps the material fexible and allows you to tweak after the "Learn." If "velocity xfade" is not on, what William said applies.

    Though I've never tried it, I'm guessing that, if you had a patch using only key velocity (no modwheel xfade), you could enable the "Velocity xfade" button just before you ran "Learn," then disable it and you'd preserve all velocities for a non-xfaded patch.
  • W
    W
    Well, I meant only velocity switching, not crossfading. I don't think of crossfading as velocity at all, since the original term velocity refers to the velocity with which the key is struck, and that makes no difference in these crossfade instruments when you use a continuous controller such as mod wheel.

    BTW there is a point to using both velocity and cc controls, which I noticed when I was putting different patches in two cells. The cells were controlled by mod wheel crossfade, but velocity still controlled the entire instrument. This resulted in more controllability than either one alone. Though you could use only two patches in this example.
  • S
    S
    Thank you all for your discussion on this subject. It's been an interesting reading the input, and also as regards the velocity crossfading.

    Thanks again guys for your help here.

    best,

    Steve [:D]
  • C
    C
    Hi Steve.

    >what surprises me is that you can't just reload a single patch by dragging a single articulation into the matrix again.

    You CAN do that - after optimising a matrix I believe you can reset any of its patches to its full, unoptimised state simply by dragging it from the patch menu into its original cell in the matrix. The only undesirable side effect is that the cell settings (volume etc.) will also be reset, but you could make a note of those settings before you reload the patch.

    (At least that's my understanding - apologies if I misunderstood your meaning!)
  • C
    C
    Conquer,

    That was me actually! [:)]

    You have understood correctly and that's precisely what I would expect it to do but it doesn't work (for me) in Logic. There are no additional samples available after dragging the patch back into the matrix again, no hint of a loading procedure and no change in the RAM used. [:'(]

    Colin
  • W
    W
    That is what I was talking about by accidentally leaving an optimized cell in a rack. You can reload a patch but it will still only have the optimized samples. So you have to reset or learn.
  • JBacalJ
    JBacalJ
    last edited
    last edited

    @cwillsher said:

    This is such a valuable function but what surprises me is that you can't just reload a single patch by dragging a single articulation into the matrix again.



    I too would love to have this feature. This would save me a ton of time and trouble.

    Best,
    Jay
  • C
    C
    Sorry about the name confusion Colin, I'm the same at parties. [:O]ops: Just tried this with a standalone VI and am surprised that to find that after optimising, only a full reset brings back all the samples. Slightly counter-intuitive, isn't it? I guess as things stand one has to regard RAM-saving as something you can only do once a part is finalised. The upside is that it could be an incentive to make a decision and move on!
  • C
    C
    last edited
    last edited

    @cwillsher said:

    This is such a valuable function but what surprises me is that you can't just reload a single patch by dragging a single articulation into the matrix again.


    I too would like to see this feature. Very handy idea, and if we're lucky, perhaps not the most difficult code change. Let's hope the VI crew read the thread...