logic crashs...need your help please!

Hi guys

I've stopped counting how many times I've written these next lines, and as I saw the need to repeat myself once again today, I thought - why not just write it down here, and any time anybody needs this advice, you can just point to here. Service, eh ?!? wink

So, if your system is somehow behaving strangely (freezes, lockups, crashes, crackles, BSOD's, lost functionality that was there yesterday etc.), one or more of the following tips should be tried before you resort to drastic solutions:

1: Trash the preferences. The global preferences for logic on your system is located in a system file.
In MacOS:
For Logic 4.8: Logic Preferences
For Logic 5 & Logic 6 OS 9: Logic 5 Preferences
On macOS9, the file is stored in the Preferences folder in the System folder.
For Logic 5 & Logic 6 OS X: info.emagic.logic
On macOSX, the file is stored in /Users/username/Library/Preferences/.
In Windows:
For logic 4.8, this file is called logic32.prf
For logic 5.5, this file is called logic5.prf
On winOS, the file is stored in either C:/windows or C:/windows/system, depending on windows version.
If this file is corrupted, it can cause really strange things to happen. The way to solve this is to move the file away from it's current location. This way, when logic boots up the next time, it can't find the file and will be forced to rebuild it from scratch. The reason why you shouldn't delete it right away is that this file stores your Key Commands, and if you use anything but the default KC's you can use the old prefs file to reimport your old Key Commands (Key Commands window -> import is found in one of the menus). After having done this successfully, delete the old prefs file.

2: Trash the Autoload. The autoload is the song that loads when you boot up logic. It is located in the logic folder.
As above, if this file is corrupted, all the songs you make with that file as a starting point will be corrupted too. If you relocate the autoload, logic will start with it's default song next time you boot it up. Now you'll have to rebuild your autoload, and this isn't done automatically - you'll have to do it yourself. If your autoload features that environment that you spent 5 days putting together, this may seem as a hell of a task, but often these things can be imported from your old autoload, hopefully without reimporting the thing that corrupted the file too. Once you're content with your new autoload, delete the old one.

3 Maintain you drivers. If the driver for any of your hw is corrupted or buggy, your system will suffer. Try to reinstall the drivers for the hw that you suspect to be the one causing the problems, even if the OS system management tools report the drivers to work correctly. The system may not see eg sample rate sync errors as a malfunction ... A lot of hw manufacturers frequently update the drivers, to enhance usability and correct possible bugs. These driver updates are usually available for download from the manufacturers website. Updating a driver may be the thing that solves the bug that is currently crashing your system!
Driver handling depends largely on the OS, and sometimes also on the hw in question, so it would be pointless to tell you how to update drivers here. Check your OS and hw manuals for details on driver handling.

Phew. Hopefully, now noone will have to write this info again. Just point anybody who needs this advice to this post :cool:

On 2007-06-24 13:43, Trip- wrote:
if not, you didn't change anything before logic started crashing?