Vienna Symphonic Library Forum
Forum Statistics

197,879 users have contributed to 43,084 threads and 258,679 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Automating channels on/off & using Cubase? Look here!

  • Automating channels on/off & using Cubase? Look here!

    S
    S

    In VEPro it’s possible to automate enabling/disabling a channel in an instance. This is very important because I can load a huge template in VEPro in no time, and only activate the channels I need.

    This can be done by using a CC, and I have selected CC 101. Sending a value of 0, turns the channel on, sending a value of 127 turns off the channel.
    So the idea is, to create a MIDI block in the beginning of a track, and the first time the sequence is running, the CC 101 - 0, is send to VEPro and the channel will be activated.
    Now it seems that every time I select a new articulation with the help of a VST expression, Cubase sends the CC 101 - 0, which causes VEPro to “hick-up”.
    I have also tried CC 15, and it’s the same problem.
    The same track runs fine, if I use old fashion key switches!
    Now I just use a button on my Metagrid to turn on the channels I need, waiting for VSL to give us activation by MIDI! ;-)
  • PaulP
    VSL Team
    PaulP

    HI Stig, 

    Thanks for reporting. 

    Can you please send us such a simple example to reproduce the behaviour, with step-by step instructions and a link to this thread? support@vsl.co.at

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • S
    S

    Well it seems that it all depends on HOW Cubase/Nuendo is chasing CC's.
    Go to preferences/MIDI/Chase Events and REMOVE check mark in:

    "Chase not limited to Part Boundaries"

    By removing the check mark (if any) Cubase will only chase events INSIDE the part!

    This has solved the problem!

    So: It seems that it's okay to automate channels on/off from the track as long as the automation CC (I have only tested this with CC's) is kept in a separate MIDI part and the "Chase not limited to Part Boundaries" is NOT checked.

    Regards Stig
  • C
    C
    @Stig-Christensen said:

    Well it seems that it all depends on HOW Cubase/Nuendo is chasing CC's.
    Go to preferences/MIDI/Chase Events and REMOVE check mark in:


    "Chase not limited to Part Boundaries"


    By removing the check mark (if any) Cubase will only chase events INSIDE the part!


    This has solved the problem!


    So: It seems that it's okay to automate channels on/off from the track as long as the automation CC (I have only tested this with CC's) is kept in a separate MIDI part and the "Chase not limited to Part Boundaries" is NOT checked.


    Regards Stig

    Hi Stig!

    I just had to chime in this old thread that I accidentally stumbled upon and give you a massive THANK YOU!!

    This helped me finally solve a problem that I’ve been tampering with for the past four years, ever since I got VE Pro (running it on the same machine as my DAW) and found out about being able to activate/deactivate specific MIDI-channels in VE Pro from directly within Cubase.
    I kept having pops and clicks during playback (and mixdown) and tried everything that I could possibly think of, from experimenting with processor/buffer/ASIO guard settings in both Cubase and VE Pro, to rebuilding my template and even buying a new audio interface, to no avail. The problem was still there and it would only go away if the Audio Interface buffer size was increased to 1024, in some cases even 2048, which literally has been driving me nuts!

    That is, until I found and read your post. After changing the MIDI-settings in Cubase as per your instructions, everything now runs butter smooth and for the first time in years, I’m able to do 256 in a big orchestral template.

    So, this is really lifting lead off my shoulders and from your name I suppose you are Danish, so if you happen to live in Copenhagen (I’m based in Malmö) I’d gladly buy you a couple of beers sometime.

    Also, for anyone else, I want to add that this is a brilliant example of how incredibly important it is to actually end a thread highlighting a problem you had, by POSTING THE SOLUTION. There are so many loose end-threads at this forum where somebody asks a question, Paul as well as other users eventually chime in to help, messaging back and forth, only to be abandoned by the original poster, presuming he/she found a solution but never cared to explain it so that other users having the same issue may save both time and money.
    So please people, keep this in mind. Next time, you might be the one who benefits from a solution posted by someone else.

    And again, thank you so much, Stig!

    Kind regards,

    Carl Falkenau
  • C
    C

    Correction: I accidentally wrote; ..."activate/deactivate specific MIDI-channels in VE Pro" etc., but I simply meant activating/deactivating specific channels in VE Pro. They can be activated/deactivated by using MIDI CC, but are of course not MIDI channels per se.

    I tried to find an edit button, but there doesn't seem to be one.

    //C