Logic pro x remove control surface free -
Looking for:
Logic pro x remove control surface free - |
- One moment, please
When this happens, Logic checks if the new controller is one it has already registered. If it is, then it prepares to use it. If it was not previously registered, Logic will ask if you wish to use it as a controller. In theory this is all quite clever, and in practice it works 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 asked 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 do not address these, then Logic may exhibit erratic control surface operation, or worse, crash! Another problem happens when Logic has registered two or more controllers. Logic's control surface system is very powerful and supports the idea of controllers working independently or in "groups". For example you might have three 8 fader MIDI controllers that you wish to set up to control 24 mixer channels simultaneously.
If Logic has a compatible driver this is possible by assigning those three 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 deliberately, 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 if 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 control 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 Remote or gbXRemote, GarageBand asks you each time if you want to use that as a control 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 likely 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 new 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 exit 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 one, Logic will not save those changes until you exit the program. Should Logic experience an unusual "termination", like a crash, those changes will be lost. Incidentally Logic also uses the control surface preferences to save control surface "state". This is why you sometimes find the control surface set to a particular track bank, or plugin parameter page when it first starts.
Since Logic keeps the control surface preferences and state in memory, it raises the possibility that Logic could damage those settings due to an unrelated problem, such as a plugin crashing.
And while we cannot be certain this is actually the case, it appears 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 have noticed is Logic crashing for no apparent reason when quitting.
One important detail that is helpful when troubleshooting control surface problems is how Logic or GarageBand "knows" when an OSC control surface is available for use, and decides if it is one it already has registered or not. When it discovers a 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. For 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 time , Logic 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 giving it another thought. But if you want to use TouchOSC's Logic "template" sometimes, then you should consider changing to 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. Note that the ' apostrophe has been discarded. You might be thinking "So?
Many users will never experience issues using lpTouch, gbXRemote, or other control surfaces. New users who have never used another control surface are very unlikely to encounter these issues.
However it is possible if Logic somehow damaged the control surface preferences in the past and you never noticed it, until now. The most common instances where this could become an issue are: You use Logic Remote sometimes, and lpTouch others. You have used TouchOSC in the past, and your iPad has a name that causes the "naming differences" mentioned previously.
Since this is considered a different OSC controller because it does not run on the same iPad , Logic will attempt to have two controllers. You just upgraded your iPad to a new model and are using a different device name from the previous iPad. You have two iPads that you use interchangeably with Logic. Your Logic set up is used by another user who has her own iPad. If your situation is similar then it is recommended that you follow the steps described in the next sections.
The best strategy once you are aware of this problem, and have "fixed" your Logic control surface set up, is to avoid situations that can lead to it reoccurring. This is actually easy if you follow some basic rules, and users with a single iPad who only run lpTouch will probably never even encounter such a situation. Basically it all boils down to one principle: Never try to use another control surface along side lpTouch, and always make sure that Logic always has but a single control surface in its set up.
Simply disconnecting or not using the other control surface is not enough! Ideally, this should be a direct connection with the computer, rather than through a hub. Refer to the documentation provided by the manufacturer of your device. An installed driver if required by your control surface supported by the macOS version running on your computer. In a standard control surface configuration you can use a single control surface, or several. Each device can run independently or can be part of a control surface group comprised of multiple devices as described in Create control surface groups in Logic Pro.
Comments
Post a Comment