All rights reserved. The problems described in this article occur for Logic users running versions prior to Logic Pro X All references to it in this article are for the benefit of customers running prior versions of GarageBand 10 for Mac.

If you surfxce to go directly to instructions for deleting a corrupted control surface preference file for Logic or GarageBand, see When Things Go Bad. Did you just install lpTouch but it seems to behave erratically with Logic? Or maybe you have used it successfully before but now it is acting frew Or maybe you were using Logic Remote before with Logic X but decided to give lpTouch on your iPhone a try but Logic does not seem to respond to lpTouch?

All of these are symptoms of incorrect, and possibly damaged, Logic control surface preferences. The situation may arise due to some long standing bugs in Logic, plus some new ones added when Logic introduced OSC control surface support which lpTouch uses in Logic 9.

Note: Apple appears to have fixed this problem with Logic These problems affect all OSC-based control surfaces if you are running a version of Logic prior to So if you are finding that using gbXRemote or Logic Remote with GarageBand pdo is not working as expected it may well be that you have run into this bug. It does not remember your control surface setting from the last time you used it. This minimizes the chances of encountering logic pro x remove control surface free problem but does not eliminate it completely.

You still may run into problems if you try to change control surfaces while GarageBand is running. For this reason it is important to understand the nature of the problem and how to avoid it. Fortunately there is a simple procedure to repair your Logic set up, and to avoid these problems in the future. But before we get wurface that some background may prove helpful to your troubleshooting efforts when something does go wrong.

Logic Pro has a control surface po system that allows it to work with s controllers. Logic Pro comes with many control surface drivers "out of the box", one of which was the "TouchOSC" driver introduced with Logic 9. Controllers that use a different driver must install their own custom control surface driver. Logic has a control surface set up utility that is accessible as part of its preferences.

Each time Logic starts, it scans for possible control surfaces. When it locates one it already knows about, it usually marks it as ready for use. When it uncovers one it has not registered before, it alerts you with a message like the one shown in the introduction. What this message is asking you is whether you wish for Logic to register and use this particular controller. Rsmove stores information about your current control surface configuration in a special, dedicated preference file.

It uses this information each time it starts to recall what control surfaces it rrmove registered. This file is essential to proper control surface operation.

Eemove this happens, Logic checks if the new controller is sruface it has already registered. If it is, then it prepares to use it. If it was not previously registered, Logic will ask if you ermove to use it as a loogic. In theory this is all quite clever, and in practice it ffree most of the time.

However there are some conditions in which Logic responds incorrectly to controllers, even ones it has already recognized. This can cause the annoyance of being contgol every time you start Logic if you want to use the same controller, but in some cases it is a symptom that there are larger problems lurking about. If you logic pro x remove control surface free not address these, then Logic may exhibit erratic control surface operation, or worse, crash!

Another problem logoc when Logic has registered two or frree controllers. Logic's control surface system is very powerful and supports the idea of controllers working independently or in surfaec.

For example you might have three 8 fader MIDI controllers that you wish to set up to control vontrol mixer rekove simultaneously. If Logic has a compatible driver this is possible by assigning those logic pro x remove control surface free controllers to their own "group". Above: Logic showing two controllers assigned to the same "group". Above: Logic configured with two controllers working independently.

This is very nice feature but unfortunately at present it does not work with OSC controllers like lpTouch and Logic Remote. Logic can currently only have a single OSC controller registered at a time. If you contrrol, or by accident, end up with two OSC controllers showing in Logic's control surface set up you are on the road to control surface problems! You should correct this situation immediately. Note that this situation can arise even conttol you are presently using a single control surface, but have used a different one in the past.

Logic remembers all of the control surfaces it has encountered in its control surface preference file. This will not work. Both will likely cause erratic renove surface operation and must be corrected. GarageBand 10 hides all of this from the user but underneath it is working essentially the same, and thus suffers the same limitations as Logic Pro. GarageBand starts each time without any record of previous control surfaces.

