Vienna Symphonic Library Forum
Forum Statistics

182,294 users have contributed to 42,217 threads and 254,749 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Can't figure out why VI Pro is not responding to Mod Wheel data sent by Cubase

  • Can't figure out why VI Pro is not responding to Mod Wheel data sent by Cubase

    DaddyOD
    DaddyOD

    I want to change my Cubase 7.5 template from using CC2 (Breath) to CC1 (Mod Wheel) for Velocity X-fade. . The basic steps are easy enough; I open up a VI Pro 2 instance, change the Y-axis trigger from CC1 to None, then change the Velocity X-fade fader assignment to CC1 using the mouse. When I move my Mod Wheel, the fader is not responding. I try "Learn" mode (right-click, move Mod Wheel). No response. I check Cubase 7.5 and the track is sending out data in response to Mod Wheel movement. The routing of the Cubase track is correct because VI Pro responds to key-playing. I can't figure out what's going on...

    I've been using CC2 for awhile now, but I know in the past VI Pro responded to CC1 because I remember using "Learn" mode previously.

    Any ideas? I feel like an idiot for not being able to troubleshoot this.

    Hobbyist ... Sy Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime ... Sy-ized Woods, Perc, Solo Str, Ch Str, App Str, Harps, Choir, Dim Brass, Dim Strings ... VE Pro, MIR Pro 3D, Vienna Suite Pro ... Cubase 12, Studio One 6, Dorico 5
  • C
    C

    I just set up my keyboard controller. I found that so far it works for {MIDI CC} through MIDI port 1 in Cubase/VI Pro but not otherwise. The note-ons work always but the fader setups for CC work for port 1 only.
  • C
    C

    No, now mysteriously Cubase is recording the physical controllers in other ports. I haven't gotten VI Pro to learn one from this controller (Edirol 61) yet. Fortunately I don't need it to, I just select them through the mouse. Other things I get to learn from Cubase controller lanes and a pencil, actually. Recently I wanted to do it all from one controller. So I feel an idiot now, I don't know what's going on if you aren't even getting CC1 from Cubase to VE Pro, that never was of issue here.
  • C
    C

    Have you simply made CC1 the controller in VI Pro by selecting it and Cubase fails to communicate?

    I don't know if I've ever gotten VI Pro in VE Pro to learn any physical controller. I set them all up in the interface, except for keyswitches for Matrices, which I right-click learn a pencil entry in Cubase.
  • DaddyOD
    DaddyOD

    Thank you so much for your responses, civilization 3. Sorry for the delay in my response. Real life has rudely interrupted me, and I'm not sure if I can jump back into this problem today or the next few days. I'll try. I suddenly have relatives coming to spend several days with us at the same time as a young suitor of my daughter is coming to have important conversations with my wife and I.

    Briefly, I am using the VE non-Pro version that comes with the Special Edition, though I do have VI Pro 2. When I can get back to this I'll have to check out some details of my setup to respond to the points you raise about ports, but I too tried the right-click "Learn" function with no response. The symptoms are as if there is no communication of Mod Wheel data between Cubase (which reponds) and VE (which does not). My guess is that it's something simple that I just don't understand. The VE channel shows incoming MIDI data for notes played and responds properly, but Mod Wheel data does not register. It is not a problem with my keyboard Mod Wheel because Cubase responds.

    I'll be back as soon as I can.

    Hobbyist ... Sy Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime ... Sy-ized Woods, Perc, Solo Str, Ch Str, App Str, Harps, Choir, Dim Brass, Dim Strings ... VE Pro, MIR Pro 3D, Vienna Suite Pro ... Cubase 12, Studio One 6, Dorico 5
  • J
    J

    Just a shot in the dark here but try setting both Cubase and VE, and/or VI Pro, to a "MIDI OMNI" setting and see if you get a response with the mod wheel in learn mode.  When it's on OMNI it should respond to MIDI data coming from any source.

    I don't own Cubase but just because Cubase is receiving MIDI data when you move the mod wheel may not necessarily mean that it's receiving the data from CC1.  A possible workaround: reroute the mod wheel from CC1 to CC2 through your keyboard if that's possible.  It may not be.  Depends on the keyboard. 

    As for your daughter's suiter.  Take him for a drive but insist that he sit in the backseat.  As you're driving around town, engage in a long conversation with your imaginary friend sitting next to you in the front seat.  If he doesn't jump out of the car screaming and running for his life, then he's a keeper.

    "Good luck.  We're all counting on you." 

  • J
    J
    last edited
    last edited

    @jasensmith said:

    As for your daughter's suiter.  Take him for a drive but insist that he sit in the backseat.  As you're driving around town, engage in a long conversation with your imaginary friend sitting next to you in the front seat.  If he doesn't jump out of the car screaming and running for his life, then he's a keeper.

     

     

    And if HE engages in a conversation with your imaginary friend, then YOU need to jump out of the car and run for your life.
  • C
    C
    last edited
    last edited

    @jasensmith said:

    just because Cubase is receiving MIDI data when you move the mod wheel may not necessarily mean that it's receiving the data from CC1.  A possible workaround: reroute the mod wheel from CC1 to CC2 through your keyboard if that's possible.  It may not be.  Depends on the keyboard.

    Unless a deliberate decision was made and implemented to make the 'Mod Wheel' into something other than CC1, the probability isn't good that there is a difference, it's hard-wired into practically everything. In all probability if Cubase is responding to the 'Mod Wheel' it is responding to CC1.

    So I feel I ought to clarify. Is Cubase sending 'CC1' per se to VI Pro, or failing to communicate that data. Ensure that CC is recording/written into a lane of the Key Editor or an Automation Lane in the project window and connected to VI Pro. Having the focus on the instrument in VI Pro and it failing to respond to a controller is a different thing altogether. As I said, I can't be sure that's ever worked here. IE: if your focus is on VI Pro, it is not on Cubase. I don't expect it to work, accordingly; the controller is connected to Cubase. It should work from Cubase, not directly at VE Pro/VI Pro.

    It appears the controller is connected to Cubase, that is it is not connected to VE Pro and VI Pro inside that. I think I have gotten a controller to talk to VE Pro on a slave machine the controller was connected to but unreliably. It is an experimental feature, not guaranteed to work, at any rate.

    So deconstruct this: ensure the CC data, whatever it is, does exist and that it talks to the instrument FROM CUBASE. I have never had this fail (except for this mystery moment just then after setting up my key controller as the CC controller, and the physical controller would work on Port 1 but 'Port 3' failed. Then it worked). But the CC data from Cubase has never failed here. It works, if it does not work for you, something is basically not right. But I'm unsure, you have in every statement said 'Mod Wheel' and I'm visualizing you moving that and something didn't happen. Check that the data, CC1 in the abstract, from CC1 lane functions right, in the case this has escaped you.
  • DaddyOD
    DaddyOD

    Thanks again for all the suggestions to address this. Hopefully I will finally be free to act on them Monday or Tuesday, and I will post about how it goes.

    Hobbyist ... Sy Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime ... Sy-ized Woods, Perc, Solo Str, Ch Str, App Str, Harps, Choir, Dim Brass, Dim Strings ... VE Pro, MIR Pro 3D, Vienna Suite Pro ... Cubase 12, Studio One 6, Dorico 5
  • DaddyOD
    DaddyOD

    FINALLY able to get back to this. I apologize for those trying to help me that real life has made it impossible to do so until today. I finally figured out that the problem was the Expression Map. I had the track set up to use the Special Edition expression map downloadable from VSL. As soon as I selected "No Map" VI Pro responded fine to CC1. Thanks again for all your efforts, guys.

    Hobbyist ... Sy Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime ... Sy-ized Woods, Perc, Solo Str, Ch Str, App Str, Harps, Choir, Dim Brass, Dim Strings ... VE Pro, MIR Pro 3D, Vienna Suite Pro ... Cubase 12, Studio One 6, Dorico 5
  • C
    C

    Well... I came around the same problem about a year ago (with older Cubase versions, too) -  and I also had problems to solve this.

    So I decided simply to convert the modwheel to CC2 (breath) - perhaps this is also an option for you?

    To reach that, put the "Transformer" plugin into the midi insert effects.
    In the upper section add two filters: "type equal controller" and "value1 equal 1".
    In the lower section add the transform destination: "value1 set to fix value CC2 (Breath)"

    I saved this as a preset and assign it to VSL MIDI tracks.
    When I now use the modwheel cubase transforms it to CC2. It saves cc2 data in midi and sends cc2 data to the VSTi.

    Regards
      Chris
  • DaddyOD
    DaddyOD

    Thanks for the suggestion, Chris. I did manage to solve the problem and retained the use of Mod Wheel data using CC1.

    Hobbyist ... Sy Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime ... Sy-ized Woods, Perc, Solo Str, Ch Str, App Str, Harps, Choir, Dim Brass, Dim Strings ... VE Pro, MIR Pro 3D, Vienna Suite Pro ... Cubase 12, Studio One 6, Dorico 5
  • C
    C

    Hey there,

     i see it's an old post, but it might be the same root problem:

    I work in cubase 8.5 on OSX yosemite, i have some templates with expression maps for different libraries that I run on a slave windows PC. The two are connected through VE Pro 6, (I am almost certain the problem already occured on VE Pro 5). 

    Everything works fine, exept sometimes the modwheel / CC1 data is not being transmitted properly to VE Pro on the slavePC. This happens when I use Spitfire Libraries through Kontakt5, and very randomly, its hard to replicate. I Already asked them for support, and they told me it's probably a VE Pro issue.

    Here's a video, see what happens at bar 18:
    https://www.dropbox.com/s/6egpfzuj1n6n970/modwheel%20CS.m4v?dl=0

    Now I read in this topic that it might have to do with expression maps... does anybody experience similar problems?

    Thanks
    Carlos