humatic - htools - TouchDAW
search   

Sequencer setup

To configure TouchDAW to work with the sequencer of your choice go to Setup / DAW Controller / Sequencer. This will bring up a selection menu as shown above. Select your DAW here. Next you need to assign a remote control device in the DAW and set it up to use the correct MIDI ports for communication.

The following shows where to do that in the sequencers that TouchDAW has dedicated support for. If you use a different program, please refer to what its manual has to say about "Mackie Control" and try what sequencer preset in TouchDAW works best with it (in most cases that will probably be "Logic", allthough some assignments on the phone interface will likely not match. On tablets the "Studio One" preset may also be a good choice as it does not change the button titles from how they are labelled on the original hardware.).

Please be aware that MIDI port names on your system will not necessarily be the same as those shown in the screenshots below. Generally rtpMIDI, mnet & Apple MIDI Network ports are bidirectional, so both input and output should be assigned to "the same" (ie: equally named) port. With ipMIDI, qmidinet and multimidicast in and outputs will have different names.

Note:
This refers to the DAW control part of the app only. TouchDAW's keyboard, XY-controllers etc. are set up like you would do with any other (hardware) keyboard or controller. We assume that you know how to do that in the sequencer of your choice.



Cubase / Nuendo

From the "Device" menu select "Device Setup", which will make the window shown below appear.

(In Cubase 9.5 this is all under Studio / Studio Setup)



In the left hand column select "Remote Devices" then click the "+" button on top of that column. From the list of predefined devices select "Mackie Control". You will then see a new entry under "Remote Devices". Select it and assign MIDI in and out ports on the right side of the window. In the screenshot "rtpMidi_1_local" refers to the first RTP session created in RTP MIDI's control panel. The name of that port will be different, depending on how you named it. The important thing is that both in- and output use the same port here when running over RTP. When using multicast you would need to select "ipMIDI Port 1" for input and "ipMIDI Port 2" for output.

TouchDAW 1.3. has additional options related to changing channel selection in the DAW when touching faders. In order for those to take effect, the "Enable Auto Select" option in Cubase / Nuendo needs to be off!

Next, to make sure control data does not interfere with musical data, select "MIDI Port Setup" from the left hand column and uncheck the control port under "In All MIDI" as shown below.



Steinberg's MCU implementation is documented in a pdf file named "Remote_Control_Devices" accessible from the DAW's help menu.

Cubase 7.5 and larger

Steinberg have changed parts of their Mackie control implementation in Cubase 7.5 without updating the documentation (in fact without documenting or mentioning it anywhere at all). You can find a user-compiled list of changes on the Cubase Forum. As of version 1.5.1 TouchDAW includes an extra preset for Cubase 7.5. If you rather want to continue working with the old implementation, leave TouchDAW at the Cubase / Nuendo preset, select "Mackie Control" from Cubase's "Devices" menu and set the popup in the little window that will come up to "Compatibility":



The pdf documentation was finally updated in Cubase 8.5 (see Help / Remote Control Devices). Unfortunately in Cubase 9 all documentation has been removed and Steinberg now want you to read it online at steinberg.help where the document in question is referred to in various places but of course is nowhere to be found. It is included in a full download of all the Cubase 9 pdfs though.


Ableton Live

From the "Options" menu select "Preferences", and click the "MIDI Sync" tab. Then in the upper part of the MIDI preferences set the first "Control Surface" to "Mackie Control" and select the first RTP session's port for in- and output when running over RTP or "ipMIDI Port 1" for input and "ipMIDI Port 2" for output when using multicast.



As with Cubase it's a good idea to disable the midi port used for remote control for normal track input:



Live's MCU implementation is documented in a pdf file from Mackie that's no longer available on their website directly but can be found on the web..


Apple Logic

