lpTouch FAQ’s

No. lpTouch is a "remote control" for Logic on your Mac. It gives you the ability to perform common Logic operations using the iPad's touch screen instead of your Mac's usual mouse and keyboard. It does not replace your mouse and keyboard. Rather lpTouch supplements your normal way of interacting with Logic.

lpTouch is also a type of "control surface" for Logic. Professional music production applications include support for a variety of hardware devices that provide direct control over the application's mixer faders and buttons to control playback, recording, muting, and other common recording functions. Logic supports devices and apps that use Open Sound Control (OSC), which lpTouch employs to communicate with Logic.
Hardly anything! Just lpTouch on your iPad or iPhone or iPhone touch (running iOS 5.1 or higher), Logic Pro 9.1.6 or higher on your Mac, and a working Wi-Fi connection between your Mac and iDevice. lpTouch is compatible with Logic's built-in TouchOSC control surface driver so no other apps, plug-ins or agent programs are needed.
Logic versions prior to 9.1.6 had some bugs that affect OSC devices. As to Logic Express, 9.1.6 or higher is supposed to offer similar control surface support as Logic Pro but we have not verified this with our own testing. It is for this reason that we do not currently support it.

lpTouch works with Logic Pro X, but please read "lpTouch and Logic Pro X" on the lpTouch Requirements & Setup page for information on minor issues and ways to handle them. It is also important that if you are using Logic Pro X or higher, that you first go to the iPad/iPhone Settings app, select 'lptouch', select 'Logic version', and set to 'Current'.
You must establish a connection between lpTouch and Logic the first time you use it. First, make sure Logic is running. Open lpTouch, click on the info button, then press 'Connect'. The next screen will show the computers where you are running Logic (typically only one). Click on that bar and a checkmark will show. Exit the info screen.

On the Logic screen, a popup message says that it has detected a new OSC device and asks if you want to add it to the setup - click the 'Add' button. After a few moments, the lpTouch screen should populate with your song data.
The info button pulses red when it is unsuccessful connecting to Logic. This could be because the computer it last connected to is no longer on the Wi-Fi network, or Logic may not be running. It may also involve general Wi-Fi network problems. Try reconnecting as you did the first time. Read #2 in the Troubleshooting chapter of the user manual for tips on Wi-Fi issues and remedies.
Depends. If you are running Logic Pro X 10.2.1 or higher, then click OK. This typically occurs the first time you use lpTouch and Logic needs to add your iPad, iPhone, or iPod touch with lpTouch to its list of recognized OSC devices. If you have previously used Logic with lpTouch or TouchOsc, then you have to perform one additional step. See this for further information.

If you are running a version of Logic prior to 10.2.1 AND you have not or are not running any other OSC apps/controller devices with Logic, then click Add or OK.

However, if you are running a version of Logic prior to 10.2.1 AND you have been running OSC apps on other devices with Logic, then do not click Add/OK until you do the 6 steps shown in FAQ #9. Logic considers lpTouch on an iPad to be a different OSC controller than lpTouch on an iPhone and vice versa, so you need to do these steps when switching between the two. This is true for any OSC based app/device. Logic prior to version 10.2.1 has some issues when multiple OSC devices have or are attempting to advertise their services.
Yes if you are running Logic 10.2.1 or higher! Logic Pro X 10.2.1 seems to have removed a limitation that restricted use to a single device at any time. See this for further information on how to set up multiple devices.

Unfortunately no if running a previous Logic version. Logic prior to 10.2.1 does not handle multiple OSC based devices at the same time. It considers each iDevice running lpTouch as a different OSC control surface. The same is true for other OSC devices you may want to use with Logic.
(Note: This situation/problem appears to have been resolved when running Logic Pro X 10.2.1 or higher. See this for further information.)

When you run TouchOSC on an iPhone or iPod touch, Logic uses different control surface settings than when lpTouch is used. Logic will ask you to add your iDevice twice, once when you run TouchOSC, and once when you run lpTouch. If you clicked "Add" each time then you end up with Logic having two OSC control surfaces registered, but to the same device. This situation works very erratically under the best of cases but in this particular case the most likely result is that lpTouch is completely unresponsive and does not receive valid data from Logic.

On the other hand if you did not click "Add" for the second popup then Logic is using the wrong settings. For example, if you first ran TouchOSC, then run lpTouch, but do not add your iDevice a second time, then Logic uses the wrong settings for lpTouch. When you run TouchOSC though it works properly. Likewise if you first ran lpTouch, and then switched to TouchOSC, then TouchOSC works improperly.

The solution in all cases is that you must remove the previous OSC device setting from Logic's control surface setup before you switch to the other app. Furthermore you must exit Logic after removing the first, then restart Logic. Otherwise Logic may operate the new control surface in an unreliable fashion. See #9 for more information about managing Logic's OSC control surface setup.
Perform these steps:
  • 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
  • If you are running Logic Pro X 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
In some situations, performing the above steps is not enough as Logic may have corrupted its control surface settings file. If you continue to suffer incorrect or erratic operation after changing control surface settings you may need to delete these preferences. Please read Logic and GarageBand 10 Control Surface Problems for instructions and discussion.
(Note: Logic Pro X 10.2.1 (or higher) seems to have lessened the chance of this problem occurring, provided you follow the recommendations here. If you should experience improper operation on Logic Pro X 10.2.1 (or higher), you may want to try the suggested remedy below.)

