All Sonars (2017.6 inclusive) : MIDILeaks (Remote Control killer)
I mention that one more time explicitly, because of recent bugfix:
Assigning a MIDI Remote Control will now save with project
I mean there is an intention to make
Remote Control working, but described here effect is
bizarre for anyone who tries to use Remote control is a project with almost any Synth.
Requirements: any MIDI controller with keys (on channel 1) and a knob or fader assigned to CC16 (channel 1), any Sonar. Particular CC is just to reproduce the example exactly, it can be any CC/Note/other MIDI on knob, fader, button, etc.
- Create an empty project, insert TTS-1
- Check you can play piano with keys
- "Remote control" track 1 volume with the knob (so assign CC16 as remote control for TTS-1 output volume).
- play keys while turning the knob, you should hear the effect: the volume is changed as expected, but pitch is also shifting...
To give you an idea why I have called that bizarre: think about 2 synth, one is currently focused (let say piano) and you have assigned a knob as Remote Control for another track volume (let say drums). You have started to play piano along recorded drums, and then have decided to lower drum track volume.... the sound of the piano is changed...
I remember the feeling the first time that has happened to me. Note that depending from CC and synth, the effect can be virtually everything, including some subtle parameter which barely affect the sound. You modify something with intention but the sound is changing rather weird way. Depending from the synth, the change can be saved into the project.
MIDI leaks exist for
all Remote Control assignments, including
MIDI learn in Matrix.
The second case of MIDI Leaks is when there are 2 Control Surface plug-ins for one controller (f.e. Generic Surface + ACT MIDI, quite popular combination). All assignments from the first plug-in are leaking into tracks/synth.