10 Troubleshooting Tips for Logic Pro

[@MusicTechHelpGuy]

In this video, I detail 10 tips and tricks for troubleshooting Logic Pro. After 20 years of working with Logic Pro, and 15 years of teaching Logic Pro and music production in college courses, I've identified these 10 troubleshooting techniques that generally will fix MOST issues in Logic Pro. Enjoy! Support the sponsor of this video! Boombox ➛ bit.ly/boomboxsponsor Download my 35-part Logic Course here! ➛ www.logicproguide.com For mixing/mastering work, contact me at my website ➛ carneymediagroup.com Follow MusicTechHelpGuy on Instagram ➛ instagram.com/musictechhelpguy Support the channel on Patreon ➛ patreon.com/musictechhelpguy Chapters: 0:00 Overview 0:53 Boombox Sponsor Segment 1:37 System Overloads 3:40 Sample Accurate Automation 5:09 Sampler Virtual Memory 6:38 Freeze Tracks 10:10 Sync Error 11:10 Simplified Mode + Initialize Key Commands 12:42 Reset Settings 13:21 Delete PLIST 15:34 Corrupted Projects 18:45 Corrupted Plugins 21:06 Wrap-up

[@FrankBrickle]

Once again, great stuff.

[@CraigStuntz]

Sometimes when Logic Pro won't open a project due to a misbehaving plugin, the problem is the configuration of the plugin within the project rather than the plugin itself. Reinstalling the plugin won't help in this case. The fix is to hold Control when starting Logic Pro, then select "Launch Without Audio Units". You can load the audio units one at a time this way and you can remove a misbehaving plugin from your project without loading it (and perhaps re-add it later).

[@bellxfm1]

Excellent as ever, so many useful tips in here, entering aspects I wasn't aware of. Many thanks sir!

[@justthefacts4965]

TURN OFF "FULL KEYBOARD ACCESS" in system settings under Keyboard if Key Commands is screwy, ntm other things in other apps. It was COMPLETELY screwing up Logic after upgrading to Sonoma. It reassigns key functions or something so for eg space bard wouldn't start/stop play, and nothing else worked. I was messing with key commands, couldn't use Logic, importing new ones for hours, and that was the problem. Thanks, Apple. Another great UI decision.

[@thundersnow819]

Josh knows how I like to get down on a Saturday Night!

[@spacecowboy373]

Has anyone else encountered the problem in Logic where you drag audio or MIDI tracks around in your arrangement, and even with snap to bar on, sometimes they wont land exactly on the bar. Super annoying because if the problem isn't noticed immediately, which often it wont be because the tracks look like they are on the bar until zoomed in, then the problem snowballs into your whole arrangement being out of time, and it takes a long time to fix. Must be a bug but it's super annoying.

[@cutseencinematics]

You need to change snap from relative to absolute

[@cutseencinematics]

Also turn off ‘smart snap’ and use division/beat/bar instead

[@hcj1967]

THANK YOU! DELETING the PLIST file fixed my M1 Mac mini 16GB RAM. While playing a song, Logic Pro II kept crashing and gave a weird System/Disk is to Slow message anytime I would try to switch the session player it would crash and loading sounds was taking longer than usual to upload the audio files. Now when I play a song, and switch it nearly does everything instantly and doesn't crashing. I hope this helps some of my fellow musicians and producers out there!! Sending God's love and peace to all my brothers and sisters out there!!

[@olegnesterov3467]

Hi Josh. I have 12 core (24 threads) 2012 Mac Pro. For some reason Logic uses only 4 cores and 5th one for master plugins. I tried to do settings as "Automatic" and "24 threads". No difference. All mastering plugins go to same core. When I turn them off Logic uses only 4 cores. Is it normal for logic using only 5 cores? How to use all of them? OOPS. After unfreezing all cores got in use but all mastering plugins use same core and I get overload.....

[@philippdrflr]

Hi Josh, there are some plugins where you have to download the .component file and drag the file manually into the right logic folder. Unfortunately, Apple then says smth like „cannot open file bc it’s not a certified source“ with an error message. Do you know how to fix this? And thank you for everything! Your videos are so helpful, thanks.