TouchDAW 1.3. has extended support for auto detection of control surfaces. When you set the sequencer in the app to Logic, TouchDAW will by default activate this and Logic should automatically detect and install a Logic Control given the underlying MIDI connection has previously been made. The option can be turned off in case you want to use the app as a generic controller.
Alternatively you can also use Logic's scan functions available at: "Logic Pro" menu / "Preferences / Control Surfaces / Setup" Those should equally discover the app and install it as a Logic Control.
Note that in both cases it may be necessary to adjust the MIDI output port that Logic assigns. The input port that it read TouchDAW's query response from should be correct.

To install things manually click the "New" dropdown in said control panel and select "Install". From the list of defined devices select the one that says "Mackie Designs" for "Manufacturer", "Logic Control" for "Model" and "Logic Control" for "Module". Click "Add" and a new control surface will appear in the setup window. Now all that is left to do is setting the MIDI ports under "Output" and "Input Port" at the top left hand side as shown below.
Settings in the "Control Surface Group" table can remain as they are, but you should make sure that the "Track Lock" option is off. See Logic documentation for details.




Logic's MCU implementation is exessively documented in a pdf file available on Apple's website.



Pro Tools

Go to Setup / Peripherals, select the "MIDI controllers" tab and set "Type" to "HUI". Then set the ports under "Receive from" and "Send To" to the MIDI ports TouchDAW is connected to. Note that Pro Tools for Windows needs to be run as Administrator to work with some MIDI drivers (those that appear with an "(Emulated)" suffix. This includes ipMIDI, LoopBee and our mnet driver)



When working with Pro Tools TouchDAW will emulate a MCU unit that again emulates a HUI. You should therefore not only read the "Mackie Control for Pro Tools" guide (no longer available from Mackie directly unfortunately) but also the original HUI documentation as much of the information given in the Mackie Control guide only makes sense if you know how things work with the original HUI

Benoni Studio have a number of good Pro Tools / TouchDAW videos on their you-tube channel. Thanks


Sonar

Go to Edit / Preferences, select MIDI / Devices and make sure the MIDI ports you plan to use are enabled for in- and output. Next select MIDI / Control Surfaces and click the yellow icon on the upper right hand side to add a new controller. In the upcoming dialog select "Mackie Control" and set in- and out ports. The dialog should look something like this then:



Additionally you may need to tune controller settings in the "Controller / Surfaces properties" dialog available from Sonar's upper toolbar. TouchDAW's phone interface will always send F1 and F2 keys to change windows in Sonar mode, so you will probably want to assign Track and Mixer views to those keys. Also you will need to enable level metering if you want TouchDAW to show audio levels: The tablet interface will show levels next to the faders with the "Signal LEDs" setting or - like a hardware MCU would - in the text displays (with the "Signal LEDs + Meters" setting). On phones both options enable the meter next to the fader.

Documentation of Sonar's MCU implementation can be found in a compiled html help file that's usually located at "Program Files/Cakewalk/Shared Surfaces/MackieControl.chm".

BEATNVISION's you-tube channel has some nice Sonar / TouchDAW videos including a setup tutorial. Thanks for that!




FL Studio

Go to the Options menu. Make sure "Enable MIDI Remote Control" and "Enable MIDI Output" are selected.

Next open the MIDI Settings window. Under "Output" select the MIDI port linked to TouchDAW's DAW controller (shown for mnet / MIDI hub below. When using rtpMIDI use the first session you created). Set the port number dial to 102 for whatever port you selected.

Next - under "Input" select the corresponding input port (same name as the output with both rtpMIDI and mnet). Select "Mackie Control Universal" from the "Controller type" dropdown, check the "Enable" box and again set the port number to 102
(Note that in FL Studio versions before 11 the port number setting only exists on outputs. In FL Studio 11 and larger you need to set it for both in- and output).

The dialog should look something like this in the end:




To enable TouchDAW's keyboard, XY-pads and the MIDI mixer you just need to enable the respective MIDI input as a "Generic Controller" as shown for "MIDIHub Port 2" in the above screenshot.

Want a video? ULTVProductions have done a nice video tutorial for FL Studio 10. Thanks for that. Find it on YouTube here

ImageLine's own 'documentation' of FL Studio's MCU implementation is here


