1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Kontakt 5 Player volume changing by itself

Discussion in 'KONTAKT' started by jamie.long951, Dec 1, 2012.

  1. jamie.long951

    jamie.long951 New Member

    Messages:
    3
    Hi,

    I'm testing out a few libraries I've just bought (session horns, west Africa) and the Kontakt 5 Player keeps adjusting the volume down to about -40 whenever I play a few notes. I move it back up to something like -6 play a few notes and it does it again. I just cannot play anything!

    Also when not pressing any keys the volume goes down very slightly on its own. I am talking about the volume slider within each NI instrument library (next to the pan slider etc)

    Help!
     
  2. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Sounds like you have CC7 being sent off from somewhere (your controller or your DAW).
     
  3. jamie.long951

    jamie.long951 New Member

    Messages:
    3
    CC7? :confused:
     
  4. David Das

    David Das Moderator Moderator

    Messages:
    7,060
    It may be the volume fader for that MIDI channel in your DAW.
     
  5. geoelectro

    geoelectro NI Product Owner

    Messages:
    520
    Probably an intermittent volume slider on the MIDI controller. Should be cleaned.

    You can set the volume of your VST with this slider and then see if the volume changes. If the slider is set close to where you need the volume set it will likely stay there even if the control is intermittent.
     
  6. Sir Nate

    Sir Nate New Member

    Messages:
    1
    Kontakt 5 random volume changes

    I am having similar problems in Kontakt 5. The volume levels of the instruments I have loaded will randomly drop or max out. When I check the midi volume level on the midi track in Pro Tools 9.1, I can see that volume automation has been written. So I delete the automation but it ends up returning. Note: This is also happening to me in Battery 3. I'm all ears if anyone has any advice for me on how to fix this.
    Thanks!
     
  7. David Das

    David Das Moderator Moderator

    Messages:
    7,060
    This really is almost certainly a problem with CC#7 and you understanding how PT (or any other sequencer) handles sending MIDI controller changes to a VI. You may want to read up in the PT manual about how they work, and/or experiment in an entirely blank project with no existing CC#7 (or other) automation so you can understand it.
     
  8. madbaldscotsman

    madbaldscotsman New Member

    Messages:
    4
    I am having this problem as well. I have had Komplete Ultimate 8, 9, and 10. I have had Pro Tools since 7... now I have 11. My Mac OS is now OS X Yosemite. Sometimes the fader (on the instrument) doesn't move until about 1:30 minutes, then goes all the way down. I have never had this problem until I updated to Yosemite. There's no option to roll back. I don't think it's an issue with PT because it worked fine before for about 4 years now. Does anyone have a specific suggestion other than to read our manuals?
     
  9. madbaldscotsman

    madbaldscotsman New Member

    Messages:
    4
    I found a fix though wish I could do this to all instruments at once: Monkey wrench>instrument options>controller>uncheck 'accept standard controllers for volume and pan' If I do this under all groups for group settings, one still must uncheck that box in all instruments. I closed and reopened Pro Tools and had to uncheck the box again. I am assuming that you must save the instrument under 'user settings' if you don't want that to happen, though I haven't tried it yet.
     
  10. Sasson

    Sasson NI Product Owner

    Messages:
    1
    I had the same issue running Cubase. It ended up being my M-Audio controller that was sending random volume change events. After I reset the program on controller and that took care of it.
     
  11. frederic hodshon

    frederic hodshon New Member

    Messages:
    3

    I am having the same issue, AND I have an M-Audio controller.

    How did you "reset the program on controller"?

    thanks