![]() ![]() Logic's control surface system is very powerful and supports the idea of controllers working independently or in "groups". If you do not address these, then Logic may exhibit erratic control surface operation, or worse, crash!Īnother problem happens when Logic has registered two or more controllers. ![]() 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. However there are some conditions in which Logic responds incorrectly to controllers, even ones it has already recognized. In theory this is all quite clever, and in practice it works most of the time. If it was not previously registered, Logic will ask if you wish to use it as a controller. When this happens, Logic checks if the new controller is one it has already registered. Logic is constantly monitoring its MIDI and OSC arena for changes that signal that a new control surface has been connected. This file is essential to proper control surface operation. It uses this information each time it starts to recall what control surfaces it has registered. Logic stores information about your current control surface configuration in a special, dedicated preference file. What this message is asking you is whether you wish for Logic to register and use this particular controller. When it uncovers one it has not registered before, it alerts you with a message like the one shown in the introduction. When it locates one it already knows about, it usually marks it as ready for use. Many controllers, including OSC-based ones like lpTouch, are automatically recognized by Logic.Įach time Logic starts, it scans for possible control surfaces. This is used to inform Logic what controller(s) you wish to use, and in the case of MIDI controllers, the MIDI ports to which the controller connects. Logic has a control surface set up utility that is accessible as part of its preferences. GarageBand 10 (the version currently in the Mac App Store) includes both of these drivers so gbXRemote also uses the TouchOSC driver. lpTouch was designed to work with a standard Logic Pro 9 or Logic Pro X installation so it is based on the TouchOSC driver. Controllers that use a different driver must install their own custom control surface driver. This was the only OSC control surface driver included with Logic until Logic Pro X introduced Apple’s proprietary Logic Remote driver. Logic Pro comes with many control surface drivers "out of the box", one of which was the "TouchOSC" driver introduced with Logic 9.1.2. Logic Pro has a control surface driver system that allows it to work with different controllers. But before we get to that some background may prove helpful to your troubleshooting efforts when something does go wrong. For this reason it is important to understand the nature of the problem and how to avoid it.įortunately there is a simple procedure to repair your Logic set up, and to avoid these problems in the future. You still may run into problems if you try to change control surfaces while GarageBand is running. This minimizes the chances of encountering the problem but does not eliminate it completely. It does not remember your control surface setting from the last time you used it. ![]() GarageBand 10 attempts to side step this issue because it takes a “clean slate” approach each time it starts. So if you are finding that using gbXRemote or Logic Remote with GarageBand 10 is not working as expected it may well be that you have run into this bug. Furthermore these same problems were inherited by GarageBand 10 as it uses the same OSC control surface system as Logic Pro X. These problems affect all OSC-based control surfaces (if you are running a version of Logic prior to 10.2.1), which includes Apple’s own Logic Remote app. (Note: Apple appears to have fixed this problem with Logic 10.2.1). 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.1.2. ![]() 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 "strangely"? 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?Īll of these are symptoms of incorrect, and possibly damaged, Logic control surface preferences. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |