Too Many disk I/O tasks (-10022) error playing song after edits

Yes, when I tried to do a few flex edits over a group of 11 drum tracks, I also got the -10022 too many disk I/O error... several times. I turned off flex mode and no more problems.

Also, while playing the tracks after flexing, I observed phase shifting between the grouped tracks (even though they were "phase locked"), as if Logic was having trouble processing the flexing while playing in realtime... I made another post about this but as of yet no solutions.

I do not have a recommendation other than just turning off flex editing and going back to traditional chop and nudge editing.... which seems to work great in Logic.

After hearing the phase shifting, I feel I cannot trust the flex mode... I'm too worried that somehow this phase shifting will somehow make it to the final work, can't have that. My uneducated guess is that Logic just can't handle a lot of flexing at once, as in 8+ grouped tracks. Maybe it works ok for single tracks though. I can live without flexing personally though it's a nice concept if it can be made to work.

beach ball boy wrote:
After hearing the phase shifting, I feel I cannot trust the flex mode... I'm too worried that somehow this phase shifting will somehow make it to the final work, can't have that. My uneducated guess is that Logic just can't handle a lot of flexing at once, as in 8+ grouped tracks. Maybe it works ok for single tracks though. I can live without flexing personally though it's a nice concept if it can be made to work.

I had read the the Flex mode edits are loaded into and played from RAM, I would imagine trying to read other audio from a drive and moving flex mode data through RAM is a little much, have you monitored your CPU use (Logic's CPU meter) when you're hearing the pahase problems?

pancenter-

Have you any idea Pancentre, of just how Logic deals with flex time? I mean is it a real time timestretch, or is it done some other way?

Because if it is, and you've got loads of them running, then that must be one **** of a drain on processing power.

bill borez wrote:
Have you any idea Pancentre, of just how Logic deals with flex time? I mean is it a real time timestretch, or is it done some other way?

Because if it is, and you've got loads of them running, then that must be one **** of a drain on processing power.

Bill, not sure right now, I keep meaning to take an existing project and work with flex time, I have a suspicion it's a real-time operation until bounced.

Getting ready to play (guitars, banjo, uke) in the Broadway touring version of Spamalot as it comes through this area.

pancenter-
Getting ready to play guitar in the touri

Just my 2 cents, but per my experience with the behavior of flexing, it really does seem to act like it's being processed in real time... especially when getting "too many disk I/O - elastic audio" errors while trying to play heavily flexed sections.

I have not yet had a chance to go back and review CPU usage etc while playing flexed sections because quite honestly, since I had the trouble, I have not used flexing... avoiding it for now... trying to meet a deadline with the current audio project. I'll perhaps experiment more at a later point.

But what I can tell you, when playing over flexed sections with 11 grouped tracks, phase shifting is heard and it does not always seem consistent.... as if the processor is just not cutting it in real time. That's my best guess at this issue. What I am hearing is definitely phase shifting, in another thread there are people questioning whether or not I know what phase shifting sounds like, trust me, I know what I'm hearing... it sounds like some of the tracks have been slid around by a few samples or whatever with respect to the other tracks, very noticeable in headphones.

I guess if the flexing sounded ok while bouncing it, it would be ok... but i'm just too nervous to take chances at this point... I would not want to accidentally bounce in even the most minor phase issue, only to find it while mixing at a later point and then maybe no longer having the ability to fix it etc...

I have 16GB of RAM, just mentioning it... still have "phasing" while flexing if that means anything.

I think flex is great, if you use it to tighten audio up and then bounce in place after.

FTR: I take it you didn't solve your drum phasing problem.

No, didn't solve it yet, after I'm done completing work to meet a deadline, I will do some experimenting and see what I can figure out. But so far I've had this phasing issue occur in two different sessions on two different rigs (both Mac Pro dual-quad core with lotsa RAM)...

One test that anyone could try... to really max it out... take one single source and record it onto 20 tracks at once... or I guess you could just record one track and then duplicate it 19 times, whatever. Group all these tracks, keep `em all at the same level. Then take a listen to all tracks at once using some good headphones.

Then put all the tracks in flex mode and do some flexing, flex every single quarter note this way and that way for three full measures or so, whatever. Then play it back again with headphones. If you hear ANY hint of phase shifting, then you are experiencing what I am experiencing.

For anyone who might not be familiar with the "phase shifting" sound I speak of, it pretty much will sound as if you are running your tracks through a classic "phase shifter" effect pedal or whatever. If using headphones, it'll seem like the audio starts swirling around in your head like some wacky stereo effect, frequency response will change and shift, etc.

I've noted that I have not always heard phase issues when flexing, it seem to be a bit inconsistent. It may be because I've been working in some very large sessions, maybe in my situations Logic was already being heavily taxed and then the extra flexing just put it over the edge. Don't know. Will do some testing perhaps next week.

But, I'd say everyone should be careful about this before bouncing forever to disk and then maybe deleting all your old raw audio, because if you permanently write in some wacky phase shifting between your group of drum tracks and have no original raw files left, you'll be in very big trouble... I don't think there would be any way to fix that. In a professional level mix, that type of issue would stick out like a sore thumb. I guess one fix would be to apply a phase shifter effect across the entire drum bus... on purpose... as some sort of artistic statement... hey, it might sound cool! 🙂

This whole issue has made me realize how incredibly important it is for DAW tracks to remain truly phase locked at all times. Been working with DAWs for years now and never really thought about it. In one regard, this is a lot to ask... to make sure your 30-odd tracks or whatever are always dead in time with each other, to the sample. It's certainly of critical importance, at least for multiple tracks of the same exact source (like when you have 12 mics on a drum kit etc).

Actually, perfect time synch is just as critical for even a mere TWO mics on a given source... any stereo recording. Once one track goes out of "synch" with the other, even by a minute amount, just for a short amount of time, you will HEAR it.,.. and it won't be good... unless you desire a wacky phase shifting effect.

I just got this error today. On ONE rhythm guitar track - lots of alternate takes there but they are all muted. There are a few other audio tracks but no flex on them. I'm using flex slice mode for the guitar track. I only get it in one place in the song, and I can't figure out why. There is nothing unusual going on there. Just a lot of VIs which synthesize or pull samples (off a different drive).

My CPU meters are only around 30% and I'm on a velociraptor drive.

Pretty lame.

Speaking of phase accuracy, in general I think the flex quality is pretty bad in Logic. Slicing is ok on some things, and Polyphonic Complex is just so-so. The other settings are totally unusable most of the time. I sure wish they would license the Prosonq Time Factory algorithms like Dirac and ClearScale-or at least something a level up from what it is now. Not impressed.

I recently learned that it is essential (for phase locking to work correctly) that the grouped regions have the exact same start and endpoints.

Don't know if that applies to you (or if I have gotten it all wrong).

Aside from that, I find flexitime most esoteric.
Sometimes I get strange pops after edits.
Then they just disappear automagically after a few passes.
Or not.