lpTouch Requirements & Setup

Do You Use Multiple OSC Controller Apps With Logic?

If you are running a version of Logic Pro prior to 10.2.1:
Please read the “Using Multiple OSC iDevices/Apps with Logic Pro“ section below before you try to setup lpTouch.

If you are running Logic Pro X 10.2.1 or higher:
Logic Pro X 10.2.1 (and higher) appears to have resolved the problem that was happening when using multiple OSC controllers, provided you follow the recommendations here.

Requirements & Setup

Requirements

  • iPad, iPad mini, iPhone or iPod touch running iOS 5.1 or greater
  • Apple Logic Pro 9.1.6 (or higher) DAW software application installed on your Mac. Compatible with Logic Pro X and higher with some minor exceptions. Read "lpTouch and Logic Pro X" below for more information.
  • Wi-Fi access to same computer where Logic is installed
  • iPad/iPhone Bluetooth must be set to OFF during an lpTouch session to ensure reliable communications with Logic

Setup

  • Open Logic Pro/Logic Pro X on your Mac and the song you want to work on.
  • Make sure your iDevice's Wi-Fi is On and set to the same network as the Mac running Logic. Also confirm that Bluetooth is OFF on your iDevice. Both of these are found in the iOS Settings application.
  • Start up lpTouch.
  • The FIRST TIME you use lpTouch you must establish the connection between Logic and lpTouch. Tap on the info button (top right of lpTouch screen). It should be pulsing red.
  • Tap on the "Connect" text/bar.
  • Tap on the name of the computer where Logic is running. Exit the info screen.
  • On the Logic computer screen, you will see a message stating that a new OSC device wants to connect or has been recognized. Click on “OK” (Logic Pro X) or ”Add" (Logic Pro 9).
  • After a few moments, the info button will stop flashing and the lpTouch screen should populate with song data. If it does not, tap on the arrow keys to move the tracks or double tap on the current tab or move through the tabs at top and return to the Main screen.

Using Multiple OSC iDevices/Apps With Logic Pro

If you plan to use lpTouch on both the iPad and iPhone or iPod touch, or have already been using Logic with other OSC controllers like Logic Remote or TouchOSC, you will need to do a few additional steps - listed below - if you want to switch back and forth between different apps. Tap the orange button if you want more in-depth information about this issue.

These steps must be done if you are running a version of Logic Pro prior to 10.2.1 and want to switch between multiple OSC apps. (It appears that this problem does not occur with Logic Pro X 10.2.1 if you follow these guidelines.) However, if you do experience erratic behavior, the remedy below may get things working correctly.

Logic's inability to reliably handle multiple OSC control surfaces (prior to Logic 10.2.1) makes it challenging to use multiple OSC controller apps side-by-side. To switch from using one OSC controller app to another, you must do these steps every time:

  • Exit Logic if it is already running. Also make sure that no OSC controller is running, including lpTouch
  • Start Logic
  • If you are running Logic Pro 9 then select the following menu item from the Logic Pro menu: Preferences/Control Surfaces/Setup OR If you are running Logic Pro X or higher then select /Control Surfaces/Setup from the Logic Pro X menu
  • Locate any OSC controllers that show in the window, select each and press the DELETE key
  • Confirm the deletions
  • Exit Logic. You must quit Logic before the changes are saved
Logic also can corrupt its control surface preferences when it has two or more OSC controllers assigned. When this happens, Logic will behave erratically with your OSC controller apps.

If you suspect your control surface preferences are corrupt, or you just want to absolutely make sure you are starting with a clean slate, then you should follow this procedure to delete the existing control surfaces preferences settings file. Logic will create a new version of this file the next time it exits. Unfortunately if you have a corrupted file and that file contains your favorite control surface customizations that you laboriously slaved to create, those will be lost. This is one reason why a backup after making such additions is essential.

  • Exit Logic and make sure your OSC controller apps are not running. If you fail to do this Logic will overwrite the new "clean" file with whatever it thinks are the current control surface settings, negating your efforts.
  • If you are running on Snow Leopard, use the Finder to navigate to [your home folder]/Library/Preferences
  • If running on Lion and later, open the Finder, tap Go in the menu, then "Go to Folder…”. Type ~/Library/Preferences in the box, then tap Go.
  • Locate the file com.apple.logic.pro.cs, then drag it to the trash. Empty the trash to make sure it stays deleted.

