Vienna Symphonic Library Forum
Forum Statistics

180,804 users have contributed to 42,141 threads and 254,364 posts.

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

  • VE Pro is stopping Cubase transport shortcut keys working

    When VE Pro is connected (Networked in my case) to Cubase, it stops the keyboard transport shortcut keys working in Cubase, it's as if VE Pro is over riding transport control.   If I don't have a VE Pro Server instance enabled in Cubase, everything is OK,  put it back on a single track,  and I cannot control Cubase with a shortcut key (SPACE bar to start/stop).

    If I use the QWERTY keyboard on the slave PC (the one with VE Pro on), then that keyboard does control Cubase, but its stops the Master PC QWERTY keyboard wokring..

    Is there anything in VE Pro that allows transport control to be turned off  - as Cubase does not like it.


  • Hi andyjh, 

    That´s very strange. Yes, VE PRO allows to start and stop the sequencer, but it shouldn´t block anything. 

    Did you maybe install any additional software like ShareMouse? Anything else that changed?

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • OK, after much experimenting,  I have found what is causing the problem.

    If I use CC0 as a controller type, with expression maps to control VE Pro, it all goes wrong, if I change CC0 to CC4, then everything is OK,

    so is perhaps VE Pro communicating transport info to Cubase with CC0 ?

     

    so new rule to follow - never use CC0 as a controller type


  • Hi andyjh, 

    That's interesting, thanks for the update...

    Did you get any reply from Steinberg? I have not seen CC 0 have any affect on transport in any sequencer...

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi there,

    I just experienced this problem with the CC0 Controller. When Cubase is sending any CC0 change through VEpro to a VIpro Instance, then the cubase window isn't in focus anymore but the VEpro Window (like you would click on the VEpro Window). If you click back to Cubase the shortcuts work. At least that is my case. Can anyone confirm that?

    I already have set up all my expression maps using CC0, so I hope for a fix soon.

    best regards

     

    Edit:
    Okay, I fooled around a bit and found out that apparently the reason for it was the midi dump. When it is set to "off" it actually reacts to CC0. I set it to CC127 for now so I can work again.


  • Thanks for the update, that's good to hear.


    Paul Kopf Product Manager VSL