Logic Pro Help

Mon Sep 05, 2011 5:33 pm

Hi there
I've had this error on my home system, and now I'm on the road with my Macbook pro and am getting the same error with a totally different system! Any ideas?
I saw on google searches it could have something to do with firewire drives, and I am using one. Could that be it?
I/O error Result code = -36

Latest macbook Pro.. 2GHZ
OSX 10.7.1

Mon Sep 05, 2011 6:18 pm

What drive is it, FW400 or 800?

Mon Sep 05, 2011 9:04 pm

800.
Turns out one of the midi regions I bounced in place to audio was causing the error. When I deleted the audio region and re-bounced it, then everything was fine. Still though, I'd like to know why it happened in the first place.

Mon Sep 05, 2011 9:17 pm

Hey, sometimes Logic does some "illogical" stuff.

If that happens regularly, you might have an issue with your projects (maybe), but if it doesn't, hallelujah!

Tue Sep 06, 2011 12:13 pm

Uhhh its back. Everything was working great. i just went to get coffee, came back, hit play to review what I just listened too and the error comes back every time I hit play.

Tue Sep 06, 2011 12:54 pm

Are you using a RAID setup on your external? If yes, that could be the issue.
Raid is not necessarily faster for audio. Definitely for video because of the needed bandwidth.

Tue Sep 06, 2011 1:09 pm

Nope not using Raid. Just an external firewire 800. I had the exact same problem on my other system which was completely different. This one has new laptop, drives, etc and now the same problem. I think it has something to do with firewire

Tue Sep 06, 2011 1:18 pm

Well I don't think its firewire now. I used the USB ports on the firewire drive and still got the same problem. Even unplugged it, same result. So it has something to do with the audio I bounced within the project. If I delete all the files then it works, but obviously I can't do that. Is there a way to resave the audio files or somehow restore them? If I deleted a particular file as I did in the beginning of this post, then it seemed to fix it, but now I can't find the file, instead I have to delete the whole thing. I'm slightly convinced this has something to do with a recent logic update as I rarely had this problem earlier in the year

Tue Sep 06, 2011 2:48 pm

This has started happening to me a lot recently. Latest logic, new macbook pro, LaCie little big disk.. it seems to happen a bit, then stop by itself.. then happen again.. ??

Tue Sep 06, 2011 3:07 pm

After messing with it, taking audio tracks out and putting it back in it would work. But if I left the computer for 10min the I/O error came back, then it would start again. I'm experimenting with changing the power settings to see if it has something to do with that. Man what a pain this is.. and I have a deadline too. Sucks

Tue Sep 06, 2011 3:27 pm

Arkadi,
Is this a Western Digital drive? They are somewhat known for this error...

Tue Sep 06, 2011 3:43 pm

Nope it's an OYEN, but my internal mac drive is a solid state. I ruled out firewire though, cause I disconnected the OYEN and am getting the same error.
Strange thing is, I've gotten this exact same error lately on a completely different mac system. Just now I got the error again by just saving my project under a new name.
If anyone has any ideas I'd be most appreciative. This is one of those 'my career hangs in the balance' deadlines. I'd pay 10K to never have this problem again, as thats the amount of money I'm going to lose if I don;t turn in my project tonight.
o_O

Tue Sep 06, 2011 3:53 pm

According to this thread it's a bug thats been introduced in the last couple updates.
https://discussions.apple.com/thread/27 ... 0&tstart=0
Is there a way to revert to an older logic without reinstalling the whole thing?

Tue Sep 06, 2011 3:55 pm

Arkadi wrote:
Nope it's an OYEN,

They don't make the actual drive. Open system profiler and see what it says for "model". Does it start with WDC?

Anyway, use disk utility and repair the drive, or better, DiskWarrior if you have it. If that doesn't solve it, you may need to multipass low level format the drive to be sure bad sectors are mapped out.

Tue Sep 06, 2011 4:00 pm

Like I said, I removed the drive completely and the error remains. But I checked anyway and its a Seagate Momentus 3Gb/s (ST9750420AS).
My mobile system, computer, drives, etc... is less than a week old. Everything brand new. Based on the link I posted in my previous response, I'm totally convinced it's a bug in a recent update in Logic 9.1.4 (or 5) since I had this exact same problem once I updated Logic on my home system with totally different gear.

Tue Sep 06, 2011 4:23 pm

Well the studio is waiting for my score and I'm totally dead in the water with this I/O crap. Thanks Apple for destroying my career with your buggy software. I shelled out 4K on Mac products JUST so I could use Logic while out of town and I'm stopped dead in my tracks because of this.
Anyone hiring at Starbucks?

Tue Sep 06, 2011 4:29 pm

Arkadi wrote:
I'm totally convinced it's a bug in a recent update in Logic 9.1.4 (or 5) since I had this exact same problem once I updated Logic on my home system with totally different gear.

Yes. It could be that previous Logic versions ignored more minor hardware error reports and now they've made it more "sensitive" to them.

New drives have plenty of bad sectors too. The drive firmware maps them out as long as it catches all of them. Unfortunately they can be intermittent which is why, in some cases, a multipass low level format is needed to be sure it catches them.

Tue Sep 06, 2011 5:06 pm

I just ran out, bought a new drive, copied the project over, opened it up and problem remains.

Tue Sep 06, 2011 5:41 pm

Were any of the files/folders ever copied to/from a FAT formatted drive? Or have they always lived on your HFS drives?

Tue Sep 06, 2011 5:46 pm

Always on mac drives. Desperation is setting in now.

Logic Pro Help

I/O error Result code = -36, Fade Update Failed (Error -36)

I/O error Result code = -36, Fade Update Failed (Error -36)

Logic Pro X 101

Apple Certification Class

Los Angeles, CA

January 23-24-25, 2017