This can happen if you have had another OSC controller device working with Logic in the past or currently, and have added lpTouch to Logic's setup of recognized OSC devices. Logic has issues with multiple OSC devices advertising their services concurrently. Go to /Control Surfaces/Setup from the Logic Pro X menu or Logic Preferences/Control Surfaces/Setup (Logic 9) and check to make sure that only your iPad, iPhone, or iPod touch is graphically shown as an OSC device. If there are 2 or more graphics side-by-side (or vertically), then you must remove all of these control surfaces from Logic's setup (see earlier FAQ) and start over with the lpTouch connection process. If things are really out-of-sorts, you will also need to delete the Logic control surface preference file (read “When Thngs Go Bad - if using Logic” in Logic & GarageBand 10 Control Surface Problems.
No. For any of the value displays, lpTouch displays what it receives from Logic. The timecode "off-by-1" situation appears to be a rounding difference that arises in Logic's control surface calculations. In these types of situations, the value differences are all minor. If you do see that the values between lpTouch and Logic appear totally out-of-sync, either restart lpTouch, or go to the info button, press on 'Connect to Logic', then the name of your computer. Reconnection causes a refresh & will sometimes get things back to normal. See the Troubleshooting guide of the user manual if you are having problems.
One of those mysteries of Logic. If you want to see the EQ popup on your computer after changing to a new track (it's not really necessary because the lpTouch EQ screen virtually replicates it with much easier to use controls), just click on a different tab on lpTouch, then click on the EQ tab again and the popup will be back on the computer display.
After Logic closes a project it seems to retain the song data in memory. You can even press "Play" on lpTouch and hear the song! However any changes you make from lpTouch, like adjusting a track's volume, only affect this "ghost song" and in no way affect the saved project.
This seems to be a bug with how that particular plugin reports its "GUI" changes to Logic. Since all control surfaces, including lpTouch, depend on the information Logic sends it, this appears to be a control surface issue but it's actually a problem with the plugin and/or Logic. In this particular case when you use the Tape Delay's "mix" control on lpTouch you can get lpTouch "back in sync" by selecting a different screen (say EQ) and then return to Channel Strip.
While lpTouch works fine with TouchOSC also on the same iPad, if you want to switch between the two, you will need to reconnect TouchOSC any time you want to use it. Do this by going to the TouchOSC info screen, tap the Enable bar to OFF, wait a few seconds, set it back to ON, and tap on your host computer. It should then work as usual.

If you are using an iPhone or iPod touch the situation is different, and depends on which version of Logic you use. Prior to version 10.2.1, you must remove your iDevice from Logic’s control surface setup (see FAQ #9) if you switch between TouchOSC and lpTouch. If you use Logic Pro X 10.2.1 or later then you should be able to switch between the two, provided you manually modify the control surface set up so that each controller is in its own group. See this for further information.
These symptoms will occur if you have Bluetooth enabled on your iPad during an lpTouch session. Go to the Settings application on the iPad, click on "General", and set Bluetooth to OFF. When your lpTouch session is over, you can turn Bluetooth back on if you wish.
This box should be left unchecked so Logic can look for new control surfaces in the future. To undo a checked box:

If using Logic 9: go to the "Logic Pro" menu and select "Preferences/Control Surfaces/Setup...". You will see the control surface setup window. Click on "New" and select "Automatic Installation". This will reinstate Logic's ability to look for new control surfaces automatically.

If using Logic X: As of Logic 10.1.1, there is a bug that keeps you from changing this back. You could delete Logic’s preferences, but this is not recommended. Instead, you can use OSX’s Terminal program, you must be very careful. If you are not experienced using Terminal, ask someone for help. You would also be wise to do a full backup!

Now that you have been warned, here are the steps:
1. Quit Logic X if it is running.
2. Start Terminal. You can find it with Spotlight, or you can find it in /Applications/Utilities.
3. At the Terminal prompt, type this exactly:
defaults delete com.apple.logic10 SuppressedAlerts
4. Press the RETURN key (if you have not done so already).
5. Quit Terminal. Logic should be back to properly popping up the alert.
BlueTooth network connections are not currently supported. The reasons are numerous for why this facility is not supported but the primary reasons are 1) iOS has very restricted use for BlueTooth networking, mainly for support of GameCenter; 2) Network performance is too limited to support responsive controllers.

This second reason is significant. BlueTooth offers only a fraction of the data throughput that Wi-Fi offers and in many uses it suffers from latency. This causes controller actions to seem sluggish and unresponsive. BlueTooth also suffers from limited connection range.
Only if you are using Logic Pro X version 10.2.1 or greater. Previous versions of Logic Pro X did not work properly if two OSC controllers were registered in Logic Pro’s control surface set up. Logic Pro X 10.2.1 appears to have addressed this limitation. See this blog post for additional information.
Only if you are using Logic Pro X version 10.2.1 or greater. Previous versions of Logic Pro X did not work properly if two OSC controllers were registered in Logic Pro’s control surface set up. Logic Pro X 10.2.1 appears to have addressed this limitation. See this blog post for additional information.