Error Message with Flex Editing (Elastic Audio)

Question

Hello....
We have a song project where we are currently grafting in bass tracks to suit the existing drums. The drum sections (verse, chorus, etc) were all recorded piecemeal one section at a time in their own unique projects (btw, everything has been tracked in LP9). Once the drum sections were completed, I then "Flexed" them and then imported all of those drum tracks into a new "Master Assembly Plant" project where mixing would begin. So far so good. In this "M.A.P." project I have penciled in the required tempo changes (via the global tempo track) and I have noticed that the new Flex Editing feature gets completely confused when a Region with Flexing is placed somewhere overlapping where there is any sort of tempo change. I am assuming that when Regions are analyzed for Flex markers that Logic embeds the tempo info into the region. Many of our drum sections were tracked at 117 BPM. Some were faster, some slower, as the song required. So when I assemble these various drum regions into the "M.A.P." project, anytime one of those regions overlaps a tempo change point, all sorts of havoc begins. The workaround we have been using is to snip the region at the same point where the tempo change occurs and then exclude Flexing for the part of the region that overhangs into the new tempo. Seems to work, albeit certain Regions then give up the Flex. Not a problem but that sort of defeats the purpose of having Flex Editing, yes? Once I got the drum tracks to my liking I then bounced out a rough mix for a guide track for the bass player to begin tracking bass.
So to make matters a bit more tricky, we have been tracking electric bass parts against that new rough mix bounce of the drums, and in order to keep things tidy, I copied the tempo changes/data into the bass tracking project. This is where the real trouble has begun. If a bass section starts at say 117BPM and then needs to gradually bump up to 125BPM, the metronome click is fine, the rough mix drum bounce is fine, and the bass is as recorded. But when we try to Flex the bass track Regions, the audio wave forms get all moved around randomly. Turn the Flexing off and all is back to normal. But for some reason Logic doesn't want to Flex in time with any tempo changes. Again, I'm guessing the tempo a recorded Region began in is somehow embedded into the Region? So a Region that starts in 117BPM but ends in 125BPM is only Flexed as if the entire Region is at 117BPM? When the tempo begins to change the Flex/Transient Markers get all screwed up and confused. Also, Logic chokes (although the audio keeps rolling along just fine) and it gives me this error message:
*+Logic Pro:+*
*+Unexpected request for audio data.+*
*+See console. (Elastic Audio)+*
(-10024)
Anyone else run into this issue?
I'm on a 2.4 Core2Duo MBP running Leopard (latest but not SL).

Answer 1

I have also experienced this, and gotten that same error message. And yes, this was in songs with some tempo changes.
It appears, at this point, that flex editing is NOT possible on regions recorded with tempo changes in the Logic song.
The recorded audio always plays fine, but as soon as you analyze it for flex editing, the markers are everywhere BUT the transients, and the track plays completely out of sync.
Its a mess... does anyone at Apple listen to, or create music that isn't 4 on the floor? Just wondering...