The answer to your question is that your solution would simply be too simple! We need the mysterious strange behavior to keep us all wondering what's happening, and to give us something to talk about. The more serious answer is that permissions issues often cause strange behavior in the OS, not just in Logic. Sometimes when nothing else makes sense, investigating the permissions can turn up a solution. Speaking of funny strange behaviors... my favorite logic crazy bug is one time I was working along on a song, everything running great, then the screen froze and I got an error message in a dialog box. The message said something like this: "Too many nested levels". Then, the funny part... at the bottom of the box, where usually there is a button that says "Continue" or "Cancel" or something like that, in this box the button said: "BAD." That was it, no other way out, you had to click the button that said "BAD." So I clicked it and Logic put me right back where I was. No crash, nothing. Now what, do I save the song? Has it been corrupted? No way to know... All I knew for sure, it was BAD. - Dave On Jun 7, 2007, at 12:38 PM, Will Thomson wrote: > If this is the case, then I wonder why on earth the software can't > simply > warn/advise the user? Or could it be that OSX security measures > prevent such > detection routines? > > Will > > >> This can be a permissions error. If Logic does not have permission >> to write to the target path directory for the audio file, the >> recording cannot be saved. >