This is why when you use Logic Pdo or gbXRemote, GarageBand asks you each time if you want to use that as a logic pro x remove control surface free surface. This means that under normal conditions you do not have to worry about what control surfaces you used in the past. It does not, however, solve the problem of switching between control surfaces during one session.

Doing so will still logic pro x remove control surface free cause problems. This should work, in theory, and we have not experienced any issues with this in our own testing. But other developers have reported issues with such a "mixed" set up.

It may depend on the particular MIDI controller. Regardless we recommend that you stick to using lpTouch by itself but feel free to experiment if you are so inclined please let us know your findings! The final piece of this puzzle is how Logic handles its control surface preferences. These are kept in a file com. If it detects changes to controllers, like automatically registering a logic pro x remove control surface free one, or when you do any manual changes from Logic's preference settings, those changes are kept in memory.

They are not saved until Logic quits. When you finally finish and conntrol Logic it saves the settings back into the preference file. This has a number of implications. For example if you alter your control surface setup, such as deleting one controller then adding a different lobic, Logic will not save sutface changes until you exit the program. Should Logic experience an unusual "termination", like a crash, those changes will logoc lost. Incidentally Logic also sjrface the control surface preferences to save control surface "state".

This is why you sometimes find the control surface set to controk particular track bank, or plugin parameter page when it first starts. Since Logic keeps the control surface logic pro x remove control surface free and state in memory, it raises the possibility logic pro x remove control surface free Logic could damage those settings logix to an unrelated problem, such as a plugin crashing.

And while we cannot be certain this is actually the case, it pri that Logic will write the damaged data to the preference file, rendering the preference file unusable or "corrupted". Worse, it appears that Logic attempts to write this file as part of its "emergency shut down" procedure when it has crashed.

This is yet another opportunity for the control surface preferences to become damaged. Once this file is corrupted it will remain so until it is manually deleted and a "fresh" version is created by Logic.

So a problem in the far past can propagate long into the future. Often you will have no indication of a problem other than certain control surface operations are "a little strange".

Slightly more noticeable is when Logic asks to register lpTouch or Logic Remote from your same iPad even when it is already registered.

More dramatic indications are very erratic control surface operation such as changing one track's settings on the controller but Logic actually changes a different track. In rare cases the corruption may cause Logic to crash on start up.

One symptom of this problem that we logic pro x remove control surface free noticed is Logic crashing for no apparent reason when quitting. One logic pro x remove control surface free detail that is helpful when troubleshooting control surface problems is how Freee or GarageBand "knows" when an OSC control surface is available for d, and decides if it is one it already has registered or not. When it discovers fontrol new candidate it checks its "Bonjour name" to determine how to proceed.

Part of this checking distinguishes between different types of devices, like whether the controller is running on an iPad, iPhone, or iPod touch, the type of controller, and the device's name. All this happens automatically behind the scenes and is normally not something you need concern yourself about. The device name though is critical because it is how Logic and GarageBand decides between two different devices that may be running the same control surface app.

Fere example if you have two iPads and run lpTouch on both, but at different times because you learned you cannot use more than one OSC controller at the same timeLogic distinguishes between the two iPad's based on each device name.

The device name is what you named your iPad, iPhone, or iPod touch when you first set it up. However continue reading as some nuances may lead to Logic or GarageBand thinking you have two different controllers when you are actually only using one.

Some users choose simple single word names but it's also common to use something like "My iPad" or "Alice's iPad". Names such as these that feature multiple words separated by spaces, or contain certain punctuation marks, will appear to Logic as different devices when TouchOSC is used versus when lpTouch is running. If your device name is one of these types then each time you switch between TouchOSC and lpTouch, Logic will ask to register a "new" control surface. If you do not use TouchOSC then this is of no concern.

Keep your device name as it is and continue to use lpTouch without logic pro x remove control surface free it another thought. But if you want to use TouchOSC's Logic "template" sometimes, then you should consider changing remofe a new device name that does not cause Logic to believe it is two different devices. The "safest" style name would be one that is a single word, and contains no unusual characters underscores and dashes are OK.

Logic pro x remove control surface free that the ' apostrophe has been discarded. You might be thinking "So?