10 x Tips for SPEED & PERFORMANCE in Logic Pro for iPad

How to improve speed and performance in Logic Pro for iPad

💾 Download Logic for iPad:

⏰ Time Stamps:
00:00 Introduction
00:28 1. Close all other apps
00:41 2. Turn off background apps
01:12 3. Create duplicate project
02:00 4. Delete unused tracks
02:40 5. I/O Buffer
03:33 6. Low Latency Monitoring
04:22 7. Convert Session Players to MIDI
06:33 8. Auto Freeze
07:21 9. Freeze Tracks (Manual)
08:14 10. Bounce in place

✔️ Support the channel:

🎞️ Other related videos:

🔉 Recommended Gear:

Note - Links provided in this video description may be affiliate links, meaning that if you choose to purchase products using these links, a small commission may be paid to me for referring you.

📢 Resources:

✉️ Connect with me:

#logicforipad #logicpro #logicipad

[mattyduknextgen]

really useful video, especially for those of us on older kit - one day I will give Apple some more cash !

[mrwindupbird]

This is extremely helpful, thank you Pete!! I have memory issues often when I use lots of plugins

[edzielinski]

Wow. I didn't know about a couple of these. They will come in very handy, especially the Auto Freeze. Thanks!

[lelongmckean]

Thanks, that’s really useful as I keep getting cpu warnings after adding 6 or more tracks where it auto freezes. I didn’t quite understand what freeze was. Thanks for the tips

[johnhamers]

Very important tips for everybody, everything nice in line presented by the most friendly host on the planet. Thank you Pete for all tight and devoted work. 💯🙏🏼✌🏼

[ScreamieBirds]

Love it! Thanks for the tips! Wonder which approach is best - freezing, bouncing, or midi?

[tylerhill]

Do you have any tips for quick arrangement tricks? I don’t have keyboard connected for using key functions.

[jamesbastani]

Automate your plugins to turn off when they’re not being used. Especially effects plugins on MIDI tracks. As long as they’re active they tax the CPU even if there’s nothing happening on the track. Also “bip” with the mute the original option as you go along. Then instead of processing all the MIDI data the CPU is just playing back an audio file with the effects baked in. The problem with freezing, especially if you have a long project is that every time you unfreeze to make adjustments and freeze again, it’s going to take its time analyzing the whole project and start freezing from the beginning to the end which can be time consuming. Same thing with the session players. As you mentioned they are very CPU intensive. Program the session player, convert to MIDI, bip, and delete the session player track. You can always add a new instance, add or edit parts and repeat the process.
Of course non of this is necessary if you’re just dealing with just a few tracks (under 10). But when you start processing individual drum kit pieces, tracks start piling up and if you’re using the session drummer, that means you have a dozen instances of the session player engine which can play havoc on the CPU. After you convert to MIDI, you can use “separate by note pitch” (a feature that I have not seen being used on any tutorials) to have individual tracks for Kick, snare, HH, etc.
usually after I create the main groove for the drums, I convert to pattern region which allows you to stretch out the pattern instead of copying and pasting. Then use the session player to design and insert my fills before converting everything to MIDI and then bip.