Reaper


Screenshot for [ mnet ], [ ipMIDI ]

In Reaper's preferences go to the "Control Surfaces" page, click "Add" and select "Mackie Control Universal". Windows users may want to install the MCU_Klinke extension from stash.reaper.fm which overcomes some of the severe limitations with the built-in MCU support in Reaper (also see the 1.2. release notes and the manual on TouchDAW's main screen for this).

Next double-click the control surface entry and set the MIDI ports for the added controller.

Please make sure that the ports you select here are set to "disabled" under "Audio / MIDI Devices" in Reaper's preferences. According to user reports all sorts of strange things may happen when they are not!

When using the built in MCU support you should make sure that the "Map F1-F8 to goto markers" option is selected as TouchDAW will use those for navigation. The app will automatically detect which dll it is working with.

Latest versions of the MCU_Klinke plugin come with detailed documentation


Reason

Go to Edit / Preferences and select the "Keyboards and Control Surfaces" page from the upper dropdown. You can then let Reason / Record autodetect TouchDAW by clicking the "Auto-detect Surfaces" button (requires TouchDAW to already be running and connected to the network MIDI system in use) or manually add a MCU.

When autodetecting, MIDI ports will be set automatically, allthough it is possible that Reason only correctly sets the Input port. Click the Edit button to verify settings.

To set things up manually click "Add" then select "Mackie" from the manufacturers list and "Control" from the device list in the next window. Then set the MIDI ports TouchDAW is connected to. The picture on the left shows setup for a multicast connection made with ipMIDI. For RTP connections select the previously created RTP session's MIDI port for both in- and output as shown for some of the other DAWs above.

Finally make sure that the "Use with Reason" checkbox is selected for the controller representing TouchDAW.

Reason MCU documentation



Studio One

From the "Studio One" menu select "Options", go to the "External Devices" page and click the "Add" button. In the upcoming window open the "Mackie" folder from the list on the left, select "Control" and assign the MIDI in- and outputs to use. The screenshot on the left uses an RTP session defined in rtpMIDI. When using ipMIDI / multicast set "Receive From" to "1 Ethernet MIDI" and "Send To" to "2 Ethernet MIDI" ("Port 1 & 2" on OS X).

A .pdf documenting the extended MCU functionality in Studio One 2.6 can be found in the DAW's help menu, resp. on the Presonus website






Samplitude



From the "Options" menu select "Program Preferences / MIDI Options". In the upcoming window select "System Options / Hardware Controller" in the left hand column. Click "Add New" and select "Logic Control" from the dropdown menu.
Important: Do not select Mackie Control but Logic Control !
We have no idea what kind of a Mackie Control Magix own, but a lot of the buttons they refer to in their manual for that controller do not exist on the Mackie units we are aware of and a great part of the implementation described in the manual does not work anyway. Everything is fine with the Logic Control entry, though, so please stick with that.
What's left is selecting the appropriate MIDI ports. The picture shows a setup for RTP, if you wish to use multicast via ipMIDI set MIDI In to "1 Ethernet MIDI" and MIDI Out to "2 Ethernet MIDI". It is not necessary to customize the controller or change any other settings here. The only thing you need to be aware of is that Samplitude allows you to limit the number of tracks shown in its mixer view and this directly reflects upon how many tracks are accessible from a hardware controller. To adjust that to your needs click the "Setup" button in the upper right hand corner of the DAW's mixer window and set the number of tracks to show.

Samplitude's MCU implementation is documented in a pdf file named "Hardware Controllers" located at Program Files/Samplitude/Controlpanels, resp. in the main program folder with newer versions. Again make sure you refer to Logic Control here.

Notes:
In Samplitude versions before 12, level meters on control surfaces will always be too low. This is an implementation fault in the DAW and was fixed with v.12. Unfortunately the updated MCU implementation is rather ineffective in that it sends fully redundant text updates with almost every action and tends to lag overall.

SAWStudio



