Here's the scenario. I'm recording a MIDI part in Logic Pro (say, a keyboard part) and as I'm playing I make a mistake. No problem. I stop recording, move the playhead to where I want to start recording over again, set a count-in to something comfortable like 2 bars so I can hit record and get my hands in position, and then when I get to the bar where I had set my playhead, I start to play.
But Logic is stupid and for some reason considers my 'count-in' region live, so there's 2 bars of silence, which completely overlaps and replaces my previous take. So I just destroyed 2 bars of a good take and this is completely unacceptable.
What Logic doesn't seem to understand is it's a "count in". It's supposed to punch in where the playhead was, otherwise what's the point of a count-in? I could have just put my playhead 2 bars earlier if that's what I wanted to erase.
"Use punch-in or autopunch" you say. No, that's not right - I mean, yeah if I just want to fix a mistake for a fixed number of bars. But I don't need to punch OUT - I just want to keep going and not think about how long the song is going to be or have to fuss with out points or project length markers.
I'm sure there are outrageous workarounds like multiple tracks, take folders etc. That's all just inefficient and adding cruft to a very simple workflow. All I want it: count-in to not record MIDI data, or at least, to not replace the midi data under it so I can at least go back and adjust my region borders after the fact.
I would even settle for allowing count-in to record MIDI data so long as i could come back and then drag the start of that new region to where my playing ACTUALLY started and not lose the MIDI data that was "under" that two bar lead-in. But I have been playing with the recording preferences for hours now (hence the frustrated tone of my post - apologies folks) and haven't hit on the combo that will allow me to do even this.