Vienna Symphonic Library Forum
Forum Statistics

197,167 users have contributed to 43,056 threads and 258,545 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Automation mapping and writing with Cubase

  • Automation mapping and writing with Cubase

    M
    M

    Hi folks,

    I'm new to VEP and I'm hoping that perhaps someone can tell me a way to make this manageable.  I can see how I can use the midi CC channels to manually write automation to synth parameters in VEP.  There are two major issues that I am seeing that I'm hoping to resolve:

    1.  I see no way to logically name the automation lane in Cubase. For example CC 0 in cubase is titled "All CC - CC 0 (BankSel MSB)" even though I'm simply automating Serum's Filter Cutoff.  This is going to be quite unweildy indeed when I am trying to automate several parameters for several synths.  I'm really hoping that there is perhaps some better way of doing this?

    2. I seem to not be able to use "write automation" within Cubase (turning on the red "W" button" and then adjust in a know on the synth manually as the song is playing).  The synth within VEP is able to read and respond to the automation lane but it doesn't seem to be able to send the midi info to the automation lane to write automation.  I'm really hoping this may be some newbie user error on my part, and I have not done anything special to make the midi track that I am sending automation from to be able to receive midi info from VEP.  

    I really hope I can get these two issues resolved, as I'm really happy with VEP so far!  Thanks for any help!
  • M
    M

    A further update:

    I have learned that the "Parameter" mapping has a higher resolution than the MIDI CC mapping.  I notice that in Cubase, other instruments that I put in the Rack Instruments have their knobs named with logical names per how they are defined, while the VEP6 Rack Instrument has "param1", "param2", etc.  It would be really great if we could nake those parameters within the VEP6 server so that when we are automating within cubase we can see what they are.  it is great that we have 512 (!!) paramaters to choose from, but it makes it a bit unweildy if we are trying to remember if we are needing to tweak #326 or #327, lol.   
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @Another User said:

    1.  I see no way to logically name the automation lane in Cubase. For example CC 0 in cubase is titled "All CC - CC 0 (BankSel MSB)" even though I'm simply automating Serum's Filter Cutoff.  This is going to be quite unweildy indeed when I am trying to automate several parameters for several synths.  I'm really hoping that there is perhaps some better way of doing this?

    I suppose you mean visually unwieldy. I do CC in the controller lanes in Key Editor.
    (While 'Bank Select Most Significant Byte' doesn't apply and is not meaningful in your example, that's the legacy of that, per original hardware where MIDI protocol originates. AFAIK you can't edit that in the Automation Lane.)

    Once assigned it just shows [attachment]:

    So I work with all parts in the Key Editor with 'Edit Active Part Only' [setup: Multiple Part Controls] and I create presets such as 'CC 0, 11-15, pb' so I have flexibility. 
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @mbira said:

    A further update:

    I have learned that the "Parameter" mapping has a higher resolution than the MIDI CC mapping.  I notice that in Cubase, other instruments that I put in the Rack Instruments have their knobs named with logical names per how they are defined, while the VEP6 Rack Instrument has "param1", "param2", etc.  It would be really great if we could nake those parameters within the VEP6 server so that when we are automating within cubase we can see what they are.  it is great that we have 512 (!!) paramaters to choose from, but it makes it a bit unweildy if we are trying to remember if we are needing to tweak #326 or #327, lol.   

    I usually use 'Host Automation', ie., the Parameters in VE Pro Automation Mapping. Yeah, I don't know what can change, it seems like this is Cubase.

    I make notes (in 'Notes') regarding this. By the time I render the thing I remember a lot of it. 😊
  • M
    M
    last edited
    last edited

    @civilization 3 said:

    I usually use 'Host Automation', ie., the Parameters in VE Pro Automation Mapping. Yeah, I don't know what can change, it seems like this is Cubase.

    It's not cubase because if you put a Kontakt instrument in Racks and load it with a factory library you can see that the knobs have meaningful titles and if you then write automation with those-those titles populate the automation lane.  

    The solution I recommended to the VEP folks was to let users rename the "paremeter 1", etc box within the instance in VEP6.  Then something like saving or maybe saving and reloading those values could be hard coded so that Cubase would recognize them like in the Kontakt instruments.

    Thanks for your reply!
  • civilization 3C
    civilization 3C

    Yes, that's right, if you write automation from an instrument - Kontakt or Reaktor, at least - from the rack, its name populates the list, and you can set the Automation Panel  to reveal parameter on write now.

    But you can't write like that in VE Pro afaict.

    I'm here from a search trying to determine what the actual full resolution of Cubendo host automation is.
    It only shows eg., .11, .12 up to 2 and so on, but in fact there is a lot more available. It looks like from eg., .9 to 1 is meaningful up to 4 decimal places.