Phantom MIDI volume

[JMSchur]

I have read other posts regarding volume bursts and MIDI bombs, but I think my issue is different. It seems to only occur with NI plugs and has been a problem for me since DP5. Here's what happens: I open a new fresh project; I instantiate Akoustic Piano; I hit play and the volume in the plugin jumps to the max. This happens without anything having been recorded. There is no MIDI volume data in the track.. for that matter, no data at all. Oddly, if I disable Event Chasing the volume jump doesn't happen. Which begs the question: What event is being chased in the first place? I'm puzzled.

Regards

John

[1nput0utput]

Continuous controller #7 is the event that is being chased. When event chasing is enabled for CCs, CC #7 (volume) and CC #10 (pan) are transmitted by the mixing board each time the sequence is played. CC #7 value 127 (which is the default fader level for MIDI tracks) corresponds to the plug-ins maximum volume.

[JMSchur]

Continuous controller #7 is the event that is being chased. When event chasing is enabled for CCs, CC #7 (volume) and CC #10 (pan) are transmitted by the mixing board each time the sequence is played. CC #7 value 127 (which is the default fader level for MIDI tracks) corresponds to the plug-ins maximum volume.

Are you saying that CC 7 & 10 are transmitted from an empty track?

[Dave Bourke]

As 1nput0utput wrote, part of that "empty" track is its strip in the mixer whose default values (127 for CC7 and 0 for CC10) are transmitted when you press Play.

However, once you enter a CC7 value in the track yourself, that value will be transmitted instead of the default 127.

So you have two choices:

a) disable CC7 chasing for that track and use an aux track for volume control – not what I'd do personally.

b) note the plug-in's volume setting in its GUI before you press Play, then manipulate the mixer fader until you match that original setting, then write the fader's corresponding MIDI value into the track.

Kind regards.

[JMSchur]

As 1nput0utput wrote, part of that "empty" track is its strip in the mixer whose default values (127 for CC7 and 0 for CC10) are transmitted when you press Play.

However, once you enter a CC7 value in the track yourself, that value will be transmitted instead of the default 127.

So you have two choices:

a) disable CC7 chasing for that track and use an aux track for volume control – not what I'd do personally.

b) note the plug-in's volume setting in its GUI before you press Play, then manipulate the mixer fader until you match that original setting, then write the fader's corresponding MIDI value into the track.

Kind regards.

IMHO that's just plain dumb... just adds extra steps to the process. I've got to add CC7 data whether I want/need it or not. I'm fairly certain that didn't happen prior to DP5. Why does it only happens with my NI Plugs? I have other plugs that have a default volume setting which doesn't change when the sequence begins unless I insert a CC7 event.

[monkey man]

It's a long shot JMSchur, but do you have an empty MIDI track that's assigned to the same (MIDI) destination (port and channel) sitting idly by?

I've found that in order to prevent the sort of thing you're talking about I've had to de-assign any empty tracks that point to the same destination, lest every time I rewind/RTZ/relocate the volume jumps (usually to 127).

As I said, it's a long shot but a phenomenon worth being aware of IMHO.

[JMSchur]

It's a long shot JMSchur, but do you have an empty MIDI track that's assigned to the same (MIDI) destination (port and channel) sitting idly by?

I've found that in order to prevent the sort of thing you're talking about I've had to de-assign any empty tracks that point to the same destination, lest every time I rewind/RTZ/relocate the volume jumps (usually to 127).

As I said, it's a long shot but a phenomenon worth being aware of IMHO.

I have the issue if I create a project with a single track and then instantiate any NI plug.

[monkey man]

Yikes! Oh well, at least I tried. Sorry about that JMSchur. It does sound NI-related then.

[JMSchur]

Yikes! Oh well, at least I tried. Sorry about that JMSchur. It does sound NI-related then.

Thanks anyway for the suggestion. I appreciate the input. I'm convinced it's a NI thing... or at best, a combination of things. This too shall pass.

Regards

John

[Dave Bourke]

I've just loaded up Akoustik Piano 1.1.3 in DP 5.13 and checked out volume control via the Mixer's MIDI fader – it works fine here, with full control over the whole range.

So does Absynth 4, B4 II, Battery 3, Elektrik Piano 1.5, FM8, Kontakt 2, and Pro-53. The only one I couldn't control via CC7 was Reaktor 5, but I can understand that, given its nature.

Kind regards.

[JMSchur]

I've just loaded up Akoustik Piano 1.1.3 in DP 5.13 and checked out volume control via the Mixer's MIDI fader – it works fine here, with full control over the whole range.

So does Absynth 4, B4 II, Battery 3, Elektrik Piano 1.5, FM8, Kontakt 2, and Pro-53. The only one I couldn't control via CC7 was Reaktor 5, but I can understand that, given its nature.

Kind regards.

It's not that I can't control the plugs with CC7; the problem is that unless I insert a CC7 at the beginning of the track, the level jumps to the max with no CC7 event present.

[tonwurm]

The default cc7 value of a newly created MIDI-track fader is at 127. Everytime you hit play this value will be sent to the VI controlled by the MIDI-track. That´s wanted, so you can control the volume by the MIDI-track fader and the level of this fader and the one of the VI are according to each other. The cc7 value 127 represents normally 0db in the instrument. The problem is that NI Acoustic Piano goes to the maximum fader value if it receives 127.
Set this fader to 90 and all is okay. I made clippings of instruments that I use frequently and my prefered default fader value is saved with the clipping and this is even the fastest way to add a VI to your project.