Search the Community
Showing results for tags 'transforming'.
Found 1 result
Preface All gurus/experts/enthusiasts, I have gone through the forum and other places as much as I could. But somehow essential/basic concepts/principles remain clouded/absent/elusive. As if they are trivial and/or common knowledge and so not worth discussing, with focus on "other complex exotic" things. Needless to say basic concepts and principles are the foundations through which one understands and deals with all the other things of the product. In the absence of which everything starts skewing towards becoming "Idioms". Trust me I am pretty functional and productive with Cakewalk, and already it has become my main staple. What I am highlighting is just one of the issues I have a compelling need to tackle. Appreciate your responses, tips and clarification anchored on the generic conceptual framework below, rather than digressing away from it. Thanks in Advance. --- Midi Track Basics Here is the Basic Mental framework of the elements/flow I have and trying to get a clearer picture. Most of it is common knowledge, and yet I am repeating it so there is clarity of context for the questions. (there may be many more. But let us keep them out for now). a) Input Source This specifies a source of MIDI events/data. Like a Midi Controller or output from some other MIDI track Note: There can be at the most only one source. Will not worry about where there is no Input Source. Questions: None b) Incoming Midi Events This specifies what MIDI Channel data will be selected as passed on for processing. OMNI - means all channels, N - a specific channel. Cakewalk does not allow a list of channels to be selected. For example, [2,3,16] Not sure why? Questions. None c) Input side preprocessing These are additional preprocessing of the incoming MIDI data. Further Filtering of MIDI events, Transforming MIDI Events Data, like param values as well as Channel numbers. Is this possible in Cakewalk? What are these elements called? Plugins, Effects?? How are these configured? d) Midi Track This is where data is recorded. Recording may be done in many modes. Overwrite. Means existing data is overwritten with New Data. Comping. Means existing data remains intact. New data is recorded in separate track lanes or versions. User can then select/combine these versions as desired. Sound On Sound. New data is recorded on top of existing data. So track data contains both the old and new data superimposed. UI is provided for seeing recorded data, as well as editing/updating/adding of events and transformation of events data. These are done through direct UI interactions, unlike in (c). e) Output side processing This is about post processing of track data while playing back. For example, changing channel numbers, transforming mid event parameter values etc. Applying effects etc. What are these elements called which does these post processing. FX, Plugins? f) Sending midi data to destination These specify the destination Synths - hardware or VSTs, or other tracks (or even other places) Can there be more than one Destination? Looks Like NO. So how does one accomplish this - without convoluted work arounds? Discussion Is the above picture an accurate basic representation of a Midi Track processing (leaving the complex details at bay)? Given this, my basic question is how to do the following? a) Input Preprocessing How do I change all events on Channel 1 to events in Channel 2? Is there a Plugin/Transformer that can help? How do I include only those MIDI Events that are on Channel 1 or 10? or a list of channels? Again are there any midi filter plugin that can help? How do I exclude Pitchbend events? or select CC events? Again are there filters, plugins that can help? b) Output Side How do I replicate MIDI events on, say, Channel 1 to Channel 3,4,5? Is there a plugin that can help?