Time and Pitch appears completely unusable at 96k (I/O Error-36)-any ideas?

Question

Hi there,
Any help for the following gratefully received. Sorry about the excessive length of this post, but I've tried a whole bunch of things trying to sort out my problem and I'd rather list them all in the interests of clarity. (or should that be catharsis?)
My simple question is: Is there anyone out there who is successfully using Time and Pitch compression / expansion at 96k? I simply can't get it to work with any degree of reliability on 2 new machines I've tried it on, and I've even managed to crash the demo machine in my nearest Apple Store trying it out.
Some background: I recently ditched my TDM PT HD system in favour of a core audio Apogee Symphony based one. I use time compression / expansion of audio files extensively in my projects, and previously used the DAE version of Serato Pitch'n Time to do this. I've never rated the Logic Time and Pitch engine, so knowing that Serato and Izotope have developed Logic friendly algorithms was a big deal for me in finally making the hardware switch to a Mac Pro Twin 3.2Ghz Quad a few weeks ago.
I've had quite a few problems / errors running Logic since then, resulting in me swapping the Twin 3.2Ghz Quad for a Twin 2.8Ghz Quad a couple of days ago. I reckon most of those errors are outside the scope of this question, but I'm happy to reel them out if people perversely want this post to be even longer. All those errors now seem to be sorted with the exception of the following:
I've been trying to carry out a series of time compressions and expansions on a stereo 96k audio file to get it to play in time with my track, but the time stretching doesn't take place - I've been getting the 'I/O error Result Code= -36' message when I click the Process button. Not every time, but almost every time. It's more prone to do it with negative tempo change values for some reason, and if it does work, then an undo will almost certainly mess the audio up by not returning to the original state. It fails with both Logic's own algorithms and the dedicated Serato Pitch'n Time LE version. All other sample edit functions (say excite, denoise etc) appear to work correctly.
Knowledge base here seems to imply that I'm getting a disk read / write error. I've tried resampling the audio. I've duplicated it and tried the copy. I've moved it to a different internal drive, having taken the first drive off line. I've moved it back again. I have four internal drives and I've tried audio running off each of them alone and in combination. I've given the file a new name with no gaps or punctuation. I've tried time stretching a completely different audio file chosen at random, usually to no avail but sometimes it works a few times, then fails. Mono files seem to be slightly more reliable, but not much. I've fixed disk permissions and all folder permissions more times than I care to mention. I've reinitialised the boot drive and reinstalled Logic. I've even installed OSX on a different drive, and installed Logic on that one, but that didn't work. I've tried it with my extra 8GB of (reliably sourced) third party RAM removed. I was getting this time-stretching error on the 3.2GHz machine as well, so you could even say I've tried it on two different machines (though it should be pointed out they had the same RAM and Hard Drives).
At the Apple Store earlier today I tried to get a display machine (a 2 core MacPro) with a version of Logic on it (that I'd had nothing to do with) to replicate this error on the demo Logic song. When everything was 44.1 time stretching worked absolutely fine, many times, but once I converted one audio file from its default 44.1 kHz to 96 kHz and tried the time compression, up came the I/O error message. Now I can't believe it's a good idea to have different sample rates in the same song, so I converted all the audio files in the demo song to 96k in a different audio folder, changed the sample rate of the song so it would play back as you'd expect, saved and restarted, and then tried time stretching one of the files - it wouldn't do it, resulting in the I/O error again. Interestingly, after that even the 44.1 version of the song started showing the same error, even after another restart.
It seems like I should work at 44.1 if I want to time stretch, but I like to work at 96k and I should be able to.
This sounds like a proper bug to me and has been crippling my productivity, but I can't believe no one else has tried repetitively time stretching sections of an audio file at 96k - either have you been able to get it to work, or has anyone got any more suggestions I may not have tried out?
Thanks in advance. (Or have you all gone to sleep by now? Self-editing was never my strong suit...!)

Answer 1

Nevermind. I was low on disk space. Duh (though the error could have been a bit more descriptive).
Move along. Nothing to see here, folks.