Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Error: Logical end-of-file reached during read operation. Result Code = -39

Hello all,

Recently, I have been suddenly getting this error message:

"Logical end-of-file reached during read operation. Result Code = -39."

In my case, when it does come up, it always pops up during the recording of an audio take. Almost immediately after hitting the stop button, this error message would pop up. And then when I go to check the take that was just recorded, there is nothing but shrieking noise. As a result, this pop up error trashes any good take I may have had. It's unpredictable as to when this error decides to pop up as well. So now, when I record, I tend to just have my fingers crossed and hope that this error doesn't pop up especially right after recording a good take!

To no avail, I have tried different I/O buffer settings, repaired permissions, rebooted, and even re-formatted my recording hard disk.

Could this be a possible hint that my hard disk is about to physically collapse? I have had it for about 2 years. Could it be some sort of bug in Logic? Or something else perhaps?

Appreciate any feedback! Thanks a lot!

Mac Pro Intel 2.8 GHz Quad 8GB Ram, Mac OS X (10.6.3), LP 9.1.1, ULN-2

Posted on Apr 17, 2010 8:10 AM

Reply
18 replies

Jun 17, 2010 12:39 PM in response to DamonGrant

Thanks for that info Damon - I've been suffering with this problem a lot lately. And was pretty convinced it wasn't a disk access type problem of the types discussed earlier in this thread.

So Applecare is saying it could be a background process - time machine, etc - demanding too many resources that trigger the problem. And yet, I do a lot of recording tracks through busses to other tracks in real time in order to create stem files ready for delivery to other parties with fairly large track counts and never have a problem with this. Only when I'm recording tracks from an analog source does this happen - in my case, tracking live drums. Intermittently hit stop, and up pops that message and sure enough the last take (with its wave form displayed perfectly on the screen) plays as nothing but white noise, until Logic decides it doesn't want to recognize the file at all.

Maybe there are more resources involved with the "live" analog recording than with more internal real time "bounce".

David

Macbook Pro 2.6 Ghz Intel Core 2 Duo, OSX 10.5.8, 6 gig ram, Logic Pro 9.1.1, Motu 896HD

Jun 17, 2010 9:38 PM in response to David Crigger

Only when I'm recording tracks from an analog source does this happen


I think other people have made the same observation, and this suggests to me that the problem is not with the disk, or with other burdens on the CPU, but rather with the audio interface drivers.

I also suspect that the problem tends to happen when a project has been open for a while, and/or when a bunch of recording has already taken place since the moment when Logic was launched. This would be consistent with a certain kind of programming error (in the interface drivers) known as a memory leak.

A way to work around this might be to periodically relaunch Logic, before the problem occurs. Yes, that's a nuisance, but maybe less of a nuisance than experiencing this problem.

Instead of relaunching Logic, possibly the same benefit could be had by toggling Core Audio off and on. That is, the "Enabled" checkbox in Logic Pro > Preferences > Audio > Devices > Core Audio. Uncheck that box, and then press "Apply Changes," and then turn "Enabled" back on, and then press "Apply Changes" again. Will it help? Who knows. But it might be worth a try.

If I have been having the -39 error, I think I would try applying this technique if I was about to do a series of important takes.

Error: Logical end-of-file reached during read operation. Result Code = -39

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.