Q: Will TouchDAW work with DAW X or DAW Y?
A: Yes if X and Y support Mackie controllers, at least not out of the box if they don't. Check your DAW's manual for MCU support.

Q: Do I need a WiFi router for this?
A: To run RTP or multicast over WiFi it is recommended, yes. There are other ways to create a network, though. See networking alternatives.

Q: Ok, but can I use the app without WiFi at all?
A: Yes, various forms of USB connectivity may be available depending on your device's system version etc. See the USB MIDI page.

Q: I got the DAW Controller working, but don't seem to receive any data from Keyboard and XY-controllers..?
A: The MIDI controllers use a separate connection that needs to be separately set up and routed in the DAW.
The DAW controller is a remote control device to the DAW and communicates bidirectionally on a MIDI port exclusively used for that purpose. Controllers on the other hand should feed MIDI to the DAW via regular track inputs

Q: I hear a piano playing / some noise being generated when I touch buttons or faders in TouchDAW. Thought this was a controller...?
A: You have a computer-side routing problem. Most likely the system's GM synth (or some VSTi or external soundmodule) receives MIDI on the port that TouchDAW sends to. The remote control protocols use of all kinds of MIDI messages, not just control changes. Make sure that the DAW control MIDI ports are exclusively used by the app and the DAW's remote control implementation.

Q: When I touch the keyboard or launchpads it activates the metronome, saves files, creates locators etc. WTF?
A: Looks like you too have a fault in your computer-side MIDI routing. MIDI notes sent to the input that the DAW uses for remote control may call Mackie Control functions. Make sure the app's second MIDI connection is only used for normal track input. Do not connect the app's second session to the RTP session used for the DAW controller.

Q: When I press stop, all faders jump to 50%. How buggy is this?
A: Another routing error. The remote control output port will also be in use in some place that the DAW sends controller resets to (like a MIDI or instrument track). Make sure the remote control ports are exclusively used for remote control.

Q: I usually start my DAW first, then when I launch and connect the app it starts playing on its own?
A: TouchDAW may start sending some commands on startup, but it's not exactly 'playing' anything here: When the app does not receive a parameter dump from the DAW right away, it will send some Mackie control commands to trigger a parameter update. A USB connected hardware control surface will usually be up and running when the DAW starts. This is not necessarily the case with an app and the DAW will eventually send its initial parameter dump into nowhere via the present virtual MIDI ports. So if TouchDAW comes online after the DAW is already running, it needs to somehow provoke a parameter dump. If you "hear" these notes, then you have a routing error, because they will only be sent via the DAW controller connection, which should be exclusively used for DAW control (see previous questions).

Q: I always get three channels grayed out on the mixer allthough all tracks are enabled in my DAW. Which ones are disabled seems to change randomly...?
A: That's the demo asking you to buy the full version. See the description for TouchDAW Demo on Google Play for a full listing of demo limitations.

Q: I changed phones / had to reset my device. How do I get TouchDAW back onto it without purchasing again?
A: Make sure you run under the account that made the purchase, open the Google Play app and select "My Apps" from the menu. You should then be able to download it again. If you experience problems with downloads, installs, refunds, payments or Google Play access, please contact Google Play help through the Google Play help center. As developers we have zero influence on how the Play Store manages your account and its purchases.

Q: I'm using RTP. Works fine, but I wonder if I really have to manually connect every time I start working?
A: Once you have the sessions in place and are familiar with the whole proceeding you may want to look at the paragraph titled "Connecting to a RTP session offered by the DAW machine" on the RTP manual page. Long as you're not affected by the device shortcommings mentioned there, the described method will make TouchDAW autoconnect the moment it is started.

Q: The app won't cover all the tracks in my project. None of the banking controls seem to work...?
A: You probably have multiple (Mackie) control surfaces in your configuration. The DAW will spread the mixer accross all of them and thinks that all of your channels are already accessible on a controller. Remove unneeded and potentially unconnected control surfaces from your configuration or see the next question.

Q: Is there a way to run TouchDAW in parallel with hardware MCU units without the mixer beeing spread accross the phone and the control surface?
A: That depends on the DAW's controller support. If it can work with HUI and MCU units in parallel you can either use the hardware controller in HUI mode or set TouchDAW to Pro Tools (HUI) mode. Alternatively: the mnet driver supports controller merging. Please have a look at the mnet manual.

Q: When I confirm or cancel a Pro Tools dialog notification after I have closed the dialog in the DAW, Pro Tools creates a new memory location. Can this be avoided?
A: Unfortunately Pro Tools does not send any MIDI in response to its dialogs being closed so TouchDAW has no way to know if the dialog is still up. You can use the phone's back button or click somewhere outside of the dialog to close the notification in TouchDAW without sending anything. TouchDAW 1.5 also has an option to suppress those notifications alltogether, but you will then not be able to confirm or cancel anything when away from the desk.