From the File menu, select "MIDI Control Template File / Open" and browse for "MidiCtrl_Mackie_Control.mct" (in SAWStudio/Configuration). Next select "MIDI Device Setup" from the "Options" menu and select the appropriate MIDI ports in the upcoming window: The screenshot on the left shows setup for rtpMIDI (the port name will be different according to how you named it), if you wish to use multicast via ipMIDI set MIDI Control Device In to "1 Ethernet MIDI" and MIDI Control Device Out to "2 Ethernet MIDI".
Next open the "Smpte/Midi" menu and make sure that both MIDI Control in and out are marked as active as shown on the upper right hand side. Finally save all this to your template file. That's it, however it should be noted that SAWStudio sometimes seems to take a restart to activate all this.

Documentation of SAWStudio's and SAC's MCU implementation can be found in the DAW's help files.

Digital Performer (7.2 and higher)



From the "Setup" menu select "Control Surface Setup". In the upcoming window select "Mackie Control" from both the "Driver" and "Unit" dropdowns, then select the appropriate MIDI ports. The screenshots above show setup for ipMIDI on the left and for RTP using Apple's Network MIDI driver on the right.
When running older versions of Digital Performer please refer to some hardware control surface's manual for general remote control setup and be aware that it will take some creative patching to get things going with network MIDI drivers.

Acid Pro / Vegas



On the preferences' MIDI tab make sure that the MIDI ports you plan to use are enabled for both in- and output. Then go to the "External Control / Automation" tab as shown in the screenshot above. From the "Available Devices" dropdown select "MackieControl" and see it appear in the listing (highlighted in red above). Double-click the entry and in the "Mackie Control Configuration" dialog that will come up set the desired MIDI ports. It should not be necessary to tune any assignments in the mapping fields of that dialog.
If your version of Acid / Vegas has an "External Control" entry in the options menu, enable it.

Two things to note with Acid / Vegas: Both programs will only be operatable from control surfaces when they have focus and will pull down all faders etc. when going out of focus. This even applies when some internal dialog grabs the focus from the main window.
Acid and Vegas allow for multiple tracks to be selected at a time. TouchDAW does not attempt to change that on the tablet display, but needs to reduce the selection to one track on phones. This has a certain failure potential and you may need to manually deselect tracks at times.

Find more details on Sony's Mackie implementation in Sony's MCU documentation





Tracktion

Go to Settings / MIDI IO and make sure that the MIDI ports you plan to use are enabled for both in- and output.



Next go to the "Control Surfaces" tab. Under "Supported Control Surfaces" select "Mackie Control Universal" and assign the desired MIDI ports in the lower part of the window.



Find more details on Tracktion's Mackie implementation in the T4 user manual (page 161 ff.) No more direct link available, expand the 'Related Guides' section.

Notes: Tracktion needs to be in focus (ie. be the active program) for many of its MCU related features to work.
The DAW does not send selection feedback, edit buttons will never be highlighted and the phone interface will not be able to follow selection changes made in the DAW or from other controllers.
MCU level meters seem to be broken in Tracktion 5.3 (works fine in Tracktion 4 and I'm pretty much sure it still worked in 5.2.4)


Bitwig

From the Options Menu select Preferences, then open the Controllers tab. If TouchDAW is already connected networkwise, you can let Bitwig autodetect the controller. There is a good 90% chance that the MIDI output port Bitwig will assign is not going to be correct though and will need manual adjustment. The input port that Bitwig got TouchDAW's query response from should be correct.
Alternatively you can manually select a Mackie Controller as shown in the screenshot below and adjust MIDI ports to your needs



Some brief info on Bitwig's Mackie implementation is available when you click the "?" button underneath the controller's name. Overall Bitwig's MCU implementation is still a bit immature with a lot of functions not accessible and quite a few functionless buttons, but that shouldn't surprise anybody with a 1.0 release. Bitwig also has a nice open javascript controller api, the MCU script is available in source and so can be changed.






humatic - htools Product names referred to in the manual are trademarks of their respective copyright owners. Humatic is not affiliated with any of them. Find a listing of mentioned trademarks here