Kontakt volume keeps resetting itself

Dudes:

The initial volume in Kontakt is too low but after I set it to the desired level, it flips back to where it was as soon as I start the track. There are no volume controlers in the MIDI data and all the velocities are the same (100). If I keep Kontakt open, the volume remains set but if I close it or restart the track, it flips back.

Anyone know why, and how to prevent that 'feature' from driving me up a tree?

Thanks - rev

Three things:

1) Do you have a volume envelope in the track?
2) Do you have "Zero Controllers When Play Stops" turned on? (Look under Options > Project... > MIDI Out > Other Options)
3) Pressing the Reset button on the SONAR transport can reset KONTAKT instrument volumes to MAX. As was suggested earlier, you need to turn off "Accept standard controllers for Volume and Pan" for each KONTAKT instrument. (In Kontakt 2: Wrench button > Instrument Options > Controller > Accept standard controllers for Volume and Pan check box << UNCHECK)

I would UN-CHECK the "Zero Controllers..." option in SONAR. It will throw you a curveball in Kontakt or something else at some point if you don't.

I just changed that "Accept Standard Controllers...." setting on all of my GPO presets last night after a little mishap : I forgot about the Reset button quirk and pressed it in the middle of an orchestral mix. The result about knocked my head off.

Al:
I found 'Default Volume' in Kontakt, either -6 or 0 but I didn't find 'Use standard CC#7 for volume' - at least not under Options.

Thanks..barlowjam simply quoted from a somewhat related reply but not exactly (a thread about RA..Kompakt engine there)

so, that #7 and #10 setting for volume/pan is only in Kompakt ..

Infinite added - "Accept standard controllers for Volume and Pan" for each KONTAKT instrument. (In Kontakt 2: Wrench button > Instrument Options > Controller > Accept standard controllers for Volume and Pan check box << UNCHECK)"

The "Accept standard..." option is just another name for the same thing. I actually meant setting it to ON and try to control the volume with an event from Sonar (event list or MIDI volume of the track)


Well , turning it off is one "solution" but I actually prefer having synths to DO respond to volume changes turning it off as a workaround would maybe work.. but it shouldn't jump anywhere in the first place , we've seen such threads before and most of the suggestions are always the same..simply don't work in the NI case.

There are also small behavior differences between the VST and DX versions that you should check.

ORIGINAL: Honest_Al
Well , turning it off is one "solution" but I actually prefer having synths to DO respond to volume changes turning it off as a workaround would maybe work..

Turning it off is the best option for GPO, because most of your GPO dynamics are set through the MOD WHEEL. The internal instrument volume control is used to adjust for optimum playback levels of each sample. In fact, the included NI presets for the GPO instruments have lots of customized volume settings -- they are not all set to 0db or -6db.

but it shouldn't jump anywhere in the first place

ABSOLUTELY -- if there is no envelope or CC#7 data in the track and "Zero Controllers..." is UN-CHECKED, then nothing (including the Reset button) should send CC#7 messages to the synth -- UNLESS you manually change the MIDI track fader level. This seems to be an issue in SONAR.

Thank goodness Kontakt 2 / Kontakt Player 2 / Kompakt / etc. have the option to disable CC#7 internally on a PER INSTRUMENT level. The original GPO Kontakt Player 1.5 was set up so that this setting was ON or OFF for then entire Kontakt engine. So either CC#7 worked for all instruments or it didn't at all. That was a pain.

Hey Al!

My "His problem was the opposite" post was a reply to barlowjam's post #6. [The OP needed to DISABLE the setting barlowjam suggested, not ENABLE it.] You and I just cross-posted. I agree with you 100%.

For libraries like GPO, where the internal Volume control (which is automated by CC#7) is used more like a set-and-forget level control, it's better to disable the CC#7 parameter altogether -- BASED ON THE WAY SONAR SENDS UNWANTED CC#7 DATA. If SONAR would just leave CC#7 alone (unless I put some CC#7 data or an envelope in the track or manually move the fader), then this would be unnecessary.

I can appreciate that. I was up till 5am the other night running backups on my 200GBs of system, projects & samples drives.