Vienna Symphonic Library Forum
Forum Statistics

182,349 users have contributed to 42,221 threads and 254,760 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP5Pro : Instance, experimental warning when using external midi

  • VEP5Pro : Instance, experimental warning when using external midi

    T
    T

    Hi,

    If you have an VEP instance run from a server, you are able to enable external midi input but you get a warning that this is an experimental feature with side effects.

    Could someone detail what these are, as Id like to use it, but im happy to use it in a 'limited' way, to avoid any known issues.

    my use case is pretty simple.

    Im using Ableton, for its recording features (clips etc), but Ableton does not support poly pressure or voice per channel midi that I require for my Eigenharp.

    So what I have done is:

    a) create a VEP VST within Ableton, I then have audio tracks in ableton to record each channel from VEP.

    b) in the VEP instance I host all my VSTs/audio units

    c) I send midi directly from my Eigenharp to the VEP instance *

    (* remember I cannot go through ableton, as this would strip the poly pressure data off)

    this enables me to do all (audio) clip recordings in ableton, and yet still use the expressiveness of the eigenharp.

    of course though, this requires the instance to use external midi, and so hence encoutering the warning.

    is this something to be concerned about?  as it appears to work ok in testing.

    btw: as an extension, it would be useful to also use an Event Input or just send midi to the VEP VST in ableton, when midi is coming from my keyboard. This would always be to a separate channel within the VEP instance. again, seems to work fine.

    Finally, im perfectly happy that the clock/sync/transport information always comes from the host i.e. ableton, which in this scenarion Id consider the master... so I wont send midi clock information over the external midi interfaces (which I could imagine could cause some confusion)

    thoughts?  anything to watch out for? why the warning :) ? 
  • C
    C

    the warning means it won't necessarily work.
  • T
    T
    last edited
    last edited

    @civilization 3 said:

    the warning means it won't necessarily work.

    sorry, but as a software developer myself, thats not really a good explanation [:)]

    under what circumstances does it work, or not work? what are the limitations or complexities involved?

    ... obviously it does work sometimes, but I don't want to get deep into using it, only to find at some point to find an issue, or worst still that VSL decide to withdraw the feature.

    personally id expect issues around midi clock/sync , but as decribed above I can avoid these... PDC, but this is again a non issue for me.
    I know if I put a warning like this in my software (or documentaton) there would have been a good reason, it wouldn't just be chucked in there 'just in case'

    or is this just a warning, its a new feature and hasn't been tested well yet? (etc)
  • C
    C
    last edited
    last edited

    @thetechnobear said:

    ... obviously it does work sometimes, but I don't want to get deep into using it, only to find at some point to find an issue, or worst still that VSL decide to withdraw the feature.


    Just a friendly advice, don't expect it to work. I wouldn't get deep into using it, hence their warning, I guess.