Control Change Recording is ARRRRRGHHHH

[kgmonarch]

Whenever I record control changes, it always assumes that CC values start at 0, even if I perform knob tweaks at the beginning of the recording. I always have to go in and manually remove that one little dot that gets recorded at the beginning.

• FML
• THIS IS HOW IT SHOULD BE

[Warrior Bob]

MIDI CC values are sent as changes, and as far as I know there's no standard way to query a device to see what a controller's current "state" is, so there isn't any easy answer to this problem.

It would be great to have a switch for new clips that goes between its current behavior, and the behavior you describe - where it assumes that everything before the first change is at the first change's level. I know I would certainly enjoy using something like that.

[kgmonarch]

MIDI CC values are sent as changes, and as far as I know there's no standard way to query a device to see what a controller's current "state" is, so there isn't any easy answer to this problem.

It would be great to have a switch for new clips that goes between its current behavior, and the behavior you describe - where it assumes that everything before the first change is at the first change's level. I know I would certainly enjoy using something like that.

Well, prior to recording, I carefully adjust all my controllers - those values that I am adjusting should be taken as the "current state" at the start of the recording. If only there was a way for M4L Midi Effects to affect how CC's were recorded BEFORE they hit the recording track.

A "MIDI record effect", so to speak.

If, however, controllers aren't changed prior to recording, then values should be taken from the ending values of the previous clip played on the track.

In the meantime I'll have to craft some sort of M4L "zero-blip-killer"

[kgmonarch]