Vienna Symphonic Library Forum
Forum Statistics

185,035 users have contributed to 42,375 threads and 255,407 posts.

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

  • Velocity -> Vel X-fade

    It sounds strange, I suppose, but I'm wondering about the note velocity to velocity crossfade mapping; it doesn't seem to work at all. This seems to be because the crossfade slider overrides any behavior mapped from note velocity. I'm using the Chamber Strings and I wanted to see what my current project would sound like if the velocity layers were allowed to blend a little (as opposed to the standard cross-switching).

    Thoughts anybody?

    J.

  • I don't actually understand what you are trying to do. Surely velocity xfade is either on, in which case it ignores the note velocity and goes for the controller value, or it is off and it ignores the controller value.

    DG

  • Nope, there's an option in "Perform -> Map Control" for "NoteOn Velocity" to map to anything. I'm choosing to map it to Velcoty Crossfade hoping to hear transitions between the velocities, governed by note velocity itself. Yes, same idea as using a controller, but the velocity values are used as the "controller", so to speak (and since these are already worked out in my score, it's a bit of a no-brainer to at least try it). This option appears to be possible, but doesn't seem to do anything.

    J.

  • Hi,

    we just found that, too. Thanks for pointing it out. This will be fixed in the next update!

    We missed that option in our tests, as we didn´t really think of it. When you assign the Note on Velocity to Vel Xfade, the whole point of the fader controlling the dynamic progress is somehow lost....

    If you hold more than 1 note, the Note On Velocity of the next note will also affect the velocity of the sustained note, so we simply might take that option out as well, to avoid confusion [:)]

    Sorry for the inconvenience!

    Best,

    Paul

    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    If you hold more than 1 note, the Note On Velocity of the next note will also affect the velocity of the sustained note, so we simply might take that option out as well, to avoid confusion [:)]


    Well, I can't exactly remember how the velocity crossfade on the old S1000 behaved in this regard, but it seems to me the voices were independent... Strictly speaking, velocity crossfading _is_ the behavior I'm referring to (crossfade as a function of velocity) -- what the VI does with the fader would be better named "sample crossfade" or "dynamic crossfade", and is basically a controller re-mapping of a velocity crossfade.

    So, are you saying that you're considering simply removing the NoteOn Velocity option as a mapping for the velocity crossfader? That would be a real shame. It's not the greatest option for solo instruments, where the phasing/doubling sound is often quite obvious, but for the full strings and chamber strings it's basically fine (sure, it would make for a funny looking score if everytime you wrote in a "p" the part had music for 6 players, whereas everything marked "mp" had music for 12!). Why not just implement the velocity crossfade by voice? I suppose the GUI fader would look a little out of place, but at least you'd have an actual velocity crossfade.

    On the other hand, if I really need it, I suppose it's possible to map velocity to CC11, or whatever, in the Logic Environment...

    J.

  • I'm using Plogue's Bidule as host.
    You may find a Bidule (Modul) inside this host, which is called "Note velocity to Parameter".
    This function transforms any velotity of a note to any MIDI controller.
    Works great.

    May be this could help you.

    [:)] Jovan

  • Hey jovan, thanks. That's good to know. Unfortunalely, this part wasn't being played on Bidule, but I can use that trick in the future! (I also use Max/MSP, which would be easy to implement this mapping with as well.)

    The more I look into Bidule the more impressed I am- it's really a great program. I'm curious to know what the final version will be like.

    cheers,

    J.

  • Really interesting.
    I was allways using VI with the forte rack on a Windows PC.
    I kept my hands of Bidule, because I thought it's only a beta version.
    But forte has one problem: you cannot pan the VI instruments, so I tried other solutions and came to Bidule.
    I was really surprised of the efficiency and the possibilites off this program.
    And it a really stabile program with low CPU consumption.
    I use it now for my new projects.
    Also the recording possiblities are great, you can record as many tracks you like in one session, which is a great help for orchestral scores.

    [:)] Jovan

  • In the latest iteration of the Vienna Instruments software (at least in the Mac version) Note-On Velocity does not appear to work as a control source for ANY parameter in the Map Control section of the Perform window. This is in contrast to previous versions where it could be used as a control source for the Master Filter, Master Attack etc.

  • last edited
    last edited

    @jbm said:

    Hey jovan, thanks. That's good to know. Unfortunalely, this part wasn't being played on Bidule, but I can use that trick in the future! (I also use Max/MSP, which would be easy to implement this mapping with as well.)

    The more I look into Bidule the more impressed I am- it's really a great program. I'm curious to know what the final version will be like.

    cheers,

    J.


    If you in the next future need a transformation of note velocity to Velocity X-fade, i have written a smal group (module) with makes this transformation for the VI & it works great.

    Please concant me by private message.

    [:)] Jovan