Mainstage notes: Difference between revisions
Jump to navigation
Jump to search
(Created page with " <!-- Like most DAWs, MainStage (And Logic Pro it is built on) has its own idea about how to structure things, and like most things, it sort of assumes this is all obvious, you will pick it up through osmosis and trial and error. Concert '''Set''' : a collection of patches, much like a folder : you could use that for :: different patches :: organizing instruments/patch/channel strip configuration for later reuse :: whatever else '''Patch''' : a singular...") |
mNo edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{#addbodyclass:tag_tech}} | |||
{{#addbodyclass:tag_media}} | |||
{{avnotes}} | |||
<!-- | <!-- | ||
| Line 5: | Line 7: | ||
Like most DAWs, MainStage (And Logic Pro it is built on) has its own idea about how to structure things, | Like most DAWs, MainStage (And Logic Pro it is built on) has its own idea about how to structure things, | ||
and like most things, it sort of assumes this is all obvious, you will pick it up through osmosis and trial and error. | and like most things, it sort of assumes this is all obvious, you will pick it up through osmosis and trial and error. | ||
| Line 63: | Line 62: | ||
Mainstage's focus on making your main interactions be a ''visible'' thing is great when | |||
It also can make it a little more opaque to do more complex things. I've seen people: | |||
* have one keyboard play all at the same time always, and separately control which of those you actually hear | * have one keyboard play all at the same time always, and separately control which of those you actually hear | ||
| Line 125: | Line 127: | ||
'''MIDI routing''' | '''MIDI routing''' | ||
A channel strip can have a MIDI control input | |||
...which will be via keyboard screen controls / | |||
Latest revision as of 18:50, 22 April 2024