![]() it does not fulfill the function you think it should, you can usually re-program that button using the MIDI learn capability of your DAW. It is worthwhile remembering that these are generic controllers and are not DAW-specific.Īnother note worth remembering is that, should your DAW send messages to a specific button, say the ‘Mixer’ button, that you find unhelpful i.e. The QCon series and the Platform series, although fantastic in their own right, cannot alter or interpret these communications. This is usually not significant, but it can lead to confusion and some frustration, because the functionality of the same machine in one DAW is not the same as in another. In other words, even though the language most used, (Mackie Control Protocol) in most cases is the same, the direction of travel of this ‘code’ can be differentiated from DAW to DAW.īecause this communication from the DAW is variable, the resulting functionality of the MIDI controller is therefore variable. ![]() ![]() In short, the answer is that the messages every DAW sends to generic control devices such as the Platform Nano or QCon Pro G2 are different. In order to help users of devices such as the controllers in the iCON QCon series, (iCON QCon Pro, iCON QCon Pro G2, iCON QCon Ex G2, iCON QCon Pro X, iCON QCon Pro XS), the Platform Series (Platform M+ and Platform X+) or single fader devices such as the iCON Platform Nano, many Digital Audio Workstation (DAW) manufacturers produce ‘Remote Control Device’ manuals, (sometimes referred to as a ‘Mackie Control’ manual). "Article: How to Use Mackie-Compatible Controllers with DAWs". ^ "Ardour Documentation: Devices Using Mackie/Logic Control Protocol".^ "Compatible software for Automap: Using Automap for DAW control".Modern MIDI: Sequencing and Performing Using Traditional and Mobile Tools. ^ HUI - Human User Interface for Digital Audio Workstations - Reference Guide (PDF).^ a b c "Taking Control of Pro Tools with a DAW Controller".Understanding Audio: Getting the Most Out of Your Project or Professional Recording Studio (2nd ed.). An Arduino library has also implemented a large portion of MCU, enabling control surfaces to be built with Arduino-compatible microcontrollers. ACID Pro 9 and ACID Pro Next from MAGIX also support MCU. DAWs which support MCU (in addition to those which support HUI) include Ardour, Ableton Live, Studio One, Cubase, and Reason. In 2003, the Mackie Control Universal (MCU) protocol was introduced, combining together functionality from Mackie Control, Logic Control and HUI into a single protocol. Other DAWs to support HUI protocol include Logic Pro, REAPER, and Cakewalk Sonar. īy the time Mackie introduced the Baby HUI in August 2002, the protocol was also supported by DAWs including Digital Performer and Nuendo, making them cross-compatible with HUI-compatible hardware controllers. It was subsequently implemented by hardware controllers from manufacturers such as Solid State Logic, Yamaha, TASCAM, and Novation. The HUI protocol was created jointly by Mackie and Digidesign in 1997 for Mackie's Human User Interface (HUI), the first non-Digidesign hardware control surface for Digidesign’s Pro Tools. It includes support for 10-bit/1,024 discrete values. The user can write console automation which can then be seen in the DAW. HUI protocol allows a digital audio workstation (DAW) and a connected hardware control surface to exchange MIDI signals that synchronize the states of their sliders, buttons, wheels, and displays. It was first created by Mackie and Digidesign in 1997 for use with Pro Tools, and is now part of the Mackie Control Universal (MCU) protocol. Human User Interface Protocol (commonly abbreviated to HUI) is a proprietary MIDI communications protocol for interfacing between a hardware audio control surface and digital audio workstation (DAW) software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |