Vienna Symphonic Library Forum
Forum Statistics

182,256 users have contributed to 42,214 threads and 254,734 posts.

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

  • MIDI EFFECTS WITHIN VEPro?

    Can I use MIDI INSERT EFFECTS WITHIN VEPro, for ex. an arpeggiator?


  • last edited
    last edited

    @Dormusic said:

    Can I use MIDI INSERT EFFECTS WITHIN VEPro, for ex. an arpeggiator?

     

    I don't think so, but I would really like this also, +1

    I often need to use something like Logic's Scripter or Plogue Bidule to massage/transform the MIDI that goes to VI Pro, and I can't do that in VE Pro, where it would make more sense and be more DAW-independent.


  • last edited
    last edited

    @Dormusic said:

    Can I use MIDI INSERT EFFECTS WITHIN VEPro, for ex. an arpeggiator?

     

    I don't think so, but I would really like this also, +1

    I often need to use something like Logic's Scripter or Plogue Bidule to massage/transform the MIDI that goes to VI Pro, and I can't do that in VE Pro, where it would make more sense and be more DAW-independent.

    Funny you should say that actually, I am a Bidule user that just bought VE Pro with intention to switch to it instead. Sick of unstable-ness of Bidule.


  • last edited
    last edited

    @Dormusic said:

    Can I use MIDI INSERT EFFECTS WITHIN VEPro, for ex. an arpeggiator?

    I don't think so, but I would really like this also, +1

    I often need to use something like Logic's Scripter or Plogue Bidule to massage/transform the MIDI that goes to VI Pro, and I can't do that in VE Pro, where it would make more sense and be more DAW-independent.

    Funny you should say that actually, I am a Bidule user that just bought VE Pro with intention to switch to it instead. Sick of unstable-ness of Bidule.

    Well, there are two jobs. For hosting the VI Pro instances, VE Pro is certainly richer and better integrated. If however VE Pro did have MIDI plugin support, for the scripting I need to do I'd still be looking at using Bidule or maybe Blue Cat Plug'n Script inside VE Pro.

    Currently I am sometimes driven to using Bidule to host VI Pro instances, even though I own VE Pro, because I need MIDI plugin/transform support.


  • I also wish VEPro had a midifx slot ahead of the instrument slot in each channel.  Even better would be if VEpro included some kind of midi scripter of its own, similar as Logic's Scripter.  An easy add would be to at least have a VST plugin slot ahead of the instrument slot in each channel, where a midi VST plugin could be inserted, including some that have been mentioned such as BlueCatAudio's scripter.  This would be VERY handy.

    In the meantime, what CAN be done is that Plogue Bidule or BlueCatAudio Patchwork, can be used in the instrument plugin slot, then inside those you can have midi processing in front of each instrument.

    Articulation handling is an area where midi scripting is extremely useful and would be very beneficial to havce inside VEPro.


  • A big +1 to that! This is actually always the thing where I face limits of what can be done to easily customize your template! One library only allows you to automate certain parameters while the other only works with CCs. And Cubase on the other side also limits you to use all the workflows in certain ways. What I want is mostly pretty simple stuff, like being able to control the microphone mixer of all instruments in a template globally. That would be possible through automation parameters from Cubase side, but it only works for some libraries, as automation cannot be turned to CC in Kontakt (actually it can be, burnout requires you to change the scripting for every single patch!). In this crazy market with every developer cooking Bosnien soup, it seems only logical to create a configurable matrix before each VST. Something like a Kontakt Multi Script with user designed GUI and all sorts of ways to route and change midi commandos and automation.

  • Having MIDI effects inside VEP would be a HUGE plus for manipulating MIDI data, sequencing, etc...and would also mean the possibility of forwarding MIDI data to different ports or channels through CC messages, opening possibilities for DAWs such as Ableton which only supports one MIDI port.