Hi Karel,
Respectfully, I still don't get that - there are no "latency changes" involved. I always run my sessions at consistent settings; it's not like I'm changing anything while working. It's simply that any VE Pro buffers (1 or 2) get added to the bounced file; setting it to 'none' or disabling Logic's latency comp fixes it. I don't mean to sound at all argumentative, it's just that turning off VE Pro's additional buffers fixes the problem, so it seems logical (no pun intended) that the problem is on that side. Enough of that though - my knowledge stops at C+ programming, so I leave it to you to figure it out ;-) Besides, as I mentioned, the workaround is 100% dependable and very easy.
As for working at higher buffer settings in Logic (512, 1024 or 2048), I don't see that as being a realistic option for anyone who wants to record their parts in real time as latency becomes a problem once you pass 128 for most folks?
Thanks as always for weighing in Karel!