I have a similar request - probably similar enough that it would be implemented as part of the same set of options. Sometimes its been referred to as negative measures (I think Craig Anderton called it that in another thread), the need for me is the following:
The ScenarioWhen scoring to Video, I often have a start point for the music (SMPTE time code), but a run-up to allow the "live" musicians to sync up. I determine the tempo and meter for the first bar(s) and I need to I calculate the SMPTE time offset for the start of the run-up bars. If I get the tempo wrong (or I'm sloshing about to figure the right tempo), I need to recalculate the pre-run start point every time I change that initial tempo. If I had the negative bars, I could set the SMPTE time at 1:1 and then the run-up would be calculated for me.
Tempo variabilityWhile the run-up is most often at the same tempo as the real bar 1, bar -2, -1, 0 sometimes have tempo changes built in - this can happen for a number of reasons, but often to give the live musicians the ability to accel or rit immediately in bar one in a musical way. The analogy for this I like the best that jumping into a moving car is difficult to do, and it's even more difficult if the driver can't keep a steady pace.
It's also important to be able to run-up the video from an appropriate point, and that may require more than two measures.
Why not use count-off? The problem with using Countoff is twofold:
1. If the player anticipates (plays on top of) the first beat, it's cut off.
2. It's a steady tempo - not accel or rit.
Hopefully this will make it in someday.
PS - Sorry Noel - I know we talked about this years ago, but I couldn't clearly articulate the process I explained above. Hopefully it is clearer here.