Reply to thread

Message: [QUOTE="Shamiso, post: 92956, member: 160"] MIDI 1.0 names CC1 Modulation Wheel and CC11 Expression, but a virtual instrument decides what either message actually changes. In orchestral libraries, CC1 and CC11 often become a useful pair because one can shape recorded dynamics while the other trims level, yet treating that setup as a MIDI rule causes trouble fast. A sustained violin or horn needs control after the note has started. Velocity cannot supply that movement because it belongs to the note attack, which is the same distinction behind [B][URL='https://goldmidi.com/community/threads/midi-volume-vs-velocity-inside-a-daw.78262/']MIDI volume versus velocity inside a DAW[/URL][/B]. Continuous controller data can keep moving for the length of the note, making it suitable for crescendos, diminuendos, and smaller phrase changes. The important detail is where the instrument maps those messages. A MIDI CC expression lane can be perfectly drawn and still produce the wrong result when the patch expects another controller. [HEADING=2]CC1 is not automatically the dynamics control[/HEADING] The common orchestral setup maps mod wheel CC1 to dynamic layers or a crossfade between samples recorded at different playing strengths. In that setup, changing CC1 MIDI controller data can alter loudness and timbre together because the instrument is moving between different recordings rather than merely turning one recording up. CC11 MIDI expression is often mapped as a level control on top of that performance. This makes MIDI modulation vs expression feel simple in practice. CC1 carries the musical intensity, while CC11 expression gives you room to pull a loud, bright performance backward without throwing away its tone. None of this is guaranteed by the controller numbers themselves. Some libraries use CC11 for dynamics, some use CC1 for vibrato or another destination, and individual patches can behave differently inside the same product. The fact that [URL='https://goldmidi.com/community/threads/the-same-midi-file-can-sound-wildly-different.77159/']the same MIDI file can sound wildly different[/URL] is partly a result of this receiving-side interpretation. Check the patch documentation or its MIDI map before drawing anything substantial. A good rule for MIDI expression control is to identify what changes timbre, what changes level, and what handles articulation before deciding which lane deserves the main phrase shape. [HEADING=2]Separate performance shaping from level control[/HEADING] For a library where CC1 really does drive dynamics, draw the broad rise and fall of the phrase there first. A MIDI expression message on CC11 can then handle smaller level corrections, entrances, tails, or balance changes without rewriting the dynamic layer choice. This separation also keeps MIDI expression vs volume from turning into one giant lane doing every job. CC7 normally serves broader channel volume, while CC11 acts as expression within that range. Once the instrument produces audio, [URL='https://goldmidi.com/community/threads/how-audio-plug-ins-actually-work-inside-a-daw.77876/']host automation and MIDI data follow separate paths inside a DAW[/URL], so moving the channel fader changes rendered audio rather than the controller performance upstream. Recording a MIDI expression fader in real time can work well because the curve follows your phrasing instead of becoming a row of perfectly spaced points. Editing afterward is still useful. Remove accidental spikes, keep the phrases from snapping between values, and confirm the lane is routed to the same instrument and channel as the notes it is meant to shape. Short articulations may need a different balance. Velocity can matter more for a staccato attack while CC1 or CC11 does little, depending on the patch. Sustains usually reward continuous movement because their level and tone need somewhere to go after Note On. Keep the dynamic lane below its ceiling until the phrase genuinely needs maximum intensity. If every sustained note already lives near 127, later accents have nowhere to go, and CC11 ends up being used to fake contrast that should have come from the instrument's own dynamic mapping. [HEADING=2]Routing can break otherwise correct CC curves[/HEADING] MIDI CC messages belong to a channel, not to a DAW track name. Two tracks feeding the same destination and channel can therefore send competing controller values even when their notes live in separate regions. The distinction between [URL='https://goldmidi.com/community/threads/midi-ports-channels-and-tracks-do-different-jobs.77157/']MIDI ports, channels, and tracks[/URL] matters whenever a carefully programmed swell changes another part unexpectedly. A CC1 curve can also appear useless when the track reaches the wrong MIDI port, the instrument filters the controller, or host automation is moving a different parameter. Troubleshooting becomes easier when you follow the data in order from the physical controller, through the recorded CC lane, into the correct channel, and finally into the patch mapping. For practical orchestral work, treat modulation in MIDI as a message source rather than a promise about sound. Treat CC11 as the MIDI CC for expression rather than assuming it always means a plain volume trim. Once the patch mapping is known, the two lanes can divide the job cleanly, and you can reshape intensity without turning every correction into a mix move. [/QUOTE]

Name