Elastic Audio Error

[Kenny Gioia]

I'm a little perplexed by this error.

I'm currently editing about 25 tracks of drums and about 8 tracks of music that all have Elastic Audio on them. Set to Real Time Processing.

Every once in a while I got this dialog:

Elastic audio processing could not keep up. Your drive may be too slow or fragmented. Try decreasing the H?W Buffer Size or increasing the DAE Buffer Size. (-9473)

Which makes sense.

But what I don't understand is that I switched all those tracks to "rendered processing" instead and I'm still getting that message.

I was under the assumption that switching to rendered just makes new audio files so no processing is occurring.

Am I wrong?

[midnightrambler]

Yes! This has been bugging me too. DIGI?

[crisjohnnieb]

besides that, have you ever had a problem when you render elastic audio and it flips the phase of the transient making it sound weird? (like a reverse sound). It happens specially with snare drums. PT HD 8.0.2

[Kenny Gioia]

Originally Posted by crisjohnnieb

besides that, have you ever had a problem when you render elastic audio and it flips the phase of the transient making it sound weird? (like a reverse sound). It happens specially with snare drums. PT HD 8.0.2

When you "commit" or just switch to "rendered processing"?

[scottgreiner]

Anybody notice that "Rhythmic" mode ruins cymbals, and that "polyphonic" mode works much better...

[Alécio Costa]

I had a nightmare here as I received some sessions coming from a PT Mpowered backup.

No matter what I did, I kept getting ticks and glitches, at the start of the song. There were no more than 12 tracks with elastic audio enabled.

I had to bounce a few tracks. I have a MAc Pro with 5GB of RAM.

I got The same warning message Kenny describes when I added 100 audio tracks to this session. Tracks were distributed between 3 Sata drives.

[DigiTechSupt]

This is purely a 'drive too slow' error - essentially the same as a 9073. Rendering won't change this, since it's not the actual process of EA causing it - it's too many tracks from a single drive or other drive throughput issue.

[Kenny Gioia]

Originally Posted by DigiTechSupt

This is purely a 'drive too slow' error - essentially the same as a 9073. Rendering won't change this, since it's not the actual process of EA causing it - it's too many tracks from a single drive or other drive throughput issue.

That makes a lot more sense as I'm running 136 tracks in this session. All on one drive. I usually stay below 120 so I never see this error.

I seem to remember a different dialog for this in the past. The "Elastic Audio" mention is what threw me.

At least now I know what my drive can handle. Not too bad.

[Alécio Costa]

Yeah, but my situation is different: I have 3 Sata drives engaged. Not playing the whole session from a single drive.

[WildHoney]

Originally Posted by Kenny Gioia

That makes a lot more sense as I'm running 136 tracks in this session. All on one drive. I usually stay below 120 so I never see this error.

I seem to remember a different dialog for this in the past. The "Elastic Audio" mention is what threw me.

At least now I know what my drive can handle. Not too bad.

While this explanation seems to make sense, I don't believe it tells the whole story. I routinely get this error during playback with MUCH smaller sessions -- 60, 70, 80, 90 tracks -- running off an internal SATA 7200 rpm drive. Whatever the throughput issue is, it doesn't consistently come up only in larger track count sessions -- even more modest sessions, with few EA tracks, throw this error for me on a regular basis. Alécio's comment would indicate that it's not that cut and dry as well.