[@adampavelec857]

I’m currently battling an issue with Logic where each and every time it’s opened, it has to scan all AU components. Totally sux with having some of them bound to an iLok!

[@moisejo]

I have an issue with my microphone signal while recording, if i'm yelling or speak quieter the signal is muted. it's like there is a supper aggressive noise gate and limiter. It's only on Logic Pro, GarageBand in the other hand, work perfectly.(in other Daw or device my mic is normal, only when i start it on logic)

[@bwm5150]

Always been a very great help and source of info with these videos, thanks!

[@jasonfashe2234]

Magnifique! Thanks a lot!

[@flexisguevarra5696]

sir, my mac was upgraded to Ventura, they say that I have to downgrade to monterey....HOW can I do that if its True .thank you Sir, in advance.from: the Philippines.....

[@jamesbastani4295]

Thanks for all your videos. I was hoping you’d cover how to fix a “conflicted copy” issue. I compose many of my pieces on LP 4 iPad and if the devices are synced, the project automatically migrates to my desktop. From what I understand this results from a syncing issue. I’m directed to find the original which is nowhere to be found. Any help would be appreciated. I was almost done with a 25 track project on LP 4 iPad, ready to open it in on my computer to add vocals, took a break, and when I returned my project was gone! Now all that’s left is a conflicted copy in the Files of my iPad Pro. Thanks.

[@wesleycurryii3341]

I use a Yamaha P-125 (Weighted Keyboard) with LOGIC PRO X to input my tracks. Every so often (about 15 minute intervals) the Keyboard shut OFF for unknown reasons. Then I have to go into SETTINGS and Re Establish the INPUT and OUTPUT section. I do not know why this is happening, but it is frustrating when I am in the middle of a recording session and I have to APPLY the re connected INPUT OUTPUT function. Can you tell me any cause that makes this happen? I have been a learner and user of your very fine tutorials for 8 years, and think you are really intelligent and a great help in my daily work with LOGIC PRO X. Thank you. Wes.

[@CrankyOldNerd]

What about core MIDI failing. Hangs at launch and won’t work. Ableton or other apps work fine but logic/GarageBand hang and error out.

[@PeteMel1875]

Nice one 👍

[@guglielmonigro]

Perfect!

[@Calciumchlorid]

you re the best. really

[@rajivmusic9519]

thanks buddy 😎

[@dantethompson167]

Great Video Tutorial! Thanks!👍🏾👍🏾👍🏾

[@galefraney]

Out of curiosity I asked ChatGPT 4 whether changing "Summing" back to 64 bit (High Precision) after already previously recording and mixing tracks in 32 bit (Standard Precision), whether the sound quality and resolution of the tracks would all be reset to 64 bit. It replied that this is not the case, that it does not retroactively improve the quality of the audio. Here's a portion of ChatGPT 4's specific reply to this question: Switching the summing mode in Logic Pro from "Standard Precision" (32-bit) to "High Precision" (64-bit) at the end of a project doesn't retroactively improve the quality of audio that was already mixed under the lower precision setting. Here’s why: 1. **Initial Processing Precision**: If you mix and process your audio with the 32-bit setting initially, all of the summing and processing during that period uses this bit depth. This determines the precision of calculations and handling of audio data during those processes. 2. **Potential for Improvement**: Changing to a 64-bit setting can increase the precision for any subsequent summing and processing. This means that any new audio tracks added or further processing done after switching to 64-bit will benefit from the higher precision. The conversion doesn't upgrade the already processed tracks; it only affects how new data and changes are processed from that point forward. Thus, while changing the setting might influence future processes, it won’t change the inherent quality of what has already been mixed and processed in 32-bit. If your project demands the highest possible fidelity from start to finish, it’s best to use the High Precision (64-bit) setting throughout the entire mixing and mastering process.

[@MusicTechHelpGuy]

ChatGPT is confused about recording bit depth and operating bit depth. If you record an audio file at 16-bit and then just up convert it to 24-bit it will make no improvement on the audio, that is true. However, the summing mode is referring to the operating resolution of Logic's mix engine, which is separate from the bit depth of audio files within the project. Unless you are printing down your busses to audio files or bouncing the project while in 32-bit mode, changing the summing engine in the middle of a mix does in fact increase the resolution of the mix engine. None of that really matters though because you're not going to hear an audible improvement in quality any way, you're just operating at a higher resolution.

[@galefraney]

When I input your feedback to ChatGPT 4 ... it is now agreeing with you. You are correct. It's possible that when I initially asked the question, I might not have been specific enough. I was actually curious because in other software like video or image editing software (ie: After Effects, Photoshop), upgrading bit depth after already working on footage or images at lower bit depth would definitely not improve it retroactively ... so I was curious to see whether this same principle would be applicable to Logic Pro. That's why I asked ChatGPT 4. Anway for what it's worth, when I re-phrased my question and input your feedback, ChatGPT is now agreeing with you. Here's it's second reply 😊: ... "When you change the Summing Mode from 32-bit to 64-bit in Logic Pro, the internal calculations of how the mix engine processes the audio are upgraded for all tracks, including those that were previously mixed under the 32-bit setting. Here’s how it works: - **Processing Resolution**: Switching the summing from Standard (32-bit) to High Precision (64-bit) means that all internal mix bus processing, including sums and routing operations, will utilize the higher resolution going forward. This includes handling audio data that was mixed earlier in the project under the 32-bit setting. - **Impact on Previously Mixed Tracks**: Even though the audio tracks themselves were mixed under the 32-bit setting, the change to 64-bit processing applies to the summing and routing stages that follow. This means any new mixdowns, effects processing, or additional routing applied after the change will benefit from the higher precision of the 64-bit engine. - **Real-world Benefit**: While technically the resolution of the mixing operations is higher, the actual audible impact may not be significant, as mentioned earlier. The key advantage of 64-bit summing is in handling very complex mixes where subtle improvements in processing precision can help maintain clarity and reduce mathematical errors, but for many projects, the difference might not be easily perceptible. Overall, changing to 64-bit summing enhances the processing resolution for all elements of the mix, regardless of their original mixing resolution, by providing a higher precision environment for summing and effects processing.

[@13thJ]

Ever since the latest update I have ran into a massive problem with my projects crashing It took me a while to figure out why but I finally realized it's happening whenever I'm using the pitch correction Which really sucks because that's been my new go to for manipulating sounds recently The workaround that I've been using is to drag a sound sample into the sampler then play it at the pitch I want then bounce it in place Hope that helps somebody else that's having problems with the crashing when you're trying to play with your pitch ✌️

[@ekansh702]

I am having the same problem but only whenever I am dragging a sound into the logic default sampler,my projects are crashing.

[@13thJ]

@@ekansh702 which sampler are you using? The optimized?

[@vewilli]

Very helpful. I will need to watch this more often, depending on what problem occurs. Thanx a lot!

[@cutseencinematics]

That too about importing tracks from corrupted projects is genius! I’ve never had a corrupted project (as yet) but it is cool to know this functionality is there and often works 👌

[@bassManDavis1953]

Josh, what a much needed tutorial, so many great tips and tricks of the trade. thank you so much

[@psylent01]

Fantastic, bookmarked for future use!

[@normjones6916]

Your best all time video 🎉🎉🎉❤❤❤ a life saver, thanks

[@Stratguy10NZ]

Brilliant! Thanks so much

[@drjthornley]

This is GOLD! Massive thanks.

[@soontaek]

Awesome stuff to know! Thank you

[@nubianrose_theband]

Please do a follow-up and include the issue with ”an audio unit has reported a problem…” wo telling wixh audio unit. That have been driving me nuts for s long time. I have kind of figured it out how to find the problem, but only kind of. Keep up the good work! 👍

[@mchest7000]

Same here, I've only had this with LP 10.8.1 on Ventura 13.6.1. It's a right pita.

[@artprojectsnz]

Great stuff.

[@emmanuelbonilla4375]

Way 2 go!!!

[@mrflynn01]

1st 🔥🔥🔥

[@capturejay3079]

Always grateful for your help!