Q: I have some weird, hard to describe problem, is there a way to make the app provide some debugging info?
A: Go to Setup / Global / Miscellaneous and tick the "Enable Logging" box. Restart the app and try to reproduce the problem. Then go back to the logging option and disable it. TouchDAW should then ask for permission to email the log file. Please do not strip any attachments from the mail and if possible provide some extra info on the misbehavior you want to report.

Q: I can't get any sound out of this, also can't find anything like an import option...?
A: TouchDAW does not play or record audio. It's a remote control app for common sequencer software. Do not forget to leave a 1 star "No sound" comment in the Play store before uninstalling.


Error notifications

Notifications you may get confronted with and their meaning:

"XYZ did not respond to the invitation" - Something is preventing network traffic from reaching its destination. Check your firewall. Power-cycle or soft-reset your router. Leave and rejoin the network with the Android device.

"No response from DAW!" - In order to get a parameter update TouchDAW will start sending MIDI to the DAW once it gets informed that a connection with a network system has been made (RTP and Bluetooth only). Should the DAW not respond within a given time, a dialog with this message will be shown. It basically means that the communication loop between the app and the DAW is broken at some point. Possible reasons include:
- the DAW has not been started or not been set to use the ports TouchDAW is using for remote control.
- Some other routing error may prevent the app from receiving the DAW's responses or the DAW from receiving the MIDI TouchDAW sends (see previous topic).

"Unhandled Invitation from XYZ" - A second RTP peer tries to connect to TouchDAW while the app is already connected elsewhere. TouchDAW's local sessions only accept a single connection, the second connection attempt can not be handled. Apple's session establishment protocol does not allow for transmission of error codes, so the peer trying to connect will just time out after a while and receive a "...did not answer to the invitation" notice.

"Error opening MIDI ports. Bind failed EADDRINUSE... - This may happen if you still have the demo version running after downloading and starting the full version. The network ports are still in use by the demo. Shut it down (and best just uninstall it right away), then restart the full version.

"RTP / Bluetooth connection closed by server" - The remote side of an established connection shut down or closed the particular session.

"DNS Socket Error..." - Network problems on the Android device, probably the WIFI connection got lost.

"WiFi Connection Lost!" - This is a notification from the system, indicating that your WiFi is not in best shape. TouchDAW does not fiddle with a device's basic network setup and does not attempt to create, start or close networks. If you see this notification your device is having serious trouble maintaining its network subscription.

Some possible trouble sources and ways to address them.

Network connection problems

Should you have problems to get a MIDI connection going because the Android device and the computer running the DAW don't seem to see each other on the network, you may need to tune your PC firewall. Temporarily switch the firewall off. If that cures the problem, reactivate it and open the following ports for local area UDP traffic: 5004-5007, 5353 and 21928 - 21930. (Of course you should also reactivate the firewall if the problem remains)

Frequent packet loss. Stuck / missing notes. Connections only working one way. Sessions not connecting.

Soft reset or power cycle the WiFi router, leave and rejoin the network with the Android device.

Also see network setup tips for more info on using your WiFi for MIDI.

Some controls seemingly not functional

Make sure that the controlled DAW is in the foreground and has keyboard focus. This is the kind of booby trap that one falls into pretty easily and has cost me a significant amount of nerves during development to date. Especially the DAWs from the most advanced of worlds will not react upon numerous MIDI commands when not in focus.

Sync loss between TouchDAW and the DAW

If you at some point are under the impression that you are not getting the correct names displayed for selected channels or editor parameters, it may be that a parameter update or a specific command that TouchDAW uses to initialize copying of names or values got lost on the air or through heavy unforeseeable parellel activity on the phone (an incoming call for example). This can and sooner or later will happen. Operations that should trigger a retransmission of tracknames and parameters include:
  • moving the currently accessible block of eight channels. Wipe over the fader view above the navigation cross to switch to the next eight channels, then wipe back to recall the block you were working on.
  • changing editor pages. Especially switching to and from the Pan page usually makes DAWs refresh track parameters.
  • flipping a channel, preferably in pan editing mode, does the same.

Temporarily lagging or overall sluggish Bluetooth performance:

On some Android devices Bluetooth performance may improve significantly when you turn off WIFI. This is not limited to low end phones!

Performance problems

In situations where TouchDAW needs to do very frequent refreshes of lots of parts of the screen, like when the phone follows sequences with heavy automation use, the selected channel is very dynamic in level, timecode is running etc. you may see performance degrate and experience things from values only changing slowly when spinning endless encoders to data being lost on the wire. While this is primarily an issue on devices with low processing power, there is a general relation between what happens on the main GUI thread and lower level things.
Here's some things you can do to reduce drawing needs:
Lower the timecode display rate, using horizontal wipes on timecode displays to shorten it.
Toggle name / value display to name (insted of constantly changing values) by touching the textfield right on top of the fader.
Make use of eventual options in your DAW to reject sending of audio levels etc.