![]() ![]()
What this does (In the case of my example using a Garritan Violin patch in ARIA), is cause the volume to go up as the phrase gets higher, and down as it gets lower. Insert CC1 before every note event and set value 2 of CC1 to value 1 of the MIDI note. Just as another practical example (rehashed from another thread to demonstrate using a Logic Editor)…say I want to add a CC-1 event before every note that matches the MIDI note number (to simulate playing louder with higher notes, and softer with lower notes on an instrument that is set up to use CC-1 for expression volume): I would open a logic editor and do this: This allows you to build scripts to do many edits in batch mode with simple logic scripts that you build in the Logic Editor. I would personally start out by practicing using the Logical Editors. Put rapidcomposer in other daws full#You can treat it like a linear MIDI sequencer right down to the machine level MIDI events you can treat it like a ‘live instrument’ and record your stuff in real time or, you can build yourself a toolbox full of stuff you use often and work in ‘a pattern based’ frame of mind, or you can treat it like an ‘automated mixing console’. Not only is it tremendously powerful in this reguard, it gives you CHOICES! You can treat it like a scoring package…with ‘translation’ schemes that you build in ‘Expression Maps’. MIDI Expression Maps (Convert symbols or text (VST3 Expression events) into a library of expressive event sequences)Īctually, I don’t know of a ‘modern’ DAW that is any better at manipulating MIDI events and dealing with remote controls. Quick Track Controls (Manipulate automation lanes with your Controller) Quick VST Controls (Manipulate automation lanes with your Controller) Generic MIDI Remote Maps (Remotely control practically anything in the DAW with your favorite MIDI controller, or transform various types of real time MIDI events). ![]() MIDI Track Sends (Same tool box as Inserts, but at a different point in the data flow). ![]() MIDI Track inserts (A big tool box full of real time MIDI tools) MIDI Local Transformers (More real time manipulation) MIDI Global Transformers (Useful for ‘real time’ MIDI manipulation of the Data stream) MIDI Logic Editors (Most useful for hard/permanent manipulation in the project arranger or a MIDI editor). Put rapidcomposer in other daws manual#Please look in the Manual and read up on the following: Oops! I think I’d rather move beats 1 and 3 to an open hi-hat! So here’s a script that’ll take every F#1 in the track that falls pretty close to beats 1 and 3, and moves them to A#1 where my open hat lives. Here’s one that accents every 2nd and 4th beat of a high-hat part by adding 6 to the velocity. Here’s an example of selecting all CC 1 events in bars 1 - 4: In the OP’s case, just open a Logic Editor and define the range of events you want to ‘select’, and then use the mouse to manipulate them all in one move: You can isolate and extract things to temporary tracks…transform, select, deselect, mute, transpose, mirror, invert, retrograde, move, slide, bump, merge, bounce, really, the sky is the limit in the power tools CuBase provides for manipulating MIDI events. ![]() No, this is not true at all! You can so DO MUCH MORE with CuBase. Right now all you can do is copy the cc data and paste it to the different tracks, if you want identical data on each one. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |