Home > sldds > Logic Pro X – Disk is too slow or System … – Apple Community

Looking for:

Logic pro x disk too slow free download

Click here to Download


Configure your system Follow these guidelines when configuring your system for use with Logic Pro: Quit other apps when using Logic Pro. Make sure your Mac has the maximum amount of RAM, especially if your projects usually include many plug-ins or multiple instances of the EXS24 sampler. Save projects with high track counts to a dedicated storage device such as an external USB-C hard drive or an external solid-state drive SSD instead of saving projects to the system drive of your Mac.

Learn more about which file system is best for you. Choose any other additional options to streamline your workflow. Choose Custom from the pop-up menu in the LCD section. Double-click the CPU meter to open it in a new, expanded window. Process Buffer Range: Set this option to Large. If you are using ReWire, set this option to Playback Mode. Learn more about setting the Multithreading preference to optimize performance. Set automation preferences If your project doesn’t include automation, or the automation doesn’t need to be sample accurate, you can reduce the CPU load by turning off Sample Accurate Automation.

From the Sample Accurate Automation pop-up menu, choose Off. Choose the best sample rate for your project Projects with higher sample rates create larger audio files, which can increase the load on the CPU and disk. Use send effects When using CPU-intensive effect plug-ins such as reverbs and delays, you can reduce the load on the CPU by using send effects. Optimize software instruments Use these guidelines when working with software instruments: When mixing, make sure to select an Audio track or an External MIDI track, not a Software Instrument track.

Select a Software Instrument track only when you’re actively working on it. If your project includes Track Stacks, make sure no Software Instrument sub-tracks are selected. Freeze tracks , especially tracks with a lot of plug-ins.

Freezing Software Instrument tracks can increase the load on the disk, increasing the likelihood of encountering a system overload alert. Set the number of voices used in a software instrument to the lowest number required. For example, if you have a Sculpture track that plays only two simultaneous notes, you could set that instance of Sculpture to use two voices. Disk Drive Speed: If you have a solid-state drive or a rpm or faster hard drive for your audio samples, choose Fast.

If you are using a rpm drive for your audio samples, choose Medium. If your projects include a lot of audio tracks, select Average or Extensive. Optimize Alchemy You can also optimize Alchemy for improved performance. I purchased my new interface a couple of weeks ago and downloaded and installed the most recent drivers for it. There was nothing about them specifically being compatible with But I’d assume a company like Focusrite wouldn’t have sketchy drivers affecting all mac users.

I just downloaded Play v4. As for configuration, perhaps showing my naievity here but I had no idea it required any tweaking, assumed it should just automatically work as is. So it’d have to be a no on configuring it if it requires special settings to run smoothly on Logic.

Even so, to fail with only one instrument loaded into it is embarrassingly poor. There were no plug-ins active and no busses running. Literally One track of Audio and A multi-output instance of play loaded with one instrument and 3 software instrument tracks attached.

Attempting to record one midi line underneath the audio track and I get the error at random points throughout the process. Haven’t been able to get to the end of the track yet. Thanks for the link, I had a read through but couldn’t see anything on there which was applicable to my working set-up. It happens at a random point in the project rather than directly upon pressing play.

I usually get a minute or two into the piece then it’ll do it. I have read that Logic does this the first time a new instrument or region is introduced because it hasn’t had a chance to load it into the memory yet.

Every time I got an error I’d save, and relaunch, so perhaps this explains why I haven’t been able to move past it, because I haven’t really given Logic a chance to run through the piece more than once or twice, before closing it and starting over. Sep 3, AM. Hi Pancenter, I was under the impression that a larger buffer size increases performance but introduces latency. As I’m not experiencing any latency but am experiencing frequent errors I thought I’d put it up to to see if that changed anything, but it didn’t.

I was still getting the errors with a lower buffer size though. As I mentioned earlier I’m not using Space Designer or any other plug-ins. It’s quite bizarre.

Going to have another bash today and see if it’s magically resolved itself over night. You’re correct but it does depend on the drivers for the audio hardware, occasionally a smaller buffer is more efficient.. The Focusrite is plugged directly into a USB port correct, not a hub? What other active USB devices besides keyboard mouse do you have plugged in? Also what sample rate are you using? Yeah I can’t understand it. To be honest it could well be related to the inteface as I had no problems when I was using my MBox 2 with it.

The only reason I changed was so I could get something more up to date which would work nicely with Logic! The interface is plugged directly into the mac pro.

I also have an iLok an iSight camera, my cinema display, a printer and the apple keyboard using the other ports and the session is 24Bit I was on a project deadline, and returned it and went back to my FW Duet ver 1 and everything worked in both Logic and Pro Tools.

I really liked the interface and “check up” on driver development occationally. They have since updated the drivers since I owned mine, so it’s too bad folks are still having issues. Not everyone is, and many have them are working just fine, but the guys at Guitar Center said a fair amount of them come back.

Sep 3, AM in response to grayter1 In response to grayter1. After doing a little research online it seems the Scarlett is one of those USB2 devices that has issues with how Apple changed their implementation of USB when they released Macs with USB3 interfaces and put this updated implementation into Lion and later Mountain Lion Oddly enough some Win 8 users are also reporting similar issues with the Scarlett for much the same reason.

The March Scarlett OS X drivers are intended to ‘alleviate’ this issue but Focusrite have stated it is only to ‘alleviate’ in some instances and not completely fix the problem for everyone who has it,. However, the good news is that Focusrite have released some beta drivers v1. Note: These beta drivers again seem to only alleviate the issues for some people and not all but it has got to be worth giving them a try I would think Thanks for the update.

I was working on a project for TV and the Scarlett had problems switching from Sep 3, PM. Sep 4, AM. Community Get Support. Sign in Sign in Sign in corporate. Browse Search. Ask a question.



Logic Pro X Compatibility – Configure your system


Logic Pro Also any other apps running? Using Time Capsule or other backup systems? LogicPro I have not tried a hard shut down cold but for some odd reason over the last 12 hours the system is no longer showing the system and disk error prompts that stop the playback I have tested on the same projects, in the same measures – have open and reopen Logic numerous times. Hoping this was a fluke or corrupt preferences but have read others where the symptoms heals itself and then come back on LPX If it starts happening again I will do a cold re boot.

I also had a systems engineer Mac tell me today that I should also try and create a new user and open projects from the new user to see if there are corrupt preferences. Will keep you posted thanks. I have the exact same problem on my MBP. The Sample Rate is how fast Logic is grabbing audio as you record it. The faster the shutter speed, the faster the camera is capturing the image.

Samples Rates deal in frequencies over time. So a The good news is that The higher you go, the more you run the risk of System Overloads. So I would stick with Doing so can make a mess. By clicking on the number, a menu will pop-up and you can choose a Sample Rate that best fits your Mac. For example, leaving your web browser open while you work in Logic. Which will only further irritate your System Overload problems.

As you can see, I have 6 applications running in the background. If I really want a better performance out of my Mac, I should quit out of all them.

When your audio tracks have an input enabled, that means Logic is expecting to record. This takes up valuable resources. To remove an input, simply click on the input field of an audio track and select No Input :. Like tip number 4, Software Instrument tracks are also expecting to record at any moment.

When you have a software instrument selected, Logic gives more priority to that track. This will reduce the load on your Mac. So you add it to 40 of the 50 tracks in your project. Need to brush up on how to use Sends and Busses in Logic? Check out this post right here. Your project has tons of plugins and instruments. And dagnabit, you need it all! And that vocal line sounds fresh as hell.

Bouncing in Place creates a new audio file with your plugins and processing printed to the region. Freezing is actually a form of bouncing in place. Logic bounces the track, and any plugins you may have in use are now unavailable to use. But say you decide later that you do need to tweak a setting. When you Freeze your tracks, you can simply turn Freeze off, and tweak your settings.

When you Bounce in Place, you have to go back to the original track and then bounce again with your new settings. Freezing is easy. Click the snowflake icon and hit play. Logic will do its thing, and you should have more CPU for your project. Your Mac is running your OS, Logic, and a slew of other functions.

Tossing audio and virtual instruments onto the pile is a lot. By saving your projects to an external hard drive, you reduce the workload for your Mac. Now your external hard drive is handling the load for:. But they also come at a great cost. Just make sure it runs at RPM.

Remember all the talk before about the Buffer? It can be a little tough. And some Macs are limited about how much memory they can use. I would check out Other World Computing for info on changing out your memory. Logic is fantastic. But all the goodies do come at a price. This is great! I decided to take a break and check my email and here is this tutorial, fresh out of the oven. Its like you read my mind! Will definitely be using these to fix up my issues!!! Great and useful tips! I knew some of these roles already, but not all ones.

Thamk you! Thank you so much! I just got a MacBook and started using Logic and not even a week in and I got that darn overload message. However, these tips are so great and everything is okay now and my anxiety is gone. You really saved the day. Great resource and great solutions. Now, between latency and just lag in general, it slows down the creative process. Hey Rob, happy to help!

Thank you, great info and very well written. Only problem is I still have a the problem. Or should one delete all plugins on the unused track after bouncing? Is my machine dying or is 96 k that much harder for it?

What might need to be upgraded in my machine to make this work better? Ram, cpu? Any advice would be highly appreciated for I have found very little on this specific problem after days of searching. Everything is about virtual instruments and I have none in my session. Hi Michael, thanks so much for your comment! The number 1 recommendation I can offer is that a Sample Rate of 96k is overkill for most applications. It can crush your CPU usage. Most audio professionals work at Muting your tracks will not offload plugin processing.

But since the release of A safer bet would be to use Flex In Slicing Mode. If you arrange software instruments before all audio recordings, it is perfectly fine to start in I do also use only mono channels during arranging. Not every software instrument provides that option, but at this stage, where possible, I only use mono instrument with an approximate sound I intend to use. I also use lighter alternatives to the heaviest programs.

When the arrangement is done, I save all the settings I like to new presets and remove all plugins. I start with the heaviest program instrument and go as far down the buffer and range as my mac can handle.

Opens only one instrument and bounces one track at a time. Then I bounce one and one instrument with the same buffer, range and sample rate. Always save presets and remove plugin hides audio tracks when BIP before I start on next. When the heaviest instruments plugins need adjustments, I bounce all tracks to a stereo track.

Except for the instrument to be adjusted. Then I creates new project alternative. Deletes all tracks I am not going to use. Loading the bounced stereo file into the alternate project. Make the necessary changes.

Check that I have the correct buffer and range for bouncing from my notes. Then I bounce the instrument again. Saves the project and returns to the main project. Adds new audio file to the track. Thanks so much for that detailed reply Chris.

Anyway, during the mastering of my last album the studio scoffed at me for working at But I looked into it and saw it was recommended to go higher but no higher than 96K. I am liking the sound of it, especially if I have to manipulate the audio. Its funny I can time stretch and flex pitch no problem. I can use all the plugins I need.

Its just in a session where I am doing simple but extensive cutting and crossfading of an audio track really slows it down to crashing or beach balling a lot. Despite adding many more plugins.

As for Flex time in slicing. I so wish I could do that instead of hand edits.



Your email address will not be published. Required fields are marked *