lpTouch and Logic Pro X

Logic Pro X has some differences from Logic Pro 9 that require some manual workarounds to achieve consistency with lpTouch, primarily related to lpTouch's Aux channel faders.

On the iPad, lpTouch's Main-Volume screen two faders on the right are defined by Logic's original OSC control surface driver to show Logic's first AUX channel and the Master volume control. (On the iPhone, these are on the Master Aux screen). Prior to Logic Pro X, a typical project (including most templates) assigned a "send effect", like reverb, to the first AUX channel. This made it convenient to adjust the overall effect level using lpTouch. Likewise, Logic's original OSC driver assigns the two right side faders on lpTouch's Pan-Sends screen to AUX 2 and AUX 3 levels. Again, prior to Logic Pro X it was typical to assign send effects to AUX 2 and AUX 3.

Logic Pro X makes extensive use of AUX channels to implement the new Track Stack feature, and Logic Pro X's instrument and channel strip "patches" also can include AUX channels. If these are added first to a project, then those will use AUX 1-3 and lpTouch will display whatever those stacks or patches have assigned to those AUX channels. This may or may not be what you wanted. And since the project starter templates have a number of instruments and channel strips already in place, AUX 1-3 will probably already be assigned before you open the new project.

lpTouch logic X 1
New Logic Pro X project with single Drummer track named "SoCal". Note that an AUX track "Small…Four" was automatically added.
lpTouch Logic X 2
lpTouch shows the "Small…Four" (name condensed to SMRM/0.6cD) auxiliary channel in its "AUX 1" position, second fader from right.

If you want to retain a consistent assignment to lpTouch's auxiliary faders, then AUX 1-3 need to be added to the project and assigned to their task (like reverb) before any "patches" are added. The easiest way to insure this is to alter your starter templates accordingly. If you regularly use Logic's built-in starter templates, consider creating personal versions by modifying the built-in ones you use.

lpTouch Logic X 3
If you then add another software instrument that is a "stack track", like "Grand Piano and Strings" as shown here, two more AUX channels have been added as part of the instrument's "patch".
lpTouch Logic X 4
Since Logic has assigned those to AUX 2 and AUX 3, lpTouch's AUX 2 and 3 faders on the Pan-Sends screen controls those.

The same project but starting first by adding three AUX channels: "reverb", "EFX1", and "EFX2". The drummer and piano software instruments were then added. Since the three AUX channels were pre-assigned, subsequent track additions (or deletions) will not cause Logic to display different AUX channels on lpTouch. It is recommended that you save a template project with your typical AUX channels assigned in this manner.

lpTouch Logic X 5
lpTouch Logic X 6

Situations may occur where Logic Pro X either fails to update the function of lpTouch's three auxiliary faders, or updates them with the incorrect assignment. It can also assign the wrong channel to the lpTouch Master fader (far right fader on Main-Volume screen). Whether this is intentional or a Logic Pro X flaw is unclear, but it is different behavior from Logic Pro 9. We have, however, had good results by "refreshing" lpTouch's screen by either momentarily switching to a different screen (say from Pan-Sends to Channel Strip and back). Alternatively, changing some aspect of the channel in question in Logic Pro X, like toggling the AUX from stereo to mono input and back will also cause a refresh.

lpTouch Logic X 7

Logic incorrectly updating lpTouch after a channel deletion from Logic's mixer - Aux 1 channel fader shows "Click".

lpTouch Logic X 8

Display corrected after "refreshing" by selecting lpTouch's EQ screen tab and then back to the Main-Volume. Changing tabs or channel settings in Logic's mixer will often cause Logic to send the proper information.