Harrison Labs V2.0.2 manual Generic Midi Control Surfaces

Page 56

27.0 Generic MIDI Control Surfaces

Mixbus can utilize generic MIDI control messages to control some common editor and mixer parameters.

You will need to use an OSX "midi router" such as http://notahat.com/midi_patchbay to connect from your MIDI inter- face to the ports of Mixbus.

You can see the various MIDI ports, and control their operation, in Windows->Preferences->MIDI.

All gain faders, panners, mute/solo/rec-enable buttons and all plug-in parameters can be controlled by MIDI Continuous Controller (CC) (which is called MIDI Parameter Control in Ardour). Mixbus can also send MIDI "feed- back" whenever gain, pan or plug-in states change so that external motorized control surfaces can reflect parameter changes caused by automation etc. In addition, MMC commands are supported. Generic MIDI control surfaces do not use the MCU protocol.

To use a generic MIDI control surface in Ardour, choose the "Options" menu, then choose the "Control Surfaces" submenu, then select "Generic MIDI".

Mixbus can send feedback to the control surface, allowing it to reflect changes caused by automation or by mouse interaction. You can enable feedback by choosing the "Options" menu, the "Control Surfaces" submenu, the "Controls" submenu, then selecting "Feedback".

To control e.g. a gain fader, use Ctrl/Cmd+Button2 (button2 is the "middle" button of a 3-button mouse) on the fader. The message "operate controller now" should appear. Move the desired fader or knob on your control surface. The fader on the screen should start to move as you move the slider on your control surface. If you activated MIDI feed- back and your control surface supports it, it should reflect changes you do with the mouse.

%Note: The assignments of the MIDI controls are saved with the Mixbus project. For each new project, you have to assign every control manually. To avoid this, you can use a session template.

Mixbus accepts Change Control (CC) MIDI commands. Those commands can be sent on arbitrary MIDI channels. Faders and other continuously moved controls are controlled with CC commands with a range of 0-127. Buttons (e.g. Mute buttons) are also controlled with CC commands, where a value of 0-63 switches the button off and a value of 64-127 switches the button on.

Mixbus also receives and sends some MMC commands, such as play, stop, locate, punch in and punch out.

To receive simple MMC transport commands from an external device, enable Options->Sync->Use MMC and con- nect your device to Ardour's "control" input port.

To use Mixbus as an MTC master, enable Options->Sync->Send MMC, and connect your device to Ardour's "control" output port. Normally you will want the digital recorder/player (Mixbus) to be the sync Master. If you want Mixbus to act as an MTC slave, route your MTC signal into the Ardour "control" port. Then switch Ardour's sync source to "MTC" at the top of the edit window next to the main clock.

Section 27.0 - Generic MIDI Control Surfaces

56

Mixbus User Guide

Image 56
Contents Harrison Mixbus OS X & Linux Table of Contents Introduction Features & Specifications Mixer FeaturesEditor/DAW Features System RequirementsInstallation Installation OSXInstalling Jack Installing MixbusSoundcard I/O support Installation LinuxDownloading and Installing Mixbus Installation All Platforms Download and Install the License fileHow does audio I/O work in Mixbus, and what is JACK? Getting StartedGetting Started Creating Tracks for recordingNeed Help? Jack I/O About JackTrack I/O Selections Track I/O EditorTrack/Bus Inspector Jack MenuOverview Mixbus Editor and Mixer WindowsInput Strips Mix Buses Master Bus Mixer WindowSignal Flow Input Channels Track Name Click to rename and other utility functionsMix Bus Channels Master Channel Right-click here to add or remove redirectsMixer Conventions & Tips Mixbus Knobs and FadersRedirects Plug-ins, Sends & Inserts RedirectsPlug-in Control Sliders Redirect MenuPlug-ins Summary of plug-in support in MixbusLatency Compensation Plug-in ManagerSends Inputs InsertsOutputs Edit Window Overview Basic Editing ConceptsCreating Tracks Track ManagementTrack and Bus Management in the Editor Track and Bus Management in the MixerRecording, Loops and Punch Ranges Using TracksGroups Navigating in the Editor window Zooming and Panning Transport Menu and ToolbarMixbus Automation Region Gain and AutomationGraphical Automation Editing Automation tracks Editing Tools Editing Tools & ModesEdit Modes Smart Editing Edit MenuGain Tool TimeFX ToolJoin Playhead Mode Operation PriorityBehaviors with Join Playhead on Behaviors with Join Playhead offEdit Point Implicit Edit RangeEdit Point = Playhead Edit Point = MouseObject Region Editing Object Region EditingRegion Context Menu Region LayersRegion level Add Files Importing FilesImporting Files to Mixbus Insert MappingExporting Files Audio Consolidation and ExportExporting to a File Initiating an ExportFormat Synchronization Clocks & SynchronizationClocks Using the Click Using the GridTempo, Click, & Grid Defining a Songs Tempo and MeterGrid Modes Monitoring MonitoringMode Locations Window Rhythm Ferret Window Keybindings Preferences SyncPaths/Files Kbd/MouseMidi Ports AuditionMisc Preferences Mixbus Options Menu OptionsControl Surfaces Mackie Control Surfaces Generic MidiAutoConnect MonitoringMisc. Options Stop Transport at Session End 12dB gain reduce during ffwd/rewdPrimary/Secondary Clock Delta to Edit Cursor Always Copy Imported FilesGeneric Midi Control Surfaces Logic Control Protocol Keyboard & Mouse Shortcuts Linux Transport and Recording ControlSession and File Handling Standard Mixbus Layout Cubasish Layout ProToolish LayoutChanging What’s Visible Window Visibility Editing With Edit PointMoving The Playhead Aligning With The Edit PointEdit Point Playback Edit Point Active Mark? Edit Range Region OperationsEdit Range Selecting Markers and LocationsDefining Loop, Punch Range, and Tempo Changes Mouse ModesMouse Object Mode Mouse Zoom ModeMouse Ops on Solo/Mute/Rec-enable Mixbus Function Mouse CommandMouse Ops on Solo Buttons Only Mouse Ops on Faders & Plug-in ControlsKeyboard & Mouse Shortcuts Mac Standard Mixbus Layout Cubasish Layout ProToolsish LayoutKeyboard Shortcuts Macintosh Window Visibility Aligning With The Edit Point Command+e Copy Command+c Cut Command+x Delete Delete alternate Defining Loop, Punch Range, and Tempo Changes Mouse Object Mode Mouse Ops on Solo Buttons Only Appendix a FAQ How do I route audio from another application into Mixbus? Why is there no Save As?What is the difference between Snapshot and Save As? What audio file formats are supported? How do I use Midi transport controls MTC/MMC with Mixbus?Debugging Midi CC What Hardware controllers are supported?For generic Midi CC Linux Mixbus just bounces in the dock when I try to launch it OSXAll Platforms Appendix B Release Notes MixbusAppendix B Release Notes Known Issues All platforms Mixbus 1.5.1Mixbus 1.4.1 Mixbus 1.4Mixbus 1.3 Features Mixbus v1.2Appendix B Release Notes Mixbus Appendix B Release Notes Contact Information Http//mixbus.harrisonconsoles.com