Looking for:
- Logic, GarageBand 10 Control Surface Problems
- Logic pro x control surface preferences free
If you have multiple control surface logic pro x control surface preferences free in your system, you can define how they relate to each. You can use the Page keys to display further send. These buttons labeled A to H have multiple uses depending on
eplan electric p8 download current mode, as indicated. The choices are: Angle: Encoders adjust surround angle. Pressing a V-Pot confirms the preselected send destination and sets the other send parameters. Channel view: Displays, and allows you to edit, multiple parameters for a single channel. I do this with my XR18 all the time - so handy.
Logic pro x control surface preferences free
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! Logic must not show it in its control surface set up screen. For example, if you are currently using another controller, or have in the past, then you want to make sure that Logic's control surface setup screen looks like the screen below before you run lpTouch for the first time.
It's always best to start with a clean control surface set up before installing any OSC controller! If you should forget this and Logic shows the "New OSC device" popup like when running lpTouch for the first time , simply click "Cancel". Open up Logic's control surface set up from the Preferences menu item , delete the other control surface s , and then reconnect lpTouch to Logic, this time answering "Add" to the popup.
By the way never "check" the 'Don't show again' option. Also, remember that Logic will not save these changes until you exit. Once you have your control surface set up completed, we recommend you exit Logic so that the changes are saved.
Furthermore it is a good idea to save the preference file in a safe place if you have further customized your control surface set up. Or consider the method suggested in ' For the paranoid '. If you try to delete one or more control surfaces from Logic's set up screen this will likely cause a crash.
GarageBand 10 users have a bit simpler situation since GarageBand starts each time with no registered control surfaces. If you wish to change between say Logic Remote and gbXRemote, or just want to use a different iDevice, you should save your project and exit GarageBand. Obviously this is not an ideal situation but it is the only way to avoid problems until Logic and GarageBand safely support multiple OSC control surfaces at the same time.
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. Locate the file com. Empty the trash to make sure it stays deleted. If you want to use multiple OSC controllers, you may need to perform these steps if you notice problems: Exit GarageBand if it is running.
Locate the one named: com. One way to buy an extra measure of protection against future mishaps has been suggested by "seasoned" Logic users in online forums.
The idea is that since Logic can only damage the control surface preferences by writing to the file, it's best to keep Logic from doing this.
Obviously this is not how Logic was intended to work but "locking" the file does not seem to cause any adverse problems. Just remember that once the file is locked Logic cannot make any changes to it, including any customizations you perform, if you wish to replace your control surface, or even save the control surface "state".
You will need to reverse this procedure to make changes. Note: we have not thoroughly tested this procedure so please consider this "experimental" and only use it if you really feel the need and are willing to address any unforeseen side effects. The procedure is simple. Locate the control surface file and have the Finder "lock" it to prevent changes. Use the method outlined in ' When things go really bad ' above to locate the file.
Right click on the file and select "Get Info". You should see a popup like this:. When you want to allow changes follow the same steps and "uncheck" Locked.
Another alternative for an advanced user is to create an Automator script that deletes the control surface preferences each time before it launches Logic Pro. Then instead of running Logic directly you run the script each time to start Logic. This insures that Logic always starts with an empty control surface preference file. This is essentially what GarageBand 10 does.
Display as a link instead. Clear editor. Upload or insert images from URL. By mq93 , 12 hours ago in Logic Pro. By joshj , 2 hours ago in Logic Pro.
By Ananna , 3 hours ago in Logic Pro. Click here! Share More sharing options Followers 0. Reply to this topic Start new topic. Recommended Posts. Posted March 19, edited. Edited March 20, by sectiond. Mac pro 2. Link to comment Share on other sites More sharing options David Nahmani Posted March 20, Posted March 20, No problem. Both the white and the light blue bands in your track list should disappear. Now deselect the same Bypass All Control Surfaces.
Only the white bands should return? Make sure you're looking in the correct library, you have to hold Option as you click Go etc?
- Apple Logic Pro X - Control Surfaces Support - Logic Pro X - Control Surfaces Support
The Behringer X-Touch is a 'very close to exact' clone of a Mackie Control Logic Control so working with it in Logic is well documented and does a lot of really useful things. You might be happier buying another Element 88 or two and using a control surface that just plays fantastically well with Logic. Enough inputs and outputs to accomplish most things. I do this with my XR18 all the time - so handy. It's an interesting concept.
I have not found a way to use the audio device controls in Logic except in the Logic interface. Actually, I found this YouTube Which explains how to control all the faders and more I think the Behringer may have a similar solution But still curious about using outboard preamps in combo with the internal Much thanks The PreSonus video explains which buttons to press, and not a whole lot about how it actually "behaves".
At the minimum some kind of overlay would be required since the placement is kind of strangely spread out. The X32 suffers from the same problem as the PreSonus I guess it really depends on just how many faders are needed. A nice help in this mode is my iPad which I put on the desk. I turn and face my X-Touch, iPad to my right hand 8 more faders and a wireless keyboard at the base of the X-Touch. The keyboard has a Logic Pro overlay on it, so I can do lots of things right there. The mixer can be extended with digital snakes - 8, 16, or 32 inputs.
If you need better than 48K samples then you would have to skip the Behringer gear. Also to not forget are the 8 effects units in the mixer as well as eq and compression for every channel independently. Some pretty nice gear on the way in to Logic should you want to do that Too many options Control Surface.
I bought an Allen and Heath Q 32 mixer for a remote recording that I was doing for a church choir. After I finished the project, I integrated the Q32 into my studio. It took a while for me to get it to work, but I got Logic to respond to all 32 faders. 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! Logic must not show it in its control surface set up screen. For example, if you are currently using another controller, or have in the past, then you want to make sure that Logic's control surface setup screen looks like the screen below before you run lpTouch for the first time.
It's always best to start with a clean control surface set up before installing any OSC controller! If you should forget this and Logic shows the "New OSC device" popup like when running lpTouch for the first time , simply click "Cancel".
Open up Logic's control surface set up from the Preferences menu item , delete the other control surface s , and then reconnect lpTouch to Logic, this time answering "Add" to the popup.
By the way never "check" the 'Don't show again' option. Also, remember that Logic will not save these changes until you exit. Once you have your control surface set up completed, we recommend you exit Logic so that the changes are saved. Furthermore it is a good idea to save the preference file in a safe place if you have further customized your control surface set up.
Or consider the method suggested in ' For the paranoid '. If you try to delete one or more control surfaces from Logic's set up screen this will likely cause a crash.
GarageBand 10 users have a bit simpler situation since GarageBand starts each time with no registered control surfaces. If you wish to change between say Logic Remote and gbXRemote, or just want to use a different iDevice, you should save your project and exit GarageBand. Obviously this is not an ideal situation but it is the only way to avoid problems until Logic and GarageBand safely support multiple OSC control surfaces at the same time.
