Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Thread

Logic Pro crashes... -And NO "crash save" upon re-boot...

Logic Pro crashes... -And NO "crash save" upon re-boot...

2007-01-21 by c_eisenhardt

Hey all, I'm a Logic Pro user (v7.2.3) using a G4 PowerBook 1.67Ghz w 2 Gigs of RAM...
I have an m-audio AudioPhile FireWire interface, Lacie drives, an MOTU MIDI interface for my 
external synth gear & various synth/fx plug-ins...
My problem is when Logic Pro crashes, there is no "crashed song file" upon re-start...
When I was using Logic Express (v7.1.1) some months back, Logic always saved a crashed 
song file "snap-shot" which was a life saver... Now with Logic Pro, I always lose everything 
when it crashes. 
I tried using a free-ware program called Logic Autosave but it doesn't seeme to work with the 
current version of Logic Pro...
BTW, I DO have my prefs set in Song Settings so that AutoBackup saves most recent version...

Is there anyone else with this issue? And what can I do to remedy this problem?
Thanks in advance...

charlie eisenhardt
3:jet

Re: [Logic_Cafe] Logic Pro crashes... -And NO "crash save" upon re-boot...

2007-01-21 by GAmoore@aol.com

I usually don't get crash file saves in Logic 7.1.1. I think it depends on 
the type of crash. I just save often, so when the inevitable crashes come, you 
don't lose too much. I also try to not use a lot of virtual instruments, 
especially ones like Sculpture or GPO. I am thinking to try to freeze things or 
convert to audio, then use the audio files, but save the previous version of the 
file in a folder in case I need to re-do it. I think Logic works pretty well 
with audio/midi - but the softsynths and plugs bring it down - despite the cpu 
meter readings.


[Non-text portions of this message have been removed]

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.