1. Register NOW and become part of this fantastic knowledge base forum! This message will go away once you have registered.

Cubase 5 volume of some VSTs keeps going to 0

Discussion in 'Cubase' started by Antony, Jul 14, 2015.

  1. Antony

    Antony Active Member

    This is a bit of an odd one.
    I had my system working fine for several years, then my PC motherboard died.
    I bought a replacement PC and re-installed everything.
    But I now have an odd problem.

    For SOME (but not all) VSTs, every so often (and this varies from 1 second to 10 minutes) the volume on the instrument drops to zero.

    VSTs showing the problem:
    Arturia Jupiter-8V
    Arturia ARP 2600V
    Kontakt 5
    Xhun IronAxe

    VSTs NOT showing the problem:
    Arturia Mini V
    Spark Drum Machine



    The fact that not all VSTs have the problem makes me think some must be responding to different MIDI messages?
    But which message?
    Where is it coming from?
    How do I stop it?

    Any thoughts welcome!

  2. Kurt Foster

    Kurt Foster Distinguished Member

    this sounds like a configuration issue. are you using an on board video card on the MB? sometimes incompatibilities with video cards cause issues. sometimes setting the video to it's lowest setting works.
  3. Antony

    Antony Active Member

    I have the nVidia GeForce 9800GT video card.
  4. Antony

    Antony Active Member

    Interesting... as I test I turned off the Yamaha P-200 keyboard, and now the volume doesn't seem to change...

    So maybe something odd is being sent by the keyboard?
  5. DonnyThompson

    DonnyThompson Distinguished Member

    Is the yamaha the only midi controller you are using, or are you using several midi devices?

    If you are using more than just the P 200, where does it sit in the order of midi devices you are using?

    It's possible that the P 200 may be sending a sys-ex command of some kind that is zero-ing out all other controllers, devices, VSTi's, and/or midi functions, including volume commands.

    121 is the midi controller code for "reset all controls", while 7 is the control/command for volume.

    If you open your midi dialog window/editor, and you notice any of these controller numbers, you should be able to see if the Yamaha is sending those commands to your DAW/VSTi's...

    Just throwing this out there for thought...
  6. Antony

    Antony Active Member

    The Yamaha P-200 was the only controller I was using, but today I have borrowed a SY85 to try to work out where the problem lies.
    This is not affecting the volume, so it must definitely be something in the P-200's setup.
    I have just downloaded MIDI-OX and reconnected the P-200, so I will leave it sitting there for a while and see what data comes out of it!
  7. Antony

    Antony Active Member

    I have now discovered the CAUSE...
    The message being sent is:
    Status: B0
    Data 1: 07
    Data 2: 02
    Event: CC: Volume

    So the question is, what is easier/possible?
    a) to block this MIDI command in Cubase somehow
    b) to turn off this message in the Yamaha P-200
  8. DonnyThompson

    DonnyThompson Distinguished Member

    It's gonna be much better - in the short and the long run - to fix this at the source than it is to have to worry about telling Cubase to block this data every time you want to record a midi track.

    Check your manual for the P 200, to see where in the midi section of the keyboard you can switch this sys-ex command off. Sections to look for could be titled "Midi Commands, or possibly "Midi Filters"...

    If all else fails, you might want to consider reinitializing the keyboard back to its default settings.... but... make sure you understand the ramifications of this first; any settings that you've previously saved in the keyboard would be gone.

    The only other option would be to contact Yamaha Tech Support. For the U.K., the info is located here: http://uk.yamaha.com/en/support/contacts/
  9. Antony

    Antony Active Member


    Thank you all for your input and help.
  10. DonnyThompson

    DonnyThompson Distinguished Member

    Glad to hear that you got it fixed.

Share This Page