Midi notes or audio region do not play at the start of a bar?

Question

I am having an issue with a midi loop I have created. If I let the song play a bit until it reaches the loop, logic works just as you'd expect it and everything plays correctly. But if I stop the song, or if I set the song into cycle mode so it repeats, the very first note of the midi loop is ignored, and not played.
So for example, if I set the cursor to start at bar 9, the starting point of the loop, the first midi note is not played. But if a set the cursor at bar 8 and let it play into bar 9 and the loop, all of the notes in the loop play correctly.
I found the following description of the same problem on another forum, but it seemed to suggest that there is no fix for this, which if true, seems kinda bad for a pro application. I was wondering if anyone knew of a workaround or fix to this, because its really annoying missing the notes, or having to expand the cycle region just to get all of the notes to play. Here is the text from the other forum:
_Logic doesn't play the very start of my audio regions when I start playback_
Question: If a region starts at e.g. 1 1 1 1, and it starts playing from the same position, it seems that Logic misses the first few samples - which is especially noticeable with fast-attack transients.
Answer: Apparently Logic doesn't use some kind of pre-play buffering. The workaround is to have your entire song start e.g. one bar later, at 2 1 1 1, and let Logic play from 1 1 1 1. This workaround obviously doesn't work if you've set up a cycle - in which case Logic will miss the first samples when it starts playing as well. Next time it loops through the cycle it does play properly. There's no workaround for this - it's a serious shortcoming of the way Logic handles audio playback. With cycles, you could resort to using the Pause instead of the Play button/command: this will let you start playback from somewhere before the start of the cycle instead of starting at cycle-start (which is what Play does).

Answer 1

I'm having the same problem.
one workaround is to change the delay to +1/192=20 in the delay box in inspector on the given midi track...but this is a terrible thing to have to do over and over again.
PLEASE help if you know what's going on.....I ran logic on my macbook and this NEVER happened. I just bought a macbook pro 2.5 and it's apparently now an issue?
I have searched the net for fixes, and none work....logic does have a pre-play buffer, but it's range isnt large enough to buffer the instrument I'm using...which means the range is less than 1/192...come on....that's messed.
If anyone figures this out, please message me back at [email protected]