Apple mainstage introductory class4/3/2023 Each element of the group control is still configured in the exact same way. These are simply individual controls that have been grouped together for convenience. The palette also has grouped controls, which is incredibly convenient for quickly adding drum pads, or a set of vertical faders in one go. The Screen Controls Palette, showing the Grouped Controls If you look at different templates you can see how some of these are used, but all are added and setup in the same way. There are sliders, and knobs, and buttons and, well, all manner of different things. There are a number of other types of control that can be added to the Layout view, and these are all shown in the Screen Controls Palette. If you click any of the parameter text fields (shown as simply 127 in this view) you can see that while they are set to all MIDI ports they are Unassigned which means that in this template they are not driven by hardware mapping, but do have different layout properties, such as colour and background. This can be the value of a hardware input device, such as the last value of a particular MIDI message (pit musicians often display the current Expression value, for instance) or it could be something else generated by MainStage or the computer itself. It is a readonly view of a particular parameter. Parameter text is a little unlike the other hardware controls. It’s just a case of having a play with it to understand how this works as it’s a little odd. The keyboard, for instance, can be visually raised and lowered in 3D to try to give some impression of perspective, and depending on where you drag the box to move it around you are either moving the keyboard, raising or lowering it, dragging towards or away from the camera, and so on. It is possible to drag components around the screen, group them with other components, resize them and so on, but many of the keyboard related components also have perspective. The Layout view in MainStage is probably the most fiddly screen you’ll ever use, and while Apple have done a lot to improve it over the years it’s still very fiddly, so starting with a template is highly recommended. If you look at this dropdown you can see that the pitch bend wheel can be mapped to any of the MIDI Controller Change values. If we click the pitch bend wheel, for instance, you can see that this is again mapped to all MIDI ports and all channels, and the controller number is set to Pitch Bend. Or if you are using MainStage with only one of a number of keyboards connected to your system you may want to specify exactly which keyboard this on-screen control refers to, but generally you can leave this alone.Īs you click the different controls you can see the inspector showing different parameters for the different controls, and most will be mapped to sensible things as most keyboards already have pitch bend, modulation wheels, and so on. If you are using a multi-keyboard setup you may need to map this to different keyboards. As you can see the keyboard is, by default, mapped to all MIDI ports on your system, and all channels. Just underneath this is the MIDI Port and Channel for this control. The properties available will depend on the control, and different controls are used for different things, but this is where we map our external equipment to an on-screen control.Īt the top of the Hardware Input inspector there is an Assign button. Hardware Input properties for the keyboard.Īll of the onscreen elements, when selected, will gain a blue border and Hardware Input properties will be shown on the left, as shown here.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |